BSOD playing LoL and minecraft, BCPcodes and other information inside

[thridy]

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80002C62AA7
BCP3: FFFFF880087CF5E0
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\030612-19531-01.dmp
C:\Users\Sam\AppData\Local\Temp\WER-63554-0.sysdata.xml

Additional Info:
Windows 7 64bit Professional (pre-installed, only OS)
8Gigs RAM
AMD Phenom II X4 955 Processor 3.20 GHz
AMD Radeon HD 6800 series graphics card (4863mb total)



I did some research myself and found that the BCCode (3b) relates to the GPU, but I was hoping I could get someone who knows what they are looking at to help me find the exact problem.

Many thanks!

 

[JMH]

These crashes were caused by memory corruption/exception (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 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 or 6 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.

So, 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).

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 "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- 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.

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.

 

[thridy]

Thank you very much for this information! I will run the RAM tests and update this post with my results.

EDIT: well that's odd. I did a total of 10 passes with memtest but it didn't discover a single error. Ill try taking out/reinserting my RAM and see if the problem persists.

 

[JMH]

You are welcome.
Good luck!

 

[thridy]

Well i'm blue screening again.This time the BCCode was 19 and the blue screen contained the text "BAD_POOL_HEADER". I think it relates to java as it said java stopped working right before the crash. Here's the minidump.

 

[zigzag3143]

Well i'm blue screening again.This time the BCCode was 19 and the blue screen contained the text "BAD_POOL_HEADER". I think it relates to java as it said java stopped working right before the crash. Here's the minidump.

Did you ever run verifier? This crash was not verified and still related to memory. Since you ran memtest we now need to find what driver is causing the problem.