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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2018-05-15T21:26:03+00:00

    I have the same question

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-05-15T14:24:31+00:00

    About the same age as the device itself! Obtained it in 2007 when I bought a Dell Inspiron 530, and now using it on a Dell Inspiron 545 which I bought in 2009. Both PCs now successfully upgraded to latest Windows 10.

    Keep up the good work!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-05-15T12:06:28+00:00

    Yes, the driver chosen by Windows 10 seems to be way too old.

    Was this answer helpful?

    0 comments