Upgrade to 2004 green sceen driver_pnp_watchdog - rolls back

banger · 02 May 2020

Trying to upgrade my HP 250 Laptop (system 2 in specs) from 1909 to RP 2004 but keep getting a green screen which says driver_PNP_watchdog and rolls back. Tried disabling Bluetooth and wifi driver but same problem. I have just updated the Intel 620 driver so wondering if it is this. Setupdiag logs are attached, please point me in the right direction for other log collectors.

SetupDiagResults.log

Here is the V2 logs

LAPTOPX64-(2020-05-02_17-15-46).zip

zbook · 02 May 2020

Hi banger,

The computer had 3 recent BSOD.
The windows upgrade failure code was: 0xC1900101-0x30017

The setupdiag usually has multiple log files in the results and these were missing.
If possible please post a share link for these files.

Please perform the following steps:

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

13) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

14) Identify the HP software related to these then uninstall and reinstall:
a) C:\Program Files (x86)\HP\HP Support Framework\Resources\HPWarrantyCheck\HPWarrantyChecker.exe
b) C:\Program Files\HPCommRecovery\HPCommRecovery.exe

15) Uninstall ESET using the applicable uninstall tool:
[KB2289] Uninstall ESET manually using the ESET uninstaller tool

16) Make a new restore point:
Create System Restore Point in Windows 10

17) Read these links on Windows driver verifier:
Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

18) Learn how to use the Windows Recovery Environment (RE) reset and bootmode commands to turn off and recover from using the tool

19) Do not use the tool until it is communicated in the thread

20) For any BSOD
a) Run the V2 log collector and upload resuts directy into this thread
b) Open file explorer > this PC > C: > in the right upper corner search for C:\windows\memory.dmp > if the file size is < 1.5 GB then zip and post a separate share link into the thread using one drive, drop box, or google drive.

21) Windows driver verifier is designed to stress test drivers.

If there are misbehaving drivers the computer will crash.

If dump files are created they can be debugged.

Misbehaving drivers are then uninstalled and reinstalled.

The tool is run for 48 hours and then an additional 36 hours after the last BSOD.

If there are no further BSOD this concludes the use of the tool.

After each BSOD you must turn off the tool in order to return to the desktop.

Learn the Windows RE commands reset and bootmode.

These are ran in safe mode or safe mode with command prompt.

In case these fail the next option is system restore.

If system restore fails you can restore a backup image or use registry commands.

banger · 02 May 2020

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

The setup logs are stored in this public onedrive folder.

- - - Updated - - -

PS C:\WINDOWS\system32> sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
PS C:\WINDOWS\system32> dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.815

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.
PS C:\WINDOWS\system32> dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.815

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
PS C:\WINDOWS\system32> sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
PS C:\WINDOWS\system32> chkdsk /scan
The type of the file system is NTFS.
Volume label is Windows.

Stage 1: Examining basic file system structure ...
513280 file records processed.
File verification completed.
6486 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
10147 reparse records processed.
654266 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
10147 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
70494 data files processed.
CHKDSK is verifying Usn Journal...
37815584 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

248765439 KB total disk space.
99235200 KB in 269863 files.
195136 KB in 70495 indexes.
0 KB in bad sectors.
635607 KB in use by the system.
65536 KB occupied by the log file.
148699496 KB available on disk.

4096 bytes in each allocation unit.
62191359 total allocation units on disk.
37174874 allocation units available on disk.
PS C:\WINDOWS\system32> wmic recoveros set autoreboot = false
Updating property(s) of '\\LAPTOPX64\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.
PS C:\WINDOWS\system32> wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\LAPTOPX64\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.
PS C:\WINDOWS\system32> wmic recoveros get autoreboot
AutoReboot
FALSE

PS C:\WINDOWS\system32> wmic recoveros get DebugInfoType
DebugInfoType
7

PS C:\WINDOWS\system32> bcdedit /enum {badmemory}
Invalid command line switch: /encodedCommand
Run "bcdedit /?" for command line assistance.
The parameter is incorrect.
PS C:\WINDOWS\system32>

- - - Updated - - -

Upgrade to 2004 green sceen driver_pnp_watchdog - rolls back-image.png

zbook · 02 May 2020

Code:

Bugcheck code : 0x000001D5

The DRIVER_PNP_WATCHDOG bug check has a value of 0x000001D5. This indicates that a driver has failed to complete a PnP operation within a specific time.

See if you can find these files: (within the last few days)
setuperr.log
Setupmem.dmp

Download and install: Everything
voidtools

When available post an image for virtual memory / page file.

banger · 02 May 2020

zbook · 02 May 2020

So far so good.
Plan to troubleshoot the misbehaving driver responsible for the upgrade rollback.

The prior commands were run with administrative PS instead of administrative command prompt.
Some commands do not work in PS and work using command prompt.
Please run the bad memory command using administrative command prompt.

banger · 02 May 2020

Setuperr.log is empty 0kb and cant find setupmem.dmp. Have downloaded Everything and running now.

- - - Updated - - -

C:\WINDOWS\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}
badmemoryaccess Yes
isolatedcontext Yes

- - - Updated - - -

HP Support Assistant containing warranty check and comms uninstalled and re-installed.

ESET removed.

Restore point made.

zbook · 02 May 2020

For Windows upgrade failures Windows creates Panther logs.
These may be hidden.
The setupdiag collected some logs.

See if you can find any of these from the past few days.

Code:

PANTHER logs
C:\Windows\Panther

folders:
\$Windows.~bt\sources\panther
\$Windows.~bt\Sources\Rollback
\Windows\Panther
\Windows\Panther\NewOS

Setupmem.dmp may be found in either (depending on when the bugcheck occurs)
%SystemDrive%$Windows.~bt\Sources\Rollback
%WinDir%\Panther\NewOS\Rollback

setuperr.log
setupact.log
Setupmem.dmp
setupapi.dev.log
BlueBox.log

When you are comfortable with the methods to turn off Windows driver verifier you can start the tool using the 3 customized test settings in the Ten Forums link.

Increase the simultaneous customized test settings by 3 - 5 / hour up to the 19 simultaneous customized test settings in the Microsoft link.

Sometimes there are performance problems or slow boot while using the tool.
If necessary the customized test settings can be modified.

Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Boot into Safe Mode on Windows 10

banger · 02 May 2020

Found some of the files including setupmem.dmp have moved them to public onedrive.

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

zbook · 02 May 2020

There may be multiple setuperr files located in different folders.