[SOLVED] Computer randomly "shuts down" or doesnt boot but still powered on. dwm.exe faulting application.

Aug 5, 2021
5
0
10
Bought a new pc about a month ago and a few weeks in it started randomly shutting down. Didnt matter if I was playing a game or just staring at my desktop. Sometimes it wouldnt happen for an entire day, other times it would happen within 10 minutes of being on. The monitor would turn off and give no signal but all the lights in my rig were still on and my gpu fans seemed to be running pretty fast. Originally in my dmp file it was telling me this

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffd00fb9d9b460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80631b36bd8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5d5c294bb8d17217\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3203

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 19740

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

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

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

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


BUGCHECK_CODE: 116

BUGCHECK_P1: ffffd00fb9d9b460

BUGCHECK_P2: fffff80631b36bd8

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffd00fb9d9b460
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffbc081bee92d8 fffff8062bbc1cae : 0000000000000116 ffffd00fb9d9b460 fffff80631b36bd8 ffffffffc000009a : nt!KeBugCheckEx
ffffbc081bee92e0 fffff8062bb724d4 : fffff80631b36bd8 ffffd00fbb784010 0000000000002000 ffffd00fbb7840d0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffbc081bee9320 fffff8062bb6b00f : ffffd00fbb778000 0000000001000000 0000000000000002 0000000000000002 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffffbc081bee9350 fffff8062bbc13d5 : 0000000000000100 ffffd00fbb778a58 00000000b1e9dc50 ffffd00fb9581060 : dxgkrnl!DXGADAPTER::Reset+0x4df
ffffbc081bee93d0 fffff8062bbc1547 : fffff80612324440 ffffd00fc643d490 0000000000000000 0000000000000300 : dxgkrnl!TdrResetFromTimeout+0x15
ffffbc081bee9400 fffff806118b8515 : ffffd00fc3193600 fffff8062bbc1520 ffffd00fb1e9dc50 ffffd00f00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffbc081bee9430 fffff80611955855 : ffffd00fc3193600 0000000000000080 ffffd00fb1eab040 fffff8061180a200 : nt!ExpWorkerThread+0x105
ffffbc081bee94d0 fffff806119fe788 : ffffc0017b8cc180 ffffd00fc3193600 fffff80611955800 000000009b610a98 : nt!PspSystemThreadStartup+0x55
ffffbc081bee9520 0000000000000000 : ffffbc081beea000 ffffbc081bee3000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+dc6bd8

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

I had tried uninstalling and reinstalling gpu drivers with ddu/safe mode, system restore, buying a new display port cable, re seating my gpu (which was hanging a bit and seems to have slightly bent but i bought as support bracket for that), windows update, updating xbox controller and none of those things seemed to work. 2 days ago I updated my bios and I thought that had fixed the issue. But now I'm having the exact same issue, with the addition of sometimes when i turn on my computer it simply wont boot. Display is off, but all lights and fans in pc are running. I turned off fast startup and it still happened. In event viewer though instead of having the same error I had prior to updating my bios I get this in event viewer,

Faulting application name: dwm.exe, version: 10.0.19041.746, time stamp: 0x6be51595
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1151, time stamp: 0x891df6d3
Exception code: 0xe0464645
Fault offset: 0x000000000010bd3e
Faulting process id: 0x1010
Faulting application start time: 0x01d78a74cdf93210
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: bc4d4136-67e5-44d0-8682-3d1fdf961818
Faulting package full name:
Faulting package-relative application ID:

There's 8 entries in event viewer like this that show up whenever this issue occurs, each with a different faulting process id and time. I had run stress tests (only for 5 minutes) when I was getting the TDR failures and I didnt seem to have an issue. I hope my explanation wasn't too bloated or missing much but this issue is driving me insane. Basically have a half assed computer cause I never know when itll just shut down.

