Constant CTD all of a Sudden

[GSalden 4,726]

22 hours ago, PilotPete99 said:

Update: Just completed the same flight after reverting back to Driver 531.68, and the flight was flawless. Not ever a stutter. This was departing Pyreegue EGAC and arriving at MK EIDW V2, also with Dublin city scenery from Orbx. Clearly, it was the latest driver.

Cheers, Pete

Yesterday I had this on my left view pc and the day before on my front view server.

So I upgraded to 531.79 and after that I completed a flight without any issues…

 

 

[Funky D 284]

There have been a bunch of threads about this and a MSFS KB article:

https://flightsimulator.zendesk.com/hc/en-us/articles/6422969348508--Your-graphics-device-has-encountered-a-problem-and-Microsoft-Flight-Simulator-will-exit-error-message

That said, I was able to run the latest drivers and DX12 after uninstalling GeForce Experience (someone in another thread mentioned this worked for them). Other people have recently noted things work if you launch MSFS from within the GeForce Experience app. Either way, everything points to this being an Nvidia issue...

[virtualstuff 776]

On 5/5/2023 at 8:39 PM, PilotPete99 said:

Hello - Not sure what's going on. but over the last few days, I can't complete a flight without a CTD at some point before arrive. I rarely over got these up until now. Just now, in PMDG 737, enroute from EGAC to EIDW, about 20 miles from EIDW. I am not sure what is going on, but hardware shouldn't be an issue. Any ideas? Here are my specs: Intel Core i7-11700F @ 2.50Ghz, Nvidia GeForce RTX 3060 @12GB, 32GB RAM DDR4, and no overclocking. I'm using the latest GeForce Game Ready Driver 531.79. Thanks in advance.

Cheers, Pete

driver issue revert back to last working driver or install without geforce experience...

[JDWalley 354]

13 hours ago, jcomm said:

Some drivers are dangerous... That's why there are so many accidents ... 😁

Especially the drunk drivers put out by nVidia.

[jcomm 6,096]

13 minutes ago, JDWalley said:

Especially the drunk drivers put out by nVidia.

🤣

[GSalden 4,726]

Just now with the latest drivers that helped me with my flight yesterday on my server :

Your graphics card ……. Etc etc 

So on my setup with both latest drivers I experience this .

- - - 

So back to the 5.31.29 drivers as MS advices since October 2022 and even today still advices. It might not solve it completely but is a very stable driver.

Hopefully Asobo can fix this or NVidia does …

Edited May 7, 2023 by GSalden

[cobalt 831]

This issue has been around for many people since SU12, and two things are clear, based on all the reports I've read plus my own experience: The problem is not drivers, and it is not an add-on. The culprit has to be SU12, as nothing else fits the facts.

[ErichB 3,674]

May as well use this thread instead of creating a new one.

The title fits my situation.  All of a sudden.  

CTD from last Thursday. Usually about 10 mins into the scenario and especially on climb-out at about 1500', usually at flap retraction stage.    It's actually not so much a CTD as it is freezing the entire PC and having to press the PC reboot button.  Usually sound freezes too and there is a loud buzzing noise.

This has happened before and after a Nvidia driver update (updated yesterday).  

Also happening with empty community folder.  No significant overheating

 

 

 

Edited August 15, 2023 by ErichB

[Brocky120 65]

47 minutes ago, ErichB said:

May as well use this thread instead of creating a new one.

The title fits my situation.  All of a sudden.  

CTD from last Thursday. Usually about 10 mins into the scenario and especially on climb-out at about 1500', usually at flap retraction stage.    It's actually not so much a CTD as it is freezing the entire PC and having to press the PC reboot button.  Usually sound freezes too and there is a loud buzzing noise.

This has happened before and after a Nvidia driver update (updated yesterday).  

Also happening with empty community folder.  No significant overheating

 

 

 

 

On Windows Search, Type in Event Viewer > Windows Logs > Applications Logs.

Look for a Red exclamation mark around the time of the crash and look at the faulting module name and the exception code, copy or post it here and will help to see the cause.

Edited August 15, 2023 by Brocky120

[ErichB 3,674]

