New
#1
BSOD while connecting controller via MotionJoy error 0x10D
I've had the same issue (at least I think its the same issue) a few months back, but this one seems to be a little more different. I had no issues with my laptop and the application, MotionJoy, for connecting my PS3 controller to my laptop in order to game until just this night. I played a new game that I have purchased (L.A. Noire) for a good few hours, absolutely no issues. I went to go eat my dinner, about 30 mins passed by. When I got back to laptop, I noticed my laptop had shut down by itself. This was clearly not normal as I never allowed my laptop to shut down, sleep, hibernate, etc. While plugged in. Immediately I knew something was wrong. I tried connection my PS3 controller again as I surprisingly saw that my game was still opened. I tried connecting my controller to my laptop with the MotionJoy app, and for some reason the app was working very funny and not as it was a few hours before I was about to play my game. Moments later, came the BSOD again, waiting for to stop dumping, a good couple minutes passed by, it wouldn't reboot, so I had to force shut down my laptop by holding down on the power button. Now here I am, ready to bawl my eyes out as I don't know a solution to this.
I ran the WhoCrashed app to get a diagnosis and this is what I got:
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 04/01/2013 3:07:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010313-66877-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x53B46)
Bugcheck code: 0x10D (0x5, 0x0, 0x1202, 0xFFFFFA800C5E8170)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Conclusion
--------------------------------------------------------------------------------
One crash dump has been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
--------------------------------------------------------------------------------
Is there another update that I missed by any chance?
Also last question, do this BSOD harm my computer? I know a couple do so.
Quote
