F5F Stay Refreshed Hardware Desktop Is your motherboard damaged?

Is your motherboard damaged?

Is your motherboard damaged?

T
Takeo_Player
Member
177
12-28-2016, 09:15 PM
#1
Hey everyone! My PC started showing a warning about over current on the USB port. It said the system would shut down after 15 seconds to protect the mainboard. I unplugged all USB devices and the issue kept happening. Once I removed the USB 3.0 cable from the motherboard, it seemed like a broken pin was causing the problem. A single damaged pin really damaged my board! Any suggestions on how to fix this?
T
Takeo_Player
12-28-2016, 09:15 PM #1

Hey everyone! My PC started showing a warning about over current on the USB port. It said the system would shut down after 15 seconds to protect the mainboard. I unplugged all USB devices and the issue kept happening. Once I removed the USB 3.0 cable from the motherboard, it seemed like a broken pin was causing the problem. A single damaged pin really damaged my board! Any suggestions on how to fix this?

S
SpookyKingzzz
Junior Member
39
12-28-2016, 09:39 PM
#2
Overcurrent would be from the PSU no? Not sure if a USB header pin snapping would cause that. If you think the PSU is fine then try powering it on with the 3.0 cable left unplugged and see if it runs fine. EDIT: Misread a bit, if it was just overcurrent on the USB device, could be that pin, or something just asking for more power than the USB header can provide.
S
SpookyKingzzz
12-28-2016, 09:39 PM #2

Overcurrent would be from the PSU no? Not sure if a USB header pin snapping would cause that. If you think the PSU is fine then try powering it on with the 3.0 cable left unplugged and see if it runs fine. EDIT: Misread a bit, if it was just overcurrent on the USB device, could be that pin, or something just asking for more power than the USB header can provide.

A
amyeenhoorn
Member
121
01-10-2017, 04:07 PM
#3
It could work if you simply leave that header behind, though if it remains it may indicate a serious issue.
A
amyeenhoorn
01-10-2017, 04:07 PM #3

It could work if you simply leave that header behind, though if it remains it may indicate a serious issue.

R
RulwenJr
Posting Freak
786
01-10-2017, 06:41 PM
#4
It seems the issue repeats annually. It turns out disabling the Thunderbolt header resolved it.
R
RulwenJr
01-10-2017, 06:41 PM #4

It seems the issue repeats annually. It turns out disabling the Thunderbolt header resolved it.