Search results

Yes, normal.

PCI(e) bus has a different topology. You can examine this in the main HWiNFO window.

HWiNFO shows GPUs in the order in which they appear on PCIe bus.

Not sure what exactly do you mean without seeing a screenshot but if you have a GIGABYTE board then it's most likely the AORUS theme used by HWiNFO. This can easily be disabled in main settings.

That's intentional for these aggregated values.

Expand the nodes by clicking the arrow to the left.

Close HWiNFO. Run "regedit" tool Navigate to: HKEY_CURRENT_USER\Software\HWiNFO64\Sensors\GpuI2cCache Delete the entire key. If that won't help, please attach the HWiNFO Debug File.

Do that reset right after starting HWiNFO (before the scan is started). Or restart HWiNFO right after the reset.

Sorry, there are no dedicated shortcuts/hotkeys for those features.

Try to "Reset GPU I2C Cache" in HWiNFO settings - "SMBus / I2C" section.

If voltage offsets are not shown, then most likely because Windows HVCI (Core isolation/Memory integrity) is blocking access and you will need to disable it to see them.

This will be fixed in the next HWiNFO (Beta) build.

I see the GPU load fluctuates a lot, so the temperature should be as well. In such case when each app measures the value at a different time point, it could be different. Can you compare the values at constant GPU load? Also, another reason could be a bug in NVIDIA drivers when temperature...

HWiNFO reads the actual timings and clock straight from the memory controller. So your RAM is really running only the standard JEDEC timing and XMP wasn't properly applied by BIOS.

Driver

NVIDIA drivers provide these measurements. I bet GPU-Z is showng the same number.

Nice, thanks for your feedback.

HWiNFO® v8.25-5715 Beta 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...

OK, I will add support for this new PID in the next (Beta) build scheduled for release today.

Thank you, now it contains what I needed. I will try to fix this issue in the next (Beta) build.