Solved BSOD Driver PNP Watchdog

Hey guys, Ive been on the dev channel of the insider programme, Everything was golden until the update that released( Cant remember the number) got rid of the spinning dots and replaced it with a circle ( Note : This is the update i had an issue with/since)
Ive read through some of the BSOD reports etc, some suggest that secure boot is off and fast boot is on, which i can assure you from my bios is not the case, Or so it says. ]
Windows version is 21h2(OS build 22000.168) or so it says.
Thanks
Michael

There was no mini dump file collected.

The logs indicate that there is an old 4 GB memory dump file.



The logs displayed GPU related problems since the Windows Education installation.

These could be software or hardware.


It's best to have a dump file rather than just a log report,

A dump file was not created in the latest crash.


The logs were cleaned just two days ago.

Please do not use Ccleaner or Windows cleanup during the troubleshooting process.

Open Ccleaner > click custom clean > scroll down to system and advanced > post images into this thread



How come there are no restore points with Windows RE disabled?

Which software if any is being used for backup images?



This script has not yet be uploaded to Eleven Forum (EF) so please log onto Ten Forums (TF) as needed to run it:

Tuneup_plus_log.bat ─ Click here to go to the BSOD batch repository to download and run this batch file.



Post a new V2 for any new crash.

zbook said:

There was no mini dump file collected.

The logs indicate that there is an old 4 GB memory dump file.



The logs displayed GPU related problems since the Windows Education installation.

These could be software or hardware.


It's best to have a dump file rather than just a log report,

A dump file was not created in the latest crash.


The logs were cleaned just two days ago.

Please do not use Ccleaner or Windows cleanup during the troubleshooting process.

Open Ccleaner > click custom clean > scroll down to system and advanced > post images into this thread



How come there are no restore points with Windows RE disabled?

Which software if any is being used for backup images?



This script has not yet be uploaded to Eleven Forum (EF) so please log onto Ten Forums (TF) as needed to run it:

Tuneup_plus_log.bat ─ Click here to go to the BSOD batch repository to download and run this batch file.



Post a new V2 for any new crash.

Click to expand...

Hey thanks for having a look, I've had some hardware failures relating to the gpu since installing win 11 as you say, I thought my gpu was possibly dying at one time but nothing has changed since and the only thing changed at all is the move from win 10 to 11 so ima say its fine xD,

Not sure why it didnt create a dump file, BSOD's etc arent my strong suit, I dont know why it didnt create one and im not sure how to make it create one.
Im also not sure how the logs were cleaned, this wasnt done by me at all( Im the only one who accesses the pc)

Also not sure why there are no restore points etc either buddy to be honest.

People prob gonna shout at me for this one, But i dont backup images, Never have.


This is from the batch file i ran as requested


Started on 20/09/2021 at 18:32:18.16

[SFC /ScanNow]

Beginning system scan. This process will take some time.

Results:

Windows Resource Protection did not find any integrity violations.

==================================================================

Started on 20/09/2021 at 18:34:14.10

[DISM /online /cleanup-image /ScanHealth]

Deployment Image Servicing and Management tool
Version: 10.0.22000.1

Image Version: 10.0.22000.168

No component store corruption detected.

The operation completed successfully.

==================================================================

Started on 20/09/2021 at 18:35:19.21

[DISM /online /cleanup-image /RestoreHealth]

Deployment Image Servicing and Management tool
Version: 10.0.22000.1

Image Version: 10.0.22000.168

The restore operation completed successfully.

The operation completed successfully.

==================================================================

The second "SFC /ScanNow" was skipped, as the first output the following:

Windows Resource Protection did not find any integrity violations.

==================================================================

Started on 20/09/2021 at 18:36:20.33

[ChkDsk /Scan]

The type of the file system is NTFS.
Volume label is M2.

Stage 1: Examining basic file system structure ...
1232384 file records processed.
File verification completed.
Phase duration (File record verification): 7.30 seconds.
14686 large file records processed.
Phase duration (Orphan file record recovery): 5.44 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.03 milliseconds.

Stage 2: Examining file name linkage ...
56270 reparse records processed.
1531096 index entries processed.
Index verification completed.
Phase duration (Index verification): 18.03 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 1.46 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.07 milliseconds.
56270 reparse records processed.
Phase duration (Reparse point and Object ID verification): 81.63 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 75.53 milliseconds.
149357 data files processed.
Phase duration (Data attribute verification): 0.04 milliseconds.
CHKDSK is verifying Usn Journal...
41906272 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 139.73 milliseconds.

Windows has scanned the file system and found no problems.

No further action is required.

999543807 KB total disk space.
914751764 KB in 758918 files.
418324 KB in 149358 indexes.
0 KB in bad sectors.
1383627 KB in use by the system.
65536 KB occupied by the log file.
82990092 KB available on disk.

