DirectX Error "GetDeviceREmovedReason"

[Krethys]

DirectX function "GetDeviceRemovedReason" failed with DXGI_ERROR_DEVICE_HUNG {The GPU will not respond to more commands"}. GPU: "NVIDIA GeForce RTX 3090", Driver:52698. This error is usually caused by the graphics driver crashing; try installing the latest drivers.

------------------
System Information
------------------
Time of this report: 11/25/2022, 23:56:43
Machine name: KRETHYS
Operating System: Windows 11 Pro 64-bit (10.0, Build 22623) (22621.ni_release.220506-1250)
Language: English (Regional Setting: English)
System Manufacturer: Micro-Star International Co., Ltd.
System Model: MS-7C35
BIOS: 1.J2 (type: UEFI)
Processor: AMD Ryzen 9 5900X 12-Core Processor (24 CPUs), ~3.7GHz
Memory: 32768MB RAM
Available OS Memory: 32690MB RAM
Page File: 20298MB used, 25702MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 96 DPI (100 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, no HDCP
Microsoft Graphics Hybrid: Not Supported
DirectX Database Version: 1.4.3
DxDiag Version: 10.00.22621.0001 64bit Unicode


Anyone else experiencing similar issues on latest NVIDIA driver?

[ENDWALKER]

Same here

[Krethys]

Автор сообщения: ENDWALKER

Same here

So I had issues on Warzone DMZ as well. I decided to go through the logs and found that Nahimic was causing me issues as well as MSI Afterburner. I disabled my OC settings unfortunately and uninstalled Nahimic and it resolved it so far for me. If you'd like, you can post your logs here and I can go through them to help out where I can

[VillrJester]

Автор сообщения: Krethys

Автор сообщения: ENDWALKER

Same here

So I had issues on Warzone DMZ as well. I decided to go through the logs and found that Nahimic was causing me issues as well as MSI Afterburner. I disabled my OC settings unfortunately and uninstalled Nahimic and it resolved it so far for me. If you'd like, you can post your logs here and I can go through them to help out where I can

Hey, I also have the same issues as you mentioned, getting the DXGI_ERROR_DEVICE_HUNG {The GPU will not respond to more commands"}. GPU: "NVIDIA GeForce RTX 3080" and I also have issues with Warzone 2.0. My audio would cut out entirely and I would hear nothing but a loud buzzing noise for around 1-2 minutes and then it would crash. This same thing happens to other Directx 12 games, but it doesn't happen to Directx 11 games. Do you know where I can get the logs for them?

[Magamedkin]

+

[fatlinesofchang]

Yeah been getting the same issue, will try disabling MSI to see if that helps. Been trying to sort this out since getting new PC.

[fatlinesofchang]

Автор сообщения: cathartic

Yeah been getting the same issue, will try disabling MSI to see if that helps. Been trying to sort this out since getting new PC.

Yeah hasn't crashed since turning off MSI which is odd.

[Boom Erang]

So totally understand. I installed MSI afterburner to see my temps and alter the fan curve.
The machine wouldn't even boot. (fan error which morphed into No boot disk and crap). I had to work some serious magic. msi uninstalled and thrown off the highest cliff... Good to go. Never look back. It was likely all my fault perhaps. It's not an MSI board.

[Krethys]

MSI Afterburner has def been known to cause issues but I would not limit it to that. There are a few things to check, precisely, I ran a DxDiag and looked for my Windows Error Reporting logs listed from WER0 down to WER#. While some of the errors are not verbose enough for troubleshooting, I'd guess that some of them will lead you to some running software and affiliated DLLs that may play culprit to crashes. I ran my OC settings again and do experience some random sequences of freezing but it resolves quickly and the game continues back at max FPS. Which is way better than before lol.

Would also check your 'reliability monitor' within windows for more avenues of dissecting the issue and compare this to event viewer at time of event occurrence. For easier parsing, you can always clear logs and replicate issue or just know the cutoff time frame and go from there. It's most likely a service/overlay/driver issue if we're speaking of common occurrences.
Feel free to post findings, log snippets, etc., and I can help out the best I can.

[VillrJester]

Автор сообщения: cathartic

Автор сообщения: cathartic

Yeah been getting the same issue, will try disabling MSI to see if that helps. Been trying to sort this out since getting new PC.

Yeah hasn't crashed since turning off MSI which is odd.

Do you know if there are any other programs besides MSI and Razor causing the problems? I don't have MSI afterburner nor any razor programs.

[VillrJester]

Автор сообщения: Krethys

MSI Afterburner has def been known to cause issues but I would not limit it to that. There are a few things to check, precisely, I ran a DxDiag and looked for my Windows Error Reporting logs listed from WER0 down to WER#. While some of the errors are not verbose enough for troubleshooting, I'd guess that some of them will lead you to some running software and affiliated DLLs that may play culprit to crashes. I ran my OC settings again and do experience some random sequences of freezing but it resolves quickly and the game continues back at max FPS. Which is way better than before lol.

Would also check your 'reliability monitor' within windows for more avenues of dissecting the issue and compare this to event viewer at time of event occurrence. For easier parsing, you can always clear logs and replicate issue or just know the cutoff time frame and go from there. It's most likely a service/overlay/driver issue if we're speaking of common occurrences.
Feel free to post findings, log snippets, etc., and I can help out the best I can.

Hello, this is what I found so far. In my Battlefield 2042 Crash Dumps folder, this is what I saw:

*** WARNING: Unable to verify timestamp for BF2042.exe

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1171

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 8620

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 358

Key : Analysis.Init.Elapsed.mSec
Value: 26985

Key : Analysis.Memory.CommitPeak.Mb
Value: 99

Key : Timeline.Process.Start.DeltaSec
Value: 1240

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1

Key : WER.Process.Version
Value: 10.0.19041.1415


FILE_IN_CAB: CrashDump_2022.12.05_10.08.29.960.mdmp

COMMENT: Frostbite MiniDump. Address: 7ffd7152cd29 (In Windbg type: .ecxr)
[EOF]

NTGLOBALFLAG: 0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

CONTEXT: (.ecxr)
rax=0000000000000000 rbx=0000000051885100 rcx=0000000000000002
rdx=00007ffd7338eb26 rsi=00000000887a0006 rdi=000000005188afc0
rip=00007ffd7152cd29 rsp=000000004fe44b80 rbp=000000004fe44d60
r8=000000000018000c r9=000000108983e080 r10=0000000000000000
r11=0000000000000000 r12=00000000000003ff r13=00000000518e4500
r14=0000000051883190 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000206
KERNELBASE!RaiseException+0x69:
00007ffd`7152cd29 0f1f440000 nop dword ptr [rax+rax]
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffd7152cd29 (KERNELBASE!RaiseException+0x0000000000000069)
ExceptionCode: 887a0006
ExceptionFlags: 00000000
NumberParameters: 0

PROCESS_NAME: BF2042.exe

ERROR_CODE: (NTSTATUS) 0x887a0006 - The GPU will not respond to more commands, most likely because of an invalid command passed by the calling application.

EXCEPTION_CODE_STR: 887a0006

STACK_TEXT:
00000000`4fe44b80 00000001`4339823c : 00000000`51883190 00000000`51883190 00000000`00000006 00000000`00000003 : KERNELBASE!RaiseException+0x69
00000000`4fe44c60 00000000`51883190 : 00000000`51883190 00000000`00000006 00000000`00000003 00000000`00000001 : BF2042+0x339823c
00000000`4fe44c68 00000000`51883190 : 00000000`00000006 00000000`00000003 00000000`00000001 00010000`01000100 : 0x51883190
00000000`4fe44c70 00000000`00000006 : 00000000`00000003 00000000`00000001 00010000`01000100 00000000`36e70640 : 0x51883190
00000000`4fe44c78 00000000`00000003 : 00000000`00000001 00010000`01000100 00000000`36e70640 80000044`00000044 : 0x6
00000000`4fe44c80 00000000`00000001 : 00010000`01000100 00000000`36e70640 80000044`00000044 00000000`2c033940 : 0x3
00000000`4fe44c88 00010000`01000100 : 00000000`36e70640 80000044`00000044 00000000`2c033940 00000000`36e70640 : 0x1
00000000`4fe44c90 00000000`36e70640 : 80000044`00000044 00000000`2c033940 00000000`36e70640 80000044`00000044 : 0x00010000`01000100
00000000`4fe44c98 80000044`00000044 : 00000000`2c033940 00000000`36e70640 80000044`00000044 00000000`2c033940 : 0x36e70640
00000000`4fe44ca0 00000000`2c033940 : 00000000`36e70640 80000044`00000044 00000000`2c033940 00000000`00000000 : 0x80000044`00000044
00000000`4fe44ca8 00000000`36e70640 : 80000044`00000044 00000000`2c033940 00000000`00000000 00000000`00000000 : 0x2c033940
00000000`4fe44cb0 80000044`00000044 : 00000000`2c033940 00000000`00000000 00000000`00000000 00000000`9107f200 : 0x36e70640
00000000`4fe44cb8 00000000`2c033940 : 00000000`00000000 00000000`00000000 00000000`9107f200 00001098`00002098 : 0x80000044`00000044
00000000`4fe44cc0 00000000`00000000 : 00000000`00000000 00000000`9107f200 00001098`00002098 00000010`00000080 : 0x2c033940


SYMBOL_NAME: bf2042+339823c

MODULE_NAME: BF2042

IMAGE_NAME: BF2042.exe

STACK_COMMAND: ~31s; .ecxr ; kb

FAILURE_BUCKET_ID: APPLICATION_FAULT_887a0006_BF2042.exe!Unknown

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 1.0.248.19364

FAILURE_ID_HASH: {14700393-1812-a0ef-8977-ef4dc7bc216b}

Followup: MachineOwner
---------

I followed your advice and actually found something very curious in Windows Event Viewer. I found that the crashing always involves the same 2 errors. The first error was:

Faulting application name: AUDIODG.EXE, version: 10.0.19041.1865, time stamp: 0x61fdcc50
Faulting module name: NvAudioEffects.dll, version: 1.0.1.0, time stamp: 0x615ff9be
Exception code: 0xc0000005
Fault offset: 0x000000000001d360
Faulting process id: 0x1ff4
Faulting application start time: 0x01d9079ff92c305f
Faulting application path: C:\WINDOWS\system32\AUDIODG.EXE
Faulting module path: c:\Windows\System32\logi_denoiser\NvAudioEffects.dll
Report Id: 587eef2e-efa5-4aaa-8475-544b3d5bf0cf
Faulting package full name:
Faulting package-relative application ID:

After that, it gets followed by this error after roughly a minute or 2:

The program svchost.exe version 10.0.19041.1806 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: dc0
Start Time: 01d9079448052940
Termination Time: 4294967295
Application Path: C:\Windows\System32\svchost.exe
Report Id: daf31fc7-d135-4710-8f6f-6cb2223f97d4
Faulting package full name:
Faulting package-relative application ID:
Hang type: Cross-process

[VillrJester]

Автор сообщения: Krethys

MSI Afterburner has def been known to cause issues but I would not limit it to that. There are a few things to check, precisely, I ran a DxDiag and looked for my Windows Error Reporting logs listed from WER0 down to WER#. While some of the errors are not verbose enough for troubleshooting, I'd guess that some of them will lead you to some running software and affiliated DLLs that may play culprit to crashes. I ran my OC settings again and do experience some random sequences of freezing but it resolves quickly and the game continues back at max FPS. Which is way better than before lol.

Would also check your 'reliability monitor' within windows for more avenues of dissecting the issue and compare this to event viewer at time of event occurrence. For easier parsing, you can always clear logs and replicate issue or just know the cutoff time frame and go from there. It's most likely a service/overlay/driver issue if we're speaking of common occurrences.
Feel free to post findings, log snippets, etc., and I can help out the best I can.

My God, I found out why I was crashing, it turns out that Nvidia Broadcast was the reason for my crashes. I had to go to C:\Windows\System32\logi_denoiser and delete the logi_denoiser folder to uninstall Nvidia Broadcast. Now I can play without crashing.

[Krethys]

Interesting, I haven't played in a while and recently crashed again. I also use broadcast, I will check this one out myself. According to your logs, it does look like the dll for broadcast was causing issues. Hope it still remains smooth as of writing this! I got to get some rest myself but will look soon. Happy Holidays to you as well!

[VillrJester]

Автор сообщения: Krethys

Interesting, I haven't played in a while and recently crashed again. I also use broadcast, I will check this one out myself. According to your logs, it does look like the dll for broadcast was causing issues. Hope it still remains smooth as of writing this! I got to get some rest myself but will look soon. Happy Holidays to you as well!

Hey there, an update about what happened so far. I can confirm that deleting logi_denoiser to get rid of Nvidia Broadcast fixed the issue for me. I'm able to play any directx 12 game without crashing, including BF2042 for hours per session. Happy Holidays to you too!

[Skymarc]

Try setting every graphic setting to ultra except terrain quality, leave that on high. My gpu is undervolted with msi afterburner and all my peripherals are razer. Seems like people with razer peps and using afterburner tend to have this problem more commonly.

[zzz]

always crash in the middle of the match.........

i got a 3080 game runs 250+ fps and this hasn't been fixed.