CPU: Intel® Core™ Processor i5-11600KF 6/12 3.90GHz [Turbo 4.9GHz] 12MB Cache LGA1200
FAN: CyberpowerPC MasterLiquid Lite 360mm ARGB CPU Liquid Cooler with Dual Chamber Pump & Copper Cold Plate
HDD: 1TB GIGABYTE AORUS (PCIe Gen4) NVMe M.2 SSD
MOTHERBOARD: MSI MPG Z590 GAMING PLUS ATX, ARGB, 2.5GbE LAN, 2 PCIe x16, 2 PCIe x1, 6 SATA3, 3x M.2 SATA/PCIe
MEMORY: 16GB (8GBx2) DDR4/3200MHz Dual Channel Memory
PSU: 1,000 Watts - Standard 80 Plus Gold Power Supply
GPU: GeForce RTX™ 3080 10GB GDDR6X (Ampere)
 
Solution
have you found any solution so far? I have pretty much the same problem with same symbol name, module name, everything even the failure ID hash is the same. My pc is crashing when playing games and running 3dmark, passes furmark and aida64 stress test with ease. I’m running an i5-11400, 16gb of dual channel ram, a 3060 and a cougar GX-S650 PSU.
Welp my computer just rebooted on its own so it seems nothing has solved the issue. Info from my memory dmp

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffd302f69e5010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8079e4a6bd8, The pointer into responsible device driver module...
Bought a new pc about a month ago and a few weeks in it started randomly shutting down. Didnt matter if I was playing a game or just staring at my desktop. Sometimes it wouldnt happen for an entire day, other times it would happen within 10 minutes of being on. The monitor would turn off and give no signal but all the lights in my rig were still on and my gpu fans seemed to be running pretty fast. Originally in my dmp file it was telling me this

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffd00fb9d9b460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80631b36bd8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5d5c294bb8d17217\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3203

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 19740

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

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

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

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


BUGCHECK_CODE: 116

BUGCHECK_P1: ffffd00fb9d9b460

BUGCHECK_P2: fffff80631b36bd8

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffd00fb9d9b460
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffbc081bee92d8 fffff8062bbc1cae : 0000000000000116 ffffd00fb9d9b460 fffff80631b36bd8 ffffffffc000009a : nt!KeBugCheckEx
ffffbc081bee92e0 fffff8062bb724d4 : fffff80631b36bd8 ffffd00fbb784010 0000000000002000 ffffd00fbb7840d0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffbc081bee9320 fffff8062bb6b00f : ffffd00fbb778000 0000000001000000 0000000000000002 0000000000000002 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffffbc081bee9350 fffff8062bbc13d5 : 0000000000000100 ffffd00fbb778a58 00000000b1e9dc50 ffffd00fb9581060 : dxgkrnl!DXGADAPTER::Reset+0x4df
ffffbc081bee93d0 fffff8062bbc1547 : fffff80612324440 ffffd00fc643d490 0000000000000000 0000000000000300 : dxgkrnl!TdrResetFromTimeout+0x15
ffffbc081bee9400 fffff806118b8515 : ffffd00fc3193600 fffff8062bbc1520 ffffd00fb1e9dc50 ffffd00f00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffbc081bee9430 fffff80611955855 : ffffd00fc3193600 0000000000000080 ffffd00fb1eab040 fffff8061180a200 : nt!ExpWorkerThread+0x105
ffffbc081bee94d0 fffff806119fe788 : ffffc0017b8cc180 ffffd00fc3193600 fffff80611955800 000000009b610a98 : nt!PspSystemThreadStartup+0x55
ffffbc081bee9520 0000000000000000 : ffffbc081beea000 ffffbc081bee3000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+dc6bd8

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

I had tried uninstalling and reinstalling gpu drivers with ddu/safe mode, system restore, buying a new display port cable, re seating my gpu (which was hanging a bit and seems to have slightly bent but i bought as support bracket for that), windows update, updating xbox controller and none of those things seemed to work. 2 days ago I updated my bios and I thought that had fixed the issue. But now I'm having the exact same issue, with the addition of sometimes when i turn on my computer it simply wont boot. Display is off, but all lights and fans in pc are running. I turned off fast startup and it still happened. In event viewer though instead of having the same error I had prior to updating my bios I get this in event viewer,

