Trying to shake the BSOD blues

[princly]

All,
First time post, but long time recipient the knowledge and expertise this forum has to offer.

This machine built appox. 1 year ago by a local custom builder began experiencing about 6 months ago unexplained and unexpected BSOD's seemingly unrelated to any particular computer function. Refusing to accept further BSOD's without attempting to correct, I've come here hopefully for final resolution and correction.

This system was custom built with Win 7 Home Premium x64 as original software.

I ran Memtest86 yesterday with both memory sticks in the two Mobo slots...1 mem stick tested well with 4 passes in each slot. Another mem stick threw 122+ errors in both memory slots early on in the test.

Attempting to resolve prior to purchasing new mem sticks, thought I'd submit the BSOD issues to this forum, what seems to be required new memory.

Please inform any missing info/spec info required. NT6 and perfmon files attached.

Best

 

[zigzag3143]

32 of 50 crashes were related to a memory issue.



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.

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

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html






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"IRP Logging and Force Pending I/O Requests. 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)

 

[princly]

Thanks Zigzag,
"I ran Memtest86 yesterday with both memory sticks in the two Mobo slots...1 mem stick tested well with 4 passes in each slot. Another mem stick threw 122+ errors in both memory slots early on in the test."

Should I re-run memtest with the 5-7 pass?

I'm familiar with the terms Overclocking and Raid, but frankly have no clue as to how to check if either or both are employed...can you advise?

Currently running Driver Verifier.

Best

 

[zigzag3143]

Thanks Zigzag,
"I ran Memtest86 yesterday with both memory sticks in the two Mobo slots...1 mem stick tested well with 4 passes in each slot. Another mem stick threw 122+ errors in both memory slots early on in the test."

Should I re-run memtest with the 5-7 pass?

If you are seeing errors you might want to run each stick independently so you can ID which stick is bad. If you find a good one test each slot with it.

I'm familiar with the terms Overclocking and Raid, but frankly have no clue as to how to check if either or both are employed...can you advise?

If you havent overclocked you self you are fine in this regard.

Currently running Driver Verifier.

Best

Good luck with verifier

 

[princly]

OK...ran Memtest86 again with both memory sticks independently in both slots. One stick in particular threw multiple errors in both slots, so new memory is on the way.

Driver Verifier created a few BSOD's while running...most were Stop Error A, but also a few others that may have been caused by memory. I have attached the most recent windows nt6 bsod jcgriff2 zip file. The BSOD's dated May 22 forward indicate the newer ones while Driver Verifier was running.

Also, I would like to revisit the question of Overclocking. Since I did not build this system, and the gentleman who did is not available, is there a reliable way to check if this was done on this system?

Thanks for hanging with me.

 

[zigzag3143]

OK...ran Memtest86 again with both memory sticks independently in both slots. One stick in particular threw multiple errors in both slots, so new memory is on the way.

Driver Verifier created a few BSOD's while running...most were Stop Error A, but also a few others that may have been caused by memory. I have attached the most recent windows nt6 bsod jcgriff2 zip file. The BSOD's dated May 22 forward indicate the newer ones while Driver Verifier was running.

Also, I would like to revisit the question of Overclocking. Since I did not build this system, and the gentleman who did is not available, is there a reliable way to check if this was done on this system?

Thanks for hanging with me.

The most recent ones which are verified seem to point to directX. More likely it is video related.

I doubt that you are overclocked and it doesnt appear you have a raid driver so I wouldnt worry about either of them.

Probably a good idea to wait for the new memory but in the mean time can you run a system file check.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7