BSOD on sleep. Latest dump attached.


  1. Posts : 14
    Windows 7 Professional x64
       #1

    BSOD on sleep. Latest dump attached.


    Hi,

    I have an Acer Ferrari One netbook running Win7 Home Premium as factory installed.
    Recently it's started crashing on sleep and BSODs before the computer manages to go into sleep mode.

    The error message is a DRIVER_POWER_STATE_FAILURE with error code 9F. The driver listed as causing the problem is 'ntoskrnl.exe' and I've no idea how to solve this!

    I've updated all my drivers to the latest versions using Device Manager but other than that I can't find any more solutions online.

    If anyone can help that'd be great. I've attached my latest minidump if this helps.
    Thanks in advance.
    Greg
      My Computer


  2. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #2

    Interesting, when I ran the Windows Debugger, it pointed to athrx.sys as the cause. This may or may not be the cause.

    The usual cause of a 9F stop error is a device driver. Here is your dmp file:

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_062910-18766-01.zip\062910-18766-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`02c4a000 PsLoadedModuleList = 0xfffff800`02e87e50
    Debug session time: Tue Jun 29 12:08:27.477 2010 (GMT-4)
    System Uptime: 0 days 1:01:39.927
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa8001f8ca20, fffff80000b9c518, fffffa80023c24d0}
    
    *** WARNING: Unable to verify timestamp for athrx.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrx.sys
    Probably caused by : athrx.sys
    
    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: fffffa8001f8ca20, Physical Device Object of the stack
    Arg3: fffff80000b9c518, Functional Device Object of the stack
    Arg4: fffffa80023c24d0, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IRP_ADDRESS:  fffffa80023c24d0
    
    DEVICE_OBJECT: fffffa80029ba050
    
    DRIVER_OBJECT: fffffa80029b8e70
    
    IMAGE_NAME:  athrx.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4aca1ff5
    
    MODULE_NAME: athrx
    
    FAULTING_MODULE: fffff88003e5e000 athrx
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80002d291b3 to fffff80002cba600
    
    STACK_TEXT:  
    fffff800`00b9c4c8 fffff800`02d291b3 : 00000000`0000009f 00000000`00000003 fffffa80`01f8ca20 fffff800`00b9c518 : nt!KeBugCheckEx
    fffff800`00b9c4d0 fffff800`02cc66a6 : fffff800`00b9c618 fffff800`00b9c618 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
    fffff800`00b9c570 fffff800`02cc5a26 : fffffa80`02c29c68 fffffa80`02c29c68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`00b9c5e0 fffff800`02cc657e : 00000008`9d5417e2 fffff800`00b9cc58 00000000`00039e75 fffff800`02e38128 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cc30 fffff800`02cc5d97 : 0000000c`55d371c4 0000000c`00039e75 0000000c`55d3719a 00000000`00000075 : nt!KiTimerExpiration+0x1be
    fffff800`00b9ccd0 fffff800`02cc2dfa : fffff800`02e34e80 fffff800`02e42c40 00000000`00000000 fffff880`01447c50 : nt!KiRetireDpcList+0x277
    fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_athrx.sys
    
    BUCKET_ID:  X64_0x9F_IMAGE_athrx.sys
    
    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: fffffa8001f8ca20, Physical Device Object of the stack
    Arg3: fffff80000b9c518, Functional Device Object of the stack
    Arg4: fffffa80023c24d0, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IRP_ADDRESS:  fffffa80023c24d0
    
    DEVICE_OBJECT: fffffa80029ba050
    
    DRIVER_OBJECT: fffffa80029b8e70
    
    IMAGE_NAME:  athrx.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4aca1ff5
    
    MODULE_NAME: athrx
    
    FAULTING_MODULE: fffff88003e5e000 athrx
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80002d291b3 to fffff80002cba600
    
    STACK_TEXT:  
    fffff800`00b9c4c8 fffff800`02d291b3 : 00000000`0000009f 00000000`00000003 fffffa80`01f8ca20 fffff800`00b9c518 : nt!KeBugCheckEx
    fffff800`00b9c4d0 fffff800`02cc66a6 : fffff800`00b9c618 fffff800`00b9c618 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
    fffff800`00b9c570 fffff800`02cc5a26 : fffffa80`02c29c68 fffffa80`02c29c68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`00b9c5e0 fffff800`02cc657e : 00000008`9d5417e2 fffff800`00b9cc58 00000000`00039e75 fffff800`02e38128 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cc30 fffff800`02cc5d97 : 0000000c`55d371c4 0000000c`00039e75 0000000c`55d3719a 00000000`00000075 : nt!KiTimerExpiration+0x1be
    fffff800`00b9ccd0 fffff800`02cc2dfa : fffff800`02e34e80 fffff800`02e42c40 00000000`00000000 fffff880`01447c50 : nt!KiRetireDpcList+0x277
    fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_athrx.sys
    
    BUCKET_ID:  X64_0x9F_IMAGE_athrx.sys
    
    Followup: MachineOwner
    ---------
    I found the following older drivers on your system. These need to be updated as Win 7 does not like older drivers.
    amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB)
    AtiPcie.sys Tue May 05 11:00:22 2009 (4A005486)
    DKbFltr.sys Wed Mar 25 23:15:42 2009 (49CAF35E)
    SynTP.sys Thu Jun 18 22:33:58 2009 (4A3AF916)
    Let's begin by updating these drivers. I recommend thast you start by going to the Acer site and see if there are updates for these drivers on the Acer site. Do you need help with this?
    Last edited by CarlTR6; 29 Jun 2010 at 12:14.
      My Computer


  3. Posts : 14
    Windows 7 Professional x64
    Thread Starter
       #3

    Thanks for your help.
    I've had a play round with the drivers for the wireless card and have sorted the problem.
    It turns out a program called Connectify had been causing the issue. It had, unknown to me, updated itself just before the problems had started and had obviously been stopping the wireless card from going into sleep.
    I have no idea why I wasn't pointed athrx.sys initially, would have saved so much stressing!
    Thanks again!
      My Computer


  4. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #4

    I also notice that you are running AVG antivirus. AVG isknow to cause crashes on some Win7 sytems. For the purposes of troubleshooting, uninstall AVG using this tool - Info > Tool (32bit) - Tool (64 bit) Replace it with MSE.
      My Computer


  5. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #5

    Great, I'm glad to know the problem is sorted. What program are you using to open the dmp files? We use Windows Debugger
      My Computer


  6. Posts : 14
    Windows 7 Professional x64
    Thread Starter
       #6

    Cheers.
    I was using BlueScreenViewer but I'll go with the windows one in future!
      My Computer


  7. Posts : 14
    Windows 7 Professional x64
    Thread Starter
       #7

    Oh and I'm using Avira not AVG. Would you still recommend MSE?
      My Computer


  8. Posts : 13,354
    Windows 7 Professional x64
       #8

    Yes, Avira causes BSODs too. It's a common mistake to confuse Avira with AVG.

    Use this removal tool for Avira: http://www.avira.com/en/documents/ut...ninstXPeng.zip
      My Computer


  9. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #9

    Thank you Jonathan. I was in too much of a hurry!
      My Computer


  10. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #10

    gcaster said:
    Cheers.
    I was using BlueScreenViewer but I'll go with the windows one in future!
    BlueScreenViewer is good and it is being developed; but we find WinDbg is more accurate.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:22.
Find Us