locked
BSOD WinDBG Shows Fault With WDF01000.sys Please Help RRS feed

  • Question

  • Ive installed WinDbg, it shows the following;


    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\User\Desktop\123012-28704-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
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
    Machine Name:
    Kernel base = 0xfffff800`03264000 PsLoadedModuleList = 0xfffff800`034a8670
    Debug session time: Sun Dec 30 23:10:23.208 2012 (UTC + 0:00)
    System Uptime: 0 days 0:06:39.660
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ......................................
    Loading User Symbols
    Loading unloaded module list
    ...........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 10D, {d, fffffa8006517ad0, fffffa800797d010, fffffa8006511c50}

    Probably caused by : Wdf01000.sys ( Wdf01000!FxPkgFdo::DispatchDeviceSetPower+b3 )

    Followup: MachineOwner
    ---------

    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    WDF_VIOLATION (10d)
    The Kernel-Mode Driver Framework was notified that Windows detected an error
    in a framework-based driver. In general, the dump file will yield additional
    information about the driver that caused this bug check.
    Arguments:
    Arg1: 000000000000000d, A power irp was received for the device but the irp was not
    requested by the device (the power policy owner). Possibly there
    are multiple power policy owners. Only one driver in the stack can
    be the power policy owner. A KMDF driver can change power policy
    ownership by calling the DDI WdfDeviceInitSetPowerPolicyOwnership.
    Arg2: fffffa8006517ad0, Device object pointer.
    Arg3: fffffa800797d010, Power Irp.
    Arg4: fffffa8006511c50, Reserved.

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


    BUGCHECK_STR:  0x10D_d

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff88000e91623 to fffff800032e2fc0

    STACK_TEXT:  
    fffff880`0c357ac8 fffff880`00e91623 : 00000000`0000010d 00000000`0000000d fffffa80`06517ad0 fffffa80`0797d010 : nt!KeBugCheckEx
    fffff880`0c357ad0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgFdo::DispatchDeviceSetPower+0xb3


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    Wdf01000!FxPkgFdo::DispatchDeviceSetPower+b3
    fffff880`00e91623 cc              int     3

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  Wdf01000!FxPkgFdo::DispatchDeviceSetPower+b3

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Wdf01000

    IMAGE_NAME:  Wdf01000.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  5010aa89

    FAILURE_BUCKET_ID:  X64_0x10D_d_Wdf01000!FxPkgFdo::DispatchDeviceSetPower+b3

    BUCKET_ID:  X64_0x10D_d_Wdf01000!FxPkgFdo::DispatchDeviceSetPower+b3

    Followup: MachineOwner
    ---------

    Ive been researching loads of forums for hours on ends no luck :( Any help is greatly appreciated!

    Thanks

    Sunday, December 30, 2012 11:35 PM

Answers

  • The driver that appears to be causing the crash is the libusb0.sys:

    BugCheck 10D, {d, fffffa80062ecc70, fffffa8003c6d290, fffffa80062d6e40}

    *** WARNING: Unable to verify timestamp for libusb0.sys
    *** ERROR: Module load completed but symbols could not be loaded for libusb0.sys
    Probably caused by : libusb0.sys ( libusb0+288a )

    2: kd> lmvm libusb0
    start             end                 module name
    fffff880`0931b000 fffff880`09324000   libusb0  T (no symbols)          
        Loaded symbol image file: libusb0.sys
        Image path: \SystemRoot\system32\drivers\libusb0.sys
        Image name: libusb0.sys
        Timestamp:        Tue Mar 20 06:33:00 2007 (45FFB85C)
        CheckSum:         0000DADF
        ImageSize:        00009000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    Sane error and driver in the following link:

    http://answers.microsoft.com/en-us/windows/forum/windows_xp-system/blue-screen-of-death-everytime-i-shutdown-windows/7109063c-82a7-43bf-aa0f-3b7541b910de

    So try updating or, if necessary, uninstall the libusb software.

    Also, you appear to be using an older version of WinDbg (6.12.0002.633) which may not have the improved logic of newer versions.

    • Marked as answer by tracycai Tuesday, January 1, 2013 6:51 AM
    Monday, December 31, 2012 6:59 PM
  • Updating failed, ive uninstalled...PERFECT! Can't thank you enough!
    • Marked as answer by tracycai Tuesday, January 1, 2013 6:51 AM
    Monday, December 31, 2012 7:14 PM

All replies

  • Anyone?
    Monday, December 31, 2012 5:46 PM
  • I am having the exact same problem!!! 
    Monday, December 31, 2012 5:49 PM
  • Can you zip up the minidump files in the C:\Windows\Minidump folder and make available (provide link) via Windows Live SkyDrive or similar site?

    The following link has information on using Windows Live SkyDrive:

    http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

    If you have problems zipping the minidump files copy the minidump files to another location such as a folder on the Desktop

    Also, you do not necessarily have to zip up the minidump files, you can upload them one at a time.

    Monday, December 31, 2012 6:00 PM
  • https://skydrive.live.com/redir?resid=D14D75D759E79171!146

    Thanks for replying.

    Monday, December 31, 2012 6:39 PM
  • The driver that appears to be causing the crash is the libusb0.sys:

    BugCheck 10D, {d, fffffa80062ecc70, fffffa8003c6d290, fffffa80062d6e40}

    *** WARNING: Unable to verify timestamp for libusb0.sys
    *** ERROR: Module load completed but symbols could not be loaded for libusb0.sys
    Probably caused by : libusb0.sys ( libusb0+288a )

    2: kd> lmvm libusb0
    start             end                 module name
    fffff880`0931b000 fffff880`09324000   libusb0  T (no symbols)          
        Loaded symbol image file: libusb0.sys
        Image path: \SystemRoot\system32\drivers\libusb0.sys
        Image name: libusb0.sys
        Timestamp:        Tue Mar 20 06:33:00 2007 (45FFB85C)
        CheckSum:         0000DADF
        ImageSize:        00009000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    Sane error and driver in the following link:

    http://answers.microsoft.com/en-us/windows/forum/windows_xp-system/blue-screen-of-death-everytime-i-shutdown-windows/7109063c-82a7-43bf-aa0f-3b7541b910de

    So try updating or, if necessary, uninstall the libusb software.

    Also, you appear to be using an older version of WinDbg (6.12.0002.633) which may not have the improved logic of newer versions.

    • Marked as answer by tracycai Tuesday, January 1, 2013 6:51 AM
    Monday, December 31, 2012 6:59 PM
  • I have read this before, i tried updating before with no luck. I will try again. 

    Thanks

    Monday, December 31, 2012 7:06 PM
  • Updating failed, ive uninstalled...PERFECT! Can't thank you enough!
    • Marked as answer by tracycai Tuesday, January 1, 2013 6:51 AM
    Monday, December 31, 2012 7:14 PM
  • You're welcome.
    Monday, December 31, 2012 7:26 PM