Çözüldü Drıver_power_state_faılure mavi ekran

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
İşletim sistemi
Windows 10
M

Mustafa911

Kilopat
Katılım
7 Mart 2015
Mesajlar
9
Başlıkta belirttiğim hatayı aldım ama minidump dosyasına erişim sağlayamıyorum. Nasıl bir yol izlemeliyim?

Adsız.png
 
Çözüm
Enes3078
Sorun IObit yazılımları. Sisteme temiz kurulum yapın ve bir daha IObit yazılımı kullanmayın. Formata rağmen sorun çözülmezse bildirin.

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

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: ffff9c069c1deb20, Physical Device Object of the stack
Arg3: fffff8017e8e6ba0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff9c06bea20a20, The blocked IRP

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 10358

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 93154

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

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

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

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: ffff9c069c1deb20

BUGCHECK_P3: fffff8017e8e6ba0

BUGCHECK_P4: ffff9c06bea20a20

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: ACPI.sys

MODULE_NAME: ACPI

FAULTING_MODULE: fffff8017ba80000 ACPI

PROCESS_NAME: System

DPC_STACK_BASE: FFFFF8017E8E6FB0

STACK_TEXT:
fffff801`7e8e6b68 fffff801`78f5f787 : 00000000`0000009f 00000000`00000003 ffff9c06`9c1deb20 fffff801`7e8e6ba0 : nt!KeBugCheckEx
fffff801`7e8e6b70 fffff801`78f5f6a1 : ffff9c06`baaba7a0 ffff9c06`ae5c2760 00000000`00000000 00000000`010eb0e1 : nt!PopIrpWatchdogBugcheck+0xdf
fffff801`7e8e6be0 fffff801`78c44f12 : ffff9c06`baaba7d8 fffff801`74746180 fffff801`7e8e6e68 fffff801`00000002 : nt!PopIrpWatchdog+0x31
fffff801`7e8e6c30 fffff801`78c06eed : fffff801`74746180 00000000`00000000 00000000`00000008 00000000`010eb0e1 : nt!KiProcessExpiredTimerList+0x172
fffff801`7e8e6d20 fffff801`78dfcdf5 : 00000000`00000000 fffff801`74746180 fffff801`796f3ba0 ffff9c06`adb58098 : nt!KiRetireDpcList+0x5dd
fffff801`7e8e6fb0 fffff801`78dfcbe0 : 00000000`00001001 fffff801`78cec5ca ffff9c06`adb58098 00000000`0010a804 : nt!KxRetireDpcList+0x5
ffffc286`a3526490 fffff801`78dfc495 : ffff9c06`adb58098 fffff801`78df7e41 00000000`00042802 fffff801`945f4563 : nt!KiDispatchInterruptContinue
ffffc286`a35264c0 fffff801`78df7e41 : 00000000`00042802 fffff801`945f4563 00000000`00000000 fffff801`94673e98 : nt!KiDpcInterruptBypass+0x25
ffffc286`a35264d0 fffff801`945e4d62 : 00000000`0010a008 ffff9c06`adb57000 ffff9c06`adb58098 00000000`0010a008 : nt!KiInterruptDispatchNoLockNoEtw+0xb1
ffffc286`a3526660 00000000`0010a008 : ffff9c06`adb57000 ffff9c06`adb58098 00000000`0010a008 00000000`00000000 : nvlddmkm+0x84d62
ffffc286`a3526668 ffff9c06`adb57000 : ffff9c06`adb58098 00000000`0010a008 00000000`00000000 00000000`00000000 : 0x10a008
ffffc286`a3526670 ffff9c06`adb58098 : 00000000`0010a008 00000000`00000000 00000000`00000000 ffff9c06`acc13790 : 0xffff9c06`adb57000
ffffc286`a3526678 00000000`0010a008 : 00000000`00000000 00000000`00000000 ffff9c06`acc13790 fffff801`94673ffd : 0xffff9c06`adb58098
ffffc286`a3526680 00000000`00000000 : 00000000`00000000 ffff9c06`acc13790 fffff801`94673ffd 00000000`00000020 : 0x10a008


IMAGE_VERSION: 10.0.19041.488

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x9F_3_i8042prt_IMAGE_ACPI.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a42f147e-922c-d9e0-658e-1c9f7b2cb9ff}

Followup: MachineOwner
---------[/CODE]
Tarihe göre sırala Puana göre sırala
warped dedi:
WinDbg'yi yönetici olarak başlatın.
Genişletmek için tıkla...
Denedim ama bi sonuç alamadım.
anomalynx dedi:
Dump dosyalarınızı paylaşın bi'.
Genişletmek için tıkla...
Dosyayı upload edemiyorum, yönetici izni istiyor ki zaten ben yöneticiyim.
Enes3078 dedi:
Dosyaya sağ tık kopyala deyip masaüstüne yapıştırın. Sonra da MediaFire'a upload edin. İndirme linkini de bizimle paylaşın.
Genişletmek için tıkla...
Dosya şu an masaüstü ama yine aynı sorun mevcut, yönetici izni istiyor anlamış değilim.
Sorun benden kaynaklıymış. Dosyayı MediaFire'a upload ettim.
Minidump dosyası.
 
