Sandy 2500K Or Asus P8P67 Pro looks to be dying

On the off chance, I just tried installing Windows XP Pro 32bit and its installed.
The only change to the bios was to set SATA to IDE mode to avoid install driver issues.

Just installing the Intel Diagnostics and will run that.
Then I will try installing each of the Asus / Intel drivers one at a time to see what and if makes if fail.
 
INTEL DIAGNOSTICS FAILED :(

It's definatly the CPU


--- Reading Integrated Memory Controller Frequency ---
Expected IMC Frequency is --> 6046663130289808
Detected IMC Frequency is --> 1236704
Integrated Memory Controller Speed Test Fail. Expected: 6046663130289808 Detected: 1236704
--- Reading Integrated Memory Controller Frequency ---
Expected IMC Frequency is --> 6046663130289808
Detected IMC Frequency is --> 1236704
Integrated Memory Controller Speed Test Fail. Expected: 6046663130289808 Detected: 1236704
--- Test End Time: 01/01/2005 12:45:51---
 
Wow.:eek: SB does overclock higher and cooler but also very fragile. Hope this is just a one off, QC slip, otherwise, these forum will be be inundated with similar issue.:confused:
To the OP, try RMA'ing thru OcUK first before going to Intel.
 
Why are people so surprised?? The 32NM process is known to be more fragile than the 45NM process used to make the previous socket 1156 and 1366 processors.

I remember a Pentium G6950 went kaput when it was overclocked by Tom's Hardware.
 
Bad times, sorry to hear you got a duff chip. Intel suggest 1.52 volts as a maximum, so you were well under that so shouldn't effect your rma. There's always bound to be duff chips in a new technology, OCUK will be prepared for this.

Fwiw, my 2600k has clocked to 4802mhz at 1.39vcore, but have it 24/7 to 4.5ghz @1.275vcore with turbo and speedstep enabled.

These chips don't need much voltage, and will proibably hit 5ghz with 1.4vcore or less, with the correct bios settings.
 
Bad times, sorry to hear you got a duff chip. Intel suggest 1.52 volts as a maximum, so you were well under that so shouldn't effect your rma. There's always bound to be duff chips in a new technology, OCUK will be prepared for this.

Fwiw, my 2600k has clocked to 4802mhz at 1.39vcore, but have it 24/7 to 4.5ghz @1.275vcore with turbo and speedstep enabled.

These chips don't need much voltage, and will proibably hit 5ghz with 1.4vcore or less, with the correct bios settings.

But Simon only went up to 1.4v :( he wasn't really pushing the volts very high and it has failed by the looks of it. We'll see in a few months if there have been a slightly higher number of failed CPUs I guess.
 
Long shot but have you checked the actual socket on the motherboard, for any bent / broken pins?

With it being within 28 days of purchase, I think they just replace the item in question . . . . .
 
Bad times, sorry to hear you got a duff chip. Intel suggest 1.52 volts as a maximum, so you were well under that so shouldn't effect your rma. There's always bound to be duff chips in a new technology, OCUK will be prepared for this.

Fwiw, my 2600k has clocked to 4802mhz at 1.39vcore, but have it 24/7 to 4.5ghz @1.275vcore with turbo and speedstep enabled.

These chips don't need much voltage, and will proibably hit 5ghz with 1.4vcore or less, with the correct bios settings.


source for 1.5v? thats higher than 45nm was and intel have not said what safe volts are as everyone is trying to find out.have intel said something?
 
INTEL DIAGNOSTICS FAILED :(

It's definatly the CPU


--- Reading Integrated Memory Controller Frequency ---
Expected IMC Frequency is --> 6046663130289808
Detected IMC Frequency is --> 1236704
Integrated Memory Controller Speed Test Fail. Expected: 6046663130289808 Detected: 1236704
--- Reading Integrated Memory Controller Frequency ---
Expected IMC Frequency is --> 6046663130289808
Detected IMC Frequency is --> 1236704
Integrated Memory Controller Speed Test Fail. Expected: 6046663130289808 Detected: 1236704
--- Test End Time: 01/01/2005 12:45:51---


It failed at all stock settings right ? Also you made sure to have the correct ram voltage set and the right timings ?

If you made sure of that, print off the INTEL DIAGNOSTICS results and send it back with the CPU... see it's a great program ;) it's saved me many times and spotted bad cpus. I always test all faulty intel pcs with it before I even carry on trying to troubleshoot. Happy it helped you track the problem now.

Next time just some advice don't overclock the pc until you have left it a couple of days running on and off (to allow the thermal paste to cure and allow the chip to get use to being used) then slowly start overclocking and only raise the overclock slowly one step at a time and leave it running few hours before each increase and NEVER go over what Intel specs for the max volts for that cpu.


RMA it with OCuk mate and send it back as faulty.. With the printout of Intels Diagnostics results as proof and add a printout of the BSOD you was getting under Windows 7 "the hardware failure error".. Also on the print out add the link to the intel test program so they can test it themselves. Any time I have had to RMA an Intel CPU with Intel they have asked me to run that program and send it with the failed report to them. As it's under a week since you purchased it send it back to OCuk, there will always be the odd bad component in a batch of electronics.



ALSO check your BIOS and set the correct date and time ;) it's not 2005 ;) "--- Test End Time: 01/01/2005 12:45:51---" re-run the test with correct time and date before printing out to send with CPU ;)
 
Last edited:
INTEL DIAGNOSTICS FAILED :(

It's definatly the CPU


--- Reading Integrated Memory Controller Frequency ---
Expected IMC Frequency is --> 6046663130289808
Detected IMC Frequency is --> 1236704
Integrated Memory Controller Speed Test Fail. Expected: 6046663130289808 Detected: 1236704
--- Reading Integrated Memory Controller Frequency ---
Expected IMC Frequency is --> 6046663130289808
Detected IMC Frequency is --> 1236704
Integrated Memory Controller Speed Test Fail. Expected: 6046663130289808 Detected: 1236704
--- Test End Time: 01/01/2005 12:45:51---

did you overvolt the memory controller? vccio? or push the memory voltage past 0.5v + vccio voltage as these can destroy cpus?
 
Sorry to hear about your problem Simon, I just ran the test on my 2500K, should I be worried? for the record I have not overclocked at all. other than the strange booting issue no problems and no BSOD

 
Sorry to hear about your problem Simon, I just ran the test on my 2500K, should I be worried? for the record I have not overclocked at all. other than the strange booting issue no problems and no BSOD


I had that with no base clock overclock. wouldn't worry...
Unless the onboard controller can tell when the BCLK has been pushed past 100, even if its in the past... Not sure thats possible though...

I just ran mine again, it fails on a clokc of 99.8mhz... And thne passes when its spot on the 100.0mhz BCLK... so wouldn't worry
 
Last edited:
The bsod code of 00124 means there is something wrong with the QPI/memory controller, looks like you have overvolted it or the board has "Auto over-volted" it, looks like you have a dead chip sir, unlucky son.

Now RMA it.
 
Back
Top Bottom