HWiNFO64 CPU Die (Average) Spike?

[Silentdreamer]

hallo, i have found this thread a week ago as im getting the same errors on HWinfo and today it also happend for the first on OCCT.
changed to am5 3 weeks ago the errors started around 2 weeks ago

is there already info where is error is coming from ?

specs
cpu 7800X3D
mobo Asus tuf b650m plus wifi / bios 1811
ram g.skill f5-6000j3038f16gx2-tz5nr / expo 1
gpu rx 6800XT
win 11 23h2 / chipset 5.08.02.027

 

[Renkou]

Hi, Made an account and chiming in on this also. I'm new to AM5 and just built a new pc. This has been happening for about a little less then a month now (noticed it on NOV 24th). My temps don't go any higher then 85c with the cooler on OCCT tests or heavy benchmarks but gaming I'm around 50-60c depending on the game with sometimes a spike to 75c or 80c on loads. vsoc is indeed locked at 1.2 in bios. My 7800X3D is running PBO curve optimizer at -22 with a high setting llc with EXPO on. Doesn't matter if im stock or not I always get a double reading on vsoc

PC Specs
AMD Ryzen 7 7800X3D 4.2 GHz 8-Core Processor running latest chipset drivers from gigabyte control center
Gigabyte B650 GAMING X AX on latest bios
G.Skill Flare X5 32 GB (2 x 16 GB) DDR5-6000 CL30-38-38-96 ram
Thermalright Peerless Assassin 120 SE
XFX Speedster MERC 310 Black Edition Radeon RX 7900 XTX 24 GB Video Card (12.12.1 drivers)
Super Flower Leadex VI Platinum PRO 850 W 80+ Platinum

 

[budida]

I haven't found anything like this on the Internet, so I'll write it here
Suddenly (suddenly, because it was only the second day and I have had the computer since September almost constantly with HWINFO turned on, monitoring whether everything is working well with cooling), around 11:30 p.m. while playing (I was playing BG3), my CPU die temp jumped literally for a second to 97 degrees, even though the current temperature did not even reach 40
I don't have anything turned on except the browser, discord and the game itself.
I don't use anything else for monitoring - I have the hwinfo log saved even from today


CPU - Ryzen 5 5600X
Motherboard - MSI B550-A PRO
GPU probably not important in this case

 

[hwinfo_koala]

I have been noticing similar behaviour over the past week or so with a 7 7800x3d and a 7900xtx running on an asus b650-plus wifi board. The Spikes usually range from about 130 degrees celsius to around 150 degrees celcius, and i have just now started logging those spikes. I used the following website to convert my logs into readable charts and noticed that the spikes only last for a very short amount of time (not sure how new this info is xD) (this is the website: https://logcharts-io.pages.dev/). My Polling Frequencies are set to 20ms. You can find my chart and HWINFO screenshot in the attached files.

Any Fixes?

Thanks in advance )


Edit: Forgot to mention that the screenshots were not taken at the exact same time (max temperatures dont really match)

 

[Renkou]

Hi, Made an account and chiming in on this also. I'm new to AM5 and just built a new pc. This has been happening for about a little less then a month now (noticed it on NOV 24th). My temps don't go any higher then 85c with the cooler on OCCT tests or heavy benchmarks but gaming I'm around 50-60c depending on the game with sometimes a spike to 75c or 80c on loads. vsoc is indeed locked at 1.2 in bios. My 7800X3D is running PBO curve optimizer at -22 with a high setting llc with EXPO on. Doesn't matter if im stock or not I always get a double reading on vsoc

PC Specs
AMD Ryzen 7 7800X3D 4.2 GHz 8-Core Processor running latest chipset drivers from gigabyte control center
Gigabyte B650 GAMING X AX on latest bios
G.Skill Flare X5 32 GB (2 x 16 GB) DDR5-6000 CL30-38-38-96 ram
Thermalright Peerless Assassin 120 SE
XFX Speedster MERC 310 Black Edition Radeon RX 7900 XTX 24 GB Video Card (12.12.1 drivers)
Super Flower Leadex VI Platinum PRO 850 W 80+ Platinum

So a little more testing on my end. Still with vsoc locked at 1.2 volts, I recently used OCCT's monitoring along hwinfo and hwinfo shows change on vsoc but OCCTs monitoring showes a min/max of 1.2v to the vsoc with no spike in it's graph. I'm basically going towards hwinfos readings being incorrect for that vsoc voltage.

 

[Martin]

Can someone please capture this spike in the HWiNFO Debug File?

 

[llkhrdh]

Same here, 7800X3D / GIGABYTE B650 AORUS ELITE AX / DDR5-6000 / XFX RX 6700 XT
negative 25 in bios

The other day, I saw 143c, and I thought it was just a bug in HWinfo. I'm not sure now.

 

[Steed]

I have been noticing similar behaviour over the past week or so with a 7 7800x3d and a 7900xtx running on an asus b650-plus wifi board. The Spikes usually range from about 130 degrees celsius to around 150 degrees celcius, and i have just now started logging those spikes. I used the following website to convert my logs into readable charts and noticed that the spikes only last for a very short amount of time (not sure how new this info is xD) (this is the website: https://logcharts-io.pages.dev/). My Polling Frequencies are set to 20ms. You can find my chart and HWINFO screenshot in the attached files.

Any Fixes?

Thanks in advance )


Edit: Forgot to mention that the screenshots were not taken at the exact same time (max temperatures dont really match)

Hey new here, but when looking at that screenshot of your HWiNFO readouts, I noticed that your values seem to be almost exactly double, what they should be. Not entirely sure what could cause this whether it is a conflict, but something is causing the values to double. If you take a look at your Frequency Limit - Global we are also looking at the maximum reporting 9,515.8 MHz. Now I am no professional but I believe that with your scenario this may be an erroneous report, just my two cents of course.

I will see if I can get a HWiNFO Debug readout of this that is small enough to upload. Since I as well have experienced similar behavior on exactly the same readouts that I have highlighted.
It happens so randomly for me that the debug file has been too large too process, when trying to upload in a post.

Edited Version of your HWiNFO Readouts has been attached.

 

[Renkou]

Can someone please capture this spike in the HWiNFO Debug File?

sure, how do i set up debug with logging in hwinfo?

 

[Martin]

sure, how do i set up debug with logging in hwinfo?

IMPORTANT - Read this before submitting a report

In order to submit a bug report, please include the following information: HWiNFO32/64 Report File (HTM or TXT preferred) HWiNFO32/64 Debug File (HWiNFO32.DBG or HWiNFO64.DBG) In case the application crashes or you are not able to create a Report File, please submit only the Debug File. This...

www.hwinfo.com

 

[Deleted member 25033]

Hello everyone I also have had a spike of 157 degrees when playing fortnite on epic settings. I have tried updating the chipset drivers and any other drivers and I have also disabled sleep mode. I also changed the sensors polling rate to 1 second. While in fortnite I landed in the bottom left of the map (Hazy Hillside) The first spike occured when I entered the second building which has a rebel hideout. I can get normal spikes of up to 87.3 (-30mv underclock on all cores). I tried to see if I could get it to trigger again by landing at the same place. It did trigger but later in the match and not in the same location. This time it was 106c. Bizarrely after doing the things I have done (Updating the drivers and bios) I only get a voltage spike on CPU VDDCR_VDD instead of all three. However I dont think its actually spiking (Or the cpu would have melted presumably?) so I tried deleting amd adrenalin and only install the driver. After doing this and trying a 1 hour fortnite session landing in the same place I have not seen the temperature spike, maybe there is a software clash with amd adrenalin? I'll report back if it comes back.

 

[Renkou]

IMPORTANT - Read this before submitting a report

In order to submit a bug report, please include the following information: HWiNFO32/64 Report File (HTM or TXT preferred) HWiNFO32/64 Debug File (HWiNFO32.DBG or HWiNFO64.DBG) In case the application crashes or you are not able to create a Report File, please submit only the Debug File. This...

www.hwinfo.com

after a little over an hour with gta online running idle, the 2.4 v soc hit...im not sure when as i was idle cleaning up around the house but when i came to check at the 1 hr 17m mark i saw it. where do i send the debug file?

 

[Martin]

after a little over an hour with gta online running idle, the 2.4 v soc hit...im not sure when as i was idle cleaning up around the house but when i came to check at the 1 hr 17m mark i saw it. where do i send the debug file?

Depends on how large the file is, probably in this case it will be quite large. First try to compress it and attach here. If that won't fit, you might send it directly to me via e-mail or upload it to some public sharing service.

 

[Renkou]

Depends on how large the file is, probably in this case it will be quite large. First try to compress it and attach here. If that won't fit, you might send it directly to me via e-mail or upload it to some public sharing service.

i tried already, raw it was 900 megs compressed its 130ish

 

[Deleted member 25033]

Is anyone not running amd adrenalin? Even if its running in the background on task manager, so just the driver because adrenalin could be the common denominator

 

[Renkou]

Is anyone not running amd adrenalin? Even if its running in the background on task manager, so just the driver because adrenalin could be the common denominator

i run it but have had it pop up still with just the driver. my direct settings were changed in the bios and not with software like ryzen master or even gigabytes. Only Hwinfo shows a spike in my vsoc when nothing else like gigabytes or occts monitoring systems show the spike. It's happened so much now that if it was true my pc should've died months ago.

 

[Deleted member 25033]

i run it but have had it pop up still with just the driver. my direct settings were changed in the bios and not with software like ryzen master or even gigabytes. Only Hwinfo shows a spike in my vsoc when nothing else like gigabytes or occts monitoring systems show the spike. It's happened so much now that if it was true my pc should've died months ago.

Have you updated to the latest bios? On F10 After updating and manually setting my vsoc I think I've stopped it (stopped the vsoc but not the VDD). Does your voltage spike for VDDCR_VDD as well? Also this might not help but there is a new version of HWiNFO EDIT: I will come back if I see it spike again maybe there are multiple factors here

 

[Renkou]

Have you updated to the latest bios? On F10 After updating and manually setting my vsoc I think I've stopped it (stopped the vsoc but not the VDD). Does your voltage spike for VDDCR_VDD as well? Also this might not help but there is a new version of HWiNFO EDIT: I will come back if I see it spike again maybe there are multiple factors here

The latest bios for my mobo is F20. Before that it was F9. I'm not on f20, I'm on F9. Only VDDCR_SOC Voltage. I have it locked in the bios at 1.2v. I don't really like to update bios right away as sometimes issues can occur and If im in a stable build i like to stay that way unless it's necessary to update. Also from my research there seems to be long training times on boot up with AMD AGESA 1.1.0.1 and expo enabled. My newest bios has AMD AGESA 1.1.0.1.

 

[Deleted member 25033]

The latest bios for my mobo is F20. Before that it was F9. I'm not on f20, I'm on F9. Only VDDCR_SOC Voltage. I have it locked in the bios at 1.2v. I don't really like to update bios right away as sometimes issues can occur and If im in a stable build i like to stay that way unless it's necessary to update. Also from my research there seems to be long training times on boot up with AMD AGESA 1.1.0.1 and expo enabled. My newest bios has AMD AGESA 1.1.0.1.

My bad I meant F20. That's fair but I would consider it at some point because that might help to fix it. At the same time I have no idea if this is going to come back yet for me. Also for context I've got a b650m aorus elite ax. I wonder why for you it's only soc and for me it's only VDD.

 

[Deleted member 25033]

Depends on how large the file is, probably in this case it will be quite large. First try to compress it and attach here. If that won't fit, you might send it directly to me via e-mail or upload it to some public sharing service.

So I've just looked at the comments on this forum page and I've tried to created a common denominator for gigabyte motherboards. Up to now I have seen 4/3 people using a Thermalright Peerless Assassin cooler and one person using a evga clc360mm aio and 5 people using a gigabyte b650 motherboard.
Two being a b650m aorus elite ax and one x670 aorus elite ax and one b650 aorus elite ax and one b650 gaming x ax .
This temp spike has been seen without amd adrenalin with just the driver. However just the driver being installed and the bios updated and limitng cpu voltages (CPU VDDCR_SOC) could maybe fix this. Im currently testing this so I'll let everyone know how it goes. Depending on the user there are a few things that happen for eg either a spike in CPU VDDCR_VDD Voltages or VDDCR_SOC voltages or having a spike with all three. I am noticing a potential common denominator of thermalright coolers (peerless assassin) and the b650 gigabyte line