BSOD about 3-4 times a week. Not specific to any particular action

Dave76 · 31 Dec 2012

You probably won't notice the difference, I have a Hyper 212 plus and it's a great cooler. Recommended the evo because the plus is getting hard to find, for $10 the plus is a great bargain.

Those temps look good, what were you running to get the high temps?

That is the same RST driver I'm using, should be just fine, I've had no problems with it.

Run Data Lifeguard Tools 11 for DOS or Data Lifeguard Diagnostic for Windows on your hard drive.
How to create a Data Lifeguard diagnostics bootable CD.
Run the QUICK TEST and then the EXTENDED TEST.

Free Acronis True Image WD Edition Software is a great image backup program, if you need one, it's on the link above.

jbora · 31 Dec 2012

Alright I've ordered the 212+ and will probably have it installed in about a week. Do you still think it could be the fan even though the temps looked ok? To make the temps go up I opened a game (half life 2), spotify, and started playing like three HD videos on google chrome. I ran Data Lifeguard Diagnostics for Windows and my system passed both the extended and quick tests.

Dave76 · 03 Jan 2013

This will tell you if there is a motherboard problem, and you'll have a good CPU cooler if it is.

jbora · 11 Jan 2013

Alright so I have finally installed the Hyper 212 Evo (not +) and posted new temp readings. I was wondering if any voltages have to be adjusted since this is a new fan. Also I wanted to mention that since I adjusted the voltages I haven't had a single crash so that might have fixed the problem. However, as I previously mentioned, the VCCSA voltage number turned red when I adjusted it to 1.1. I was just wondering if this is something to be concerned about. I posted a pic of it from my bios. Thanks again for your time.

Dave76 · 11 Jan 2013

The red font is indicating a high voltage level, this is not an extreme voltage and most motherboards/BIOS don't consider this setting as high.

You can lower it a little at a time, test for stability, then lower again, test for stability, repeat until it crashes or run a stability test and when it fails then raise the voltage setting a little.

If you want to stress test the system you can run OCCT.
OCCT stability checking tool
Run the CPU:OCCT test for at least 30 minutes, be sure to monitor your CPU and GPU temps.
Set the time before you start.
When its done, pass or fail, it will make some graphs. Post these here as they are useful for analyses.
Post the first one for reference, then another if there is an issue.

Start with setting VCCSA to 1.050 volts.
Run OCCT stress test, if it fails you can increase the VCCSA to 1.070 volts.
If it passes you can lower the VCCSA to 1.030 volts.
At some point you can adjust by 0.010 volts.

Finial CPU:OCCT test should be ran for minimum 1 hour.

jbora · 12 Jan 2013

Alright I ran the stress test at 1.05 volts and it passed. It ended up giving me like 18 graphs. I wasn't sure if you wanted me to post all of them so I just attached the ones pertaining to temperatures. I saved the rest of them in case you do want me to post them. When I ran the GPU stress test it didn't give me any graphs but the hottest it got was 69 C so I think that's ok. I'm gonna continue adjusting the voltage and testing until I find a level I think works. I'll post my final hour long test findings when I think I've got it. Also, when I ran the GPU stress test I didn't check the "error checking" box. I think this is why I didn't get any graphs. When I do check it, however, it asks how much memory I wanna use. The default value is 60MB but it says it will go up to 2GB. Do you have any suggestions on how much memory I should use or if I even should do this test at all. Thanks again

jbora · 12 Jan 2013

Alright just had another crash. This time it happened right after I hit computer restart (I was getting ready to open BIOS and adjust the VCCSA down to 1.03 volts). Iv'e attached the logs and here are the problem details:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 4e
BCP1: 0000000000000099
BCP2: 00000000001A3D37
BCP3: 0000000000000000
BCP4: 00000000001A25B7
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Dave76 · 12 Jan 2013

Zip all the graphs and upload here.
Temps look ok.
For the GPU test use the max RAM allowed.

Stop code 4E is a memory crash.
Bump your VCCSA to 1.070 volts.
Run the CPU:OCCT test again for at least 30 minutes.

Code:

PFN_LIST_CORRUPT (4e)
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

Running OCCT for 30 minutes is just a quick stability test, not a long term 100% stable test. That will take longer and is done when everything is as close to stable as you can get it.
It's not unusual for OCCT to pass a short test and then get a crash on boot.
A couple of the stability tests that will need to be run when you get everything stable is memtest86+ for 7 full passes and Linpack or Prime95 torture test for several hours.

jbora · 13 Jan 2013

I ran the stress tests at 1.07 volts and everything passed ok. I'v attached all the graphs from the CPU and GPU (I found the ones from the previous test) stress tests for both 1.05 and 1.07 volts. I'm gonna run memtest tonight and do a torture test tomorrow. I'll post again tomorrow with the results.

Dave76 · 13 Jan 2013

Good news.
All the graphs look good.
Good test plan, let us know the results.