Artı 0 Eksi
Mustafa911 dedi:
Denedim ama bi sonuç alamadım.

Dosyayı upload edemiyorum, yönetici izni istiyor ki zaten ben yöneticiyim.

Dosya şu an masaüstü ama yine aynı sorun mevcut, yönetici izni istiyor anlamış değilim.
Sorun benden kaynaklıymış. Dosyayı MediaFire'a upload ettim.
Minidump dosyası.
Genişletmek için tıkla...
Tamam o zaman @Enes3078.
 
Artı 0 Eksi
Sorun IObit yazılımları. Sisteme temiz kurulum yapın ve bir daha IObit yazılımı kullanmayın. Formata rağmen sorun çözülmezse bildirin.

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

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: ffff9c069c1deb20, Physical Device Object of the stack
Arg3: fffff8017e8e6ba0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff9c06bea20a20, The blocked IRP

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 10358

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 93154

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

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

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

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: ffff9c069c1deb20

BUGCHECK_P3: fffff8017e8e6ba0

BUGCHECK_P4: ffff9c06bea20a20

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: ACPI.sys

MODULE_NAME: ACPI

FAULTING_MODULE: fffff8017ba80000 ACPI

PROCESS_NAME: System

DPC_STACK_BASE: FFFFF8017E8E6FB0

STACK_TEXT:
fffff801`7e8e6b68 fffff801`78f5f787 : 00000000`0000009f 00000000`00000003 ffff9c06`9c1deb20 fffff801`7e8e6ba0 : nt!KeBugCheckEx
fffff801`7e8e6b70 fffff801`78f5f6a1 : ffff9c06`baaba7a0 ffff9c06`ae5c2760 00000000`00000000 00000000`010eb0e1 : nt!PopIrpWatchdogBugcheck+0xdf
fffff801`7e8e6be0 fffff801`78c44f12 : ffff9c06`baaba7d8 fffff801`74746180 fffff801`7e8e6e68 fffff801`00000002 : nt!PopIrpWatchdog+0x31
fffff801`7e8e6c30 fffff801`78c06eed : fffff801`74746180 00000000`00000000 00000000`00000008 00000000`010eb0e1 : nt!KiProcessExpiredTimerList+0x172
fffff801`7e8e6d20 fffff801`78dfcdf5 : 00000000`00000000 fffff801`74746180 fffff801`796f3ba0 ffff9c06`adb58098 : nt!KiRetireDpcList+0x5dd
fffff801`7e8e6fb0 fffff801`78dfcbe0 : 00000000`00001001 fffff801`78cec5ca ffff9c06`adb58098 00000000`0010a804 : nt!KxRetireDpcList+0x5
ffffc286`a3526490 fffff801`78dfc495 : ffff9c06`adb58098 fffff801`78df7e41 00000000`00042802 fffff801`945f4563 : nt!KiDispatchInterruptContinue
ffffc286`a35264c0 fffff801`78df7e41 : 00000000`00042802 fffff801`945f4563 00000000`00000000 fffff801`94673e98 : nt!KiDpcInterruptBypass+0x25
ffffc286`a35264d0 fffff801`945e4d62 : 00000000`0010a008 ffff9c06`adb57000 ffff9c06`adb58098 00000000`0010a008 : nt!KiInterruptDispatchNoLockNoEtw+0xb1
ffffc286`a3526660 00000000`0010a008 : ffff9c06`adb57000 ffff9c06`adb58098 00000000`0010a008 00000000`00000000 : nvlddmkm+0x84d62
ffffc286`a3526668 ffff9c06`adb57000 : ffff9c06`adb58098 00000000`0010a008 00000000`00000000 00000000`00000000 : 0x10a008
ffffc286`a3526670 ffff9c06`adb58098 : 00000000`0010a008 00000000`00000000 00000000`00000000 ffff9c06`acc13790 : 0xffff9c06`adb57000
ffffc286`a3526678 00000000`0010a008 : 00000000`00000000 00000000`00000000 ffff9c06`acc13790 fffff801`94673ffd : 0xffff9c06`adb58098
ffffc286`a3526680 00000000`00000000 : 00000000`00000000 ffff9c06`acc13790 fffff801`94673ffd 00000000`00000020 : 0x10a008


IMAGE_VERSION: 10.0.19041.488

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x9F_3_i8042prt_IMAGE_ACPI.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a42f147e-922c-d9e0-658e-1c9f7b2cb9ff}

Followup: MachineOwner
---------[/CODE]
 
Artı 0 Eksi
Çözüm
Enes3078 dedi:
Sorun IObit yazılımları. Sisteme temiz kurulum yapın ve bir daha IObit yazılımı kullanmayın. Formata rağmen sorun çözülmezse bildirin.

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

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: ffff9c069c1deb20, Physical Device Object of the stack.
Arg3: fffff8017e8e6ba0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack.
Arg4: ffff9c06bea20a20, The blocked IRP.

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 10358.

