Fatal D3D error (25, DXGI_ERROR_DEVICE_HUNG, 0x887a0006)

[Thortuga]

So, I'm about to stop playing at this point. It keeps happening, completely random, temps and utilizations in HWinfo are normal. Drivers up do date, also windows. I gave admin rights to the game and steam. There is literally no way for me to track what the actual problem is.

Could someone help me if I share a Dxdiag maybe?

[MajesticAsian21]

Originally posted by mart:

I was plagued by this crashing since launch and like many others tried a combination of all the fixes already suggested and what worked for me is underclocking my gpu. I was sceptical but gave it a try and haven't had a crash since and could turn all other options back on up to max, frame gen, ddls 4, highest res textures, mods with reframework etc.
Running on i9 12900, rtx4090.
Underclocked using MSI after burner, first had core clock set to -200MHz and memory clock at +0MHz and this was running all good. I have since changed it to -100MHz underclock and it is also running stable for last 2 days.

I underclocked mine by 300 and it still crashes. Should I go even lower?

[AmaiAmai]

Originally posted by MajesticAsian21:

Originally posted by mart:

I was plagued by this crashing since launch and like many others tried a combination of all the fixes already suggested and what worked for me is underclocking my gpu. I was sceptical but gave it a try and haven't had a crash since and could turn all other options back on up to max, frame gen, ddls 4, highest res textures, mods with reframework etc.
Running on i9 12900, rtx4090.
Underclocked using MSI after burner, first had core clock set to -200MHz and memory clock at +0MHz and this was running all good. I have since changed it to -100MHz underclock and it is also running stable for last 2 days.

I underclocked mine by 300 and it still crashes. Should I go even lower?

If you are getting the error the OP said, then it likely won't matter much. It worked for them because they had a bad overclock, unless that is your issue it won't matter.

The error listed by the OP just means that the operating system thinks the GPU is in a non-responsive state. There can be various reasons both hardware and software based, but if it's this game only it's unlikely a hardware one.

Yes, bad overclocks can cause it. But they are not the only cause, and the cause can be literally anything. But one thing is in common with people having the issue: the game -- it is the game that is at fault and the devs do need to fix the problem.

Now, it's true you can set the operating system to not check if the GPU is frozen by various means

The easiest is adjusting TDR in Windows:

https://answers.microsoft.com/en-us/windows/forum/all/how-to-change-tdr-values-and-edit-registry-keys/84a9b079-6048-4968-982a-e648152c17fd

You will have to find the value that works best for you as it is entirely dependent on your system, and also...understanding TDR if you care about understanding what the error means and want to look deeper into the cause (in case you have some software that might simply be tripping this as well, but the game is still at fault):

https://learn.microsoft.com/en-us/windows-hardware/drivers/display/timeout-detection-and-recovery

But the thing is that IF the GPU is actually hung it will freeze your computer or bluescreen.

[アンジェル]

Originally posted by AmaiAmai:

Originally posted by MajesticAsian21:

I underclocked mine by 300 and it still crashes. Should I go even lower?

If you are getting the error the OP said, then it likely won't matter much. It worked for them because they had a bad overclock, unless that is your issue it won't matter.

The error listed by the OP just means that the operating system thinks the GPU is in a non-responsive state. There can be various reasons both hardware and software based, but if it's this game only it's unlikely a hardware one.

Yes, bad overclocks can cause it. But they are not the only cause, and the cause can be literally anything. But one thing is in common with people having the issue: the game -- it is the game that is at fault and the devs do need to fix the problem.

Now, it's true you can set the operating system to not check if the GPU is frozen by various means

The easiest is adjusting TDR in Windows:

https://answers.microsoft.com/en-us/windows/forum/all/how-to-change-tdr-values-and-edit-registry-keys/84a9b079-6048-4968-982a-e648152c17fd

You will have to find the value that works best for you as it is entirely dependent on your system, and also...understanding TDR if you care about understanding what the error means and want to look deeper into the cause (in case you have some software that might simply be tripping this as well, but the game is still at fault):

