Well, not to pry, but I do see you are an editor here at Tom's Hardware. Perhaps you could pass this story on to the staff, and get a broader discussion going, so we can get clearer answers and a definite fix from either Intel, Microsoft, or the game developers whose games are affected?If you were testing motherboards, sure. I'm testing GPUs, and I want maximum performance possible from the CPU, so I want the performance optimizations to be applied. The problem is that the MSI MEG Z790 Ace likely pushes things too far, or else the Cooler Master 360mm cooler just isn't quite able to handle the heat, so to speak.
Really, one of two things should happen:
1) All the motherboard manufacturers should do additional testing to verify their tweaks don't cause the CPU to overheat. And honestly, I'm really not doing much: I enable XMP in the BIOS after loading the defaults. If that crashes consistently, it's a mobo firmware issue as far as I'm concerned.
2) If Oodle has code that consistently crashes on Raptor Lake CPUs, whether it's overheating or something else, Oodle should debug this and figure out what needs to be done to prevent the crashing. It doesn't matter if "the code works on everything else!" I was a programmer, and if your code has problems on a popular subset of systems, you should try to fix it. Hell, it might be an Oodle bug in the first place that only shows up with Raptor Lake.
Frankly, both of these should happen as far as I'm concerned. Because if Oodle is causing the crash, that means other applications should trigger it as well — it's only a matter of hitting the right 'buttons' on the CPU, so to speak. And in the interim, Oodle shouldn't be okay with code that consistently causes crashes.
As of yet, despite this issue increasingly affecting more and more games, and more and more consumers are buying 13900ks and 14900ks, no tech outlet has written about it, and I've tried to get GamersNexus to cover it many times to no avail.