1 Reply Latest reply on Mar 25, 2013 11:53 AM by Diego_Intel

    Blue Screen - Driver Power State Failure

    jeffh

      My laptop does not shut down completely when powered off. I got a blue screen indicating that there was a Driver Power State Failure. I got someone to review the dump files from the last two failures. There seems to be an issue with my iastor driver (Version 8.9.2.1002). I've been trying to find an update to the drive, but can't find one in the support section on the site. Can someone help me out here?

       

      P.S. My BIOS is INSYDE 1.70 , 09/15/2009; model number A500-ST5601; OS: Windows 7

       

       

      Dump message below:

       

      Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
      Machine Name:
      Kernel base = 0xfffff800`03051000 PsLoadedModuleList = 0xfffff800`0328ee50
      Debug session time: Thu May  6 13:08:54.983 2010 (GMT-4)
      System Uptime: 0 days 8:20:22.918
      Loading Kernel Symbols
      ...............................................................
      ................................................................
      .................................
      Loading User Symbols
      Loading unloaded module list
      ........
      *******************************************************************************
      *                                                                             *
      *                        Bugcheck Analysis                                    *
      *                                                                             *
      *******************************************************************************
      
      Use !analyze -v to get detailed debugging information.
      
      BugCheck 1000009F, {4, 258, fffffa8003d00040, fffff80000b9c4d0}
      
      Unable to load image \SystemRoot\system32\DRIVERS\iaStor.sys, Win32 error 0n2
      *** WARNING: Unable to verify timestamp for iaStor.sys
      *** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
      *** WARNING: Unable to verify timestamp for win32k.sys
      *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
      Probably caused by : memory_corruption
      
      Followup: memory_corruption
      ---------
      
      0: kd> !analyze -v
      *******************************************************************************
      *                                                                             *
      *                        Bugcheck Analysis                                    *
      *                                                                             *
      *******************************************************************************
      
      DRIVER_POWER_STATE_FAILURE (9f)
      A driver is causing an inconsistent power state.
      Arguments:
      Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
          subsystem.
      Arg2: 0000000000000258, Timeout in seconds.
      Arg3: fffffa8003d00040, The thread currently holding on to the Pnp lock.
      Arg4: fffff80000b9c4d0
      
      Debugging Details:
      ------------------
      
      
      DRVPOWERSTATE_SUBCODE:  4
      
      FAULTING_THREAD:  fffffa8003d00040
      
      CUSTOMER_CRASH_COUNT:  1
      
      DEFAULT_BUCKET_ID:  CODE_CORRUPTION
      
      BUGCHECK_STR:  0x9F
      
      PROCESS_NAME:  System
      
      CURRENT_IRQL:  2
      
      LAST_CONTROL_TRANSFER:  from fffff800030c8752 to fffff800030c74da
      
      STACK_TEXT:  
      fffff880`02fd2130 fffff800`030c8752 : fffffa80`03d00040 fffffa80`03d00040 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
      fffff880`02fd2270 fffff800`030ca8af : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
      fffff880`02fd2300 fffff800`031d17f5 : fffffa80`05e30c00 fffffa80`00000000 fffffa80`04a69b00 fffffa80`05e5a300 : nt!KeWaitForSingleObject+0x19f
      fffff880`02fd23a0 fffff880`01104c28 : fffffa80`046d91a0 fffffa80`046d9050 00000000`00000001 00000000`00000000 : nt!IoReleaseRemoveLockAndWaitEx+0x45
      fffff880`02fd23e0 fffffa80`046d91a0 : fffffa80`046d9050 00000000`00000001 00000000`00000000 00000000`00000020 : iaStor+0x50c28
      fffff880`02fd23e8 fffffa80`046d9050 : 00000000`00000001 00000000`00000000 00000000`00000020 fffff880`01042a80 : 0xfffffa80`046d91a0
      fffff880`02fd23f0 00000000`00000001 : 00000000`00000000 00000000`00000020 fffff880`01042a80 fffffa80`05e67030 : 0xfffffa80`046d9050
      fffff880`02fd23f8 00000000`00000000 : 00000000`00000020 fffff880`01042a80 fffffa80`05e67030 fffffa80`046d91a0 : 0x1
      
      
      STACK_COMMAND:  .thread 0xfffffa8003d00040 ; kb
      
      CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
          fffff800030c7805 - nt!SwapContext_PatchXSave+2
          [ 01:21 ]
          fffff800030c78e8 - nt!SwapContext_PatchXRstor+2 (+0xe3)
          [ 09:29 ]
          fffff800030c7aa5 - nt!EnlightenedSwapContext_PatchXSave+2 (+0x1bd)
          [ 01:21 ]
          fffff800030c7b8a - nt!EnlightenedSwapContext_PatchXRstor+2 (+0xe5)
          [ 09:29 ]
      4 errors : !nt (fffff800030c7805-fffff800030c7b8a)
      
      MODULE_NAME: memory_corruption
      
      IMAGE_NAME:  memory_corruption
      
      FOLLOWUP_NAME:  memory_corruption
      
      DEBUG_FLR_IMAGE_TIMESTAMP:  0
      
      MEMORY_CORRUPTOR:  ONE_BIT_LARGE
      
      FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE
      
      BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE
      
      Followup: memory_corruption
      ---------