Search results

Hmm, those Debug File seem to be from a different system/configuration. First one has ATA drive WDC WD10EZEX and NVMe WDS100T3X0C. It hangs when HWiNFO queries the ATA drive for SMART status. Second DBG has WDC PC SN730 and KINGSTON SA2000M NVMe drives. It hangs at detecting the KINGSTON drive...

HWiNFO64.DBG should be in the folder when HWiNFO is installed. You might need to compress (ZIP, 7z, RAR) it before attaching here.

https://www.hwinfo.com/forum/threads/read-this-before-submitting-a-report.241/

I don't have information how to retrieve these values. Will request from Glenfly.

HWiNFO® v8.24 available. Changes: Added Memory-only mode. Added monitoring of VRAM Read/Write Bandwidth on Intel Arc B-series GPUs. Enhanced sensor monitoring on ASUS ROG CROSSHAIR X870E EXTREME. Fixed Razer PWM support. Fixed MSI MEG Ai1600T PSU support. Added monitoring of 12VHPWR pin and...

https://www.hwinfo.com/forum/threads/hwinfo64-cpu-die-average-spike.8044/

Yes, you'll need to wait for TRCC update. Don't worry they do care.

Thank you. This will be fixed in the next HWiNFO build and require an update to TRCC.

Sorry but that's the Report File. I need the Debug File as described above.

What RGB control application are you using? Please run standard HWiNFO64 and attach the HWiNFO Debug File generated by it.: https://www.hwinfo.com/forum/threads/read-this-before-submitting-a-report.241/

Thank you. I found the bug and it shall be fixed in the next build. For the time being, you can get rid of those keys by deleting the following registry keys under HKEY_CURRENT_USER\Software\HWiNFO64\Sensors: AutoLoggingHotKey, ResetValuesHotKey

Did you also click "OK" after unchecking the respective boxes? Please do a "Backup User Settings" from main settings of HWiNFO. The compress the file saved (with ZIP, RAR, 7z) and attach here so I can analyze the settings.

Oh, indeed. That's a bug, shall be fixed in the next build.

Try to manually attach it to the respective process ID (PID) of the game. Get the game's PID from Task Manager and then enter into the bottom right and press Lock.

You should better check on some forums dealing with legacy systems, e.g.: https://www.vogons.org/

BTW, reporting 115V for VIN can result in some mess when calculating power consumption. Corsair uses certain formulas (estimates) to calculate either PIN from POUT or vice-versa and they depend on whether the PSU is 110V or 230V.

Such static values don't need to be constantly monitored, so there's no sensor for it. You can however see this value in the main HWiNFO window.

You can do that by defining a hotkey - Toggle OSD output.

It's not possible to universally determine if an application is a game or something else. One can only make assumptions. So is the targeting of the OSD.. You can change targeting of the OSD in Sensor settings - OSD.

This is quite expected as during sleep several interfaces are switched off and it might take a while to wake them up.