BSOD since windows 7 upgrade, usually error 3B

[joe369]

Since I upgraded from xp to windows 7 I have been getting the BSOD. It usually happens while I am doing something graphic intense (like playing a game), but also occurs while the computer is idle. I have tried everything i can think to fix it. I have done memtest, processor tests, HDD tests, and graphic card test. I have even tried a complete re install several times. I am pretty sure its driver related, but I can not figure out which driver it is.

I have:
Windows 7 Professional 64-bit
Intel core 2 duo E8500
Asus P5E3 pro motherboard
4GB DDR3 1600
XFX Radeon HD 4870
Kingston 64GB SSD
Seagate 500GB HDD
Thermaltake 500watt power supply

Any help would be greatly appreciated. Thanks!
View attachment 177967

 

[JMH]

JOE369,

At least 12 of these were caused by a memory exception.
Run these two tests to verify your memory and find which driver is causing the problem.


1-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.

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



2-Driver verifier

I'd suggest that you first backup your data 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" 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 (an estimate on my part).

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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[joe369]

Hey, thanks for responding JMH. I am confident it is not my ram because i have done memtest several times without error. i tried the driver verifier and finally got it to crash again. Should i repost the mem dumps? Recently the computer has started doing something slightly different. Instead of crashing completely, the graphics will crash, meaning the graphics card will stop outputting a signal and the computer freezes, but does not crash.

 

[JMH]

Submit any further Dmps for analysis.

 

[joe369]

View attachment 178440

 

[JMH]

* As a test does this happen in safe mode?

* Is this the same crash log (DMP) from the last time?
It is dated October 1, 2011 and the same advice still holds.

This error is often caused by a graphics driver passing bad data to the kernel.
Please re-install your graphics driver using this method.

When upgrading your graphic driver you MUST remove all traces of the current driver.
In order to do that we recommend using

Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

 

[joe369]

Hey, sorry it took me so long to reply, had a busy week. i do not know if the problem happens in safe mode as it only occurs when i am doing something graphically intensive, which i can not do in safe mode. My previous post should have contained the new dump file, but if it did not i re-ran the program and attached a new file below.
View attachment 179565
I tried the driver sweeper and re-installed fresh driver. However, while i was playing a game the graphics card stopped working and the computer froze up. i have yet to get it to crash, but i imagine it will only be a matter of time before it crashes again.

 

[JMH]

The DMP from 10/8/2011 still is related to a memory exception.
There are only three categories this can be > RAM, a driver, or the OS.

If you are that certain that your RAM is ok, and since driver verifier (which is sometimes an 'iffy' proposition) did not find the actual culprit.... lets have you try another test which is fairly short.

Please do the below >

* Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Let us know the results.

 

[zigzag3143]

After you have run the system file check suggested by JMH and reported the results I would like you to check event viewer to see if anything is logged there

There are several ways to find what the problem is. One of the best is to go into event viewer (type eventvwr in search). Please go to event viewer (local) and look for the critical errors listed in the last day, week, etc. Then go to the windows log>application tab. Finally the windows Logs>system tabs.

You want to look for critical errors (they have red in the left column ).

When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.

When you find them please note the event ID, and the source codes and tell us what they are.

We only need the the event ID and source codes not the whole log thanks

 

[joe369]

I ran the system file check you asked me to run and it did not find anything. I then looked through the event viewer and i did not find any that said app hang or app crash. All the critical lever ones were event ID 41 and source kernel-power. however, there were a lot of red errors, some that stood out to me were: source HAL event id 12, source bowser event id 8003, source disk event id 11, and source windowsupdateclient event id 20.

 

[JMH]

Suggest you do these..

* C-CHKDSK LogFile:

Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter

Expand the Windows logs heading, then select the Application log file entry.

Double click on the Source column header.

Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).

Copy/paste the results into your next post.

http://www.sevenforums.com/tutorials/433-disk-check.html

* * Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

* * * How to troubleshoot event ID 9, event ID 11, and event ID 15 error messages

 

[joe369]

Hey, i ran Prime95 for a while without error or warning. I also checked the eventlog and i could only find winlogon entries, which you wrote were fro windows xp, but i have windows 7. I don't know if that matters or not, but there were a lot of them all with event id 6000 or 4101. there were also three warnings, all with event id 6004. i looked at your link to how to troubleshoot those event ids from my previous post, but they all had different sources than the ones i have, i don't know if that matters of not.