Sandy Bridge 2500k Just Died

[lollyhayes]

Looks like my 2500k is dead... 4 days of use, now it doesn't even make it into windows without locking up...
locks up on windows load up. Windows repair locks up.
Tried to use another HD and install windows on that. Locks up...
Looks like these might be duff, another guy with a d2 stepping 2500k had his die...
Any ideas on a way to test with only around 30sec before lockup when started?
Trying to underclock now...

 

[lollyhayes]

managed to get it to boot @ 1.6Ghz the lowest multi setting... Intel diagnostic turns nothing up... aside from stating it is running at 1.6ghz...

 

[lollyhayes]

running at 26 degrees on full load when I booted it at 16multi. No prob on the temps...
was running a Vcore within the spec, well within the spec, rolled it back today after hearing someones died. 1.080v when at 16multi (as per Vid)...
ok managed to boot it @ stock 3.3 ghz but even though turbo is allegedly on. Under prime95 its stuck at 3.3ghz so no turbo...
Wont boot if I set turbo to enabled (not auto - where it is apparently shut off)...
Trying individual cores as suggested...

 

[lollyhayes]

single core - boots @ 3.3 as before, turbo enabled - wont boot, turbo set to auto boots to windows no turbo on prime...
continuing to try cores... Also will try upping TDP limit (from auto to 95w in bios).

 

[lollyhayes]

same for othe cores... looking into the tdp

 

[lollyhayes]

didn't buy it from here btw... just letting you guys know. think I'm gunna take it up with the guys I bought it off...
Will keep you posted...

 

[lollyhayes]

it sounds, and I can't really believe it, like its very unstable at stock...

 

[lollyhayes]

no memory errors in memtest, just finished running

 

[lollyhayes]

I think sandybridge is very very fragile chip! Had to be more careful when overclocking exspecially vcore voltage

seconded

 

[lollyhayes]

This thread is getting linked from various places, but is there actually other reports of this? Only thread I can find on "2500k died" or variations is this one.

Also "was running a Vcore within the spec, well within the spec at 4.8ghz" sounds a bit clandestine. What vCore were you actually running?

 

[lollyhayes]

guys, I have got the cpu back again albeit at 1.38vcore. I think the advice Gibbo is giving is good, and I have booted my ram (rated 1.65) at 1.5v with no ill effects... I am also running it at 1.6v now but only because it rules out the ram as a source of the problem whilst I prime95 the CPU...
I think maybe this thread should be re labelled as it now gives a false interpretation of the current status of the CPU.
So far there has only been one failure (in another thread of this forum) which was the IMC, my problems are liekly simply to be due to my overvolting @ 4.8ghz. Which whilst they lasted for a short duration may have imapacted on the subsequent performance of the processor... Who knows...
I will post a screenie of Vcore, temps and prime95 results in a few hours.

 

[lollyhayes]

I just been contact Intel customer support and they say both i5 and i7 2500 and 2600 chip must NOT go over 1.380v in the bios and the memory volt must NOT go over 1.65v and that's the safer one!

looks like I guessed spot on then...

 

[lollyhayes]

WTF "Sandy Bridge 2500k Just Died'.

How about changing the title because if it really died it wouldn't now be working. Sounds more like a BIOS fubar.

if you read back I requested it... when I got the CPU working again 1st or 2nd page