PNP DRIVER WATCHDOG

Anonymous
2018-05-01T21:35:45+00:00

I have been trying to install the April2018 Update but I get a blue screen with the Stop Code PNP DRIVER WATCHDOG. Is there a workaround?

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2018-05-02T18:55:08+00:00

The setupmem.dmp references the volsnap.sys (Volume Shadow Copy driver) but not a third party driver :

BugCheck 1D5, {6900630070, ffff9f06c6092ab0, ffffd209730df040, 2bf32}

Implicit thread is now ffffd209`730df040

Probably caused by : volsnap.sys ( volsnap!VspSynchronousIo+14b )

The error may indicate an issue with a file system driver possibly third party.

Can you check if the following folders exist (to see the folders you may have to "show hidden files and folders"):

C:$WINDOWS.~BT\Sources\Panther

C:$WINDOWS.~BT\Sources\Rollback

If those folders exist can you zip them up and provide via OneDrive.

Was this answer helpful?

6 people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2018-05-08T21:31:02+00:00

I would go with the WHQL.zip as the motherboard appears to have a "JMicron® JMB363 PATA and SATA controller".

Was this answer helpful?

4 people found this answer helpful.
0 comments

50 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-05-10T12:17:38+00:00

    I have the same problem.

    I already did what Pedro T 32 did:

    • Uninstall the "Display Adapter" driver.
    • Hide all Microsoft services.

    But still can not get Windows update.And, I also have the setupmem.dmp file in C:\WINDOWS\Panther\NewOs\Rollback. Can you help me? (I've tried updating my Windows almost 7 times)

    Here is the file setupmem.dmp: https://drive.google.com/drive/folders/1p9HggoRn5AzH83hK9BE6vop2QtoMUeJk?usp=sharing

    Thank you

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-05-10T20:47:08+00:00

    I ran into the same BSOD during the 1803 April update.  the dmp also has volsnap.sys in the stack.  I ran:

    vssadmin delete shadows /all

    to delete all the shadow copies.  The command took a while execute.  After this was done, the April upgrade was restarted manually and completed successfully.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-05-10T21:44:20+00:00

    Hi,

    Unfortunately there is currently an issue with symbols which are necessary to debug the error.

    However you could try deleting all shadow copies as suggested by Lit - MSFT in the previous post.

    Was this answer helpful?

    0 comments