4096 bytes in each allocation unit.
249885951 total allocation units on disk.
20747523 allocation units available on disk.
Total duration: 27.11 seconds (27110 ms).

==================================================================

Started on 20/09/2021 at 18:36:58.40

AutoReboot

TRUE

==================================================================

[Set AutoReboot = False]

Updating property(s) of '\\MICHAEL\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Education|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'

Property(s) update successful.

==================================================================

AutoReboot

FALSE

==================================================================

DebugInfoType

7

==================================================================

[Set DebugInfoType = 7]

Updating property(s) of '\\MICHAEL\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Education|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'

Property(s) update successful.

==================================================================

DebugInfoType

7

==================================================================

[WMIC PageFile list]

AllocatedBaseSize=8192
CurrentUsage=118
Description=C:\pagefile.sys
InstallDate=20200608160027.079222+000
Name=C:\pagefile.sys
PeakUsage=209
Status=
TempPageFile=FALSE

==================================================================

AutomaticManagedPagefile

TRUE

==================================================================

[Set AutomaticManagedPagefile = True]

Updating property(s) of '\\MICHAEL\ROOT\CIMV2:Win32_ComputerSystem.Name="MICHAEL"'

Property(s) update successful.

==================================================================

AutomaticManagedPagefile

TRUE

==================================================================

[BcdEdit /enum {badmemory}]

RAM Defects
-----------
identifier {badmemory}

==================================================================

Finished on 20/09/2021 at 18:36:59.31

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Also have attached the CCleaner image also, Which i havent ran for possibly maybe a few months?
Thanks again
Michael

For Ccleaner uncheck:
a) Memory Dumps
b) Windows Log Files


Create a new restore point:



Open administrative command prompt and type or copy and paste:

reagentc /info
reagentc /enable
reagentc /info

Post an image or share link of the commands with results.



For any unexpected shutdown and restart > run V2 > upload results into this thread

Done,
As for the restore point, I went in a checked and it actually comes up with a couple of auto ones but i made a new manual one too anyway,
Done that and it produced this.




As for unexpected shutdowns, Has only happened to this pc maybe once in the last year due to a gpu issue at one time, Only really hangs and BSOD'S on the windows update, Runs flawless elsewhere

Thanks Again for youre help!
Michael

Was this while attempting an upgrade in dev? The latest dev channel release notes have an open issue:

We’re working on a fix for an issue that is causing some devices to bug check with DRIVER_PNP_WATCHDOG error when attempting to update to a recent build.

geneo said:

Was this while attempting an upgrade in dev? The latest dev channel release notes have an open issue:

We’re working on a fix for an issue that is causing some devices to bug check with DRIVER_PNP_WATCHDOG error when attempting to update to a recent build.

Click to expand...

Yeah thats the one buddy, it started maybe a few dev updates ago, i didnt get maybe the last 2? and the one prior to that is the one that started it i believe

Update, I have rolled back to the beta channel on the insider, it came up with an update, installed no problem etc following the advised steps which was fine, Went back into dev, found update of course, re ran the process and the same driver pnp watchdog bsod again, So ima guess its just an issue with the update that some people have and some dont, Im happy with the beta channel until they fix it :) Thanks

Windows can malfunction with various dumps generated.

The log collector had collected:

a) memory dump: 4 GB > only BSOD file
b) livekernel: many




These were over one month old.

The memory dump was dated: 18/08/2021

The log files indicated that there was a BSOD yesterday 09/20/2021.
There was no dump file generated:




If there are new dump files they can be debugged.
Often the Microsoft database for troubleshooting is incomplete until there is a typical windows version release (scheduled Oct 5).

It did actually create some dump files this time i believe, ive attached them here, Thanks
Edit : Windows version is now 22000.194 as opposed to 22000.168 as it was when thread was created. I still get the bsod when updating on the newest DEV build to which the files below are from.

Please post images of the current restore points.
Use a share link as necessary: one drive, drop box, or google drive

Open administrative powershell and type or copy and paste:

get-computerrestorepoint
reagentc /info
reagentc /enable
reagentc /info

Post an image of the command with results into this thread.


The current windows version displayed in the logs: 10.0.22000
Windows 11 Education 64-bit (10.0, Build 22000) (22000.co_release.210604-1628)


The last recorded BSOD remained: 2021-09-20T15:24:30.1080000Z


To monitor for BSOD please use reliability monitor:

In saying that, I created a restore point yesterday, When checking today it just says there are none available which is weird.
As for powershell it came up with this.

V unusual its not showing any BSOD today when it was only a handful of hours ago :S.

Please run this Ten Forums script:

