locked
Can you guys help with this BSOD? RRS feed

  • Question

  • This BSOD only occurs when I put the computer to sleep and then try to shut down. It takes about 10 minutes to show up. 

    Windows 7 Home Premium 64- Bit 

    Gateway 6gb 1 Tb Intel i3 

    Here are some of the dump files 

    http://sdrv.ms/MXHG5a

    http://sdrv.ms/MXHL91

    http://sdrv.ms/MXHLGj

    http://sdrv.ms/MXHPWx

    Tuesday, July 31, 2012 7:34 PM

Answers

  • Hi,


    After checking the dump, I notice the error, BugCheck 9F, {3, 862a56a8, 82d3cae0, 85fb7d20}.


    Please see Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE for details.


    The issue seems to be related to 0x9F_3_VBoxUSB_IMAGE_usbhub.sys, you can try to update the driver for you USB Hub or remove the device and see how it works.


    Hope this helps.


    Jeremy Wu

    TechNet Community Support

    • Proposed as answer by Jeremy_Wu Monday, September 3, 2012 5:55 AM
    • Marked as answer by Jeremy_Wu Tuesday, September 4, 2012 5:17 AM
    Thursday, August 2, 2012 2:57 AM
  • Hi,


    After checking the dump, I notice the error, BugCheck 9F, {3, 862a56a8, 82d3cae0, 85fb7d20}.


    Please see Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE for details.


    The issue seems to be related to 0x9F_3_VBoxUSB_IMAGE_usbhub.sys, you can try to update the driver for you USB Hub or remove the device and see how it works.


    Hope this helps.


    Jeremy Wu

    TechNet Community Support

    Actually, Jeremy discovered something I think crucial to this problem. That driver doesn't seem to be for a USB hub, rather, it seems to be a VirtualBox driver. Have you installed VirtualBox on your machine? If so, try uninstalling it and then installing the latest version. 

    Otherwise, yes, you may have a malware or hardware problem.

    -Julian

    • Proposed as answer by Jeremy_Wu Monday, September 3, 2012 5:55 AM
    • Marked as answer by Jeremy_Wu Tuesday, September 4, 2012 5:17 AM
    Thursday, August 2, 2012 9:18 AM

