win11 BSOD thread: DPC Watchdog Violation error

[stingo93]

version 21H2 (OS build 22000.493)

one drive link for the thread: DESKTOP-FMTV5MK-(2022-03-03_18-51-59).zip

thanks!

 

[stingo93]

I also run the DM Log collector and here is the link into the log:
log link
Event_logs-(2022-03-03_19-05-48).zip

Thanks!

 

[philc43]

Hello @stingo93 :)

I will look into this for you but I am going to need to analyse the memory.dmp file created by the crash. This one is not collected by the LOGS so please copy the file C:\Windows\memory.dmp to your desktop and then zip it and share it via OneDrive.

Thanks!

 

[philc43]

I have also had a look at your mini-dump crash files which are included in the logs and there does seem to be evidence that suggests the graphics driver is the most likely cause. The full memory.dmp should confirm this but if you wanted to try updating to the latest nVidia graphics driver this might actually fix the problem.

See this for the latest drivers: Latest NVIDIA GeForce Graphics Drivers for Windows 11

We recommend using DDU to uninstall the existing drivers but it is not always necessary.

Pending DPCs:
----------------------------------------
CPU Type      KDPC       Function
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvle.inf_amd64_bd9fe034c417866c\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
 0: Normal  : 0xffff9481453660e0 0xfffff80049a8313c nvlddmkm
 0: Normal  : 0xffff94814bc27610 0xfffff800492f9a40 nvlddmkm
 0: Normal  : 0xfffff382ffff6f60 0xfffff8002be8d0c0 nt!PopExecuteProcessorCallback
 0: Normal  : 0xfffff8002b1945d8 0xfffff8002bed4f10 nt!PpmPerfAction
Failed to read DPC at 0xffff948155986218
 0: Threaded: 0xfffff8002b194758 0xfffff8002be4d0d0 nt!KiDpcWatchdog

 

[zbook]

There were 5 mini dump files collected.

There were no memory dump files posted.

The mini dump debugging may be incomplete.

Two of the mini dump files indicated that netwtw10.sys was involved in the respective crashes.

It may have been a bystander or cause.

Other mini dump files indicated that nvlddmkm.sys was also involved in the crashes.

Once the memory dump file is available the misbehaving drivers should be clearer.

If you've used Windows Driver Verifier (WDV) it's an additional option in the debugging.

 

[jimbo45]

Hi there
You need one of these "Watch dogs" to prevent Nvidia updates at the moment -- there's been a few posts on the Forums about Nvidia drivers causing some issues with latest Windows updates.



Cheers
jimbo

 

[stingo93]

Hello @stingo93 :)

I will look into this for you but I am going to need to analyse the memory.dmp file created by the crash. This one is not collected by the LOGS so please copy the file C:\Windows\memory.dmp to your desktop and then zip it and share it via OneDrive.

Thanks!

There were 5 mini dump files collected.

There were no memory dump files posted.

The mini dump debugging may be incomplete.

Two of the mini dump files indicated that netwtw10.sys was involved in the respective crashes.

It may have been a bystander or cause.

Other mini dump files indicated that nvlddmkm.sys was also involved in the crashes.

Once the memory dump file is available the misbehaving drivers should be clearer.

If you've used Windows Driver Verifier (WDV) it's an additional option in the debugging.

Hi @philc43 and @zbook,
Thank you for the timely reply. In the link please find my memory dump.dmp file.
memory: MEMORY.zip

Thank you!
Stingo93

 

[zbook]

Please perform the following steps:


1) Run:

https://aka.ms/GetPCHealthCheckApp

Post images or share links displaying each of the compatibility checks and results.



2) Uninstall and reinstall the Nvidia GPU drivers: Nvlddmkm.sys

a) Uninstall using DDU
Make sure that you check the clean install box and if available install the physx driver.

Display Driver Uninstaller: How to use

How to Use Display Driver Uninstaller to Uninstall any Installed Display Driver

www.sevenforums.com

Display Driver Uninstaller (DDU)

Drivers removal utility and other tools.

www.wagnardsoft.com

b) Reinstall using the Nvidia website

Download the latest official NVIDIA drivers

Download the latest official NVIDIA drivers

www.nvidia.com

3) Download and install Intel Diver and Support Assistant:

Intel® Driver & Support Assistant

This application for the Intel® Driver & Support Assistant enables you to scan computing devices for the latest drivers available from Intel. (22.5.33.3)