https://learn.microsoft.com/en-us/windows-hardware/drivers/display/timeout-detection-and-recovery

But the thing is that IF the GPU is actually hung it will freeze your computer or bluescreen.

It is not a game problem.

[Armnorn]

Got the same issue: https://pastebin.com/hUZ0vmUM DxDiag followed by Crash Report. Sadly they are partially in German

I am suspecting that it is from me upgrading my graphics driver or a holdover from me installing mods though I was pretty sure I removed everything after it caused issues. Can someone pinpoint what it is? I don't really understand the logs. Haven't been able to finish a single hunt. And I have tried several times. Until today everything worked fine.

[Zehke]

Originally posted by AmaiAmai:

Originally posted by MajesticAsian21:

I underclocked mine by 300 and it still crashes. Should I go even lower?

If you are getting the error the OP said, then it likely won't matter much. It worked for them because they had a bad overclock, unless that is your issue it won't matter.

The error listed by the OP just means that the operating system thinks the GPU is in a non-responsive state. There can be various reasons both hardware and software based, but if it's this game only it's unlikely a hardware one.

Yes, bad overclocks can cause it. But they are not the only cause, and the cause can be literally anything. But one thing is in common with people having the issue: the game -- it is the game that is at fault and the devs do need to fix the problem.

Now, it's true you can set the operating system to not check if the GPU is frozen by various means

The easiest is adjusting TDR in Windows:

https://answers.microsoft.com/en-us/windows/forum/all/how-to-change-tdr-values-and-edit-registry-keys/84a9b079-6048-4968-982a-e648152c17fd

You will have to find the value that works best for you as it is entirely dependent on your system, and also...understanding TDR if you care about understanding what the error means and want to look deeper into the cause (in case you have some software that might simply be tripping this as well, but the game is still at fault):

https://learn.microsoft.com/en-us/windows-hardware/drivers/display/timeout-detection-and-recovery

But the thing is that IF the GPU is actually hung it will freeze your computer or bluescreen.

To me the error looks like a access-violation. Could be a bad sign, but before worrying to much, try this guide:

https://www.makeuseof.com/windows-dxgi-error-device-hung-error/

If this does not help, contact the vendor. In the worst case there is an access-violation from the memory-controller on GPU-memory. (Which can point to corrupted memory)

Besides, don't set the TDR to '0'—this is complete nonsense. The graphics driver will not recover from stalls (single cores of a gpu constantly stall - this is how they work), which will almost certainly result in a bluescreen. Instead, set your GPU power settings to default, unless an employee of the vendor specifically instructed you to use a certain value. And if the GPU hangs, since Windows Vista the OS is capable of preventing crashes by resetting the graphics-driver (or call it TDR!)

[Zehke]

Followup comment:
Who reads this, who likes overclocking each poor processor:
Inform yourself about *electromigration* and *power dissipation* => this is what shortens the lifespan of your chip!

Beside you cannot only kill your chip you instantly kill your warranty

[HIRO]

Originally posted by アンジェル:

Originally posted by Thortuga:

Fatal D3D error (25, DXGI_ERROR_DEVICE_HUNG, 0x887a0006)
So, I'm about to stop playing at this point. It keeps happening, completely random, temps and utilizations in HWinfo are normal. Drivers up do date, also windows. I gave admin rights to the game and steam. There is literally no way for me to track what the actual problem is.

Could someone help me if I share a Dxdiag maybe?

No DxDiag report needed. It can help to identify more indicators of the issue, but mainly it is a hardware issue you having.

I would just make a guess into the blue that it is some AMD GPU which are known to behave like that if they come overclocked out of the box. So take something like MSI Afterburner and tune it down by a few hundred Hertz and check if it helps.

Would like to add that you can simply google "D3D error" and most post on reddit include a RTX 4070-4080. this is not an AMD issue

[The Architect]

I've been getting these too recently.

