OCCT Large Data Set Fails (defective CPU / RAM ?)

Oct 1, 2003
156
0
0
I built a budget PC for a friend to use casually and play WoW and Diablo 3 and this is the first time I've encountered something like this with all stock settings. I've overclocked my own computers successfully many times but I can't get this one stable no matter what, and this is all stock...

The system will pass memtest86 overnight as well as the small data set in OCCT. However it cannot pass the OCCT Large Data Set even with increased voltages and relaxed RAM timings. The system appears stable for the most part but it will occasionally lock up or blue screen so I know there is a problem. The error in OCCT is something like "error detected on core 0".

The specs are:

Asus P8H61-M LX PLUS
Intel G530
G.SKILL Ripjaws X Series 4GB (2 x 2GB) DDR3 1333

Now I know the processors memory controller can only support DDR3 1066 but the RAM was on sell. I have the RAM running at 1066 with the default timings assigned by the profile (something like 7-7-7-21) and whether I run those timings or DDR3 1066 @ 9-9-9-27 I still can't get it stable.

I'm thinking of trying different ram rated at 1066 and not 1333 maybe the Crucial stick on the Asus qualified list and seeing if this resolves the issue. But then why is it memtest86 stable? Is it possible to have a defective memory controller on the CPU? I've never had a defective CPU before.

Any insight would be greatly appreciated you guys have helped me out many times before.
 
Last edited:

Bubbaleone

Golden Member
Nov 20, 2011
1,803
4
76
If you run CPU-Z; under the SPD tab are the timings and voltage for XMP. Have you tested by manually setting the XMP timings and voltage, that CPU-Z lists, using the AI Tweaker? (the pic is just an example)

Wil6E.png
 
Oct 1, 2003
156
0
0
The timings and voltage are set to the XMP profile by default through the auto bios settings. I've tried with both XMP and manual looser timings both fail the OCCT Large Data Set. Sometimes it takes 5 minutes to fail and sometimes 2 hours. I've also tried 1T and 2T commant rates doesn't make a difference. I'm not sure what the bsod code is I haven't had time to mess with it more right now. I'm waiting on new ram to try that.