BSOD after Computer is put to Hibernation


  1. Posts : 3
    Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
       #1

    BSOD after Computer is put to Hibernation


    Hi. I have an HP Pavilion dv7 running Windows Home Premium x64 and I frequently experience BSOD when I try to enter the computer into Hibernation mode. First, it will take some time to Hibernate, having a black screen with the power light on. When it finally hibernates and I try to turn it back on I get the Blue Screen and Windows have to RESTART rather than RESUME. I have attached the zip file with the information needed as well as system spec.
    Thank you very much for your much needed help!
      My Computer


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

    Welcome

    Your Intel(R) Wireless WiFi Link 5000 Series Adapter Driver for Windows 7 needs to be updated.

    Check for an update from this Link: Download Center

    Code:
    Start Menu\Programs\Norton Internet Security    Public:Start Menu\Programs\Norton Internet Security    Public
    Also recommend to replace Norton Internet Security to Microsoft Security Essentials free which is a great combination with the free version of Malware Bytes :)

    Free up your start-up:
    Click on the start || Type msconfig || Go to the Start-up tab ||
    Deselect all except for antivirus/video/audio programs.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa8007301a10, fffff800049593d8, fffffa80116cd010}
    
    *** WARNING: Unable to verify timestamp for pci.sys
    *** ERROR: Module load completed but symbols could not be loaded for pci.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 : pci.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: fffffa8007301a10, Physical Device Object of the stack
    Arg3: fffff800049593d8, Functional Device Object of the stack
    Arg4: fffffa80116cd010, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IMAGE_NAME:  pci.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f
    
    MODULE_NAME: pci
    
    FAULTING_MODULE: fffff88000d5d000 pci
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    STACK_TEXT:  
    fffff800`04959388 fffff800`0314b6c2 : 00000000`0000009f 00000000`00000003 fffffa80`07301a10 fffff800`049593d8 : nt!KeBugCheckEx
    fffff800`04959390 fffff800`030ebe3c : fffff800`049594c0 fffff800`049594c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34050
    fffff800`04959430 fffff800`030ebcd6 : fffff800`03288f20 00000000`008e42d3 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`049594a0 fffff800`030ebbbe : 00000152`a2e11639 fffff800`04959b18 00000000`008e42d3 fffff800`03257ce8 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`04959af0 fffff800`030eb9a7 : 00000048`96dadec1 00000048`008e42d3 00000048`96dade52 00000000`000000d3 : nt!KiTimerExpiration+0x1be
    fffff800`04959b90 fffff800`030d8eca : fffff800`03253e80 fffff800`03261cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`04959c40 00000000`00000000 : fffff800`0495a000 fffff800`04954000 fffff800`04959c00 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_NETwNs64_IMAGE_pci.sys
    
    BUCKET_ID:  X64_0x9F_3_NETwNs64_IMAGE_pci.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: fffffa8007301a10, Physical Device Object of the stack
    Arg3: fffff800049593d8, Functional Device Object of the stack
    Arg4: fffffa80116cd010, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IMAGE_NAME:  pci.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f
    
    MODULE_NAME: pci
    
    FAULTING_MODULE: fffff88000d5d000 pci
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    STACK_TEXT:  
    fffff800`04959388 fffff800`0314b6c2 : 00000000`0000009f 00000000`00000003 fffffa80`07301a10 fffff800`049593d8 : nt!KeBugCheckEx
    fffff800`04959390 fffff800`030ebe3c : fffff800`049594c0 fffff800`049594c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34050
    fffff800`04959430 fffff800`030ebcd6 : fffff800`03288f20 00000000`008e42d3 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`049594a0 fffff800`030ebbbe : 00000152`a2e11639 fffff800`04959b18 00000000`008e42d3 fffff800`03257ce8 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`04959af0 fffff800`030eb9a7 : 00000048`96dadec1 00000048`008e42d3 00000048`96dade52 00000000`000000d3 : nt!KiTimerExpiration+0x1be
    fffff800`04959b90 fffff800`030d8eca : fffff800`03253e80 fffff800`03261cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`04959c40 00000000`00000000 : fffff800`0495a000 fffff800`04954000 fffff800`04959c00 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_NETwNs64_IMAGE_pci.sys
    
    BUCKET_ID:  X64_0x9F_3_NETwNs64_IMAGE_pci.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: fffffa8007301a10, Physical Device Object of the stack
    Arg3: fffff800049593d8, Functional Device Object of the stack
    Arg4: fffffa80116cd010, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IMAGE_NAME:  pci.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f
    
    MODULE_NAME: pci
    
    FAULTING_MODULE: fffff88000d5d000 pci
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    STACK_TEXT:  
    fffff800`04959388 fffff800`0314b6c2 : 00000000`0000009f 00000000`00000003 fffffa80`07301a10 fffff800`049593d8 : nt!KeBugCheckEx
    fffff800`04959390 fffff800`030ebe3c : fffff800`049594c0 fffff800`049594c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34050
    fffff800`04959430 fffff800`030ebcd6 : fffff800`03288f20 00000000`008e42d3 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`049594a0 fffff800`030ebbbe : 00000152`a2e11639 fffff800`04959b18 00000000`008e42d3 fffff800`03257ce8 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`04959af0 fffff800`030eb9a7 : 00000048`96dadec1 00000048`008e42d3 00000048`96dade52 00000000`000000d3 : nt!KiTimerExpiration+0x1be
    fffff800`04959b90 fffff800`030d8eca : fffff800`03253e80 fffff800`03261cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`04959c40 00000000`00000000 : fffff800`0495a000 fffff800`04954000 fffff800`04959c00 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_NETwNs64_IMAGE_pci.sys
    
    BUCKET_ID:  X64_0x9F_3_NETwNs64_IMAGE_pci.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !irp fffffa80116cd010
    Irp is active with 5 stacks 3 is current (= 0xfffffa80116cd170)
     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
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0  0 fffffa800bb5a050 00000000 00000000-00000000    
              Unable to load image \SystemRoot\system32\DRIVERS\NETwNs64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for NETwNs64.sys
    *** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ndis.sys - 
     \Driver\NETwNs64
                Args: 00015500 00000000 00000005 00000003
     [ 16, 2]   0 e1 fffffa800b14ae20 00000000 fffff80003325200-fffffa800cbc6210 Success Error Cancel pending
              Unable to load image \SystemRoot\system32\DRIVERS\vwifibus.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for vwifibus.sys
    *** ERROR: Module load completed but symbols could not be loaded for vwifibus.sys
    Unable to load image \SystemRoot\system32\drivers\Wdf01000.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Wdf01000.sys
    *** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
     \Driver\vwifibus    nt!PopSystemIrpCompletion
                Args: 00015500 00000000 00000005 00000003
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa800cbc6210    
    
                Args: 00000000 00000000 00000000 00000000
    Let us know if the BSoD problem persists.
      My Computer


  3. Posts : 3
    Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #3

    Thank you all very much for your time and valuable advice. I will follow through and let you know if the problem persists.
      My Computer


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

    Sure. Take your time.
      My Computer


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

    Hi, just a follow up.

    Did the BSODs reoccur after the driver update?
      My Computer


  6. Posts : 3
    Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #6

    Hello. Very sorry for the delay. So I updated the driver and I had the same difficulty the first 2 instances. Then I followed your advice cleaning up the running programs through msconfig and ever since I have not had a BSOD problem.

    I would like to thank you again for your help! I will let you know if any related issues come up again (hopefully not!).
      My Computer


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

    No problem, keep the thread open for another week just in case :)
      My Computer


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

    Just wanted to know if you had more BSoDs?
    Let me know!
      My Computer


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

    Did you get more BSODs?
      My Computer


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

       Tip

    • If your problem is solved please use the Mark this thread as solved link at the top of your thread or down on the left corner

      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 12:48.
Find Us