dead 2600k or asrock extreme4

My new system recently stopped booting, the fans spin up but it doesn't post.
I requested a new motherboard (asrock extreme4 p67) because it was recalled for the sata bug, but that shouldnt have anything to do with not posting.

I'm really hoping it's not my processor, but I don't know how to identify a dead processor as opposed to the motherboard.

The display on my mobo outputs error code "23" which means "OEM pre-memory initialization codes"

When I remove all my memory, I get the code that means no memory detected. I am guessing that since the memory controller is on the processor, if the proc was dead, it wouldn't be able to detect memory in the first place, but I have no idea...

any suggestions?

Thank you in advance for any insight you might have!

edit:
when I unplug cpu power, there is nothing on the readout, so I would assume a) cpu is getting power and b) cpu probably works
these are pretty big assumptions though

Personally, I have never had a cpu be "bad".

I would RMA the motherboard first and go from there.

Quote:

---

Originally Posted by gr1p

Personally, I have never had a cpu be "bad".

I would RMA the motherboard first and go from there.

---

+1, believe the same

So did you allready swap out your board for the new revision and havent been able to boot since or is this your original board that all the sudden doesnt post and you put in to swap your board now because of the sata bug?

Did you try reseating the cpu? Hat nearly the same issue, one of the pins didn't make proper contact it seems...

Newegg overnighted me the replacement board (new b3 one) and I have the same problem. I don't see how it could be a cpu pin, because it worked for 2 months without any problems.

I'm thinking it could be my memory (both sticks at the same time!?) or my cpu (which has the memory controller)

I suppose it could be a psu, but I think that would give me a different readout on the mobo :-(

cpu vcore?

Try switching out memory. And cmos reset your bios.

Ive reset the cmos several times, but seeing as ive now had the same issue on two boards, I dont think that would do anything. Ive also tried different memory combinations in different slots with no success. Going to try my memory in a friends computer later today

Quote:

---

Originally Posted by cakofony

Ive reset the cmos several times, but seeing as ive now had the same issue on two boards, I dont think that would do anything. Ive also tried different memory combinations in different slots with no success. Going to try my memory in a friends computer later today

---

try your CPU in different MB

Did an advanced rma with intel last night (called at 7pm) and the replacement was here at 10am (gotta love intel)

system works like a charm now ^.^
now I don't have to worry about the sata2 bug on the old chipsets either :-P

I was going to say I highly doubt its the Extreme4 as my Extreme4 even survived a fire in my PC yesterday and would of guessed either memory or CPU, but as your problem is resolved, theres not much point in this post :p:

Quote:

---

Originally Posted by cakofony

Did an advanced rma with intel last night (called at 7pm) and the replacement was here at 10am (gotta love intel)

system works like a charm now ^.^
now I don't have to worry about the sata2 bug on the old chipsets either :-P

---

Bad CPU?

Bizarre.

what Vcore were you using PLEASE???

I was running stock volts, oc to 4.4 with hyperthreading.
temps never hit 70. ever.

I've got the replacement running stock... I doubt the oc had anything to do with its premature demise, but I've never had a cpu die before... my q6600 ran at 3.6ghz (and well overvolted) for about 4 years, and its still running great

I think you are the first one to ever kill a 2600k :P

Quote:

---

Originally Posted by jstutman

I think you are the first one to ever kill a 2600k :P

---

i had the same issue with one 2600k

resetting the proc several times and adjusting the pressure of my heatsink solved the trick

the same issue? after a few months of working perfectly, it just stopped? and reseating it fixed it? thats really weird! I'll keep that in mind in case it happens again!