This is the only game with this issue, i've played quite long sessions of Assassin's Creed Shadows and i have no issues.

I've tried:

- Lower GPU clocks (i didn't overclock it)
- Disable RAM Overclock
- DDU Safe Mode, Install older driver that is considered more stable

These didn't make any difference, the temperatures and everything is more than fine, my RTX4080 power cable is not burned or on the GPU either, the GPU is properly slotted as well.

Event Viewer shows this:

The description for Event ID 153 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\Video3
Error occurred on GPUID: 100

chkdsk didn't help or sfc /scannow

SMART shows no issues with the drive either.

[Lumi]

Originally posted by Thortuga:

Originally posted by アンジェル:

Well, I see two issues which might be related: lack of free space on C: and memory leak here and there.

Thank you, I'll try to free some space on C then, though MH Wilds is installed on D.
As for memory leaks, you mean Ram or Vram? Any clue on how to fix that ?

Would it be possible to clear up enough space to move the game to your C drive? My crashes went away after moving the game from a SATA SSD to a NVMe one.

[G*R | Shukusei]

Originally posted by Lumi:

Originally posted by Thortuga:

Thank you, I'll try to free some space on C then, though MH Wilds is installed on D.
As for memory leaks, you mean Ram or Vram? Any clue on how to fix that ?

Would it be possible to clear up enough space to move the game to your C drive? My crashes went away after moving the game from a SATA SSD to a NVMe one.

Don't think that matter, same issue as everyone above. Installed on NVME from the get go.
All troubleshooting options exhausted.

Somehow someway got past the crash, but died on the boss. Ran back, crashed again.

Removed the game, don't care anymore.

No refund 'possible' -70

GOG has gotten themselves a new customer.

[The Architect]

I no longer have this issue, i renamed the game folder and verified on Steam so it downloaded everything again, then i installed RE Framework again and found out some mods were causing this issue, in my case it was "Crown Helper" mod.

So remove all mods and maybe try downloading the game again but without having any files on new folder by renaming existing one before downloading the game again.

The DXGI error seems to be exclusive to Capcom games too, Google doesn't show anything else besides Street Fighter and Dragons Dogma 2 for this error.

If it was indeed a hardware issue then it would cause issues in other games too, in the event it was the SSD then SMART would show something too, it doesn't.

So try to get rid of all mods and then install them again maybe one by one and play a bit before installing a new mod.

Alternative is installing it to another SSD if you have but you should avoid placing all the mods back if you use them and install one by one.

[Shokudaikiri Mitsutada]

This was literally the same error that haunted people in Rise.

[HIRO]

Used DDU to uninstall all my GPU drivers and reinstalled them in how DDU tells you to, the issue hasn't happened in 5 days, will keep updated

[Glass]

Originally posted by アンジェル:

Originally posted by Thortuga:

My config:

6950xt
i5 13600k
32gb ram ddr4 3600hz
Sata SSD

Already tried lowering clocks (to those indicated on my graphics card website), didn't help.
I asked about Dxdiag as I've seen people asking for it when trying to solve problems.

Yeah. I prefer seeing a DxDiag instead of what you just wrote. A DxDiag is more reliable and tells much more.

Try lowering the clock more, or better, run the GPU in debug mode.

Originally posted by Thortuga:

Also, this error message is posted by many Nvidia users too

I see no Nvidia user here with that problem.

I have the exact same issue, and im nvidia user.

[The Architect]

Originally posted by Glass:

Originally posted by アンジェル:

Yeah. I prefer seeing a DxDiag instead of what you just wrote. A DxDiag is more reliable and tells much more.

Try lowering the clock more, or better, run the GPU in debug mode.



I see no Nvidia user here with that problem.

I have the exact same issue, and im nvidia user.

I use NVIDIA and no longer have this problem, currently on 572.83

Complete install of game from scratch and removing mods solved the problem, using mods again but installed one by one again but not all of them, RE Framework mods can cause crashes.