Game Crash DX11BACKEND: DX device removed. Reason: 0x887A0007

[nrlemo]

dcs.log-20201207-171826.zip

[nrlemo]

2 hours ago, nrlemo said:

dcs.log-20201207-171826.zip 902.13 kB · 6 downloads

Hello!

i'd appreciate the help on this matter. I've got constant CTD usings DCS. Already did two complete reinstallations of DCS World and the GPU drivers using DDU.

 

Thanks

[Flappie]

Hello. Your archive doesn't contain the full dcs.log file, only the final crashlog. I can already say it looks like a driver crash, but it's not always the case:

 

# -------------- 20201207-171826 --------------
DCS/2.5.6.55960 (x86_64; Windows NT 10.0.20215)
C:\WINDOWS\SYSTEM32\d3d11.dll
# C0000005 ACCESS_VIOLATION at E395C7C5 00:00000000
SymInit: Symbol-SearchPath: '.;E:\DCS World;E:\DCS World\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'nrlemo'
OS-Version: 10.0.20215 () 0x100-0x1
0x000000000013C7C5 (d3d11): CreateDirect3D11SurfaceFromDXGISurface + 0xED95
0x0000000000030857 (dx11backend): createRenderer + 0x17907
0x0000000000076523 (edterrainGraphics41): edtg41::TerrainRenderable::dumpRenderItem + 0x65C13
0x00000000000C942F (edterrainGraphics41): createInstancerRenderable + 0x368FF
0x00000000000C4FB0 (edterrainGraphics41): createInstancerRenderable + 0x32480
0x00000000000C6200 (edterrainGraphics41): createInstancerRenderable + 0x336D0
0x00000000000DC9B8 (edCore): ed::this_thread::yield + 0x318
0x00000000000D3F7A (edCore): ed::make_render_thread_tasks + 0x1A
0x0000000000724408 (DCS): CoreUtils::TempFilesManager::operator= + 0x3B67D8
0x00000000006F6604 (DCS): CoreUtils::TempFilesManager::operator= + 0x3889D4
0x00000000006F69C9 (DCS): CoreUtils::TempFilesManager::operator= + 0x388D99
0x00000000016E8CEB (DCS): AmdPowerXpressRequestHighPerformance + 0xB1ACE7
0x00000000008E261E (DCS): CoreUtils::TempFilesManager::operator= + 0x5749EE
0x0000000000018394 (KERNEL32): BaseThreadInitThunk + 0x14
0x000000000005262B (ntdll): RtlUserThreadStart + 0x2B

 

 

Can you please attach your latest dcs.log file? ( C:\Users\username\Saved Games\DCS...\Logs\dcs.log )

Your dxdiag log might be useful too. Here's how to obtain one.

[nrlemo]

1 hour ago, Flappie said:

Hello. Your archive doesn't contain the full dcs.log file, only the final crashlog. I can already say it looks like a driver crash, but it's not always the case:

 

# -------------- 20201207-171826 --------------
DCS/2.5.6.55960 (x86_64; Windows NT 10.0.20215)
C:\WINDOWS\SYSTEM32\d3d11.dll
# C0000005 ACCESS_VIOLATION at E395C7C5 00:00000000
SymInit: Symbol-SearchPath: '.;E:\DCS World;E:\DCS World\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'nrlemo'
OS-Version: 10.0.20215 () 0x100-0x1
0x000000000013C7C5 (d3d11): CreateDirect3D11SurfaceFromDXGISurface + 0xED95
0x0000000000030857 (dx11backend): createRenderer + 0x17907
0x0000000000076523 (edterrainGraphics41): edtg41::TerrainRenderable::dumpRenderItem + 0x65C13
0x00000000000C942F (edterrainGraphics41): createInstancerRenderable + 0x368FF
0x00000000000C4FB0 (edterrainGraphics41): createInstancerRenderable + 0x32480
0x00000000000C6200 (edterrainGraphics41): createInstancerRenderable + 0x336D0
0x00000000000DC9B8 (edCore): ed::this_thread::yield + 0x318
0x00000000000D3F7A (edCore): ed::make_render_thread_tasks + 0x1A
0x0000000000724408 (DCS): CoreUtils::TempFilesManager::operator= + 0x3B67D8
0x00000000006F6604 (DCS): CoreUtils::TempFilesManager::operator= + 0x3889D4
0x00000000006F69C9 (DCS): CoreUtils::TempFilesManager::operator= + 0x388D99
0x00000000016E8CEB (DCS): AmdPowerXpressRequestHighPerformance + 0xB1ACE7
0x00000000008E261E (DCS): CoreUtils::TempFilesManager::operator= + 0x5749EE
0x0000000000018394 (KERNEL32): BaseThreadInitThunk + 0x14
0x000000000005262B (ntdll): RtlUserThreadStart + 0x2B

 

 

