DPC_WATCHDOG_VIOLATION (0x133,1,1e00,0fb320,0)

H

hansfett98

New member
Joined
Nov 4, 2021
Posts
3
Dear All,

I have this DPC_WATCHDOG_VIOLATION Blue Screen. Sometimes the Computer runs fine for 15 days and sometimes it crashs three times a day... It just happens very randomly. Last time it crashed when I was writing a Mail. Then it crashed when surfing. Then it crashed when using my CAD program....

I'm so close to think it's a hardware issue, since I've tried so many things:
- Run Antivirus check and now only using defender from microsoft
- Run instant Upgrade from Windows 10
- Update all the driver, Bios and so on.
- Run Chkdsk, sfc scannow

Computer Specs:
Lenovo Legion T5 28IMB05
Intel Core i7-10700, 16 GB, 512 GB SSD, 1 TB HDD,
nVidia GeForce RTX 2070 Super

Download Memory Dump from https://www.buchli-it.ch/memory.dmp

!analyze -v from memory.dmp

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: fffff8032a0fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*************************************************************************
*** ***
*** ***
*** 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: 2452

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2523

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

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

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

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: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8032a0fb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME: ffff8f8fe61e26c0 -- (.trap 0xffff8f8fe61e26c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffff8032cbf1f98
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803296d79cc rsp=ffff8f8fe61e2850 rbp=ffff8f8fe61e29a9
r8=0000000000000000 r9=0000000000040408 r10=fffff803296d7910
r11=ffffd28f1df19ef8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KxWaitForSpinLockAndAcquire+0x2c:
fffff803`296d79cc 488b07 mov rax,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffff9a01`fbeaee18 fffff803`2981f57e : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`2a0fb320 : nt!KeBugCheckEx
ffff9a01`fbeaee20 fffff803`29616953 : 000000b7`7e8e811f ffff9a01`fbe5c180 00000000`00000000 ffff9a01`fbe5c180 : nt!KeAccumulateTicks+0x2063ce
ffff9a01`fbeaee80 fffff803`2961643a : ffffd28f`178ec040 ffff8f8f`e61e2740 00000000`00000000 ffffd28f`178c74c0 : nt!KeClockInterruptNotify+0x453
ffff9a01`fbeaef30 fffff803`296de055 : ffffd28f`178ec040 fffff803`29752447 00000000`00000000 00000000`00000000 : nt!HalpTimerClockIpiRoutine+0x1a
ffff9a01`fbeaef60 fffff803`297f8c5a : ffff8f8f`e61e2740 ffffd28f`178ec040 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff9a01`fbeaefb0 fffff803`297f91c7 : 00000000`d7e68fd6 fffff803`2cb92490 ffffd28f`23845010 ffffd28f`23845010 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8f8f`e61e26c0 fffff803`296d79cc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8f8f`e61e2850 fffff803`296d7998 : fffff803`2cbf1f98 ffff9a01`fbe5c180 00000000`00000000 00000000`00000000 : nt!KxWaitForSpinLockAndAcquire+0x2c
ffff8f8f`e61e2880 fffff803`2cba0bab : ffffd28f`23845198 00000000`00040408 00000000`00000000 ffffd28f`23845198 : nt!KeAcquireSpinLockRaiseToDpc+0x88
ffff8f8f`e61e28b0 fffff803`2cb75243 : ffffd28f`23845010 ffffd28f`00040408 ffffd28f`23845198 00000000`00000100 : ACPI!ACPIInterruptEventCompletion+0x2b
ffff8f8f`e61e28e0 fffff803`2cb74685 : ffffd28f`17dc8000 ffffd28f`23845010 00000000`00000000 00000000`00000032 : ACPI!RunContext+0x833
ffff8f8f`e61e2a10 fffff803`2cb9a325 : ffffd28f`23845010 00000000`00000080 ffffd28f`23845010 00000000`000001d2 : ACPI!InsertReadyQueue+0x2a5
ffff8f8f`e61e2a70 fffff803`2cb98c97 : fffff803`2cbf2790 00000000`00000000 00000000`00000000 ffff8f8f`e63a7c00 : ACPI!RestartCtxtPassive+0x35
ffff8f8f`e61e2aa0 fffff803`29755855 : ffffd28f`178c74c0 fffff803`2cb98b90 00000000`00000000 ffffd28f`178b3140 : ACPI!ACPIWorkerThread+0x107
ffff8f8f`e61e2b10 fffff803`297fe808 : ffff9a01`fbe5c180 ffffd28f`178c74c0 fffff803`29755800 05ebd88b`af758b4c : nt!PspSystemThreadStartup+0x55
ffff8f8f`e61e2b60 00000000`00000000 : ffff8f8f`e61e3000 ffff8f8f`e61dc000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: ACPI!ACPIInterruptEventCompletion+2b

MODULE_NAME: ACPI

IMAGE_NAME: ACPI.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 2b

FAILURE_BUCKET_ID: 0x133_ISR_ACPI!ACPIInterruptEventCompletion

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {66ccecbc-0d7a-4186-e177-11481af8fb9f}

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

11: kd> !dpcwatchdog

All durations are in seconds (1 System tick = 15.625000 milliseconds)

Circular Kernel Context Logger history: !logdump 0x2
DPC and ISR stats (total since boot): !intstats /d
DPC and ISR stats (during DPC watchdog period): !intstats /w

--------------------------------------------------
CPU#0
--------------------------------------------------
Current DPC: ACPI!ACPIInterruptDispatchEventDpc (Normal DPC)
Debugger Saved IRQL: 15
Cumulative DPC Time Limit: 120.000 seconds
Current Cumulative DPC Time: 120.000 seconds
Single DPC Time Limit: 20.000 seconds
Current Single DPC Time: 0.500 seconds
dt nt!_ISRDPCSTATS fffff8032a0f3a10
IsrActive: TRUE

Pending DPCs:
----------------------------------------
CPU Type KDPC Function
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvlei.inf_amd64_31ecf038806d15fe\nvlddmkm.sys, Win32 error 0n2
Page 44c6f6 not present in the dump file. Type ".hh dbgerr004" for details
Page 44c6f6 not present in the dump file. Type ".hh dbgerr004" for details
0: Normal : 0xffffd28f23d440e0 0xfffff80346220d1c nvlddmkm
0: Normal : 0xffffd28f2357acb0 0xfffff80345a998b4 nvlddmkm
0: Normal : 0xfffff8032a020e00 0xfffff8032961fef0 nt!PpmCheckPeriodicStart
0: Normal : 0xfffff8032a031f20 0xfffff80329728ed0 nt!KiBalanceSetManagerDeferredRoutine
0: Normal : 0xffffd28f178cad30 0xfffff80329728c90 nt!ExpCenturyDpcRoutine


DPC Watchdog Captures Analysis for CPU #0.
DPC Watchdog capture size: 641 stacks.
Number of unique stacks: 298.
Most common function: fffff803297f8d21 nt!KiInterruptDispatch+0xB1

List of functions that exist often in the Watchdog record:
Module Name Function Name #Stack #Of Occurrences
nt KiInterruptSubDispatch 018 74 (of 151)
ACPI READ_PM1_STATUS 004 34 (of 68)

List of functions that are called often in the Watchdog record:
Module Name Function Name #Stack #Of Occurrences
ACPI ACPIInterruptServiceRoutine 003 223 (of 223)
HDAudBus HdaController::Isr 019 68 (of 68)
nt KiDpcInterruptBypass 070 3 (of 3)
dxgkrnl DpiFdoLineInterruptRoutine 270 2 (of 2)

--------------------------------------------------
CPU#1
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function

dpcs: no pending DPCs found

--------------------------------------------------
CPU#2
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function

dpcs: no pending DPCs found

--------------------------------------------------
CPU#3
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function

dpcs: no pending DPCs found

--------------------------------------------------
CPU#4
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function

dpcs: no pending DPCs found

--------------------------------------------------
CPU#5
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function

dpcs: no pending DPCs found

--------------------------------------------------
CPU#6
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function

dpcs: no pending DPCs found

--------------------------------------------------
CPU#7
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function

dpcs: no pending DPCs found

--------------------------------------------------
CPU#8
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function

dpcs: no pending DPCs found

--------------------------------------------------
CPU#9
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function

dpcs: no pending DPCs found

--------------------------------------------------
CPU#10
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function

dpcs: no pending DPCs found

--------------------------------------------------
CPU#11
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function
11: Normal : 0xffff9a01fbe64868 0xfffff803297515c0 nt!KiEntropyDpcRoutine


DPC Watchdog Captures Analysis for CPU #11.
DPC Watchdog capture size: 641 stacks.
Number of unique stacks: 1.
No common functions detected!

The captured stacks seem to indicate that only a single DPC or generic function is the culprit.
Try to analyse what other processors were doing at the time of the following reference capture:
CPU #11 DPC Watchdog Reference Stack (#0 of 641) - Profiling started at time since boot: 4 Min 15 Sec 593.75 mSec
# RetAddr Call Site
00 fffff8032961643a nt!KeClockInterruptNotify+0x453
01 fffff803296de055 nt!HalpTimerClockIpiRoutine+0x1A
02 fffff803297f8c5a nt!KiCallInterruptServiceRoutine+0xA5
03 fffff803297f91c7 nt!KiInterruptSubDispatchNoLockNoEtw+0xFA
04 fffff803296d79cc nt!KiInterruptDispatchNoLockNoEtw+0x37
05 fffff803296d7998 nt!KxWaitForSpinLockAndAcquire+0x2C
06 fffff8032cba0bab nt!KeAcquireSpinLockRaiseToDpc+0x88
07 fffff8032cb75243 ACPI!ACPIInterruptEventCompletion+0x2B
08 fffff8032cb74685 ACPI!RunContext+0x833
09 fffff8032cb9a325 ACPI!InsertReadyQueue+0x2A5
0a fffff8032cb98c97 ACPI!RestartCtxtPassive+0x35
0b fffff80329755855 ACPI!ACPIWorkerThread+0x107
0c fffff803297fe808 nt!PspSystemThreadStartup+0x55
0d ---------------- nt!KiStartSystemThread+0x28

--------------------------------------------------
CPU#12
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function

dpcs: no pending DPCs found

--------------------------------------------------
CPU#13
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function

dpcs: no pending DPCs found

--------------------------------------------------
CPU#14
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function

dpcs: no pending DPCs found

--------------------------------------------------
CPU#15
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function

dpcs: no pending DPCs found
 

Attachments

Last edited:
There were no dump files collected.

The logs were in a foreign language and were not scanned.

The RAM is overclocked at 3200.

The Intel CPU:
Product Specifications
DDR4-2933

Please return all overclocks to stock.
And turn off XMP during the troubleshooting.
 
@x BlueRobot and @zbook

Thanks for the answer. Please check the updated Link bellow:

https://buchli-it.ch/MEMORY.zip
zbook said:
The RAM is overclocked at 3200.

The Intel CPU:
Product Specifications
DDR4-2933

Please return all overclocks to stock.
And turn off XMP during the troubleshooting.
Click to expand...

This is funny that the RAM should be overclocked... This RAM comes prebuild from the vendor and I have not changed anything at all. Still I might do a BIOS Reset to defaults.

so DDR4-2933 ist actually the maximum memory speed which is supported by this CPU or what does it mean? Could 3200 not be the nativ speed of the rigs?

Best Regards
 
Overclocks and high temperatures can be seen with BSOD.

When troubleshooting BSOD it's best to eliminate these factors.

The problems caused by misbehaving drivers, malfunctioning hardware, and BIOS are then easier to identify.

Once the computer is stable XMP settings and or overclocks can be used.


What is XMP | Extreme Memory Profile | Crucial.com


Please perform the following steps:

1) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
2) re-install the Nvidia GPU driver from the Nvidia website
3) make sure that you check the clean install box and if available install the physx driver.

