Instant Blue Screen (BSOD) when trying to run MSFS - See Error Msg below

I have been unable to get MSFS 2020 started because of this error. I have called both Microsoft and Xbox support phone lines and only been able to talk to incompetent staff in India, who just hangs up when they can’t find the answer in the script!

I Have done 2 clean 120Gb installs and have no idea how to solve this!

Any help would be welcome.

2 Likes

Hi @Kaptajnen1583,
A blue screen (BSOD) is generally cause by hardware or drivers. Is your video drivers current?

The BSOD error is: “system_thread_exception_not_handled”

https://www.troubleshootingcentral.com/how-to-fix-system-thread-exception-not-handled-error-on-windows-10

2 Likes

@Kaptajnen1583 Same here… I played on Thursday night (Today is Saturday) and there were absolutely no issues. I haven’t even been on my computer since then and I went to launch the game today & I’m getting the same error, and its ONLY when I launch MSFS2020. I’m glad you posted saying that clean installs did not fix the problem because that is what I was going to do as well. Do you happen to have FlyByWire A32nx installed? @Hester40MT No, I don’t think this is the case because it was just working two days ago. All other games I’ve got installed are working as expected

2 Likes

two days is a long time and many things can happen… additional the OP mentioned that “since last update” , thus it happend somewhat :wink:

BSOD is in 99.9% system issue… If we assume your hardware is fine, then check your anti-virus solution. Which one you use ? Try to stop it completly.

Otherwise do the action we mentioned so often in other topics: limit your fps.

Yeah but the issue is I’m getting several varying error codes on the BSOD. Its either thread exception not handled or system service exception. I work in IT and I know that BSOD is usually a hardware or corrupt/malfunctioning drivers. All me and the OP are saying is that it was once working (for me only 48 hours ago) no hardware changes have been made nor have any config files for MSFS2020 been changed and I can easily go about other tasks or programs for hours and won’t see the BSOD until I open MSFS. It’s the only program I open that has ever caused a BSOD. I also recently performed a clean windows install as well to start my system off fresh. It’s something that has changed with Microsoft in the last 36 hours or so, albeit windows updates, Microsoft store updates and or updates to the sim. Hardware and drivers have been tested/updated. Me and the OP are not the only ones having this issue in the recent hours either. Antivirus was disabled as a first test area, still no resolve.

3 Likes

now, is just not a conflict that you get the BSOD only in MSFS. It drives your pc much harder, use avx instructions, etc…

And of course there are windows updates, therfore I mentioned that two days are a long time. May be you get in these time the latest windows update and may be have an effect…
( I assume sfc /scannow is already executed ? )

If I see the post history of the OP then I assume he got the game update already some days ago and the issues started, like yours, because of a different trigger.

I wonder a bit , if you have IT background, why you not give us specific informations about your system ( from hardware specs till driver versions ). Then community users can compare.

Beside of the AntiVir, where we had some cases where it caused a bsod too ( latest I remember was Sophos installed ), have you checked to limit the fps for a test-case e.g. 30 ?

Solving a BSOD of the is nature is going to involve pinpointing exactly which driver in the system is failing to handle an exception: because the stop code is SYSTEM THREAD EXCEPTION NOT HANDLED.

This isn’t a typical BSOD that can occur because of system issues like temperatures.

Some kernel mode driver in the system is not playing nice with the windows OS.

