F5F Stay Refreshed Hardware Desktop Damage to 5820K is significant but cause remains unclear.

Damage to 5820K is significant but cause remains unclear.

Damage to 5820K is significant but cause remains unclear.

V
VORGDEV
Junior Member
Find
6
07-02-2023, 12:22 AM
#1
My 5820K is beyond repair, and I'm unsure what led to this. It once handled 4.4ghz at 1.3v with the hottest core staying under 80°C. It's been cooled with a Noctua NH-D15 chromax, which isn't old, and the thermal paste has been refreshed regularly. The photo I shared is taken under normal operating settings with some RAM tweaks. Recently, the package temperature isn't reading properly—it worked just fine a few days ago. If I leave everything stock and XMP enabled, it stays below 60°C. However, without overclocking, the core temps never exceed 90°C, and the package only shows around 55°C. Plus, I set the max CPU temp to 85°C in BIOS before shutdowns occurred. What's happening? Did something go wrong, or is the system failing?
Reply
Reply
V
VORGDEV
07-02-2023, 12:22 AM #1

My 5820K is beyond repair, and I'm unsure what led to this. It once handled 4.4ghz at 1.3v with the hottest core staying under 80°C. It's been cooled with a Noctua NH-D15 chromax, which isn't old, and the thermal paste has been refreshed regularly. The photo I shared is taken under normal operating settings with some RAM tweaks. Recently, the package temperature isn't reading properly—it worked just fine a few days ago. If I leave everything stock and XMP enabled, it stays below 60°C. However, without overclocking, the core temps never exceed 90°C, and the package only shows around 55°C. Plus, I set the max CPU temp to 85°C in BIOS before shutdowns occurred. What's happening? Did something go wrong, or is the system failing?

Reply
Reply
E
emstay26
Senior Member
Find
441
07-08-2023, 11:27 AM
#2
Are you noticing identical outcomes in HWinfo64? HWMonitor is often reported as unreliable.
Reply
Reply
E
emstay26
07-08-2023, 11:27 AM #2

Are you noticing identical outcomes in HWinfo64? HWMonitor is often reported as unreliable.

Reply
Reply
X
xFrusky
Junior Member
Find
43
07-08-2023, 01:12 PM
#3
HWiNFO64 accurately interprets the sensors and displays a wealth of additional information, capturing every available sensor reading.
Reply
Reply
X
xFrusky
07-08-2023, 01:12 PM #3

HWiNFO64 accurately interprets the sensors and displays a wealth of additional information, capturing every available sensor reading.

Reply
Reply
N
Nero12321
Posting Freak
Find
858
07-08-2023, 09:39 PM
#4
Reset the CMOS and see if it resolves the issue. If not, verify whether a newer BIOS version is available. There might be a voltage setting affecting temperature readings due to thermistors inside the CPU. It seems to be an Intel or AMD problem—I’m not sure which one. @ShrimpBrime
Reply
Reply
N
Nero12321
07-08-2023, 09:39 PM #4

Reset the CMOS and see if it resolves the issue. If not, verify whether a newer BIOS version is available. There might be a voltage setting affecting temperature readings due to thermistors inside the CPU. It seems to be an Intel or AMD problem—I’m not sure which one. @ShrimpBrime

Reply
Reply
S
S4NP3I
Member
Find
194
07-11-2023, 08:13 PM
#5
Package temperature is off; it's not a core reading. Your system's Agent offset likely shows elevated temperatures. Current value is +0.358v—much higher than expected. Aim for around 1.1v maximum, with a small offset of 0.1v or less.
Reply
Reply
S
S4NP3I
07-11-2023, 08:13 PM #5

Package temperature is off; it's not a core reading. Your system's Agent offset likely shows elevated temperatures. Current value is +0.358v—much higher than expected. Aim for around 1.1v maximum, with a small offset of 0.1v or less.

Reply
Reply
1
11rperry
Junior Member
Find
17
07-12-2023, 03:42 AM
#6
I realized the CPU wasn't damaged; the issue stemmed from HWMonitor malfunctioning when I set a manual shutdown temperature in BIOS. At the time, my OC ran at 4.2GHZ with 1.25V. I adjusted it later to maintain lower temperatures. Thanks to Zando Bob and SpiderMan for their guidance—I was mistaken! Appreciate all the feedback.
Reply
Reply
1
11rperry
07-12-2023, 03:42 AM #6

I realized the CPU wasn't damaged; the issue stemmed from HWMonitor malfunctioning when I set a manual shutdown temperature in BIOS. At the time, my OC ran at 4.2GHZ with 1.25V. I adjusted it later to maintain lower temperatures. Thanks to Zando Bob and SpiderMan for their guidance—I was mistaken! Appreciate all the feedback.

Reply
Reply