BSOD During Diablo 3. BCCodes such as "124, 50, 3b".

[Surrender]

Hey guys. I'm running a new build I got about a month ago. I wanted to buy a new computer for D3 (needed a new one anyways), but I wasn't confident to build a computer by myself. So the company I bought it off allowed me to choose the parts and they would build it and test it for me provided I paid the small fee.

Everything was good when it came, and it has been since, however recently I've been getting these BSOD errors with the codes I put in title. After googling I saw that it's a possible hardware, so I wanted to make sure so I ended up here. I found this only happens while playing Diablo 3.

I've reinstalled Windows 7 once.
I'm running Windows 7 x64 OEM.

4(2x2)GB DDR3 1333(PC3 10666) Mushkin Ram, Radeon HD 6770, AMD Phenom II X4 965

Dump's are in there, so is the System health report.

 

[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)

 

[Surrender]

I haven't done DriverVerifier yet, but I have done Memtest86+.

Today I tried Memtest86+ with BOTH ram sticks in. I got lots of errors. So I removed Stick in slot 2. I restarted Memtest with Stick #1 in slot #1 and let it run for 6 passes, and there was no errors. I then put the stick in slot 2 and did it again for 6 passes, and did with no errors.

I haven't tested stick 2, but i'm assuming it's no good?

Is it possible my BIOS needs updating? The current version of my BIOS is 17.5. And on MSI's website, there's an update to 17.9 for my motherboard. And one of it's features are "- Improved memory compatibility." Could this be a solution or impossible?
http://www.msi.com/product/mb/760GM-P21--FX-.html#/?div=BIOS

 

[zigzag3143]

Does seems like stick 2 is suspect. Your BIOS is currently 2011,m and there is (as you know) one newer. If you decide to update be sure to make a restore point.

BTW the active application in 2 of 3 crashes has been audiodg.exe. It is a known problem and updating the BIOS might help this as well.