I would look really closely at which drivers are installed and in use. Remove devices that aren’t essential (like your phone might be plugged in to charge it, but it appears as a USB storage device to the OS, and if the USB driver is bugged , that is one way a BSOD might come about.

Unplugging un-necessary devices and rebooting should make drivers related to unnecessary hardware not load, and therefore narrow the possibilities.

Assuming the issue persists after doing that… look closely at drivers installed in support of your specific motherboard. If the motherboard is aged, I tend to allow windows update to replace drivers as it likes, but if the system develops specific issues like this thread, I will re-install whatever drivers were for that motherboard.

That would include usb driver, shipset, possibly storage, audio, etc.

Then there is the GPU driver – I would use DDU in safe mode to remove and then reinstall the latest. I’ve seen that fix many weird problems over the years.

Also, if there is RGB lighting, and corsair’s software is installed to control RGB lighting – that tends to be an area where instability is introduced.

If you still come up dry, I’d look at the files in c:\windows|system32\drivers and the file dates on the .sys files. The ones that are very old is where I would focus. Figure out what hardware they are – or were associated with, see if there are newer versions.

But, that said, don’t just download new .sys driver files from sites that offer that – because that is very unsafe. Look for packaged drivers from the device manufacturer.

1 Like

I’m having exactly the same issue as the OP.

As it’s a new system I’m on I’ve even tried a fresh OS Win 10 install followed by a new MSFS install. Installed up to date GPU drivers etc. Problem persists.

I will try some of the advice given above, and if I do happen to find a solution I’ll report back. Hopefully we can get this sorted. As the OP said MSFS is the only program on my system too that’s giving this issue.

1 Like

I get that device error sometimes when I plug in a usb device into my usb hub. Try unplugging all usb devices and start computer, then msfs to see if that helps. If so replug one at a time to see if you still get error. If that does not fix try running this in command prompt ( DISM /Online /Cleanup-Image /RestoreHealth ).

can you check whether you see same ?

https://forums.flightsimulator.com/t/instant-blue-screen-when-trying-to-run-msfs/504491/23?u=michamma

Ps: we have unfortunately two topics for this

1 Like

Are you using Developer Mode or made changes in it?

No

Brief description of the issue:

When first installing MSFS onto my new system it downloaded the initial files ok to the C drive (O/S drive). When I clicked on the run icon within the xbox app to launch MSFS I get an instant blue screen and the system reboots, with either “System Service Exception” or “System Thread Exception Not Handled” on the blue screen. This happens 3 times out of 4 when trying to run MSFS and always happens within seconds of clicking the run icon. If I get as far as the launch graphics just before the update icon appears it runs ok. When MSFS does manage to load it works flawlessly in VR. It took 5 attempts to get it to load so I could proceed to the updates and download the packages. More often than not I get the BSOD on clicking run from either the Xbox app or the start menu list. Other programs run no problem on the system - DCS, Sea Of Thieves (only program causing this issue so far is MSFS). I have checked the memory using the Win memory check tool, no issues were found. Also ran SFC/scannow etc again no issues found.

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

PC specs and/or peripheral set up if relevant:

i7-12700K, ASUS ROG Strix Z690-A Gaming motherboard, 64GB Corsair Vengeance RGB PRO DDR4 4800Mhz, ASUS ROG Strix Geforce RTX 3090, 500GB Samsung 980 PRO M.2, 2TB Samsung 980 PRO M.2, Corsair 1000W RMx Series Modular 80 plus Gold PSU. System running latest Win 10 version 21H2 (OS Build 19044.1586) GPU Driver 511.79

These are almost always caused by driver issues.

Since the error is most likely being caused by a malfunctioning driver, you can use the Windows Log to find out which one.

To do this simply follow these steps:

  1. Press Windows Key + R and in the Run dialog box, type eventvwr.
  2. Navigate to the Windows Logs menu and expand it, then select System.
  3. Look for a log named system_thread_exception_not_handled and click on it to find out which driver is causing the issue.

Thanks for the reply.

I just checked the event viewer for the last blue screen.

It say’s "Event 1001, Bug check. and lists this :- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80508498f34, 0xfffffa0f5c8965e0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 5e973f11-fa7b-46fd-85e0-e6f55447d0a2.

I couldn’t find anything on the list under system_thread_exception_not_handled

I did a system reboot and as soon as I got to the desktop I went to the MSFS icon under the start menu and the sim loaded no problem. Came out of it and tried again and it blue screened. Strange how it works sometimes but most of the time it blue screens.

2 Likes

this is whats happens with driver or hardware issues :wink:

At first ensure the issue comes not from anti-virus and do some test-runs with disabled anti-vir.

Then may try to limit the fps to 30…

Otherwise you can only narrow down the cause by disconnect all devices , cameras, whats ever … check that drivers up2date… stop fancy Asus RGB tools, etc.

Also if I see “Corsair Vengeance RGB PRO DDR4 4800Mhz” … it’s not rare that these moon-frequencies cause issues :slight_smile:

There is also a little change that the latest windows update “made things better”. But then I expect much more users have trouble, and at least I just got back from a 6.5h flight…

EDIT: with a dump-analyse tool you can have a look into these memory.dmp file

1 Like

Moved to #self-service:pc-hardware which is more appropriate :+1:

Hey. I am having the exact same issue as you, I have checked everything, drivers, hardware.
Yesterday I opened MSFS in the morning and it worked perfectly, then I wasnt home all day and then in the evening when I try to open MSFS… bam BSODS when I try to open it. Either from desktop, of the xbox app. I dont know what to try anymore…
things to note:
Im running it under gamepass, and I only installed it 5 days ago
Drivers are all up to date
I have never touched the BIOS since getting my laptop, aside from updating it
no overclocks
Windows log finds no issues
same results when disabling antivirus (norton)
Windows 10 21H2
System is more than capable to run MSFS (RTX 3060 MAX-P Ryzen 7 5800H)
its just really strange, I close msfs in the morning, nobody touched the pc since then, and then when I try to open msfs when I come back I get BSODS.

its almost like it doesnt want me to open msfs no matter what

1 Like

beside of the former given hints, can you pleas check “when was the latest windows update installed ?”

it was installed yesterday. Something tells me that a windows auto update went wrong. However when I try to revert the update it keeps downloading it again

hmmm… I have these one and no issue ( Steam version ).

But if this is the only change at the users system… hmmmmmmm :thinking:

May be enabled Dump Creation, install these Dump-Analyse tool and we see the exact dll which cause it…

Thanks for your post. First one too! welcome aboard buddy :slight_smile:

I initially thought it was my new PC that had an issue but more and more folk are coming forward saying they are having similar issues too (see the linked post above for some others with the issue).

Thursday last week sounds about right from my end too. Another strange thing is on my other PC, which is incidentally still able to run MSFS ok, it started having a strange issue when booting it up for the first time in the day. After pressing the on button fans etc start, then it shuts down, restarts, shuts down again and on the 3rd attempt it boots. This has just started since an update last week, and I’ve had this PC for 4 years issue free!. Something looks to have gone amiss with an update somewhere.

Hopefully others come forward and report a similar issue with MSFS and either Asobo or MS look into it soon.