F5F Stay Refreshed Hardware Desktop Issue Report: Crash/Blue Screen Error DPC Wathdog Violation 0x133

Issue Report: Crash/Blue Screen Error DPC Wathdog Violation 0x133

Issue Report: Crash/Blue Screen Error DPC Wathdog Violation 0x133

K
KAPAMASTERPTYT
Member
Find
117
12-12-2025, 12:39 AM
#1
Hi everyone,
My PC has been having crashes/BSOD upon loading games (usually Civ 7). I am getting a 'DPC Wathdog Violation_0x133' message upon crash, and the PC cycles back to the login screen.
Upon rebooting, the primary/dedicated GPU is sometimes not detected at all and I have to restart the system. Once the GPU is detected again, the issue stops and the system does not crash again until the same scenario the following day. Once a game is up and running, everything works fine (long sessions, high graphics settings/rendering). I am assuming this is GPU/driver related since it seems to only occur when loading graphics-intensive games. This crash has never occurred when not in a game.
I've tried a few steps (listed below), but would appreciate any insight you all might have.
Hardware specs:
CPU: Intel I9 12900K 3.2GHz
CPU cooler: ASUS Ryuo 240mm Liquid Cooler
Motherboard: ASUS Ryuo STRIX B-760I
Ram: GSkill Ripjaws S5 DDR5 6000 SDRAM 64GB (2x32)
SSD/HDD: Crucial MX500 4TB 3D NAND SSD
GPU: Zotac Nvidia GeForce 4070Ti 12GB GDDR6 192-bit
PSU: Corsair SF750watt SFX80+ Platinum
Chassis: Lian Li A4-H20 Mini-ITX
OS: Windows 11 Home 64bit
Monitor: ASUS TUF gaming 32in. 1440P VG32AQL1A
Things I have already tried:
Full re-install of Windows and all drivers
Remove all GPU drivers with DDU and update to latest Nvidia drivers (have done this a few times)
Revert to prior versions of GPU drivers (tried several older versions)
Confirm GPU is physially seated/wired correctly and have monitored temps during gaming, issue does not seem to be thermal-related.
Thanks in advance!
Dumpfile from most recent crash spoilered below:
Spoiler:
Dump file
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff800975c43b0, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4406
Key : Analysis.Elapsed.mSec
Value: 13075
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 24
Key : Analysis.Init.CPU.mSec
Value: 4078
Key : Analysis.Init.Elapsed.mSec
Value: 70520
Key : Analysis.Memory.CommitPeak.Mb
Value: 108
Key : Analysis.Version.DbgEng
Value: 10.0.29457.1000
Key : Analysis.Version.Description
Value: 10.2506.23.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2506.23.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x133
Key : Bugcheck.Code.TargetModel
Value: 0x133
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: 0x133_ISR_nvlddmkm!unknown_function
Key : Failure.Hash
Value: {f97493a5-ea2b-23ca-a808-8602773c2a86}
Key : Hypervisor.Enlightenments.ValueHex
Value: 0x7417df84
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 0
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1
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: 55185662
Key : Hypervisor.Flags.ValueHex
Value: 0x34a10fe
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
Key : Stack.Pointer
Value: ISR
Key : WER.System.BIOSRevision
Value: 4.1.0.0
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff800975c43b0
BUGCHECK_P4: 0
FILE_IN_CAB: 101725-16750-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump
FAULTING_THREAD: ffffe789d4685280
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1 (!blackboxwinlogon)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff9800`d2ddbc18 fffff800`96873d96 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`975c43b0 : nt!KeBugCheckEx
ffff9800`d2ddbc20 fffff800`968732e1 : 00000000`00000000 00000000`00007875 00000000`00000000 ffff9800`d2dbf180 : nt!KeAccumulateTicks+0x596
ffff9800`d2ddbc90 fffff800`9687978a : 00000001`1f33d36d ffff9800`d2dbf180 00000000`0000000f ffffe789`00000002 : nt!KiUpdateRunTime+0xb1
ffff9800`d2ddbe50 fffff800`9687a11c : ffffe789`d4577ea0 ffffe789`d4577f50 fffff800`9758e728 ffff9800`00000002 : nt!KeClockInterruptNotify+0x41a
ffff9800`d2ddbf40 fffff800`96ca1b6e : 00000000`00000002 ffffe789`d4577ea0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x32c
ffff9800`d2ddbfb0 fffff800`96ca237c : ffffd889`3006ed60 00000000`00000000 00000000`00000000 00000001`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
ffffd889`3006ed50 fffff800`4419840f : 00000000`00000003 00000000`0000001f ffffd889`3006efe0 fffff800`451fb784 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
ffffd889`3006eee0 00000000`00000003 : 00000000`0000001f ffffd889`3006efe0 fffff800`451fb784 0000000e`00000090 : nvlddmkm+0xd840f
ffffd889`3006eee8 00000000`0000001f : ffffd889`3006efe0 fffff800`451fb784 0000000e`00000090 000bf8bd`68f2e7ea : 0x3
ffffd889`3006eef0 ffffd889`3006efe0 : fffff800`451fb784 0000000e`00000090 000bf8bd`68f2e7ea 68f2e7ea`ffffffff : 0x1f
ffffd889`3006eef8 fffff800`451fb784 : 0000000e`00000090 000bf8bd`68f2e7ea 68f2e7ea`ffffffff a0a40399`000bf8bd : 0xffffd889`3006efe0
ffffd889`3006ef00 0000000e`00000090 : 000bf8bd`68f2e7ea 68f2e7ea`ffffffff a0a40399`000bf8bd ffffd889`c0040090 : nvlddmkm+0x113b784
ffffd889`3006ef08 000bf8bd`68f2e7ea : 68f2e7ea`ffffffff a0a40399`000bf8bd ffffd889`c0040090 ffffd889`3006f1f0 : 0x0000000e`00000090
ffffd889`3006ef10 68f2e7ea`ffffffff : a0a40399`000bf8bd ffffd889`c0040090 ffffd889`3006f1f0 00000000`00000000 : 0x000bf8bd`68f2e7ea
ffffd889`3006ef18 a0a40399`000bf8bd : ffffd889`c0040090 ffffd889`3006f1f0 00000000`00000000 00000000`00000013 : 0x68f2e7ea`ffffffff
ffffd889`3006ef20 ffffd889`c0040090 : ffffd889`3006f1f0 00000000`00000000 00000000`00000013 00000000`00000000 : 0xa0a40399`000bf8bd
ffffd889`3006ef28 ffffd889`3006f1f0 : 00000000`00000000 00000000`00000013 00000000`00000000 ffffd889`3006f060 : 0xffffd889`c0040090
ffffd889`3006ef30 00000000`00000000 : 00000000`00000013 00000000`00000000 ffffd889`3006f060 00000000`00000004 : 0xffffd889`3006f1f0
SYMBOL_NAME: nvlddmkm+d840f
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .process /r /p 0xfffff800975cef80; .thread 0xffffe789d4685280 ; kb
BUCKET_ID_FUNC_OFFSET: d840f
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}
Followup: MachineOwner
Reply
Reply
K
KAPAMASTERPTYT
12-12-2025, 12:39 AM #1

