Random BSODs at idle and starting up

Hello, I've included as much information that I can think of about this problem. I've been getting random blue screens for months now at idle and while starting up. I saw a post about using Avast, which I was and have removed, and started using MSE.

When I removed it, my computer ran about 6 days straight with no problems so I thought maybe that fixed it. However, I had a BSOD this morning when I got up and have had about 3 more in just the last hour.

I do need to say that when I got this motherboard the IDE did not work. I didn't think much of it since I wasn't going to be using it. I know, I should have sent it back so that was my mistake.

You guys seem to really know your computer stuff so I'm hoping one of you can help me resolve this problem. If you need anymore information please ask and I will do whatever I can to get it. Thank you in advance.

P.S. The OS is about 6 months old and the rest of the hardware, except for the video card, is about 1 1/2 years old. The VC is around 10 months old. I've also tried updating and rolling back drivers without success.

brianlee1979 said:

Hello, I've included as much information that I can think of about this problem. I've been getting random blue screens for months now at idle and while starting up. I saw a post about using Avast, which I was and have removed, and started using MSE.

When I removed it, my computer ran about 6 days straight with no problems so I thought maybe that fixed it. However, I had a BSOD this morning when I got up and have had about 3 more in just the last hour.

I do need to say that when I got this motherboard the IDE did not work. I didn't think much of it since I wasn't going to be using it. I know, I should have sent it back so that was my mistake.

You guys seem to really know your computer stuff so I'm hoping one of you can help me resolve this problem. If you need anymore information please ask and I will do whatever I can to get it. Thank you in advance.

P.S. The OS is about 6 months old and the rest of the hardware, except for the video card, is about 1 1/2 years old. The VC is around 10 months old. I've also tried updating and rolling back drivers without success.

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


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.

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

Thanks for the quick reply Zig. One question, on the memtest when you run it from start up how long does it run for each pass? I've used memtest before but not from a bootable disk. From what I remember it just keeps running until you stop it. Is there a setting or anything I need to change for this?

P.S. I'm not overclocking anything either for additional information.

brianlee1979 said:

Thanks for the quick reply Zig. One question, on the memtest when you run it from start up how long does it run for each pass? I've used memtest before but not from a bootable disk. From what I remember it just keeps running until you stop it. Is there a setting or anything I need to change for this?

P.S. I'm not overclocking anything either for additional information.

You need to run it for abt 6-8 passes (will take a while). If any errors occur try testing one stick at a time.

So do I need to run the memtest with all my ram installed? From what you said earlier it sounded like I need to start off running them individually.

brianlee1979 said:

So do I need to run the memtest with all my ram installed? From what you said earlier it sounded like I need to start off running them individually.

Start with all of it. If it passes you are fine, if errors show run individual sticks to find out which one is bad. Use a known good stick in each mobo slot to determine if it is the ram, or mobo slot.

Ok will do, thanks for the help. I'll let you know how it turns out.

Well I ran the test with all 4 sticks of ram in and it immediately came up with errors. I narrowed it down and found there was a bad stick of ram. I just now started back up so I'll see how it goes. Thanks for the help Ziggy! Very much appreciated.

brianlee1979 said:

Well I ran the test with all 4 sticks of ram in and it immediately came up with errors. I narrowed it down and found there was a bad stick of ram. I just now started back up so I'll see how it goes. Thanks for the help Ziggy! Very much appreciated.

My pleasure and good luck

Hey Zig I enabled the driver verifier and it blue screened as soon as windows loaded up. The cause was vsdatant.sys associated with Zone Alarm. I know for a fact because after some reading I uninstalled ZA and everything is fine now. Is there anything that can be done where I can use ZA without having that problem?

I ask because I really like ZA and enjoy using it. I know other people have also had the same problem but not sure what has/can be done about it. Any help would be greatly appreciated.