BSOD 0x9f sleep/hybernate on acer 5470g


  1. Posts : 3
    x64
       #1

    BSOD 0x9f sleep/hybernate on acer 5470g


    Hi guys, i need your help...

    I've been struggling with this problem for a while on my laptop (5742g i3, 6gb ram, Broadcom Wlan & LAN, Realtek audio, Radeon hd5470) BSOD appears frequently when i put computer on sleep/hibernate. Problem persists after OS (win7 x64) reinstall with only 2 external (OEM)drivers installed (WLAN and GPU).

    Whocrashed reports:

    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

    I've uploaded two (zipped) .dmp files if anyone can help with their interpretation

    http://tinyurl.com/bfg5d5z
    http://tinyurl.com/aycaj6p

    Thanks !
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Welcome to SevenForums.

    Please remove Avira antivirus: Avira AntiVir Removal Tool - Download

    Replace with Microsoft security essentials

    Microsoft Security Essentials.

    Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-
       Warning
    Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

    Run a full scan with both (separately) once downloaded, installed and updated.


    Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

    Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.


    Perform a System File Check:
    1. Click on the start
    2. Type CMD on Search
    3. Left click and Run as Administrator
    4. Type SFC /scannow

    Full tutorial here:



    Disk Check on your hard drive for file system errors and bad sectors on it:



    Await the .nfo file.

    SUMMARY
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa8005a67e30, fffff80000b9c518, fffffa80086f8e10}
    
    Unable to load image \SystemRoot\system32\DRIVERS\avfwim.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for avfwim.sys
    *** ERROR: Module load completed but symbols could not be loaded for avfwim.sys
    Probably caused by : ntkrnlmp
    
    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: fffffa8005a67e30, Physical Device Object of the stack
    Arg3: fffff80000b9c518, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa80086f8e10, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IMAGE_NAME:  ntkrnlmp
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAULTING_MODULE: fffff88005bc9000 avfwim
    
    DEVICE_OBJECT: fffffa8006b10050
    
    DRIVER_OBJECT: fffffa80070a0460
    
    IRP_ADDRESS:  fffffa80086f8e10
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0
    
    STACK_TEXT:  
    fffff800`00b9c4c8 fffff800`0293f6d2 : 00000000`0000009f 00000000`00000003 fffffa80`05a67e30 fffff800`00b9c518 : nt!KeBugCheckEx
    fffff800`00b9c4d0 fffff800`028dfc3c : fffff800`00b9c600 fffff800`00b9c600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33ac0
    fffff800`00b9c570 fffff800`028dfad6 : fffff800`02a7cf20 00000000`0011ca59 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00b9c5e0 fffff800`028df9be : 0000002a`591bcb16 fffff800`00b9cc58 00000000`0011ca59 fffff800`02a4ada8 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cc30 fffff800`028df7a7 : 00000008`ccfac0c1 00000008`0011ca59 00000008`ccfac0bb 00000000`00000059 : nt!KiTimerExpiration+0x1be
    fffff800`00b9ccd0 fffff800`028cccca : fffff800`02a47e80 fffff800`02a55cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: ntkrnlmp
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp
    
    BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp
    
    Followup: MachineOwner
    ---------
    
    0: kd> !irp fffffa80086f8e10
    Irp is active with 3 stacks 2 is current (= 0xfffffa80086f8f28)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0 e1 fffffa8006b10050 00000000 fffff80002b19200-fffffa80087725f0 Success Error Cancel pending
    	       \Driver\avfwim	nt!PopSystemIrpCompletion
    			Args: 00014400 00000000 00000004 00000002
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa80087725f0    
    
    			Args: 00000000 00000000 00000000 00000000
      My Computer


  3. Posts : 3
    x64
    Thread Starter
       #3

    Tnx. I am following your instructions. If problem does not occur again, I'll report and hopefully close the tread.
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #4

    OK, keep us posted and give it a week before marking as solved. :)
      My Computer


  5. Posts : 3
    x64
    Thread Starter
       #5

    Avira was causing trouble. Everything works like a charm now with MSE, i've restored faith in computing :) Thanks !
      My Computer


  6. Posts : 15,026
    Windows 10 Home 64Bit
       #6

    Good to hear that.
    Thanks for letting us know.
      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 22:19.
Find Us