Hi everyone,
My PC has been having crashes/BSOD upon loading games (usually Civ 7). I am getting a 'DPC Wathdog Violation_0x133' message upon crash, and the PC cycles back to the login screen.
Upon rebooting, the primary/dedicated GPU is sometimes not detected at all and I have to restart the system. Once the GPU is detected again, the issue stops and the system does not crash again until the same scenario the following day. Once a game is up and running, everything works fine (long sessions, high graphics settings/rendering). I am assuming this is GPU/driver related since it seems to only occur when loading graphics-intensive games. This crash has never occurred when not in a game.
I've tried a few steps (listed below), but would appreciate any insight you all might have.
Hardware specs:
CPU: Intel I9 12900K 3.2GHz
CPU cooler: ASUS Ryuo 240mm Liquid Cooler
Motherboard: ASUS Ryuo STRIX B-760I
Ram: GSkill Ripjaws S5 DDR5 6000 SDRAM 64GB (2x32)
SSD/HDD: Crucial MX500 4TB 3D NAND SSD
GPU: Zotac Nvidia GeForce 4070Ti 12GB GDDR6 192-bit
PSU: Corsair SF750watt SFX80+ Platinum
Chassis: Lian Li A4-H20 Mini-ITX
OS: Windows 11 Home 64bit
Monitor: ASUS TUF gaming 32in. 1440P VG32AQL1A
Things I have already tried:
Full re-install of Windows and all drivers
Remove all GPU drivers with DDU and update to latest Nvidia drivers (have done this a few times)
Revert to prior versions of GPU drivers (tried several older versions)
Confirm GPU is physially seated/wired correctly and have monitored temps during gaming, issue does not seem to be thermal-related.
Thanks in advance!
Dumpfile from most recent crash spoilered below:
Spoiler:
Dump file
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff800975c43b0, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4406
Key : Analysis.Elapsed.mSec
Value: 13075
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 24
Key : Analysis.Init.CPU.mSec
Value: 4078
Key : Analysis.Init.Elapsed.mSec
Value: 70520
Key : Analysis.Memory.CommitPeak.Mb
Value: 108
Key : Analysis.Version.DbgEng
Value: 10.0.29457.1000
Key : Analysis.Version.Description
Value: 10.2506.23.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2506.23.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x133
Key : Bugcheck.Code.TargetModel
Value: 0x133
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: 0x133_ISR_nvlddmkm!unknown_function
Key : Failure.Hash
Value: {f97493a5-ea2b-23ca-a808-8602773c2a86}
Key : Hypervisor.Enlightenments.ValueHex
Value: 0x7417df84
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 0
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1
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: 55185662
Key : Hypervisor.Flags.ValueHex
Value: 0x34a10fe
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
Key : Stack.Pointer
Value: ISR
Key : WER.System.BIOSRevision
Value: 4.1.0.0
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff800975c43b0
BUGCHECK_P4: 0
FILE_IN_CAB: 101725-16750-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump
FAULTING_THREAD: ffffe789d4685280
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1 (!blackboxwinlogon)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff9800`d2ddbc18 fffff800`96873d96 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`975c43b0 : nt!KeBugCheckEx
ffff9800`d2ddbc20 fffff800`968732e1 : 00000000`00000000 00000000`00007875 00000000`00000000 ffff9800`d2dbf180 : nt!KeAccumulateTicks+0x596
ffff9800`d2ddbc90 fffff800`9687978a : 00000001`1f33d36d ffff9800`d2dbf180 00000000`0000000f ffffe789`00000002 : nt!KiUpdateRunTime+0xb1
ffff9800`d2ddbe50 fffff800`9687a11c : ffffe789`d4577ea0 ffffe789`d4577f50 fffff800`9758e728 ffff9800`00000002 : nt!KeClockInterruptNotify+0x41a
ffff9800`d2ddbf40 fffff800`96ca1b6e : 00000000`00000002 ffffe789`d4577ea0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x32c
ffff9800`d2ddbfb0 fffff800`96ca237c : ffffd889`3006ed60 00000000`00000000 00000000`00000000 00000001`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
ffffd889`3006ed50 fffff800`4419840f : 00000000`00000003 00000000`0000001f ffffd889`3006efe0 fffff800`451fb784 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
ffffd889`3006eee0 00000000`00000003 : 00000000`0000001f ffffd889`3006efe0 fffff800`451fb784 0000000e`00000090 : nvlddmkm+0xd840f
ffffd889`3006eee8 00000000`0000001f : ffffd889`3006efe0 fffff800`451fb784 0000000e`00000090 000bf8bd`68f2e7ea : 0x3
ffffd889`3006eef0 ffffd889`3006efe0 : fffff800`451fb784 0000000e`00000090 000bf8bd`68f2e7ea 68f2e7ea`ffffffff : 0x1f
ffffd889`3006eef8 fffff800`451fb784 : 0000000e`00000090 000bf8bd`68f2e7ea 68f2e7ea`ffffffff a0a40399`000bf8bd : 0xffffd889`3006efe0
ffffd889`3006ef00 0000000e`00000090 : 000bf8bd`68f2e7ea 68f2e7ea`ffffffff a0a40399`000bf8bd ffffd889`c0040090 : nvlddmkm+0x113b784
ffffd889`3006ef08 000bf8bd`68f2e7ea : 68f2e7ea`ffffffff a0a40399`000bf8bd ffffd889`c0040090 ffffd889`3006f1f0 : 0x0000000e`00000090
ffffd889`3006ef10 68f2e7ea`ffffffff : a0a40399`000bf8bd ffffd889`c0040090 ffffd889`3006f1f0 00000000`00000000 : 0x000bf8bd`68f2e7ea
ffffd889`3006ef18 a0a40399`000bf8bd : ffffd889`c0040090 ffffd889`3006f1f0 00000000`00000000 00000000`00000013 : 0x68f2e7ea`ffffffff
ffffd889`3006ef20 ffffd889`c0040090 : ffffd889`3006f1f0 00000000`00000000 00000000`00000013 00000000`00000000 : 0xa0a40399`000bf8bd
ffffd889`3006ef28 ffffd889`3006f1f0 : 00000000`00000000 00000000`00000013 00000000`00000000 ffffd889`3006f060 : 0xffffd889`c0040090
ffffd889`3006ef30 00000000`00000000 : 00000000`00000013 00000000`00000000 ffffd889`3006f060 00000000`00000004 : 0xffffd889`3006f1f0
SYMBOL_NAME: nvlddmkm+d840f
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .process /r /p 0xfffff800975cef80; .thread 0xffffe789d4685280 ; kb
BUCKET_ID_FUNC_OFFSET: d840f
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}
Followup: MachineOwner

