Core i7 failure

Well, there's a first time for everything.  Actually had a CPU go bad on me.  Thought it was mobo for quite some time, didn't even consider CPU failure as an option.  Thank the Lord I had the spare lab box with another Core i7.  Little upgrade I guess...i7-920 to -950.  However, the CPU has a code that indicates 2008 manufacture, so might be out of warranty.

I'll be calling Intel tomorrow, so praying it'll be covered.  If not...no cheap to replace!

For anyone interested, the symptoms of the failed CPU are just this: System will no longer post, or show any video.  For all appearances it looks like a dead motherboard, or perhaps dead PSU.


update: Ah, was purchased in July 2009, so should be okay.

Constructive update:

Decided to post my troubleshooting process just in case someone isn't sure:
  1. System BSOD'd.
  2. I noted the BSOD error and codes via photograph, just in case they would help.  No drivers were mentioned in the BSOD, so chances are it's hardware.
  3. Once the memory dump completed (12GB of RAM takes a bit to dump), I reset the computer using the reset button.
  4. The PC would no longer boot - no video; monitors went into powersave, but still indicated they were connected.
  5. Immediately guessed motherboard was the issue, proceeded to colour my investigation with that assumption.
  6. Disconnected power and removed the SAS card, tried booting again.  Same symptoms.
  7. Disconnected power and removed all PCI cards (NIC, GPU, SAS), tried booting again.  Same symptoms.
  8. Got frustrated.
  9. Disconnected power and removed all RAM sticks, SATA cables, changed out GPU for a known good GPU, tried booting again.  Same symptoms.
  10. Disconnected power and removed motherboard/CPU/HSF from case, attached to another power supply from another system (PSU known good), tried booting again. Same symptoms.
  11. Srsly.  What.
  12. ...
  13. Ok, maybe CPU is bad.  Hahaha, silly notion.
  14. Took 'spare' CPU from lab server and swapped it out, installed Intel OEM cooler for ease of use, tried booting using the known good PSU.  System boots.
  15. So a different CPU on the same motherboard allows me to boot.  Therefore, the CPU is preventing the computer from booting (POSTing).
  16. Contact Intel for warranty replacement.  (which was handled like a consummate professional should - you go Intel)
  17. It arrives the next day.  Send bad one back to complete warranty.
  18. Put replacement 920 into lab server because the 950 is prettier in my PC anyways.

Comments

  1. KeithNovember 8, 2011 at 6:24 AM

    I had this happen a few years ago as well. Same symptoms, and I never would have guessed it was the CPU until I replaced the mainboard and the problem was still there :)

    ReplyDelete
  2. Chris TrotterNovember 8, 2011 at 7:22 AM

    Haha, yeah, wow...I was floored when I came to that realization.

    In related news, Intel's support chat guy was awesome. They have two options for warranty, once you get done with the preliminaries. One, you send it back and they send you a replacement. Since I don't have any CPU shipping stuff (and I'm particular about that kind of thing) I opted for option 2: They send me a replacement CPU with shipping label and I send it back.

    Very pleased with Intel's warranty, will continue my habit of purchasing Intel CPUs in future.

    ReplyDelete

Post a Comment

Popular posts from this blog

Learning through failure - a keyboard creation journey

Image
tl;dr Built a custom keyboard cuz I have weirdo nerve pain issues.   Learned a lot cuz I failed a lot.   Maybe 'do it right the first time' is a bad frame of mind.   The keyboard ended up being kinda nifty.   It has lights, and a trackball, and QMK, and it helps my issues.   \o/ ( tl;dr is internet lingo that means, too long; didn't read ) Pain as a key ingredient An old proverb says, 'necessity is the mother of invention', and that is how this story begins. Over the last few years, age or stress or something has caught up with me and I developed the need to change my human-to-computer interface.  Mousing changed to trackballing.  The traditional keyboard was swapped out for an ergonomic, and then split keyboard.  Complicated multi-finger-and-hand key combinations were replaced by single keypress macros.  And yet more was still needed. It's often said that change only happens with pain - indeed, the organizations many...
Read more

Learning Opportunities - Watching/listening list

Over the last year I've spent a lot of time learning (thank you, long commute & lunch hours).  Many topics ranging from Chef to DevOps to architecture concepts to management concepts and everything in between.  Why have I done this? DevOps Demystified with Ben Rockwood: https://www.youtube.com/watch?v=h5E--QSBVBY DevOps at ancestry.com: https://www.youtube.com/watch?v=pF5ya0q53kk Those two presentations were key in sending me down this road.  First, and most important, was Mr. Rockwood's explanation as to the real 'why', and the point behind DevOps from an operational perspective.  Second, and no less important but for a different reason, the continuous delivery system at ancestry.com really made it real to me because they are a 'Windows shop'.  So much of what I'd been reading about Chef/config mgmt. relied on amazing tools (see the error there?) only available to the Linux world.  Suddenly here's this guy telling me that it's possible...
Read more

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder: You are trying to set up replication for a DFS folder (no existing replication) Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2) You have no issues getting replication configured You see the DFSR folders get created on the other end, but nothing stages Finally you get EventID 4312: The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.    Additional Information:  Folder: F:\Users$\user.name\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D...
Read more