BSOD happened 5 times in one hour for a 4 monthes old pc

Hi,
I built my own desktop 4 monthes ago with windows 7. The BSOD started to happen after I installed a new Microsoft LifeCAM. But not sure this is a real casue for this issue. Recently BSOD happened more often than before. As today it happened 5 times in one hour. I ran the memory test (Memtest86+) and did not get any errors after 8 passes. Also I unplugged all the USB ports from the PC. But BSOD seems never give up. Here is my PC hardware configuration list. Please let me know if you need anything more from me. I am pretty frustrated with issue right now since I never have this kind of experience before.
thanks in advance.

- Windows 7 Ultimate x64
- Full Retail Version
- Intel core i5-2500k@3.3GHz
- ASUS P8P67 PRO
- Kingston Hyper X 8GB (2x4GM) 1600MHZ DDR3 Non-ECC C19 DIMM
- NVIDIA GeForce GTX 460 SE
- OCZ Stealth X Stream2 600W
- SAMSUNG SyncMaster T240

pennster said:

Hi,
I built my own desktop 4 monthes ago with windows 7. The BSOD started to happen after I installed a new Microsoft LifeCAM. But not sure this is a real casue for this issue. Recently BSOD happened more often than before. As today it happened 5 times in one hour. I ran the memory test (Memtest86+) and did not get any errors after 8 passes. Also I unplugged all the USB ports from the PC. But BSOD seems never give up. Here is my PC hardware configuration list. Please let me know if you need anything more from me. I am pretty frustrated with issue right now since I never have this kind of experience before.
thanks in advance.

- Windows 7 Ultimate x64
- Full Retail Version
- Intel core i5-2500k@3.3GHz
- ASUS P8P67 PRO
- Kingston Hyper X 8GB (2x4GM) 1600MHZ DDR3 Non-ECC C19 DIMM
- NVIDIA GeForce GTX 460 SE
- OCZ Stealth X Stream2 600W
- SAMSUNG SyncMaster T240

These are related to memory management caused by your Symantec. I would remove and replace it with Microsoft Security Essentials

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

Virus, Spyware & Malware Protection | Microsoft Security Essentials


I would also run these two tests.




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.

RAM - Test with Memtest86+



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.

Driver Verifier - Enable and Disable

zigzag, thanks for your quick response. I have run the memory test early this morning and it passed 8 runs. I will run the driver verifier. Meanwhile I will uninstall the norton. Thanks again.

pennster said:

zigzag, thanks for your quick response. I have run the memory test early this morning and it passed 8 runs. I will run the driver verifier. Meanwhile I will uninstall the norton. Thanks again.

Just un-installing Norton might do the trick and verifier can take a while. Might want to wait and see.

pennster said:

zigzag, thanks for your quick response. I have run the memory test early this morning and it passed 8 runs. I will run the driver verifier. Meanwhile I will uninstall the norton. Thanks again.

My pleasure and good luck

hi, I uninstalled the Norton and installed the MSE. Also I enabled Driver Verifier but still got BSOD. Do I need to attach the same error report or something else for you guys to review? really appriciate your help.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2052
Additional information about the problem:
BCCode: c1
BCP1: FFFFF9801D848C10
BCP2: FFFFF9801D8483D6
BCP3: 0000000000E103E8
BCP4: 0000000000000023
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

pennster said:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2052
Additional information about the problem:
BCCode: c1
BCP1: FFFFF9801D848C10
BCP2: FFFFF9801D8483D6
BCP3: 0000000000E103E8
BCP4: 0000000000000023
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

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.

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.