Display Driver Uninstaller Download version 18.0.4.3 (or newer version if available)
Wagnardsoft

Download Drivers | NVIDIA
Download Drivers | NVIDIA



For any new BSOD please post a new zipped memory dump if the file size is < 2GB.





Code: 
kd> !dpcs
CPU Type      KDPC       Function
Page 44c6f6 not present in the dump file. Type ".hh dbgerr004" for details
Page 44c6f6 not present in the dump file. Type ".hh dbgerr004" for details
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 0: Normal  : 0xffffd28f23d440e0 0xfffff80346220d1c nvlddmkm
 0: Normal  : 0xffffd28f2357acb0 0xfffff80345a998b4 nvlddmkm
 0: Normal  : 0xfffff8032a020e00 0xfffff8032961fef0 nt!PpmCheckPeriodicStart
 0: Normal  : 0xfffff8032a031f20 0xfffff80329728ed0 nt!KiBalanceSetManagerDeferredRoutine
 0: Normal  : 0xffffd28f178cad30 0xfffff80329728c90 nt!ExpCenturyDpcRoutine


Code: 
kd> lmDvmnvlddmkm
Browse full module list
start             end                 module name
fffff803`45a10000 fffff803`47e75000   nvlddmkm   (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\System32\DriverStore\FileRepository\nvlei.inf_amd64_31ecf038806d15fe\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Aug 27 05:45:03 2021 (6128DE4F)
    CheckSum:         023BD732
    ImageSize:        02465000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
 
hansfett98 said:
This is funny that the RAM should be overclocked... This RAM comes prebuild from the vendor and I have not changed anything at all. Still I might do a BIOS Reset to defaults.

so DDR4-2933 ist actually the maximum memory speed which is supported by this CPU or what does it mean? Could 3200 not be the nativ speed of the rigs?

Best Regards
Click to expand...
It is overclocked as in it goes beyond the SPD speed which is the default speed the RAM will run at if no XMP profile is selected. I can't find official specs of your RAM model to confirm, but usually the SPD speed is somewhere around 2400 with DDR4.

DDR4-2933 indicates the maximum speed the CPU supports; this is not my area of expertise, but I don't think it automatically means if you go beyond it, problems will occur. It just means that is the maximum speed the vendor has tested to be stable I believe.
 
For some reason, the log trace from your dump file is corrupted and unable to parse using WPA.

Rich (BB code): 
11: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffff9a01`fbeaee18 fffff803`2981f57e nt!KeBugCheckEx
01 ffff9a01`fbeaee20 fffff803`29616953 nt!KeAccumulateTicks+0x2063ce
02 ffff9a01`fbeaee80 fffff803`2961643a nt!KeClockInterruptNotify+0x453
03 ffff9a01`fbeaef30 fffff803`296de055 nt!HalpTimerClockIpiRoutine+0x1a
04 ffff9a01`fbeaef60 fffff803`297f8c5a nt!KiCallInterruptServiceRoutine+0xa5
05 ffff9a01`fbeaefb0 fffff803`297f91c7 nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
06 ffff8f8f`e61e26c0 fffff803`296d79cc nt!KiInterruptDispatchNoLockNoEtw+0x37
07 ffff8f8f`e61e2850 fffff803`296d7998 nt!KxWaitForSpinLockAndAcquire+0x2c
08 ffff8f8f`e61e2880 fffff803`2cba0bab nt!KeAcquireSpinLockRaiseToDpc+0x88
09 ffff8f8f`e61e28b0 fffff803`2cb75243 ACPI!ACPIInterruptEventCompletion+0x2b
0a ffff8f8f`e61e28e0 fffff803`2cb74685 ACPI!RunContext+0x833
0b ffff8f8f`e61e2a10 fffff803`2cb9a325 ACPI!InsertReadyQueue+0x2a5
0c ffff8f8f`e61e2a70 fffff803`2cb98c97 ACPI!RestartCtxtPassive+0x35
0d ffff8f8f`e61e2aa0 fffff803`29755855 ACPI!ACPIWorkerThread+0x107
0e ffff8f8f`e61e2b10 fffff803`297fe808 nt!PspSystemThreadStartup+0x55
0f ffff8f8f`e61e2b60 00000000`00000000 nt!KiStartSystemThread+0x28

Judging from the call stack, it seems that a driver is endlessly waiting on a spinlock which is then causing a DPC timeout error, hence the bugcheck. Unfortunately, this issue is going to much more difficult to debug without a WPA trace to use since the issue is a cumulative DPC timeout rather than a single DPC timeout.

Rich (BB code): 
11: kd> !dpcwatchdog

All durations are in seconds (1 System tick = 15.625000 milliseconds)

Circular Kernel Context Logger history: !logdump 0x2
DPC and ISR stats (total since boot): !intstats /d
DPC and ISR stats (during DPC watchdog period): !intstats /w

--------------------------------------------------
CPU#0
--------------------------------------------------
Current DPC: ACPI!ACPIInterruptDispatchEventDpc (Normal DPC)
Debugger Saved IRQL: 15
Cumulative DPC Time Limit: 120.000 seconds
Current Cumulative DPC Time: 120.000 seconds
Single DPC Time Limit: 20.000 seconds
Current Single DPC Time: 0.500 seconds
dt nt!_ISRDPCSTATS fffff8032a0f3a10
IsrActive: TRUE

Notice how the cumulative timeout limit is reached and not the single one? That's why you can't use !dpcwatchdog here.

Although, I've dug a little deeper, and it seems there might have been another bugcheck while the system was preparing the Stop 0x133 bugcheck. If you check the context saved on the first process (0), you'll notice that there is a Stop 0x80 being thrown which is typically due to some form of hardware failure. The !analyze -v command defaults to processor 11 for some reason, yet the processor context is set to processor 0 which would have been the last crash.

Rich (BB code): 
11: kd> ~0
0: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff803`2ec83b58 fffff803`298b443a nt!KeBugCheckEx << Stop 0x80
01 fffff803`2ec83b60 fffff803`270915b0 nt!HalBugCheckSystem+0x7a
02 fffff803`2ec83ba0 fffff803`299b612e PSHED!PshedBugCheckSystem+0x10
03 fffff803`2ec83bd0 fffff803`298b8af2 nt!WheaReportHwError+0x46e
04 fffff803`2ec83cb0 fffff803`2990d882 nt!HalHandleNMI+0x142
05 fffff803`2ec83ce0 fffff803`29802882 nt!KiProcessNMI+0x132
06 fffff803`2ec83d30 fffff803`29802652 nt!KxNmiInterrupt+0x82
07 fffff803`2ec83e70 fffff803`297f753c nt!KiNmiInterrupt+0x212
08 fffff803`2ec6e0e8 fffff803`29918c45 nt!KiSaveProcessorControlState+0x3c
09 fffff803`2ec6e0f0 fffff803`2990d32a nt!KiFreezeTargetExecution+0x145
0a fffff803`2ec6e200 fffff803`29912479 nt!KiCheckForFreezeExecution+0x2a
0b fffff803`2ec6e230 fffff803`297f72b7 nt!KeBugCheck2+0xcc9
0c fffff803`2ec6e940 fffff803`2981f57e nt!KeBugCheckEx+0x107 << Stop 0x133
0d fffff803`2ec6e980 fffff803`2961c3cd nt!KeAccumulateTicks+0x2063ce
0e fffff803`2ec6e9e0 fffff803`2961c971 nt!KiUpdateRunTime+0x5d
0f fffff803`2ec6ea30 fffff803`296167e3 nt!KiUpdateTime+0x4a1
10 fffff803`2ec6eb70 fffff803`2961f1a2 nt!KeClockInterruptNotify+0x2e3
11 fffff803`2ec6ec20 fffff803`296de055 nt!HalpTimerClockInterrupt+0xe2
12 fffff803`2ec6ec50 fffff803`297f8c5a nt!KiCallInterruptServiceRoutine+0xa5
13 fffff803`2ec6eca0 fffff803`297f91c7 nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
14 fffff803`2ec6ecf0 fffff803`297976d9 nt!KiInterruptDispatchNoLockNoEtw+0x37
15 fffff803`2ec6ee88 fffff803`29796ca9 nt!HalpAcpiPmRegisterReadPort+0x9
16 fffff803`2ec6ee90 fffff803`2cb9671a nt!HalpAcpiPmRegisterRead+0x39
17 fffff803`2ec6eec0 fffff803`2cb95c94 ACPI!ACPIReadGpeStatusRegister+0x66
18 fffff803`2ec6ef00 fffff803`296de055 ACPI!ACPIInterruptServiceRoutine+0x54
19 fffff803`2ec6ef40 fffff803`297f89df nt!KiCallInterruptServiceRoutine+0xa5
1a fffff803`2ec6ef90 fffff803`297f8ca7 nt!KiInterruptSubDispatch+0x11f
1b fffff803`2ec67870 fffff803`2977bcdc nt!KiInterruptDispatch+0x37
1c fffff803`2ec67a08 fffff803`2977a6f9 nt!HalpAcpiPmRegisterWritePort+0xc
1d fffff803`2ec67a10 fffff803`2cb9644b nt!HalpAcpiPmRegisterWrite+0x39
1e fffff803`2ec67a40 fffff803`2cb963b7 ACPI!ACPIWriteGpeEnableRegister+0x6f
1f fffff803`2ec67a80 fffff803`2cb95fcf ACPI!ACPIGpeEnableDisableEvents+0x37
20 fffff803`2ec67ab0 fffff803`2969a24e ACPI!ACPIInterruptDispatchEventDpc+0x1bf << DPC from the !dpcwatchdog command
21 fffff803`2ec67bb0 fffff803`29699534 nt!KiExecuteAllDpcs+0x30e
22 fffff803`2ec67d20 fffff803`297fe1f5 nt!KiRetireDpcList+0x1f4
23 fffff803`2ec67fb0 fffff803`297fdfe0 nt!KxRetireDpcList+0x5
24 ffff8f8f`e909f9c0 fffff803`297fd895 nt!KiDispatchInterruptContinue
25 ffff8f8f`e909f9f0 fffff803`297f8d21 nt!KiDpcInterruptBypass+0x25
26 ffff8f8f`e909fa00 00007ff8`bab2b967 nt!KiInterruptDispatch+0xb1
27 0000002f`278ff9d8 00000000`00000000 0x00007ff8`bab2b967

zbook said:
Please perform the following steps:

1) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
2) re-install the Nvidia GPU driver from the Nvidia website
3) make sure that you check the clean install box and if available install the physx driver.

Display Driver Uninstaller Download version 18.0.4.3 (or newer version if available)
Wagnardsoft

Download Drivers | NVIDIA
Download Drivers | NVIDIA
Click to expand...
That isn't the issue. You've just looked at the pending DPC queue rather than the actual DPC which was running at the time of the crash.
 
The Stop 0x80 crash may explain why the trace is potentially corrupt and why WPA gives the following error:

1636115458212.png
 
thank you guys so much for sharing your thoughts with me
Click to expand...

@x BlueRobot
I've found more minidumps from the affected system:
https://www.buchli-it.ch/Minidumps.zip

are they also corrupted?

Could it be a graphic driver issue? In the Memory dump it sais something like this:
Pending DPCs:
----------------------------------------
CPU Type KDPC Function
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvlei.inf_amd64_31ecf038806d15fe\nvlddmkm.sys, Win32 error 0n2
 
All "pending DPCs" indicates is that the display driver has a few DPCs pending for execution, however the 0x133 (both variants) is due to DPC(s) currently being executed taking too much time.

Minidumps do not have sufficient data required to analyze a 0x133 where multiple DPCs caused the crash. You can try it yourself by running this command below on a minidump, most likely it will return the error "Failed to Find Logger" because a lot of traces are not present in minidumps and the one needed is Circular Kernel Context Logger.
Code: 
!wmitrace.logsave 2 C:\users\log.etl
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top