Warning: Your graphics device has encountered a problem

Bug Reporting Hub Install, Performance & Graphics
, ,
1331

its related to the subject we are talking about, we have seen some had problems with the newest driver with the desktop window manager. so rolling back to the pervious driver for them is indeed a solution in this case until nvidia figure out what conflict occurred in these user’s end. but this error has nothing to do with MSFS, because desktop window manager and its gpu high usage is a separate error, due to the special function of the windows system process of the desktop window manager.

but the same scenario can’t be applied to SU10 CTD, as users are getting it in a large scale of hardwares, so we cant count the two scenarios as a same one. & for this reason, upgrading to the newest driver is better than getting back to the older one, because the newest will limit the incompatibilities if they exist.

Conflicts, Errors, incompatibilities, are always a part from the development process since the early days of introducing windows and softwares running on it.

so if we think we can deal with programs with 0 errors all the time, that would be fiction. LOL.

3 Likes
1332

I don’t overclock and I run zero mods. Zero CTDs after the latest SU. Did the driver update from Nvidia and got three back to back CTDs. Currently unusable. Running a 3080RTX. Hope they fix this soon. :frowning:

2 Likes
1333

When I was programming (not games but robots and business software) there was a saying. “If it works the first time I must have made a mistake”

3 Likes
1334

:wave: Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

No

Have you disabled/removed all your mods and addons?

Yes.

Brief description of the issue:

Game crahes to desktop after taking off with warning window that states: Warning - Your graphics device encountered a problem.

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

Detailed steps to reproduce the issue encountered:

Start a flight, and take off.

PC specs and/or peripheral set up if relevant:

AMD Ryzen 9 5900X, 64 GB 3600 MHz RAM, ASUS Tuf 3090Ti.

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

1898824341928503798

Build Version # when you first started experiencing this issue:

1.27.21.0

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

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

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

If relevant, provide additional screenshots/video:

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

1335

Nice, hhhh

1 Like
1336

It was a very interesting time. The computers I was using were the same ones used to to guide the Apollo missions as well as 50 tonne robots. A long time ago in a land faraway.

1 Like
1337

I’m getting the error on a 3090 Ti with 24 GB of ram. Running 64 GB actual RAM in my system. If I am using all the RAM in my system. I have way bigger issues than I am aware of.

1 Like
1338

Genuine & Original (expression). Cheers.

1340

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

I can reproduce it only with DX12

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

Game crahes to desktop after taking off with warning window that states: Warning - Your graphics device encountered a problem.

If relevant, provide additional screenshots/video:

Intel 12700KF , AMD RX Vega 64, 32GB RAM , WINDOWS 10 22h2

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

2079555441204951943

Also I got this one

breakpoint
breakpoint365×201 5.93 KB

1341

Guys, I have come across something possibly important. I went looking to a bunch of crash dump files and they all had the same details inside them relating to a problem with Nvidia’s Aftermath SDK program that improves gameplay. I looked through all 31 crash dumps and they all said the same thing. I tried to replace the relevant .dll file in the game directory and I went from crashing before the main menu to at least getting into the main menu for a couple minutes before it crashed again. I am unable to verify if I have the most up-to-date version of this Nvidia aftermath program but I am looking into it more. Google searching has pointed me to various sites and articles talking about this and the “Your gpu device has encountered an error” error.

image
image480×289 7.85 KB

1342

So I was running the 522 drivers that were striped down to nothing but video driver and audio driver, nothing else. I had no errors except the crashed when leaving the game, and for some reason when running in PG I could only do single digit FPS no matter what.

So I decided to install the full driver instead of making a strip down driver, did a ddu, installed the fresh 5.22 GRD driver and within 20 min, I got the little message your card is misconfigure etc…same as everyone of you are getting.

I then re-installed 5.22 GRD striped of nothing but graphics driver and audio driver, and lo and behold, no more message (so far) but will still crash on the way out of the menus leaving the game I call it fast quit. ;p

