- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
0x887A006: DXGI_ERROR_DEVICE_HUNG with shadows enabled in Shadow of the Tomb Raider DX12 multi-gpu
Having solved my previous Shadow of the Tomb Raider problem, I upgraded to a multi-gpu setup to drive a 1440p/144hz display.
Unfortunately it seems that I have to set Shadow Quality to 'Off' to avoid the game crashing to the desktop with DXGI_ERROR_DEVICE_HUNG when I try to continue the game or run the benchmark via Option -> Display and Graphics (though it does seem to occasionally work).
I went ahead and moved up to Windows 10 build 1809. I did uninstall the recent KB44282887 due to reports of degraded performance.
System:
i7-4790K 4GHZ
16GB Corsair Vengeance RAM (4x4, purchased as a kit)
Asus Z97 Pro WiFi ac Motherboard (Bios 5303)
2x PowerColor Red Dragon Vega 56
Samsung C27HG70 at 1440p
EVGA SuperNOVA 1200 watt Power Supply
Windows 10 build 1809
I'm on a clean install of Adrenalin 19.3.1.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So it turns out this is just a problem the developer didn't want to fix and the drivers are innocent.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think this is where it goes south (log file excerpt):
20:52:34:963 (00008400) > [D3D] cdc::PCDX12DeviceManager::GatherGPUTimes: nodeResource.m_pTimingReadback->Map(0, &range, (void**)&pTimingData) failed with HRESULT 0x887a0005
20:52:34:963 (00008400) > [D3D] ERROR! Device removed detected (0x887A0006: DXGI_ERROR_DEVICE_HUNG)
20:52:37:040 (00008400) > [D3D] cdc::PCDX12GraphicsCommandListPool::GetCommandList: pDevice->CreateCommandList(1 << m_node, m_CLType, *ppAllocator, nullptr, __uuidof(**(ppCL)), IID_PPV_ARGS_Helper(ppCL)) failed with HRESULT 0x887a0005
20:52:37:041 (00008400) > [Crash] Memory statistics:
20:52:37:041 (00008400) > [Crash] Total RAM = 15.9 GB (16324 MB)
20:52:37:041 (00008400) > [Crash] Avail RAM = 8.9 GB (9078 MB)
20:52:37:041 (00008400) > [Crash] Total virtual memory = 131072.0 GB (134217727 MB)
20:52:37:041 (00008400) > [Crash] Avail virtual memory = 131056.4 GB (134201742 MB)
20:52:37:041 (00008400) > [Crash] Unhandled exception at address 0x0000000047218957 (code: 0xc0000005): "Access violation"
20:52:37:285 (00008400) > [Crash] Created minidump at "C:\Users\8-fingered\Documents\Shadow of the Tomb Raider\Shadow of the Tomb Raider-v1.0 build 279.0_64 2019-03-12-20-52-37.mdmp".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same exact issue here. I didn't have this issue with my 290X xfire setup, but I do with my 2x Vega 64 setup. I'm on a clean install of 19.3.3, Win10 1809.
10:01:46:154 (00002276) > [D3D] cdc::PCDX12DeviceManager::GatherGPUTimes: nodeResource.m_pTimingReadback->Map(0, &range, (void**)&pTimingData) failed with HRESULT 0x887a0005
10:01:46:154 (00002276) > [D3D] ERROR! Device removed detected (0x887A0006: DXGI_ERROR_DEVICE_HUNG)
10:01:57:002 (00001252) > [DXGI] Present failed with HRESULT 0x887a0001
10:01:57:002 (00002276) > [D3D] cdc::PCDX12QueryHeap::BeginReadback: m_pReadbackResource[GPULengthQuery::s_nFrameIndexRead]->Map(0, &range, (void**)&m_pTimestamps) failed with HRESULT 0x887a0005
10:01:57:003 (00002276) > [Crash] Memory statistics:
10:01:57:003 (00002276) > [Crash] Total RAM = 15.9 GB (16315 MB)
10:01:57:003 (00002276) > [Crash] Avail RAM = 9.8 GB (10002 MB)
10:01:57:003 (00002276) > [Crash] Total virtual memory = 131072.0 GB (134217727 MB)
10:01:57:003 (00002276) > [Crash] Avail virtual memory = 131055.2 GB (134200554 MB)
10:01:57:003 (00002276) > [Crash] Unhandled exception at address 0x0000000049169e9f (code: 0xc0000005): "Access violation"
10:01:57:232 (00002276) > [Crash] Created minidump at "C:\Users\OVerLoRDI\Documents\Shadow of the Tomb Raider\Shadow of the Tomb Raider-v1.0 build 280.0_64 2019-03-22-10-01-57.mdmp".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What driver version is your dual 290x setup using?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Its been since earlier this year before I sold of my 290x setup, so it would have been 19.2 or 19.3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Have a report that nothing later than 18.9.1 was working a dual 290x setup.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same problem with Radeon VII x2
Without shadow and without TAA SMAA, Game don't crash.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm getting nowhere with AMD or Square Enix. We need more reports. If you haven't already opened tickets, go here and do so:
Don't let them blow you off. Insist they pass along the info to the developers / driver maintainers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I did both, submitted feedback via the AMD driver feedback system. No response there.
With Square-Enix they replied and told me to open a ticket with Microsoft among other things, their response is contradictory.
"We apologize for the inconvenience. However, error "0x887a0006:dxgi_error_device_hung" is a Windows-generated error code that indicates the application's device failed due to badly formed commands sent by the application. This is a design-time issue that should be investigated and fixed.
Unfortunately, as error "0x887a0006:dxgi_error_device_hung" is a Windows-generated error code, this would have to be resolved by Microsoft. As Windows is managed by Microsoft, the SQUARE ENIX Support Center is unable to assist. Please contact Microsoft Support for further assistance by clicking the following URL: https://support.microsoft.com/en-us"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have the same cpu (4790k) but one RX 580 and I play STTR normally... however you said 'multi-gpu' then Maybe the bug be the CrossFire
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's not CrossFire, it's mGPU via DX12. You're correct in that it only happens when utilizing multiple GPUs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm having this issue with a single Vega 56.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What Windows build are you on (run winver from cmdline)?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The new Driver was released
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Doesn't resolve the issue for me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same here. On 19.4.1 driver with SOTTR build 286.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Still no bueno.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What is the problem ? For me SOTTR run smooth and Perfect...
'address 0x0000000047218957 (code: 0xc0000005): "Access violation" ' --> only a Game Bug (maybe my game version be different - 1.0.237.6 17th Nov.18)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can run it just fine also with only one GPU enabled...but that can't drive a 1440p/144hz monitor at a high enough frame rate to justify the 144hz feature.
I think Nvidia did issue a driver fix that sounds like it might be related:
"Shadow of the Tomb Raider: Fixes occasional application crash in DirectX 12 mode"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I wonder if ULPS could be causing this? If you try it, make sure to disable on both cards. Just a thought.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nope. Disabled ULPS as suggested, rebooted and same issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nope. Made sure to get both entries.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Still broken with patch to SOTTR build 291.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
19.4.3 drivers don't help either. Still crashes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Still broken with patch to SOTTR build 292. More reports of others with this problem:
I think Nvidia issued another driver hotfix to deal with broken mGPU with the last couple game builds. AMD? Help us out?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, I've had the same error "DXGI Error" multiple times in Anthem with 19.4.3. Hope they will solve it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So Nixxes is now saying action is needed from AMD to get this fixed:
Everybody with this problem please open a ticket:
...and file a report against the drivers:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Opened a ticket
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same here, also filed new report against the drivers, made sure to include the link to the Nixxes statement and quoted it.
Any AMD folks out there reading this that can help get this info to the driver maintainers and help get them in contact with the Nixxes devs?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same issue with 19.5.1. I have a ticket opened with AMD and provided video of the issue as well as lots of system info.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Reportedly escalated to the driver team.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same here. Crossing my fingers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Got a new monitor in, was wanting to test frame rates, so I set Shadow Quality to 'Off', but now the benchmark exits (or silently crashes) to desktop when it finishes instead of showing a summary screen with the results. Found this in the log file:
17:51:57:588 (00008788) > [Crash] Unhandled exception at address 0x000000004c19cb44 (code: 0xc0000005): "Access violation"
Seems to be an issue with build 292:
https://steamcommunity.com/app/750920/discussions/0/1680315447988879470/?ctp=8
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Backing off to build 286 gets the benchmark working. Can get up to 120fps consistently. Shadow Quality isn't that expensive according to the performance tuning guide, so it should be a good experience if we ever get a fix.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
19.5.2 is out, but this issue didn't even make the 'Known Issues' list in the release notes, so I presume 19.5.2 is still broken (will confirm tonight).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
19.5.2 does not help. Please do file reports against it though.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same issue for me, hopefully this can be fixed soon. I get way lower FPS playing on DX11... almost unplayable
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
19.6.1 is out, again, no mention of the SOTTR Vega mGPU problem in the release notes as even a known issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
...and it's still not working. Everybody please once again report the issue against 19.6.1.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
19.6.2 is out, again, no mention of the SOTTR Vega mGPU problem in the release notes as even a known issue......and it's still not working. Everybody please once again report the issue against 19.6.2..