Windows 7: BSoDs on random intervals

whisp · 05 May 2012

Greetings, everyone.

I have an issue that I believe You might be able to take care of or at least explain it to me. I've bought a new machine a while ago (6 months, I believe), built it from scratch with various components.
Since the beginning, I've been having weird BSoD problems.
For instance, I get to have like 5-6 BSoDs in a single day, then nothing for like 2-3 weeks, and then they start again. I do believe it's the hardware issue, but please check out all of the information provided and try to figure something out.

Attached You'll find zipped system report, jcgriff and minidump folders, as requested in the tutorial for BSoD problems.

System spec:

AMD Phenom x4 975, 3.6 ghz
4 GB DDR3, 1667 mhz
1 GB VRAM, ATI Radeon HD 6700
A cheap 1 TB hard drive (was buying the machine during those unfortunate events in hard disk factory)
Windows 7 Ultimate x64

Hope all of this information will be enough, and that you'll be able to, if not address, then at least identify the problem.

Best regards,

W.

JMH · 05 May 2012

whisp,

Lets see if this information can help you...

These crashes were caused by memory corruption/exception (Cx05) probably a driver.
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.
In other words STOP!!!

* If you have a Raid update its Driver.

Memtest.

Quote:

*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-7 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+

Driver Verifier

Quote:

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 stuff 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/Windows 7 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"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

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

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

Thanks to JGriff2 & Usasma.

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

whisp · 08 May 2012

Well, I did the Driver Scanner thingy and it seems like it worked. My Ethernet network card had, I quote, an "ancient" driver, so I manually updated that and no BSoD since then.

We'll see if they come back eventually, if this is just calm before the storm, but until then, it'll be nice to work normally on my computer.

Thank you, JMH, for kind and swift assistance.

Best regards,

W.

JMH · 08 May 2012

You are welcome.
When you are happy that all is well please mark your thread as solved.
Should you get any more BSOD's upload the DMP's here again.

whisp · 12 May 2012

I'll just mark this as solved, if any more BSoDs occur, I'll... be angry.
Thank you again.

Regards,

W.

JMH · 12 May 2012

Should any more occur you know where to find us.
Good luck!

Windows 7: BSoDs on random intervals

BSoDs on random intervals problems?