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-04T14:59:46+00:00

    Fixed!

    I would not have found it without this help from auggy:

    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 )

    I found lots of "generic shadow volume" entries in Drivers, including some hidden non-active ones

    vssadmin List Shadows revealed a shadow on my D drive that was last modified in 2015

    vssadmin Delete Shadows would not delete it - saying it had to be deleted by the application which created it.

    I used vssadmin Resize ShadowStorage to delete it by setting the size to 320MB, then back to UNBOUND.

    All my generic shadow volumes disappeared from drivers. The update worked fine.

    Incidentally I had previously run both "Dism /Online /Cleanup-Image /RestoreHealth" and "SFC ScanNow" with no effect.

    So again, thanks to auggy, I now have a fixed machine.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2018-05-08T16:26:22+00:00

    Same problem here. Update stuck at 42% and then this DRIVER PNP WATCHDOG screen.

    Already tried:

    • Open "task Manager" & go to startup tab and disable everything
    • Open msconfig and go to services tab; click "Hide all Microsoft services" then check everything else and disable everything
    • Open Device Manager, go to "Display Adapter", right-click entry (videocard) and uninstall device, and also all Realtek sound devices

    Yes, I have this C:\Windows\Panther\NewOs\Rollbackfolder with the setupmem.dmp file in it

    What do I do?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2018-05-08T19:38:58+00:00

    Can you make the setupmem.dmp available (provide link) via a public folder on OneDrive or similar site?

    Was this answer helpful?

    0 comments