locked
[W7] What is causing me to get this bsod? 0x1000007e Wdf01000.sys RRS feed

  • Question

  • Here are the .dmp files.

    https://www.dropbox.com/s/i01byrxgg3it63o/Minidump.zip

    This happens when I have my android device plugged in through usb and in debugging mode.

    Thanks


    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        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: ffffffff80000003, The exception code that was not handled
    Arg2: fffff800036bda10, The address that the exception occurred at
    Arg3: fffff880033a0be8, Exception Record Address
    Arg4: fffff880033a0440, Context Record Address

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

    FAULTING_IP:
    nt!DbgBreakPoint+0
    fffff800`036bda10 cc              int     3

    EXCEPTION_RECORD:  fffff880033a0be8 -- (.exr 0xfffff880033a0be8)
    ExceptionAddress: fffff800036bda10 (nt!DbgBreakPoint)
       ExceptionCode: 80000003 (Break instruction exception)
      ExceptionFlags: 00000000
    NumberParameters: 1
       Parameter[0]: 0000000000000000

    CONTEXT:  fffff880033a0440 -- (.cxr 0xfffff880033a0440)
    rax=0000000000000000 rbx=fffffa800a894980 rcx=234ebbcbfaac0000
    rdx=0000000000000008 rsi=0000057ff83f7f78 rdi=fffffa8007c083c0
    rip=fffff800036bda10 rsp=fffff880033a0e28 rbp=fffff88000eace50
     r8=0000000000000001  r9=fffff800037030a0 r10=0000000000000000
    r11=fffff880033a0e28 r12=0000000000000001 r13=0000000000000000
    r14=fffffa8007c083c0 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`036bda10 cc              int     3
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1

    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 fffff88000ec5028 to fffff800036bda10

    STACK_TEXT:  
    fffff880`033a0e28 fffff880`00ec5028 : fffff880`00eacb70 fffffa80`06a31b50 fffff880`00eace50 0000057f`f83f7f78 : nt!DbgBreakPoint
    fffff880`033a0e30 fffff880`00ebf62d : ffffffff`dc3cba00 0000057f`f83f7f78 fffff880`033a0ea0 fffffa80`07c08090 : Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+0x70
    fffff880`033a0e70 fffff880`00ebf3f0 : fffffa80`07c08080 0000057f`f83f7f00 fffffa80`07c083f0 fffffa80`07c08090 : Wdf01000!FxIoQueue::StopProcessingForPower+0x1ed
    fffff880`033a0ec0 fffff880`00f34323 : 00000000`00000000 fffff880`033a0f00 fffffa80`07612fc0 fffffa80`0bb0e520 : Wdf01000!FxPkgIo::StopProcessingForPower+0x22c
    fffff880`033a0f30 fffff880`00ebcc3c : 00000000`00000000 fffff880`033a1090 fffff880`00f42100 fffffa80`0bb0e520 : Wdf01000!FxPkgPnp::PowerGotoD3Stopped+0x73
    fffff880`033a0f90 fffff880`00ebd106 : fffff880`00f41f60 fffffa80`0bb0e6d8 fffffa80`0bb0e520 fffffa80`0bb0e520 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1d8
    fffff880`033a10f0 fffff880`00ebce9f : 00000000`00000000 fffff880`033a11d0 fffffa80`0bb0e6c0 fffffa80`0bb0e520 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
    fffff880`033a1160 fffff880`00f3a3e3 : 00000000`00000000 fffffa80`0bb0e520 fffff880`00f44910 fffff880`01abe2a7 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1b3
    fffff880`033a1200 fffff880`00ec5b4b : 00000000`0000055b fffff880`033a1330 00000000`ffff7fff fffffa80`0bb0e520 : Wdf01000!FxPkgPnp::PowerPolStopping+0x1b
    fffff880`033a1230 fffff880`00ebd801 : fffff880`00f44a50 fffffa80`0bb0e790 fffffa80`0bb0e520 fffffa80`0bb0e520 : Wdf01000!FxPkgPnp::PowerPolicyEnterNewState+0x1d7
    fffff880`033a1390 fffff880`00ebd595 : 00000000`00000000 fffff880`033a1470 fffffa80`0bb0e778 fffffa80`0bb0e520 : Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x145
    fffff880`033a1400 fffff880`00f37cde : 00000000`00000000 00000000`00000129 00000000`00000129 fffff800`039be116 : Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x1c1
    fffff880`033a14a0 fffff880`00ed181d : 00000000`00000129 fffff880`033a1540 00000000`00000127 fffffa80`0bb0e520 : Wdf01000!FxPkgPnp::PnpEventFailedIoStarting+0xe
    fffff880`033a14d0 fffff880`00ed2032 : fffffa80`0bb0e630 fffffa80`0bb0e648 fffffa80`0bb0e520 fffffa80`0bb0e520 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a1
    fffff880`033a1570 fffff880`00ed1cdd : 00000000`00000000 fffff880`033a1650 fffffa80`0bb0e630 fffffa80`0bb0e520 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
    fffff880`033a15e0 fffff880`00f36701 : 00000000`00000000 fffffa80`0bb0e520 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x18d
    fffff880`033a1680 fffff880`00ebaecf : fffffa80`0a894980 fffff880`033a1700 00000000`00000000 fffff800`001e001c : Wdf01000!FxPkgFdo::_PnpSurpriseRemoval+0x25
    fffff880`033a16b0 fffff880`00eb29da : fffffa80`0b0e6740 fffffa80`0b0e6740 fffffa80`0b0e6740 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x18f
    fffff880`033a1710 fffff880`00eb2aa6 : fffffa80`0b0e6740 fffff880`033a1848 fffffa80`076e66a0 fffffa80`076e66a0 : Wdf01000!FxDevice::Dispatch+0x19a
    fffff880`033a1750 fffff800`03933d11 : fffffa80`076e66a0 fffff880`033a1848 00000000`c00000bb fffffa80`0b0e6740 : Wdf01000!FxDevice::DispatchWithLock+0xa6
    fffff880`033a1790 fffff800`03ab2681 : fffffa80`08ba5a00 00000000`00000000 fffffa80`09578be0 fffff880`033a1828 : nt!IopSynchronousCall+0xe1
    fffff880`033a1800 fffff800`03aad058 : fffffa80`07a78fe0 fffffa80`08ba5a00 00000000`0000030a 00000000`00000308 : nt!IopRemoveDevice+0x101
    fffff880`033a18c0 fffff800`03ab21c7 : fffffa80`09578be0 00000000`00000000 00000000`00000003 00000000`00000136 : nt!PnpSurpriseRemoveLockedDeviceNode+0x128
    fffff880`033a1900 fffff800`03ab22e0 : 00000000`00000000 fffff8a0`05312a00 fffff8a0`155c70b0 fffff880`033a1a58 : nt!PnpDeleteLockedDeviceNode+0x37
    fffff880`033a1930 fffff800`03b42c4f : 00000000`00000002 00000000`00000000 fffffa80`073f3a90 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
    fffff880`033a19a0 fffff800`03b4380c : fffff880`033a1b78 fffffa80`087ef800 fffffa80`06a31b00 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0x6cf
    fffff880`033a1ae0 fffff800`03a2c9ae : 00000000`00000000 fffffa80`087ef870 fffff8a0`05f06bc0 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c
    fffff880`033a1b10 fffff800`036cf251 : fffff800`03932b98 fffff8a0`05312ab0 fffff800`0386b2d8 fffff800`0386b2d8 : nt! ?? ::NNGAKEGL::`string'+0x552ab
    fffff880`033a1b70 fffff800`03963ede : 00000000`00000000 fffffa80`06a31b50 00000000`00000080 fffffa80`06a099e0 : nt!ExpWorkerThread+0x111
    fffff880`033a1c00 fffff800`036b6906 : fffff880`03165180 fffffa80`06a31b50 fffff880`0316ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`033a1c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


    FOLLOWUP_IP:
    Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70
    fffff880`00ec5028 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 0xfffff880033a0440 ; kb

    FAILURE_BUCKET_ID:  X64_0x7E_Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70

    BUCKET_ID:  X64_0x7E_Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70

    Followup: MachineOwner
    • Edited by Kamuzai Tuesday, April 16, 2013 6:38 PM
    Tuesday, April 16, 2013 6:25 PM

