Computer restarting Bugcheck 0x0000009f

Anonymous
2023-06-10T12:35:22+00:00

Hey, my PC is rebooting every now and again with the following error in event viewer

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffb9827c20f050, 0xfffff8041386f178, 0xffffb9827e0cb8a0). A dump was saved in: C:\Windows\Minidump\061023-20265-01.dmp. Report Id: 4bbb2d9f-ebcf-4a88-8ef3-bb92d9267c47.

This is what comes up when I open the DMP file

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\061023-20265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff804`16800000 PsLoadedModuleList = 0xfffff804`174134d0
Debug session time: Sat Jun 10 13:24:19.026 2023 (UTC + 1:00)
System Uptime: 0 days 3:47:14.662
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`16c2c0f0 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffff804`1386f130=000000000000009f
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: 0000000000000003, A device object has been blocking an IRP for too long a time
Arg2: ffffb9827c20f050, Physical Device Object of the stack
Arg3: fffff8041386f178, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffb9827e0cb8a0, The blocked IRP

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1000

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 1088

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

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

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

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x9f

    Key  : Bugcheck.Code.Register
    Value: 0x9f

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

FILE_IN_CAB:  061023-20265-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffb9827c20f050

BUGCHECK_P3: fffff8041386f178

BUGCHECK_P4: ffffb9827e0cb8a0

DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: ffffb98279f49d50

IMAGE_NAME:  storahci.sys

MODULE_NAME: storahci

FAULTING_MODULE: fffff80419dd0000 storahci

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffff804`1386f128 fffff804`16d9c596     : 00000000`0000009f 00000000`00000003 ffffb982`7c20f050 fffff804`1386f178 : nt!KeBugCheckEx
fffff804`1386f130 fffff804`16d9c46c     : 00000000`00000002 fffff804`1252e180 ffffb982`7e328280 fffff804`1386f2a9 : nt!PopIrpWatchdogBugcheck+0x122
fffff804`1386f1b0 fffff804`16ab5ccb     : ffffb982`00000003 00000000`00000001 fffff804`00000000 00000000`00000002 : nt!PopIrpWatchdog+0xc
fffff804`1386f1e0 fffff804`16ab3834     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff804`125359a8 : nt!KiProcessExpiredTimerList+0x1eb
fffff804`1386f310 fffff804`16c30eee     : 00000000`00000000 fffff804`1252e180 fffff804`1754c6c0 ffffb982`976a90c0 : nt!KiRetireDpcList+0xa94
fffff804`1386f5c0 00000000`00000000     : fffff804`13870000 fffff804`13869000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e

IMAGE_VERSION:  10.0.22621.1690

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x9F_3_IMAGE_storahci.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {21defffd-4d1f-b62d-8f72-d4892aa9cff8}

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

Any idea what is causing this and how to fix?

Thanks
Windows for home | Windows 11 | Performance and system failures

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.

0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Anonymous
    2023-06-10T13:07:29+00:00

    Hello,

    I'm Mostafa, and I'm here to assist you.

    Could you please share the minidump that your PC made?

    Go to C:\Windows\Minidump > Zip those files >Upload the zip file to the Cloud > Then share the link here.

    https://support.microsoft.com/en-US/office/shar...

    Thank you.

    0 comments No comments
  2. Anonymous
    2023-06-10T15:11:45+00:00

    Here you go, thanks

    https://we.tl/t-UpL05uzScT

    0 comments No comments
  3. Anonymous
    2023-06-10T15:34:40+00:00

    Thank you for sharing. The minidump indicates BSOD caused by the storage controller driver.

    1. Hold the Windows key down, then press R.
    2. Type devmgmt.msc and click on OK. This will open the Device Manager.
    3. Click on View from the top menu bar and check – Show hidden devices.
    4. Expand the category IDE ATA/ATAPI controllers. Your SATA controller(s) should be specified inside this section.
    5. Right-click on each item in this category's list and select Update driver.
    6. Select – Search automatically for drivers.
    7. If Windows detects a driver update, it will immediately download and install it on your system.
    8. When this option fails, manually locate the drivers on the manufacturer's website, and download and install them from there.

    If that does not help, please update BIOS by visiting its manufacturer's website.

    0 comments No comments