cancel
Showing results for 
Search instead for 
Did you mean: 

Random Spikes

ReapingGamer02
Level 8

Screenshot 2025-02-16 080319.pngScreenshot 2025-02-17 102532.pngScreenshot 2025-02-17 104344.png

Anyone noticed any glitches like these, only recently noticed it and it seems somewhat consistent, even tried wiping windows reinstalling drivers and at this point i'm unsure if it's the monitoring software as it consistently seems to report spikes even had CPU#0 report over 1.3 vsoc when i left settings at default, and consistently it's UCLK/FCLK, Vsoc and vdd_misc spiking

453 Views
1 ACCEPTED SOLUTION

Accepted Solutions

gupsterg
Level 13

@ReapingGamer02 

As Silent Scone said other software in the background can cause sensor read out errors as they try to read sensor together.

Some SW are aware of one another and will wait for one to finish reading sensor, before it reads sensor. This information was from author of HWINFO who I do talk to on forums and in private messages on OCN/HWINFO forum.

FCLK/UCLK/MEMCLK deviation can be down to Clock Spread Spectrum being [Auto] which defaults to Enabled as far as I know. The base clock is deviated ever so slightly when Clock Spread Sprectrum is working, this is to comply with EMI regulations. The base clock is referenced by those other buses for frequency. Thus I have always disabled this feature. You also don't want base clock deviation as could destabilse OC.

I have used HWINFO for many hours on several AM4/AM5. At times done beta testing for author. It maybe down to how I keep a cleaner OS by not having lots of apps running in the background. Generally I don't encounter crazy errors in HWINFO, it is one of the most reliable SW monitoring tools IMO. Sometimes some combos of HW/SW/FW are just buggy for SW reading, I don't know why.

Intel Defector :eek: AMD Rebel

View solution in original post

15 REPLIES 15

ReapingGamer02
Level 8

Well it shut down during a stress test so now not sure what to do

gupsterg
Level 13

I run HWINFO a lot not seen major glitches, may be one odd value. To be honest in my test runs usually no glitches I have noticed. Here's a recent 10hr one.

DuringDuring

 

EndEnd

 Any spread spectrum settings I would disable in UEFI.

VRM Spread Spectrum [Disabled]

Clock Spread Spectrum [Disabled]

Intel Defector :eek: AMD Rebel

Sorry to ask but when you say disable you mean don't leave it on auto right? haven't really messed with the VRM settings

Silent_Scone
Super Moderator

Hi @ReapingGamer02 

What sensors are you referring to?


@ReapingGamer02 wrote:

Screenshot 2025-02-17 104344.pngeven had CPU#0 report over 1.3 vsoc when i left settings at default, and consistently it's UCLK/FCLK, Vsoc and vdd_misc spiking


Use CPU VDDCR_SOC Voltage (SVI3) for the SOC voltage.

Make sure not to run multiple polling tools (can induce polling errors)

9800X3D / 6400 CAS 28 / ROG X870 Crosshair / TUF RTX 4090

If that's the one that jumped to 1.216 then yes that's the one i'm monitoring, the only two applications that would be polling asf as i'm aware is ICUE and Hwinfo, but even if it was a polling error would 5 metrics really be jumping i'd be more understanding if it were just the one, or are you referring to going into AMD Overclocking and setting the Vsoc in there

Could it be the polling setting being too agressive it was either .75ms or .5ms

Just ensure nothing else is running that could interfere with HWINFO polling the system, there should be no need to adjust the rate. SVI3 is the CPUs internal telemetry so should be the most accurate sensor. 1.216v is well within reasonable bounds.

If you want to compare power readings between the motherboard SIO and SVI3 make sure to do so at stock, but there should be minor realtime voltage deviation due to die sense implementation

9800X3D / 6400 CAS 28 / ROG X870 Crosshair / TUF RTX 4090

Yh that jump was but that's also the sensor that spikes past 1.3v after resetting everything to defaults and realising game first also polls I think, the motherboard sensors for the most part are static besides a 0.1v deviation 

Since I'm probably irritating you with questions may as well say it you'd just leave it down to sensor irregularities right, also the voltages and fclk/uclk jumps happen at the same time that's the main reason I was concerned