www.intel.com

4) Uninstall Intel Wi-Fi 6 AX200: netwtw10.sys

Reinstall using Intel Driver and Support Assistant.




5) The BIOS: Version/Date LENOVO O4NKT14A, 6/9/2020

Upgrade the BIOS: 14A > 19A

BIOS for Windows 10 (64-bit) - Legion R5-28IMB05 Desktop, Legion T5-28IMB05 Desktop - Lenovo Support US

pcsupport.lenovo.com

6) Run:

a) The Lenovo Automatic driver update tool:

desktops and all in ones :: legion series :: legion t5 28imb05contentdetail - Lenovo Support US

pcsupport.lenovo.com

b) Windows updates and reboot

Name    [00000002] Intel(R) Wi-Fi 6 AX200 160MHz
Adapter Type    Ethernet 802.3
Product Type    Intel(R) Wi-Fi 6 AX200 160MHz
PNP Device ID    PCI\VEN_8086&DEV_2723&SUBSYS_00808086&REV_1A\4&57B0124&0&00D8
Service Name    Netwtw10.
Driver    C:\WINDOWS\SYSTEM32\DRIVERS\NETWTW10.SYS (22.110.1.1, 4.72 MB (4,954,184 bytes), 2/24/2022 3:54 PM)

netwtw10    ___ Intel(R) Wireless Adapter Driver for Windows 10 - 64 Bit    c:\windows\system32\drivers\netwtw10.sys

Name    NVIDIA GeForce GTX 1660 SUPER
PNP Device ID    PCI\VEN_10DE&DEV_21C4&SUBSYS_37971462&REV_A1\4&22AA181&0&0008
Adapter Type    NVIDIA GeForce GTX 1660 SUPER, NVIDIA compatible
Adapter Description    NVIDIA GeForce GTX 1660 SUPER
Adapter RAM    (1,048,576) bytes
Installed Drivers    C:\WINDOWS\System32\DriverStore\FileRepository\nvle.inf_amd64_bd9fe034c417866c\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvle.inf_amd64_bd9fe034c417866c\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvle.inf_amd64_bd9fe034c417866c\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvle.inf_amd64_bd9fe034c417866c\nvldumdx.dll
Driver Version    30.0.14.7239
INF File    oem31.inf (Section025 section)
Driver    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NVLE.INF_AMD64_BD9FE034C417866C\NVLDDMKM.SYS (30.0.14.7239, 35.78 MB (37,515,392 bytes), 2/7/2022 11:40 AM)

nvlddmkm    nvlddmkm    c:\windows\system32\driverstore\filerepository\nvle.inf_amd64_bd9fe034c417866c\nvlddmkm.sys

 

[philc43]

Hello @stingo93 :)

I have looked at the full memory dump and the information on the deferred procedure calls (DPCs) is rather better.

Pending DPCs:
----------------------------------------
CPU Type      KDPC       Function
 0: Normal  : 0xffff9481453660e0 0xfffff80049a8313c nvlddmkm
 0: Normal  : 0xffff94814bc27610 0xfffff800492f9a40 nvlddmkm
 0: Normal  : 0xfffff382ffff6f60 0xfffff8002be8d0c0 nt!PopExecuteProcessorCallback
 0: Normal  : 0xfffff8002b1945d8 0xfffff8002bed4f10 nt!PpmPerfAction
 0: Normal  : 0xffff948155986218 0xfffff80092714350 MpKslDrv
 0: Normal  : 0xffff9481451f66e8 0xfffff800452a6cb0 dxgkrnl!DpiFdoDpcForIsr
 0: Normal  : 0xffff94813c141c40 0xfffff8002be32a10 nt!KiDpcRuntimeHistoryHashTableCleanupDpcRoutine
 0: Normal  : 0xfffff38302606f60 0xfffff8002be8d0c0 nt!PopExecuteProcessorCallback
 0: Normal  : 0xffff948143b890b8 0xfffff800322c68b0 tcpip!TcpPeriodicTimeoutHandler
 0: Normal  : 0xffff94814f631aa0 0xfffff80092356d90 Ndu!NduQueryStatisticsDpc
 0: Normal  : 0xfffff38301046f60 0xfffff8002be8d0c0 nt!PopExecuteProcessorCallback
 0: Normal  : 0xfffff38300976f60 0xfffff8002be8d0c0 nt!PopExecuteProcessorCallback
 0: Threaded: 0xfffff8002b194758 0xfffff8002be4d0d0 nt!KiDpcWatchdog

