BSOD playing games Wdf01000.sys

Dan581 · 25 May 2012

First off, the perfmon /report thing did not work, after a minute, it says "The way for the report generation tool to finish has timed out" right under "Error: An error occured while attempting to generate the report." If I click perfmon /report and run as admin, it doesn't give me anything I can save. I hope it's not a big deal. The BSOD happens while I am playing games, I think, it's only occured 3 times, twice was while playing games, and the 3 was forced because I used advice from this site and check driver verification, afterwards, it wouldn't start, it just went to the BSOD, so I booted into safe mode and and unchecked all of them, the first BSOD happened a couple days ago, and the major problem is I can't do a system restore because I don't have any resort points before the first BSOD, the only option I can think of now is uninstalling my entire OS which is definitely a last resort.

Edit: What are the chances that reinstalling my OS would fix this?

System Specs:
WIndows 7 Home Premium, SP1, ASUSTeK, Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz 2.00GHz
8GB RAM, 64-bit. The model is G53SX.

Vir Gnarus · 25 May 2012

The Driver Verifier crashes were caused by a false positive due to one of the checks you selected. Contrary to what the article says, there are two other checks besides Low Resource Sim you should also not check: IRP Logging and Force Pending I/O Requests. The latter is especially true for commonly causing false positives.

Anyways, the other bugchecks described a WDF driver violation caused by a bug in some driver. That driver is the Motionjoy MijXfilt.sys driver, which is commonly used for hooking up console controllers to the PC. You may be able to fix the problem by following this thread. You may need to forgo using Motionjoy, as this most likely isn't a driver conflict but just that there's a bug in this driver.

Dan581 · 25 May 2012

How would I go about checking to see if the changes I made fixed the problem?

Dan581 · 26 May 2012

Could you tell me which version of MotionJoy caused it?

writhziden · 28 May 2012

We can't give you a specific version number, but we can tell you the date of the driver. Would that be sufficient?

Vir Gnarus · 29 May 2012

Yah, as writhziden stated, details like file version aren't retained in memory for 3rd-party drivers, and that's because often those details are unnecessary and it speed things up a bit when you don't force it to save that info in the image headers. The only details that are retained for debugging purposes is the path of the file the image came from, the image (file) name, timestamp, checksum and image size, as well as some extra verification data.

The timestamp on this is May 12, 2012, so you may wanna either update again if available or back it up to an older version as a bug may have been written into this one. If necessary, contact the developer in their forums with this information to see if they can assist. You may be able to help them find a bug and therefore patch it up.