Consecutive BSOD now occuring almost once a day, help appreciated

fastalan · 22 Feb 2012

Hello

I have been experiencing frequent BSOD issues with my server computer. Recently, the problem is occurring at least once a day and since this is my main work computer, I am starting to get very worried. The dump file and system report have been uploaded per forum instruction.

System Information
OS: Windows 7 Professional 64 bit
Microsoft SQL server 2008 R2 Installed
OS: Microsoft Virtual PC installed with one XP running mostly legacy accounting softwares
CPU: AMD Phenom II 1090T stock speed stock fan
CPU temp: I use core temp, 25c idle rarely over 40c.
Mobo: MSI 890FXA-GD70 (original shipped firmware v1.7, not updated due to numerous horror stories bricking this mobo after firmware update)
Memory: Kingston value ram 12GB
Main HD: 120GB Intel 320 SSD (25GB space left)
Add HD: two 500GB HD running Windows 7 mirror
one more 500GB HD
Video Card: ASUS EAH4350 silent with latest driver from AMD site
Power Supply: 750W Corsair with APC battery back up
Lan Card: using 1/2 lan port on the mobo plus one Intel Lan card
USB 3.0 card reader - I got this in Taiwan during Computex, local brand, it doesn't have driver, just plug and play, have been using is for over 6 months w/o problem.
Anti Virus - Norton Internet Security
SQL Database - I run an eBay desktop selling program called Blackthorne Pro, this is the main reason for installing the SQL server 2008.

What I have done so far:
1) Updated video card driver (I also back date driver but still BSOD)
2) Pulled out and re-inserted all 4 ram sticks
3) We have two computers using EAH4350 card, swap them, but still BSOD on the Win 7 machine, the other machine has no problem.
4) The computer case is cleaned and vacuumed on a regular basis, there is no heat problem, room temp 17-18C during winter (I am in Canada). There are two case fans and one extra slim fan cooling the hard drives.

The last physical upgrade was adding an extra stick of RMA a few months ago but I could not remember exactly which one it was.

It seems to me the video card always went crazy with all colors going mad for about 1 second before each BSOD.

Some helps in diagnosing the dump file will be most appreciated.

Regards,
Alan

zigzag3143 · 22 Feb 2012

You uploaded the app instead of the data. Try this method

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

fastalan · 22 Feb 2012

Thanks so much for getting back to my message. I have attached the correct DMP file this time.

zigzag3143 · 22 Feb 2012

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

RAM - Test with Memtest86+

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.

Symantec is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST

http://us.norton.com/support/kb/web_...080710133834EN

Microsoft Security Essentials - Free Antivirus for Windows