Need Some Help Fixing Driver_power_state_failure Bsod

I've had this STOP error several times over the last year and a half and don't know the cause.

DRIVER_POWER_STATE_FAILURE
0x00000024

The latest drivers from the motherboard mfgr. web site are installed.
I did find that the Intel Smart Connect feature was Enabled in the BIOS, although I don't use it and the motherboard driver for that was Not installed.
I've now Disabled that in the BIOS.

I do have a minidump file from the latest crash, but I don't know how to use it.

There are (3) devices attached via USB:

• mouse
• all-in-one printer
• APC backup power supply

The cable connector at the BPS often gets loose and there is a communication error popup message from the task bar.
Reinserting the cable connector (RJ-45?) fixes that. I don't know if that is related to this error or if a new cable would help.

The printer was turned Off.

Otherwise, everything else works well.

I did install a new SSD for the system drive three days ago, but it's working OK, and this began happening about a year and a half ago.

I'm at a loss as to what to do next. ???

 

Sounds like a 0x9f:

There are some MS Hotfixes listed in the link above, if your scenario+OS matches any of the descriptions given.

Copy the minidump to the Desktop, zip it and attach the zip, I'll take a look at it.

 

Thanks, satrow.
I'll look over those Hotfixes.
zipped minidump is attached.

 

Looks like your Atheros Ethernet driver was causing (blamed, at least) the problem, it had been sent a power down request but hadn't responded to it. Might be some other related driver interfering, possibly a poor setting for the hardware (if it's a Desktop/tower), set the Ethernet controller in Device Manager and Power(Control Panel) setting advanced so that it isn't allowed to power down by either one.

Update the driver (I think this is the correct one).

 

I removed and reinstalled the driver, from ASRock downloads. It's the same version number as the one you linked to.

Device Manager -> Properties -> Advanced -> Shutdown Wake Up was Enabled
Device Manager -> Properties -> Power Management -> Allow the computer to turn off this deveice to save power was Enabled
Both Disabled now. Nothing related in System Power Options.

There is a Hotfix for this issue from the source you gave:
Stop error when you put a computer that is running Windows 7 or Windows Server 2008 R2 to sleep or into hibernation...: "0x9F"

Should I apply this hotfix? It seems appropriate?

Thank you for your help, satrow. I think this will lick the problem.


I gave the wrong number in my original post.
The 0x24 was a ntfs.sys error, maybe caused by initial virtual memory setting being too low. I increased that to 1025MB and it hasn't happened again.

 

The recommended virtual memory is 1.5 times the physical memory.
Or you could select System managed size.

 

Run that Hotfix but check Windows Update again afterwards, the fix is from 2009 so some files might be outdated by now.

 

The hotfix ran for about 20 seconds and displayed a message that it does not apply to this computer.
I'm satisfied that for now, the problem has been remedied.

Thanks for the suggestion.

In my case that would result in a 12 Gigabyte pagefile.
I haven't used the System Managed virtual memory in a very long time, so I gave it a try just to see what it would do.
The result was a pagefile of 7843MB.

I think that's too big for a 120GB SSD, but I'll try that for a while and see how it performs.
My usual setting is 1024MB Initial and 2048MB Maximum. I've had no problems with that.

The Samsung Magician SSD utility recommends a custom setting with 200MB initial size and 2048MB maximum size.
I think that's too small for the initial size. I may have been using something like 512MB initial size when the 0x24 error occurred.

That's not really a likely cause of this BSOD.
STOP 0x00000024: NTFS_FILE_SYSTEM

Bug Check 0x24: NTFS_FILE_SYSTEM

 

Dump(s), please?

 

At the time I posted the 0x24 stuff, I did not have a dump for that because it happened some time ago.
Maybe one of the disk cleanup tools is deleting them.

It happened again during the last Windows shut down.
Virtual Memory was set to System Managed.

I've run chkdsk /r on both SSD from the Windows install CD and also a memory check.
No errors were found by either of those.
The install CD did add bootmgr to the default boot drive.

 

How many drives are in the PC, is there RAID setup or a caching SSD?

I'm wondering whether IntelRST is running interference here. It's not needed except for RAID or an SSD caching setup. Using it only adds an extra driver to both the drive controller and to the drive compared to running the default MS SATA AHCI Controller driver. Uninstall/replacement method here.

Analysis below, not that it means much to me, looks like *something* started a thread that required sole access to virtual memory but presumably *something else* denied it access... similar topics I've found online look to be inconclusive or way beyond my limited debugging scope:

Windbg description of this Bugcheck:

 

Thanks for checking this out, satrow. Much appreciated!
This is very helpful.

There are two SSD's and one HDD. The second SSD was cloned from the first.
No RAID or drive caching.

Intel Rapid Storage Technology had been installed.
The removal procedure works well for replacing the driver with Standard AHCI Controller.
Only one of the IntelRST drivers is able to be removed.
The other two never show in Device Manager, but do show in DriverView and Autoruns.
Attempts by others to rename iaStorF to disable it resulted in BSOD at bootup.
Judging from the discussion, no one was able to successfully remove/disable iaStorF or iaStorV.

I didn't know if Rapid Storage should or should not be installed.
I fell for the hype and claims of performance magic. Best Never to install it.

Intel® Rapid Storage Technology Product Overview

THANKS.

 

Hmm, I haven't checked out all the comments for some time, I do have some history with Patrick's article, we were in discussion over it during the planning stages. At that time, both my machines had (already) failed to get rid of iastor*X* as well, I'd put that down to the age of the install and my usual 'messing' with Windows' innards.

Tell Intel: "MS SATA controllers use AHCI/NCQ as well, fewer overheads, often better throughput, too.".

If/next time it crashes, upload the minidump and run MSInfo32, click through the output so that it's fully populated and then save it as the default MSInfo32.arn. Zip that and attach the zip or that, too.