Faulting application name: dwm.exe, version: 10.0.19041.746, time stamp: 0x6be51595
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1151, time stamp: 0x891df6d3
Exception code: 0xe0464645
Fault offset: 0x000000000010bd3e
Faulting process id: 0x1010
Faulting application start time: 0x01d78a74cdf93210
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: bc4d4136-67e5-44d0-8682-3d1fdf961818
Faulting package full name:
Faulting package-relative application ID:

There's 8 entries in event viewer like this that show up whenever this issue occurs, each with a different faulting process id and time. I had run stress tests (only for 5 minutes) when I was getting the TDR failures and I didnt seem to have an issue. I hope my explanation wasn't too bloated or missing much but this issue is driving me insane. Basically have a half assed computer cause I never know when itll just shut down.

CPU: Intel® Core™ Processor i5-11600KF 6/12 3.90GHz [Turbo 4.9GHz] 12MB Cache LGA1200
FAN: CyberpowerPC MasterLiquid Lite 360mm ARGB CPU Liquid Cooler with Dual Chamber Pump & Copper Cold Plate
HDD: 1TB GIGABYTE AORUS (PCIe Gen4) NVMe M.2 SSD
MOTHERBOARD: MSI MPG Z590 GAMING PLUS ATX, ARGB, 2.5GbE LAN, 2 PCIe x16, 2 PCIe x1, 6 SATA3, 3x M.2 SATA/PCIe
MEMORY: 16GB (8GBx2) DDR4/3200MHz Dual Channel Memory
PSU: 1,000 Watts - Standard 80 Plus Gold Power Supply
GPU: GeForce RTX™ 3080 10GB GDDR6X (Ampere)
Your bios isn't set properly sounds like.
Have you tried to set dual channel mode if you have to sticks of ram, have you made sure the cpu turbo is adjusted right on you motherboard try disabling, reinstall your motherboard drivers for windows not the bios
 
Aug 5, 2021
5
0
10
Your bios isn't set properly sounds like.
Have you tried to set dual channel mode if you have to sticks of ram, have you made sure the cpu turbo is adjusted right on you motherboard try disabling, reinstall your motherboard drivers for windows not the bios
Admittedly I didnt/dont know how to do any of that. Or rather I dont know where I would find those things
 
Aug 5, 2021
5
0
10
Welp my computer just rebooted on its own so it seems nothing has solved the issue. Info from my memory dmp

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffd302f69e5010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8079e4a6bd8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5d5c294bb8d17217\nvlddmkm.sys, Win32 error 0n2

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2687

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 3785

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

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

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

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


BUGCHECK_CODE: 116

BUGCHECK_P1: ffffd302f69e5010

BUGCHECK_P2: fffff8079e4a6bd8

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffd302f69e5010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffe382a076f2d8 fffff8079ad01cae : 0000000000000116 ffffd302f69e5010 fffff8079e4a6bd8 ffffffffc000009a : nt!KeBugCheckEx
ffffe382a076f2e0 fffff8079acb24d4 : fffff8079e4a6bd8 ffffd302ee9a4860 0000000000002000 ffffd302ee9a4920 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffe382a076f320 fffff8079acab00f : ffffd302ee9ab000 0000000001000000 0000000000000002 0000000000000002 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffffe382a076f350 fffff8079ad013d5 : 0000000000000100 ffffd302ee9aba58 00000000e509ccd0 fffff80783524440 : dxgkrnl!DXGADAPTER::Reset+0x4df
ffffe382a076f3d0 fffff8079ad01547 : fffff80783524440 ffffd302ec55a610 0000000000000000 0000000000000100 : dxgkrnl!TdrResetFromTimeout+0x15
ffffe382a076f400 fffff80782ab8515 : ffffd302ec407240 fffff8079ad01520 ffffd302e509ccd0 ffffd30200000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffe382a076f430 fffff80782b55855 : ffffd302ec407240 0000000000000080 ffffd302e50b8040 001fa4efbd9bbfff : nt!ExpWorkerThread+0x105
ffffe382a076f4d0 fffff80782bfe788 : ffffab8109ccc180 ffffd302ec407240 fffff80782b55800 329f329e329d329c : nt!PspSystemThreadStartup+0x55
ffffe382a076f520 0000000000000000 : ffffe382a0770000 ffffe382a0769000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+dc6bd8

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