DiskParInfo.bat - Click here to go to the BSOD batch repository to download and run this batch file.


Post an image of disk management (widen each column as necessary so that no characters are cutoff)

Open administrative command prompt and type or copy and paste:

dir /a /s c:\winre.wim

Allow several minutes for it complete then post an image into this thread.



The problems that you're having may be best managed when Windows 11 is released on October 5, 2012.
(some may disappear with the official release of the new version)

Until then you can use the feedback hub to report problems:

Disk 0 : SSD. It has 4 partition(s). Model: ADATA SX8200PNP
Disk 1 : SSD. It has 5 partition(s). Model: Samsung SSD 850 EVO 250GB

The script has found the above 2 storage device(s) in total.
=======================================================================

Microsoft DiskPart version 10.0.22000.1

Copyright (C) Microsoft Corporation.
On computer: MICHAEL

Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 953 GB 0 B *
Disk 1 Online 232 GB 2048 KB *

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 C M2 NTFS Partition 953 GB Healthy Boot
Volume 1 NTFS Partition 529 MB Healthy Hidden
Volume 2 FAT32 Partition 99 MB Healthy System
Volume 3 D SAMSUNG EVO NTFS Partition 231 GB Healthy
Volume 4 NTFS Partition 450 MB Healthy Hidden
Volume 5 FAT32 Partition 99 MB Healthy Hidden
Volume 6 NTFS Partition 492 MB Healthy Hidden

Disk 0 is now the selected disk.

ADATA SX8200PNP
Disk ID: {DAE294EF-1552-4D51-9E65-6B7EB4DFE7FC}
Type : NVMe
Status : Online
Path : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1D00)#PCI(0000)#NVME(P00T00L00)
Current Read-only State : No
Read-only : No
Boot Disk : Yes
Pagefile Disk : Yes
Hibernation File Disk : No
Crashdump Disk : Yes
Clustered Disk : No

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 C M2 NTFS Partition 953 GB Healthy Boot
Volume 1 NTFS Partition 529 MB Healthy Hidden
Volume 2 FAT32 Partition 99 MB Healthy System

Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Recovery 529 MB 1024 KB
Partition 2 System 99 MB 530 MB
Partition 3 Reserved 16 MB 629 MB
Partition 4 Primary 953 GB 645 MB

Partition 1 is now the selected partition.

Partition 1
Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden : Yes
Required: Yes
Attrib : 0X8000000000000001
Offset in Bytes: 1048576

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 1 NTFS Partition 529 MB Healthy Hidden

Partition 2 is now the selected partition.

Partition 2
Type : c12a7328-f81f-11d2-ba4b-00a0c93ec93b
Hidden : Yes
Required: No
Attrib : 0X8000000000000000
Offset in Bytes: 555745280

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 2 FAT32 Partition 99 MB Healthy System

Partition 3 is now the selected partition.

Partition 3
Type : e3c9e316-0b5c-4db8-817d-f92df00215ae
Hidden : Yes
Required: No
Attrib : 0X8000000000000000
Offset in Bytes: 659554304

There is no volume associated with this partition.

Partition 4 is now the selected partition.

Partition 4
Type : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
Hidden : No
Required: No
Attrib : 0000000000000000
Offset in Bytes: 676331520

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 0 C M2 NTFS Partition 953 GB Healthy Boot

Disk 1 is now the selected disk.

Samsung SSD 850 EVO 250GB
Disk ID: {4DFD76F2-5E3F-4AFD-8E32-8728626021C4}
Type : SATA
Status : Online
Path : 0
Target : 1
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1700)#ATA(C00T01L00)
Current Read-only State : No
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 3 D SAMSUNG EVO NTFS Partition 231 GB Healthy
Volume 4 NTFS Partition 450 MB Healthy Hidden
Volume 5 FAT32 Partition 99 MB Healthy Hidden
Volume 6 NTFS Partition 492 MB Healthy Hidden

Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Recovery 450 MB 1024 KB
Partition 2 System 99 MB 451 MB
Partition 3 Reserved 16 MB 550 MB
Partition 4 Primary 231 GB 566 MB
Partition 5 Recovery 492 MB 232 GB

Partition 1 is now the selected partition.

Partition 1
Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden : Yes
Required: Yes
Attrib : 0X0000000000000001
Offset in Bytes: 1048576

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 4 NTFS Partition 450 MB Healthy Hidden

Partition 2 is now the selected partition.

Partition 2
Type : c12a7328-f81f-11d2-ba4b-00a0c93ec93b
Hidden : Yes
Required: No
Attrib : 0000000000000000
Offset in Bytes: 472907776

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 5 FAT32 Partition 99 MB Healthy Hidden

Partition 3 is now the selected partition.

