here is the zip file
DRIVER_POWER_STATE_FAILURE
My computer gives bleuscreent immediately after 5 mins here is teh debug file help me please
Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`33600000 PsLoadedModuleList = 0xfffff804`3422a1b0
Debug session time: Wed Jan 26 11:50:12.489 2022 (UTC + 3:00)
System Uptime: 0 days 0:06:21.154
Loading Kernel Symbols
...............................................................
.....Page 44ba12 not present in the dump file. Type ".hh dbgerr004" for details
...........................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`339f70d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8200`7c65f720=000000000000009f
4: 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: 0000000000000003, A device object has been blocking an IRP for too long a time
Arg2: ffffb40dbf144360, Physical Device Object of the stack
Arg3: ffff82007c65f750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffb40dbf176920, The blocked IRP
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2577
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 2667
Key : Analysis.Init.CPU.mSec
Value: 515
Key : Analysis.Init.Elapsed.mSec
Value: 3172
Key : Analysis.Memory.CommitPeak.Mb
Value: 80
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
FILE_IN_CAB: MEMORY.DMP
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffffb40dbf144360
BUGCHECK_P3: ffff82007c65f750
BUGCHECK_P4: ffffb40dbf176920
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: pci.sys
MODULE_NAME: pci
FAULTING_MODULE: fffff80438470000 pci
BLACKBOXACPI: 1 (!blackboxacpi)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
ffff8200`7c65f718 fffff804`33b5fdc7 : 00000000`0000009f 00000000`00000003 ffffb40d`bf144360 ffff8200`7c65f750 : nt!KeBugCheckEx
ffff8200`7c65f720 fffff804`33b5fce1 : ffffb40d`bf1761e8 00000000`00000000 ffffb40d`ce2bb1f0 00000000`00000000 : nt!PopIrpWatchdogBugcheck+0xdf
ffff8200`7c65f790 fffff804`338816f2 : ffffb40d`bf176220 ffffa400`e279f180 ffffa400`e279f180 00000000`00000002 : nt!PopIrpWatchdog+0x31
ffff8200`7c65f7e0 fffff804`338999fd : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`000038e3 : nt!KiProcessExpiredTimerList+0x172
ffff8200`7c65f8d0 fffff804`339fac3e : ffffffff`00000000 ffffa400`e279f180 ffffa400`e27aa340 ffffb40d`ce2c9080 : nt!KiRetireDpcList+0x5dd
ffff8200`7c65fb60 00000000`00000000 : ffff8200`7c660000 ffff8200`7c659000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e
IMAGE_VERSION: 10.0.19041.1387
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x9F_3_AML!_SB.PCI0.SAT0._PS3_ACPI_IMAGE_pci.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {a7b10e60-a004-699b-de4c-0573a3c01757}
Followup: MachineOwner
---------
4: kd> dt ffff82007c65f750
Symbol not found at address ffff82007c65f750.
4: kd> !irp ffffb40dbf176920
Irp is active with 6 stacks 4 is current (= 0xffffb40dbf176ac8)
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
[IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
0 0 ffffb40dbf144360 00000000 fffff804383b11c0-fffff8043838de40
\Driver\pci ACPI!ACPIDeviceIrpDeviceFilterRequest
Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
0 e1 ffffb40dbf14ccd0 00000000 fffff80438894150-00000000 Success Error Cancel pending
\Driver\ACPI storport!RaidAdapterPowerDownDeviceCompletion
Args: 00000000 00000001 00000004 00000000
[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
0 e1 ffffb40dbf16f050 00000000 fffff804339789d0-ffffb40dbf1761e8 Success Error Cancel pending
\Driver\storahci nt!PopRequestCompletion
Args: 00000000 00000001 00000004 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-ffffb40dbf1761e8
Args: 00000000 00000000 00000000 00000000
4: kd> !devstack ffffb40dbf144360
!DevObj !DrvObj !DevExt ObjectName
ffffb40dbf16f050 \Driver\storahci ffffb40dbf16f1a0 RaidPort0
ffffb40dbf14ccd0 \Driver\ACPI ffffb40dbf0c47f0
> ffffb40dbf144360 \Driver\pci ffffb40dbf1444b0 NTPNP_PCI0009
!DevNode ffffb40dbf1848a0 :
DeviceInst is "PCI\VEN_8086&DEV_06D2&SUBSYS_86941043&REV_00\3&11583659&0&B8"
ServiceName is "storahci"
Windows for home | Windows 10 | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
9 answers
Sort by: Most helpful
-
Anonymous
2022-01-26T09:56:04+00:00 -
Anonymous
2022-01-26T09:51:07+00:00 Okay I'll post that file ASAP.
-
Anonymous
2022-01-26T09:40:08+00:00 Hi KHacal
I checked your other thread, that is a debug file not a minidump file, please upload those and provide a link here.
-
Anonymous
2022-01-26T09:36:47+00:00 Thank you,I uploaded the minidump file on other thread with same title.
Or I can upload to this thread if you want
-
Anonymous
2022-01-26T09:26:28+00:00 Hi KHacal
I am Dave, I will help you with this.
Please upload any minidump files you have, I will check those to see if they provide any insight into a potential cause of the system crashes.
Open Windows File Explorer.
Navigate to C:\Windows\Minidump
Copy any minidump files onto your Desktop, then zip those up.
Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.
Then post the link here to the zip file, so we can take a look for you.