Troubleshooting Desktop Failure, Some Moral Support?

Thats pretty impressive, never had a RMA go that fast for the many things I had to send back over the years.
 
AMD's RMA process is pretty awesome.

They received, tested my CPU and shipped a replacement CPU all in the same day. Very impressed. They put Gigabyte to shame.

Not that Gigabyte were bad or anything, but AMD really just showed up everyone in the "how you handle a product failure" category.

I had expected this to drag out longer, so now I'm likely not going to be ready for the CPU when the new one gets here :p

I told you AMD would hook you up with no problems.
 
to the OP,

well, you posted this back in late Jan 2020 and I will presume you solved it but I did notice in your initial comment that you did not first check the PS. ALWAYS check the PS first (a checker is very cheap on ebay, Newegg, etc) or just use a paper clip and short the two terminals on the 24 pin connector (info is online).

Back when I was an electronics repair tech at HP (system test instrumentation) I saw not just one tech (including myself once) troubleshooting for perhaps 2-3 hours and scratching their head as to why the readings were so low and then a fellow tech would walk over, ask how it was going and would then notice the instrument was not plugged into the AC outlet, an external PS being used was not turned on or they failed to check the internal PS in the unit being worked on and this was usually the tech's reaction to having missed that ---- > :eek: :oops: :rolleyes: :)
 
Last edited:
to the OP,

well, you posted this back in late Jan 2020 and I will presume you solved it but I did notice in your initial comment that you did not first check the PS. ALWAYS check the PS first (a checker is very cheap on ebay, Newegg, etc) or just use a paper clip and short the two terminals on the 24 pin connector (info is online).

Back when I was an electronics repair tech at HP (system test instrumentation) I saw not just one tech (including myself once) troubleshooting for perhaps 2-3 hours and scratching their head as to why the readings were so low and then a fellow tech would walk over, ask how it was going and would then notice the instrument was not plugged into the AC outlet, an external PS being used was not turned on or they failed to check the internal PS in the unit being worked on and this was usually the tech's reaction to having missed that ---- > :eek: :oops: :rolleyes: :)


I think you misread.

The power supply was the first thing I checked.
 
So, I finally finished my build over here a few days ago.

WTF!

Go to start up my desktop this morning and it has no power. Just like last time. It was working fine for a while and then just refuses to power up one morning.

It took months of RMA's and rebuild to get to the point of getting it up again, and it lasts a few days and then it is down again. Same as last time, it was working perfectly, shut it down at night. Won't power on next day. No apparent leaks or other problems.

I'm pissed. Not quite sure what to do. Last time, after mistakenly RMA:ing the PSU and motherboard, and the manufacturers finding no problems, it turned out to be a dead CPU. I just don't have the time to do more troubleshooting right now.

What are the chances of getting two bad Threadrippers in a row, one an RMA for the last?
 
So, I finally finished my build over here a few days ago.

WTF!

Go to start up my desktop this morning and it has no power. Just like last time. It was working fine for a while and then just refuses to power up one morning.

It took months of RMA's and rebuild to get to the point of getting it up again, and it lasts a few days and then it is down again. Same as last time, it was working perfectly, shut it down at night. Won't power on next day. No apparent leaks or other problems.

I'm pissed. Not quite sure what to do. Last time, after mistakenly RMA:ing the PSU and motherboard, and the manufacturers finding no problems, it turned out to be a dead CPU. I just don't have the time to do more troubleshooting right now.

What are the chances of getting two bad Threadrippers in a row, one an RMA for the last?

be honest with yourself regarding the following Q's (no need to reply to this):

did you wear a grounding strap at all times while building the PC?
was it pluggfed in to a QUALITY surge protector?
 
I strongly suspect there is something wrong with the motherboard that slowly kills CPU's over a period of 1 to 8 weeks, that didn't show up in Gigabytes testing when I RMA'd it because they probably just do a quick power on test...
 
be honest with yourself regarding the following Q's (no need to reply to this):

did you wear a grounding strap at all times while building the PC?
was it pluggfed in to a QUALITY surge protector?

What do you suppose the chances are of the first time of seeing ESD or surge damage in 30 years of building PC's comes within a couple of months of eachother, and exhibit the exact same symptoms?
 
I strongly suspect there is something wrong with the motherboard that slowly kills CPU's over a period of 1 to 8 weeks, that didn't show up in Gigabytes testing when I RMA'd it because they probably just do a quick power on test...
look at he bright side? it only takes a few days to rma a cpu and you be back online by next weekend.
 
As for why there dying? Not sure yet....I would closely monitor all the cpu voltages best i could, and see if it could even be double checked with a quality meter (if even possible)....As far as ESD its easy enough to ground yourself on the case it self with out using a strap...right now i just think you have 2 bad cpus in a row. Is it dying after a power down by chance? Or did you check on it in the AM and the thing had turned off by itself? I will say thing going by your luck...Im sticking with Asus MB's :whistle:
 
As for why there dying? Not sure yet....I would closely monitor all the cpu voltages best i could, and see if it could even be double checked with a quality meter (if even possible)....As far as ESD its easy enough to ground yourself on the case it self with out using a strap...right now i just think you have 2 bad cpus in a row. Is it dying after a power down by chance? Or did you check on it in the AM and the thing had turned off by itself? I will say thing going by your luck...Im sticking with Asus MB's :whistle:

I don't have a UPS on this machine, but my main server and switch both have them and they would have alarmed if the power fluctuated. I have no alarms for the time period.

To be clear, I have not done any troubleshooting yet. I'm dreading pulling everything out t I'm dreading pulling everything out yet again to confirmthat it is the CPU this time again, but the symptoms are exactly the same, so I am leaning in that direction...
 
As for why there dying? Not sure yet....I would closely monitor all the cpu voltages best i could, and see if it could even be double checked with a quality meter (if even possible)....As far as ESD its easy enough to ground yourself on the case it self with out using a strap...right now i just think you have 2 bad cpus in a row. Is it dying after a power down by chance? Or did you check on it in the AM and the thing had turned off by itself? I will say thing going by your luck...Im sticking with Asus MB's :whistle:

I did some googling and found a few posts online where people are saying the default voltage of their Threadrippers is WAY too high out of the box.

I wonder if that is what happened here. I didn't even check. I don't usually mess with voltage settings unless I plan on overclocking.

If the voltage were way too high for some strange reason (bad default BIOS settings?) that would have exactly this symptom. Working well for a while, but slowly killing the CPU.

This is my theory considering I have found it posted online, but I can't confirm it now.
 
I did some googling and found a few posts online where people are saying the default voltage of their Threadrippers is WAY too high out of the box.

I wonder if that is what happened here. I didn't even check. I don't usually mess with voltage settings unless I plan on overclocking.

If the voltage were way too high for some strange reason (bad default BIOS settings?) that would have exactly this symptom. Working well for a while, but slowly killing the CPU.

This is my theory considering I have found it posted online, but I can't confirm it now.
i think it is no other explanation....its 7nm tech which if i had to guess every new smaller process becomes more and more sensitive to damage from excessive voltage, and correct me if im wrong but your somewhat thinking your temps were a bit higher than you had planned for. (if the voltage was sky high then this makes perfect sense)...Did you ever even run the rig thru a heavy task like Intel burn test on max on say 10 runs for test purpose?
 
Do you have anything plugged into the fan headers of your mobo? I had a buddy who RMA'd his PSU at least twice before discovering that a case fan was shorting out and causing the PSU to shut off/not turn on.
 
Back
Top