DRIVER_POWER_STATE_FAILURE mavi ekran hatası

Bora55

Hectopat
Katılım
20 Ocak 2021
Mesajlar
162
Çözümler
3
Daha fazla  
Sistem Özellikleri
Hp Victus 16 | i7 14700HX | RTX4070 | 16Gb Ram

CPU: Fx-6300
GPU: Rx580 8Gb
RAM: 4+8 Gb Ram
PSU: SilverStone 1200W
Anakart: A960m-m3
Cinsiyet
Erkek
Meslek
Öğrenci
Ekran kartı
RX580
Anakart
A960M-M3
İşlemci
FX-6300
Merhaba. Bilgisayarı kapatırken bu mavi hata ile karşılaştım. Minidump klasöründeki DMP dosyasını aşağıda paylaştım. Kendim WinDbg ile analiz ettim ancak pek bir şey anlamadığımı söyleyebilirim:|. Ancak sanırsam Wi-Fi driveri ile ilgili (bilgisayara USB üzerinden bağlı Wi-Fi adaptörü var). Aynı zamanda analiz sonuçlarını da aşağıya bırakıyorum.

Minidump Dosyası

Kod:
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp.
 subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffca05f5bcb140, The thread currently holding on to the Pnp lock.
Arg4: fffff80737a77880, nt!TRIAGE_9F_PNP on Win7 and higher.

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

Implicit thread is now ffffca05`f5bcb140
*** WARNING: Check Image - Checksum mismatch - Dump: 0x18561b, File: 0x1856f7 - C:\ProgramData\Dbg\sym\BTHport.sys\70388B82185000\BTHport.sys

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 6780.

 Key : Analysis.Elapsed.mSec
 Value: 30582.

 Key : Analysis.IO.Other.Mb
 Value: 3

 Key : Analysis.IO.Read.Mb
 Value: 0

 Key : Analysis.IO.Write.Mb
 Value: 6

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

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x1000009f.

 Key : Failure.Bucket
 Value: 0x9F_4_USB_vwifimp_IMAGE_vwifibus.sys

 Key : Failure.Hash
 Value: {3feeea6b-6cf3-300d-f10f-3abbe160e412}

 Key : Hardware.BusType
 Value: USB.

 Key : Hardware.DeviceID
 Value: PID_3070.

 Key : Hardware.HardwareID
 Value: USB\VID_148F&PID_3070

 Key : Hardware.VendorID
 Value: VID_148F.

 Key : WER.OS.Branch
 Value: vb_release.

 Key : WER.OS.Version
 Value: 10.0.19041.1

BUGCHECK_CODE: 9f.

BUGCHECK_P1: 4

BUGCHECK_P2: 12c.

BUGCHECK_P3: ffffca05f5bcb140.

BUGCHECK_P4: fffff80737a77880.

FILE_IN_CAB: 062423-42453-01.dmp

DRVPOWERSTATE_SUBCODE: 4

HARDWARE_ID_BUS_TYPE: USB.

HARDWARE_VENDOR_ID: VID_148F.

HARDWARE_DEVICE_ID: PID_3070.

HARDWARE_ID: USB\VID_148F&PID_3070

IMAGE_NAME: vwifibus.sys

MODULE_NAME: vwifibus.

FAULTING_MODULE: fffff807585d0000 vwifibus.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

STACK_TEXT:
fffff807`37a77848 fffff807`3210bc86 : 00000000`0000009f 00000000`00000004 00000000`0000012c ffffca05`f5bcb140 : nt!KeBugCheckEx
fffff807`37a77850 fffff807`325b56b6 : 00000000`00000000 00000000`00000002 00000000`00000080 fffff807`2f762180 : nt!PnpBugcheckPowerTimeout+0x76
fffff807`37a778b0 fffff807`31e8bbd2 : ffff8201`6c8f8330 fffff807`2f762180 fffff807`37a77b18 00000000`00000000 : nt!PopBuildDeviceNotifyListWatchdog+0x16
fffff807`37a778e0 fffff807`31e8ac4d : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`000940cf : nt!KiProcessExpiredTimerList+0x172
fffff807`37a779d0 fffff807`3200092e : 00000000`00000000 fffff807`2f762180 fffff807`32927a00 ffffca05`f5b57080 : nt!KiRetireDpcList+0x5dd
fffff807`37a77c60 00000000`00000000 : fffff807`37a78000 fffff807`37a72000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e

IMAGE_VERSION: 10.0.19041.1030

STACK_COMMAND: .cxr; .ecxr ; kb.

FAILURE_BUCKET_ID: 0x9F_4_USB_vwifimp_IMAGE_vwifibus.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {3feeea6b-6cf3-300d-f10f-3abbe160e412}

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

0: kd> lmvm vwifibus.
Browse full module list.
start end module name.
fffff807`585d0000 fffff807`585de000 vwifibus # (pdb symbols) C:\ProgramData\Dbg\sym\vwifibus.pdb\20D6421CFCAD08D11E874471CF19D53A1\vwifibus.pdb
 Loaded symbol image file: vwifibus.sys
 Mapped memory image file: C:\ProgramData\Dbg\sym\vwifibus.sys\8AF48D2Ce000\vwifibus.sys
 Image path: \SystemRoot\System32\drivers\vwifibus.sys
 Image name: vwifibus.sys
 Browse all global symbols functions data.
 Image was built with /Brepro flag.
 Timestamp: 8AF48D2C (This is a reproducible build file hash, not a timestamp)
 CheckSum: 0000E969.
 ImageSize: 0000E000.
 File version: 10.0.19041.1030
 Product version: 10.0.19041.1030
 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: VWiFiBus.sys
 OriginalFilename: VWiFiBus.sys
 ProductVersion: 10.0.19041.1030
 FileVersion: 10.0.19041.1030 (WinBuild.160101.0800)
 FileDescription: Virtual Wireless Bus Driver

Aygıt Yöneticisi'nden baktığımda USB Wi-Fi adaptörünün sürücü kısmında hata çıkaran aynı sürücüyü gösterdiğini gördüm. Şimdi sürücüyü güncelleştirmeye çalışacağım.
 
Son düzenleyen: Moderatör:
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…