T
Tony de Lacey
Guest
Hiya
I recently bought a really powerful gaming PC and just under a year in whilst gaming (on 2 monitors) the pc images freeze and occasionally goes to black and the pc reboots itself, but many times i have to hard reboot it.
I see that it is linked to Kernal Power Error 41. IT is sporadic and keeps happening a lot.
Below is the analysed memory dump:
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. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff806664fa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
Debugging Details:
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2921
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G63KE67
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 3447
Key : Analysis.Memory.CommitPeak.Mb
Value: 81
Key : Analysis.System
Value: CreateObject
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
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff806664fa320
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
TRAP_FRAME: ffffed031e42ecc0 -- (.trap 0xffffed031e42ecc0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=ffffc981f1864990
rdx=ffffc981f0bdc000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8068332ce0b rsp=ffffed031e42ee50 rbp=ffffed031e42ef80
r8=fffff80683bfeb10 r9=ffffed031e42eeb0 r10=000000000000000d
r11=0000000000000004 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nvlddmkm+0xcce0b:
fffff806`8332ce0b 448bc0 mov r8d,eax
Resetting default scope
PROCESS_NAME: System
STACK_TEXT:
ffffb580`fe7f8e18 fffff806`65c3aa0c : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`664fa320 : nt!KeBugCheckEx
ffffb580`fe7f8e20 fffff806`65a6f9a3 : 00000140`c4d81282 ffffb580`fe1a8180 00000000`00000000 ffffb580`fe1a8180 : nt!KeAccumulateTicks+0x1c880c
ffffb580`fe7f8e80 fffff806`65a6f48a : ffffc981`e6b02480 ffffed03`1e42ed40 fffff806`7fc20200 00000000`00006001 : nt!KeClockInterruptNotify+0x453
ffffb580`fe7f8f30 fffff806`65b27ef5 : ffffc981`e6b02480 00000000`00000000 00000000`00000000 ffffc656`c4de0264 : nt!HalpTimerClockIpiRoutine+0x1a
ffffb580`fe7f8f60 fffff806`65bf722a : ffffed03`1e42ed40 ffffc981`e6b02480 ffffed03`1e42ef50 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffb580`fe7f8fb0 fffff806`65bf7797 : ffffc981`f0b35570 ffffc981`f1c5f000 ffffffff`00000000 00001fa0`00000202 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffed03`1e42ecc0 fffff806`8332ce0b : ffffed03`1e42efa0 ffffc981`f1c6d3f0 ffffa8bd`eb5d8d5a ffffc981`f1c6d3f0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffed03`1e42ee50 fffff806`8331b1a6 : ffffc981`f1c5f000 ffffc981`f1c6d3f0 00000140`00000000 00000000`00000002 : nvlddmkm+0xcce0b
ffffed03`1e42ee80 fffff806`65a0781e : ffffb580`fe1ab240 ffffc981`e6cec000 ffffed03`1e42f3f0 ffffb580`fe1a8180 : nvlddmkm+0xbb1a6
ffffed03`1e42f120 fffff806`65a06b04 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
ffffed03`1e42f290 fffff806`65bf92ee : ffffffff`00000000 ffffb580`fe1a8180 ffffb580`fe1b3540 ffffc981`e6b9a080 : nt!KiRetireDpcList+0x1f4
ffffed03`1e42f520 00000000`00000000 : ffffed03`1e430000 ffffed03`1e429000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e
SYMBOL_NAME: nvlddmkm+cce0b
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: cce0b
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}
Followup: MachineOwner
Any help would be brilliant. Thank you ever so much!
Continue reading...
I recently bought a really powerful gaming PC and just under a year in whilst gaming (on 2 monitors) the pc images freeze and occasionally goes to black and the pc reboots itself, but many times i have to hard reboot it.
I see that it is linked to Kernal Power Error 41. IT is sporadic and keeps happening a lot.
Below is the analysed memory dump:
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. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff806664fa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
Debugging Details:
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2921
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G63KE67
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 3447
Key : Analysis.Memory.CommitPeak.Mb
Value: 81
Key : Analysis.System
Value: CreateObject
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
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff806664fa320
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
TRAP_FRAME: ffffed031e42ecc0 -- (.trap 0xffffed031e42ecc0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=ffffc981f1864990
rdx=ffffc981f0bdc000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8068332ce0b rsp=ffffed031e42ee50 rbp=ffffed031e42ef80
r8=fffff80683bfeb10 r9=ffffed031e42eeb0 r10=000000000000000d
r11=0000000000000004 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nvlddmkm+0xcce0b:
fffff806`8332ce0b 448bc0 mov r8d,eax
Resetting default scope
PROCESS_NAME: System
STACK_TEXT:
ffffb580`fe7f8e18 fffff806`65c3aa0c : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`664fa320 : nt!KeBugCheckEx
ffffb580`fe7f8e20 fffff806`65a6f9a3 : 00000140`c4d81282 ffffb580`fe1a8180 00000000`00000000 ffffb580`fe1a8180 : nt!KeAccumulateTicks+0x1c880c
ffffb580`fe7f8e80 fffff806`65a6f48a : ffffc981`e6b02480 ffffed03`1e42ed40 fffff806`7fc20200 00000000`00006001 : nt!KeClockInterruptNotify+0x453
ffffb580`fe7f8f30 fffff806`65b27ef5 : ffffc981`e6b02480 00000000`00000000 00000000`00000000 ffffc656`c4de0264 : nt!HalpTimerClockIpiRoutine+0x1a
ffffb580`fe7f8f60 fffff806`65bf722a : ffffed03`1e42ed40 ffffc981`e6b02480 ffffed03`1e42ef50 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffb580`fe7f8fb0 fffff806`65bf7797 : ffffc981`f0b35570 ffffc981`f1c5f000 ffffffff`00000000 00001fa0`00000202 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffed03`1e42ecc0 fffff806`8332ce0b : ffffed03`1e42efa0 ffffc981`f1c6d3f0 ffffa8bd`eb5d8d5a ffffc981`f1c6d3f0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffed03`1e42ee50 fffff806`8331b1a6 : ffffc981`f1c5f000 ffffc981`f1c6d3f0 00000140`00000000 00000000`00000002 : nvlddmkm+0xcce0b
ffffed03`1e42ee80 fffff806`65a0781e : ffffb580`fe1ab240 ffffc981`e6cec000 ffffed03`1e42f3f0 ffffb580`fe1a8180 : nvlddmkm+0xbb1a6
ffffed03`1e42f120 fffff806`65a06b04 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
ffffed03`1e42f290 fffff806`65bf92ee : ffffffff`00000000 ffffb580`fe1a8180 ffffb580`fe1b3540 ffffc981`e6b9a080 : nt!KiRetireDpcList+0x1f4
ffffed03`1e42f520 00000000`00000000 : ffffed03`1e430000 ffffed03`1e429000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e
SYMBOL_NAME: nvlddmkm+cce0b
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: cce0b
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}
Followup: MachineOwner
Any help would be brilliant. Thank you ever so much!
Continue reading...