Random BSOD and Programs CTD on a new build.

dudear · 08 May 2012

Hi, I've built this pc from scratch, everything was running smooth but then I had to install MacOS in a partition in order to access to some Final Cut projects I had. I've already done a few dualboots with no problem at all (Windows XP and Ubuntu). But during this installation something went wrong (it crashed) and I ended up reinstalling Windows 7 again to get a clean install and forget about the dualboot.

Now, I'm experiencing some random crashes to desktop not only from games or intense resource programas like Adobe Premiere but also programs like Utorrent, Firefox, Iexplorer and even with BSOD sometimes.

My system is not OC, I already ~~tried leaving~~ left the default values at BIOS.
The core I5 temps are around 30C and go no higher than 40ºC.
I've already done a chkdsk and everything was ok.

Any help would be greatly appreciated and if I'm missing any information please let me know and I'll update this.

System Specs.
OEM Windows 7 Home Premium 64bit
Intel Core I5 2500K Gigabyte Z68-AP-D3
Corsair Vengeance 8 GB (2X4 GB) PC3-12800 1600mHz DDR3
SAPPHIRE AMD Radeon HD 6870 1GB GDDR5
Western Digital Caviar Blue 500 GB SATA III 7200 RPM 16 MB Cache X2 (in raid)
Corsair Enthusiast Series 650-Watt 80 Plus
Cooler Master Hyper 212 Plus 120mm Sleeve CPU Cooler

Thanks,
Dudear.

zigzag3143 · 08 May 2012

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

*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

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/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"
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 JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table (DRT)

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

Driver Verifier

Using Driver Verifier (Windows Drivers)

dudear · 08 May 2012

Thanks for the answer, (just to clarify I did not OC the system, I did not expressed myself correctly before).
I'm goint to give this solution a try and let you know tomorrow.

zigzag3143 · 08 May 2012

dudear said:

Thanks for the answer, (just to clarify I did not OC the system, I did not expressed myself correctly before).
I'm goint to give this solution a try and let you know tomorrow.

good luck

dudear · 08 May 2012

I did as you suggested, now I have the driver updated but... I think the issue was one faulty ram stick. First I ran the test with both sticks, got errors. Ran it again with the 1st stick, errors again. But luckily the second stick was working correctly. I know it may be too early to tell (because I didn't complete the test up to pass 7) but it's working correctly and really stable now. Guess I'm gonna have to buy a new one.

Thanks again.