Warning: Your graphics device has encountered a problem

Crash again 3 times in a row after latest update.
NVIDIA drivers are updated and nothing changed in my SIM… except for the damages that are done after each update

3 Likes

Maybe I should keep my old driver and current underclocking settings, it is stable right now for me, can fly 10+ hours without issues.

How to rollback NVIDIA drivers?

You can go to the Nvidia drivers page and download any version to your taste.
Can’t link directly because you need to find the drivers corresponding to your GPU but you can start here:

1 Like

Thanks mate.

Please let us know if you’re still w/out issues for the previous driver.

Today i had this issue first time! CTD after Error Message…

1 Like

If your problems are still ongoing you may be best doing a ddu before reinstalling the latest drivers. Use the search function above to find out how.

1 Like

I never saw this message. What is this?

2 Likes

Welcome to the club. This is an error that was fixed in SU 12 (Externally) :wink:

To be honest I get this way less than I used to but still get it now and again so it definitely isnt fixed

yeah i got this too today. first time actually. just installed latest nvidea drivers, did a restart and started a flight. the moment i got on the rwy ready for takeoff, BAM

2 Likes

Haven’t had this issue before. Now every flight after SU12… (does rolling back to older nvidia drivers help? haven’t had time to try yet…)

This is what Microsoft’s ChatGPT have to say about this CTD: (its really deep) lol

i would try these advanced programming level workarounds, but no free time @ the moment, anyone else is welcome if he likes.

BTW: These steps are officially troubleshooting recommendations on Microsoft’s website.
also, i tried to test ChatGPT many times, with complex Qs, but it can really give you accurate updated results if you used the right words.

for more info, you can read the sources that chatgpt includes if you used the same Q.

1 Like

had the issue last few days on a brand new PC
Ryzen 9/RTX3070ti/32GB/1TB all settings on ultra

after much testing and frustrations ,the culprit seems to be for me DX12 and DLSS

Reverted back to DX11 and TAA and now 2 days without the issue

gonna keep testing following days

1 Like

Ryzen 9/5900X/RTX3070/32GB/1TB all settings on ultra.

DX12 and TAA in my side. Version: 531.41 03/23/2023 Nvidia Drivers.

LEIPZIG taxi: CTD. :face_exhaling:

1 Like

We need a FIX.

Some user migth remember that I tried a long time to reproduce the issue, without success.

Now, first time, I get the popup while scrolling on the world map.

The logged messages in event viewer:

Error Event 0 nvlddmkm :
\Device\Video3
Error occurred on GPUID: 100
Warning Event 4101 nvlddmkm:
nvlddmkm … restored
Error Event 1000 : Application Error
FlightSimulator.exe
Ausnahmecode: 0x80000003

The created CrashReport within MSFS points, as expected to:
OnCrash:
Msg=GPU Device Removed

I installed some days ago the nvidia driver release 531.41 , who knows…

Another thing to mention, I had since a long time the MSI-Afterburner not running and started it now for a Test-Case. Might have also an effect.

EDIT:

additional noticalble: MSFS consume now on the world-map ~70% load on a 4080

Do you have the same issue if you follow the OP’s steps to reproduce it?

Kinda - flying in a high load area (LA) right now with the latest drivers I encounter this issue on SU12 (not in beta and not with the NV driver which I had installed during beta).

Provide extra information to complete the original description of the issue:

As telemetry doesn’t seem to have been uploaded so I include it here as well as all other relevant information:

CrashReport

CrashReport.txt (37.8 KB)

DxDiag

DxDiag.txt (107.6 KB)

UserCfg.opt as text

UserCfg.txt (3.4 KB)

Related eventviewer information:

nvlddmkm error
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="nvlddmkm" /> 
  <EventID Qualifiers="0">0</EventID> 
  <Version>0</Version> 
  <Level>2</Level> 
  <Task>0</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2023-03-25T17:24:21.3533808Z" /> 
  <EventRecordID>73957</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="4" ThreadID="12700" /> 
  <Channel>System</Channel> 
  <Computer>DESKTOP-XXXXXX</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>\Device\000000b3</Data> 
  <Data>Error occurred on GPUID: 100</Data> 
  <Binary>00000000020030000000000000000000000000000000000000000000000000000000000000000000</Binary> 
  </EventData>
  </Event>
Display warning
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Display" /> 
  <EventID Qualifiers="0">4101</EventID> 
  <Version>0</Version> 
  <Level>3</Level> 
  <Task>0</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2023-03-25T17:24:22.5559635Z" /> 
  <EventRecordID>73959</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="2244" ThreadID="0" /> 
  <Channel>System</Channel> 
  <Computer>DESKTOP-XXXXXX</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>nvlddmkm</Data> 
  <Data /> 
  </EventData>
  </Event>`
MSFS error
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> 
  <EventID>1000</EventID> 
  <Version>0</Version> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000000000000000</Keywords> 
  <TimeCreated SystemTime="2023-03-25T17:24:43.0665741Z" /> 
  <EventRecordID>24934</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="19488" ThreadID="8340" /> 
  <Channel>Application</Channel> 
  <Computer>DESKTOP-XXXXXX</Computer> 
  <Security UserID="XXXXXX" /> 
  </System>
- <EventData>
  <Data Name="AppName">FlightSimulator.exe</Data> 
  <Data Name="AppVersion">1.31.22.0</Data> 
  <Data Name="AppTimeStamp">6409dda0</Data> 
  <Data Name="ModuleName">FlightSimulator.exe</Data> 
  <Data Name="ModuleVersion">1.31.22.0</Data> 
  <Data Name="ModuleTimeStamp">6409dda0</Data> 
  <Data Name="ExceptionCode">80000003</Data> 
  <Data Name="FaultingOffset">0000000001a24db2</Data> 
  <Data Name="ProcessId">0xbdc</Data> 
  <Data Name="ProcessCreationTime">0x1d95f38d29df879</Data> 
  <Data Name="AppPath">C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe</Data> 
  <Data Name="ModulePath">C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe</Data> 
  <Data Name="IntegratorReportId">3bfc9705-2ebc-482f-a53c-eac821717206</Data> 
  <Data Name="PackageFullName" /> 
  <Data Name="PackageRelativeAppId" /> 
  </EventData>
  </Event>`

Are you using DX12?

Yes

Are you using DLSS?

yes, DLAA mode

If relevant, provide additional screenshots/video:

I have never had this error and since I’ve updated my nvidia drivers I got this on the first two attempts to fly. I tried the ini A310 from LVFR’s KMIA and the first error/crash happened at the end of the pushback and the second time I error/crashed a few minutes after I started getting the EFB set up.

The only reason I upgraded the driver so soon was that it was Diablo 4 ready as I’ve been playing the open beta, but now I’m going to downgrade the drivers and see what happens. I hope this isn’t a SU12 issue.

1 Like

Rolling back to Game Ready Driver 531.29 fixed this issue for me. I sent a notification through NVIDIA Geforce experience. I think the issue is with the latest driver.

3 Likes

Yup, just rolled back to 531.18 and no issues. I also noticed my GPU wasn’t working as hard.

2 Likes