Can you please attach your latest dcs.log file? ( C:\Users\username\Saved Games\DCS...\Logs\dcs.log )

Your dxdiag log might be useful too. Here's how to obtain one.

Hello Flappie, thanks for your reply, i think the log is this one.

dcs.log

[Flappie]

Thank you. This is the dreaded "DXGI_ERROR_DEVICE_REMOVED" error, which means the GPU was not responding to DirectX requests in the expected timing.

 

However, you have two unusual events a few seconds before the crash: an "invalidated" audio device, and a new TrackIR discovery (as if you had closed the TIR program then reopened it while the game was on - did you?).

 

2020-12-07 20:10:44.332 ERROR   SOUND: IAudioClient::GetCurrentPadding failed: 0x88890004 (AUDCLNT_E_DEVICE_INVALIDATED)
2020-12-07 20:10:45.734 INFO    SOUND: Opening default audio device.
2020-12-07 20:10:45.741 INFO    SOUND: Driver reports 2 channels with mask 0x3
2020-12-07 20:10:45.741 INFO    SOUND: Using 2 channels at 48000 Hz
2020-12-07 20:10:45.741 INFO    SOUND: Channel layout: Headphones/Stereo
2020-12-07 20:10:49.088 INFO    INPUT: Device [TrackIR] created deviceId = -1
2020-12-07 20:10:50.984 ERROR   DX11BACKEND: DX device removed. Reason: 0x887A0007
2020-12-07 20:19:27.084 WARNING LOG: 88223 duplicate message(s) skipped.
2020-12-07 20:19:27.084 ERROR   DX11BACKEND: Failed to create shader resource view for dxgui/skins/skinme/images/mission_editor/static_me_question.png. Reason: The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action.

 

Can you check for an audio driver issue?

In your NVIDIA panel, what is the value of the "Maximm pre-rendered frames" parameter?

[nrlemo]

Flappie, currently the "Maximm pre-rendered frames" setting is set to "Use the 3d application settings". Although, i reloaded the drivers to a previous version 432.00 and no issues so far.

I dont have a trackir hardware. And i have an asus xonar DG sound card installed, its active but its not the currently used sound output.

 

Regarding the "dreaded "DXGI_ERROR_DEVICE_REMOVED" error".... is it happening to other users as well? any hints of its cause?

 

THANKS!

[Flappie]

You're welcome!

 

Yes, the "DXGI_ERROR_DEVICE_REMOVED" is probably the most seen error in this section of the forum. As I said, it means DirectX has work to do with the GPU, which doesn't respond in the expected timing. Unfortunately, DCS logs don't say much more about this.

 

If it happens to you again, please come back here.

[Glow]

Hi. I had similar error: DX device removed 0x887A0006

 

I found solution, looks like it's working fine:
https://docs.substance3d.com/spdoc/gpu-drivers-crash-with-long-computations-128745489.html

In short: GPU drivers will stop and get a kick from Windows and DCS will crash. I had like 50-60fps, but when to many textures or smoke and explosions, I get crash with no hang or any foreshadowing of evil forces involvement, not a hang, no fps drop, just a CTD.

 

Solution: Add to DWORD (32-bit) Values to Windows registry to alow Windows to wait for a driver (60-120 sec).

 

 Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers
    TdrDelay
    TdrDdiDelay

 

 Give both value of 60 (secunds decimal).

I'm testing this now in my scenarios and looks like is working.

Maybe would be a good thing to add this to DCS World updater? Windows updates will clean those values, so you have to remember to set those after any Win update.

Edited March 21, 2021 by Glow

[Flappie]

Hi @Glow. Thanks for your feedback. I've already helped someone using this tweak in the past, but this is a last resort measure in my opinion. Chances are it hides another issue. However, it's a good solution when nothing else works.

[Harley]

Having similar CTD, and reviving this old thread to use these tweaks. It's still an issue, or has resurfaced recently.

[silverdevil]

9 hours ago, Harley said:

Having similar CTD, and reviving this old thread to use these tweaks. It's still an issue, or has resurfaced recently.

hello, you replied to a nearly four year old post. you should start a new thread and post all your relevant logs. 

Edited January 31 by silverdevil

[Raven (Elysian Angel)]

9 hours ago, Harley said:

Having similar CTD

Not to be the bearer of ill news, but when I had a similar error message, the graphics card I was using at the time had started to die. It took over a year, but it did die and replacing it "fixed" that issue. Perhaps something to keep in mind.

 

25 minutes ago, silverdevil said:

you replied to a nearly four year old post. you should start a new thread and post all your relevant logs