Followup: MachineOwner
 
Welp my computer just rebooted on its own so it seems nothing has solved the issue. Info from my memory dmp

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffd302f69e5010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8079e4a6bd8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5d5c294bb8d17217\nvlddmkm.sys, Win32 error 0n2

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2687

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 3785

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

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

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

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


BUGCHECK_CODE: 116

BUGCHECK_P1: ffffd302f69e5010

BUGCHECK_P2: fffff8079e4a6bd8

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffd302f69e5010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffe382a076f2d8 fffff8079ad01cae : 0000000000000116 ffffd302f69e5010 fffff8079e4a6bd8 ffffffffc000009a : nt!KeBugCheckEx
ffffe382a076f2e0 fffff8079acb24d4 : fffff8079e4a6bd8 ffffd302ee9a4860 0000000000002000 ffffd302ee9a4920 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffe382a076f320 fffff8079acab00f : ffffd302ee9ab000 0000000001000000 0000000000000002 0000000000000002 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffffe382a076f350 fffff8079ad013d5 : 0000000000000100 ffffd302ee9aba58 00000000e509ccd0 fffff80783524440 : dxgkrnl!DXGADAPTER::Reset+0x4df
ffffe382a076f3d0 fffff8079ad01547 : fffff80783524440 ffffd302ec55a610 0000000000000000 0000000000000100 : dxgkrnl!TdrResetFromTimeout+0x15
ffffe382a076f400 fffff80782ab8515 : ffffd302ec407240 fffff8079ad01520 ffffd302e509ccd0 ffffd30200000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffe382a076f430 fffff80782b55855 : ffffd302ec407240 0000000000000080 ffffd302e50b8040 001fa4efbd9bbfff : nt!ExpWorkerThread+0x105
ffffe382a076f4d0 fffff80782bfe788 : ffffab8109ccc180 ffffd302ec407240 fffff80782b55800 329f329e329d329c : nt!PspSystemThreadStartup+0x55
ffffe382a076f520 0000000000000000 : ffffe382a0770000 ffffe382a0769000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+dc6bd8

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

Followup: MachineOwner
This honestly sends like a you need to be in front of the machine to help with type problem. I don't think I would be able to help online here in sorry. I hope someone else can solve this remotely for you
 
Aug 7, 2021
3
0
10
Welp my computer just rebooted on its own so it seems nothing has solved the issue. Info from my memory dmp

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffd302f69e5010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8079e4a6bd8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5d5c294bb8d17217\nvlddmkm.sys, Win32 error 0n2

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2687

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 3785

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

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

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

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


BUGCHECK_CODE: 116

BUGCHECK_P1: ffffd302f69e5010