1 hour ago, Brocky120 said:

 

On Windows Search, Type in Event Viewer > Windows Logs > Applications Logs.

Look for a Red exclamation mark around the time of the crash and look at the faulting module name and the exception code, copy or post it here and will help to see the cause.

Thanks, will do that tonight

 

[fppilot 4,459]

On 5/6/2023 at 1:45 PM, sidfadc said:

If you use Add on Linker, there is an inbuilt tool which scans all scenery for conflicting model lib files and renames things automatically - very handy!

Would you please point out the menu option in Addons Linker you are referencing, and what you choose/select to perform this check?

 

[sidfadc 1,345]

18 minutes ago, fppilot said:

Would you please point out the menu option in Addons Linker you are referencing, and what you choose/select to perform this check?

 

Click Tools from the drop down menu and you are looking for Modellib Changer and MaterialLibs Changer.  Just follow the on screen instructions, it will take you through a wizard and scan all your addons and fix where appropriate.

Hope this helps!

Edited August 15, 2023 by sidfadc

[Bob Scott 7,782]

4 hours ago, ErichB said:

May as well use this thread instead of creating a new one.

The title fits my situation.  All of a sudden.  

CTD from last Thursday. Usually about 10 mins into the scenario and especially on climb-out at about 1500', usually at flap retraction stage.    It's actually not so much a CTD as it is freezing the entire PC and having to press the PC reboot button.  Usually sound freezes too and there is a loud buzzing noise.

This has happened before and after a Nvidia driver update (updated yesterday).  

Also happening with empty community folder.  No significant overheating

My last prolonged visit to MSFS CTD Hell was the result of bugged new nVidia drivers...reversion to 531.29 fixed it definitively.  M$/Asobo acknowledged that mutiple users were reporting problems and recommended the reversion.  I have not updated drivers since, and have not had any recurrences, either.

[TacomaSailor 192]

I fly about 2-hours per day - most days.  Following is the list of CTDs I have experienced in the last seven days and the faulting module as shown by event viewer (FS is Flightsimulator.exe):

FS nvwqf2um.dll
FS flightsim.exe (5 occurrences)
FS ucrtbase.dll
GTN_simulator.exe KRNL.dll (4 occurrences)
GTN_simulator.exe d3d11.dll (2 occurrences)
AVASTAntiTrack.exe ucrtbase.dll (2 occurrences)
AVASTAntiTrack.exe libcef.dll 
AVASTAntiTrack.exe unhandled exception

Prior to the last update I would go weeks at a time with no CTD.

 

 

 

[Brocky120 65]

33 minutes ago, TacomaSailor said:

I fly about 2-hours per day - most days.  Following is the list of CTDs I have experienced in the last seven days and the faulting module as shown by event viewer (FS is Flightsimulator.exe):

FS nvwqf2um.dll
FS flightsim.exe (5 occurrences)
FS ucrtbase.dll
GTN_simulator.exe KRNL.dll (4 occurrences)
GTN_simulator.exe d3d11.dll (2 occurrences)
AVASTAntiTrack.exe ucrtbase.dll (2 occurrences)
AVASTAntiTrack.exe libcef.dll 
AVASTAntiTrack.exe unhandled exception

Prior to the last update I would go weeks at a time with no CTD.

 

What are the exception codes?

 

nvwqf2um.dll - Try a clean install of the graphics card driver using DDU, and create your own driver using NVcleanstall and see if that helps

flightsim.exe - Exception code? 0xc0000005? - If so I get it from time to time, highly likely RAM/CPU related

ucrtbase.dll - Ensure all visual is fully up to date - https://github.com/abbodi1406/vcredist

 

 

Not entirely sure on the rest, run this in Command Prompt (CMD) as Admin:

 

sfc /scannow

DISM /Online /Cleanup Image /CheckHealth

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /RestoreHealth

sfc /scannow

 

 

reboot your computer, run it again, and reboot again.

 

Then Open Disk Cleanup as Administrator, select your main drive, and tick every box to clean up, you can do this for all drives on the computer. Finally restart your computer and try.

 

Edited August 15, 2023 by Brocky120
add info