locked
Can anyone help me out solve this BSOD on my Dell when I hibernate my machine? RRS feed

  • Question

  • Hi,

    I'm having this BSOD on my machine that I have no idea how to fix. I believe all my drivers are updated but I can't find the root cause... I have a Dell Latitude E5520 (it's my work machine) running Windows 7 Enterprise. This problem occurs when I hibernate my machine. Not every time I hibernate but some of the times... I believe it has something to do with the dock station (where I have 2 monitors connected) and when I unplug it from the dock station, plug it back in and hibernate. Or something like that, I'm not really sure... Can't yet figure out the pattern when this BSOD is occurring.

    I have tried to use WinDbg and search a bit about it reports me back but I couldn't yet found the solution, maybe you guys can help me out...

    Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available
    
    Symbol search path is: srv*
    Executable search path is: srv*
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
    Machine Name:
    Kernel base = 0xfffff800`03201000 PsLoadedModuleList = 0xfffff800`03445670
    Debug session time: Tue Feb 26 19:22:34.339 2013 (UTC + 0:00)
    System Uptime: 1 days 10:07:24.366
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................................................
    Loading User Symbols
    
    Loading unloaded module list
    ..................................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7E, {ffffffff80000003, fffff8000326ea50, fffff8800b3f43f8, fffff8800b3f3c50}
    
    Probably caused by : Wdf01000.sys ( Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
    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.
    Arguments:
    Arg1: ffffffff80000003, The exception code that was not handled
    Arg2: fffff8000326ea50, The address that the exception occurred at
    Arg3: fffff8800b3f43f8, Exception Record Address
    Arg4: fffff8800b3f3c50, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid
    
    FAULTING_IP: 
    nt!DbgBreakPoint+0
    fffff800`0326ea50 cc              int     3
    
    EXCEPTION_RECORD:  fffff8800b3f43f8 -- (.exr 0xfffff8800b3f43f8)
    ExceptionAddress: fffff8000326ea50 (nt!DbgBreakPoint)
       ExceptionCode: 80000003 (Break instruction exception)
      ExceptionFlags: 00000000
    NumberParameters: 1
       Parameter[0]: 0000000000000000
    
    CONTEXT:  fffff8800b3f3c50 -- (.cxr 0xfffff8800b3f3c50)
    rax=0000000000000000 rbx=fffffa8007e57e40 rcx=1e367ac68d540000
    rdx=0000000000000008 rsi=0000057ff6667808 rdi=fffffa8009998b30
    rip=fffff8000326ea50 rsp=fffff8800b3f4638 rbp=fffff88000ea2e50
     r8=0000000000000001  r9=fffff800032b4180 r10=fffffffffffffffe
    r11=fffff8800b3f4638 r12=0000000000000001 r13=0000000000000000
    r14=fffffa8009998b30 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202
    nt!DbgBreakPoint:
    fffff800`0326ea50 cc              int     3
    Resetting default scope
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x7E
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    LAST_CONTROL_TRANSFER:  from fffff88000ebb028 to fffff8000326ea50
    
    STACK_TEXT:  
    fffff880`0b3f4638 fffff880`00ebb028 : fffff880`00ea2b70 fffffa80`0b5097d0 fffff880`00ea2e50 0000057f`f6667808 : nt!DbgBreakPoint
    fffff880`0b3f4640 fffff880`00eb562d : ffffffff`dc3cba00 0000057f`f6667808 fffff880`0b3f46b0 fffffa80`09998800 : Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+0x70
    fffff880`0b3f4680 fffff880`00eb53f0 : fffffa80`099987f0 0000057f`f6667800 fffffa80`09998b60 fffffa80`09998800 : Wdf01000!FxIoQueue::StopProcessingForPower+0x1ed
    fffff880`0b3f46d0 fffff880`00eb51a8 : 00000000`00000000 fffff880`0b3f4700 fffffa80`086afcf0 fffffa80`0998a080 : Wdf01000!FxPkgIo::StopProcessingForPower+0x22c
    fffff880`0b3f4740 fffff880`00eb5131 : 00000000`00000004 00000000`00000000 fffffa80`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::PowerGotoDx+0x64
    fffff880`0b3f4780 fffff880`00eb2c3c : 00000000`0000031a fffff880`0b3f48b0 00000000`ffff7fff fffffa80`0998a080 : Wdf01000!FxPkgPnp::PowerGotoDxArmedForWakeNP+0x9
    fffff880`0b3f47b0 fffff880`00eb3106 : fffff880`00f37f60 fffffa80`0998a238 fffffa80`0998a080 fffffa80`0998a080 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1d8
    fffff880`0b3f4910 fffff880`00eb2e9f : 00000000`00000000 fffff880`0b3f49f0 fffffa80`0998a220 fffffa80`0998a080 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
    fffff880`0b3f4980 fffff880`00ebc687 : 00000000`00000000 fffffa80`0998a080 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1b3
    fffff880`0b3f4a20 fffff880`00eb0fea : 00000000`00000002 0000057f`f8869ce8 fffffa80`0923ccc0 fffffa80`0a7bb502 : Wdf01000!FxPkgFdo::DispatchDeviceSetPower+0x117
    fffff880`0b3f4a70 fffff880`00ea89da : fffffa80`0a7bb500 fffffa80`0a7bb500 fffffa80`0a7bb500 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x2aa
    fffff880`0b3f4ad0 fffff880`00ea8aa6 : fffffa80`0a7bb500 00000000`00000000 fffffa80`0923ccc0 fffffa80`0923ccc0 : Wdf01000!FxDevice::Dispatch+0x19a
    fffff880`0b3f4b10 fffff800`03393085 : 00000000`00000001 00000000`00000000 fffffa80`0923ccc0 fffffa80`0a7bb5a8 : Wdf01000!FxDevice::DispatchWithLock+0xa6
    fffff880`0b3f4b50 fffff800`0351734a : ffffffff`fa0a1f00 fffffa80`0b5097d0 00000000`00000080 00000000`00000000 : nt!PopIrpWorker+0x3c5
    fffff880`0b3f4c00 fffff800`03267946 : fffff880`02fd7180 fffffa80`0b5097d0 fffffa80`069fdb50 00000000`00000202 : nt!PspSystemThreadStartup+0x5a
    fffff880`0b3f4c40 00000000`00000000 : fffff880`0b3f5000 fffff880`0b3ef000 fffff880`0b3f4390 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    FOLLOWUP_IP: 
    Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70
    fffff880`00ebb028 488b442440      mov     rax,qword ptr [rsp+40h]
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Wdf01000
    
    IMAGE_NAME:  Wdf01000.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5010aa89
    
    STACK_COMMAND:  .cxr 0xfffff8800b3f3c50 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70
    
    BUCKET_ID:  X64_0x7E_Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70
    
    Followup: MachineOwner
    ---------
    


    Wednesday, February 27, 2013 11:05 AM

Answers

  • You were right Gerry... It's my One X causing the BSOD.

    Today I got another one after a while and then I decided to test this a little bit further. Every time I hibernate my machine with my One X connected to the PC, it gives a BSOD. If I don't have it plugged in, it hibernates just fine.

    I need to find drivers that let me hibernate without crashing my machine...

    • Marked as answer by tracycai Thursday, March 14, 2013 2:15 AM
    • Unmarked as answer by Ricardo.Amaral Thursday, March 14, 2013 1:00 PM
    • Marked as answer by ZigZag3143x Friday, March 15, 2013 4:23 PM
    Wednesday, March 13, 2013 9:51 PM

All replies

  • Please post a copy of your dumpfile as shared file to your Sky Drive with a link here.

    For advice on how to configure your system to create dump files please read:
    http://support.microsoft.com/kb/254649

    The dumpfile will be created at c:\windows\minidump. You may need to change your settings in Windows to be able to see the file. To show hidden files type Folder Options in the search box above the Start button and select View, Advanced Settings and verify that the box before "Show hidden files and folders" is checked and "Hide protected operating system files" is unchecked. You may need to scroll down to see the second item. You should also make certain that the box before "Hide extensions for known file types" is not checked.

    What is your computer make and model? If not a branded computer what is your motherboard make and model?

    Please download and run Driver View and upload a copy of the report it produces to your Sky Drive.

    http://www.nirsoft.net/utils/driverview.html

    Type System Information in the Search Box above the start Button and press the ENTER key. Select File, Export and give the file a name noting where it is located. Please upload to your Sky Drive, share with everyone and post a link here. The request for a copy of this file is additional to answering the question about make and model. Failure to deal with both requests will delay finding a solution.

    Please say if you need help with using Sky Drive.


    Hope this helps, Gerry

    Wednesday, February 27, 2013 1:16 PM
  • Wednesday, February 27, 2013 2:06 PM
  • RA

    While not implicated in these crashes I view McAffee and highly suspect.  It is easy enough to remove and replace with MSE to test that it might be worthwile.  Were it me, I would.

    http://download.mcafee.com/products/licensed/cust_support_patches/MCPR.exe



    Dyami & Wanikiya -Team-ZigZag.

    Wednesday, February 27, 2013 6:30 PM
  • This is a work machine and McAffee came pre-installed. I don't think I'm supposed to uninstall it and if I did, I think it would install itself back. That's the kind of software I'm not supposed to touch and I probably don't have the permissions to do so.

    Any other solution? Maybe upgrade it somehow?

    Wednesday, February 27, 2013 9:22 PM
  • Ricardo

    This device shows up in System Information as a Problem Device:
    Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64   ROOT\NET\0001      This device is disabled.

    I am connecting this entry to an error being reported by Windows Error Reporting referring to this device:
    Event Name: WUDFHostProblem USB\VID_0BB4&PID_0DFB&REV_0232

    I think you have connected an HTC mobile phone. You either need to remove ( uninstall ) the device in Device Manager or get the right driver. Knowing the mobile phone model detail could help locate the right driver. Disabling the device has not resolved the problems it's existence on your computer is creating.



    Hope this helps, Gerry

    Wednesday, February 27, 2013 9:46 PM
  • The Cisco thing is the client I use to connect to my company's VPN network and I believe it's disabled because I wasn't connected to the VPN. Not sure if that's relevant or not...

    Yes, I have connected my HTC One X. For the record, I have connected more devices as I'm an Android developer. I can't uninstall the device as you can imagine, I'll try to get a more recent driver, but I'm not sure one exists :(

    Thursday, February 28, 2013 10:27 AM
  • Ricardo

    "I can't uninstall the device as you can imagine". You do have two strands to the problem. You need to find out for certain that the device is causing the system to crash. The second part is find a solution. Removal is the best test to find out if it is the problem.


    Hope this helps, Gerry

    Thursday, February 28, 2013 11:58 AM
  • I understand that. But there isn't a pattern to this crash and I can't just uninstall the device drivers and wait to see if it's causing the crash or not. I can't do my job properly if those devices are not installed.

    I have now updated the device drivers to the latest version. For now, I'll wait and see if I get another crash... Hopefully not.

    Thursday, February 28, 2013 6:51 PM
  • You were right Gerry... It's my One X causing the BSOD.

    Today I got another one after a while and then I decided to test this a little bit further. Every time I hibernate my machine with my One X connected to the PC, it gives a BSOD. If I don't have it plugged in, it hibernates just fine.

    I need to find drivers that let me hibernate without crashing my machine...

    • Marked as answer by tracycai Thursday, March 14, 2013 2:15 AM
    • Unmarked as answer by Ricardo.Amaral Thursday, March 14, 2013 1:00 PM
    • Marked as answer by ZigZag3143x Friday, March 15, 2013 4:23 PM
    Wednesday, March 13, 2013 9:51 PM