Unfortunately same issue after 19hrs and 21min with VR400 v3. As you can see CRC errors raised to 700k suddenly and internet became useless. I think VR400 has the same chipset (Mediatek) as VR2100 so i didn't think it will be fix the problem.

@naz_eg I would test too but i haven't vr400. Only VR2100 :X.

But it's weird. I thought the VR400 have Broadcom chipset.

For me i'm testing now VR2100 with any UK firmware from engineers. Now uptime 2 days and CRC are crazy, speed unstable and i am thinking its near to crash.

(short uptime = all fine, long uptime = big unstable problems)

I give TPLINK time to fix it to end of March. Then i think i will return it and maybe contact our "The Czech Trade Inspection Authority" in Czech Republic. I think that's fair.

Firmware Version:1.4.0 0.9.1 v009e.0 Build 210107 Rel.75133n (engineer marked as any old UK firmware)

My stats now (behaviour very similar as before): 

EDIT: It seems CRC error grow up recursive. O.O CRC numbers are growing up faster and faster.

I thought I would join in on this thread as my VR2100 purchased in November is suffering from multiple random reboots, which I believe it wasn't doing from initial set-up.  My old W9880 occasionally rebooted, but the main issue was the 2.5gz wireless power not being strong enough to cope with interference from other devices in neighboring homes

After following this thread I investigated the beta release firmware and this exaggerated the issue, meaning I have gone back to the last production release (1.4.0 0.9.1 v009e.0 Build 201122 Rel.72659n). 

I'm now in communication with technical support, but it is of concern that there doesn't seem to be any reason for these reboots and the vanishing log doesn't aid troubleshooting.  Is there a way to get the system to write the log to a USB stick and not have it reset on reboot?

Thanks

@JGMTB There is possible solution for logging. You can enable "remote logs" and send it to other device through rsyslog. But it is useless. There is no any exception in logs explaining the fall of the device. 

They would have to change logging. (maybe it is not possible)

From engineer i got firmware marked as 210107 (any UK old firmware). Uptime 2 days 22 hours 25 minutes. Still no restart. But i stopped using it because engineer sent me new beta firmware for trying fix CRC error. We will see. This testing take more time.

@JGMTB That is coincidental.  I too moved from an old W9980 due to the occasional reboot.  The new VR2100 was far far worse, and in the end, I just returned it back to Amazon.  I was fed up with wasting my time on it and the constant complaints from my family with lost connections, especially with the ongoing home schooling/working from home.  There was no point in flogging a dead horse so to speak.  With respect to gathering the logs, I have read that this is nothing to see except for a sudden increases in CRC errors.  I hope that TP-Link are able to solve this issue as ASUS were not able to resolve a similar issue when they switched to a MediaTek modem chipset with the DSL AC68U.

I have gone back to my old BT router, bought some wifi repeaters "Deco M4 ", no reboots or internet drops since changing router back. If using a NTE5c MK2 & VDSL/ADSL Faceplate MK4, try taking faceplate off and going direct to master socket with an inline filter. I think these faceplates with built in filter are also an issue. 

@PaulPP Interesting thing to try and probably worth a go but I doubt it would make any difference.  The filter is only applied to the line connected to your phones to filter out the high frequency noise caused by DSL.  Glad that you have found a working and stable alternative solution.  I now have 2 x AVM Fritzbox 7530's with one setup as a Mesh master and the other as a Mesh repeater.  DSL connection is rock solid and decent Wi-Fi throughout including the back garden.  In the end, the total cost of the 2 x Fritzbox 7530 routers (second hand) was the same cost as 1 x VR2100 and with none of the stress!!

TP-Link Turkey has just contacted with to tell they can take back the router and make a refund. I don't know if this their decision or headquarter's. I bought the router on 27.08.2020

I think these Mediatek chipset Routers have this issue so i will send the item back and buy a Broadcom chipset modem router.

Good luck everyone.