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-14T19:38:43+00:00

    The setupmem.dmp file points to the usbehci.sys, a Windows USB driver :

    BugCheck 1D5, {740072, 90a5fc94, 85d66040, 2bf36}

    Implicit thread is now 85d66040

    Probably caused by : usbehci.sys

    Do you have a USB wireless adapter that may be using an older driver as the netr70.sys, which appears to be from 2007, is a loaded driver.

    If so, what is the make/model of the adapter?

    And you could try the update without the adapter attached.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-05-14T13:15:17+00:00

    PMFJI

    This has happened to me. I think the version where it got as far as 42% then produced BSOD with Stopcode  DRIVER PNP WATCHDOG, but I wasn't watching the progress so it could have reached a different point.

    Following the cold restart the previous version (1709) of Windows 10 was restored.

    I have posted the setupmem.dmp file at https://1drv.ms/u/s!AnuHdSuVylHMkSuPgjIkaz2D5csz

    Can anyone suggest what might have caused this in my case?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-05-12T11:43:57+00:00

    OK, since you already started a topic maybe stick with that one.

    I'll make a post in that existing topic.

    Was this answer helpful?

    0 comments