• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

And the CPU socket is toasted

  • Thread starter Thread starter Deleted member 50521
  • Start date Start date
D

Deleted member 50521

Guest
i thought it was the PSU. Turns out it was the motherboard. Plugged the CPU into a friend's MoBo ans it boots just fine. I have no idea how the hell this could have happened. Rig was working perfectly and all of a sudden it just decided to crap out. I have been super careful during swap out to 6950X. I am just sitting here scratching my head.

On close examination pins seems to be fine. I don't know WTH was wrong. It was stuck in a bootup loop. On and off and on and off for over 20 minutes
 
Last edited by a moderator:
Pop goes the hardware
 
doesn't need to be the socket could be a bad vrm bad cap bad trace a issue with one the bga's a dozen other things dead board is dead
 
That sabertooth x99 is cheap compared to some x99 boards...

Pretty interesting how the sabertooth went from a truly tough product (990FX R2.0 ) to a cheap product (X99).

At op did you breadboard it?
 
OK I unplugged the two additional 8+4 plug to mobo and it WILL boot up. But no signal. CPU fan wont spin


BTW thanks for the awesome help guys. I knew i could count on you guys.
 
one of the vrm stages bought it then
 
Both VRM unplugged. Boot no signal. Either VRM plugged, boot looping.

VRM shot? Time to get the good old RMA then.
 
Both VRM unplugged. Boot no signal. Either VRM plugged, boot looping.

VRM shot? Time to get the good old RMA then.
fried like tofu and Doritos
 
Both VRM unplugged. Boot no signal. Either VRM plugged, boot looping.

VRM shot? Time to get the good old RMA then.

Id say so
 
Well everything is out now. Hope ASUS RMA won't be too much of a hassle.

IMG_1416.JPG
 
I was gonna say, how much for the cpu, but guess you're gonna rebuild....
 
I am trying to think of any other possible cause. If CPU is toasted it should not even boot. I just don't understand when unplugging VRM can lead to booting up but no display signal
 
Last edited by a moderator:
no power to the peg slots would be a good start
 
doesn't need to be the socket
Sockets don't just go bad. Generally, they have to be physically abused and that is pretty hard to do once the CPU is properly mounted.

Any component on the motherboard, however can fail. In fact, all electronics age and WILL fail eventually, if given a chance.

If your motherboard is still under warranty, you don't want to do anything to it that would void that warranty. You might try one stick of RAM at a time just to see what happens. Since the CPU works on another system, I would attempt to reset the BIOS/CMOS settings. If no luck there, RMA it.
 
Sockets don't just go bad. Generally, they have to be physically abused and that is pretty hard to do once the CPU is properly mounted.

Any component on the motherboard, however can fail. In fact, all electronics age and WILL fail eventually, if given a chance.

If your motherboard is still under warranty, you don't want to do anything to it that would void that warranty. You might try one stick of RAM at a time just to see what happens. Since the CPU works on another system, I would attempt to reset the BIOS/CMOS settings. If no luck there, RMA it.


Tried all of that. Did not work. Scary part was on friends machine we didn't see if it would enter BIOS. We just did a quick on and off to see if it lights up. I sincerely hope the CPU is not dead. Now I need to ask him to spare me his machine for one more day.

FML





OK a quick recap of event:

I was trying to install Windows 10 onto the new NVMe SSD. Installed fine. Booted up fine. Then after I installed the drivers and thought to reinstall softwares the machine crashed. Then this refuse to boot problem started.

Waited overnight, eventually it will allow me to boot up again. Run good for about half a day and then dead again. This time it refuse to boot up.

Fast forward a week. Got the replacment PSU. Hooked up. Stuck in boot loop. If I unplug the VRM 8+4 plug it will stay on buy no signal display over monitor.

This board does not have a Q-CODE and the TUF detective requires an Andriod. RMA filed with ASUS.


Before the attempted Windows 10 Reinstallation everything was perfect. Honestly I have no freaking idea what went wrong.
 
Last edited by a moderator:
Honestly I have no freaking idea what went wrong.
Ugh, problems like this are the worst, hopefully smooth sailing once you get the new board. Nice pile of parts btw! ;)
 
Cursed OS that win10 ;)

I hope the CPU is live mate and with a RMA you will be up and running soon :toast:

BTW, pretty weird series of events you faced there. From the looks of it, mobo is the cause as most already implied.
 
One small detail. During both of the crash the problem happened right around when I installed the Intel Chipset driver. Now looking back I should have installed the 10.1.1.xx version which is for consumer version. I installed 10.1.2.xx, which is supposed only for server version. Could this be causing all the problem?

Already got RMA lined up and ready to go ATM. Will the board to ASUS and hope for the best.
 
No i dont think so, that would only be loaded once you are in the OS. If you are having a hard time booting, it's not software related.
 
Could be a BIOS coruption from that driver you installed?
Just a wild guess.

Take out that NVME, use a spare sata drive with Windows on it, reset the BIOS (take out battery) and try to boot.

Could be NVME failled or BIOS coruption.
That is all i can think of.

P.S: Forgive me for not following whole thread but i read your initial problem and first thing that poped in to my head, i wrote.

Boot looping tells me 2 things:
Bad boot device
BIOS coruption
Jayz2Cents had a simmilar problem, check out his video.
 
Last edited:
Thx for the input Filip, the board has already gone out to RMA. Just mailed it. Frankly i'd rather drive over there since their service center is only 3 hrs drive from where I live.


Now you mentioned it. Should i also get a replacement for the 960Pro just in case it is faulty? Still within newegg's return for replacement period.
 
Back
Top