Solved BSOD playing Shank... on multiple occasions; error 0x0D1

[Noober2029]

Hey guys, I'm new here, but I need some assistance..
Just last week, I built this computer to play newer games. However, sometimes when I'm playing games such as Shank, I'll receive a random BSOD error (see title). I took the steps needed to report to you guys the errors, and they're attached to this thread. I updated this Bios to 1.20 (from 1.0), and I also ran windows update for the latest drivers. Appreciate any help I can get on this one!

System Specs:
AsRock 880GM-LE FX running 1.20
Ripshark 8gb RAM (1333Mhz)
Corsair 300W PSU
AMD Phenom II X4 3.4Ghz
Windows 7 Ultimate x64 (Full Retail)
Just recently installed windows (2 days ago), after building the computer about a 5 days ago.

 

[JMH]

These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html






Driver Verifier

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation"IRP Logging and Force Pending I/O Requests. and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table (DRT)

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[Noober2029]

These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html






Driver Verifier

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation"IRP Logging and Force Pending I/O Requests. and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table (DRT)

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

Thank you for the hasty reply, JMH!
I'm happy to say that I've already ran a memtest for about 4.5 hours and after about 6 passes (if my memory serves me right) there were no errors!
However, after doing the driver verifier, I've come to the conclusion that the Mijxfilt.sys is the culprit! I'm not TOO deep into IT knowledge, but I know enough to assume that this is due to the program "Motioninjoy", and must be uninstalled, correct?

 

[zigzag3143]

Motionjoys DS3_tool is causing a driver framework error. I would remove motionjoy and update these two drivers

Rt64win7.sys    2/26/2009 5:04:13 AM        fffff880`02c00000    fffff880`02c32000    0x00032000    0x49a65b0d                        
xusb21.sys    4/8/2009 10:28:44 AM        fffff880`059bf000    fffff880`059cfd80    0x00010d80    0x49dcb49c

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
Driver Reference Table (DRT)

 

[Noober2029]

Motionjoys DS3_tool is causing a driver framework error. I would remove motionjoy and update these two drivers

Rt64win7.sys    2/26/2009 5:04:13 AM        fffff880`02c00000    fffff880`02c32000    0x00032000    0x49a65b0d                        
xusb21.sys    4/8/2009 10:28:44 AM        fffff880`059bf000    fffff880`059cfd80    0x00010d80    0x49dcb49c

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
Driver Reference Table (DRT)

Thanks for the help as well, Zig! I've successfully updated both of those drivers.. But does this also mean that there's no way I can use the DS3 tool now? Because I'd like to continue using my controllers to play my games! Either way, thank you guys for your help. This is a great community you've got here!

 

[zigzag3143]

Your call on DS3. Maybe there is a newer version, a patch, etc. If the driver date is before June 2009, you may be able to use it by installing it in compatibility mode


To install an older driver in win 7 you need to install it in compatibility mode.


To install in compatibility mode right click the installer, go to properties, then compatibility. Choose the appropriate OS


http://www.sevenforums.com/tutorials/316-compatibility-mode.html?ltr=C

 

[Noober2029]

When I went to reinstall DS3, I found out that the version I was using was actually a beta version. I reverted to the older, (and more stable version, I might add), and found that playing Shank has yet to give me a BSOD! Hopefully it'll stay like that, but either way, thanks man. It's appreciated.

 

[zigzag3143]

When I went to reinstall DS3, I found out that the version I was using was actually a beta version. I reverted to the older, (and more stable version, I might add), and found that playing Shank has yet to give me a BSOD! Hopefully it'll stay like that, but either way, thanks man. It's appreciated.

Good luck and if/when you feel it is solved please use the red triangle and ask this thread be marked solved.