question

Adil-3232 avatar image
0 Votes"
Adil-3232 asked Adil-3232 published

DPC Watchdog Violation

I have been getting the DPC Watchdog Violation for a while now. Tried most of the solutions that I could find on the internet. Even tried factory resetting the pc but that didn't help.

Upload of the dump file
https://1drv.ms/u/s!Av2ODNp33wjYoELa36CmWI2gooUd?e=RspHbx

Getting the following when reading the memory.dmp

 Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
 Copyright (c) Microsoft Corporation. All rights reserved.
    
    
 Loading Dump File [C:\WINDOWS\MEMORY.DMP]
 Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
    
 Dump completed successfully, progress percentage: 100
    
    
 ************* Path validation summary **************
 Response                         Time (ms)     Location
 Deferred                                       srv*
 Symbol search path is: srv*
 Executable search path is: 
 Windows 10 Kernel Version 22000 MP (16 procs) Free x64
 Product: WinNt, suite: TerminalServer SingleUserTS Personal
 Edition build lab: 22000.1.amd64fre.co_release.210604-1628
 Machine Name:
 Kernel base = 0xfffff806`15c00000 PsLoadedModuleList = 0xfffff806`16829730
 Debug session time: Sun Jul 31 20:28:50.450 2022 (UTC + 2:00)
 System Uptime: 0 days 1:06:20.219
 Loading Kernel Symbols
 ...............................................................
 ................................................................
 ................................................................
 ................................
 Loading User Symbols
    
 Loading unloaded module list
 ................
 For analysis of this file, run !analyze -v
 nt!KeBugCheckEx:
 fffff806`16017d20 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffb900`2f5e0de0=0000000000000133
 7: kd> !analyze -v
 *******************************************************************************
 *                                                                             *
 *                        Bugcheck Analysis                                    *
 *                                                                             *
 *******************************************************************************
    
 DPC_WATCHDOG_VIOLATION (133)
 The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
 or above.
 Arguments:
 Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
  component can usually be identified with a stack trace.
 Arg2: 0000000000000501, The DPC time count (in ticks).
 Arg3: 0000000000000500, The DPC time allotment (in ticks).
 Arg4: fffff80616905330, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
  additional information regarding this single DPC timeout
    
 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: 3483
    
     Key  : Analysis.DebugAnalysisManager
     Value: Create
    
     Key  : Analysis.Elapsed.mSec
     Value: 3576
    
     Key  : Analysis.Init.CPU.mSec
     Value: 359
    
     Key  : Analysis.Init.Elapsed.mSec
     Value: 6447
    
     Key  : Analysis.Memory.CommitPeak.Mb
     Value: 103
    
     Key  : Bugcheck.Code.DumpHeader
     Value: 0x133
    
     Key  : Bugcheck.Code.KiBugCheckData
     Value: 0x133
    
     Key  : Bugcheck.Code.Register
     Value: 0x133
    
     Key  : Dump.Attributes.AsUlong
     Value: 1000
    
     Key  : WER.OS.Branch
     Value: co_release
    
     Key  : WER.OS.Timestamp
     Value: 2021-06-04T16:28:00Z
    
     Key  : WER.OS.Version
     Value: 10.0.22000.1
    
    
 FILE_IN_CAB:  MEMORY.DMP
    
 DUMP_FILE_ATTRIBUTES: 0x1000
    
 BUGCHECK_CODE:  133
    
 BUGCHECK_P1: 0
    
 BUGCHECK_P2: 501
    
 BUGCHECK_P3: 500
    
 BUGCHECK_P4: fffff80616905330
    
 DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED
    
 TRAP_FRAME:  fffff50e33a8e330 -- (.trap 0xfffff50e33a8e330)
 NOTE: The trap frame does not contain all registers.
 Some register values may be zeroed or incorrect.
 rax=0000000000ac0095 rbx=0000000000000000 rcx=0000000000000002
 rdx=ffffcd073bef6230 rsi=0000000000000000 rdi=0000000000000000
 rip=fffff80615e8c250 rsp=fffff50e33a8e4c0 rbp=ffffcd073bef6230
  r8=000000000000000c  r9=0000000000000000 r10=ffffcd07386c3ba8
 r11=ffffb9002f574180 r12=0000000000000000 r13=0000000000000000
 r14=0000000000000000 r15=0000000000000000
 iopl=0         nv up ei pl nz na pe nc
 nt!KeInsertPriQueue+0x3f0:
 fffff806`15e8c250 418b0424        mov     eax,dword ptr [r12] ds:00000000`00000000=????????
 Resetting default scope
    
 BLACKBOXBSD: 1 (!blackboxbsd)
    
    
 BLACKBOXNTFS: 1 (!blackboxntfs)
    
    
 BLACKBOXPNP: 1 (!blackboxpnp)
    
    
 BLACKBOXWINLOGON: 1
    
 PROCESS_NAME:  System
    
 STACK_TEXT:  
 ffffb900`2f5e0dd8 fffff806`15eb737e     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
 ffffb900`2f5e0de0 fffff806`15eb6e01     : 00000a87`4a6067a4 ffffb900`00000500 00000000`00000002 fffff806`15eb258e : nt!KeAccumulateTicks+0x39e
 ffffb900`2f5e0e50 fffff806`15eb4fea     : ffffb900`2f57d200 fffff50e`33a8e330 ffffb900`2f57d388 fffff806`15f1c7fb : nt!KiUpdateRunTime+0x61
 ffffb900`2f5e0eb0 fffff806`15eb4dd6     : ffffcd07`38748ec0 ffffcd07`38748f70 00000000`00000003 00000000`00000000 : nt!KeClockInterruptNotify+0x11a
 ffffb900`2f5e0f40 fffff806`15e913d0     : 00000000`00000000 ffff559a`ed3ef9f4 ffffcd07`3bef6230 00000000`00000000 : nt!HalpTimerClockIpiRoutine+0x16
 ffffb900`2f5e0f70 fffff806`1601992a     : fffff50e`33a8e3b0 ffffcd07`38748ec0 00000000`00000000 ffffcd07`3bef6230 : nt!KiCallInterruptServiceRoutine+0xa0
 ffffb900`2f5e0fb0 fffff806`16019ef7     : 00000000`00000030 00000010`00059cf8 00000000`00000000 00000000`00000004 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
 fffff50e`33a8e330 fffff806`15e8c250     : 00000000`00000000 00000000`00000001 fffff806`1a71ad90 00000000`00000600 : nt!KiInterruptDispatchNoLockNoEtw+0x37
 fffff50e`33a8e4c0 fffff806`15e8ba5a     : 00000000`00000040 ffffcd07`3bef6230 00000000`00000600 ffffcd07`00000000 : nt!KeInsertPriQueue+0x3f0
 fffff50e`33a8e550 fffff806`15e8b93b     : 00000000`00000000 00000000`00000000 ffffcd07`59cf90a0 fffff806`1a71ad90 : nt!ExQueueWorkItemFromIo+0x10a
 fffff50e`33a8e5b0 fffff806`1a4640e2     : fffff806`1a7592b0 00000000`00000000 fffff50e`33a8e705 fffff806`1a58eb98 : nt!IoQueueWorkItemEx+0x1b
 fffff50e`33a8e5e0 fffff806`1a58ea76     : 00000000`0000001b 00000000`00000000 fffff50e`33a8e705 00000000`00000000 : NETIO!NetioInsertWorkQueue+0x62
 fffff50e`33a8e630 fffff806`1a58e74b     : fffff50e`33a8eb01 fffff50e`33a8e770 00000000`00000000 ffffcd07`3bfa89e0 : tcpip!WfpAlepAuthTelemetry+0xce
 fffff50e`33a8e670 fffff806`1a58de06     : ffffcd07`4c6a5801 00000000`00000030 ffffcd07`4c6a58a0 00000000`00000002 : tcpip!WfpAlepReauthorizeOutboundConnection+0x87f
 fffff50e`33a8e840 fffff806`1a58c542     : ffffcd07`4c6a58a0 00000000`00000000 00000000`00000001 fffff50e`33a8ec40 : tcpip!WfpAleReauthorizeOutboundConnection+0x1ee
 fffff50e`33a8e9b0 fffff806`1a5e20d9     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!WfpAleReauthorizeConnection+0x356
 fffff50e`33a8eb70 fffff806`1a563210     : ffffcd07`4c6a58a0 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!AleInspectTcpDatagram+0x181
 fffff50e`33a8ece0 fffff806`1a561e4b     : fffff50e`33a8f350 00000014`00000007 ffffcd07`5616a8e0 ffffcd07`4c6a5b18 : tcpip!IppInspectLocalDatagramsOut+0xae0
 fffff50e`33a8efe0 fffff806`1a5712ea     : ffffcd07`3bfce500 fffff806`1a553c40 fffff806`1a74ba10 ffffcd07`4c6a58a0 : tcpip!IppSendDatagramsCommon+0x40b
 fffff50e`33a8f180 fffff806`1a57940c     : 00000000`00000000 00000000`00000007 fffff50e`00000010 00000000`003c6e2b : tcpip!TcpTcbSend+0x72a
 fffff50e`33a8f4f0 fffff806`15ea74a1     : fffff50e`33a8fa00 00000000`00000007 ffffb900`2f5774c0 ffffb900`2f574180 : tcpip!TcpPeriodicTimeoutHandler+0x153c
 fffff50e`33a8f690 fffff806`15ea64a2     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x491
 fffff50e`33a8f890 fffff806`1601bc6e     : 00000000`00000000 ffffb900`2f574180 ffffb900`2f580440 ffffcd07`5477b0c0 : nt!KiRetireDpcList+0x2a2
 fffff50e`33a8fb40 00000000`00000000     : fffff50e`33a90000 fffff50e`33a89000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e
    
    
 SYMBOL_NAME:  NETIO!NetioInsertWorkQueue+62
    
 MODULE_NAME: NETIO
    
 IMAGE_NAME:  NETIO.SYS
    
 STACK_COMMAND:  .cxr; .ecxr ; kb
    
 BUCKET_ID_FUNC_OFFSET:  62
    
 FAILURE_BUCKET_ID:  0x133_DPC_NETIO!NetioInsertWorkQueue
    
 OS_VERSION:  10.0.22000.1
    
 BUILDLAB_STR:  co_release
    
 OSPLATFORM_TYPE:  x64
    
 OSNAME:  Windows 10
    
 FAILURE_ID_HASH:  {0ebba73e-63d8-cb04-b209-0e24c2781f59}
    
 Followup:     MachineOwner
 ---------
windows-11
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Docs-4663 avatar image
1 Vote"
Docs-4663 answered Adil-3232 edited

The latest BSOD was bugcheck 50 and was caused by an older Nvidia GPU driver.



Some of the Live kernel event bugchecks seen in the logs were:


117 Bug Check 0x117: VIDEO_TDR_TIMEOUT_DETECTED
141 Bug Check 0x141: VIDEO_ENGINE_TIMEOUT_DETECTED
193 Bug Check 0x193: VIDEO_DXGKRNL_LIVEDUMP




With multiple BSOD and different driver versions for Nvidia GPU driver nvlddmkm.sys it is important to identify any malfunctioning hardware before the warranty expires.

Contact Lenovo now to report recurrent BSOD with Windows 11.

This includes multiple BSOD caused by different versions of Nvidia GPU drivers.

This typically is caused by malfunctioning GPU.

It can also be caused by a malfunctioning motherboard however there is no option for the computer user to swap test the GPU in a laptop.


If Lenovo accepts the multiple recurrent BSOD as malfunctioning hardware then request a Return Merchandise Authorization (RMA).

If Lenovo insists on additional testing the continue with the steps later in this thread.



Windows 11 backup images can be made and restored so that the laptop can be tested with Windows 10.

If possible, plan to use Windows 10 for a week and after testing restore a Windows 11 image.


The testing of the Nvidia GPU drivers and hardware can be repeated by upgrading to Windows 11.

Once testing has completed a backed up Windows 11 image can be restored.



If there are BSOD related to Nvidia GPU with both Windows 11 and Windows 10 then this confirms malfunctioning hardware.


If Lenovo does not require a clean install of either Windows 11 or Windows 10 for testing and authorizes a RMA then you can skip all further testing.





1) Turn off WDV


2) Make free backup images using Macrium and save the images to another disk drive or the cloud
https://www.tenforums.com/tutorials/61026-backup-restore-macrium-reflect.html


3) Find a flash drive that you can format ( > or = 8 GB)


4) Create a bootable Windows 10 iso
https://www.tenforums.com/tutorials/2376-create-bootable-usb-flash-drive-install-windows-10-a.html
https://www.tenforums.com/tutorials/9230-download-windows-10-iso-file.html
https://www.microsoft.com/en-us/software-download/windows10


3) Clean install Windows 10
https://www.tenforums.com/tutorials/1950-clean-install-windows-10-a.html
Do not install any drivers at this time.
Later, plan to install drivers from the Nvidia website during the testing


4) Restart WDV


5) If there is no BSOD then post a new querysettings into the newest post


6) For any BSOD
a) Post a new V2 share link into the newest post
b) Post a new compressed memory dump share link into the newest post (separate share link)




Name NVIDIA GeForce RTX 2070 SUPER
PNP Device ID PCI\VEN_10DE&DEV_1E84&SUBSYS_C72B1462&REV_A1\4&3292EEB7&0&0008
Adapter Type GeForce RTX 2070 SUPER, NVIDIA compatible
Adapter Description NVIDIA GeForce RTX 2070 SUPER
Adapter RAM (1 048 576) bytes
Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\nvle.inf_amd64_c4410ab03e8e99d7\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvle.inf_amd64_c4410ab03e8e99d7\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvle.inf_amd64_c4410ab03e8e99d7\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvle.inf_amd64_c4410ab03e8e99d7\nvldumdx.dll
Driver Version 27.21.14.5785
INF File oem18.inf (Section021 section)
Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NVLE.INF_AMD64_C4410AB03E8E99D7\NVLDDMKM.SYS (27.21.14.5785, 31,53 MB (33 056 416 bytes), 2022-08-06 14:10)


.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @Docs-4663,

I'll contact Lenovo regarding this.
The thing is I have had this problem before upgrading to windows 11, had the BSOD with windows 10 as well.

But I'll check with Lenovo and see what can be done.
Again thank you very much for the help.

0 Votes 0 ·
Docs-4663 avatar image
1 Vote"
Docs-4663 answered Adil-3232 commented

Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

https://www.elevenforum.com/t/bsod-posting-instructions.103/

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @Docs-4663,

Here is the link to the zip file from V2 log collector.
https://1drv.ms/u/s!Av2ODNp33wjYoEPoDplvqskPer2x?e=eN6uxd

0 Votes 0 ·
Docs-4663 avatar image
1 Vote"
Docs-4663 answered Adil-3232 commented

Please run:

(bat files by default prompt antivirus software and require manual overrides)

a) https://www.tenforums.com/attachments/bsod-crashes-debugging/360137d1645183388-batch-files-use-bsod-debugging-tuneup_plus_log.bat

b) https://www.elevenforum.com/resources/gather-additional-dump-files.5/

Post share links into this thread that include the above script results.



Open administrative command prompt and copy and paste:

PowerShell $D=(New-Object -ComObject Wscript.Shell).SpecialFolders(4);Compress-Archive "%WinDir%\MEMORY.DMP" "$D\Memory_dmp"

Post a separate share link into this thread that only has the compressed memory dump.
(Please make sure that this is a separate share link and that it does not include any other files)


.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Docs-4663 avatar image
1 Vote"
Docs-4663 answered Adil-3232 edited

First scannow: Windows Resource Protection found corrupt files and successfully repaired them.

Second scannow: Windows Resource Protection did not find any integrity violations.



See if this link works: (may require Ten Forums logon)
https://www.tenforums.com/attachments/bsod-crashes-debugging/358470d1643456903-batch-files-use-bsod-debugging-gather_additional_dump_files.bat

Post a share link into this thread using one drive, drop box, or google drive.

(The memory dump seems to have the data needed for the troubleshooting but if available I'd still like to view the live kernel event files)



1) The BIOS: Version/Date LENOVO O4NKT14A, 2020-06-09

Upgrade the BIOS: 14A > 19A

https://pcsupport.lenovo.com/us/en/products/desktops-and-all-in-ones/legion-series/legion-t5-28imb05/downloads/ds544035-bios-for-windows-10-64-bit-legion-r5-28imb05-desktop-legion-t5-28imb05-desktop?category=BIOS%2FUEFI




2) Turn off Windows fast startup:
https://www.elevenforum.com/t/turn-on-or-off-fast-startup-in-windows-11.1212/



3) Uninstall the Nvidia GPU driver nvlddmkm.sys using Display Driver Uninstaller (DDU).

Reinstall from the Nvidia website.

Make sure that the clean install box is checked and if available install the physx driver.

https://www.wagnardsoft.com/display-driver-uninstaller-ddu-

https://www.sevenforums.com/tutorials/367109-display-driver-uninstaller-how-use.html

https://www.nvidia.com/download/index.aspx




4) Uninstall and reinstall:

ibtusb.sys
Intel Wireless Bluetooth



5) Uninstall Kaspersky AV software using the applicable uninstall tool:
https://support.kaspersky.com/common/uninstall/12783
https://support.kaspersky.com/common/uninstall/1464


Kaspersky AV can be reinstalled or you can use Microsoft Defender.

https://www.taylorwessing.com/en/insights-and-events/insights/2022/03/bsi-warning-against-products-from-kaspersky#:~:text=The%20German%20Federal%20Office%20for,the%20company%20should%20be%20replaced.

https://www.avast.com/c-is-kaspersky-safe




ibtusb Intel(R) Wireless Bluetooth(R) c:\windows\system32\driverstore\filerepository\ibtusb.inf_amd64_c274fcae8cc5c71d\ibtusb.sys Kernel Driver Yes Manual Running OK Normal No Yes


.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @Docs-4663,

Here is the link to the live kernel event files
https://1drv.ms/u/s!Av2ODNp33wjYoEYq6FdDOwK_wte1?e=k8c4zE

0 Votes 0 ·

Hi @Docs-4663,

I have upgraded the BIOS


The computer did freeze (which happens before I get the BSOD) after the BIOS upgrade but it didn't happen directly but happened after a while, but probably wasn't related to it.
227364-image.png

I have turned off Windows fast start-up
227347-image.png

Uninstalled the Nvidia GPU driver nvlddmkm.sys using Display Driver Uninstaller (DDU) and reinstalled Nvidia GPU driver from the Nvidia website.

Uninstalled and reinstall ibtusb.sys Intel Wireless Bluetooth


Uninstalled Kaspersky AV software using the applicable uninstall tool which you sent the link to.
I installed Avast free antivirus instead.


Didn't understand your last comment
ibtusb Intel(R) Wireless Bluetooth(R) c:\windows\system32\driverstore\filerepository\ibtusb.inf_amd64_c274fcae8cc5c71d\ibtusb.sys Kernel Driver Yes Manual Running OK Normal No Yes


0 Votes 0 ·
image.png (140.5 KiB)
image.png (35.8 KiB)

Hi @Docs-4663,

Still getting the BSOD DPC Watchdog Violation.
The loading of the BSOD reached 100% completion and it seems it got stuck there for a long time so I shut the computer down using the powebutton on the pc.

0 Votes 0 ·
Docs-4663 avatar image
1 Vote"
Docs-4663 answered Adil-3232 commented

The script results included a text file without a dump file.

On the bottom of posts you may see information that was related to the recent troubleshooting.
These typically are findings.
In the earlier post it was one of the misbehaving drivers.


For any BSOD:
a) Post a new V2 log collector share link into the newest post



Make a new restore point:
https://www.elevenforum.com/t/create-system-restore-point-in-windows-11.3602/


Read this link on Windows Driver Verifier (WDV):
https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html

Learn how to recover from using the tool by booting in to safe mode and running one or more of these commands:
verifier /reset
verifier /bootmode resetonbootfail

If there is no immediate BSOD then open administrative command prompt and type or copy and paste: verifier /querysettings
Post a share link into this thread using one drive, drop box, or google drive.


.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @Docs-4663,

Gotten following error message when running the V2 log collector
227520-image.png

But the V2 still manages to collect the logs,
https://1drv.ms/u/s!Av2ODNp33wjYoEfGiwoh3M3C7FHb?e=OTqSQd

0 Votes 0 ·
image.png (216.1 KiB)

Hi @Docs-4663,

The Windows Driver Verifier is running and after reboot I got no BSOD
227613-image.png


0 Votes 0 ·
image.png (128.8 KiB)

Hi @Docs-4663,

Here is results with the dump file as well from
https://www.tenforums.com/attachments/bsod-crashes-debugging/358470d1643456903-batch-files-use-bsod-debugging-gather_additional_dump_files.bat

https://1drv.ms/u/s!Av2ODNp33wjYoEhRonZ5jW2B9j_h?e=bCsIE1

Windows Driver Verifier is still running and there hasn't been any BSOD.
There has actually been no BSOD since the last one yesterday.
Seems like maybe everything is working.
I'll keep you updated

0 Votes 0 ·
Docs-4663 avatar image
1 Vote"
Docs-4663 answered Adil-3232 edited

Multiple files were missing from the latest V2 run.

During the troubleshooting please uninstall third party antivirus software with the applicable uninstall tool.
https://support.avast.com/en-nz/article/Uninstall-Antivirus#pc
https://support.avast.com/en-us/article/uninstall-antivirus-utility/#pc


Make sure that Microsoft Defender is on.

These steps should enable the V2 log collector to collect all of it's script files.


What had happened the first time when the getadditional dump files script ran?
It only had the text file.

The second time it had included the dump file.


The debugging displayed misbehaving Kaspersky antivirus drivers.

These drivers were uninstalled earlier in the thread.





If there were no major performance problems or very slow boot then modify the WDV customized tests to:

 [ ] 0x00000001 Special pool.
 [ ] 0x00000002 Force IRQL checking.
 [ ] 0x00000008 Pool tracking.
 [ ] 0x00000010 I/O verification.
 [ ] 0x00000020 Deadlock detection.
 [ ] 0x00000080 DMA checking.
 [ ] 0x00000100 Security checks.
 [ ] 0x00000800 Miscellaneous checks.
 [ ] 0x00020000 DDI compliance checking.
 [ ] 0x00000200 Force pending I/O requests.
 [ ] 0x00000400 IRP logging.
 [ ] 0x00080000 DDI compliance checking (additional).


If there is no immediate BSOD then post a new querysettings share link.

For any BSOD post a new V2 share link.


If there are no major performance problems with the above customized tests then modify the customized tests to include all customized tests except:

 [ ] 0x00000004 Randomized low resources simulation.


If there is no immediate BSOD then post a new querysettings share link.

For any BSOD post a new V2 share link.

Run these settings for 24 hours.

If there are no BSOD then turn off WDV.

This will conclude the troubleshooting.


So far the misbehaving drivers were:
Nvidia GPU and Kaspersky AV drivers.
Nvidia GPU drivers were replaced and Kaspersky AV drivers were uninstalled.



.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.


· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @Docs-4663,

I had added the dump file manually instead.

I have uninstalled Avast now
I'll run the WDV again with the settings you have mentioned.

0 Votes 0 ·

Hi @Docs-4663,228104-querysetttings.txt

Here is the querysettings for the second run.

228185-image.png


0 Votes 0 ·
querysetttings.txt (2.4 KiB)
image.png (109.0 KiB)

Hi @Docs-4663,

When running the WDV the third time with all the settings selected except for

  [ ] 0x00000004 Randomized low resources simulation.

I got the BSOD.
BSOD was stuck at 100% completion for awhile so had to shut the pc down using the power button and use system restore to disable the WDV.

V2 share link:
https://1drv.ms/u/s!Av2ODNp33wjYoEk1YcuhjQj64A9g?e=UkxK4u

0 Votes 0 ·

Hi @Docs-4663,

I have gotten another BSOD from normal usage.

V2 share link:
https://1drv.ms/u/s!Av2ODNp33wjYoEoo0nSpcIytZu6T?e=NL6Bjg

Noticing that all BSOD that I get now are getting stuck at 100% and never restarts the computer.

I tried running the WDV again the BSOD from normal usage with the following settings:

  [ ] 0x00000001 Special pool.
  [ ] 0x00000002 Force IRQL checking.
  [ ] 0x00000008 Pool tracking.
  [ ] 0x00000010 I/O verification.
  [ ] 0x00000020 Deadlock detection.
  [ ] 0x00000080 DMA checking.
  [ ] 0x00000100 Security checks.
  [ ] 0x00000800 Miscellaneous checks.
  [ ] 0x00020000 DDI compliance checking.
  [ ] 0x00000200 Force pending I/O requests.
  [ ] 0x00000400 IRP logging.
  [ ] 0x00080000 DDI compliance checking (additional).


And there were no BSOD.
228292-image.png


0 Votes 0 ·
image.png (107.3 KiB)
Docs-4663 avatar image
1 Vote"
Docs-4663 answered Adil-3232 commented

The misbehaving driver was vgk.sys.

1) Please uninstall Vanguard / Valorant Riot software / games.

https://support-valorant.riotgames.com/hc/en-us/articles/360044648213-Uninstalling-and-Disabling-Riot-Vanguard


2) Make a new restore point


3) Restart WDV selecting all customized tests except
[ ] 0x00000004 Randomized low resources simulation.

4) Run the tool continuously for 24 hours.

5) If there is no immediate BSOD post a new querysettings share link

6) For any BSOD post a new V2 share link

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @Docs-4663,

I have uninstalled Vanguard / Valorant Riot software and ran WDV selecting all customized tests except
[ ] 0x00000004 Randomized low resources simulation.

Got another BSOD when running the WDV

V2 share link
https://1drv.ms/u/s!Av2ODNp33wjYoEsbsRk5Jiqwf-Cd?e=1LgJK1

0 Votes 0 ·
Docs-4663 avatar image
1 Vote"
Docs-4663 answered Adil-3232 commented

1) Uninstall or uninstall and reinstall all of the Razer software:

RzDev_025.sys or rzcommon.sys

rzdev_025a Razer 025a Service c:\windows\system32\drivers\rzdev_025a.sys
rzdev_025b Razer 025b Service c:\windows\system32\drivers\rzdev_025b.sys
rzdev_025c Razer 025c Service c:\windows\system32\drivers\rzdev_025c.sys


2) Make a new restore point


3) Restart WDV selecting all customized tests except
[ ] 0x00000004 Randomized low resources simulation.

4) Run the tool continuously for 24 hours.

5) If there is no immediate BSOD post a new querysettings share link

6) For any BSOD post a new V2 share link

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @Docs-4663,

I reinstalled Razer Synapse and tried running the WDV but got BSOD immediately after restart,
So I uninstalled Razer Synapse and tried running the WDV, this time it is working and no BSOD so far.
I checked online and it seems like other have had their Razer software cause BSOD as well.
I'll update you after 24h of running the WDV.
Thank you very much for the time and effort you have put to help me.
Seems like there were multiple causes for the BSOD.
Is there a way to select multiple answers?
So far I can only select one thread as an answer.

228573-image.png


0 Votes 0 ·
image.png (113.1 KiB)

Hi @Docs-4663,

Got BSOD but this did not have the stop code Watchdog Violation instead it was SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.
What failed: ndis.sys

The WDV is still running.

V2 share link
https://1drv.ms/u/s!Av2ODNp33wjYoEwjYtJdq-PcoSs7?e=U6wxWQ

0 Votes 0 ·

Hi @Docs-4663,

Got another BSOD, this was DPC Watchdog Violation

I have stopped running WDV.

V2 share link
https://1drv.ms/u/s!Av2ODNp33wjYoE3P9x0m3kHcV9fn?e=P2FNmW

0 Votes 0 ·
Docs-4663 avatar image
1 Vote"
Docs-4663 answered Adil-3232 published




There were three mini dump files collected by the most recent run the V2 log collector.
They were all while running WDV.
The first were the Razer drivers as per the most recent post.
The second was a recurrent hardware driver: Nvidia GPU nvlddmkm.sys
The third was without a misbehaving driver.



Please perform the following steps:

1) Open administrative command prompt and copy and paste:

PowerShell $D=(New-Object -ComObject Wscript.Shell).SpecialFolders(4);Compress-Archive "%WinDir%\MEMORY.DMP" "$D\Memory_dmp"

Post a separate share link into this thread that only has the compressed memory dump.



2) Uninstall the Nvidia GPU nvlddmkm.sys using Display Driver Uninstaller (DDU)

Reinstall the Nvidia GPU driver using the Lenovo website.

27.21.14.6231 27 May 2021


3) Make a new restore point


4) Restart WDV

Post a new V2 share link for any BSOD.

Plan to run WDV continuously for 24 hours after replacing the driver..






Name NVIDIA GeForce RTX 2070 SUPER
PNP Device ID PCI\VEN_10DE&DEV_1E84&SUBSYS_C72B1462&REV_A1\4&3292EEB7&0&0008
Adapter Type NVIDIA GeForce RTX 2070 SUPER, NVIDIA compatible
Adapter Description NVIDIA GeForce RTX 2070 SUPER
Adapter RAM (1 048 576) bytes
Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\nvleig.inf_amd64_6370d798d320e1c6\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvleig.inf_amd64_6370d798d320e1c6\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvleig.inf_amd64_6370d798d320e1c6\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvleig.inf_amd64_6370d798d320e1c6\nvldumdx.dll
Driver Version 31.0.15.1659
INF File oem18.inf (Section011 section)
Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NVLEIG.INF_AMD64_6370D798D320E1C6\NVLDDMKM.SYS (31.0.15.1659, 41,69 MB (43 718 120 bytes), 2022-08-02 18:47)

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @Docs-4663,

I have uninstalled NVidia GPU
driver and installed the version you mention via Lenovo site
https://pcsupport.lenovo.com/se/en/products/desktops-and-all-in-ones/legion-series/legion-t5-28imb05/90nc/90nc008bmw/s1019ufl/downloads/driver-list/component?name=Graphics%20Processing%20Units%20%28GPU%29%20and%20Server-AI%20Accelerators

After installation I was changing the resolution of the screen and then got a BSOD
Stop code: PAGE_FAULT_IN_NONPAGED_AREA
What failed: nvlddmkm.sys

V2 share link:
https://1drv.ms/u/s!Av2ODNp33wjYoE98fnV3L_y4Re_b?e=UWvZnW

another memorydump share link:
https://1drv.ms/u/s!Av2ODNp33wjYoFAa7IIHcJ2Ndnde?e=kbneiP



0 Votes 0 ·

Hi @Docs-4663,

The WDV is running:
228690-image.png


0 Votes 0 ·
image.png (112.9 KiB)