locked
Windows 7 BSOD - DRIVER_POWER_STATE_FAILURE another one RRS feed

  • Question

  • Hy!

     

    I have a dell studio laptop, and I got BSOD problem every time when the laptop try to hibernate.

    My minidump file is here:

    http://cid-0ab1b136cac063fa.office.live.com/self.aspx/.Public/051411-48641-01.dmp

     

    Could you send me also the way how can you identify the problematic driver from the following information( if it possible). I got this kind of problem at the last 1 year, and i really wanted o trace the problematic drivers.

    I also installed the windows sdk with debug tolls. But i can't identify the problematic driver (Unknown_Image ( ANALYSIS_INCONCLUSIVE )

    ) This is the output from windbg:

     

    Thanks for your further help!

     

    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.

     

     

    Loading Dump File [C:\temp\051411-48641-01.dmp]

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

     

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

    Executable search path is: 

    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631

    Machine Name:

    Kernel base = 0xfffff800`03265000 PsLoadedModuleList = 0xfffff800`034aa650

    Debug session time: Fri May 13 20:30:34.256 2011 (UTC + 1:00)

    System Uptime: 0 days 19:48:36.911

    Loading Kernel Symbols

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

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

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

    Loading User Symbols

    Loading unloaded module list

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

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 9F, {3, fffffa8003d1be30, fffff80000b9c4d8, fffffa8004d07680}

    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

    Followup: MachineOwner

    ---------

    0: kd> !analyze -v

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

    DRIVER_POWER_STATE_FAILURE (9f)

    A driver is causing an inconsistent power state.

    Arguments:

    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time

    Arg2: fffffa8003d1be30, Physical Device Object of the stack

    Arg3: fffff80000b9c4d8, Functional Device Object of the stack

    Arg4: fffffa8004d07680, The blocked IRP

    Debugging Details:

    ------------------

    DRVPOWERSTATE_SUBCODE:  3

    IRP_ADDRESS:  fffffa8004d07680

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x9F

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

     

    STACK_TEXT:  

    fffff800`00b9c488 fffff800`033519c2 : 00000000`0000009f 00000000`00000003 fffffa80`03d1be30 fffff800`00b9c4d8 : nt!KeBugCheckEx

    fffff800`00b9c490 fffff800`032f0652 : fffff800`00b9c5c0 fffff800`00b9c5c0 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90

    fffff800`00b9c530 fffff800`032f04f6 : fffffa80`074aa168 fffffa80`074aa168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66

    fffff800`00b9c5a0 fffff800`032f03de : 000000a6`0c310f3d fffff800`00b9cc18 00000000`0045c1af fffff800`0345b868 : nt!KiProcessExpiredTimerList+0xc6

    fffff800`00b9cbf0 fffff800`032f01c7 : 00000029`6cfdbcc2 00000029`0045c1af 00000029`6cfdbcb4 00000000`000000af : nt!KiTimerExpiration+0x1be

    fffff800`00b9cc90 fffff800`032dca2a : fffff800`03457e80 fffff800`03465cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277

    fffff800`00b9cd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

    STACK_COMMAND:  kb

    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

    FOLLOWUP_NAME:  MachineOwner

     

    MODULE_NAME: Unknown_Module

     

    IMAGE_NAME:  Unknown_Image

     

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

     

    FAILURE_BUCKET_ID:  X64_0x9F_3_ANALYSIS_INCONCLUSIVE

     

    BUCKET_ID:  X64_0x9F_3_ANALYSIS_INCONCLUSIVE

     

    Followup: MachineOwner

    --------

     

     

    Saturday, May 14, 2011 3:09 PM

Answers

  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8003d1be30, Physical Device Object of the stack
    Arg3: fffff80000b9c4d8, Functional Device Object of the stack
    Arg4: fffffa8004d07680, The blocked IRP
    Debugging Details:
    ------------------
    DRVPOWERSTATE_SUBCODE:  3
    IRP_ADDRESS:  fffffa8004d07680
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    STACK_TEXT:  
    fffff800`00b9c488 fffff800`033519c2 : 00000000`0000009f 00000000`00000003 fffffa80`03d1be30 fffff800`00b9c4d8 : nt!KeBugCheckEx
    fffff800`00b9c490 fffff800`032f0652 : fffff800`00b9c5c0 fffff800`00b9c5c0 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
    fffff800`00b9c530 fffff800`032f04f6 : fffffa80`074aa168 fffffa80`074aa168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`00b9c5a0 fffff800`032f03de : 000000a6`0c310f3d fffff800`00b9cc18 00000000`0045c1af fffff800`0345b868 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cbf0 fffff800`032f01c7 : 00000029`6cfdbcc2 00000029`0045c1af 00000029`6cfdbcb4 00000000`000000af : nt!KiTimerExpiration+0x1be
    fffff800`00b9cc90 fffff800`032dca2a : fffff800`03457e80 fffff800`03465cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`00b9cd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    STACK_COMMAND:  kb
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: Unknown_Module
    IMAGE_NAME:  Unknown_Image
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    FAILURE_BUCKET_ID:  X64_0x9F_3_ANALYSIS_INCONCLUSIVE
    BUCKET_ID:  X64_0x9F_3_ANALYSIS_INCONCLUSIVE
    Followup: MachineOwner
    ---------
    ---------------------------------------------------------------------------------------------------------------------
    You have to upload download a full dump MEMORY.DMP so tha I try to determine the faulty driver.
    You can also contact Microsoft CSS.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration


    • Edited by Mr XMVP Saturday, May 14, 2011 3:47 PM correct a fault
    • Marked as answer by Leo Huang Friday, June 3, 2011 7:16 AM
    Saturday, May 14, 2011 3:24 PM
  • You have the Connectify program (driver = connctfy.sys), installed in 64-bit Windows 7.

    Consider that the Connectify program may be the issue even if this is not readily apparent by analyzing the dump file as in the following link:

    http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/blue-screen-when-computer-tries-to-sleep/d7815afd-7072-46ff-bdf6-73c63d10cfd1

    Consider uninstalling Connectify and see if the BSODs resolve.

     

     

    • Marked as answer by Leo Huang Friday, June 3, 2011 7:16 AM
    Sunday, May 15, 2011 4:18 AM

All replies

  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8003d1be30, Physical Device Object of the stack
    Arg3: fffff80000b9c4d8, Functional Device Object of the stack
    Arg4: fffffa8004d07680, The blocked IRP
    Debugging Details:
    ------------------
    DRVPOWERSTATE_SUBCODE:  3
    IRP_ADDRESS:  fffffa8004d07680
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    STACK_TEXT:  
    fffff800`00b9c488 fffff800`033519c2 : 00000000`0000009f 00000000`00000003 fffffa80`03d1be30 fffff800`00b9c4d8 : nt!KeBugCheckEx
    fffff800`00b9c490 fffff800`032f0652 : fffff800`00b9c5c0 fffff800`00b9c5c0 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
    fffff800`00b9c530 fffff800`032f04f6 : fffffa80`074aa168 fffffa80`074aa168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`00b9c5a0 fffff800`032f03de : 000000a6`0c310f3d fffff800`00b9cc18 00000000`0045c1af fffff800`0345b868 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cbf0 fffff800`032f01c7 : 00000029`6cfdbcc2 00000029`0045c1af 00000029`6cfdbcb4 00000000`000000af : nt!KiTimerExpiration+0x1be
    fffff800`00b9cc90 fffff800`032dca2a : fffff800`03457e80 fffff800`03465cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`00b9cd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    STACK_COMMAND:  kb
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: Unknown_Module
    IMAGE_NAME:  Unknown_Image
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    FAILURE_BUCKET_ID:  X64_0x9F_3_ANALYSIS_INCONCLUSIVE
    BUCKET_ID:  X64_0x9F_3_ANALYSIS_INCONCLUSIVE
    Followup: MachineOwner
    ---------
    ---------------------------------------------------------------------------------------------------------------------
    You have to upload download a full dump MEMORY.DMP so tha I try to determine the faulty driver.
    You can also contact Microsoft CSS.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration


    • Edited by Mr XMVP Saturday, May 14, 2011 3:47 PM correct a fault
    • Marked as answer by Leo Huang Friday, June 3, 2011 7:16 AM
    Saturday, May 14, 2011 3:24 PM
  • ---- 
    You have to download a full dump MEMORY.DMP so tha I try to determine the faulty driver
    -----

    Could you help me how can i do it?

     

    Thanks 

    Saturday, May 14, 2011 3:44 PM
  • I made a fault, I mean upload.

    You have to configure your Windows to generate a full dump and then upload MEMORY.DMP at the next crash.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    Saturday, May 14, 2011 3:48 PM
  • Hy!

     

    Thank for the answere, i changed the dump type by registry( i have more than 2 gb) I "waiting" to have the problem again, and i try to upload the full dump.


    Saturday, May 14, 2011 4:01 PM
  • You have the Connectify program (driver = connctfy.sys), installed in 64-bit Windows 7.

    Consider that the Connectify program may be the issue even if this is not readily apparent by analyzing the dump file as in the following link:

    http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/blue-screen-when-computer-tries-to-sleep/d7815afd-7072-46ff-bdf6-73c63d10cfd1

    Consider uninstalling Connectify and see if the BSODs resolve.

     

     

    • Marked as answer by Leo Huang Friday, June 3, 2011 7:16 AM
    Sunday, May 15, 2011 4:18 AM
  • Thanks the answere. I uninstalled the connectify driver, i wait is it helped or not.

     

    I also changed to full memory dump, but i can't upload the file cause it too big.

     

    The windbg output was the following

     

    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [E:\dump\MEMORY.DMP]
    Kernel Complete Dump File: Full address space is available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Machine Name:
    Kernel base = 0xfffff800`0321d000 PsLoadedModuleList = 0xfffff800`03462650
    Debug session time: Sun May 15 06:49:01.084 2011 (UTC + 1:00)
    System Uptime: 0 days 11:48:36.739
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ......................................................
    Loading User Symbols
    
    Loading unloaded module list
    ......
    *******************************************************************************
    *                    *
    *      Bugcheck Analysis         *
    *                    *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa8003d28060, fffff8000485b4d8, fffffa8003f824e0}
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                    *
    *      Bugcheck Analysis         *
    *                    *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8003d28060, Physical Device Object of the stack
    Arg3: fffff8000485b4d8, Functional Device Object of the stack
    Arg4: fffffa8003f824e0, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE: 3
    
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    
    FAULTING_MODULE: fffff80003806000 hal
    
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    
    BUGCHECK_STR: 0x9F
    
    PROCESS_NAME: System
    
    CURRENT_IRQL: 2
    
    STACK_TEXT: 
    fffff800`0485b488 fffff800`033099c2 : 00000000`0000009f 00000000`00000003 fffffa80`03d28060 fffff800`0485b4d8 : nt!KeBugCheckEx
    fffff800`0485b490 fffff800`032a8652 : fffff800`0485b5c0 fffff800`0485b5c0 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
    fffff800`0485b530 fffff800`032a84f6 : fffffa80`048a0c68 fffffa80`048a0c68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`0485b5a0 fffff800`032a83de : 00000062`fdf39cb1 fffff800`0485bc18 00000000`00299626 fffff800`03412748 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`0485bbf0 fffff800`032a81c7 : 00000018`bde6cac4 00000018`00299626 00000018`bde6ca3f 00000000`00000026 : nt!KiTimerExpiration+0x1be
    fffff800`0485bc90 fffff800`03294a2a : fffff800`0340fe80 fffff800`0341dcc0 00000000`00000002 fffff800`00000000 : nt!KiRetireDpcList+0x277
    fffff800`0485bd40 00000000`00000000 : fffff800`0485c000 fffff800`04856000 fffff800`0485bd00 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND: kb
    
    SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
    
    FOLLOWUP_NAME: MachineOwner
    
    MODULE_NAME: Unknown_Module
    
    IMAGE_NAME: Unknown_Image
    
    FAILURE_BUCKET_ID: X64_0x9F_3_ACPI_ANALYSIS_INCONCLUSIVE
    
    BUCKET_ID: X64_0x9F_3_ACPI_ANALYSIS_INCONCLUSIVE
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm hal
    start    end     module name
    fffff800`03806000 fffff800`0384f000 hal  (pdb symbols)   c:\symbols\hal.pdb\A085D08B9C5D4BFDBA48AC285BDA03F22\hal.pdb
     Loaded symbol image file: hal.dll
     Image path: hal.dll
     Image name: hal.dll
     Timestamp:  Sat Nov 20 13:00:25 2010 (4CE7C669)
     CheckSum:   000404C3
     ImageSize:  00049000
     Translations:  0000.04b0 0000.04e4 0409.04b0 0409.04e4
    

     


    Sunday, May 15, 2011 6:36 PM
  • Use 7ZIP or WinRAR to compress it and then upload it.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    Sunday, May 15, 2011 7:41 PM