[SOLVED] Threadripper dead?

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Jun 28, 2020
15
0
10
I just assembled my threadripper 1920x, with an S24 cooler and it was working fine. I didn't do any overclock or change any settings on BIOS besides boot order.

Since I wanted to do some heavy stuff I put 8 CPU heavy tasks throughout the night. The next morning the image was frozen but the system was on. After rebooting there is an error 3E on the motherboard Aorus x399.

I tried reassembling it, removing ram and still the same error code on the motherboard.

My only suspicion is that the cooler was not well connected and the cpu could be burnt?

Why didn't the automatic thermal protection kick in and switch off the system before that happen?

Is my cpu dead?
 
Solution
Resetting the CMOS I did with a screwdriver touching both pins... You think removing the battery could make a difference? I didn't change anything on the BIOS besides boot order and it worked fine before that.
To do a proper clear CMOS:
-turn the PC off
-unplug the psu from the wall
-remove the battery from the motherboard
-press and hold the power button on the chassis for 15 seconds. This discharges any leftover power in the capacitors.
-put everything back and try again


Boot order: Was Compatibility Support Module(CSM) enabled?
There's 2 different drivers that run your storage: Legacy, and Windows UEFI.
All my storage drives use the Legacy driver, and if I set CSM to use UEFI driver only, save and exit, the system brings me...
To do a proper clear CMOS:
-turn the PC off
-unplug the psu from the wall
-remove the battery from the motherboard
-press and hold the power button on the chassis for 15 seconds. This discharges any leftover power in the capacitors.
-put everything back and try again


Boot order: Was Compatibility Support Module(CSM) enabled?
There's 2 different drivers that run your storage: Legacy, and Windows UEFI.
All my storage drives use the Legacy driver, and if I set CSM to use UEFI driver only, save and exit, the system brings me right back to bios because it no longer detects my storage drives.
If that were the case with you, it should've brought you right back to bios.
Thanks will try a proper CMOS reboot.

On the boot order, the system doesn't get to bios so I doubt this could be the case.
 
This is the answer I got from gigabyte tech support just today:

-------
Thanks for using GIGABYTE products.

Could you please install all the power cords, CPU, memories again and try to change your memories to other slots. If it still can’t boot, please try to clear CMOS. Thank you

Clear CMOS:
(1) Turn off the power.
(2) Remove the power cords from the motherboard.
(3) Take out the battery gently and put it aside for about 5 minutes or longer.
(Or you can use a conductive metal to connect the two pins in the battery holder to make them short-circuited.)
(4) Re-insert the battery to the battery holder.
(5) Short-circuit the clr_CMOS header.
(6) Connect the power cords to motherboard again and turn on the power.
If it still can’t boot, please contact a local dealer or repair center (where you bought the products) for further check.
 
try booting with no memory to see if you get a different code, all i can find on this error indicates RAM incompatibility issues. short of that id say something fried.

I think you were right.

Finally I tried as you advised (and also Gygabyte) and restarted with no memory and got error 10.

Then removed all the memory except one, two and three and seems the system doesn't work with 1 one of the 4 sticks of ram. So now the system is running with 3 sticks of memory.

I assume during the 8 hours of work it started using the damaged memory and marked it as a bad memory?
 
was memory sold as a 4 piece kit? if not there no guarantee it works together, if it was, then id think one would be dead, or the slot, you could test simply enough and just replace ram with the 2 other and see if it still boots, but if there still 2 separate matched pairs, it could be they just not playing nice