Why? I for one am happy to see there are at least people who don't constantly make new things about stuff already discussed, bloating the forum even more than it already is. This thread here is as good a place as any (probably better even) to post, as long as the error message received is exactly the same.

[Harley]

9 hours ago, silverdevil said:

hello, you replied to a nearly four year old post. you should start a new thread and post all your relevant logs. 

There already multiple threads about this topic. I'm looking for more information from people that also have this issue.

[fagulha]

I had this issue with my old rig until late October when i built a new one. I was using a old GTX 1080ti with VR, now with the new rig i never had the issue again. My though at the time was that the GPU was years old and getting maxed out. I searched a lot about the issue and never find an focused answer.   

[silverdevil]

11 hours ago, Raven (Elysian Angel) said:

Why? I for one am happy to see there are at least people who don't constantly make new things about stuff already discussed, bloating the forum even more than it already is. This thread here is as good a place as any (probably better even) to post, as long as the error message received is exactly the same.

i was not trying to be mean or anything. users hopping on a topic and to say "me too" without any other empirical info is not exactly helpful to those of us trying to help. i personally go for the low reply numbers in threads. also if there is actually a solution to an OP, then they can say they fixed their issue by doing this. mark it solved. this helps by having a green solved checkbox.

2 hours ago, Harley said:

There already multiple threads about this topic. I'm looking for more information from people that also have this issue.

i understand and like i said, i am not try to be impolite. your issue may be totally different. without the appropriate logs that tell us more information. and more information, the better.

[Harley]

Ok. There are crash log entries, and this thread seems to be alive with the sound of music. Maybe someone can sift through these and tell me what area I need to look at. It appears that in one of those files, it shows an entry wawnting to reprocess the f-18 texture or something like that? I am not sure that is it, but it appears to be the last thing it tried to do before a stack of the very nearly same error message flooded the file. Can someone make sense of these? It always opens an AMD error reporting window about a driver timeout, and some folks have also showed a work-around to increase the timeout duration, and if someone sees that this is possibly where I should look, I'll try that. I get a little nervous about using regedit, because it's not really intuitive, and I'm not sure if I'll be able to undo some of the things that an impatient person can do there.

 

I wanna drop some bombs, man!

dcs.20250201-040316.crash dcs.20250201-040316.dmp dcs.20250201-040316.log dcs.20250201-040316.trk dxdiag.txt hash

[sleighzy]

3 hours ago, Harley said:

Ok. There are crash log entries, and this thread seems to be alive with the sound of music. Maybe someone can sift through these and tell me what area I need to look at. It appears that in one of those files, it shows an entry wawnting to reprocess the f-18 texture or something like that? I am not sure that is it, but it appears to be the last thing it tried to do before a stack of the very nearly same error message flooded the file. Can someone make sense of these? It always opens an AMD error reporting window about a driver timeout, and some folks have also showed a work-around to increase the timeout duration, and if someone sees that this is possibly where I should look, I'll try that. I get a little nervous about using regedit, because it's not really intuitive, and I'm not sure if I'll be able to undo some of the things that an impatient person can do there.

 

I wanna drop some bombs, man!

dcs.20250201-040316.crash 1.48 kB · 0 downloads dcs.20250201-040316.dmp 658.36 kB · 0 downloads dcs.20250201-040316.log 603.69 kB · 0 downloads dcs.20250201-040316.trk 308.36 kB · 0 downloads dxdiag.txt 90.67 kB · 0 downloads hash 32 B · 0 downloads

You've now posted this on somebody's else's post as well. I've responded there anyway. However you should raise your own post in case your issue is unrelated, e.g. you also have mods which could be a problem, or is overclocks...or your GPU is dying.

[Harley]

I figured it out, and it did involve replacing the GPU. Not because it was faulty, but because the way the Radeon VII measures temps at the junction. It was getting too hot under the demand of some of the newer scenery and throttling, causing the driver timeout. I'm on a 7800XT now, and it's rocking Baghdad amazingly. I even turned up many of the settings that were causing performance issues on my prior card. Thank you for trying! The GPU is still fine, it just can't do SAM, and perhaps some of the other newer things theyre doing now, and I think we're going to be required to enable that and/or resize BAR in BIOS from here on out. This card is definitely a leap in improvement from 7 years ago.

I've been testing and tuning some of the settings, and it seems the generational gap is much more apparent than I had initially thought. It has been a while since I've upgraded the GPU, and much has happened since the Radeon vii. The 7000 series really is doing some pretty powerful things as compared to the generation I've been using.

I still consider myself pretty fortunate to not have needed to upgrade the Vega 64/vii for some years. Those were great cards. I hope this one does as well. It would be good to have finally found a sweet spot and can settle in for a while.

Edited February 23 by Harley