New Ryzen 7000 build crashing and rebooting every 8-12 hours

Question

New Ryzen 7000 build crashing and rebooting every 8-12 hours

Anonymous

New Ryzen 7000 build

Ryzen 9 7900X

32GB G.Skill DDR5 Flare X5 (AMD Expo)

ASRock B650E PG Riptide Wifi

PNY RTX 4070 Ti

All M.2 slots filled

Sabrent Rocket 4.0 Plus 1TB (boot)

WD Black SN770 2TB

WD Blue SATA M.2 2TB

2 14TB Seagate Exos

I have updated all drivers

I have updated the BIOS (3/3/23)

I have reinstalled the chipset drivers

It looks as if the MS storahci.sys is the issue but I don't know of a way to update that

031323-31437-01.zip

Microsoft (R) Windows Debugger Version 10.0.22621.755 AMD64

Loading Dump File [C:\Users\install\Desktop\031323-31437-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 22621 MP (24 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0xfffff8061b800000 PsLoadedModuleList = 0xfffff8061c413430

Debug session time: Mon Mar 13 17:37:35.163 2023 (UTC - 4:00)

System Uptime: 0 days 5:07:32.758

Loading Kernel Symbols

...............................................................

................................................................

.......................

Loading User Symbols

Loading unloaded module list

............

For analysis of this file, run !analyze -v

3: 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: ffffcb0ad9c31050, Physical Device Object of the stack

Arg3: ffffb801f2077198, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack

Arg4: ffffcb0adff1f9c0, The blocked IRP

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec 

Value: 921 

Key  : Analysis.DebugAnalysisManager 

Value: Create 

Key  : Analysis.Elapsed.mSec 

Value: 1011 

Key  : Analysis.Init.CPU.mSec 

Value: 203 

Key  : Analysis.Init.Elapsed.mSec 

Value: 25539 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 101

FILE_IN_CAB: 031323-31437-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008

Kernel Generated Triage Dump

BUGCHECK_CODE: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffcb0ad9c31050

BUGCHECK_P3: ffffb801f2077198

BUGCHECK_P4: ffffcb0adff1f9c0

DRVPOWERSTATE_SUBCODE: 3

DRIVER_OBJECT: ffffcb0ad9ab8ca0

IMAGE_NAME: storahci.sys

MODULE_NAME: storahci

FAULTING_MODULE: fffff806211f0000 storahci

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:

ffffb801f2077148 fffff8061bd71846 : 000000000000009f 0000000000000003 ffffcb0ad9c31050 ffffb801f2077198 : nt!KeBugCheckEx

ffffb801f2077150 fffff8061bd7171c : 0000000000000002 ffffb980dad85180 ffffcb0adff1f2a0 ffffb801f20772c9 : nt!PopIrpWatchdogBugcheck+0x122

ffffb801f20771d0 fffff8061babc09b : ffffcb0a00000002 0000000000000001 ffffb80100000000 0000000000000002 : nt!PopIrpWatchdog+0xc

ffffb801f2077200 fffff8061babd816 : 0000000000000000 0000000000000000 0000000000000000 00000000000abdac : nt!KiProcessExpiredTimerList+0x1eb

ffffb801f2077330 fffff8061bc2e17e : ffffb980dad85180 ffffb980dad85180 ffffcb0ad738d040 ffffcb0ae71d6080 : nt!KiRetireDpcList+0xed6

ffffb801f20775c0 0000000000000000 : ffffb801f2078000 ffffb801f2071000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e

IMAGE_VERSION: 10.0.22621.608

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

3: kd> lmvm storahci

Browse full module list

start end module name

fffff806211f0000 fffff80621222000 storahci (pdb symbols) C:\ProgramData\dbg\sym\storahci.pdb\C1C58BAFD3E29FF64813435F84CDA4671\storahci.pdb

Loaded symbol image file: storahci.sys 

Mapped memory image file: C:\ProgramData\dbg\sym\storahci.sys\3A43E6AD32000\storahci.sys 

Image path: storahci.sys 

Image name: storahci.sys 

Browse all global symbols  functions  data 

Image was built with /Brepro flag. 

Timestamp:        3A43E6AD (This is a reproducible build file hash, not a timestamp) 

CheckSum:         0003853A 

ImageSize:        00032000 

File version:     10.0.22621.608 

Product version:  10.0.22621.608 

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:     storahci.sys 

    OriginalFilename: storahci.sys 

    ProductVersion:   10.0.22621.608 

    FileVersion:      10.0.22621.608 (WinBuild.160101.0800) 

    FileDescription:  MS AHCI Storport Miniport Driver 

    LegalCopyright:   © Microsoft Corporation. All rights reserved.

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

7 answers

Answer 1

Anonymous

Hey! Did you end up figuring this out? I have the same exact build, with the exception of our GPUs and Storage devices!

0 comments

Answer 2

Anonymous

Thank you for the update. Please let me know if you have any quesitons.

Cindy

0 comments

Answer 3

Anonymous

I am running through all of the above steps doing one every evening so it might take a few days to get through everything.

So far sfc /scannow and removal of external devices have yielded no positive results.

0 comments

Answer 4

Hi,

My name is Cindy. I am sorry you are having this problem. I know it is really frustrating. I will do my best to help you with this problem.

Please note: This is a user-to-user community forum. We are users just like you who help others. We are not employees of Microsoft.

You are having a problem with the AHCI Storport Mini Driver. Updating the computer will usually take care of the problem.

Check for new updates on your computer.

Please type the word update in the search and see if there are any new updates. Update if necessary.

On the same page click on the advanced or additional updates.

Update.

If this does not work, go to the website of the maker of the computer. Check for updates on their website.

___

Windows has a feature that allows users to scan for corruptions in Windows system files and restore corrupted files. I have enclosed the directions below. You can cut and paste the code.

Type CMD in the search box. Do not hit enter.
select Run as Administrator then hit enter.
Then type without the quotes. "DISM.exe /Online /Cleanup-image /Restorehealth" and hit enter.

On the same page run these two scans below.

sfc /scannow

DISM /Online /Cleanup-Image /StartComponentCleanup

Please let me know if you have any questions.

Best Wishes,

Cindy

Answer 5

Hi mtxguy74. I am Jacob. I am here to help you with this issue. Let’s get started. From my analysis, it looks like a driver has failed to complete a power IRP within a specific time, causing a DRIVER_POWER_STATE_FAILURE code. Here is a fix I found:

https://softwarekeep.com/help-center/what-is-driver-power-state-failure-in-windows-and-how-to-fix-it

Hope it helps

Share via

New Ryzen 7000 build crashing and rebooting every 8-12 hours

7 answers