Sandy 2500K Or Asus P8P67 Pro looks to be dying

SimonMaltby · 11 Jan 2011 at 16:02

Purgatory said:
Starting to think your motherboard should have been RMAed at same time as your 2500K .. Nath did offer you to swap both the CPU and motherboard..

At the moment I don't see there being an issue with the motherboard it's just done 45 minutes of Prime (Bend) with ram volts at 1.45 - Now trying 1.425 and seems ok too. Nothing about it seems wrong other than the Intel test results.

Taking your advice this time and going to bed this chip in properly, taking my time to step up the over clock

I tried 1.6v on RAM and that did not solve the Intel test. I also disabled Speedstep,Turbo and the Asus Environment settings (as recommended in the Intel readme) made no difference still failed.

SimonMaltby · 11 Jan 2011 at 16:12

Purgatory said:
Dave ignore the Base Clock test Fail.. It will fail that because all motherboards seem to be slightly over the 100.

Yea edit the config and untick the Base Clock test. then please try again. Thanks.

SimonMaltby · 11 Jan 2011 at 16:19

Purgatory said:
Simon which of these RAM sticks did you use when testing?

Patriot PC3 - 19200 2400Mhz 2x2GB @2133 9,11,9,27 also OCZ PC3 12800 1600Mhz 6,8,6,24

Also did you try 1 stick test only ?

I'm currently using the OCZ @1600 6,8,6,24 1T 1.425v

SimonMaltby · 11 Jan 2011 at 16:21

dave_beast said:
Ok, now i've run it with bclk test disabled, and it's still fallen over
Integrated Memory Controller Speed Test Fail. Expected: 0 Detected: 0

Excellent.... Thanks Dave....

That is exactly what I get - well sometimes the second value is a big number but the actual is always 0 and it fails.
This means I'm quite happy that this CPU and Motherboard are fine.

Really appreciate your help

//Goes off to delete the stupid Intel test from his system LOL

SimonMaltby · 11 Jan 2011 at 16:32

matthab said:
Id say it has issues with your memory?

There is no problem with the memory. I'm 99% confident of that. As said, This is almost certainly an issue with the Intel software or the fact that the Asus motherboard does not conform exactly to Intel's specification or a combination of the two.

SimonMaltby · 11 Jan 2011 at 16:33

Purgatory said:
So far we proved in Simons case 1.4v on the core, raising the base clock and setting memory to 1.65v fried his previous chip.

Or I just had a bad chip!

SimonMaltby · 11 Jan 2011 at 16:35

dave_beast said:
Ok, disabled Base Clock Test and the Integrated Memory Controller test and passed but it still ran the Integrated Memory Controller stress test

Yea I got a pass if i disabled both.... but did not notice that it still did some IMC tests - good spot and also confused

SimonMaltby · 11 Jan 2011 at 16:37

I would also add to the mix that I did try the Asus 1053 Beta bios which includes some PLL overvolting to help D2 stepping CPU's overclock. This may be another factor, maybe combined with the others.

I rolled back to the last official 1003 before inserting this new chip.

SimonMaltby · 11 Jan 2011 at 16:39

dave_beast said:
I want to see what Overclockers say when they test it

It's only going back tomorrow, so they wont get it back to test until Thursday. I waited to send it back until i had confirmed that it was the chip and not the Motherboard. I have an RMA for both.

The guy's at OCUK have been brilliant i have to say.
Combined with the user support on the forum I could not have asked for more.

SimonMaltby · 11 Jan 2011 at 16:47

Justintime said:
Should have run the test on that dodgy 2600k i had. Same blue screen and general degradation until no POST, only difference is that it was not overclocked yet and about 3hrs old. Extremely fragile IMC?

You can't do much if it wont post. The faulty 2500K of mine will still post and works fine until the OS applies some driver or other. Now I can't say its the IMC its a real mystery to explain what is wrong with it. Although someone else did say the BSOD related to IMC.

Also now i think about it, several installers (including the Asus Suite) would not run when i installed XP... I think it was an error running kernal32.dll but cant be 100% sure. At the time i thought the files were either not XP comparable or corrupted... but I have installed the same files today on the new CPU in windows 7

SimonMaltby · 11 Jan 2011 at 16:52

If this experience reminds people to be more cautious and take their time while overclocking then it's all for the good.

When I started overclocking 14 or so years ago you had to work really hard to overclock.... Since Conroe its been rather easy and maybe we, me included, have become rather blasé.

SimonMaltby · 11 Jan 2011 at 18:34

coldfused said:
I'd put money on the RAM. OCZ are crap for their memory. I had 2 sticks of OCZ Platinum ram... it'd blue screen like hell. Stuck a pair of Geil's in there and I've not had a problem.
Now I use the OCZ ram in my 2nd computer.... that blue screens like a biatch lol

Could you borrow another stick of DDR3 ram to check/rule out?

I have OCZ and Patriot RAM both do the same.... But I stress again there is NO issue here with my new CPU. The Intel CPU Diagostic Software does not work with SB