BUGCHECK_P2: fffff8079e4a6bd8

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffd302f69e5010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffe382a076f2d8 fffff8079ad01cae : 0000000000000116 ffffd302f69e5010 fffff8079e4a6bd8 ffffffffc000009a : nt!KeBugCheckEx
ffffe382a076f2e0 fffff8079acb24d4 : fffff8079e4a6bd8 ffffd302ee9a4860 0000000000002000 ffffd302ee9a4920 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffe382a076f320 fffff8079acab00f : ffffd302ee9ab000 0000000001000000 0000000000000002 0000000000000002 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffffe382a076f350 fffff8079ad013d5 : 0000000000000100 ffffd302ee9aba58 00000000e509ccd0 fffff80783524440 : dxgkrnl!DXGADAPTER::Reset+0x4df
ffffe382a076f3d0 fffff8079ad01547 : fffff80783524440 ffffd302ec55a610 0000000000000000 0000000000000100 : dxgkrnl!TdrResetFromTimeout+0x15
ffffe382a076f400 fffff80782ab8515 : ffffd302ec407240 fffff8079ad01520 ffffd302e509ccd0 ffffd30200000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffe382a076f430 fffff80782b55855 : ffffd302ec407240 0000000000000080 ffffd302e50b8040 001fa4efbd9bbfff : nt!ExpWorkerThread+0x105
ffffe382a076f4d0 fffff80782bfe788 : ffffab8109ccc180 ffffd302ec407240 fffff80782b55800 329f329e329d329c : nt!PspSystemThreadStartup+0x55
ffffe382a076f520 0000000000000000 : ffffe382a0770000 ffffe382a0769000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+dc6bd8

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

Followup: MachineOwner
have you found any solution so far? I have pretty much the same problem with same symbol name, module name, everything even the failure ID hash is the same. My pc is crashing when playing games and running 3dmark, passes furmark and aida64 stress test with ease. I’m running an i5-11400, 16gb of dual channel ram, a 3060 and a cougar GX-S650 PSU.
 
have you found any solution so far? I have pretty much the same problem with same symbol name, module name, everything even the failure ID hash is the same. My pc is crashing when playing games and running 3dmark, passes furmark and aida64 stress test with ease. I’m running an i5-11400, 16gb of dual channel ram, a 3060 and a cougar GX-S650 PSU.
Welp my computer just rebooted on its own so it seems nothing has solved the issue. Info from my memory dmp

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffd302f69e5010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8079e4a6bd8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5d5c294bb8d17217\nvlddmkm.sys, Win32 error 0n2

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2687

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 3785

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

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

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

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


BUGCHECK_CODE: 116

BUGCHECK_P1: ffffd302f69e5010

BUGCHECK_P2: fffff8079e4a6bd8

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffd302f69e5010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffe382a076f2d8 fffff8079ad01cae : 0000000000000116 ffffd302f69e5010 fffff8079e4a6bd8 ffffffffc000009a : nt!KeBugCheckEx
ffffe382a076f2e0 fffff8079acb24d4 : fffff8079e4a6bd8 ffffd302ee9a4860 0000000000002000 ffffd302ee9a4920 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffe382a076f320 fffff8079acab00f : ffffd302ee9ab000 0000000001000000 0000000000000002 0000000000000002 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffffe382a076f350 fffff8079ad013d5 : 0000000000000100 ffffd302ee9aba58 00000000e509ccd0 fffff80783524440 : dxgkrnl!DXGADAPTER::Reset+0x4df
ffffe382a076f3d0 fffff8079ad01547 : fffff80783524440 ffffd302ec55a610 0000000000000000 0000000000000100 : dxgkrnl!TdrResetFromTimeout+0x15
ffffe382a076f400 fffff80782ab8515 : ffffd302ec407240 fffff8079ad01520 ffffd302e509ccd0 ffffd30200000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffe382a076f430 fffff80782b55855 : ffffd302ec407240 0000000000000080 ffffd302e50b8040 001fa4efbd9bbfff : nt!ExpWorkerThread+0x105
ffffe382a076f4d0 fffff80782bfe788 : ffffab8109ccc180 ffffd302ec407240 fffff80782b55800 329f329e329d329c : nt!PspSystemThreadStartup+0x55
ffffe382a076f520 0000000000000000 : ffffe382a0770000 ffffe382a0769000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+dc6bd8

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

Followup: MachineOwner
Have you both used ddu, in safe mode remove all display divers and reinstall
 
Solution