I had similar issues, got an email from support saying there were problems with Simple Queues and this kernel.
I am running 5.7 right now. I found this thread looking for any info about 5.17 or better on x86.
Hopefully they won't mind me posting this.
At the moment there are few known issues that can and will be fixed only in
upcoming RouterOS v6.x, which will be ready for public release sometime this
summer. Perhaps the best choice for you would be to keep using RouterOS v4.17
until stable version 6 is released.
Currently (v5.11 and above) all x86 crashes/reboots/halts are related to 2 things:
1) resource management in complex setups on multi-core systems - as temporary
solution you can:
*) reduce number of CPU cores (by disabling Hyperthreading on Intel CPU boards)
*) reduce possible amount of core switching -
a) disable all entires in "/system resource irq rps" menu
b) while monitoring "/system resource cpu" menu, manually allocate "/system
resource irq" to specific cores
c) change your configuration to avoid using "global-in" and "global-out" HTBs
(no simple queues)
d) change your configuration to avoid deep packet inspection ("layer-7",
"content" all 3 "use-ip-firewall" options.
e) in "/queue interface" menu set all queues to "multi-queue-ethernet-default"
*) switch to single-core Linux Kernel - "/system hardware set multi-cpu=no"
2) interface driver problems - we are not maintaining other vendor drivers, so
fixes to driver related problems can be done only with driver update, some driver
updates require Linux Kernel update - and in RouterOS that is possible only with
next major RouterOS release (v6.x) as temporary solution you should change your
interfaces to other type/vendor cards.
I do wonder if the same problem exists on AMD systems. I have a backup for our Core i7 router running a Phenom II that hasn't had any issues, however it is just sitting there, no traffic passing through.