F5F Stay Refreshed Hardware Desktop Your extremely hot motherboard may have damaged the SATA connectors.

Your extremely hot motherboard may have damaged the SATA connectors.

Your extremely hot motherboard may have damaged the SATA connectors.

P
phatbobrmr
Member
Find
53
10-20-2016, 12:58 PM
#1
I own a JINGSAH X79M-S3.0 LGA2011 motherboard (purchased from Alibaba) with an Intel Xeon E5-2690 CPU. After assembling the PC, I realized the case was overheating and the CPU cooler fan wasn’t working properly—possibly due to a loose connection. The system ran smoothly enough for Windows 10 installation and most OS updates. Now it’s functioning mostly, but there are issues: one rear USB 3.0 port isn’t working and the HDD isn’t detected in Disk Management. When trying to connect the HDD, I’ve tested all four SATA ports on the motherboard with two different cables, yet Windows still doesn’t recognize it. The OS is installed on an m.2 NVMe SSD, and other rear USB ports are working fine. What’s likely causing these problems? Could the overheating during Windows 10 installation have played a role?
Reply
Reply
P
phatbobrmr
10-20-2016, 12:58 PM #1

I own a JINGSAH X79M-S3.0 LGA2011 motherboard (purchased from Alibaba) with an Intel Xeon E5-2690 CPU. After assembling the PC, I realized the case was overheating and the CPU cooler fan wasn’t working properly—possibly due to a loose connection. The system ran smoothly enough for Windows 10 installation and most OS updates. Now it’s functioning mostly, but there are issues: one rear USB 3.0 port isn’t working and the HDD isn’t detected in Disk Management. When trying to connect the HDD, I’ve tested all four SATA ports on the motherboard with two different cables, yet Windows still doesn’t recognize it. The OS is installed on an m.2 NVMe SSD, and other rear USB ports are working fine. What’s likely causing these problems? Could the overheating during Windows 10 installation have played a role?

Reply
Reply
S
Sheikrik
Senior Member
Find
441
10-21-2016, 01:28 AM
#2
The board isn't what I expected; rather, if the CPU wasn't adequately cooled, its I/O ports might have sustained damage.
Reply
Reply
S
Sheikrik
10-21-2016, 01:28 AM #2

The board isn't what I expected; rather, if the CPU wasn't adequately cooled, its I/O ports might have sustained damage.

Reply
Reply
N
nascar_fan
Member
Find
140
10-25-2016, 07:49 AM
#3
You wonder if the warmth from the system might have harmed the USB 3.0 connector, and whether the SATA connections for the hard drive on the motherboard are secure.
Reply
Reply
N
nascar_fan
10-25-2016, 07:49 AM #3

You wonder if the warmth from the system might have harmed the USB 3.0 connector, and whether the SATA connections for the hard drive on the motherboard are secure.

Reply
Reply
P
Phantomz_MC
Member
Find
53
10-29-2016, 01:59 AM
#4
I don't believe the motherboard is likely to be damaged.
Reply
Reply
P
Phantomz_MC
10-29-2016, 01:59 AM #4

I don't believe the motherboard is likely to be damaged.

Reply
Reply
3
3gilad3
Senior Member
Find
735
10-29-2016, 02:17 PM
#5
I don't believe the CPU is faulty; the issue seems linked to the SATA connectors not functioning properly. Since the HDD isn't appearing in BIOS or Disk Management, it might indicate a hardware or configuration problem rather than a CPU failure.
Reply
Reply
3
3gilad3
10-29-2016, 02:17 PM #5

I don't believe the CPU is faulty; the issue seems linked to the SATA connectors not functioning properly. Since the HDD isn't appearing in BIOS or Disk Management, it might indicate a hardware or configuration problem rather than a CPU failure.

Reply
Reply
I
IkBenHetBram
Senior Member
Find
735
10-30-2016, 04:25 AM
#6
I believe it's feasible since you mentioned the CPU cooler fan wasn't working. Thermal issues can arise, but verify the CPU is properly seated before jumping to a fault. Adjusting core settings or reseating the chip might resolve the problem.
Reply
Reply
I
IkBenHetBram
10-30-2016, 04:25 AM #6

I believe it's feasible since you mentioned the CPU cooler fan wasn't working. Thermal issues can arise, but verify the CPU is properly seated before jumping to a fault. Adjusting core settings or reseating the chip might resolve the problem.

Reply
Reply