Recent content by Martin

Does the other system perhaps have multiple monitors with different scaling?

Thank for your feedback, I will need to investigate this problem in more detail...

Do you seen an "ACPI" sensor in the list? If yes, try to disable its monitoring by pressing the Del key over its heading.

What display scaling is used on your monitors? Is "Anti-aliased" HWiNFO tray setting enabled on both?

Are you using the latest version of MSI Center?

Even older versions didn't display the warning and if another application was blocking them, they might show wrong sensor values.

Version 8.28 did only improve synchronization with other applications when accessing shared sensors. If you see that warning it means the other app is either improperly using synchronization or it hammers the sensor so that other apps can't access it. So the problem is in MSI Center. Version...

Does HWiNFO display some warning about a stuck mutex?

That's certainly an invalid value due to a collision in software, the CPU wouldn't survive such voltages.

Sorry, I posted this in the other thread, so copying here too: The "Recovery Count" counts the number of changes from L0 to Recovery. It triggers for example during a change in speed, width, or other possible reasons that usually don't mean a PCIe error occured. The other counters however might...

I can see all values reported there.

Thanks but I need one that includes also start of HWiNFO. Debug Mode must be enabled prior to starting the scan.

Please provide the HWiNFO Debug File

Are you maybe running some othe rmonitoring/tweaking/RGB or Fan control tools? Some such tools might be causing this.. Is the first screenshot from the GIGABYTE SIV tool?

Sorry, there's no option to disable that entirely. You might try to disable the "opeAPI Support" option in HWiNFO. That will disable most of Intel GPU monitoring functions except a few IGCL calls. Maybe that will help at least partially.