W11'e yükseltirken DRIVER_PNP_WATCHDOG mavi ekran hatası

İşletim sistemi
Windows 11

Arif Kemal

Decapat
Katılım
1 Aralık 2021
Mesajlar
67
Daha fazla  
Cinsiyet
Erkek
RAM
8 GB
Windows 10 Pro kullanıyorum, W11'e manuel yükseltme yaparken yükleme bitip PC yeniden başlatılıyorken mavi ekran hatası veriyor. Hata adı DRIVER_PNP_WATCHDOG, birçok şey denedim ama bir şey değişmedi. Bilenler yardımcı olabilir mi?
 
Son düzenleyen: Moderatör:
Minidump dosyası oluşuyor mu? Ayrıca Windows 11'e geçtiğinizde güvenli modda sistem açılıyor mu? Açılıyorsa o sırada minidumpları paylaşırsınız.

 
Minidump dosyası oluşuyor mu? Ayrıca Windows 11'e geçtiğinizde güvenli modda sistem açılıyor mu? Açılıyorsa o sırada minidumpları paylaşırsınız.


W11'e geçemedim hata veriyor dediğim gibi. Minidump'ı da analizledim CAD.sys hatası veriyor.
 
Son düzenleyen: Moderatör:
İndirilebilir olması lazım.

Hayır indiremiyorum. Farklı bir servis kullanmanızı öneririm. MediaFire'ı bunun için kullanabilirsiniz.

1646482795840.png
 
Tamamdır, öncelikle sizden birkaç isteğim olacak.

İlk olarak CMD'yi yönetici olarak başlatıp powercfg -energy -output %userprofile%\desktop\energy-report.html kodunu girip masaüstünde oluşacak energy-report.html dosyasını bizimle paylaşın.

Ek olarak hızlı başlatmayı ve uyku modunu kapatın.


Son olarak bütün mavi ekranlarınız pildeyken oluyor değil mi? Güç modu yüksek performansta ise dengeliye de almayı deneyebilirsiniz.

