BSOD, Error 0x0000010d


  1. Posts : 2
    Windows 7 Home Premium x64
       #1

    BSOD, Error 0x0000010d


    Hi everyone,

    Can anyone help with diagnosing a BSOD problem that I have been having. It's been happening about 3-5 times a day now. It happens more often when I try to start and use Cubase 6 LE.

    As far as I can tell I've installed all the drivers necessary (nothing comes up as obviously missing in the Device Manager), all software and Windows Update is up-to-date.

    System spec:

    OS:Windows 7 Home x64
    CPU:Intel Core i7 950
    Motherboard: Gigabyte X58A-UD3R
    Graphics Card(s): GeForce GTX 480
    Screen Resolution: 1920 x 1200

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

    Additional information about the problem:
    BCCode: 10d
    BCP1: 0000000000000006
    BCP2:0000000000000003
    BCP3: 0000057f`fa0f3c98
    BCP4: fffffa80`05c72e40

    Using BlueScreenView I was able to get a little more additional information:

    Caused by driver: Wdf01000.sys
    Caused by address: Wdf01000.sys+7027

    I have attached the dmp file for the BSOD.

    I also performed memory and disk checks and every comes out fine.

    Can someone shed some light on what is happening and how to fix it?

    Thanks in advance,

    Justin
      My Computer


  2. Posts : 4,161
    Windows 7 Pro-x64
       #2

    It appears to be a programming error. The 0x10D is enacted by a Windows Framework Library as a result of a calling program that requested I/O back-to-back. Check to see if there is an update or patch for Cubase 6 LE.

    Code:
     
    BugCheck 10D, {6, 3, 57ffa0f3c98, fffffa8005c72e40}
    Probably caused by : Wdf01000.sys ( Wdf01000!FxIoTarget::SubmitLocked+cb )
    Followup: MachineOwner
    ---------
    7: 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: 0000000000000006, A fatal error was made in handling a WDF request. In this case,
     Parameter 2 further specifies the type of fatal error that has
     been made, as defined by the enumeration WDF_REQUEST_FATAL_ERROR.
    Arg2: 0000000000000003, The driver attempted to send a framework request that has
     already been sent to an I/O target.
    Arg3: 0000057ffa0f3c98, The WDF request handle value.
    Arg4: fffffa8005c72e40, Reserved.
    Debugging Details:
    ------------------
    
    BUGCHECK_STR:  0x10D_6
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    LAST_CONTROL_TRANSFER:  from fffff88000e5a027 to fffff800032c8fc0
    STACK_TEXT:  
    fffff880`0338f5b8 fffff880`00e5a027 : 00000000`0000010d 00000000`00000006 00000000`00000003 0000057f`fa0f3c98 : nt!KeBugCheckEx
    fffff880`0338f5c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Wdf01000!FxIoTarget::SubmitLocked+0xcb
    
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    Wdf01000!FxIoTarget::SubmitLocked+cb
    fffff880`00e5a027 cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  Wdf01000!FxIoTarget::SubmitLocked+cb
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: Wdf01000
    IMAGE_NAME:  Wdf01000.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  5010aa89
    FAILURE_BUCKET_ID:  X64_0x10D_6_Wdf01000!FxIoTarget::SubmitLocked+cb
    BUCKET_ID:  X64_0x10D_6_Wdf01000!FxIoTarget::SubmitLocked+cb
    Followup: MachineOwner
      My Computer


  3. Posts : 2
    Windows 7 Home Premium x64
    Thread Starter
       #3

    I updated Cubase 6 to its latest version, however it is still BSODing. Although it happens more often when I used Cubase, it still happens at other times. Could this be due to faulty memory or some sort of other hardware failure?
      My Computer


  4. Posts : 4,161
    Windows 7 Pro-x64
       #4

    Is it the same BSOD?

    Follow the instructions at the top of the page for posting BSODs and include the files from the "Grab All" option in the utility. We need the files to better diagnose the cause.
      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 08:07.
Find Us