Random Bsod

Yes its all DDR2 800mhz Apacer.I was using KINGSTON and A-DATA before but i had the same problems.

shaylol said:

Yes its all DDR2 800mhz Apacer.I was using KINGSTON and A-DATA before but i had the same problems.

Have you run memtest?

Yes did 8-10 PASS on each stick - no errors.

shaylol said:

Yes did 8-10 PASS on each stick - no errors.

Great we can move on.

If not hardware/ram might be a driver corruption same. Driver verifier usually will find those.

Run it yet?


If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


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.

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


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users[/B]

Uhm i said in the previous posts that i was using driver verifier for more than 20 hours without errors.And im not overcloking.Is it possible to be other hardware than ram ?

shaylol said:

Uhm i said in the previous posts that i was using driver verifier for more than 20 hours without errors.And im not overcloking.Is it possible to be other hardware than ram ?

Sorry too little sleep too many posts. It certainly can be mobo slot, voltage, power, heat, the usual suspects.

Does it do it in safe mode (F8) with networking?

Does it crash with all the USB (but keyboard, mouse) removed?

Has it always done it, or if it recently started, was new software, or hardware, added?

No problems :) Well it doesnt do it in safe mode and it crashed once with all usbs removed.It started with bsods like year ago when i started using all ram slots.I changed the ram cause it was giving errors and it was ok for a month then it started again.

shaylol said:

No problems :) Well it doesnt do it in safe mode and it crashed once with all usbs removed.It started with bsods like year ago when i started using all ram slots.I changed the ram cause it was giving errors and it was ok for a month then it started again.

You changed the ram but the mobo slots are the same. Could be either.

is there a way to check if the mobo slots are working fine?And also when i do Aida64 stress test it fail on Stress cache with "hardware failure" message.

shaylol said:

is there a way to check if the mobo slots are working fine?And also when i do Aida64 stress test it fail on Stress cache with "hardware failure" message.

By inference, you can check the mobo slots using a known good stick of ram. In a good slot it will work a bad one wont.

Makes sense Aida will report that.