How to solve DRIVER_PNP_WATCHDOG blue screen error?
DRIVER_PNP_WATCHDOG resolution

We beforehand checked out resolve the DRIVER_POWER_STATE_FAILURE blue display error. On this information, we’ll go into additional element and resolve the DRIVER_PNP_WATCHDOG blue display error.

First, this blue display error code signifies {that a} driver was unable to finish a PnP operation inside a specified time. We additionally want the Minidump file to determine the motive force inflicting the issue. We’ll use software program known as WinDbg Preview to research these information. You probably have entry permission issues whereas opening the minidump file, it’s worthwhile to take possession of the file. It’s helpful to level this out.

To begin with, we’ll attempt to analyze the file as we’ve got defined in our earlier guides. !analyze -v We begin with the command. Within the post-command output, the DRIVER_PNP_WATCHDOG header and different particulars meet us.

*******************************************************************************
*                                                                             *
*                        Bugcheck Evaluation                                    *
*                                                                             *
*******************************************************************************

DRIVER_PNP_WATCHDOG (1d5)
A driver has failed to finish a Pnp operation inside a particular time.
Arguments:
Arg1: 0000006900630070, First few character of the service related to the devnode.
Arg2: ffffd80a692fb710, Pointer to the nt!TRIAGE_PNP_WATCHDOG on Win10 RS4 and better.
Arg3: ffffc807e0470140, Thread liable for the Pnp Watchdog.
Arg4: 0000000000057e4c, Milliseconds elapsed for the reason that watchdog was armed.

Debugging Particulars:
------------------

