Windows 10: Driver_PNP_Watchdog error

Hello,I am having a BSOD problem with my Windows 11 home computer. The error is Driver_PNP_Watchdog. Before the error I got my computer booted normally, but I couldn't open Steam. At the same time I could still open some other files from my hard drive I only have one hard drive on my computer. When I got the problem opening some files, I tried to restart my computer. After that I can't get it to boot to desktop. There wasn't any notable changes I made before the problem started to occur. I might have done some normal windows updates earlier, but I don't think that is the sole reason. Now I c

:)

 

driver_pnp_watchdog error

Hello,

Today I tried updating to the latest version of Windows 1803 and a BSOD saying DRIVER_PNP_WATCHDOG appeared after 42% of the installation was complete. After the failed attempt it rolled back to previous version of the OS.

My current version is 1703 (I can't update to 1709 due to a different error).

After some research I've found that there maybe be a key to a solution in a file named setupmem.dmp located in C:\$WINDOWS.~BT\Sources\Rollback.

I don't know how to view this type of file but I can provide a link to it on Google Drive.

setupmem.dmp (Hope the link works.)

 

UnattendedJoin error: failed to find the domain data (0x6e)

Thanks for the suggestion! I don't want to add a domain account, as this is a generic unattended install that will be used for all company machines. Do you think it's possible that the computer would join the domain if, instead of using UnattendedJoin in specialize, I used your steps but left out the specific account? The other thing I was thinking was to use a generic account to allow the domain join during the specialize step. I added a machine password in the UnattendedJoin component, and instead of getting the error listed above, I got an authentication error, which makes me think I could probably do a secure join instead of the unsecure join. Thoughts?

 

Error: No work available to process

Hmm. Either it's put out errors and WCG is limiting the work units available, or the project list may not be set to supply other WU when one runs out. (if the problem lies here and not on your end)

On the options to your left, if you go into Results Status, select the computer from Device Name and then look through results see if either they were returned late, errors or any other kind of issue that would stop the servers supplying WU from that perspective.

If there are no errors then it's maybe down to your project list. So selecting Device Manager from the left menu and then clicking on the profile assigned to that computer and make sure that it's assigned to receive WU for other projects if they run out.

At least those steps will rule out problems from the WCG end.