Partition 3
Type : e3c9e316-0b5c-4db8-817d-f92df00215ae
Hidden : Yes
Required: No
Attrib : 0000000000000000
Offset in Bytes: 576716800

There is no volume associated with this partition.

Partition 4 is now the selected partition.

Partition 4
Type : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
Hidden : No
Required: No
Attrib : 0000000000000000
Offset in Bytes: 593494016

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 3 D SAMSUNG EVO NTFS Partition 231 GB Healthy

Partition 5 is now the selected partition.

Partition 5
Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden : Yes
Required: Yes
Attrib : 0X8000000000000001
Offset in Bytes: 249541165056

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 6 NTFS Partition 492 MB Healthy Hidden

===============================================================================

Windows Recovery Environment (Windows RE) and system reset configuration
Information:

Windows RE status: Disabled
Windows RE location:
Boot Configuration Data (BCD) identifier: 2ae4713d-d570-11eb-ba68-dc5b7350b294
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0

REAGENTC.EXE: Operation Successful.

===============================================================================

Firmware Boot Manager
---------------------
identifier {fwbootmgr}
displayorder {ee2deed5-f157-11eb-ba84-806e6f6e6963}
{bootmgr}
timeout 1

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager
locale en-GB
inherit {globalsettings}
flightsigning Yes
default {current}
resumeobject {2ae4713a-d570-11eb-ba68-dc5b7350b294}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Firmware Application (101fffff)
-------------------------------
identifier {ee2deed5-f157-11eb-ba84-806e6f6e6963}
device partition=\Device\HarddiskVolume7
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10
locale en-GB
inherit {bootloadersettings}
recoverysequence {2ae4713d-d570-11eb-ba68-dc5b7350b294}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
flightsigning Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {2ae4713a-d570-11eb-ba68-dc5b7350b294}
nx OptIn
bootmenupolicy Standard

Windows Boot Loader
-------------------
identifier {2ae4713d-d570-11eb-ba68-dc5b7350b294}
device ramdisk=[\Device\HarddiskVolume6]\Recovery\WindowsRE\Winre.wim,{2ae4713e-d570-11eb-ba68-dc5b7350b294}
path \windows\system32\winload.efi
description Windows Recovery Environment
locale en-GB
inherit {bootloadersettings}
displaymessage Recovery
osdevice ramdisk=[\Device\HarddiskVolume6]\Recovery\WindowsRE\Winre.wim,{2ae4713e-d570-11eb-ba68-dc5b7350b294}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes

Resume from Hibernate
---------------------
identifier {2ae4713a-d570-11eb-ba68-dc5b7350b294}
device partition=C:
path \WINDOWS\system32\winresume.efi
description Windows Resume Application
locale en-GB
inherit {resumeloadersettings}
recoverysequence {2ae4713d-d570-11eb-ba68-dc5b7350b294}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
custom:21000026 partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=\Device\HarddiskVolume7
path \EFI\Microsoft\Boot\memtest.efi
description Windows Memory Diagnostic
locale en-GB
inherit {globalsettings}
badmemoryaccess Yes

EMS Settings
------------
identifier {emssettings}
bootems No

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Local

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

Device options
--------------
identifier {2ae4713e-d570-11eb-ba68-dc5b7350b294}
description Windows Recovery
ramdisksdidevice partition=\Device\HarddiskVolume6
ramdisksdipath \Recovery\WindowsRE\boot.sdi



Thats from the batch file



Also the picture from the disk management and cmd

Were or are you dual booting?

Had the latest Windows installation or update been performed while both drives were installed?



In the left lower corner type: msconfig > click boot tab > post an image into this thread


Please open administrative command prompt and type or copy and paste:

dir /a /s d:\winre.wim

Post an image of the results.

zbook said:

Were or are you dual booting?

Had the latest Windows installation or update been performed while both drives were installed?



In the left lower corner type: msconfig > click boot tab > post an image into this thread


Please open administrative command prompt and type or copy and paste:

dir /a /s d:\winre.wim

Post an image of the results.

Click to expand...

Nah i have never dual booted, I did however at one time only have my samsung SSD which was loaded with windows 10 until around june last year i got some upgrades, including my m2 drive so windows 10 was loaded onto there by my local pc shop. Then i joined the win 11 insider whenever that launched the first dev version. Both drives have been in the pc for over a year together now, the SSD was in for around 2 years prior to the m2.

the usual option in this forum is clean install

tonez4466 said:

the usual option in this forum is clean install

Click to expand...

Its a known bug in the update according to microsofts notes, They know about it, i just wanted to know if there was something i could do to sort it, Its still an issue listed in todays dev build which released in the last half hour or so

Well maybe tomorrow an update with it fixed