F5F Stay Refreshed Hardware Desktop Error indicating the CPU is overheating on the Asus device.

Error indicating the CPU is overheating on the Asus device.

Error indicating the CPU is overheating on the Asus device.

1
1Point10
Member
Find
144
02-23-2019, 11:38 PM
#1
Before diving into the subject, here are my details. PSU 1000w Thermaltake 80 gold plus CPU 3900x, motherboard ASUS Crosshair Hero VIII (WiFi), latest BIOS installed. GPU is EVGA 2080TI K. RAM is 3600 G.Skill Trident Enermax 360 Liquid Cooler. I’ve overclocked the 3900x to 4.475 with one core and others at 4.3. Vcore sits at 1.35, dropping to 1.32 under load—still stable. Cinebench, cpuz, and gaming have all performed well. About a week ago I encountered crashes while using Blender, reporting an overheating warning. I ran the Blender benchmark tool and hwinfo64 showed temperatures under 75, with the CPU package at 10°C higher than actual. Still, crashes occur. Could hwinfo64 be accurate or is the voltage insufficient? I’m trying to determine the cause. I can push it to 4.5 and it works, but random crashes persist elsewhere?
Reply
Reply
1
1Point10
02-23-2019, 11:38 PM #1

Before diving into the subject, here are my details. PSU 1000w Thermaltake 80 gold plus CPU 3900x, motherboard ASUS Crosshair Hero VIII (WiFi), latest BIOS installed. GPU is EVGA 2080TI K. RAM is 3600 G.Skill Trident Enermax 360 Liquid Cooler. I’ve overclocked the 3900x to 4.475 with one core and others at 4.3. Vcore sits at 1.35, dropping to 1.32 under load—still stable. Cinebench, cpuz, and gaming have all performed well. About a week ago I encountered crashes while using Blender, reporting an overheating warning. I ran the Blender benchmark tool and hwinfo64 showed temperatures under 75, with the CPU package at 10°C higher than actual. Still, crashes occur. Could hwinfo64 be accurate or is the voltage insufficient? I’m trying to determine the cause. I can push it to 4.5 and it works, but random crashes persist elsewhere?

Reply
Reply
I
InsygniaS
Member
Find
55
02-25-2019, 06:57 PM
#2
Re-examine using HWMonitor. After that, reset the CPU to its default settings and observe any crashes; if it fails, your overclock is likely unstable. A different method involves testing with OCCT and big data sets.
Reply
Reply
I
InsygniaS
02-25-2019, 06:57 PM #2

Re-examine using HWMonitor. After that, reset the CPU to its default settings and observe any crashes; if it fails, your overclock is likely unstable. A different method involves testing with OCCT and big data sets.

Reply
Reply
T
TommyTheLommy
Posting Freak
Find
846
02-27-2019, 08:51 AM
#3
Returned to stock settings with no problems. Reloaded the profile and tweaked the fan curves slightly for better performance. After consecutive blender tests, stability improved. Temperatures stayed below 73°C, but the VCore showed minor fluctuations—around 1.32 instead of 1.35, dropping to 1.304 even with maximum load. It’s possible a faulty PSU is contributing to the instability during overclocking, as voltage droop might trigger errors without noticeable overheating.
Reply
Reply
T
TommyTheLommy
02-27-2019, 08:51 AM #3

Returned to stock settings with no problems. Reloaded the profile and tweaked the fan curves slightly for better performance. After consecutive blender tests, stability improved. Temperatures stayed below 73°C, but the VCore showed minor fluctuations—around 1.32 instead of 1.35, dropping to 1.304 even with maximum load. It’s possible a faulty PSU is contributing to the instability during overclocking, as voltage droop might trigger errors without noticeable overheating.

Reply
Reply
J
JeronimoYT
Senior Member
Find
428
02-27-2019, 10:37 AM
#4
Temperature isn't the only issue when overclocking. Several other elements can affect performance even at low temperatures. I'd verify the reading with another tool, but it's unlikely that hardware information would be wrong.
Reply
Reply
J
JeronimoYT
02-27-2019, 10:37 AM #4

Temperature isn't the only issue when overclocking. Several other elements can affect performance even at low temperatures. I'd verify the reading with another tool, but it's unlikely that hardware information would be wrong.

Reply
Reply
H
hdoor20
Senior Member
Find
477
03-07-2019, 04:14 AM
#5
I solved the problem. I didn’t notice having two ccx at 4.475 when it should have been one. After entering the right numbers, everything functions properly again. Still puzzling about why a temporary spike appeared when HWinfo64 displayed the max temperature at 75°C. I’m unsure which reading to focus on—my CPU temp is 75°C, but the package temps are consistently 10°C higher, suggesting a high of around 87°C. I added a push-pull configuration to my radiator, and now temperatures stay below 66°C. I double-checked using the ASUS AI app, which matches HWINFO64 readings.
Reply
Reply
H
hdoor20
03-07-2019, 04:14 AM #5

I solved the problem. I didn’t notice having two ccx at 4.475 when it should have been one. After entering the right numbers, everything functions properly again. Still puzzling about why a temporary spike appeared when HWinfo64 displayed the max temperature at 75°C. I’m unsure which reading to focus on—my CPU temp is 75°C, but the package temps are consistently 10°C higher, suggesting a high of around 87°C. I added a push-pull configuration to my radiator, and now temperatures stay below 66°C. I double-checked using the ASUS AI app, which matches HWINFO64 readings.

Reply
Reply