Answers

  • Related to Wdf01000.sys WDF Dynamic driver from Microsoft. I would run SFC (system file check) but since ti is waiting for the FX driver I would also run

    Try this free video stress test:  http://www.ozone3d.net/benchmarks/fur/
    FurMark Setup:

    - If you have more than one GPU, select Multi-GPU during setup
    - In the Run mode box, select "Stability Test" and "Log GPU Temperature"
    Click "Go" to start the test
    - Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first)
    - Click "Quit" to exit


    Wanikiya & Dyami -Team-ZigZag. www.ZigZag3143.com email Admin@zigzag3143.com


    • Edited by ZigZag3143x Sunday, June 9, 2013 1:38 AM
    • Marked as answer by ZigZag3143x Sunday, June 9, 2013 1:38 AM
    Tuesday, April 16, 2013 7:39 PM

All replies

  • Your problem is related to Wdf01000.sys WDF Dynamic driver from Microsoft.

    Please run a System File Check {SFC}...

    Go to start>type CMD>right click and run as administrator> Type SFC /scannow

    Let us know what it says at the end.

    You may have to run this up to 3 times.

    http://pcsupport.about.com/od/toolsofthetrade/ht/sfc-scannow.htm

    BugCheck 1000007E, {ffffffff80000003, fffff800036bda10, fffff880033a0be8, fffff880033a0440}
    Probably caused by : Wdf01000.sys ( Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70 )
    Followup: MachineOwner
    ---------

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

    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.


    Dyami & Wanikiya ...Team ZigZag.



    Tuesday, April 16, 2013 7:39 PM
  • Related to Wdf01000.sys WDF Dynamic driver from Microsoft. I would run SFC (system file check) but since ti is waiting for the FX driver I would also run

    Try this free video stress test:  http://www.ozone3d.net/benchmarks/fur/
    FurMark Setup:

    - If you have more than one GPU, select Multi-GPU during setup
    - In the Run mode box, select "Stability Test" and "Log GPU Temperature"
    Click "Go" to start the test
    - Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first)
    - Click "Quit" to exit


    Wanikiya & Dyami -Team-ZigZag. www.ZigZag3143.com email Admin@zigzag3143.com


    • Edited by ZigZag3143x Sunday, June 9, 2013 1:38 AM
    • Marked as answer by ZigZag3143x Sunday, June 9, 2013 1:38 AM
    Tuesday, April 16, 2013 7:39 PM
  • So I ran it once and came back with this.

    Beginning verification phase of system scan.
    Verification 100% complete.
    Windows Resource Protection found corrupt files but was unable to fix some of th
    em.
    Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
    C:\Windows\Logs\CBS\CBS.log

    The system file repair changes will take effect after the next reboot.

    Here is the CBS.log.

    https://www.dropbox.com/s/qxiwejlm0yb56c7/CBS.log

    Tuesday, April 16, 2013 8:39 PM
  • The link is bad.  Tp be honest if there are important enough files that could not be repaired your quickest way to get working is a repair install from the win 7 dvd.  You might be able to fix the problems one a t a time but that is usually a time consuming and intensive procedure.

    Still if you want to continue fix the link.


    Wanikiya & Dyami -Team-ZigZag. www.ZigZag3143.com email Admin@zigzag3143.com

    Tuesday, April 16, 2013 9:29 PM
  • Try this one. https://www.dropbox.com/s/qxiwejlm0yb56c7/CBS.log
    Tuesday, April 16, 2013 10:12 PM
  • Quite a fe corrupted items in the store including slmgr which appears to have been tampered with.  You are not going to be able to replace these one by one.  Just in case try running it 3 more times.  There is a finite limit to how many corrections it can make per run

    Wanikiya & Dyami -Team-ZigZag. www.ZigZag3143.com email Admin@zigzag3143.com

    Tuesday, April 16, 2013 10:20 PM
  • Well, now it says it hasn't found any errors. What now? lol
    Tuesday, April 16, 2013 11:15 PM
  • run it a third time.

    Sometimes that reflect an I/o issue like a HD so I would run CHKDSK as welll

    A- CHKDSK /R /F:

    Chkdsk disclaimer: While performing chkdsk on the hard drive if any bad sectors are found  when chkdsk tries to repair that sector  any data available on that sector might be lost.


    Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.
    Do this for each hard drive on your system.
    When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.

    Then reboot and let the test run.
    It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.
    http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/


     See "CHKDSK LogFile" below in order to check the results of the test.


    B- Elevated Command Prompt:
    Go to Start and type in "cmd.exe" (without the quotes)
    At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"


    C-CHKDSK LogFile:

    Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
    Expand the Windows logs heading, then select the Application log file entry.
    Double click on the Source column header.
    Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
    Copy/paste the results into your next post. 


    Wanikiya & Dyami -Team-ZigZag. www.ZigZag3143.com email Admin@zigzag3143.com

    Wednesday, April 17, 2013 12:15 AM
  • I did get the BSOD again. After I ran it 3 times.

    So the best solution would be to run the win7 cd and have it repair?

    I will however do the CHKDSK first though.

    Wednesday, April 17, 2013 1:25 AM