All replies

  • Hi abee_13,

    By "then try to shut down" - do you mean whilst the computer is asleep or whilst it's at the desktop?

    -Julian

    Tuesday, July 31, 2012 11:25 PM
  • If my computer is asleep and I wake it up to shut it down BSOD is almost guaranteed.  
    Wednesday, August 1, 2012 12:36 AM
  • Then maybe try not putting your PC to sleep? Some motherboards have issues with sleeping in Windows, I just solved it by having my desktops never sleep, only shutdown.
    Wednesday, August 1, 2012 12:41 AM
  • This BSOD only occurs when I put the computer to sleep and then try to shut down. It takes about 10 minutes to show up. 

    Windows 7 Home Premium 64- Bit 

    Gateway 6gb 1 Tb Intel i3 

    Here are some of the dump files 

    http://sdrv.ms/MXHG5a

    http://sdrv.ms/MXHL91

    http://sdrv.ms/MXHLGj

    http://sdrv.ms/MXHPWx

    071312-20326-01.dmp

    *******************************************************************************
    *                                                                             *
    *                        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: fffffa8005e94060, Physical Device Object of the stack
    Arg3: fffff80000ba2748, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa800e43a5a0, The blocked IRP
    Debugging Details:
    ------------------
    DRVPOWERSTATE_SUBCODE:  3
    IMAGE_NAME:  pci.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f
    MODULE_NAME: pci

    FAULTING_MODULE: fffff88000e6a000 pci
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    STACK_TEXT:  
    fffff800`00ba26f8 fffff800`030f56c2 : 00000000`0000009f 00000000`00000003 fffffa80`05e94060 fffff800`00ba2748 : nt!KeBugCheckEx
    fffff800`00ba2700 fffff800`03095e3c : fffff800`00ba28c0 fffff800`00ba28c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34050
    fffff800`00ba27a0 fffff800`03095cd6 : fffff880`0a262990 fffff880`0a262990 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00ba2810 fffff800`03095bbe : 000000f6`8de562eb fffff800`00ba2e88 00000000`006793d1 fffff800`03201ca8 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00ba2e60 fffff800`030959a7 : fffff800`031fdec8 fffffa80`006793d1 00000000`00000000 00000000`000000d1 : nt!KiTimerExpiration+0x1be
    fffff800`00ba2f00 fffff800`0308e305 : 00000000`00000000 fffffa80`054e6660 00000000`00000000 fffff880`10214588 : nt!KiRetireDpcList+0x277
    fffff800`00ba2fb0 fffff800`0308e11c : fffffa80`09e98000 fffff800`035fe895 fffff800`03624460 fffff880`035caca0 : nt!KyRetireDpcList+0x5
    fffff880`035cabe0 fffff800`030d6193 : fffff800`03087740 fffff800`030877ac 00000000`00000000 fffffa80`09e98001 : nt!KiDispatchInterruptContinue
    fffff880`035cac10 fffff800`030877ac : 00000000`00000000 fffffa80`09e98001 00000000`00000000 fffffa80`00000000 : nt!KiDpcInterruptBypass+0x13
    fffff880`035cac20 fffff880`0460f8bf : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x1fc
    fffff880`035cadb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Rt64win7+0xf8bf
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    FAILURE_BUCKET_ID:  X64_0x9F_3_Rt64win7_IMAGE_pci.sys
    BUCKET_ID:  X64_0x9F_3_Rt64win7_IMAGE_pci.sys
    Followup: MachineOwner
    --------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Bug Check 0x9F: http://msdn.microsoft.com/en-us/library/windows/hardware/ff559329(v=vs.85).aspx

    ** The Blue Screen Caused by Rt64win7 : a component of your Realtek networking , Try to update it to the latest Version : http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=7&PFid=10&Level=3&Conn=2

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

    071812-17752-01.dmp

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

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

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

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

    This is a very common bugcheck.  Usually the exception address pinpoints

    the driver/function that caused the problem.  Always note this address

    as well as the link date of the driver/image that contains this address.

    Some common problems are exception code 0x80000003.  This means a hard

    coded breakpoint or assertion was hit, but this system was booted

    /NODEBUG.  This is not supposed to happen as developers should never have

    hardcoded breakpoints in retail code, but ...

    If this happens, make sure a debugger gets connected, and the

    system is booted /DEBUG.  This will let us see why this breakpoint is

    happening.

    Arguments:

    Arg1: ffffffffc0000005, The exception code that was not handled

    Arg2: fffff88001868e0d, The address that the exception occurred at

    Arg3: fffff880035b6268, Exception Record Address

    Arg4: fffff880035b5ac0, Context Record Address

    Debugging Details:

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

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    FAULTING_IP:

    ndis!NdisAllocateCloneOidRequest+4d

    fffff880`01868e0d 410fb64500      movzx   eax,byte ptr [r13]

    EXCEPTION_RECORD:  fffff880035b6268 -- (.exr 0xfffff880035b6268)

    ExceptionAddress: fffff88001868e0d (ndis!NdisAllocateCloneOidRequest+0x000000000000004d)

       ExceptionCode: c0000005 (Access violation)

      ExceptionFlags: 00000000

    NumberParameters: 2

       Parameter[0]: 0000000000000000

       Parameter[1]: ffffffffffffffff

    Attempt to read from address ffffffffffffffff

    CONTEXT:  fffff880035b5ac0 -- (.cxr 0xfffff880035b5ac0)

    rax=0000000000000000 rbx=0000000000000000 rcx=fffff880018ccec0

    rdx=fffff880035b6800 rsi=0000000000000000 rdi=fffff880035b6800

    rip=fffff88001868e0d rsp=fffff880035b64a0 rbp=00000000646e5446

     r8=00000000646e5446  r9=fffff880035b6530 r10=000000000000000c

    r11=0000000000000000 r12=fffff880035b6530 r13=0002020400020203

    r14=fffff880018c9110 r15=fffff880018c9110

    iopl=0         nv up ei pl nz na pe nc

    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202

    ndis!NdisAllocateCloneOidRequest+0x4d:

    fffff880`01868e0d 410fb64500      movzx   eax,byte ptr [r13] ds:002b:00020204`00020203=??

    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    EXCEPTION_PARAMETER1:  0000000000000000

    EXCEPTION_PARAMETER2:  ffffffffffffffff

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b8100

    GetUlongFromAddress: unable to read from fffff800032b81c0

     ffffffffffffffff

    FOLLOWUP_IP:

    wfplwf!FilterOidRequest+2b

    fffff880`030d65ef 448bd8          mov     r11d,eax

    BUGCHECK_STR:  0x7E

    LAST_CONTROL_TRANSFER:  from fffff880030d65ef to fffff88001868e0d

    STACK_TEXT: 

    fffff880`035b64a0 fffff880`030d65ef : fffff880`035b6800 00000000`00010117 fffffa80`0add71a0 fffffa80`0ae09610 : ndis!NdisAllocateCloneOidRequest+0x4d

    fffff880`035b6500 fffff880`018ee57b : 00000000`00000000 fffffa80`0ae07c90 00000000`00000000 fffffa80`0ae07c90 : wfplwf!FilterOidRequest+0x2b

    fffff880`035b6530 fffff880`018683f9 : fffffa80`00000000 fffffa80`0ae07c90 fffffa80`0add71a0 00000000`00000001 : ndis!ndisFDoOidRequest+0x21b

    fffff880`035b6600 fffff880`0186b7f3 : fffff880`035b6801 fffff880`035b6800 00000000`00000000 00000000`00000000 : ndis!ndisQueueRequestOnTop+0x219

    fffff880`035b66a0 fffff880`019121ec : 00000000`00000500 fffff880`035b6800 fffffa80`0add71a0 00000000`000000f0 : ndis!ndisQuerySetMiniportEx+0x143

    fffff880`035b6710 fffff880`018dbdf2 : fffffa80`0ae09010 00000000`00000000 00000000`00000148 00000000`00000000 : ndis!ndisQuerySetMiniport+0x1c

    fffff880`035b6750 fffff880`018db80b : 00000000`00000520 00000000`00000000 fffffa80`0add71a0 00000000`00000520 : ndis!ndisQueryCustomGuids+0xa2

    fffff880`035b67c0 fffff880`018dbbc6 : fffff800`032116c0 fffff880`035b6a00 00000000`00000000 00000000`00000000 : ndis!ndisQuerySupportedGuidToOidList+0x1bb

    fffff880`035b6930 fffff880`018d9065 : 00000000`00000000 fffffa80`0ae11000 fffffa80`0ae145a8 fffffa80`0add7050 : ndis!ndisWmiRegister+0x76

    fffff880`035b6990 fffff800`0331c838 : fffff880`00000000 fffffa80`0add7050 fffffa80`0ae14010 fffffa80`0ae11008 : ndis!ndisWMIDispatch+0x185

    fffff880`035b6a00 fffff800`0331cf4e : 00000000`00000000 fffffa80`0ae14010 00000000`00002000 fffffa80`0ae11000 : nt!WmipForwardWmiIrp+0x16c

    fffff880`035b6a80 fffff800`034afee4 : 00000000`c0000010 00000000`00002000 00000000`00000000 fffff8a0`0192cb90 : nt!WmipSendWmiIrp+0xa2

    fffff880`035b6ae0 fffff800`034dd07c : fffffa80`0adb8a30 fffff800`032262d8 fffffa80`054e8660 fffff8a0`0192cb90 : nt!WmipRegisterOrUpdateDS+0xb4

    fffff880`035b6b40 fffff800`03092841 : fffff800`034dd020 fffff800`0337b601 fffffa80`054e8600 fffffa80`0ac2fc58 : nt!WmipRegistrationWorker+0x5c

    fffff880`035b6b70 fffff800`0331fe6a : 00000000`00000000 fffffa80`054e8660 00000000`00000080 fffffa80`054d2b30 : nt!ExpWorkerThread+0x111

    fffff880`035b6c00 fffff800`03079ec6 : fffff880`033d7180 fffffa80`054e8660 fffff880`033e1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a

    fffff880`035b6c40 00000000`00000000 : fffff880`035b7000 fffff880`035b1000 fffff880`035b66f0 00000000`00000000 : nt!KiStartSystemThread+0x16

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  wfplwf!FilterOidRequest+2b

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: wfplwf

    IMAGE_NAME:  wfplwf.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bccb6

    STACK_COMMAND:  .cxr 0xfffff880035b5ac0 ; kb

    FAILURE_BUCKET_ID:  X64_0x7E_wfplwf!FilterOidRequest+2b

    BUCKET_ID:  X64_0x7E_wfplwf!FilterOidRequest+2b

    Followup: MachineOwner

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

    Bug Check 0x7E : http://msdn.microsoft.com/en-us/library/windows/hardware/ff559239(v=vs.85).aspx

    1. Download and install updates and device drivers for your computer from Windows Update.
    2. Scan your computer for computer viruses.
    3. Check your hard disk for errors.

    Regards,





    MCT / MCITP / MCTS / MCSA / MCSE / C|EH

    Wednesday, August 1, 2012 7:56 AM
  • Thanks, I'll try updating the driver. But now I'm starting to think it's a virus or some kind of malware because I transferred some files to another computer and it had gotten the same BSOD.

    Here's the dump for that BSOD. 

    http://sdrv.ms/M4Gv4x

    Wednesday, August 1, 2012 11:41 PM
  • Hi,


    After checking the dump, I notice the error, BugCheck 9F, {3, 862a56a8, 82d3cae0, 85fb7d20}.


    Please see Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE for details.


    The issue seems to be related to 0x9F_3_VBoxUSB_IMAGE_usbhub.sys, you can try to update the driver for you USB Hub or remove the device and see how it works.


    Hope this helps.


    Jeremy Wu

    TechNet Community Support

    • Proposed as answer by Jeremy_Wu Monday, September 3, 2012 5:55 AM
    • Marked as answer by Jeremy_Wu Tuesday, September 4, 2012 5:17 AM
    Thursday, August 2, 2012 2:57 AM
  • Hi,


    After checking the dump, I notice the error, BugCheck 9F, {3, 862a56a8, 82d3cae0, 85fb7d20}.


    Please see Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE for details.


    The issue seems to be related to 0x9F_3_VBoxUSB_IMAGE_usbhub.sys, you can try to update the driver for you USB Hub or remove the device and see how it works.


    Hope this helps.


    Jeremy Wu

    TechNet Community Support

    Actually, Jeremy discovered something I think crucial to this problem. That driver doesn't seem to be for a USB hub, rather, it seems to be a VirtualBox driver. Have you installed VirtualBox on your machine? If so, try uninstalling it and then installing the latest version. 

    Otherwise, yes, you may have a malware or hardware problem.

    -Julian

    • Proposed as answer by Jeremy_Wu Monday, September 3, 2012 5:55 AM
    • Marked as answer by Jeremy_Wu Tuesday, September 4, 2012 5:17 AM
    Thursday, August 2, 2012 9:18 AM
  • Thanks I will report as soon as possible. 
    Friday, August 3, 2012 2:32 AM
  • hello abee_13,

    I have also experienced similar BSOD many times. As a result i got scared and frustrated also. That's why i tried to find out some solution for this problem and then i got this:http://www.techyv.com/questions/how-remove-bosd-or-blue-screen-death-my-computer

    i help me to understand the real problem and i follow its instruction and now i think its gone.

    hope it will also help you.

    Friday, August 3, 2012 4:42 AM