If your problem still exist, it is advised to contact their supporter directly.

Thanks, but I have had a similar problem some time ago that had been discussed by other users long before (freeze with DynDNS). It is true that even a German service person contacted me (which is good) but it took quite some time until TP-Link finally saw it's their problem, then I got a beta version (which resolved the problem) but then it took more than a month until that fix had been deployed in the "standard" release so others could fix that, too.

This time I have an error where I have no chance of looking into the logfiles because
If there is an offending machine, the logfile will not track its MAC address nor the offending packet.
[*]I will not be able to even access the logfile for the only thing I can do when the router gets stuck is to reset it. With a reset, to my knowing, all traces get cleared.
[*]Thus, even TP-Link is not able to learn from the incident. The only option is to reboot on site which I can't afford with my clients.
This is why I have to stick to my assessment until TP-Link opens up their machines for better examination and enable coredumps or permanent logs.