Search results

Probably a temporary glitch, I don't see any problem now. Try to refresh the page.

You probably meant Windows 95. There has never been a 97. The first HWiNFO was running on DOS 3.2x :) I still recall testing first code at school on PC XT and 286s :) 386 was a beast back then :)

I agree that such behavior is odd and don't know what could be causing it. The symptoms you describe clearly indicate a fault accessing the LPC/SIO chips. In fact, software is hard to blame here because the problem is a hardware erratum when those LPC/SIO chips are used in dual-configuration...

Accessing sensors on systems with dual SIO chips (IT87952E as the second one) requires special precautions. If a software doesn't do it right, the result is as you described - loss of IT87952E or even the primary chip (IT8689E), and this can also lead to system instability. You mentioned that...

Invalid readout, will be filtered out in the next build.

Thank you for your kind words :) It feels great to hear that my work is so helpful.

Disabling "CorsairLink and Asetek Support" will just disable support of those devices in HWiNFO but can't solve the problem that iCUE is blocking others. Clicking "Ignore" will disable all future warnings. To enable it back, you'll need to either delete the HWiNFO64.INI file or remove the...

Thank you for your offer!

"Snapshot CPU Polling" is for AMD CPUs only. Enable "Auto Start" or disable the "Show Welcome Screen...". Greece - maybe this summer ;)

Memory clock is tied to bus clock (BCLK) and if BCLK isn't exactly 100 MHz, then you see such difference. It's common for BCLK to be slightly lower due to SSC.

Thanks for the feedback. I'm curious how the modules appear now because they seem to be using a different part number in HP. Could you please attach a new Debug File so I can check that?

Yes, currently the position will always start from 1 regardless if it's already taken. You can use the table on top to check which positions are currently assigned. But I understand this is quite inconvenient and will check how to improve this in the next (Beta) build.

Great to hear that :) You're welcome!

I see... I will change this in the next (Beta) build to dynamically adjust the range based on width.

Please try the new v8.25-5705 Beta and let me know the result. Prior to running it, please do a shutdown to clear any previous erratic state. If the problem wasn't solved, please attach a new DBG file after shutdown.

Please try the new v8.25-5705 Beta and let me know the result. It should work also with the ACPI sensor enabled.

HWiNFO® v8.25-5705 Beta available. Changes: Fixed DIMM polling on AMD TRX50/WRX80/WRX90 systems. Fixed ACPI sensor synchronization. Enhanced workaround for Kingston Fury Beast RGB DIMMs.

The sampling period of the OSD time axis is same as the Global Polling period of sensors. You can change this period in main sensor settings. Otherwise you can change the OSD width.

Thanks, I will try to fix this in the next (Beta) build. But I'm wondering if HWiNFO shows the memory modules at least the first time after a clean boot.

You didn't disable both ACPI sensor values. Best would be todisable the heading. But anyway, I have an idea what could be causing this and will try to fix this in the next (Beta) build.