BSoD Stop Error Code 0x0000010D (Iunno what the cause is...)

Hello, peoples. I seem to have attained a BSoD yesterday.

The STOP Error code was "0x0000010D (0x00000005, 0x00000000, 0x00001202, 0x84E36560)".

I believe that one of the problems is MotioninJoy's DS3 Tool program and it's driver, as every time I attempt to use it, it BSOD's. I also believe that another problem is my PSU's fan, as it does not seem to be working anymore (I plan to buy a new PSU in April... Hopefully it'll last long enough til then...).

I have attached the zip file containing the system information, as per requested.

Any help will be appreciated.

Thanks in advance. :)

Hi Zero Aurion.

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Also, the BIOS is very old, off 2006. The latest available one is old too, of 2009. If possible, tryto update the BIOS to the latest. BIOS Update [NT94510J.86A]
_________________________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10D, {5, 0, 1202, 84e051a8}

Probably caused by : Wdf01000.sys ( Wdf01000!FxVerifierBugCheck+21 )

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

1: 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: 00000005, A framework object handle of the incorrect type was passed to
    a framework object method.
Arg2: 00000000, The handle value passed in.
Arg3: 00001202, Reserved.
Arg4: 84e051a8, Reserved.

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


BUGCHECK_STR:  0x10D_5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  DS3_Tool.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from 88a76aa7 to 82d1bbfc

STACK_TEXT:  
9ed73888 88a76aa7 0000010d 00000005 00000000 nt!KeBugCheckEx+0x1e
9ed738a4 88a59904 00000005 00000000 00001202 Wdf01000!FxVerifierBugCheck+0x21
9ed73aec 88a26c75 74617453 00000c76 88a21bf4 Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+0x69
9ed73b0c 7ab0fcb0 000000e5 00000001 00226004 Wdf01000!FxRequest::Release+0x2f
WARNING: Frame IP not in any known module. Following frames may be wrong.
9ed73b44 88a239d4 7ab0fcb0 9ed73b8c 854f0348 0x7ab0fcb0
9ed73b64 88a29397 85450500 00000000 854505e0 Wdf01000!FxIoQueue::DispatchEvents+0x4af
9ed73b84 88a23509 85450500 854f0348 84e03e74 Wdf01000!FxIoQueue::QueueRequest+0x204
9ed73bb8 88a2652e 86cf33f0 84ca4a58 86cf33f0 Wdf01000!FxPkgIo::Dispatch+0x3ba
9ed73be0 88a2639f 84ca4a58 86cf33f0 8548bbd0 Wdf01000!FxDevice::Dispatch+0x155
9ed73bfc 82c73c1e 84ca4a58 86cf33f0 86cf33f0 Wdf01000!FxDevice::DispatchWithLock+0x77
9ed73c14 82e67bf9 8548bbd0 86cf33f0 86cf3460 nt!IofCallDriver+0x63
9ed73c34 82e6ade2 84ca4a58 8548bbd0 00000000 nt!IopSynchronousServiceTail+0x1f8
9ed73cd0 82eb1779 84ca4a58 86cf33f0 00000000 nt!IopXxxControlFile+0x6aa
9ed73d04 82c7a8c6 000007ac 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
9ed73d04 76ea70f4 000007ac 00000000 00000000 nt!KiSystemServicePostCall
0012a684 00000000 00000000 00000000 00000000 0x76ea70f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Wdf01000!FxVerifierBugCheck+21
88a76aa7 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  Wdf01000!FxVerifierBugCheck+21

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Wdf01000

IMAGE_NAME:  Wdf01000.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51c50c11

IMAGE_VERSION:  1.11.9200.16648

FAILURE_BUCKET_ID:  0x10D_5_Wdf01000!FxVerifierBugCheck+21

BUCKET_ID:  0x10D_5_Wdf01000!FxVerifierBugCheck+21

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x10d_5_wdf01000!fxverifierbugcheck+21

FAILURE_ID_HASH:  {9e3004cc-c6e3-3103-bd11-b353464529ea}

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

In that case, dont attempt the BIOS update yourself. Ask anybody who can do it for you, or ask any PC technician. Remember that BIOS update is a critical job and any interruption during it will make the motherboard a brick only.

Zero Aurion said:

Eh, I did it myself. I used the express installer.

Zero Aurion said:

...I may not know some stuff, but I'm a complete noob when it comes to PCs. lol

May be it is the first step, and shortly you will be called a super computer geek.

Let us know about the other test, too.

Sephiroth! Like your new avatar!!

Now disable verifier use the computer normally. If there is any more BSOD, let us know :)