X399 Creation DRIVER_POWER_STATE_FAILURE

Katılım
14 Ağustos 2010
Mesajlar
79.057
Makaleler
289
Çözümler
2.268
Yer
İstanbul
Daha fazla  
Cinsiyet
Erkek
Profil Kapağı
1522743131
Muhtemelen stabil olmayan BIOS kaynaklı bir hata.

Kod:
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffff9709248b9d40, Physical Device Object of the stack
Arg3: ffffa70ba8e3eba0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff930bc21a19e0, The blocked IRP

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

Implicit thread is now ffff930b`b476c080

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6156

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 26767

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

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

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

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffff9709248b9d40

BUGCHECK_P3: ffffa70ba8e3eba0

BUGCHECK_P4: ffff930bc21a19e0

DRVPOWERSTATE_SUBCODE:  3

FAULTING_THREAD:  ffff930bb476c080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Creative Cloud.exe

DPC_STACK_BASE:  FFFFA70BA8E3EFB0

STACK_TEXT:
ffffa70b`a8e1b170 fffff804`61e65850     : ffffd300`f8519180 00000000`ffffffff ffff930b`c20a1400 00000000`00000000 : nt!KiSwapContext+0x76
ffffa70b`a8e1b2b0 fffff804`61e64d7f     : ffff930b`00000036 ffffa70b`00000008 ffffa70b`a8e1b470 fffff804`00000000 : nt!KiSwapThread+0x500
ffffa70b`a8e1b360 fffff804`61e64623     : 00000000`00000019 fffff804`00000000 ffff930b`be7e4000 ffff930b`b476c1c0 : nt!KiCommitThreadWait+0x14f
ffffa70b`a8e1b400 fffff804`6e14fbf3     : ffff930b`c20a1900 ffff930b`00000000 fffff804`6e17ed00 000068f6`db746f00 : nt!KeWaitForSingleObject+0x233
ffffa70b`a8e1b4f0 fffff804`6e13832b     : ffff930b`c20a1900 ffff9709`248b9310 00000000`00000000 ffffffff`dc3cba00 : UsbHub3!HUBMISC_WaitForSignal+0xff
ffffa70b`a8e1b560 fffff804`66dc8a0e     : 00000000`0a380a6c ffff9709`248b9aa8 ffff9709`248b9020 00000000`00000660 : UsbHub3!HUBPDO_EvtDeviceD0Entry+0x16b
ffffa70b`a8e1b5e0 fffff804`66dc6f81     : ffff9709`248b9aa8 fffff804`66dc7f23 ffffa70b`a8e1000e ffffa70b`a8e1b6d8 : Wdf01000!FxPnpDeviceD0Entry::InvokeClient+0x2e [minkernel\wdf\framework\shared\irphandlers\pnp\pnpcallbacks.cpp @ 93]
ffffa70b`a8e1b640 fffff804`66dc7dfd     : ffff9709`248b9570 ffffa70b`a8e1b7b0 00000000`00000660 00000000`00000000 : Wdf01000!FxPrePostCallback::InvokeStateful+0x69 [minkernel\wdf\framework\shared\irphandlers\pnp\cxpnppowercallbacks.cpp @ 275]
ffffa70b`a8e1b680 fffff804`66dc25f5     : 00000000`00000300 00000000`00000060 ffff9709`248b9570 00000000`00000303 : Wdf01000!FxPkgPnp::PowerWaking+0x3d [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 3549]
ffffa70b`a8e1b6b0 fffff804`66dc23aa     : 00000000`00000001 ffff9709`248b9570 ffff9709`248b9570 00000000`00000000 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x155 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1699]
ffffa70b`a8e1b810 fffff804`66dc1911     : ffff9709`248b9570 00000000`00000000 00000000`00000001 00000000`00000000 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0xea [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1615]
ffffa70b`a8e1b890 fffff804`66dc01c1     : 00000000`00000000 ffff9709`248b9570 00000000`00000000 ffff9709`248b9190 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1d1 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1394]
ffffa70b`a8e1b920 fffff804`66dc0075     : ffff9709`248b9570 ffff9709`248b9020 00000000`00000004 00000000`00000000 : Wdf01000!FxPkgPdo::DispatchDeviceSetPower+0x51 [minkernel\wdf\framework\shared\irphandlers\pnp\pdopower.cpp @ 208]
ffffa70b`a8e1b970 fffff804`66dbcc5f     : ffff9709`248b9570 ffff9709`248b9020 00000000`00000001 00000000`00000000 : Wdf01000!FxPkgPdo::_DispatchSetPower+0x25 [minkernel\wdf\framework\shared\irphandlers\pnp\pdopower.cpp @ 89]
ffffa70b`a8e1b9a0 fffff804`66dc3723     : ffff930b`c21a19e0 ffff9709`248b9190 00000000`00000005 ffff930b`c21a1ea0 : Wdf01000!FxPkgPnp::Dispatch+0xaf [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 765]
ffffa70b`a8e1ba10 fffff804`66dc36b4     : ffff930b`c21a19e0 ffff9709`248b9190 ffff9709`248b9020 fffff804`6e121c30 : Wdf01000!DispatchWorker+0x53 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1589]
ffffa70b`a8e1ba40 fffff804`66dc3835     : ffff930b`be724de0 ffff930b`c20a12d0 ffff930b`c21a19e0 00000000`00000000 : Wdf01000!FxDevice::DispatchPreprocessedIrp+0x88 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1654]
ffffa70b`a8e1ba80 fffff804`6e1366fc     : ffff9709`248b9020 ffff930b`c21a19e0 000068f6`db746fd8 fffff804`6740ef02 : Wdf01000!imp_WdfDeviceWdmDispatchPreprocessedIrp+0x65 [minkernel\wdf\framework\shared\core\km\fxdeviceapikm.cpp @ 258]
ffffa70b`a8e1bac0 fffff804`66dba976     : ffff930b`c21a19e0 00000000`00000016 ffff9709`248b9020 fffff804`62823480 : UsbHub3!HUBPDO_EvtDeviceWdmIrpPnPPowerPreprocess+0x42c
ffffa70b`a8e1bb10 fffff804`61f9cb29     : 00000000`00000000 00000000`00000000 ffffd300`f60ff000 ffff930b`b476c080 : Wdf01000!FxDevice::DispatchWithLock+0x266 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447]
ffffa70b`a8e1bb70 fffff804`61f17e85     : 00000000`00000000 fffff804`61f9c950 00000000`00000000 00000000`000000b4 : nt!PopIrpWorker+0x1d9
ffffa70b`a8e1bc10 fffff804`61ffd408     : ffffd300`f60f0180 ffff930b`b476c080 fffff804`61f17e30 245c8948`cccccccc : nt!PspSystemThreadStartup+0x55
ffffa70b`a8e1bc60 00000000`00000000     : ffffa70b`a8e1c000 ffffa70b`a8e16000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


STACK_COMMAND:  .thread 0xffff930bb476c080 ; kb

SYMBOL_NAME:  UsbHub3!HUBMISC_WaitForSignal+ff

MODULE_NAME: UsbHub3

IMAGE_NAME:  UsbHub3.sys

IMAGE_VERSION:  10.0.19041.264

BUCKET_ID_FUNC_OFFSET:  ff

FAILURE_BUCKET_ID:  0x9F_3_UsbHub3!HUBMISC_WaitForSignal

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {48c69e11-75d2-409c-f737-24f5cea8e890}

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

2: kd> lmvm UsbHub3
Browse full module list
start             end                 module name
fffff804`6e120000 fffff804`6e1c3000   UsbHub3    (pdb symbols)          C:\ProgramData\Dbg\sym\usbhub3.pdb\FEB0212F8C4FD77DDEEBF0678FB00EA21\usbhub3.pdb
    Loaded symbol image file: UsbHub3.sys
    Mapped memory image file: C:\ProgramData\Dbg\sym\UsbHub3.sys\FDA30E83a3000\UsbHub3.sys
    Image path: \SystemRoot\System32\drivers\UsbHub3.sys
    Image name: UsbHub3.sys
    Browse all global symbols  functions  data
    Image was built with /Brepro flag.
    Timestamp:        FDA30E83 (This is a reproducible build file hash, not a timestamp)
    CheckSum:         000AC346
    ImageSize:        000A3000
    File version:     10.0.19041.264
    Product version:  10.0.19041.264
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     usbhub3.sys
        OriginalFilename: usbhub3.sys
        ProductVersion:   10.0.19041.264
        FileVersion:      10.0.19041.264 (WinBuild.160101.0800)
        FileDescription:  USB3 HUB Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
2: kd> !irp ffff930bc21a19e0
Irp is active with 18 stacks 14 is current (= 0xffff930bc21a1e58)
No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.
     cmd  flg cl Device   File     Completion-Context
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000  

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000  

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000  

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000  

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000  

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000  

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000  

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000  

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000  

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000  

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000  

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000  

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000  

            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffff9709248b9d40 00000000 fffff8046e13a5d0-ffff930bc20a12d0 Success Error Cancel pending
           \Driver\USBHUB3    UsbHub3!HUBPDO_WdmPnpPowerIrpCompletionRoutineForAsynchronousCompletion
            Args: 00000000 00000001 00000001 00000000
[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffff9709248b9d40 00000000 fffff8046e362ab0-00000000 Success Error Cancel pending
           \Driver\USBHUB3    hidusb!HumPowerCompletion
            Args: 00000000 00000001 00000001 00000000
[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e0 ffff930bc2176120 00000000 fffff8046e304f90-ffff930bc2176270 Success Error Cancel
           \Driver\HidUsb    HIDCLASS!HidpFdoPowerCompletion
            Args: 00000000 00000001 00000001 00000000
[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffff930bc2176120 00000000 fffff80461f77bc0-ffff930bc21a12a8 Success Error Cancel pending
           \Driver\HidUsb    nt!PopRequestCompletion
            Args: 00000000 00000001 00000001 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffff930bc21a12a8  

            Args: 00000000 00000000 00000000 00000000
2: kd> !devstack ffff9709248b9d40
  !DevObj           !DrvObj            !DevExt           ObjectName
  ffff930bc2176120  \Driver\HidUsb     ffff930bc2176270  InfoMask field not found for _OBJECT_HEADER at ffff930bc21760f0

  ffff930bc2176de0  \Driver\ACPI       ffff930bb4723020  InfoMask field not found for _OBJECT_HEADER at ffff930bc2176db0

> ffff9709248b9d40  \Driver\USBHUB3    ffff9709248b9310  Cannot read info offset from nt!ObpInfoMaskToOffset

!DevNode ffff9709248cca20 :
  DeviceInst is "USB\VID_1462&PID_7B92\A02018061911"
  ServiceName is "HidUsb"
 
Abi buradan BIOS'un stabil olmadığını nasıl çıkardın? :) Bence sorun Adobe'nin Creative Cloud'undan kaynaklı. Çünkü senin de dediğin gibi Windows'tan kaynaklı olma ihtimali çok düşük.
 
İşin numarası orada zaten :D
Ben cevabımı söyledim, belki benim cevabım doğru :=). Çünkü Recep hocamın cevabı kesin değil, olasılık içeren bir cümle.

Yoksa ACPI'dan mı çıkıyor abi cevap?
Hidusb.sys is a Windows driver. A driver is a small software program that allows your computer to communicate with hardware or connected devices. This means that a driver has direct access to the internals of the operating system, hardware etc.

Cevap altı çizili yerden mi çıkıyor?

Buradan deneyeceğim fakat .dmp dosyası yok.
 
Açıkçası Recep abinin bunu nasıl BIOS'la ilişkilendirdiğini ben de inanılmaz merak ediyorum. Biraz baktım belki beta BIOS'tur diye, en son BIOS 2 sene önce çıkmış. Güncel sürümde sorun yaşayan var mı diye baktım, tabii ki var fakat sadece bununla sonuca atlanamaz.

Döküm örneğinden görebildiğim ve tahmin edebildiğim, eğer varsa Bluetooth adaptörü derdim ben. Ama Recep abi gelip de sistemde Bluetooth aygıtı yok diyecek diye de korkmuyor değilim 😄
 
Açıkçası Recep abinin bunu nasıl BIOS'la ilişkilendirdiğini ben de inanılmaz merak ediyorum. Biraz baktım belki beta BIOS'tur diye, en son BIOS 2 sene önce çıkmış. Güncel sürümde sorun yaşayan var mı diye baktım, tabii ki var fakat sadece bununla sonuca atlanamaz.

Döküm örneğinden görebildiğim ve tahmin edebildiğim, eğer varsa Bluetooth adaptörü derdim ben. Ama Recep abi gelip de sistemde Bluetooth aygıtı yok diyecek diye de korkmuyor değilim 😄

Bana USB port sürücüsü gibi geldi. BIOS ile alakalı olma ihtimali yok gibi geliyor. Tabii ki Recep abide yılların tecrübesi var. O bizden daha iyi bilir.
 

Geri
Yukarı