Solved Driver_power_state_failure

[meat juice]

Hello,
I have been receiving the BSOD noted in the subject line of this post for some time now. I've done multiple re-installations of Windows, driver updates and so on. Without some guidance related to this blue screen I will remain at a loss as to where to focus my attention. Immediately below is a brief log of the crash and I've also uploaded the logs created with SF Diagnostic Tool. Note below File Description Class Driver for Port/Miniport Devices. I updated the gpu driver and also tried the previous 2 releases. Same with usb drivers and network driver. Thanks for any and all consideration of this issue.

Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`0dbbb050
Parameter 3 : fffff800`00b9c3d8
Parameter 4 : fffffa80`0eb85810
Caused By Driver : portcls.sys
Caused By Address : portcls.sys+6642
File Description : Port Class (Class Driver for Port/Miniport Devices)
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0

 

[YoYo155]

Welcome to SF meat juice .
0x9F which is DRIVER POWER STATE FAILURE that happens in
transitions between power states most commonly S0 (ON state) > S3 (Sleep state)
or vice-verse. You can read more HERE.
The most common cause is a device driver but sometimes it's the hardware itself
that is at fault.

Please upload a picture of your Disk management (Your RAID configuration looks like a complete mess).

• http://www.sevenforums.com/tutorials/274797-disk-management-post-screen-capture-image.html

The problem appears to be coming from your RAID controller.

BugCheck 9F, {3, fffffa800dbbf050, fffff80004a813d8, fffffa8012893c10}

*** WARNING: Unable to verify timestamp for 2310_00.sys
*** ERROR: Module load completed but symbols could not be loaded for 2310_00.sys
[COLOR=Red]Probably caused by : 2310_00.sys[/COLOR]


FAILURE_BUCKET_ID:  X64_0x9F_3_disk_IMAGE_2310_00.sys


!irp fffffa8012893c10

>[ 16, 2]   0 e1 fffffa800dddd060 00000000 fffff88000feff50-00000000 Success Error Cancel pending
           \Driver\Disk    partmgr!PmPowerCompletion
            Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0 e1 fffffa800ddddb90 00000000 00000000-00000000    pending
           \Driver\partmgr

The driver is very very old.

lmvm 2310_00
Browse full module list
start             end                 module name
fffff880`0102e000 fffff880`0105c000   2310_00  T (no symbols)           
    Loaded symbol image file: 2310_00.sys
    Image path: \SystemRoot\system32\DRIVERS\2310_00.sys
    Image name: 2310_00.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=Red]Thu Jun 11 05:16:19 2009[/COLOR]

Name    RocketRAID 230x SATA Controller
Manufacturer    HighPoint
PNP Device ID    PCI\VEN_1103&DEV_2300&SUBSYS_11AB11AB&REV_02\6&25BF1F09&0&00180008
Driver    c:\windows\system32\drivers\2310_00.sys (2.3.9.611, 166.53 KB)

 

[meat juice]

Hi YoYo,

Thanks for responding to my post! Your observations have actually focused on the oldest part in the box. For clarity I have two Highpoint RocketRaid 2300 controller cards.

HighPoint Global website

Neither run in RAID, one is new the other is as old as the driver you pointed out. There was a special manufacturer supplied BIOS I had to use to get both cards to work on the same board. Ran fine for months. As you can see my disk requirements are larger than average.

I had difficulty bringing up the Disk Management Window. The system is clearly struggling with it. Unless you suggest otherwise I'll likely replace the oldest of the two cards.

Attached is the screen shot you requested and thank you again for your help. It truly is appreciated.

Meat Juice

 

[YoYo155]

What will you lose from removing the older card of the two?
Do you have Hard-Drives connected through it?

If you don't feel you have a problem with physically removing it then go ahead, but I'm not sure
what will come of it as I don't know how the HDD's connect and to what.

 

[meat juice]

Little to lose by removing the old card. After doing so the system runs stable x24hrs now. Each card supports 4 hdd. Accordingly I've lost access to 4 drives until I replace the part. I feel very fortunate because it was the least expensive part in the box in addition to the oldest.

More importantly I feel fortunate that your good soul took the time to scour my logs to find the issue. I need to acknowledge that because if it were not for folks like you the world would be a much crappier place. So, thank you very much Yo Yo. You relieved what was turning into one giant time consuming headache.

 

[YoYo155]

Little to lose by removing the old card. After doing so the system runs stable x24hrs now. Each card supports 4 hdd. Accordingly I've lost access to 4 drives until I replace the part. I feel very fortunate because it was the least expensive part in the box in addition to the oldest.

More importantly I feel fortunate that your good soul took the time to scour my logs to find the issue. I need to acknowledge that because if it were not for folks like you the world would be a much crappier place. So, thank you very much Yo Yo. You relieved what was turning into one giant time consuming headache.

That is good to hear!
Keep the thread open for another week or so, asses the situation and post back with an update .

 

[meat juice]

Well Yo Yo, it's been a week and I've had no further BSOD. I think it is relatively safe to say the issue has been resolved in no small part thanks to you. The replacement card is on order and should arrive shortly. Again, I truly appreciate you being there.

Kind regards,

Meat Juice

 

[YoYo155]

Wonderful, happy to be an assistant .