Search results

One should not compare the TBP with "GPU Power Maximum" value. The "GPU Power Maximum" captures the highest (short) power spike which is relevant only for power delivery constraints and such short spikes are expected by design.

Sorry but what exact SDK do you use, where have you got it from?

Looks like access to DIMMs is locked on this mainboard, so HWiNFO cannot read SPD content, PMICs and thermal sensors on DIMM.

Hmm, that's a huge delay required. HWiNFO in each polling cycle and before accessing the GPU queries the state. If the GPU is sleeping, it won't proceed with further queries to avoid waking it up. Must be some bug in drivers...

It should be possible. If it doesn't show that, please attach a new HWiNFO Debug File.

HWiNFO® v8.26 available. Changes: Fixed DIMM polling on AMD TRX50/WRX80/WRX90 systems. Fixed ACPI sensor synchronization. Enhanced workaround for Kingston Fury Beast RGB DIMMs. Added scaling of OSD x-axis based on width. Improved assigning of OSD position when adding items. Enhanced sensor...

11000 ms (11 seconds) really or is that a typo?

This could be an issue with the storage (NVMe) driver for the KINGSTON SA2000M. Try to re-install/upgrade the driver or install latest Windows updates.

Please attach the HWiNFO Debug File for analysis.

There might indeed be a problem is the configuration but the exact outcome depends on your configuration. I'd recommend to clear the settings in HWiNFO and create a new configuration from scratch.

This is not HWiNFO's fault. As you can see with HAGS enabled, the GPU doesn't expose those counters.

HWiNFOMonitor is developed by a 3rd party (https://www.hwinfo.com/forum/members/stangowner.467/) and doesn't seem to be maintained anymore.

Does Task Manager show those values under the GPU performance tab? Can you attach the HWiNFO Debug File of both settings?

Please try this build and let me know if it fixes the problem: www.hwinfo.com/beta/hwi64_825_5724.zip

Thanks. It it an application or full system crash?

Please attach the HWiNFO Debug File of the crash. I need to analyze it to see what's failing there.

Yes, that's the reason why you see a problem in RTSS. Chinese simplified and traditional require a different encoding for this symbol but HWiNFO converts it to be properly interpreted in RTSS. Are you perhaps using some custom settings in HWiNFO? Do you run HWiNFO with Chinese (Simplified) language?

Do you use HWiNFO's built-in RTSS OSD to export data to RTSS, or importing data into RTSS from some other app like MSI AB with the HWiNFO plugin?

DigiDash should have integrated HWiNFO support.

That thread discusses a different issue - slight variation in BCLK measurement which is in fact correct due to SSC. 13th Gen has the alternate method.