[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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

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

Implicit thread is now ffffc78a`becd6540

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 8937

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 24225

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

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

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

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


FILE_IN_CAB: 030222-11406-01.dmp

BUGCHECK_CODE: 1d5

BUGCHECK_P1: 4400410043

BUGCHECK_P2: fffff8043ccda710

BUGCHECK_P3: ffffc78abecd6540

BUGCHECK_P4: 57e4d

FAULTING_THREAD: ffffc78abecd6540

BLACKBOXNTFS: 1 (!blackboxntfs)


CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff308`2a8ecb10 fffff804`379327f7 : ffff9380`99891180 fffff308`ffffffff fffff308`2a8ecd49 00000000`00000000 : nt!KiSwapContext+0x76
fffff308`2a8ecc50 fffff804`379346a9 : ffff7fff`00000002 00000000`00000008 fffff308`2a8ece30 fffff804`00000000 : nt!KiSwapThread+0x3a7
fffff308`2a8ecd30 fffff804`3792e5c4 : 00000000`00000000 00000000`00000000 00000000`000000d9 00000000`db6602a4 : nt!KiCommitThreadWait+0x159
fffff308`2a8ecdd0 fffff804`378234ed : fffff308`2a8ecfa0 ffffffff`0000001b 00000000`00000000 fffff804`38245600 : nt!KeWaitForSingleObject+0x234
fffff308`2a8ecec0 fffff804`3792d7e6 : fffff804`38246160 fffff308`2a8ecf88 fffff804`00010224 fffff804`37851fd0 : nt!ExpWaitForResource+0x6d
fffff308`2a8ecf40 fffff804`37da61f5 : fffff308`2a8ed100 ffffc78a`bf065bf0 00000000`00000190 00000000`00000001 : nt!ExAcquireResourceExclusiveLite+0x196
fffff308`2a8ecfd0 fffff804`37e156e7 : 00000000`00000000 ffffc78a`bf065bf0 fffff308`2a8ed100 ffffc78a`bf065bf0 : nt!PpDevNodeLockTree+0x59
fffff308`2a8ed000 fffff804`451310e9 : 00003875`416e6800 00000000`00000000 ffffc78a`bec13000 ffffc78a`bf065aa0 : nt!IoReportRootDevice+0xd7
fffff308`2a8ed410 fffff804`45121f37 : 00000000`00000000 ffffc78a`bec13000 ffffc78a`bf1ff3d0 ffffc78a`beeac010 : CAD!DriverEntry+0xad
fffff308`2a8ed480 fffff804`45121e80 : ffffc78a`bec13000 fffff308`2a8ed650 ffffc78a`bf1ff3d0 ffffc78a`bf065aa0 : CAD!FxDriverEntryWorker+0xa3
fffff308`2a8ed4c0 fffff804`37cc1d78 : ffffc78a`bec13000 00000000`00000000 00000000`00000000 00000000`00000000 : CAD!FxDriverEntry+0x20
fffff308`2a8ed4f0 fffff804`37dc4a12 : 00000000`00000008 00000000`00000000 00000000`00000000 fffff804`00001000 : nt!PnpCallDriverEntry+0x4c
fffff308`2a8ed550 fffff804`37ca7297 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopLoadDriver+0x8ba
fffff308`2a8ed700 fffff804`378417e1 : 00000000`00000000 ffffffff`80000194 00000000`00000000 00000000`00000000 : nt!IopLoadUnloadDriver+0x57
fffff308`2a8ed740 fffff804`37ca6a39 : ffffc78a`becd6540 ffffc78a`b96c5a20 00000000`00000ba0 ffffc78a`bf1ff3c0 : nt!IopLoadDriverImage+0x1e9
fffff308`2a8ed7f0 fffff804`37a28778 : fffff804`38333680 00000000`00000000 00000000`00000000 ffff9380`00000000 : nt!NtLoadDriver+0x9
fffff308`2a8ed820 fffff804`37a1aa70 : fffff804`37f9a987 00000000`00000000 00000000`00000000 00000000`00000100 : nt!KiSystemServiceCopyEnd+0x28
fffff308`2a8ed9b8 fffff804`37f9a987 : 00000000`00000000 00000000`00000000 00000000`00000100 fffff804`38333680 : nt!KiServiceLinkage
fffff308`2a8ed9c0 fffff804`3791d35f : ffffc78a`b96c5a20 ffffc78a`becd6500 ffffc78a`00000000 ffffc78a`00000000 : nt!PopCadTriggerDriverLoad+0x27
fffff308`2a8eda00 fffff804`378478f5 : ffffc78a`becd6540 ffff9380`99f0a000 ffffc78a`becd6540 000f8067`bcbbbdff : nt!ExpWorkerThread+0x14f
fffff308`2a8edbf0 fffff804`37a1a2d4 : ffff9380`99efb180 ffffc78a`becd6540 fffff804`378478a0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffff308`2a8edc40 00000000`00000000 : fffff308`2a8ee000 fffff308`2a8e8000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


STACK_COMMAND: .thread 0xffffc78abecd6540 ; kb

SYMBOL_NAME: CAD!DriverEntry+ad

MODULE_NAME: CAD

IMAGE_NAME: CAD.sys

IMAGE_VERSION: 10.0.21390.1

BUCKET_ID_FUNC_OFFSET: ad

FAILURE_BUCKET_ID: 0x1D5_CAD!DriverEntry

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f153ff15-714d-6545-ac6b-3d6791b80f97}

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

0: kd> lmDvmCAD
Browse full module list
start end module name
fffff804`45120000 fffff804`45135000 CAD # (pdb symbols) C:\ProgramData\Dbg\sym\CAD.pdb\62B48B10E4097829EA28955AF42253AA1\CAD.pdb
Loaded symbol image file: CAD.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\CAD.sys\FDFE356915000\CAD.sys
Image path: \SystemRoot\System32\drivers\CAD.sys
Image name: CAD.sys
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: FDFE3569 (This is a reproducible build file hash, not a timestamp)
CheckSum: 0001AACA
ImageSize: 00015000
File version: 10.0.21390.1
Product version: 10.0.21390.1
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0000.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: cad.sys
OriginalFilename: cad.sys
ProductVersion: 10.0.21390.1
FileVersion: 10.0.21390.1 (WinBuild.160101.0800)
FileDescription: Charge Arbiration Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.[/CODE]
 

Yeni konular

Geri
Yukarı