Solved BSOD Power State Failure

[JokerNfear]

i have 3 identical computer's and all crash to blue screen with a Power State Failure.i have not been able to figure out why. all system are fresh install of windows with windows updates and up to date drivers for there sites.system specs have been filled out windows 7 pro 64bit installed on ssd solo the 2x tb drives in raid 0 are for temp storage. ive come here cause i think ive been look at the problem to long and might be a simple fix im just not seeing



*edit* attached file been created using Seven forums utility

 

[Arc]

The BSOD is caused by LSI Adapter, SAS2 2008 Falcon (c:\windows\system32\drivers\lsi_sas2.sys). And the driver is very old, of 2009.

I am totally against using third party storport drivers, but disabling it may need a clean install. In that case, your first try should be updating it from Download Search.

Also, you need to uninstall Virtual CloneDrive.

Let us know the results.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 9F[/COLOR], {3, fffffa8006e2c570, fffff80004479518, fffffa800785e580}

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

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8006e2c570, Physical Device Object of the stack
Arg3: fffff80004479518, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800785e580, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

[COLOR=Red]IMAGE_NAME:  lsi_sas2.sys[/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  4a11fdf4

MODULE_NAME: lsi_sas2

FAULTING_MODULE: fffff88000cc0000 lsi_sas2

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF8000447FFB0

STACK_TEXT:  
fffff800`044794c8 fffff800`0314d8c2 : 00000000`0000009f 00000000`00000003 fffffa80`06e2c570 fffff800`04479518 : nt!KeBugCheckEx
fffff800`044794d0 fffff800`030e885c : fffff800`04479600 fffff800`04479600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`04479570 fffff800`030e86f6 : fffff800`0328df80 00000000`0020b162 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`044795e0 fffff800`030e85de : 0000004d`d25ef89b fffff800`04479c58 00000000`0020b162 fffff800`0325bec8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04479c30 fffff800`030e83c7 : 00000014`969565c1 00000014`0020b162 00000014`96956593 00000000`00000062 : nt!KiTimerExpiration+0x1be
fffff800`04479cd0 fffff800`030d588a : fffff800`03258e80 fffff800`03266cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04479d80 00000000`00000000 : fffff800`0447a000 fffff800`04474000 fffff800`04479d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_disk_IMAGE_lsi_sas2.sys

[COLOR=Red]BUCKET_ID:  X64_0x9F_3_disk_IMAGE_lsi_sas2.sys[/COLOR]

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

0: kd> lmvm lsi_sas2
start             end                 module name
fffff880`00cc0000 fffff880`00cd3000   lsi_sas2 T (no symbols)           
    Loaded symbol image file: lsi_sas2.sys
    Image path: \SystemRoot\system32\drivers\lsi_sas2.sys
[B][COLOR=Red]    Image name: lsi_sas2.sys
    Timestamp:        Tue May 19 06:01:48 2009[/COLOR][/B] (4A11FDF4)
    CheckSum:         0002002E
    ImageSize:        00013000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> !irp fffffa800785e580
Irp is active with 4 stacks 2 is current (= 0xfffffa800785e698)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [ 16, 0]   0  0 fffffa8006e2c570 00000000 fffff88001913d30-fffffa80075745a0    
           [COLOR=Red]\Driver\LSI_SAS2    CLASSPNP!ClasspPowerUpCompletion[/COLOR]
            Args: 00000000 00000000 00000000 00000002
>[ 16, 2]   0 e1 fffffa8007574060 00000000 fffff88000e45f50-00000000 [COLOR=Red]Success Error Cancel pending
           \Driver\Disk    partmgr!PmPowerCompletion[/COLOR]
            Args: 00041100 00000001 00000001 00000002
 [ 16, 2]   0 e1 fffffa8007574b90 00000000 00000000-00000000   [COLOR=Red] pending
           \Driver\partmgr[/COLOR]
            Args: 00041100 00000001 00000001 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800917f790    

            Args: 00000000 00000000 00000000 00000000
0: kd> !devobj fffffa8007574060
Device object (fffffa8007574060) is for:
 InfoMask field not found for _OBJECT_HEADER at fffffa8007574030
 \Driver\Disk DriverObject fffffa8007558140
Current Irp 00000000 RefCount 0 Type 00000007 Flags 01002050
Vpb fffffa8007452b20 DevExt fffffa80075741b0 DevObjExt fffffa8007574858 Dope fffffa8007452ab0 
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
A[COLOR=Red]ttachedDevice (Upper) [B]fffffa8007574b90 \Driver\partmgr[/B]
AttachedTo (Lower) [B]fffffa8006e2c570 \Driver\LSI_SAS2[/B][/COLOR]
Device queue is not busy.

 

[JokerNfear]

Ok ive done what you said and installed new drivers from LSI for the SAS9211-8i LSI Adaptor and uninstalled Virtual CloneDrive. give me 24 hrs to be sure its fixed ty so much for your help so far Arc you a boss

 

[JokerNfear]

ok so it crashed again this time i turned monitor off let it go to sleep and next morning i woke up to below plus i reran the SF tool and attached and like before thank you ahead of time for your help

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8006E1E300
BCP3: FFFFF80000B9C518
BCP4: FFFFFA8008FFEE10
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\110413-22557-01.dmp
C:\Users\Two\AppData\Local\Temp\WER-25116-1.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[x BlueRobot]

0: kd> [COLOR="SeaGreen"]lmvm lsi_sas2[/COLOR]
start             end                 module name
fffff880`00c77000 fffff880`00c95000   lsi_sas2 T (no symbols)           
    Loaded symbol image file: lsi_sas2.sys
    Image path: \SystemRoot\system32\drivers\lsi_sas2.sys
    Image name: lsi_sas2.sys
    Timestamp:       [COLOR="Red"] Tue Jan 29 17:28:46 2013[/COLOR] (510806CE)
    CheckSum:         000278C4
    ImageSize:        0001E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I would suggest removing the driver completely, since it seems to be still be causing the exact same problem.

Create a backup of all your important files, and then remove the driver via Device Manager.

Reboot the computer after removal. Windows should auto-configure it's own driver.

 

[JokerNfear]

ok took a couple tries cause it keep crashing while uninstalling the driver but i got it uninstalled giving this s try thank you guys so far for the help

 

[JokerNfear]

ok crashed again uploading new SF tool zip with dump file i uninstalled the driver and let windows install its own i made sure the virtual clone driver was uninstalled also. i was watching netflix as this crash happened

 

[JokerNfear]

is it possible that its error in driver and this type of system setup like chipset and all its just incomparable with that practical LSI Card. dose this have the chance of being even fixed without just removing the card? cause what ive picked up from the help is it seem to be the LSI Card only

 

[x BlueRobot]

The latest dump file still shows the driver as being installed for some reason.

It's a problem with the driver code.

 

[JokerNfear]

im placing it solved ty Arc and BlueRobot for all your help guys we know its the card and if i remove solves it ill try different versions of drivers to make sure but this is resolved in my eyes Thank you again

 

[x BlueRobot]

Glad to be able of some assistance