The video below was posted on YouTube two days ago about Intel CPU’s having issues. Could this be some of the reasons MSFS blows up so much? We all know how MSFS requires all the resources that our computers have.
I’m just posting this in hopes of helping others understand how complex our systems have become and it may not have anything to do with Asobo or Microsoft. It’s just something for all of us to think about. That’s all!
I absolutely believe that most CTD’s are caused by hardware, drivers, or the OS.
Cheap power supplies, non-qualified RAM, cheap motherboards with substandard VRM’s, chip binning, and a host of other things need to be looked at before blaming the core sim software.
The issue with certain BIOS overvolting the new Intel CPUs is a pretty ugly thing. If, as suggested in that video, it turns out that there’s something more fundamentally flawed in those CPU’s, then things are even uglier.
Non-qualified RAM is insidious. I’ve seen lots of sticks of ECC RAM start throwing errors in a production environment. RAM can have cells get flaky or just be iffy from the factory. ECC traps and reports most errors but regular PC RAM doesn’t have a parity bit. Errors in non-ECC are generally silent but can still trip up or crash an app or the system.
The only way to have confidence in regular RAM is to test it with an app that writes to RAM and reads back and compares with what it wrote. Memtest86 is great for this. I run it whenever I build a system to make sure the RAM starts out clean and trustworthy and any time there might be a question.
I wish folks having odd system behavior would take a moment and validate their RAM. There are lots of things that can go wrong in a computer but RAM issues are some of the more common. It can at least eliminate RAM as the trouble source if it’s something else.
I haven’t experienced any issues with I9 13900K. This might be because I’ve been pairing Intel CPU with MSI motherboards for as long as I can remember. Over the years I’ve become very familiar with the correct BIOS settings - almost knowing them by heart.
My i9 13900K has just been replaced under warranty. So far so good! 
I’m also using an MSI motherboard with my 5800X3D, eVGA 3090 Ti, and HP V10 DDR. One of their cheapest motherboards actually. The B550A-Pro doesn’t have a lot bells and whistles, but the memory controller and the VRM section are very good. I don’t tweak anything in the BIOS, and my system has been rock solid.
Same here. Never had an issue with the14900k. I have built Intel systems for several builds now and have always been very careful to pair motherboard, CPU and RAM as well as setting up BIOS properly. Never had a hardware issue to date and this is across at least four builds.
I believe the issue is not crashes or not, but rather whether the MB built-in overclocks DEGRADE the cpu in normal use. That’s why Intel is saying that all bets are off if the MB seriously overclocks out of the box. Stock MB voltages May be way too high for the cpu.
That’s been pretty well known for a while now. Certain motherboard manufacturers (ASUS being the main culprit) delivered BIOS that OC’d Intel 14th Gen CPUs beyond their design spec. They walked it backward with a BIOS update, but that didn’t help people whose CPU’s burst into flames…
I take it you didn’t watch the video, because it talks about how that is NOT the entire story!
Short version: even CPUs used in servers with workstation-class chipsets (W680) are having major issues, and those motherboards follow conservative power limits.
Also, sidenote: Intel previously explictly said that any power limit was in-spec, including 4095 W, so don’t accept their nonsense about the issue being “out-of-spec” usage. That’s them trying to skirt responsibility to save money (and face).
I had problems with an i9-13900K and i9-14900KF especially in X-Plane. Got an RMA for both and set the short duration and long duration power package limit to 253 and have had zero problems since.
If you’re directing that comment at me, I did watch the video.
The error rates for the the real 13th and 14th gen CPU’s (not the rebadged 12th gen 12900K) were far higher than any other CPU’s. He was careful to explain that the dataset he had was not statistically perfect. Still , it was clear that he concluded that it was the 13900K and 14900K that were the most problematic chips - regardless of the motherboard and processing task environment.
Right, and therefore “[c]ertain motherboard manufacturers (ASUS being the main culprit) delivered BIOS that OC’d Intel 14th Gen CPUs beyond their design spec” is misleading, since the stability issues are triggered even on boards that don’t OC or raise power limits beyond the “baseline” spec.
You’re of course correct that many manufacturers did this, but saying it like that to me implies that the crash issues are because of the raised power limits – and it seems CPUs that have spent their entire life in standard conditions in W680 boards are also unstable, so the issue seems to go much deeper than power/current limits.
Fair enough.
Perhaps it was a passive aggressive dig at ASUS. I had a horrific experience with support for a client’s (obviously) DOA motherboard. I actually ended up yelling at the 7th tech I spoke with in front of my client. I swore I’d never buy another ASUS product. I’m not the only one.
I ditched ASUS many years ago and have been running MSI since and never looked back.
The support over at ASUS is really subpar where MSI has been great the few times I’ve had to contact them.
What is this an MSI love in?
Way back when they were the first to use military grade caps and mosfets. I switched immediately as practically all I’d ever faced was burnt out components
I’ve been buying MSI motherboards for as long as I can remember. Currently I have an MSI MAG Z790 Tomahawk WIFI and I’ve just purchased MSI MAG X670E TOMAHAWK WIFI for an AMD CPU. I appreciate MSI for their customer-focused approach and their intuitive BIOS settings which they update quite frequently.
And here was me thinking an odd number of tens was just for AMD and evens for Intel.
I guess now I’ll have to be careful