Various BSODs, not sure why.

[Luxis]

- x64
- It is the original installed OS on the system
- Full retail
- My hardware is about 1½ years old.
- I once reinstalled my OS, and this was done perhaps almost a year ago.

I have had this computer since March 2010 I think, when I bought parts and built it myself. (First time doing this, with a bit of help though.) Ever since then I have had some problems with BSODs, sometimes almost once a day, sometimes not in several months, without showing any obvious pattern. I have had at least 10+ different error codes.

I am not too good with computers, so I am looking for someone to help me, and possibly tell me where the error is to be found.

 

[zigzag3143]

- x64
- It is the original installed OS on the system
- Full retail
- My hardware is about 1½ years old.
- I once reinstalled my OS, and this was done perhaps almost a year ago.

I have had this computer since March 2010 I think, when I bought parts and built it myself. (First time doing this, with a bit of help though.) Ever since then I have had some problems with BSODs, sometimes almost once a day, sometimes not in several months, without showing any obvious pattern. I have had at least 10+ different error codes.

I am not too good with computers, so I am looking for someone to help me, and possibly tell me where the error is to be found.

These crashes were caused by memory corruption. 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.

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



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

 

[Luxis]

I've tried memtest, ran several passes without any issues whatsoever. Now, if I am to proceed to step 2, I would like a more throughout explanation. How exactly am I supposed to find out what is causing the crashes? And if I dont, am I supposed to keep running it until I learn what does? What if I dont? Also, if I dont find the issue, can I somehow cancel it and enter the state I am in now?