F5F Stay Refreshed Hardware Desktop Rtx4090RTX 4090FE appears with a black screen and maximum fan operation. Driver issues or hardware damage possible?

Rtx4090RTX 4090FE appears with a black screen and maximum fan operation. Driver issues or hardware damage possible?

Rtx4090RTX 4090FE appears with a black screen and maximum fan operation. Driver issues or hardware damage possible?

T
Thelexyinator
Junior Member
Find
17
09-11-2025, 04:22 AM
#1
Update 2: Issue is not resolved, just went through 4 crashes/failed bootup attempts. Nothing in event viewer other than the "unexpected loss of power" error. Minidumps place the blame on nvlddmkm.sys. On a simple webpage. Trying another round of /sfc scannow Update 1: Potentially solved. BIOS was out of date. Currently dealing with an issue I have never had before, wanted to see if anyone here might be able to help. More than anything, I'd like to just rule out hardware faults. Issue goes: In seemingly random circumstances my display output will go black, and the GPU fans will ramp to 100%. Onboard graphics will still work if I switch my input from the GPU to the motherboard, but Windows will eventually crash, needing a hard reboot. Some information I think is irrelevant: I have occasionally gotten errors in Event Viewer pointing to nvlddmkm.sys 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 Restarting TDR occurred on GPUID:100 The message resource is present but the message was not found in the message table Complete minidumps: VIDEO_DXGKRNL_FATAL_ERROR (113) The dxgkrnl has detected that a violation has occurred. This resulted in a condition that dxgkrnl can no longer progress. By crashing, dxgkrnl is attempting to get enough information into the minidump such that somebody can pinpoint the crash cause. Any other values after parameter 1 must be individually examined according to the subtype. Arguments: Arg1: 0000000000000019, The subtype of the BugCheck: Arg2: 0000000000000001 Arg3: 00000000000010de Arg4: 0000000000002684 Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for nvlddmkm.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 781 Key : Analysis.Elapsed.mSec Value: 1412 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 343 Key : Analysis.Init.Elapsed.mSec Value: 7439 Key : Analysis.Memory.CommitPeak.Mb Value: 117 Key : Analysis.Version.DbgEng Value: 10.0.27871.1001 Key : Analysis.Version.Description Value: 10.2505.01.02 amd64fre Key : Analysis.Version.Ext Value: 1.2505.1.2 Key : Bugcheck.Code.LegacyAPI Value: 0x113 Key : Bugcheck.Code.TargetModel Value: 0x113 Key : DirectX.FatalError.Code Value: 0x19 Key : DirectX.FatalError.Desc Value: UNEXPECTED_DEFERRED_DESTRUCTION Key : Dump.Attributes.AsUlong Value: 0x21808 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0x0 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 0 Key : Failure.Bucket Value: 0x113_19_nvlddmkm!unknown_function Key : Failure.Exception.IP.Address Value: 0xfffff80162b990a1 Key : Failure.Exception.IP.Module Value: nvlddmkm Key : Failure.Exception.IP.Offset Value: 0x19890a1 Key : Failure.Hash Value: {fb504da1-90a7-64ec-e7aa-d0c04338976f} Key : Hypervisor.Enlightenments.ValueHex Value: 0x7497cf94 Key : Hypervisor.Flags.AnyHypervisorPresent Value: 1 Key : Hypervisor.Flags.ApicEnlightened Value: 1 Key : Hypervisor.Flags.ApicVirtualizationAvailable Value: 0 Key : Hypervisor.Flags.AsyncMemoryHint Value: 0 Key : Hypervisor.Flags.CoreSchedulerRequested Value: 0 Key : Hypervisor.Flags.CpuManager Value: 1 Key : Hypervisor.Flags.DeprecateAutoEoi Value: 0 Key : Hypervisor.Flags.DynamicCpuDisabled Value: 1 Key : Hypervisor.Flags.Epf Value: 0 Key : Hypervisor.Flags.ExtendedProcessorMasks Value: 1 Key : Hypervisor.Flags.HardwareMbecAvailable Value: 1 Key : Hypervisor.Flags.MaxBankNumber Value: 0 Key : Hypervisor.Flags.MemoryZeroingControl Value: 0 Key : Hypervisor.Flags.NoExtendedRangeFlush Value: 0 Key : Hypervisor.Flags.NoNonArchCoreSharing Value: 1 Key : Hypervisor.Flags.Phase0InitDone Value: 1 Key : Hypervisor.Flags.PowerSchedulerQos Value: 0 Key : Hypervisor.Flags.RootScheduler Value: 0 Key : Hypervisor.Flags.SynicAvailable Value: 1 Key : Hypervisor.Flags.UseQpcBias Value: 0 Key : Hypervisor.Flags.Value Value: 38408431 Key : Hypervisor.Flags.ValueHex Value: 0x24a10ef Key : Hypervisor.Flags.VpAssistPage Value: 1 Key : Hypervisor.Flags.VsmAvailable Value: 1 Key : Hypervisor.RootFlags.AccessStats Value: 1 Key : Hypervisor.RootFlags.CrashdumpEnlightened Value: 1 Key : Hypervisor.RootFlags.CreateVirtualProcessor Value: 1 Key : Hypervisor.RootFlags.DisableHyperthreading Value: 0 Key : Hypervisor.RootFlags.HostTimelineSync Value: 1 Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled Value: 0 Key : Hypervisor.RootFlags.IsHyperV Value: 1 Key : Hypervisor.RootFlags.LivedumpEnlightened Value: 1 Key : Hypervisor.RootFlags.MapDeviceInterrupt Value: 1 Key : Hypervisor.RootFlags.MceEnlightened Value: 1 Key : Hypervisor.RootFlags.Nested Value: 0 Key : Hypervisor.RootFlags.StartLogicalProcessor Value: 1 Key : Hypervisor.RootFlags.Value Value: 1015 Key : Hypervisor.RootFlags.ValueHex Value: 0x3f7 BUGCHECK_CODE: 113 BUGCHECK_P1: 19 BUGCHECK_P2: 1 BUGCHECK_P3: 10de BUGCHECK_P4: 2684 FILE_IN_CAB: 070825-19546-01.dmp TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b DUMP_FILE_ATTRIBUTES: 0x21808 Kernel Generated Triage Dump FAULTING_THREAD: ffffab02627e9040 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: fffffd08`7c4e1b98 fffff801`1bec1316 : 00000000`00000113 00000000`00000019 00000000`00000001 00000000`000010de : nt!KeBugCheckEx fffffd08`7c4e1ba0 fffff801`1c129157 : ffffab02`7139b117 ffffab02`7139b117 ffffab02`7139b180 fffffd08`7c4e1d79 : watchdog!WdLogSingleEntry5+0x156 fffffd08`7c4e1c30 fffff801`1c1265f4 : 7fffffff`ffffff00 00000000`00000000 ffffab02`7139b117 fffff801`1bf2fce7 : dxgkrnl!DpiFdoHandleSurpriseRemoval+0x157 fffffd08`7c4e1c90 fffff801`1c2a0249 : ffffab02`7139b030 ffffab02`80c40de0 ffffab02`7139b030 ffffab02`713a2000 : dxgkrnl!DpiFdoDispatchPnp+0xd4 fffffd08`7c4e1d30 fffff801`62b990a1 : 00000000`00000000 fffffd08`069c0000 ffffab02`713a2000 00000000`00000000 : dxgkrnl!DpiDispatchPnp+0xe9 fffffd08`7c4e1e50 00000000`00000000 : fffffd08`069c0000 ffffab02`713a2000 00000000`00000000 fffff801`62b993d1 : nvlddmkm+0x19890a1 SYMBOL_NAME: nvlddmkm+19890a1 MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys STACK_COMMAND: .process /r /p 0xffffab0262563040; .thread 0xffffab02627e9040 ; kb BUCKET_ID_FUNC_OFFSET: 19890a1 FAILURE_BUCKET_ID: 0x113_19_nvlddmkm!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {fb504da1-90a7-64ec-e7aa-d0c04338976f} Followup: MachineOwner VIDEO_DXGKRNL_FATAL_ERROR (113) The dxgkrnl has detected that a violation has occurred. This resulted in a condition that dxgkrnl can no longer progress. By crashing, dxgkrnl is attempting to get enough information into the minidump such that somebody can pinpoint the crash cause. Any other values after parameter 1 must be individually examined according to the subtype. Arguments: Arg1: 0000000000000019, The subtype of the BugCheck: Arg2: 0000000000000001 Arg3: 00000000000010de Arg4: 0000000000002684 Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for nvlddmkm.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 750 Key : Analysis.Elapsed.mSec Value: 1389 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 453 Key : Analysis.Init.Elapsed.mSec Value: 6936 Key : Analysis.Memory.CommitPeak.Mb Value: 118 Key : Analysis.Version.DbgEng Value: 10.0.27871.1001 Key : Analysis.Version.Description Value: 10.2505.01.02 amd64fre Key : Analysis.Version.Ext Value: 1.2505.1.2 Key : Bugcheck.Code.LegacyAPI Value: 0x113 Key : Bugcheck.Code.TargetModel Value: 0x113 Key : DirectX.FatalError.Code Value: 0x19 Key : DirectX.FatalError.Desc Value: UNEXPECTED_DEFERRED_DESTRUCTION Key : Dump.Attributes.AsUlong Value: 0x21808 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0x0 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 0 Key : Failure.Bucket Value: 0x113_19_nvlddmkm!unknown_function Key : Failure.Exception.IP.Address Value: 0xfffff803b3fb90a1 Key : Failure.Exception.IP.Module Value: nvlddmkm Key : Failure.Exception.IP.Offset Value: 0x19890a1 Key : Failure.Hash Value: {fb504da1-90a7-64ec-e7aa-d0c04338976f} Key : Hypervisor.Enlightenments.ValueHex Value: 0x7497cf94 Key : Hypervisor.Flags.AnyHypervisorPresent Value: 1 Key : Hypervisor.Flags.ApicEnlightened Value: 1 Key : Hypervisor.Flags.ApicVirtualizationAvailable Value: 0 Key : Hypervisor.Flags.AsyncMemoryHint Value: 0 Key : Hypervisor.Flags.CoreSchedulerRequested Value: 0 Key : Hypervisor.Flags.CpuManager Value: 1 Key : Hypervisor.Flags.DeprecateAutoEoi Value: 0 Key : Hypervisor.Flags.DynamicCpuDisabled Value: 1 Key : Hypervisor.Flags.Epf Value: 0 Key : Hypervisor.Flags.ExtendedProcessorMasks Value: 1 Key : Hypervisor.Flags.HardwareMbecAvailable Value: 1 Key : Hypervisor.Flags.MaxBankNumber Value: 0 Key : Hypervisor.Flags.MemoryZeroingControl Value: 0 Key : Hypervisor.Flags.NoExtendedRangeFlush Value: 0 Key : Hypervisor.Flags.NoNonArchCoreSharing Value: 1 Key : Hypervisor.Flags.Phase0InitDone Value: 1 Key : Hypervisor.Flags.PowerSchedulerQos Value: 0 Key : Hypervisor.Flags.RootScheduler Value: 0 Key : Hypervisor.Flags.SynicAvailable Value: 1 Key : Hypervisor.Flags.UseQpcBias Value: 0 Key : Hypervisor.Flags.Value Value: 38408431 Key : Hypervisor.Flags.ValueHex Value: 0x24a10ef Key : Hypervisor.Flags.VpAssistPage Value: 1 Key : Hypervisor.Flags.VsmAvailable Value: 1 Key : Hypervisor.RootFlags.AccessStats Value: 1 Key : Hypervisor.RootFlags.CrashdumpEnlightened Value: 1 Key : Hypervisor.RootFlags.CreateVirtualProcessor Value: 1 Key : Hypervisor.RootFlags.DisableHyperthreading Value: 0 Key : Hypervisor.RootFlags.HostTimelineSync Value: 1 Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled Value: 0 Key : Hypervisor.RootFlags.IsHyperV Value: 1 Key : Hypervisor.RootFlags.LivedumpEnlightened Value: 1 Key : Hypervisor.RootFlags.MapDeviceInterrupt Value: 1 Key : Hypervisor.RootFlags.MceEnlightened Value: 1 Key : Hypervisor.RootFlags.Nested Value: 0 Key : Hypervisor.RootFlags.StartLogicalProcessor Value: 1 Key : Hypervisor.RootFlags.Value Value: 1015 Key : Hypervisor.RootFlags.ValueHex Value: 0x3f7 BUGCHECK_CODE: 113 BUGCHECK_P1: 19 BUGCHECK_P2: 1 BUGCHECK_P3: 10de BUGCHECK_P4: 2684 FILE_IN_CAB: 070825-19078-01.dmp TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b DUMP_FILE_ATTRIBUTES: 0x21808 Kernel Generated Triage Dump FAULTING_THREAD: ffffc88b98580400 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffdd0c`de677b98 fffff803`6f451316 : 00000000`00000113 00000000`00000019 00000000`00000001 00000000`000010de : nt!KeBugCheckEx ffffdd0c`de677ba0 fffff803`6f6b9157 : ffffc88b`a380e117 ffffc88b`a380e117 ffffc88b`a380e180 ffffdd0c`de677d79 : watchdog!WdLogSingleEntry5+0x156 ffffdd0c`de677c30 fffff803`6f6b65f4 : 7fffffff`ffffff00 00000000`00000000 ffffc88b`a380e117 fffff803`6f4bfce7 : dxgkrnl!DpiFdoHandleSurpriseRemoval+0x157 ffffdd0c`de677c90 fffff803`6f830249 : ffffc88b`a380e030 ffffc88b`b1be69a0 ffffc88b`a380e030 ffffc88b`a3813000 : dxgkrnl!DpiFdoDispatchPnp+0xd4 ffffdd0c`de677d30 fffff803`b3fb90a1 : 00000000`00000000 ffffdd0c`069c0000 ffffc88b`a3813000 00000000`00000000 : dxgkrnl!DpiDispatchPnp+0xe9 ffffdd0c`de677e50 00000000`00000000 : ffffdd0c`069c0000 ffffc88b`a3813000 00000000`00000000 fffff803`b3fb93d1 : nvlddmkm+0x19890a1 SYMBOL_NAME: nvlddmkm+19890a1 MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys STACK_COMMAND: .process /r /p 0xffffc88b98586040; .thread 0xffffc88b98580400 ; kb BUCKET_ID_FUNC_OFFSET: 19890a1 FAILURE_BUCKET_ID: 0x113_19_nvlddmkm!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {fb504da1-90a7-64ec-e7aa-d0c04338976f} Followup: MachineOwner Other tidbits: This doesn't seem to be related to load, and has happened waking up out of sleep, signing into Windows, at the desktop, etc. Oddly enough, I don't think it's ever happened during a game. The problem was incredibly persistent, occurring almost every single time I turned my machine on. There were times where I couldn't even enter my PIN fast enough before it would crash. It wasn't until using DDU to remove the graphics driver and reinstalling it that the issue almost completely disappeared... However, just this morning when getting on my machine and waking it out of sleep, the same problem. The CPU fan does not follow suit and remains at its normal idle speed when this issue occurs. System specs: ROG Strix B850-I Gaming Wi-Fi - Bios 1022 Ryzen 7 9800X3D Corsair Dominator 32GB (2x16) 7200 RTX 4090 FE - Driver 576.88 WD Black 4Tb NVME SSD Corsair SF1000 (GPU Powered Using the 12 pin off the PSU, not using the adapter) My thoughts: My mind has jumped around a lot thinking it could be anything from the system itself and some components to software problems. It not happening under load has ruled out power delivery to me, and my mind really points towards a driver issue, especially given the improvement after I updated. Any thoughts? Edited July 9, 2025 by MVZE Added additonal info, crash logs, noted problem is not solved.
Reply
Reply
T
Thelexyinator
09-11-2025, 04:22 AM #1

