Solved BSOD at random.

[myoblastic]

I've been having many BSOD's literally at random, and I can't figure out what's wrong.

Basic Specs:

-x64 bit
-Original Os (Win 7 Home Premium)
-OEM
-Less than 6 Months Old
-Custom Built

Hardware:

-MSI p67a-c43 mb
-i5-2400 CPU (stock cooling)
-8gb of Corsair Vengeance RAM
-OCZ ModstreamxPro 700w PSU
-Western Digital Caviar Black 500gb HDD
-Some cheapo DVD drive
-Nvidia GTS 450 Graphics Card

The crash report and system health report are attached, as it said I should do.

More Info:

The crashes are at random, sometimes I wake my comp from sleep and it crashes, I exit out of chrome and it crashes, etc.

I have done Windows Memory Diagnostics, and checked my drivers. What could possibly be wrong? (the crashes happen almost daily and the comp isn't important, but it's annoying)

Edit:
In the BSOD's, it says 'PFN_LIST_CORRUPT' or 'CRITICAL STRUCTURE CORRUPTION' or 'MODIFICATION OF CRITICAL SYSTEM CODE'. If I need to state the bug check code stuff, I will post it.

Edit2: I was just browsing through the forums... did anyone else actually follow the instructions besides me? lol.

 

[zigzag3143]

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.

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" 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)

 

[myoblastic]

I will try memtest and see if that pops up anything.

Edit: why isn't Windows Memory Diagnostic reliable? Also, is memtest 64 bit? It does not say. And I don't know this stuff.

But is there anyway to check drivers except driver verifier, because that seems dangerous.

Edit: And too much of a hassle.

Final Edit: I will mark this post as solved when the questions above are answered.

 

[zigzag3143]

I will try memtest and see if that pops up anything.

Edit: why isn't Windows Memory Diagnostic reliable? Also, is memtest 64 bit? It does not say. And I don't know this stuff.

But is there anyway to check drivers except driver verifier, because that seems dangerous.

Edit: And too much of a hassle.

Final Edit: I will mark this post as solved when the questions above are answered.

Windows diagnostic doesnt stress the memory to real life levels and it tests from within the windows environment.


With more than 10K analysis under my belt I have found less than 10 instances where we couldnt get the user working after verifier. It is after all built into the system and is the best way to test drivers.

 

[myoblastic]

Windows diagnostic doesnt stress the memory to real life levels and it tests from within the windows environment.


With more than 10K analysis under my belt I have found less than 10 instances where we couldnt get the user working after verifier. It is after all built into the system and is the best way to test drivers.

Thanks! I will come back if i have more problems. Marked as solved for now.

 

[myoblastic]

Just a few questions about memtest. I tested both my sticks of 4gb ram and got errors in the second stick. Removed the first stick and tested it. I didn't get any errors. So what do I do now?

(Marked as unsolved so people will actually read the post.)

 

[zigzag3143]

Just a few questions about memtest. I tested both my sticks of 4gb ram and got errors in the second stick. Removed the first stick and tested it. I didn't get any errors. So what do I do now?

(Marked as unsolved so people will actually read the post.)

Both sticks together mean it could be either. Then you have to test them one at a time in the same slot If one tests good and one bad chances are its the ram

Then take the known good ram and test each slot they all should be good.

 

[myoblastic]

But doesn't memtest tell you approximately which point in the ram it failed? Like mine failed around 6500mb, or in the second 4gb stick.

 

[myoblastic]

I gave up for a bit and decided to fix it at next crash. I reseated both ram sticks. Windows has been lasting for 1 1/2 days (not a long time, but not daily crashes.)

SIDE NOTE: My ram was rated at 1600mhz, but defaulted to 1333mhz in BIOS. I changed it to 1600mhz. Then in memtest, it reported it as XMP. Should that have been a factor? Should I change it back?

 

[writhziden]

Changing to XMP essentially overclocks the RAM, but if it is running stable now, that should be fine since it is actually designed to run in XMP mode. How is the system responding at this time?

 

[myoblastic]

Changing to XMP essentially overclocks the RAM, but if it is running stable now, that should be fine since it is actually designed to run in XMP mode. How is the system responding at this time?

It's been running completely fine after i reseated the RAM... I took them out, switched them, and put them back in. Although it is too early to tell if it is stable, it seems to be fine.

I actually am not sure if it swtiched back from 1600mhz to 1333 mhz in BIOS. But as long as it works, I'm too lazy and scared to change anything.

 

[writhziden]

I agree. If it ain't broke, don't fix it. Glad to see the thread marked solved at any rate.