Search results

Temp2 is a bogus reading that should be ignored. Max Turbo is a normal indicator that core clock is reduced because multiple cores are utilized (standard Turbo Boost behavior).

Not CSV but Debug File. It's described in the post I linked above.

Can you capture that spike in HWiNFO Debug File?

Must be an invalid readout similar to: https://www.hwinfo.com/forum/threads/hwinfo64-cpu-die-average-spike.8044/page-19#post-49517 Would you be able to capture this in the HWiNFO Debug File?

First try to reboot the system and avoid other monitoring tools. If that won't help, then: https://www.hwinfo.com/forum/threads/read-this-before-submitting-a-report.241/

Oh, that's "great" support... Blaming others for their problems. iCUE is a well known "masterpiece"... DIMM info, DIMM sensors and VRM sensors.

Depends on mainboard but usually you'll lose DIMM information and monitoring and on some boards also sensors. Why not report the problem to Corsair?

To add these sensors one would need to know the protocol used by the controller. This is certainly something proprietary the vendor won't disclose. I can also see an Adlink SMBus controller present, so the I2C device is most likely connected to it. But this is also using a proprietary protocol...

Thanks for your feedback.

Yes, all Beta are in portable format only. Just copy the file from portable package to replace the one in installed folder. Or if you have the Pro version, it will do the job automatically.

If it's a conflict then it's easy to find out - try to run only HWiNFO and see if the problem happens.

Probably next week.

No :(

Most probably it's this: https://www.hwinfo.com/forum/threads/hwinfo64-cpu-die-average-spike.8044/

Thanks. Support for your model will be added in the next (Beta) build.

The Report File is OK but DSDT is only the header, I need full dump in .bin format.

I will need: - The HWiNFO Report File - Dump of DSDT table by: www.hwinfo.com/beta/FirmwareTablesView.exe.zip

Try to Reset Preferences or click F2 over the sensor heading to check for renamed sensor.

That's certainly an invalid readout or glitch in the sensor.

GPU drivers. If that won't help try to also Reset Preferences in HWiNFO.