Random BSOD in computer's start-up

[sharon122]

Well, yesterday like always I was at home, afternoon I needed to go somewhere, I was back in a couple of hours, turned on the PC and bam BSOD, I really don't know why because in the morning everything was just fine, the only think I remember is the details of the BSOD, something about registry.

Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? yes
- an OEM or full retail version? OEM
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? about 1 year+
- What is the age of OS installation (have you re-installed the OS?) yes, maybe half year already

 

[zigzag3143]

Well, yesterday like always I was at home, afternoon I needed to go somewhere, I was back in a couple of hours, turned on the PC and bam BSOD, I really don't know why because in the morning everything was just fine, the only think I remember is the details of the BSOD, something about registry.

Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? yes
- an OEM or full retail version? OEM
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? about 1 year+
- What is the age of OS installation (have you re-installed the OS?) yes, maybe half year already

These were caused by a memory exception. Please 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