Trashcanclippy
Member
A silly update on my end. Pretty sure my CPU should be dead right now if these values are correct.
Should have desoldered too.
Should have desoldered too.
HWiNFO64 CPU Die (Average) Spike?
- Thread starter Venoxium
- Start date
Holy crap. I've never seen them that high.
Try running HWmonitor at the same time. I'm doing it, and it doesn't show anything. I wonder if that's because it's not sampling often enough to catch the spike, or if there's a difference with the way HWinfo gets the data. I'd love to talk to someone who knows how those things work. In my mind, it could be whatever mechanism AMD uses to feed data to the software (the BIOS/AGESA?) or how the software interprets the data.
How often does HWinfo poll the sensors? Apparently HWmonitor does it every second, would it be the same here? Is it customizable?
Edit: I answered my own question. For me it's set to poll every 2 seconds. I'm going to change it to 1 second and see if that makes a difference.
Edit: I answered my own question. For me it's set to poll every 2 seconds. I'm going to change it to 1 second and see if that makes a difference.
Last edited:
Looks like your numbers are shown tripled, both temps and voltages. Mine just doubled for now.
Trashcanclippy
Member
I see gigabyte has an updated BIOS available with so-called "more accurate" reporting for HWiNFO. Will I still see 200+ C on my CPU die average?
GIGABYTE and HWiNFO Exclusively Collaborate for Accurate Information and New Memory Timings Feature | News - GIGABYTE Global
July 28, 2023–GIGABYTE TECHNOLOGY Co. Ltd, a leading manufacturer of motherboards, graphics cards, and hardware solutions, is pleased to announce its close collaboration with H...
I see gigabyte has an updated BIOS available with so-called "more accurate" reporting for HWiNFO. Will I still see 200+ C on my CPU die average?
GIGABYTE and HWiNFO Exclusively Collaborate for Accurate Information and New Memory Timings Feature | News - GIGABYTE Global
July 28, 2023–GIGABYTE TECHNOLOGY Co. Ltd, a leading manufacturer of motherboards, graphics cards, and hardware solutions, is pleased to announce its close collaboration with H...www.gigabyte.com
That's for other things like advanced BIOS options reported in HWiNFO. I doubt it will have any effect on this issue.
Not sure if.. but I have not observed the issue since a couple of weeks now. My best guess is that some of recent Windows 11 updates fixed it. Also I have been updating the Adrenalin GPU drivers. However I do not know whether or not this may have an effect.
Also it may be worth to mention that I disabled the internal GPU of my Ryzen CPU. Here as well I do not know if thas had any effect. I did it to save a couple of watts of power consumption.
Also it may be worth to mention that I disabled the internal GPU of my Ryzen CPU. Here as well I do not know if thas had any effect. I did it to save a couple of watts of power consumption.
Casanova Hammerhaulk
New Member
Just finished building an AM5 system and ran into this same issue.
After some investigating, it appears to be related to HWinfo and Fan Control software. So far in my testing, I have not seen a CPU Die (average) spike since disabling Fan Control. I'd be curious how many other users here experiencing the same issue also use Fan Control?
Build:
Software:
After 5 hours of testing I've seen no spikes. Previously, I would see spikes under idle or load conditions, seemingly at random.
I'm assuming these are erroneous values. As others have noted, the CPU would be toast if they were true. However, still unsettling to see.
Update: 10 hours and no spikes.
After some investigating, it appears to be related to HWinfo and Fan Control software. So far in my testing, I have not seen a CPU Die (average) spike since disabling Fan Control. I'd be curious how many other users here experiencing the same issue also use Fan Control?
Build:
- MSI X670E Carbon Wifi (MS-7D70)
- Bios Vers: 7D70v17
- AMD 7950x3d
- G.Skill Z5 Neo 64gb (2x32gb) PC5 48000
- EXPO@ 6000
- MSI 4090 Suprim Liquid X
Software:
- OpenRGB
- V: 0.9
- Fan Control
- V: 165
- HWInfo
- V: 7.60-5170
After 5 hours of testing I've seen no spikes. Previously, I would see spikes under idle or load conditions, seemingly at random.
I'm assuming these are erroneous values. As others have noted, the CPU would be toast if they were true. However, still unsettling to see.
Update: 10 hours and no spikes.
Last edited:
Same here with my M17 R5 Alienware (Ryzen 9 6900HX CPU) it read 122c and 150c on two different instances... No way that's possible.... right?
Update: Just got this reading: 229.5 C ... My laptop isn't hitting 229c is it?
Update: Just got this reading: 229.5 C ... My laptop isn't hitting 229c is it?
Attachments
Last edited:
blobstinate
New Member
Be aware, I have also gone a while without any episodes, just for them to reappear again. Please let us know if you see it happen again. I switched to Windows 11, and it didn't solve it, so I went back to 10. If a Windows update has indeed fixed the issue, I'd definitely be willing to upgrade again (even if I can't move the taskbar). I also have my iGPU disabled, it hasn't changed anything. I was just hoping that if there is a spike, it's less likely to destroy the chip if the iGPU is off.
Last edited:
At this point, I'm throwing my hands up over this issue. Everyone I've contacted points the finger at someone else, nobody seems to be taking it seriously enough to track it down for good. I'm going to operate under the assumption that it's some sort of software error and isn't actually a real spike. If my CPU explodes down the road, I'll just shrug and reinforce the knowledge that you can't trust anyone to do the right thing.
Considering HWmonitor doesn't show the spikes, I'm going to assume that the problem lies with HWinfo (misinterpreting the data), HWmonitor (maybe it's not sensitive enough to pick up the spikes) Windows (maybe HWinfo uses a different method to access the data than HWmonitor) or AMD drivers/BIOS (maybe the data is being fed to the software incorrectly).
Either way, I'll never buy another AMD product, I can't afford the stress of worrying if my $1000 CPU is going to burn up.
Considering HWmonitor doesn't show the spikes, I'm going to assume that the problem lies with HWinfo (misinterpreting the data), HWmonitor (maybe it's not sensitive enough to pick up the spikes) Windows (maybe HWinfo uses a different method to access the data than HWmonitor) or AMD drivers/BIOS (maybe the data is being fed to the software incorrectly).
Either way, I'll never buy another AMD product, I can't afford the stress of worrying if my $1000 CPU is going to burn up.
Saltywag86
New Member
so This is a bug from hwinfo? btw guys i got update on bios 1602 ( e-egaming wifi x670 rog strix board ) also same problem.. and my cpu is like 45 C and first time i saw Cpu die like 93 C and really wondering...
Saltywag86
New Member
so we dont focus on this because is not valid , i guess,,.. hmm ? i mean that temps are not real for sure
Similar threads