Reply
Reply
D
Default_Matix
Member
Find
138
12-12-2025, 12:39 AM
#2
Welcome to the forums, newcomer!
It would have been better if you analyzed the .dmp files for us to understand, but let's try to figure it out.
nvlddmkm.sys
This is typically a problem with your Nvidia GPU drivers.
After rebooting, the main GPU might not be detected at all, forcing me to restart the system.
Possible causes include a power supply issue or a motherboard BIOS problem.
PSU: Corsair SF750watt SFX80+ Platinum
How old is your PSU?
Motherboard: ASUS Ryuo STRIX B-760I
What BIOS version are you running?
Performing a full reinstall of Windows and drivers
Where did you obtain the installer for your operating system? Did you install it offline? Were you installing all necessary drivers manually in an elevated command while offline?
Chassis: Lian Li A4-H20 Mini-ITX
You're using a riser cable. I recommend testing without it—check if the GPU is seated properly in the motherboard's physical PCIe x16 slot. If the problem disappears, the issue likely lies with the riser cable.
Reply
Reply
D
Default_Matix
12-12-2025, 12:39 AM #2

Welcome to the forums, newcomer!
It would have been better if you analyzed the .dmp files for us to understand, but let's try to figure it out.
nvlddmkm.sys
This is typically a problem with your Nvidia GPU drivers.
After rebooting, the main GPU might not be detected at all, forcing me to restart the system.
Possible causes include a power supply issue or a motherboard BIOS problem.
PSU: Corsair SF750watt SFX80+ Platinum
How old is your PSU?
Motherboard: ASUS Ryuo STRIX B-760I
What BIOS version are you running?
Performing a full reinstall of Windows and drivers
Where did you obtain the installer for your operating system? Did you install it offline? Were you installing all necessary drivers manually in an elevated command while offline?
Chassis: Lian Li A4-H20 Mini-ITX
You're using a riser cable. I recommend testing without it—check if the GPU is seated properly in the motherboard's physical PCIe x16 slot. If the problem disappears, the issue likely lies with the riser cable.

