I am not sure if i have this exact problem or a linked one. MSFS via Steam running DX12 and previously with approx 850 hours without issue. In the last 2 weeks though the game will not run and will crash with a black screen reboot usually when clicking “Fly” but, sometimes during loading as well. I’ve tried all the steps mentioned here but the behavior persists even when rolling back to previously working NVIDIA drivers. It now happens 100% of the time in both Normal and Safe modes. I am not sure if this was caused by the Windows 25H2 patch, upgrading to NVIDIA 581.57 (since used DDU and rolled back but, has made no difference) or something else but, the end result is the same the game will no longer load.
My event viewer looks different from the images posted in this thread though as i just get a generic 1001 error with no application specified hence not sure if this is the same problem or a closely linked different problem. [new cant upload files so cant attach the MSFS crash report].
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 116
P2: ffffcc0ceefd1010
P3: fffff8034b0a7a90
P4: ffffffffc000009a
P5: 4
P6: 10_0_26100
P7: 0_0
P8: 768_1
P9:
P10:
This is not the same thing. It’s what we call a TDR 116. It’s the nvidia driver that crashed.
You should try an older driver. (one that you knew worked)
If you haven’t seen this, it is the first of the troubleshooting help topics found in the Sim Support tab at the top of the forum page:
https://flightsimulator.zendesk.com/hc/en-us/articles/4412295717650-Read-first-Windows-10-11-troubleshooting
If you need to dig deeper than this, there are more articles of this type in there.
Trouble is I have rolled back and tried several previous NVIDIA drivers that did work previously without issue (cf 850 hours without problems previously) and still have the same problem. So it is something other than the NVIDIA driver causing the issue though it is likely from the event log that whatever it is, is conflicting with the NVIDIA driver itself. I’ve gone all the way back to drivers from 2024 and tried multiple different 2025 versions that have been reported as stable on this forum with no luck.
thank you for that unfortunately, none of those steps has resolved the issue and have been combing the forums trying to find other ideas to try.
Not really sure at this stage after working on it for 2 weeks without progress. The game will mostly load to the Menus and I can sit there at the main menu screen for quite some time but eventually it will blackscreen reboot. I can also load into Fly and get into an aircraft but will get the same behaviour usually faster than just leaving it idling on the menus.
On the basis it was an NVIDIA driver issue (GTX3080) I’ve tried using DDU and going back through;
- 581.57
- 581.15 (previously working)
- 580.88 (previously working)
- 577.00 (previously working)
- 576.28 (cant remember if I had used this version before)
- 566.36 (previously working)
All gives the same behavior.
I’ve done SFC /scannow (no errors) and DISM repair checks (no errors).
I am assuming at this stage that something in the 25H2 Windows Update has broken something along the way but, since there is no more detail in the crash logs it is proving very hard to resolve.
Check what other issues cause BSOD’s. There are a few other ideas to look at online particularly if your rig is older, like overheating etc.
I’ve checked the obvious ones and prior to this recent issue had 800+ hours without any issues including lots of long haul 10-15 hour flights in the sim and nothing springs to mind. The GPU/CPU temps are all in the normal operating range so nothing seems out of the ordinary there.
I am not seeing this behavior in other games not launched via Steam which initially led me to think that it was a Steam related issue but, I’ve also fully repaired the Steam library, verified the downloads , deleted the cache etc in Steam and that hasn’t helped either so don’t think Steam itself is the culprit.
Can you check in MSFS settings whether you’re using DX11 or DX12?
P1: 116 is quite revealing.
It’s a Bug Check 0x116: VIDEO_TDR_FAILURE
The GPU driver crashed. Official MS information :
Now how to fix.
Since it was working before on earlier driver, I think we can rule out a driver bug.
So either a windows update is broking something for you are something on the hardware side got weaker.
Things I would do.
1- Check if bios is latest for your motherboard.
2- No overclocking except memory XMP stuff.
3- Reseat the GPU (remove and reinsert into the slot)
4- Give NVIDIA Control Panel’s “Debug Mode” a shot. It prevent OC the card
5- Limit the FPS drastically with either NVCP or RTSS, to something like 30 fps to see if the system is not taxed, does the issue occur.
6- If issue does not occured when limitting the card, then either the GPU is more fragile or the PSU has a problem.
Extra: Check when the system is taxed / under load (when loading your game for example) with a tool like the HWINFO, check the min on the voltages. the 3.3v 12v, etc.. and be sure that they are under the ATX spec. Ex: if 12v go to < 11.4v it’s out of spec so the PSU is probably bad.
I am using DX12. I did try DX11 but have the same behavior there so went back to DX12.
Thank you for the suggestions will give them a go.
1- yes latest BIOS confirmed
2- no O/C
3- done
4- had previously tried this and didn’t resolve issue so assume whatever Debug mode does wasnt the answer either.
5 & 6 - will try those today thank you.
Ran OCCT CPU/GPU/PSU stress tests , no issues on the hw side it would seem. Each test ran for the full hour without problem and nothing seems amiss in particular on the PSU front.
Not sure what else to test in my view is that something happened with either the 25H2 patch or the 25H2 cumulative update (KB5070773) or 24H2 cumulative update (KB5066835) , or the cumulative update for .NET (KB5066131) and my system not agreeing with each other.
I’ve Windows Repair Installed the 25H2 version so far and has not resolved the issue.
I see Microsoft has already released a .NET update (KB5067931) since then but, this also did not resolve the issue.
I believe I have found the root cause of this. After running all the OCCT tests I was out of ideas so started pulling stuff out of the PC including all the peripherals trying to work out what was causing the issue. When I unplugged all my flight controls and throttles and just had a keyboard stuff started working.
The culprit in my case seems to be my old Logitech 3D Extreme Pro. There are other threads on this forum that this device can cause issues with the Windows Defender Core Isolation security function. Even though I didn’t get any error message from Windows Defender or Windows Update when applying the 25H2 patch I suspect that something about the joystick driver offended something else.
I was not running the Logitech legacy driver and just was using the Windows USB joystick default as far as I can tell as there are no Logitech joystick files on my PC but, I did find a bunch of updated Logitech force feedback files dated 25th Oct so perhaps there was something from Logitech in the 25H2 update (or perhaps I broke that trying to repair the 25H2 patch).
In any event unplugging everything , rebooting and resetting all the USB peripherals seems to have resolved this issue and I’ve been in MSFS now for a few hours without issue.
Logitech have said the Ex3DPro is not Windows 11 compatible but, it’s always been fine before but, perhaps its days are numbered now as it appears to have almost certainly been the culprit here.
There was no indication from Windows Defender that there was a problem and nothing flagged in the Core Isolation driver error area so can’t really 100% validate it but, that’s what I believe happened here if it helps anyone else with a similar issue.
Really happy for you getting this resolved - happy flying 
Thanks for sharing what caused your BSOD - it’s always good to know what can trigger those.
Your USB issue actually reminded me of a problem I had with Windows 11 24H2 myself. My VKB joystick would disconnect right after logging into Windows - I could hear the “device disconnected” sound every single time. I honestly thought I was in for a long fight with drivers, OS or maybe even a full reinstall, but after a cup of coffee I came up with another idea: I just swapped the USB plugs between the joystick and the throttle (Logitech X56).
Both the VKB joystick and the Logitech X56 throttle are connected to a USB 2.0 bracket that goes directly to the motherboard, while the rest of my peripherals used with MSFS are plugged into a USB hub. After updating to Windows 11 25H2, the issue came back but this time it was the throttle that kept disconnecting. Swapping the plugs again instantly fixed it.
So if unplugging and reconnecting your devices helped, there’s a good chance you actually plugged your joystick into a different USB port and that might’ve been exactly what fixed it, just like in my case.
If you’ve had any issues and found any fixes related to Windows 11 24H2 or 25H2, feel free to share them in the thread linked below:
https://forums.flightsimulator.com/t/windows-11-25h2-24h2-and-msfs-observations-insights-issues-and-tips/657704
Hmm sadly this doesn’t appear to be the end of the problem. After the USB stuff, the game worked fine for a couple of days including some 3-4 hour flights and appeared to be working fine. Now today it is back to crashing again.
The USB stuff was definitely an issue as fixing that made a lot of problems go away and i actually get an MSFS error in the event log rather than just a generic P1 116.
Faulting application name: FlightSimulator.exe, version: 1.39.9.0, time stamp: 0x00000000
Faulting module name: CoherentGTJS.dll, version: 0.0.0.0, time stamp: 0x680f8058
Exception code: 0xc0000005
Fault offset: 0x00000000002e9b11
Faulting process id: 0x4C34
Faulting application start time: 0x1DC4BC5E2B413A8
Faulting application path: D:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: D:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\CoherentGTJS.dll
Report Id: 4811180f-451e-4de2-a1af-a2f28521160b
Faulting package full name:
Faulting package-relative application ID:
I’d already rolled nvidia drivers back to 566.36 which seemed to be the most common suggestion for issues with CoherentGTJS.dll but, still not loading.
Could you clarify what you mean by “still not loading”? Do you mean MSFS doesn’t start at all, gets stuck while loading, or CTD during loading? A bit more detail would really help figure out what’s going on.
It will start to the menu / main screen but crash when you select Fly most of the time before the plane loads , the rest of the time the plane will load and it will crash shortly thereafter in both normal and safe mode. I’ve tried several airplanes both standard content, premium deluxe content and 3rd party aircraft and happens with all of them , similarly picking random airports around the globe.
Could you please attach a dxdiag text report file in your reply?
How to create a DxDiag report