I was hoping to be able to extract the Circular Kernel Context Logger history and analyse the data in Windows Performance Analyser to see which one was causing the timeout but for some reason I have been unable to get this information.
I did get this data on the logger analysis:

DPC Watchdog Captures Analysis for CPU #0.
   DPC Watchdog capture size: 641 stacks.
   Number of unique stacks: 350.
Most common function: fffff8002c01a16e  nt!KiIdleLoop+0x9E

List of functions that exist often in the Watchdog record:
Module Name    Function Name                            #Stack  #Of Occurrences
ACPI           ACPIGpeEnableDisableEvents               000     109 (of 266)
nt             KiInterruptSubDispatch                   006     11 (of 26)

List of functions that are called often in the Watchdog record:
Module Name    Function Name                            #Stack  #Of Occurrences
ACPI           ACPIInterruptServiceRoutine              001     338 (of 338)
nt             KiChainedDispatch                        028     6 (of 6)
dxgkrnl        DpiFdoLineInterruptRoutine               122     2 (of 2)

I would begin with the nvlddmkm graphics driver update and see if this stops the BSODs. If it does not help we can look at some other drivers based on the above list. The fact that tcpip shows up is interesting as this often is a clue that network drivers might be involved. The ACPI functions relate to power management and plug and play devices.

 

[stingo93]

Hi @zbook,

Thank you very much for the clear instructions. I have followed it and updated my Nvidia GPU drivers, WIFI and BIOS. Finally I run Lenovo Automatic driver update tool and it said no drivers need to be updated.

However, the blue screen error is still happening with the same code: DPC Watchdog Violation. Could you advise me fixing it?

I also upload the memory.dmp (memory) and log (log) for your diagnosis.

Thanks,
Stingo

 

[zbook]

The memory dump from 03/14/2022 was debugged.
There were three misbehaving drivers seen in the raw stack: nvlddmkm.sys and netwtw10.sys and ibtusb.sys

The logs displayed the installation of AMD GPU drivers.
If the switch to AMD GPU was after 3/14 then the problematic driver may have already been removed.
If the switch to AMD GPU was before 3/13 then the Nvidia GPU drivers were incompletely removed.
Please indicate the timing of the switch from one GPU card to the other.

The netwtw10.sys was replaced earlier in the thread and was likely a bystander in this crash.

Please uninstall the Nvidia GPU driver using DDU.

Wagnardsoft

Wagnardsoft : Computer software (DDU, ISLC), support and news.

www.wagnardsoft.com

Uninstall the Intel Bluetooth driver and reinstall using the Intel Driver and Support Assistant.

Intel® Driver & Support Assistant

This application for the Intel® Driver & Support Assistant enables you to scan computing devices for the latest drivers available from Intel. (22.5.33.3)

www.intel.com

Name    [00000001] Intel(R) Wi-Fi 6 AX200 160MHz
Adapter Type    Ethernet 802.3
Product Type    Intel(R) Wi-Fi 6 AX200 160MHz
PNP Device ID    PCI\VEN_8086&DEV_2723&SUBSYS_00848086&REV_1A\4&303B37F5&0&0012
Service Name    Netwtw10.
Driver    C:\WINDOWS\SYSTEM32\DRIVERS\NETWTW10.SYS (22.110.1.1, 4.73 MB (4,955,248 bytes), 1/8/2022 8:55 PM)

netwtw10    ___ Intel(R) Wireless Adapter Driver for Windows 10 - 64 Bit    c:\windows\system32\drivers\netwtw10.sys

ibtusb    Intel(R) Wireless Bluetooth(R)    c:\windows\system32\driverstore\filerepository\ibtusb.inf_amd64_0e6c4115aef06163\ibtusb.sys

ibtusb.sys   Mon Jan 17 08:55:01 2022 (61E59F65)

Netwtw10.sys Mon Jan  3 01:20:10 2022 (61D2BFCA)

nvlddmkm.sys Thu Jan 27 23:50:31 2022 (61F3A047)

 

[x BlueRobot]

Your dump file type doesn't seem quite right, it's a bitmap file? Could you please provide a screenshot of your dump file settings? The most reliable way to debug this variation of Stop 0x133 is to get a ETL trace and then check what DPCs are cumulatively taking a considerable time to complete. Unfortunately, the dump file isn't allowing WinDbg to parse that information and save it.