We have now had a second CCR1036-8G-2S+ router ‘die’ after running RouterOS 6.36. The first landed in a boot loop where the router loads the kernel, then briefly displays ‘starting kernel’ before rebooting. The second was behaving erratically where the ether ports would briefly flap but would otherwise be operational. After factory resetting the second router and leaving it in our workshop over the weekend it is now also in a boot loop this Monday morning.
The first incident happened shortly after upgrading RouterOS 6.36 (running 3.33 firmware) whilst the second router started behaving erratically last week Wednesday with the boot loop starting sometime this last weekend, with factory defaults (no ‘default’ configuration). AKA:
system reset-configuration skip-backup=yes no-defaults=yes
Another really annoying problem with RouterOS 6.36 is that Winbox keeps disconnecting randomly. We have observed the same problem with completely separate routers and PC combinations after upgrading to RouterOS 6.36.