X570 Sistem DRIVER_PNP_WATCHDOG hatası

Katılım
14 Ağustos 2010
Mesajlar
79.065
Makaleler
287
Çözümler
2.268
Yer
İstanbul
Kurgucumuzun PC'sinde hatalardan birini 20H2 güncellemesi yaparken diğerini de Windows 11 kurarken aldım. İkisi de başarısız oldu tabi.

Bana bellek hatası gibi geldi ama bakıcam.

Kod:
DRIVER_PNP_WATCHDOG (1d5)
A driver has failed to complete a Pnp operation within a specific time.
Arguments:
Arg1: 0000006900630070, First few character of the service associated with the devnode.
Arg2: ffffd80a692fb710, Pointer to the nt!TRIAGE_PNP_WATCHDOG on Win10 RS4 and higher.
Arg3: ffffc807e0470140, Thread responsible for the Pnp Watchdog.
Arg4: 0000000000057e4c, Milliseconds elapsed since the watchdog was armed.

Debugging Details:
------------------

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5124

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 21435

    Key  : Analysis.Init.CPU.mSec
    Value: 702

    Key  : Analysis.Init.Elapsed.mSec
    Value: 9882

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 80

    Key  : WER.OS.Branch
    Value: co_release

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

    Key  : WER.OS.Version
    Value: 10.0.22000.1


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)

Resource @ nt!PiEngineLock (0xfffff8020e445f20)    Exclusively owned
    Contention Count = 46
    NumberOfExclusiveWaiters = 2
     Threads: ffffc807e0470140-01<*>

     Threads Waiting On Exclusive Access:
              ffffc807e03ba080       ffffc807f100b0c0     
1 total locks

PNP_TRIAGE_DATA:
    Lock address  : 0xfffff8020e445f20
    Thread Count  : 1
    Thread address: 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:  Windows 10

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

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

Kod:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8043929f170, The address that the exception occurred at
Arg3: fffffb0cea1a33d8, Exception Record Address
Arg4: fffffb0cea1a2c20, Context Record Address

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullClassPtr

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 3171

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 15496

    Key  : Analysis.Init.CPU.mSec
    Value: 1562

    Key  : Analysis.Init.Elapsed.mSec
    Value: 11361

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 79

    Key  : WER.OS.Branch
    Value: 19h1_release

    Key  : WER.OS.Timestamp
    Value: 2019-03-18T12:02:00Z

    Key  : WER.OS.Version
    Value: 10.0.18362.1


BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8043929f170

BUGCHECK_P3: fffffb0cea1a33d8

BUGCHECK_P4: fffffb0cea1a2c20

EXCEPTION_RECORD:  fffffb0cea1a33d8 -- (.exr 0xfffffb0cea1a33d8)
ExceptionAddress: fffff8043929f170 (nt!FsRtlAcquireFileForCcFlushEx+0x000000000000023c)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000008
Attempt to read from address 0000000000000008

CONTEXT:  fffffb0cea1a2c20 -- (.cxr 0xfffffb0cea1a2c20)
rax=ffffb982b1ab8040 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8043929f170 rsp=fffffb0cea1a3610 rbp=fffffb0cea1a3710
 r8=0000000000000008  r9=0000000000000000 r10=7ffffffffffffffc
r11=0000000000000000 r12=0000000000000000 r13=ffffb982b2d88b50
r14=ffffb982b1b4d8f0 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050202
nt!FsRtlAcquireFileForCcFlushEx+0x23c:
fffff804`3929f170 488b4b08        mov     rcx,qword ptr [rbx+8] ds:002b:00000000`00000008=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff804391713b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 0000000000000008

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek  u olamaz %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000008

EXCEPTION_STR:  0xc0000005

STACK_TEXT:
fffffb0c`ea1a3610 fffff804`38eb9759     : 00000000`00000000 00000000`00000000 ffffb982`b2db3e50 ffffb982`b2db3e50 : nt!FsRtlAcquireFileForCcFlushEx+0x23c
fffffb0c`ea1a38d0 fffff804`38eb8e06     : 00000000`00000001 00000000`00000001 fffffb0c`ea1a39e0 fffffb0c`ea1a39e8 : nt!MiFlushControlArea+0x99
fffffb0c`ea1a3990 fffff804`38e7604d     : 00000000`00000000 00000000`00000000 fffff804`39068ae8 fffff804`39068b50 : nt!MiDeleteCachedSegment+0x16a
fffffb0c`ea1a39e0 fffff804`38d33585     : ffffb982`b1ab8040 ffffb982`b1ab8040 00000000`00000080 fffff804`38d91000 : nt!MiDereferenceSegmentThread+0xe504d
fffffb0c`ea1a3c10 fffff804`38dcb128     : ffff9481`d0400180 ffffb982`b1ab8040 fffff804`38d33530 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffffb0c`ea1a3c60 00000000`00000000     : fffffb0c`ea1a4000 fffffb0c`ea19e000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!FsRtlAcquireFileForCcFlushEx+23c

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.18362.1198

STACK_COMMAND:  .cxr 0xfffffb0cea1a2c20 ; kb

BUCKET_ID_FUNC_OFFSET:  23c

FAILURE_BUCKET_ID:  AV_nt!FsRtlAcquireFileForCcFlushEx

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {6f5021e6-ddbb-4be7-5bae-fcfd522b8cd9}
 
Son düzenleme:
Bana kalırsa hatanın nedeni Wi-Fi kartı. Onu söküp denediniz mi hocam? Gerçi boot sırasından çıkartmak da aynı işlevi görecektir kanımca fakat emin değilim listeden çıkarma konusunda. Sorunu cidden ben de merak ettim ayrıca.
 
@Enes3078 Sorun WiFi kartı gibi. Özellikle bir ibare ni gördün kartla ilgili yoksa tahmin mi?

Yok hocam tahmin değil. Unloaded Modules'de yer alan SYS'lerden biri Wi-Fi kartına aitti ama bu sadece denklemi doğrulayan bir etmen. Şu an mobildeyim fakat hatayı gösteren şey donanım kimliğiydi. Fault nedenini veren donanım kimliğinin sonucuna baktım ve Wi-Fi kartı çıktı. Sorun tamamen çözülmüş olsa gerek fakat yine de çözülüp çözülmediğine siz karar verirsiniz.
 
Yok hocam tahmin değil. Unloaded Modules'de yer alan SYS'lerden biri Wi-Fi kartına aitti ama bu sadece denklemi doğrulayan bir etmen. Şu an mobildeyim fakat hatayı gösteren şey donanım kimliğiydi. Fault nedenini veren donanım kimliğinin sonucuna baktım ve Wi-Fi kartı çıktı. Sorun tamamen çözülmüş olsa gerek fakat yine de çözülüp çözülmediğine siz karar verirsiniz.
Şu anda sistemde bir sorun yok ama kapsamlı bir döküm yaparsan ben buna bir video rehber çekerim 👍
 
Uyarı! Bu konu 5 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Technopat Haberler

Geri
Yukarı