I’m having a weird sort-of crash at random points. All screens (I have 6) immediately go black and all the fans on my PC start to run at full speed. No input is recognised, I can’t get to the desktop, CTRL-ALT-DEL does nothing. However, the game audio still plays. The only way to get out of this is to soft-reset my PC and restart Windows. The first time this happened I was changing control bindings, but the second time I was just sitting in the aircraft on the ground working on another app while the sim was running. There are no event log entries that indicate any kind of OS or application issue. No appcrash event - because I don’t think this actually is an app crash.
This has happened twice now while playing MSFS 2024, and only while playing it.
I need to do further investigation of logs and some other diagnostics which I will do tomorrow (it’s 0130 in the UK now), but has anyone else seen anything similar? I’ve never had anything remotely like this on my PC before, and the Windows install I’m using basically only has MSFS 2024 installed on it.
YES.
This is happening to me!
I’ve tried absolutely EVERYTHING I can think of to try and fix it.
I’ve rolled back the driver.
Swapped out DP cables.
Uninstalled. Reinstalled.
Clicked ‘repair’
Windows update
Lowered graphics settings to low end
Nothing works and my PC crashes in the EXACT same way that you’re describing!
It’s intolerable, and I have spent 24 hours trying to fix it. Nothing works! Tried CTD recommended fixes, didn’t work either.
I’m desperate for a solution!
This is happening to me only in career mode. seems to lose monitor sync while loading cut scenes in career mode. I get the spinny circle lower right, then boom both monitors go black (no sync) and I can still hear audio. Having to hit the hard reset button is the only way to recover and windows really doesn’t like this…
any ideas I can try?
@XvDrumahvX See my answers on the other thread: Full PC crash after about 30 minutes in the sim.
The working theory right now is that it’s a network driver problem with Intel NICs (assuming you have one) and to attempt to solve it I updated to the latest drivers from Intel (via Asus) and updated my BIOS. Someone else did the same and had good results.
No crashes so far, but that doesn’t mean it’s fixed.
I saw that… i just updated my intel network driver. I will try bios as well… thanks
network driver didnt do it… got about 4 lessons in on career mode then, boom lost monitor sync. hard to hard reset the PC… very frustrating. I would take a CTD over this
Yes, frustrating isn’t it? I haven’t had the problem again but then I didn’t have it for days after my first attempted fix.
I’m about to build a new PC so either things might end up better… or worse.
NH
I saw this 3-4 times when I was trying out 2024 prior to returning it.
I even think the first time I left it alone and it rebooted my PC on its own.
Yes, what seems to happen is that if you leave it long enough the system finally BSODs, you just can’t see it because all the displays have stopped.
I’d be very curious to know whether or not it was the network driver for others who have this, but this would require someone to leave the machine to BSOD rather than reset it, then grab the minidump file and analyse it with WinDbg, which I appreciate is a more technical task than many are comfortable with.
For Windows to blue-screen, there must be a driver-level problem, so ultimately this isn’t a bug in MSFS 2024, it’s one that is triggered by MSFS 2024 somehow. Fixing the triggering might fix the appearance of the issue, but only fixing the driver will ultimately fix the bug.
1 Like
Had this start happening to me. I began experimenting with the dynamic settings set to 30 FPS and TLOD at 200 on the Fenix. I suggest trying to turn off dynamic settings and TLOD to see if there’s a different effect? I am having suspicions it has to do with VRAM going over. .
If the VRAM budget was exceeded, the game itself could certainly crash under DX12 (since it does not protect against that in the way that DX11 does), but it wouldn’t crash the OS, which can happily survive the display driver faulting and being re-loaded, since it no longer has any components running at Ring 0. You’d get a traditional crash to desktop. Also, I had this happen while just setting keyboard controls, where VRAM use would be minimal, and I have a 4090 with 24GB of VRAM. Seems unlikely as a culprit to me.
This crash takes down the whole OS, and begins by blanking the displays on which DX12 windows are being drawn - though not necessarily all of them, as I’ve seen an Air Manager instrument remain visible after the crash process begins - and then somehow causes the fans to run at maximum, which could be as simple as pinning enough cores at 100% to make the system respond. Running tasks continue to run - I managed to continue on a Zoom call for a good couple of minutes after a crash started, and I could still hear sim audio, indicating that the sim process itself was still running. Input is blocked, but this could be because the threads responsible for processing hardware I/O like keyboard and mouse are deadlocked.
Eventually, the system blue-screens - I wasn’t in the room to see if an actual BSOD was displayed - and reboots. As I mentioned earlier in the thread, the driver exception that caused the BSOD in this case was in tcpip.sys, which indicates a networking issue, although that isn’t necessarily the actual root cause.
It would be useful to gather system data from those who have these specific crashes. Are we all using the same Intel network adapter chipset, for example? Do we all have the same CPU / CPU family? The same motherboard chipset? Are we all on Windows 11? Which version? And so on.
While it’s clearly the sim that is triggering this somehow, it’s not the sim itself that is crashing. It’s Windows. The solution will either be isolating the Windows problem (most likely a driver) or Asobo identifying and replicating this crash and working out how MSFS triggers it, and fixing that.
Here are my specs for reference.
No real commonality there, then. My sim PC is Intel (13900K) and I’m running Win11 build 26100 - are you on a preview build? What about your NIC? Device Manager will tell you what it is.
RTX3080TI
Intel(R) Ethernet Connection (11) I219-V
I suspect it will turn out that Intel network adapter is the common factor here.
was hoping some of the recent updates would have addressed this issue, but nope. Just went back to my training in career mode and did 2 modules, then black screen… I really hate holding down the power button to get out of that, cant be good for windows.
Have you checked your event viewer in windows for any errors. I say this because I was having the same sort of issue and managed to solve it by increasing the windows startup ready boot file size from 20mb to 128mb and all is good now. You can find tutorials on how to do this from Microsoft support forums or google search. I struggled with this for weeks running msfs 2020, I know your running 24 but worth a try and it will not impact your system whatsoever. I refuse to buy 2024 until all the bugs and glitches have been settled.
My pc specs are:
HP Omen i9 13900k
Nvidia Gforce 4090
64GB Fury Beast DDR5 ram
WD BLACK 2TB SSD X2
Yes, I evaluated the event logs. I’m a developer so I’m very familiar with that process. Nothing indicative of a problem, up until the PC blue-screens and then you get the ‘the previous system shutdown was unexpected’ as usual.
As I mentioned on the other thread (I do wish the mods had merged them), I looked at the minidump file produced when my PC blue-screened (when I left it to see what would happen) and the faulting driver was tcipip.sys. I updated my Intel network drivers and didn’t see the problem again.
Now I’ve switched to an AMD rig with a Realtek NIC. No crashes so far.
I assume you don’t really mean all bugs, because that’s literally never going to happen, just like it’s never happened in the history of any complex software ever. But if you want to wait for 2024 to be on the same level of stability as 2020, say, I would think that’s probably years and many SUs away at this point.