Implicit thread is now ffffc807`e0470140
*** WARNING: Unable to confirm timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Evaluation.CPU.mSec
    Worth: 9578

    Key  : Evaluation.DebugAnalysisManager
    Worth: Create

    Key  : Evaluation.Elapsed.mSec
    Worth: 17212

    Key  : Evaluation.Init.CPU.mSec
    Worth: 952

    Key  : Evaluation.Init.Elapsed.mSec
    Worth: 3554

    Key  : Evaluation.Reminiscence.CommitPeak.Mb
    Worth: 79

    Key  : WER.OS.Department
    Worth: co_release

    Key  : WER.OS.Timestamp
    Worth: 2021-06-04T16:28:00Z

    Key  : WER.OS.Model
    Worth: 10.0.22000.1


FILE_IN_CAB:  setupmem.dmp

BUGCHECK_CODE:  1d5

BUGCHECK_P1: 6900630070

BUGCHECK_P2: ffffd80a692fb710

BUGCHECK_P3: ffffc807e0470140

BUGCHECK_P4: 57e4c

FAULTING_THREAD:  ffffc807e0470140

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

LOCK_ADDRESS:  fffff8020e445f20 -- (!locks fffff8020e445f20)

Useful resource @ nt!PiEngineLock (0xfffff8020e445f20)    Completely owned
    Competition Depend = 46
    NumberOfExclusiveWaiters = 2
     Threads: ffffc807e0470140-01<*> 

     Threads Ready On Unique Entry:
              ffffc807e03ba080       ffffc807f100b0c0       
1 complete locks

PNP_TRIAGE_DATA: 
	Lock deal with  : 0xfffff8020e445f20
	Thread Depend  : 1
	Thread deal with: 0xffffc807e0470140
	Thread wait   : 0x5f89

STACK_TEXT:  
ffffd80a`693e21a0 fffff802`0da5dc17     : fffff802`00000000 00000000`00000000 00000000`00000600 ffffc807`df010000 : nt!KiSwapContext+0x76
ffffd80a`693e22e0 fffff802`0da5fac9     : ffffc807`00000000 00000000`0000001e ffffd80a`693e24f8 00000000`00000000 : nt!KiSwapThread+0x3a7
ffffd80a`693e23c0 fffff802`0da8a9e1     : 00000000`00000000 fffff802`00000000 00000000`0000006a 00000000`f5a9df12 : nt!KiCommitThreadWait+0x159
ffffd80a`693e2460 fffff802`0de8b449     : ffffdc00`aabdbda0 ffffdc00`00000000 ffffdc00`aabdbda0 ffffdc00`aa9885a0 : nt!KeWaitForMultipleObjects+0x2b1
ffffd80a`693e2560 fffff802`0dfd90b8     : 00000000`00000000 ffffdc00`aa988500 00000000`00000000 ffffffff`ee1e5d00 : nt!PiUEventNotifyUserMode+0x285
ffffd80a`693e25f0 fffff802`0e15c746     : ffffdc00`aadfbd20 ffffdc00`aa9885a0 ffffdc00`aadfbd20 ffffd80a`693e28c8 : nt!PnpNotifyUserModeDeviceRemoval+0xc4
ffffd80a`693e2800 fffff802`0e0ef3a4     : 00000000`00000000 00000000`00000000 ffffd80a`693e28e9 00000000`00000000 : nt!PiProcessQueryAndCancelRemoval+0x15a
ffffd80a`693e2870 fffff802`0dfd73e5     : ffffd80a`693e29b0 ffffc807`e3f2d800 ffffc807`ee702900 ffffdc00`0000002d : nt!PnpProcessQueryRemoveAndEject+0x119ddc
ffffd80a`693e2950 fffff802`0de662b5     : ffffdc00`a9ddc9c0 ffffdc00`aacaa990 ffffc807`e02abc00 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x109
ffffd80a`693e2980 fffff802`0da48aaf     : ffffc807`e02abcd0 ffffc807`e0470140 ffffc807`ee7029d0 fffff802`00000000 : nt!PnpDeviceEventWorker+0x2c5
ffffd80a`693e2a00 fffff802`0db5b615     : ffffc807`e0470140 ffffb701`8c520000 ffffc807`e0470140 00000000`00000000 : nt!ExpWorkerThread+0x14f
ffffd80a`693e2bf0 fffff802`0dc16c24     : ffffb701`8c510180 ffffc807`e0470140 fffff802`0db5b5c0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffd80a`693e2c40 00000000`00000000     : ffffd80a`693e3000 ffffd80a`693dd000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


STACK_COMMAND:  .thread 0xffffc807e0470140 ; kb

SYMBOL_NAME:  nt!KiSwapContext+76

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22000.176

BUCKET_ID_FUNC_OFFSET:  76

FAILURE_BUCKET_ID:  0x1D5_nt!KiSwapContext

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Home windows 10

FAILURE_ID_HASH:  {3ada5172-33ef-c5a1-2a56-a080946d38c5}

Followup:     MachineOwner
---------

lm What’s the command?

Then to the command line as we all the time do. lm we’re writing. To outline it briefly, lm command lists all modules and the standing of symbols for every module. Right here the command presents the ends in two lists, modules loaded and modules not loaded. Unloaded modules typically, however not all the time, give us the supply of the issue.

Beneath lm command’s output of unloaded modules, and listed below are a number of SYS information that aren’t usually seen.

Unloaded modules:
fffff802`0ad70000 fffff802`0ae88000   aqnic650.sys
fffff802`1f940000 fffff802`1f96d000   HDAudBus.sys
fffff802`1f970000 fffff802`1f9e2000   portcls.sys
fffff802`1f9f0000 fffff802`1fa12000   drmk.sys
fffff802`135f0000 fffff802`13622000   storahci.sys
fffff802`1fad0000 fffff802`1fae2000   kbdhid.sys
fffff802`1fb10000 fffff802`1fb21000   mouhid.sys
fffff802`0a920000 fffff802`0a92c000   AMDPCIDev.sy
fffff802`0aeb0000 fffff802`0afcd000   e3xw10x64.sy
fffff802`0b280000 fffff802`0b296000   ipt.sys 
fffff802`205d0000 fffff802`205df000   dump_storpor
fffff802`1f640000 fffff802`1f675000   dump_stornvm
fffff802`1f6a0000 fffff802`1f6be000   dump_dumpfve
fffff802`1fa30000 fffff802`1fa3d000   amdgpio2.sys
fffff802`1fa40000 fffff802`1fa72000   msgpioclx.sy
fffff802`20500000 fffff802`2051f000   dam.sys 
fffff802`20520000 fffff802`2052f000   KMPDC.sys
fffff802`203d0000 fffff802`20465000   csc.sys 
fffff802`11de0000 fffff802`11df2000   WdBoot.sys
fffff802`14860000 fffff802`14872000   hwpolicy.sys

Once we searched the SYS information on the web, we got here up with a consequence concerning the Wi-Fi module. aqnic650.sys and e3xw10x64.sys information belong to community drive. You may get this type of info by looking out the SYS file identify on the web. For now, our suspect is the community drive, however let’s proceed the evaluation simply to make certain.

As you possibly can see, not a lot element is introduced within the minidump. So, let’s check out Microsoft’s Bug Examine 0x1D5: DRIVER_PNP_WATCHDOG article, as that is an article the place we will get detailed details about the blue display error we acquired.

within the article trigger that’s, within the why part, we’re introduced with related info by way of an in depth resolution. Accordingly, let’s check out the why half within the article. Right here it tells us “This means {that a} driver was unable to finish a PnP operation inside a specified time.” attempting.

What’s PnP (Plug and Play)?

To briefly speak about PnP; It’s quick for Plug and Play, which implies Plug and Play. We are able to additionally outline it as a construction that allows Home windows to adapt to {hardware} modifications. For instance, a consumer can use the mouse after ready for Home windows to do the required installations with out manually configuring a USB mouse to plug in.

Since Microsoft has advised us right here that the PnP operation couldn’t be accomplished, we additionally recognized the PnP system that was the supply of the error. !blackbox pnp We’ll discover it with the command

!blackbox pnp What’s the command?

This command shows details about PnP gadgets that may be captured throughout the creation of a minidump file. It normally offers us an concept of ​​the supply of the error. Beneath is the minidump file we simply analyzed. !blackbox pnp output is included.

    PnpActivityId      : {00000000-0000-0000-0000-000000000000}
    PnpActivityTime    : 132774097103997317
    PnpEventInformation: 0
    PnpEventInProgress : 1
    PnpProblemCode     : 21
    PnpVetoType        : 0
    DeviceId           : PCIVEN_1022&DEV_1483&SUBSYS_7C341462&REV_003&11583659&0&0A
    VetoString         :

As you possibly can see, a {hardware} ID is written within the DeviceId part. Because of our analysis on the web, we see that this {hardware} ID factors to a PCI system below chipset management. So a tool utilizing the PCI interface is the reason for this error.

Now we can’t detect the wi-fi community card immediately right here, however once we look with HWInfo, we will see that the community card is related to this PCIe controller.

HWInfo Hardware ID
With HWInfo you possibly can decide which {hardware} is related to which PCIe controller.

Additionally, as you possibly can see within the output PnpProblemCode: 21 he’s writing. You’ll find detailed descriptions of those codes in Microsoft’s Machine Supervisor error messages article. In response to our code, after coming into the required article, Microsoft really helpful that we restart the system because the really helpful resolution. After all, rebooting the system wasn’t sufficient to repair the issue.

Answer

After disabling the Wi-Fi card, each the Home windows replace works easily and the crashing issues below macOS disappear. anyway lm The small print we discovered within the command led us to this thought, however we’ve got higher recognized the supply of the issue with the {hardware} ID.

One other downside has thus been solved. You probably have an issue, you possibly can create your personal subject within the Blue Display screen Error Evaluation class in Technopat Social and get technical help from our members. We want you trouble-free days.