Asked for information and raised a point, period. Did you actually read the thread and what was posted? His device was WORKING, he was having system issues, and before you even posted followed up by saying additional information was uncovered pointing to the CPU. Past that, the device is very obviously finding the firmware, since again, IT IS WORKING. And we do not 'know' that it's a hardware driver issue, since there is precious little in the system logs that point to that.

The OP had zero problems with what I posted and asked, what's the point of this?

I have to add that the MCE errors did not turn up until recently. I've meticulously gone through journalctl many times to try and find the cause of my problems so they weren't there when I first posted. Hopefully though it was the cause of my crashes so my new CPU will fix it.

As for the driver I got that suggested in a different part of these forums, and I didn't find any of the replies here rude.

Thanks...I didn't think so either, but who knows sometimes? I do find it a bit odd, though, that the network hardware in question isn't better supported by Manjaro. Might be worth a try to pick up a cheap USB wifi adapter with a different chipset and try it first, before a new mobo. Can always return it.

I wonder what *cron is doing on that system at all.
On my (fairly fresh) ArchLinux install, there's nothing like that:
No output for either command.

I honestly don't believe that Manjaro would take this sort of backwards step to reintroduce cron into their Arch base.

Agreed; I suggested looking at cron/anacron a while back, but OP didn't find anything. I did think it was odd.