Key : Analysis.DebugAnalysisManager
Value: Create.

Key : Analysis.Elapsed.mSec
Value: 93154.

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

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

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

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: ffff9c069c1deb20.

BUGCHECK_P3: fffff8017e8e6ba0.

BUGCHECK_P4: ffff9c06bea20a20.

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: ACPI.sys

MODULE_NAME: ACPI.

FAULTING_MODULE: fffff8017ba80000 ACPI.

PROCESS_NAME: System.

DPC_STACK_BASE: FFFFF8017E8E6FB0.

STACK_TEXT:
fffff801`7e8e6b68 fffff801`78f5f787 : 00000000`0000009f 00000000`00000003 ffff9c06`9c1deb20 fffff801`7e8e6ba0 : nt!KeBugCheckEx
fffff801`7e8e6b70 fffff801`78f5f6a1 : ffff9c06`baaba7a0 ffff9c06`ae5c2760 00000000`00000000 00000000`010eb0e1 : nt!PopIrpWatchdogBugcheck+0xdf
fffff801`7e8e6be0 fffff801`78c44f12 : ffff9c06`baaba7d8 fffff801`74746180 fffff801`7e8e6e68 fffff801`00000002 : nt!PopIrpWatchdog+0x31
fffff801`7e8e6c30 fffff801`78c06eed : fffff801`74746180 00000000`00000000 00000000`00000008 00000000`010eb0e1 : nt!KiProcessExpiredTimerList+0x172
fffff801`7e8e6d20 fffff801`78dfcdf5 : 00000000`00000000 fffff801`74746180 fffff801`796f3ba0 ffff9c06`adb58098 : nt!KiRetireDpcList+0x5dd
fffff801`7e8e6fb0 fffff801`78dfcbe0 : 00000000`00001001 fffff801`78cec5ca ffff9c06`adb58098 00000000`0010a804 : nt!KxRetireDpcList+0x5
ffffc286`a3526490 fffff801`78dfc495 : ffff9c06`adb58098 fffff801`78df7e41 00000000`00042802 fffff801`945f4563 : nt!KiDispatchInterruptContinue
ffffc286`a35264c0 fffff801`78df7e41 : 00000000`00042802 fffff801`945f4563 00000000`00000000 fffff801`94673e98 : nt!KiDpcInterruptBypass+0x25
ffffc286`a35264d0 fffff801`945e4d62 : 00000000`0010a008 ffff9c06`adb57000 ffff9c06`adb58098 00000000`0010a008 : nt!KiInterruptDispatchNoLockNoEtw+0xb1
ffffc286`a3526660 00000000`0010a008 : ffff9c06`adb57000 ffff9c06`adb58098 00000000`0010a008 00000000`00000000 : nvlddmkm+0x84d62
ffffc286`a3526668 ffff9c06`adb57000 : ffff9c06`adb58098 00000000`0010a008 00000000`00000000 00000000`00000000 : 0x10a008.
ffffc286`a3526670 ffff9c06`adb58098 : 00000000`0010a008 00000000`00000000 00000000`00000000 ffff9c06`acc13790 : 0xffff9c06`adb57000
ffffc286`a3526678 00000000`0010a008 : 00000000`00000000 00000000`00000000 ffff9c06`acc13790 fffff801`94673ffd : 0xffff9c06`adb58098
ffffc286`a3526680 00000000`00000000 : 00000000`00000000 ffff9c06`acc13790 fffff801`94673ffd 00000000`00000020 : 0x10a008.

IMAGE_VERSION: 10.0.19041.488

STACK_COMMAND: .thread ; .cxr ; kb.

FAILURE_BUCKET_ID: 0x9F_3_i8042prt_IMAGE_ACPI.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {a42f147e-922c-d9e0-658e-1c9f7b2cb9ff}

Followup: MachineOwner.
---------[/CODE]
Genişletmek için tıkla...

İlgilendiğiniz için teşekkür ederim.
 
Artı 0 Eksi
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.

Benzer konular

D
  • Soru
Lenovo Z580 "Drıver_power_state_faılure" mavi ekran hatası
Mesaj
1
Görüntüleme
369
Murat5038
Murat5038
Metin can
  • Soru
Mavi ekran hatası
Mesaj
4
Görüntüleme
1.078
246941
2
Oktay_Aygun
  • Soru
Mavi ekran hatası
Mesaj
3
Görüntüleme
901
Oktay_Aygun
Oktay_Aygun
H
  • Soru
Mavi ekran analizi
Mesaj
1
Görüntüleme
722
Ma'at
Ma'at
Sefa ATICI
  • Soru
Mavi ekran hatası
Mesaj
1
Görüntüleme
599
Lindorie Miriel
Lindorie Miriel

Bu konuyu görüntüleyen kullanıcılar

Toplam: 2 (üye: 0, misafir: 2)

Technopat Haberler

Yeni konular

Yeni mesajlar

Geri
Yukarı