I recently had to get a replacement computer from Corsair. I reinstalled MSFS 2020. I updated all my drivers. Now I am having issues with the error message “DXGI_Error_device_hung” when loading. On my old system with the same specs, I was running the same settings. Now it’s a huge issue. I tried changing drivers to an older version. I had MSI afterburner but uninstalled because people said it was the issue. I am still having the same issue. Nvidia App recommends the DX12 setting. I was using that setting the last system. I tried DX11 and still having the issue. I am not overclocking the system. I am running out of box with no tweaks in the bios.
Had that since last year update. Had to unistall all graphic drivers and installed 588 version and never updated again.
DX12 is important, DX11 often causes this error. There is a long thread regarding this error. Make sure all Windows updates are installed. A bunch of root causes for this problem was solved by a Windows update some time ago. Nevertheless often it is a hardware issue.
I went back to 581.80. I will try this one.
Yeah, Microsoft removed the Zendesk post at the bottom of the error message. So, I am searching the forums to maybe find something definite and final. I am running into alot of midstream fixes but see people started having issues again even with the fixes. I have been running it in DX12. I don’t know the reason it now stopped working. No changes other than the MSI afterburner, just started.
Yes, I made the same experience. There are a lot of workarounds floating around, but the one big solution solving the problem is not available. At least I was not able to find it.
I’ve had the DXGI error only twice since MSFS 2020 launched.
The first time was sometime last year, and I eventually tracked down the cause - it was MSI Afterburner and RTSS. After fully uninstalling both, the problem was gone.
The second time was just this week. I had just bought a new 4K OLED monitor (AOC Agon Pro AG326UD) and was testing HDR and general display behavior on an older Nvidia driver, specifically 566.14. After some time, I suddenly got a DXGI error.
What really surprised me was that I had never had issues with this driver before, so at first I thought something might be wrong with the monitor or its driver. MSFS 2024 wasn’t even on my list of suspects.
After some analysis, it turned out the Nvidia driver itself had somehow bugged out or become corrupted. I reinstalled the driver and the issue completely disappeared. After further testing, I installed the latest hotfix driver and I haven’t had any problems since.
https://forums.flightsimulator.com/t/nvidia-geforce-hotfix-driver-591-67-discussion-thread/751850
So in my case, it wasn’t Windows updates or MSFS servers - it was a corrupted Nvidia driver install.
I don’t have 2024. I only have 2020. I am still pulling my hair out on this. I made sure everything is up to date on drivers. In 2025, I had an issue where I had to go back to 572.16 and delete Nvidia App completely to get it to stop crashing. My game driver for Geforce is up to date and I am using the Nvidia app. I uninstalled MSI afterburner. The zendesk is no help. I don’t mess with any setting on the computer. I took it out of the box. Turned it on updated windows and all drivers. Installed my Pimax, MSFS 2020, downloaded all my purchases from the MS Store. rebooted. Installed GSX, FSTL, and Fs2crew SOP1 for the 737. it worked great until last week and mando MSFS update hit. Then this all started. I am wondering if I need to delete MSFS 2020 and reinstall it. Its going to take all day to download everything again.
I ended up reinstalling MSFS 2020 and the Nvidia drivers. IT seems to be working in DX 11. I am scared to move to DX 12 where it looked and ran the best before the new system. Now I am having audio issues with it. I use flex beats headphones in VR for my FS2crew. Now I getting grabbled audio or it sounds like digital artifact. The headphones are working normally will my iphone and other devices. just not MSFS 2020 ATC. I was hoping a reinstall would have fixed that issue also.