BSOD on hibernate


  1. Posts : 4
    Windows 7 Professional x64
       #1

    BSOD on hibernate


    Hi

    Have recently found that my system no longer hibernates without a BSOD. Have tried updating drivers but can't see what the issue is. Hope someone can help.

    I have attached the minidumps as per the forum requested format

    regards Hugh
      My Computer


  2. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #2

    Hello and Welcome !

    Seems like the crash has caused by connctfy.sys i.e Connectify - Turn your Windows 7 laptop into a Wi-Fi Hotspot i would recommend to uninstall it completely.

    Update the Following Drivers:

    Code:
    VSTAZL6.SYS  Thu Oct 16 06:23:42 2008 - SoftK56 Modem Driver
    VSTCNXT6.SYS Thu Oct 16 06:22:22 2008 - SoftK56 Modem Driver
    VSTDPV6.SYS  Thu Oct 16 06:27:45 2008 - SoftK56 Modem Driver
    LHidFilt.Sys Fri Dec 19 13:08:04 2008 - Logitech SetPoint(TM)
    btwaudio.sys Wed Nov 12 00:12:22 2008 - Bluetooth Software
    btwavdt.sys  Wed Nov 12 00:11:18 2008 - Bluetooth Software
    btwl2cap.sys Thu Jul 24 08:47:48 2008 - Bluetooth Software
    btwrchid.sys Wed Nov 12 00:12:34 2008 - Bluetooth Software


    Bugcheck:

    Code:
    Unable to load image \SystemRoot\system32\DRIVERS\connctfy.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for connctfy.sys
    *** ERROR: Module load completed but symbols could not be loaded for connctfy.sys
    Probably caused by : ntkrnlmp
    
    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: fffffa800373e980, Physical Device Object of the stack
    Arg3: fffff80000ba2748, Functional Device Object of the stack
    Arg4: fffffa8003f1aa80, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IMAGE_NAME:  ntkrnlmp
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MODULE_NAME: ntkrnlmp
    
    FAULTING_MODULE: fffff88010085000 connctfy
    
    IRP_ADDRESS:  fffffa8003f1aa80
    
    DEVICE_OBJECT: fffffa8005d89050
    
    DRIVER_OBJECT: fffffa80057e4060
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  Connectifyd.ex
    
    CURRENT_IRQL:  2
    
    STACK_TEXT:  
    fffff800`00ba26f8 fffff800`02ef1273 : 00000000`0000009f 00000000`00000003 fffffa80`0373e980 fffff800`00ba2748 : nt!KeBugCheckEx
    fffff800`00ba2700 fffff800`02e8e29e : fffff800`00ba2830 fffff800`00ba2830 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
    fffff800`00ba27a0 fffff800`02e8ddd6 : fffffa80`0825cc68 fffffa80`0825cc68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`00ba2810 fffff800`02e8e4be : 00000010`21129107 fffff800`00ba2e88 00000000`0006c69f fffff800`03000668 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00ba2e60 fffff800`02e8dcb7 : fffff800`02ffcec2 fffffa80`0006c69f fffffa80`05a0da28 00000000`0000009f : nt!KiTimerExpiration+0x1be
    fffff800`00ba2f00 fffff800`02e88865 : 00000000`00000000 fffffa80`0812eb60 00000000`00000000 fffff880`010c7908 : nt!KiRetireDpcList+0x277
    fffff800`00ba2fb0 fffff800`02e8867c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
    fffff880`07f157f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_ntkrnlmp
    
    BUCKET_ID:  X64_0x9F_3_IMAGE_ntkrnlmp
    
    Followup: MachineOwner
    Hope this helps,
    Captain
      My Computer


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

    BSOD on hibernate


    Excellent - thanks. Will give it a go
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    hughleslie said:
    Hi

    Have recently found that my system no longer hibernates without a BSOD. Have tried updating drivers but can't see what the issue is. Hope someone can help.

    I have attached the minidumps as per the forum requested format

    regards Hugh
    1-These were caused by VBoxNetFlt.sys part of VBOX2.1. It should be removed to test

    Ken J


    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\New folder\101910-54943-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\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
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`0304be50
    Debug session time: Mon Oct 18 22:10:59.719 2010 (GMT-4)
    System Uptime: 0 days 1:32:12.639
    Loading Kernel Symbols
    .
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    ..............................................................
    ................................................................
    ....................................................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000009F, {4, 258, fffffa80036df680, fffff80000b9c510}
    
    Unable to load image \SystemRoot\system32\DRIVERS\VBoxNetFlt.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for VBoxNetFlt.sys
    *** ERROR: Module load completed but symbols could not be loaded for VBoxNetFlt.sys
    Probably caused by : VBoxNetFlt.sys ( VBoxNetFlt+938f )
    
    Followup: MachineOwner
    ---------
    
    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: fffffa80036df680, The thread currently holding on to the Pnp lock.
    Arg4: fffff80000b9c510
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  4
    
    FAULTING_THREAD:  fffffa80036df680
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80002e85992 to fffff80002e845da
    
    STACK_TEXT:  
    fffff880`031df1f0 fffff800`02e85992 : fffffa80`036df680 fffffa80`036df680 00000000`00000000 00000000`0000000c : nt!KiSwapContext+0x7a
    fffff880`031df330 fffff800`02e87cff : 00000000`00000246 fffff800`02e8624a fffff800`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
    fffff880`031df3c0 fffff800`02edc906 : fffff880`018dc100 fffff880`00000000 00000000`00000000 fffff880`031df600 : nt!KeWaitForSingleObject+0x19f
    fffff880`031df460 fffff880`019362b3 : fffffa80`0813d010 fffff880`031df6e8 fffff880`01967fe0 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x13066
    fffff880`031df4d0 fffff880`016c491e : fffffa80`0813d840 fffffa80`05bc31a0 fffffa80`041e9860 fffffa80`0813d840 : tcpip!FlUnbindAdapter+0x83
    fffff880`031df530 fffff880`016c560f : fffffa80`05bc31a0 00000000`00000000 fffffa80`05add6c0 00000000`00000000 : ndis!ndisUnbindProtocol+0x1fe
    fffff880`031df640 fffff880`016c6c6b : 00000000`00000001 fffffa80`05bc31a0 fffff880`031df6d0 fffffa80`05add6c0 : ndis!ndisCloseMiniportBindings+0x2df
    fffff880`031df750 fffff880`016923df : fffffa80`05bc31a0 fffffa80`05bc31a0 00000000`00000001 00000000`00000000 : ndis!ndisPnPRemoveDevice+0x25b
    fffff880`031df8f0 fffff880`0400938f : fffffa80`08126bd0 fffffa80`05bae100 fffff880`031dfb28 00000000`00000000 : ndis!NdisIMDeInitializeDeviceInstance+0x8f
    fffff880`031df930 fffffa80`08126bd0 : fffffa80`05bae100 fffff880`031dfb28 00000000`00000000 fffffa80`08126bd0 : VBoxNetFlt+0x938f
    fffff880`031df938 fffffa80`05bae100 : fffff880`031dfb28 00000000`00000000 fffffa80`08126bd0 fffff880`04007f6c : 0xfffffa80`08126bd0
    fffff880`031df940 fffff880`031dfb28 : 00000000`00000000 fffffa80`08126bd0 fffff880`04007f6c 00000000`00000000 : 0xfffffa80`05bae100
    fffff880`031df948 00000000`00000000 : fffffa80`08126bd0 fffff880`04007f6c 00000000`00000000 00000000`00000001 : 0xfffff880`031dfb28
    
    
    STACK_COMMAND:  .thread 0xfffffa80036df680 ; kb
    
    FOLLOWUP_IP: 
    VBoxNetFlt+938f
    fffff880`0400938f ??              ???
    
    SYMBOL_STACK_INDEX:  9
    
    SYMBOL_NAME:  VBoxNetFlt+938f
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: VBoxNetFlt
    
    IMAGE_NAME:  VBoxNetFlt.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c24afec
    
    FAILURE_BUCKET_ID:  X64_0x9F_VBoxNetFlt+938f
    
    BUCKET_ID:  X64_0x9F_VBoxNetFlt+938f
    
    Followup: MachineOwner
    ---------
    
    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: fffffa80036df680, The thread currently holding on to the Pnp lock.
    Arg4: fffff80000b9c510
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  4
    
    FAULTING_THREAD:  fffffa80036df680
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80002e85992 to fffff80002e845da
    
    STACK_TEXT:  
    fffff880`031df1f0 fffff800`02e85992 : fffffa80`036df680 fffffa80`036df680 00000000`00000000 00000000`0000000c : nt!KiSwapContext+0x7a
    fffff880`031df330 fffff800`02e87cff : 00000000`00000246 fffff800`02e8624a fffff800`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
    fffff880`031df3c0 fffff800`02edc906 : fffff880`018dc100 fffff880`00000000 00000000`00000000 fffff880`031df600 : nt!KeWaitForSingleObject+0x19f
    fffff880`031df460 fffff880`019362b3 : fffffa80`0813d010 fffff880`031df6e8 fffff880`01967fe0 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x13066
    fffff880`031df4d0 fffff880`016c491e : fffffa80`0813d840 fffffa80`05bc31a0 fffffa80`041e9860 fffffa80`0813d840 : tcpip!FlUnbindAdapter+0x83
    fffff880`031df530 fffff880`016c560f : fffffa80`05bc31a0 00000000`00000000 fffffa80`05add6c0 00000000`00000000 : ndis!ndisUnbindProtocol+0x1fe
    fffff880`031df640 fffff880`016c6c6b : 00000000`00000001 fffffa80`05bc31a0 fffff880`031df6d0 fffffa80`05add6c0 : ndis!ndisCloseMiniportBindings+0x2df
    fffff880`031df750 fffff880`016923df : fffffa80`05bc31a0 fffffa80`05bc31a0 00000000`00000001 00000000`00000000 : ndis!ndisPnPRemoveDevice+0x25b
    fffff880`031df8f0 fffff880`0400938f : fffffa80`08126bd0 fffffa80`05bae100 fffff880`031dfb28 00000000`00000000 : ndis!NdisIMDeInitializeDeviceInstance+0x8f
    fffff880`031df930 fffffa80`08126bd0 : fffffa80`05bae100 fffff880`031dfb28 00000000`00000000 fffffa80`08126bd0 : VBoxNetFlt+0x938f
    fffff880`031df938 fffffa80`05bae100 : fffff880`031dfb28 00000000`00000000 fffffa80`08126bd0 fffff880`04007f6c : 0xfffffa80`08126bd0
    fffff880`031df940 fffff880`031dfb28 : 00000000`00000000 fffffa80`08126bd0 fffff880`04007f6c 00000000`00000000 : 0xfffffa80`05bae100
    fffff880`031df948 00000000`00000000 : fffffa80`08126bd0 fffff880`04007f6c 00000000`00000000 00000000`00000001 : 0xfffff880`031dfb28
    
    
    STACK_COMMAND:  .thread 0xfffffa80036df680 ; kb
    
    FOLLOWUP_IP: 
    VBoxNetFlt+938f
    fffff880`0400938f ??              ???
    
    SYMBOL_STACK_INDEX:  9
    
    SYMBOL_NAME:  VBoxNetFlt+938f
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: VBoxNetFlt
    
    IMAGE_NAME:  VBoxNetFlt.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c24afec
    
    FAILURE_BUCKET_ID:  X64_0x9F_VBoxNetFlt+938f
    
    BUCKET_ID:  X64_0x9F_VBoxNetFlt+938f
    
    Followup: MachineOwner
    ---------

    2-Remove STPD.sys (used in daemon tools/alcohol120)



    Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
    [/quote]
    You can use MagicDisc as an alternative.

    Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview
      My Computer


  5. Posts : 4
    Windows 7 Professional x64
    Thread Starter
       #5

    BSOD on hibernate - FIXED


    Hi All

    Thanks so much for the help.

    The culprit was Connectify - must have occurred after an update. System is functioning perfectly again and hibernating correctly.

    Thanks again for the very rapid and knowledgable help

    regards Hugh
      My Computer


  6. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #6

    hughleslie said:
    Hi All

    Thanks so much for the help.

    The culprit was Connectify - must have occurred after an update. System is functioning perfectly again and hibernating correctly.

    Thanks again for the very rapid and knowledgable help

    regards Hugh
    Your very Welcome ! Thanks for reporting back :)

    - Captain
      My Computer


  7. Posts : 28,845
    Win 8 Release candidate 8400
       #7

    hughleslie said:
    Hi All

    Thanks so much for the help.

    The culprit was Connectify - must have occurred after an update. System is functioning perfectly again and hibernating correctly.

    Thanks again for the very rapid and knowledgable help

    regards Hugh

    Hope you removed SPTD.sys
      My Computer


  8. Posts : 4
    Windows 7 Professional x64
    Thread Starter
       #8

    Yes - I had already run the SPTD.sys uninstaller. Thanks anyway.
      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 18:25.
Find Us