F5F Stay Refreshed Hardware Desktop Error indicates overheating but temperature is still within safe range.

Error indicates overheating but temperature is still within safe range.

Error indicates overheating but temperature is still within safe range.

S
Stealthycat75
Member
74
11-20-2016, 03:27 PM
#1
Hello everyone, I’m currently using a Xeon X5660 running on an Asus Rampage III Gene with a 120mm AIO. I managed to push the CPU to a 3.6GHz overclock at 1.3v and it ran smoothly under a modest FFT Prime95 workload, keeping temperatures below 70°C across all cores. But after roughly 20 minutes, the system crashes and restarts, showing the AMI post screen with a message about CPU overheating and asking to press F1 to continue. This is puzzling since the HWINFO reports the CPU temperature is only 30°C above TJMAX, which shouldn’t trigger any warnings. I’ve checked the BIOS but couldn’t find any option to suppress this error. Any advice or guidance would be really helpful. Thanks a lot!

System Specs: Xeon X5660 Asus Rampage III Gene 6x2Gb, OCZ Gold 1600MHz CL7 GTX Titan Black Seasonic Prime Platinum 750W, Windows 10 21H2, all drivers current, latest BIOS.
S
Stealthycat75
11-20-2016, 03:27 PM #1

Hello everyone, I’m currently using a Xeon X5660 running on an Asus Rampage III Gene with a 120mm AIO. I managed to push the CPU to a 3.6GHz overclock at 1.3v and it ran smoothly under a modest FFT Prime95 workload, keeping temperatures below 70°C across all cores. But after roughly 20 minutes, the system crashes and restarts, showing the AMI post screen with a message about CPU overheating and asking to press F1 to continue. This is puzzling since the HWINFO reports the CPU temperature is only 30°C above TJMAX, which shouldn’t trigger any warnings. I’ve checked the BIOS but couldn’t find any option to suppress this error. Any advice or guidance would be really helpful. Thanks a lot!

System Specs: Xeon X5660 Asus Rampage III Gene 6x2Gb, OCZ Gold 1600MHz CL7 GTX Titan Black Seasonic Prime Platinum 750W, Windows 10 21H2, all drivers current, latest BIOS.

J
jamiwilos
Member
118
11-22-2016, 12:08 PM
#2
You likely have a core spike issue. 96c reaches its T-junction limit, and 81.3 is its Tcase peak. At this temperature, x58 chips begin to degrade during overclocking. In the BIOS monitoring area, set the CPU temperature to ignore, but I recommend focusing on cooling solutions first—consider trying alternative temperature monitoring tools like CoreTemp to verify accuracy.
J
jamiwilos
11-22-2016, 12:08 PM #2

You likely have a core spike issue. 96c reaches its T-junction limit, and 81.3 is its Tcase peak. At this temperature, x58 chips begin to degrade during overclocking. In the BIOS monitoring area, set the CPU temperature to ignore, but I recommend focusing on cooling solutions first—consider trying alternative temperature monitoring tools like CoreTemp to verify accuracy.

I
IvyTheCat
Member
208
12-01-2016, 08:48 PM
#3
Recognized, I was aiming to create a tailored loop soon, but budget constraints are a bit tight. I’ll reduce the original cost and adjust the tools until I locate something with better performance under stress. Appreciate the help!
I
IvyTheCat
12-01-2016, 08:48 PM #3

Recognized, I was aiming to create a tailored loop soon, but budget constraints are a bit tight. I’ll reduce the original cost and adjust the tools until I locate something with better performance under stress. Appreciate the help!

O
Otherliterlink
Junior Member
40
12-19-2016, 03:36 AM
#4
Creating a custom loop sounds enjoyable, yet I’d allocate the money to genuinely improve the platform.
O
Otherliterlink
12-19-2016, 03:36 AM #4

Creating a custom loop sounds enjoyable, yet I’d allocate the money to genuinely improve the platform.