Reply
Reply
G
GewoonThijs
Member
Find
65
12-12-2025, 12:39 AM
#3
Thank you for your prompt response.
My PSU is approximately 2.5 years old, matching the condition of the rest of the system.
BIOS on the motherboard is AMI 0401 [10/21/22].
Windows was installed from an external drive using offline mode. The source was directly from the MS download portal or store. All necessary drivers were installed via elevated command (admin) during offline installation, though not individually. Some drivers came packaged with me. The GPU driver was consistently downloaded and installed separately.
If necessary, I can open the case again to evaluate the riser cable problem. Your advice on this matter would have been unexpected for me.
I plan to perform a complete OS and driver wipe before addressing the hardware side again.
Reply
Reply
G
GewoonThijs
12-12-2025, 12:39 AM #3

Thank you for your prompt response.
My PSU is approximately 2.5 years old, matching the condition of the rest of the system.
BIOS on the motherboard is AMI 0401 [10/21/22].
Windows was installed from an external drive using offline mode. The source was directly from the MS download portal or store. All necessary drivers were installed via elevated command (admin) during offline installation, though not individually. Some drivers came packaged with me. The GPU driver was consistently downloaded and installed separately.
If necessary, I can open the case again to evaluate the riser cable problem. Your advice on this matter would have been unexpected for me.
I plan to perform a complete OS and driver wipe before addressing the hardware side again.

Reply
Reply
P
Pandalaf
Junior Member
Find
33
12-12-2025, 12:39 AM
#4
The BIOS on the motherboard is AMI 0401 from October 21, 2022.
ROG STRIX B760-I GAMING WIFI | ROG Strix | Gaming Motherboards｜ROG - Republic of Gamers｜ROG Global
This model offers strong Raptor Lake performance and numerous connectivity features in a compact mini-ITX design.
Reply
Reply
P
Pandalaf
12-12-2025, 12:39 AM #4

The BIOS on the motherboard is AMI 0401 from October 21, 2022.
ROG STRIX B760-I GAMING WIFI | ROG Strix | Gaming Motherboards｜ROG - Republic of Gamers｜ROG Global
This model offers strong Raptor Lake performance and numerous connectivity features in a compact mini-ITX design.

Reply
Reply