But now my PG fps have gone back to be double digits again, and while it will do 36 fps, the studders are so bad its like the sim is waiting on packets to get here before it will display the next set of frames. If I lock fps at 20 it runs smooth no studders.

To me it feels like the servers are having issues ( the low PG fps started right after they migrated the servers last week, and before I installed the beta 11 update).

1343

Your statement reminded me of these TV commercials:
DIRECT TV: “Get Rid Of Cable” - The Full Compilation - YouTube

1344

hhhhhhhh.

anyway now lets stay on subject, we got out of it many times, LOL.

1345

This is how errors are beintg spotted by devs, but fixing them is complex & demanding, and out of range of the regular troubleshootings users can do.

1346

:wave: Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

NO

Have you disabled/removed all your mods and addons?

NO

Brief description of the issue:

The simulator stops.

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

Microsoft Flight Simulator

Your graphics device has encountered a problem and Microsoft Flight Simulator will exit.
This may be due to graphics card overclocking, overheating or due to a driver fault.

OK

Your graphics device has encountered a problem and Microsoft Flight Simulator will exit.
This may be due to graphics card overclocking, overheating or due to a driver fault.

OK

Detailed steps to reproduce the issue encountered:

Every time the flgiht reachs an hours

PC specs and/or peripheral set up if relevant:

Rayzen 7 . Geforce 3070 64mb RAM

If on PC, Fault Bucket ID - Instructions here - Falha no bucket , tipo 0 - Falha no bucket , tipo 0 - Falha no bucket 1234370011979737258, tipo 5 - Falha no bucket 1380610964820555909, tipo 5 - Falha no bucket , tipo 0 - Falha no bucket 1667417165950008190, tipo 4 - Falha no bucket , tipo 0
Nome do Evento: CbsPackageServicingFailure2 - Falha no bucket , tipo 0
Nome do Evento: CbsPackageServicingFailure2
Resposta: Não disponível
ID do CAB: 0 - Falha no bucket 1587934709365739186, tipo 5
Nome do Evento: CbsPackageServicingFailure2
Resposta: Não disponível
ID do CAB: 0 - Falha no bucket , tipo 0
Nome do Evento: CbsPackageServicingFailure2
Resposta: Não disponível
ID do CAB: 0 - Falha no bucket , tipo 0
Nome do Evento: CbsPackageServicingFailure2
Resposta: Não disponível
ID do CAB: 0 -

Resposta: Não disponível
ID do CAB: 0
Nome do Evento: APPCRASH
Resposta: Não disponível
ID do CAB: 0
Nome do Evento: APPCRASH
Resposta: Não disponível
ID do CAB: 0
Nome
Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

Build Version # when you first started experiencing this issue: Neve rhappened Latest Version with Canadian Scenery

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

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

Did not try

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

If relevant, provide additional screenshots/video:Falha no bucket , tipo 0
Nome do Evento: CbsPackageServicingFailure2
Resposta: Não disponível
ID do CAB: 0

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

1 Like
1347

image
image832×815 38.3 KB

Not thinking it is using all of the memory as some of the posts seem to point to. I am using about 10 Gigs of RAM out of the 64 total I am using on my system.

1348

MODERATOR EDIT:
This post merged into this topic.

dx12 Developer Mode click options CTD try again

Cpu i7-9750H
Ram 32GB
Video NVIDIA GeForce RTX 2060
Solid State Drive 512GB

Screenshot 2022-10-17 235751
Screenshot 2022-10-17 2357511280×669 266 KB

1349

The Nsight Aftermath library doesn’t improve gameplay. It allows developers to generate minidumps when the GPU crashes. The dumps are important, as those show the reason the GPU crashed.

1 Like
1350

Here I also turned off this option and it solved.

1351

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

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

Are you using DX12?

Are you using DLSS?

If relevant, provide additional screenshots/video: