This is expected to a degree. You will always have differences even in the same circuit due to voltage drop. This would be exacerbated by readings from two different tools (the multimeter vs onboard sensors). .5 volts is a lot, but not surprising.I'm still getting the 2.4V on the SOC and CPU Die (average) temps spiking way above 100C, so no change on my end. So a friend sent me this video by Gigabyte Aorus, and was interesting to see that perhaps the CPU reporting in HWiNFO is not so accurate.
For me, it has nothing to do with resource demand, gaming has no effect on the problem for me. It tends to happen when I leave the machine for a bit and then come back, as if something's waking up froma low-power state.This is my random spike on gaming sessions. It was not in an intense map at all.
If I install my new board and am happy with it, would you be interested in having me send you the old one? I'd want it back when you're done, but it would just be a spare, I couldn't sell it in good conscience unless I found that the problem isn't with the motherboard.I'm still looking into this issue in the lab. I'll catch up on the thread in a bit and see if I can pull anymore clues, but it seems like it 'just happens'. I've racked up hundreds of machine hours on our reference board without a repro. Those systems are logging VRM telemetry via EVC2 in parallel and not a single blip.
Seems to me as if we are doing / having something that you don't.I'm still looking into this issue in the lab. I'll catch up on the thread in a bit and see if I can pull anymore clues, but it seems like it 'just happens'. I've racked up hundreds of machine hours on our reference board without a repro. Those systems are logging VRM telemetry via EVC2 in parallel and not a single blip.
There's certainly a missing factor. It could be the board itself. Maybe early boards have the problem and later boards don't. It could be the VRM components came faulty from another vendor and have since been switched. It could be chipset drivers, EMI noise, the presence of a hard drive or cooling pump, there are thousands of possible factors. Maybe if I get the time, I'll put together a spreadsheet and ask everyone for specific details about their setup. It could help uncover a common denominator.Seems to me as if we are doing / having something that you don't.
My main concern is this is a latent failure. It will slowly degrade over time and eventually kill the CPU. I'd very much like to measure the voltage externally, but I can't bring myself to start poking at the board in case I short something and ruin it. I've offered to send my board to a few folks, but haven't had any luck so far.Hi guys, first post here so please bear with me if I am missing any posting protocol or necroing a thread (found on google!) but I just got the same issue after gaming for a couple hours in my 7800X3D and 7900XT setup:
View attachment 9530
Seems to line up with everything I've seen in this thread so far - I am using a Asus PRIME B650M-A WiFi board, and I did upgrade the BIOS pretty much immediately after buying after I heard about the fried 7000 cpus fiasco. I did reset my bios to default today using the Load Optimized Defaults option when I was installing the 7900XT - not sure if that adds any helpful info.
I'm guessing this must be a "bug" of some kind because I imagine temperatures and voltages like that would just kill the system. It is however worrying.
My recommendation is to report it to both AMD and ASUS through their respective ticket systems.Just signed up to report this too. I’d thought the whole over-voltage issue was fixed with the latest bios update (at least that’s what AMD/ASUS said) so decided to go ahead and purchase a 7800x3d and ASUS b650e-i to go in a new pc.
Put everything together yesterday, updated the bios to the latest (1616), and enabled expo. I also set up a SOC voltage alert in hwinfo. Today I was alerted to a SOC voltage of 2.480v and CPU die temp of 103.7. I’ll attach a photo below (sorry for the quality).
Seems like this follows the doubled regular figure for voltage/temp that was picked up on in this thread. I believe my computer also briefly went into sleep mode automatically a bit earlier in the day.
Is there a recommended procedure for reporting this to AMD/ASUS or do I just go through the usual support channels for my region?
View attachment 9532
Will do. Funny that you mention the 1.33333x multiplier as I just had a spike today of 1.653v from 1.240v (in keeping with your observation), and was about to ask here what people’s thoughts were.My recommendation is to report it to both AMD and ASUS through their respective ticket systems.
As for the double value. I've noticed several variations. 1.33333, 1.5 and 2.0 times the normal setting. This is far too exact to be coincidence.
That's interesting. I have disabled the onboard graphics, but because it uses the SoC voltage and according to Gamer's Nexus, might be the component that's exploding. I figured if it was disabled, there's less chance of this happening.Will do. Funny that you mention the 1.33333x multiplier as I just had a spike today of 1.653v from 1.240v (in keeping with your observation), and was about to ask here what people’s thoughts were.
Personally, I seemingly only started getting the voltage spikes after disabling the CPU’s integrated graphics in Windows (solely because it was slowing down steam startup). Could just be a total coincidence but I wonder if anyone else with this issue has also done the same?
I’m on the latest version of Windows 11.