Unfortunately, the bug dxgi_error_device_hung (0x887a0006) has not been fixed in the new Beta 4 version (for me)… Now the SIM CTD’s more often without the message, but I assume it is the same problem
7950X3D / 7900XTX
For me, the CTDs started with the su4 beta. It happens mostly when I’m tinkering in dev mode or when I switch windows with ALT + TAB.
I have them a little less often when I activate the most recent AMD FSR 3 DLL with DLSS Swapper (see above). Be careful: you have to repeat the manipulation after each installation of a new msfs 2024 beta.
AMD 9070xt with last Adrenaline driver.
I was hoping they had fixed it with the new beta 4 update, but unfortunately that doesn’t seem to be the case.
Yes, I tried the DLL Swapper suggestion (thank you for that), but without success… I still get frequent CTDs, where the SIM just closes without any message.
Before that, I tried downgrading various Adrenalin drivers, deleting the cache (AMD and MSFS), and various setting changes (minimizing graphics workload), but nothing helped…
I hope there will be a fix soon! The su4 beta is actually really fun in terms of performance. But with my frequent crashes unplayable
Then you are wrong in this thread. In this thread we are discussing about GPU hangs. CTDs without messages have other reasons. Please analyze with the Windows Logs, what happened.
I don’t think I’m wrong here. The real problem is this:
Sometimes also this:
That’s why I tried the actually good idea mentioned earlier in the thread and manually updated to the latest version using DLSS Swapper, but then I often get crashes without any message. So the basic problem is dxgi_error_device_hung (0x887a0006)
But this is no CTD, this is a GPU hang. You were talking about CTDs without message.
With GPU hang you are right, without message not. Completely different problems, completely different reasons.
Hello everyone, I had this issue almost every flight in MSFS 2024 driving me crazy and making it absolutely unplayable for longer airliner flights. For me the solution was to disable by Alt+F3 all of the filters in the NVDIA app. Since I have done this there were no issues at all. Absolutely no issues means, that I can fly 12 hour flight and land on my destination.
This one once again confirms that MSFS absolutely hates any type of overlays, filters, FPS-counters and so on. By the way, FSRealistic in MSFS 2020 made also so much trouble two years ago, so I have banned this since then.
I solved my “device hung” CTD problem by installing the latest AMD GPU driver version 25.10.2, after running the “AMD Cleanup Utility” who runs in safe mode. Since then, no more CTDs…
I just had this error latest build on beta, RTX 4090 along with 7950x3D
So I think I have resolved this problem, for myself anyway and feel somewhat foolish as what seems to be causing the issue was kind of obvious. Firstly, my system is not overheating, is not overclocked and has the latest up to date drivers, So I was fairly happy the issue was not related to these matters. I have now had two full active weeks with no hangs, whereas before I was getting almost one a day, sometimes two. Have been with MSFS2024 since the start and as we all know it was somewhat unplayable initially with it suffering from a variety of different CTDs. However, since SU2 I have mostly suffered from the dreaded 0x887a0006 / 7 graphics hang. Like most of you I have searched high and low and implemented dozens of suggested solutions, all to no avail. Whilst lying awake one night thinking about what to do next, as I seem to have exhausted all possible fixes, I suddenly realised that there is a pattern to the issue. I fly almost exclusively GA and spend my time flying in and around the UK countries and on going on world missions. e.g. I flew from top of Scandinavia to bottom tip of Africa, approx. 100 flights and I only recall one hang. I then flew from southernmost tip of the American Continent to the northernmost tip, again about 100 flights. I would occasionally jump back to flying in and around the UK where I seemed to suffer regular hangs. On this last trip up the east coast of the American Continent I never suffered any hangs until I reached USA where they became regular. I use MSFS Addons Linker and have downloaded numerous airport and scenery mods which I separate into folders depending on country. Sometimes I will activate all mods for the country in which I am flying and sometimes only those mods for the start and destination airport. I have about ten USA mods and dozens for the UK. When flying down Africa, due to the lack of airport mods I generally flew with no mods activated at all. The same can be said for when I flew up the south American coast with no issue and it all started to go wrong again when I activated my USA airports. Two weeks ago I then started flying with no airport/scenery mods/add ons. I had no issues. I then upped my graphics back to Ultra, again no issues. Week two and I started to use 2024 mods only, again no issues. So, in short DO NOT under any circumstances use any mods that are not approved for 2024. Once again I am a happy simmer and I hope the past two weeks have not just been a fluke. I am no expert, and I know we have been advised to clear out old 2020 mods for 2024 but there is no shortage of users out there who report using old 2020 mods as they still seem to work with no issue…well maybe they don’t.
AMD Ryzen 9 78900X3d / Radeon RX 7900XTX 64Gb
1 Like
I occasionally experience “device hung” with my 9070 XT when I enable developer mode to display the FPS and switch between different windows several times using Alt+Tab, or when I record video using the Adrenaline Record function.
But as long as developer mode isn’t enabled, I have no stability issues.
Windows 11 Update KB5072033 - Must-Have for AMD Gamers.
The update improves stability by reducing CTD and “device hung” crashes in games.
More info > https://forums.flightsimulator.com/t/windows-11-25h2-24h2-and-msfs-observations-insights-issues-and-tips
1 Like
Running MSFS 2024 on Windows 10 with a GTX 1080 Ti.
I’ve never experienced this issue before, neither in 2020 nor in 2024…. until today when it happened twice for no apparent reason. I haven’t installed any Windows or Nvidia driver updates (my 1080Ti is no longer supported since november, and drivers worked flawlessly until now, so I can’t figure out why today they behave differently. Haven’t done any recent changes to my computer, and this is the first time the error has appeared.
It’s frustrating, especially knowing this problem has affected 2020 since 2023, and disappointing that 2024 is now impacted without a proper patch in place. Since I haven’t changed my PC setup, I suspect it might be something on MSFS’s server side that’s causing the driver to crash.
The application software has nothing to do with Device Hungs. It is a Hardware/Driver/OS issue. The Device Hungs of AMD cards have been fixed by a Windows Update, not a Simulator Update.
So no, there is nothing on the server side or similar. You have to search for a local problem, but outside the Simulator.
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.
1 Like
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:
After the last update after the “Fly now” everything freeze and the nessage DXGI_ERROR_DEVICE_HUNG (0x887a0006) appear. I have install and DDU the drivers on my AMD 6900XT card, but nothing…Installing windows and game again doesn’t help
Past week I started to have this error on MSFS 2024 - GTX 1080 Ti. Never happened before and I still can’t find a reason why my GPU or driver started to crash.
I was on NVidia drivers 581.xx , the latest for the 1080Ti.
I reverted back to 576.28 as many recommended, and for the past two days i never a crash anymore, and fps are even better, gained at least 6-10 fps!
Drivers 576.28 didn’t completely fix the issue for me, but 577.00 combined with undervolting and underclocking my GPU did the trick.
Slightly off-topic, but I’d like to share how I resolved this problem on my end.
For those with an ASUS Strix 1080 Ti like mine, here’s what I did:
- I asked Copilot/Chat GPT for a stable voltage and GPU clock for my model and got 1850 MHz @ 0.95 V, but you need to find the ideal combination that avoids VRel throttling.
- In GPU Tweak III, i adjusted the clock curve by clicking the button VF Tuner, and capped the GPU at 1835 Mhz @ 0.95 V, which worked better than 1850 Mhz.
- Run GPU-Z and checked the Sensors tab to ensure the PerCap Reason isn’t showing VRel. If it is, that means the GPU is demanding more voltage than it can receive to stay stable, so it compensates by lowering the clock speed. You could also be experiencing thermal throttling due to default or higher voltages.
- Back in GPU Tweak, I lowered the clock slightly while keeping 0.95V as the maximum voltage (the GPU might occasionally jump to 0.98 if necessary, but 0.95V is a solid stable value).
- Keep experimenting with the GPU clock and voltage until you find a stable setup that eliminates VRel throttling.
- Increased the Power Target to 120%. This doesn’t boost the GPU’s actual power usage, but it makes it more tolerant if it needs a bit extra.
Since configuring my GPU this way, I haven’t had any CTDs or DXGI Device Hung errors for days actually. I’ve also completely eliminated micro stutters, reduced temps by 20 degrees, and achieved stable FPS at 1440p, capped at 45 before frame generation, which jump to 90 with AMD FG enabled. Hopefully this helps, and I’m confident you can replicate my steps even if you’re using MSI Afterburner or similar tools.
my 6900xt was not powerful enough and 16gb were filled too fast, so i got a 7900xtx and wow, what an upgrade. Problem is, now i get that error flying in VR, first a sound (probably when popping up the error window), then i see that steamVR lost track and i have to manually kill steamVR, msfs..