Update 2: Issue is not resolved, just went through 4 crashes/failed bootup attempts. Nothing in event viewer other than the "unexpected loss of power" error. Minidumps place the blame on nvlddmkm.sys. On a simple webpage. Trying another round of /sfc scannow Update 1: Potentially solved. BIOS was out of date. Currently dealing with an issue I have never had before, wanted to see if anyone here might be able to help. More than anything, I'd like to just rule out hardware faults. Issue goes: In seemingly random circumstances my display output will go black, and the GPU fans will ramp to 100%. Onboard graphics will still work if I switch my input from the GPU to the motherboard, but Windows will eventually crash, needing a hard reboot. Some information I think is irrelevant: I have occasionally gotten errors in Event Viewer pointing to nvlddmkm.sys 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 Restarting TDR occurred on GPUID:100 The message resource is present but the message was not found in the message table Complete minidumps: VIDEO_DXGKRNL_FATAL_ERROR (113) The dxgkrnl has detected that a violation has occurred. This resulted in a condition that dxgkrnl can no longer progress. By crashing, dxgkrnl is attempting to get enough information into the minidump such that somebody can pinpoint the crash cause. Any other values after parameter 1 must be individually examined according to the subtype. Arguments: Arg1: 0000000000000019, The subtype of the BugCheck: Arg2: 0000000000000001 Arg3: 00000000000010de Arg4: 0000000000002684 Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for nvlddmkm.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 781 Key : Analysis.Elapsed.mSec Value: 1412 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 343 Key : Analysis.Init.Elapsed.mSec Value: 7439 Key : Analysis.Memory.CommitPeak.Mb Value: 117 Key : Analysis.Version.DbgEng Value: 10.0.27871.1001 Key : Analysis.Version.Description Value: 10.2505.01.02 amd64fre Key : Analysis.Version.Ext Value: 1.2505.1.2 Key : Bugcheck.Code.LegacyAPI Value: 0x113 Key : Bugcheck.Code.TargetModel Value: 0x113 Key : DirectX.FatalError.Code Value: 0x19 Key : DirectX.FatalError.Desc Value: UNEXPECTED_DEFERRED_DESTRUCTION Key : Dump.Attributes.AsUlong Value: 0x21808 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0x0 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 0 Key : Failure.Bucket Value: 0x113_19_nvlddmkm!unknown_function Key : Failure.Exception.IP.Address Value: 0xfffff80162b990a1 Key : Failure.Exception.IP.Module Value: nvlddmkm Key : Failure.Exception.IP.Offset Value: 0x19890a1 Key : Failure.Hash Value: {fb504da1-90a7-64ec-e7aa-d0c04338976f} Key : Hypervisor.Enlightenments.ValueHex Value: 0x7497cf94 Key : Hypervisor.Flags.AnyHypervisorPresent Value: 1 Key : Hypervisor.Flags.ApicEnlightened Value: 1 Key : Hypervisor.Flags.ApicVirtualizationAvailable Value: 0 Key : Hypervisor.Flags.AsyncMemoryHint Value: 0 Key : Hypervisor.Flags.CoreSchedulerRequested Value: 0 Key : Hypervisor.Flags.CpuManager Value: 1 Key : Hypervisor.Flags.DeprecateAutoEoi Value: 0 Key : Hypervisor.Flags.DynamicCpuDisabled Value: 1 Key : Hypervisor.Flags.Epf Value: 0 Key : Hypervisor.Flags.ExtendedProcessorMasks Value: 1 Key : Hypervisor.Flags.HardwareMbecAvailable Value: 1 Key : Hypervisor.Flags.MaxBankNumber Value: 0 Key : Hypervisor.Flags.MemoryZeroingControl Value: 0 Key : Hypervisor.Flags.NoExtendedRangeFlush Value: 0 Key : Hypervisor.Flags.NoNonArchCoreSharing Value: 1 Key : Hypervisor.Flags.Phase0InitDone Value: 1 Key : Hypervisor.Flags.PowerSchedulerQos Value: 0 Key : Hypervisor.Flags.RootScheduler Value: 0 Key : Hypervisor.Flags.SynicAvailable Value: 1 Key : Hypervisor.Flags.UseQpcBias Value: 0 Key : Hypervisor.Flags.Value Value: 38408431 Key : Hypervisor.Flags.ValueHex Value: 0x24a10ef Key : Hypervisor.Flags.VpAssistPage Value: 1 Key : Hypervisor.Flags.VsmAvailable Value: 1 Key : Hypervisor.RootFlags.AccessStats Value: 1 Key : Hypervisor.RootFlags.CrashdumpEnlightened Value: 1 Key : Hypervisor.RootFlags.CreateVirtualProcessor Value: 1 Key : Hypervisor.RootFlags.DisableHyperthreading Value: 0 Key : Hypervisor.RootFlags.HostTimelineSync Value: 1 Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled Value: 0 Key : Hypervisor.RootFlags.IsHyperV Value: 1 Key : Hypervisor.RootFlags.LivedumpEnlightened Value: 1 Key : Hypervisor.RootFlags.MapDeviceInterrupt Value: 1 Key : Hypervisor.RootFlags.MceEnlightened Value: 1 Key : Hypervisor.RootFlags.Nested Value: 0 Key : Hypervisor.RootFlags.StartLogicalProcessor Value: 1 Key : Hypervisor.RootFlags.Value Value: 1015 Key : Hypervisor.RootFlags.ValueHex Value: 0x3f7 BUGCHECK_CODE: 113 BUGCHECK_P1: 19 BUGCHECK_P2: 1 BUGCHECK_P3: 10de BUGCHECK_P4: 2684 FILE_IN_CAB: 070825-19546-01.dmp TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b DUMP_FILE_ATTRIBUTES: 0x21808 Kernel Generated Triage Dump FAULTING_THREAD: ffffab02627e9040 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: fffffd08`7c4e1b98 fffff801`1bec1316 : 00000000`00000113 00000000`00000019 00000000`00000001 00000000`000010de : nt!KeBugCheckEx fffffd08`7c4e1ba0 fffff801`1c129157 : ffffab02`7139b117 ffffab02`7139b117 ffffab02`7139b180 fffffd08`7c4e1d79 : watchdog!WdLogSingleEntry5+0x156 fffffd08`7c4e1c30 fffff801`1c1265f4 : 7fffffff`ffffff00 00000000`00000000 ffffab02`7139b117 fffff801`1bf2fce7 : dxgkrnl!DpiFdoHandleSurpriseRemoval+0x157 fffffd08`7c4e1c90 fffff801`1c2a0249 : ffffab02`7139b030 ffffab02`80c40de0 ffffab02`7139b030 ffffab02`713a2000 : dxgkrnl!DpiFdoDispatchPnp+0xd4 fffffd08`7c4e1d30 fffff801`62b990a1 : 00000000`00000000 fffffd08`069c0000 ffffab02`713a2000 00000000`00000000 : dxgkrnl!DpiDispatchPnp+0xe9 fffffd08`7c4e1e50 00000000`00000000 : fffffd08`069c0000 ffffab02`713a2000 00000000`00000000 fffff801`62b993d1 : nvlddmkm+0x19890a1 SYMBOL_NAME: nvlddmkm+19890a1 MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys STACK_COMMAND: .process /r /p 0xffffab0262563040; .thread 0xffffab02627e9040 ; kb BUCKET_ID_FUNC_OFFSET: 19890a1 FAILURE_BUCKET_ID: 0x113_19_nvlddmkm!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {fb504da1-90a7-64ec-e7aa-d0c04338976f} Followup: MachineOwner VIDEO_DXGKRNL_FATAL_ERROR (113) The dxgkrnl has detected that a violation has occurred. This resulted in a condition that dxgkrnl can no longer progress. By crashing, dxgkrnl is attempting to get enough information into the minidump such that somebody can pinpoint the crash cause. Any other values after parameter 1 must be individually examined according to the subtype. Arguments: Arg1: 0000000000000019, The subtype of the BugCheck: Arg2: 0000000000000001 Arg3: 00000000000010de Arg4: 0000000000002684 Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for nvlddmkm.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 750 Key : Analysis.Elapsed.mSec Value: 1389 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 453 Key : Analysis.Init.Elapsed.mSec Value: 6936 Key : Analysis.Memory.CommitPeak.Mb Value: 118 Key : Analysis.Version.DbgEng Value: 10.0.27871.1001 Key : Analysis.Version.Description Value: 10.2505.01.02 amd64fre Key : Analysis.Version.Ext Value: 1.2505.1.2 Key : Bugcheck.Code.LegacyAPI Value: 0x113 Key : Bugcheck.Code.TargetModel Value: 0x113 Key : DirectX.FatalError.Code Value: 0x19 Key : DirectX.FatalError.Desc Value: UNEXPECTED_DEFERRED_DESTRUCTION Key : Dump.Attributes.AsUlong Value: 0x21808 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0x0 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 0 Key : Failure.Bucket Value: 0x113_19_nvlddmkm!unknown_function Key : Failure.Exception.IP.Address Value: 0xfffff803b3fb90a1 Key : Failure.Exception.IP.Module Value: nvlddmkm Key : Failure.Exception.IP.Offset Value: 0x19890a1 Key : Failure.Hash Value: {fb504da1-90a7-64ec-e7aa-d0c04338976f} Key : Hypervisor.Enlightenments.ValueHex Value: 0x7497cf94 Key : Hypervisor.Flags.AnyHypervisorPresent Value: 1 Key : Hypervisor.Flags.ApicEnlightened Value: 1 Key : Hypervisor.Flags.ApicVirtualizationAvailable Value: 0 Key : Hypervisor.Flags.AsyncMemoryHint Value: 0 Key : Hypervisor.Flags.CoreSchedulerRequested Value: 0 Key : Hypervisor.Flags.CpuManager Value: 1 Key : Hypervisor.Flags.DeprecateAutoEoi Value: 0 Key : Hypervisor.Flags.DynamicCpuDisabled Value: 1 Key : Hypervisor.Flags.Epf Value: 0 Key : Hypervisor.Flags.ExtendedProcessorMasks Value: 1 Key : Hypervisor.Flags.HardwareMbecAvailable Value: 1 Key : Hypervisor.Flags.MaxBankNumber Value: 0 Key : Hypervisor.Flags.MemoryZeroingControl Value: 0 Key : Hypervisor.Flags.NoExtendedRangeFlush Value: 0 Key : Hypervisor.Flags.NoNonArchCoreSharing Value: 1 Key : Hypervisor.Flags.Phase0InitDone Value: 1 Key : Hypervisor.Flags.PowerSchedulerQos Value: 0 Key : Hypervisor.Flags.RootScheduler Value: 0 Key : Hypervisor.Flags.SynicAvailable Value: 1 Key : Hypervisor.Flags.UseQpcBias Value: 0 Key : Hypervisor.Flags.Value Value: 38408431 Key : Hypervisor.Flags.ValueHex Value: 0x24a10ef Key : Hypervisor.Flags.VpAssistPage Value: 1 Key : Hypervisor.Flags.VsmAvailable Value: 1 Key : Hypervisor.RootFlags.AccessStats Value: 1 Key : Hypervisor.RootFlags.CrashdumpEnlightened Value: 1 Key : Hypervisor.RootFlags.CreateVirtualProcessor Value: 1 Key : Hypervisor.RootFlags.DisableHyperthreading Value: 0 Key : Hypervisor.RootFlags.HostTimelineSync Value: 1 Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled Value: 0 Key : Hypervisor.RootFlags.IsHyperV Value: 1 Key : Hypervisor.RootFlags.LivedumpEnlightened Value: 1 Key : Hypervisor.RootFlags.MapDeviceInterrupt Value: 1 Key : Hypervisor.RootFlags.MceEnlightened Value: 1 Key : Hypervisor.RootFlags.Nested Value: 0 Key : Hypervisor.RootFlags.StartLogicalProcessor Value: 1 Key : Hypervisor.RootFlags.Value Value: 1015 Key : Hypervisor.RootFlags.ValueHex Value: 0x3f7 BUGCHECK_CODE: 113 BUGCHECK_P1: 19 BUGCHECK_P2: 1 BUGCHECK_P3: 10de BUGCHECK_P4: 2684 FILE_IN_CAB: 070825-19078-01.dmp TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b DUMP_FILE_ATTRIBUTES: 0x21808 Kernel Generated Triage Dump FAULTING_THREAD: ffffc88b98580400 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffdd0c`de677b98 fffff803`6f451316 : 00000000`00000113 00000000`00000019 00000000`00000001 00000000`000010de : nt!KeBugCheckEx ffffdd0c`de677ba0 fffff803`6f6b9157 : ffffc88b`a380e117 ffffc88b`a380e117 ffffc88b`a380e180 ffffdd0c`de677d79 : watchdog!WdLogSingleEntry5+0x156 ffffdd0c`de677c30 fffff803`6f6b65f4 : 7fffffff`ffffff00 00000000`00000000 ffffc88b`a380e117 fffff803`6f4bfce7 : dxgkrnl!DpiFdoHandleSurpriseRemoval+0x157 ffffdd0c`de677c90 fffff803`6f830249 : ffffc88b`a380e030 ffffc88b`b1be69a0 ffffc88b`a380e030 ffffc88b`a3813000 : dxgkrnl!DpiFdoDispatchPnp+0xd4 ffffdd0c`de677d30 fffff803`b3fb90a1 : 00000000`00000000 ffffdd0c`069c0000 ffffc88b`a3813000 00000000`00000000 : dxgkrnl!DpiDispatchPnp+0xe9 ffffdd0c`de677e50 00000000`00000000 : ffffdd0c`069c0000 ffffc88b`a3813000 00000000`00000000 fffff803`b3fb93d1 : nvlddmkm+0x19890a1 SYMBOL_NAME: nvlddmkm+19890a1 MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys STACK_COMMAND: .process /r /p 0xffffc88b98586040; .thread 0xffffc88b98580400 ; kb BUCKET_ID_FUNC_OFFSET: 19890a1 FAILURE_BUCKET_ID: 0x113_19_nvlddmkm!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {fb504da1-90a7-64ec-e7aa-d0c04338976f} Followup: MachineOwner Other tidbits: This doesn't seem to be related to load, and has happened waking up out of sleep, signing into Windows, at the desktop, etc. Oddly enough, I don't think it's ever happened during a game. The problem was incredibly persistent, occurring almost every single time I turned my machine on. There were times where I couldn't even enter my PIN fast enough before it would crash. It wasn't until using DDU to remove the graphics driver and reinstalling it that the issue almost completely disappeared... However, just this morning when getting on my machine and waking it out of sleep, the same problem. The CPU fan does not follow suit and remains at its normal idle speed when this issue occurs. System specs: ROG Strix B850-I Gaming Wi-Fi - Bios 1022 Ryzen 7 9800X3D Corsair Dominator 32GB (2x16) 7200 RTX 4090 FE - Driver 576.88 WD Black 4Tb NVME SSD Corsair SF1000 (GPU Powered Using the 12 pin off the PSU, not using the adapter) My thoughts: My mind has jumped around a lot thinking it could be anything from the system itself and some components to software problems. It not happening under load has ruled out power delivery to me, and my mind really points towards a driver issue, especially given the improvement after I updated. Any thoughts? Edited July 9, 2025 by MVZE Added additonal info, crash logs, noted problem is not solved.

Reply
Reply
B
Bebbe2013
Junior Member
Find
5
09-11-2025, 04:22 AM
#2
No updates were applied to the board.
Reply
Reply
B
Bebbe2013
09-11-2025, 04:22 AM #2

No updates were applied to the board.

Reply
Reply
_
_Pilif
Member
Find
114
09-11-2025, 04:22 AM
#3
Error detected, BIOS version 1022... System reports 1063. Updating soon. Hope it works.
Reply
Reply
_
_Pilif
09-11-2025, 04:22 AM #3

Error detected, BIOS version 1022... System reports 1063. Updating soon. Hope it works.

Reply
Reply
P
papa515
Junior Member
Find
3
09-11-2025, 04:22 AM
#4
Recent update: Encountered identical problem while browsing Reddit Windows, it crashed and entered a loop. Unclear cause, but latest drivers and BIOS are in use.
Reply
Reply
P
papa515
09-11-2025, 04:22 AM #4

Recent update: Encountered identical problem while browsing Reddit Windows, it crashed and entered a loop. Unclear cause, but latest drivers and BIOS are in use.

Reply
Reply