Crashes when loading sensors in the latest beta, and pretty much every problem, ever.

Supahgl00

Member
Hey everyone.
First time post here.
Hopefully someone can help me out with an absolute nightmare i'm having.
The latest beta hwinfo64 crashes to desktop when i try to load the sensor window. No error message.
My system is only 3 months old and has been nothing but an complete headache since day 1.
My RTX 3080 died after a clean install of new drivers, luckily got an RMA for that.
3 corsair LED strips have died, I had a corrupt bios, random restarts, sometimes I have to clear CMOS just to stop a continuous reboot cycle. There is instability in games, the Asus Aura RGB IO on the motherboard is stuck in rainbow wave puke lighting mode even when the PC is off. the previous version of hwinfo64 was fine and so was the beta up until two days ago, and I did notice my power reporting deviation was all over the place. Asus software gives me errors when updating drivers or utilities. My corsair iCue even says I have 3 AIO coolers installed......I mean, come on. I've done no overclocking or pushed any voltages ect.
Just a lot of weird (and worrying) behavior.
Sorry for going on about more than just a hwinfo64 bug, but I just want the damn thing to work. :(
I'm guessing it's the motherboard (Asus Rog Strix x570 F) as i've tried all I can think of, from swapping RAM sticks down to a fresh reinstall of windows. the beta still crashes.
Any help with this would be greatly appreciated.

Edit: I would post the debug file but it crashes before I can get that far.
 

Martin

HWiNFO Author
Staff member
Have you been using custom sensors order in the previous versions?
I will need to see the Debug File. Even if it crashes, it still will produce that file. If the initial screen where you can enable Debug Mode is not shown, you might need to insert "DebugMode=1" at the end of HWiNFO64.INI file.
 

Supahgl00

Member
Have you been using custom sensors order in the previous versions?
I will need to see the Debug File. Even if it crashes, it still will produce that file. If the initial screen where you can enable Debug Mode is not shown, you might need to insert "DebugMode=1" at the end of HWiNFO64.INI file.
Thanks for the quick response Martin. I have indeed managed to create a debug file.
 

Attachments

  • HWiNFO64.DBG
    1.7 MB · Views: 2

Martin

HWiNFO Author
Staff member
You said that HWiNFO was crashing, but according to that file it didn't crash, it was normally terminated.
Ah yes, you didn't open sensors. Please do so and attach a new file after it crashes.
 

Supahgl00

Member
Ah sorry mate you're right, I didn't open sensors. Duh. But I can assure you I definitely didn't terminate the application.
Awesome, another problem to add to the list lol. Anyway, here is another debug file.
 

Attachments

  • HWiNFO64.DBG
    1.2 MB · Views: 1

Martin

HWiNFO Author
Staff member
Thanks, this seems to be a bug in latest build of HWiNFO.
Did you have monitoring of some items disabled or used custom order of sensors before?
It would be great if you could run "regedit" and export the following key into a file and post it here: HKEY_CURRENT_USER\SOFTWARE\HWiNFO64\Sensors
 

Supahgl00

Member
Sure thing. And no, I never disabled any of the sensors. The only thing I ever did if anything was just expand the sensor pages into 3 columns and had it fullscreen.
The main reason I use hwinfo64 really is to keep my eye on those VRAM temps in game. 90c memory junction makes me feel uncomfortable.
Here's my registry key. :)
 

Attachments

  • Sensors.rar
    2.9 KB · Views: 1

Martin

HWiNFO Author
Staff member
Thanks, this should help me to find the bug.
You should be able to workaround this bug by doing a "Reset Preferences" from the main settings menu.
 

Supahgl00

Member
Aha! I just made a registry backup, deleted the HWiNFO64 registry directory and then deleted the HWiNFO64 ini file, launched the standalone and it works! I Guess my registry was messed up or something... But I did a fresh install of Windows 10 and it didn't work. Hmm.
Oh well I can chalk that one off the list of problems lol. Thanks for your help anyway Martin you're a star!
 

Dodge-Gee

Member
Good Day Martin,
I am having an issue between HWInfo 7.06-4500 and ICUE 4.13.226.
I have a Corsair 1000D with a built-in Commander Pro/Fan Controller. The ICUE software works correctly, however, when I start HWInfo, it causes the sensors in ICUE to disappear and reports random speed fans in HWInfo for the fan controller.
In order to get ICUE to work, I have to close HWInfo and then force a firmware update on the fan controller.
I have reset the HWInfo preferences, added "DebugMode=1" at the end of HWiNFO64.INI file, enabled CorsairLink in HWInfo settings/Safety Tab, Registry export, and other screenshots. The HWiNFO64.DBG is over 100mb so can't upload.

Appreciated
 

Attachments

  • HWInfo.zip
    745.5 KB · Views: 1

Martin

HWiNFO Author
Staff member
Good Day Martin,
I am having an issue between HWInfo 7.06-4500 and ICUE 4.13.226.
I have a Corsair 1000D with a built-in Commander Pro/Fan Controller. The ICUE software works correctly, however, when I start HWInfo, it causes the sensors in ICUE to disappear and reports random speed fans in HWInfo for the fan controller.
In order to get ICUE to work, I have to close HWInfo and then force a firmware update on the fan controller.
I have reset the HWInfo preferences, added "DebugMode=1" at the end of HWiNFO64.INI file, enabled CorsairLink in HWInfo settings/Safety Tab, Registry export, and other screenshots. The HWiNFO64.DBG is over 100mb so can't upload.

Appreciated
Corsair software cannot work together with any other software accessing their devices and Corsair refuses to implement a simple mechanism that would allow this.
Please check many other threads about this issue on this forum.
You will have to disable the "CorsairLink and Asetek Support" option in HWiNFO.
 

Dodge-Gee

Member
Appreciated Martin. I think if enough users report it to Corsair, maybe they will change it.
Disabling "CorsairLink and Asetek Support" did not work.
I have logged a ticket with Corsair.
Thanks for all the work!
 

Martin

HWiNFO Author
Staff member
What happens with "CorsairLink and Asetek Support" option disabled, does HWiNFO still crash? If yes, please attach the HWiNFO Debug File of the crash.
 

Dodge-Gee

Member
When it disabled, HWInfo doesn't crash, but reports random variating speeds for the Commander Pro/Fan Controller. The ICUE software then stops showing/reporting fan speeds. Does the same whether enabled or diaabled
 

Dodge-Gee

Member
Thanks again Martin!

So with ICUE running, I disabled the "CorsairLink and Asetek Support" option, then restarted the PC.
I then had ICUE running in background reporting correctly, then opened HWInfo, and ICUE was working correctly, however, HWInfo does not report the Corsair Link/Commander Pro sensors.

I have logged a ticket with Corsair and hopefully, they will allow this in the future to work with HWInfo.

Appreciate the support! I will continue to use HWInfo & ICUE like this and proceed with my testing/setup.
 

SpeedyIV

Active Member
HA! Good luck getting Corsair to do that. The developer of SIV spent years trying to get them to use the proper interlocks that allow multiple programs to access the same sensors without conflicts. He even showed them how to do it. IIRC, they actually did implement it for a short time but then decided to not continue doing it. It was a conscious, informed decision on their part. He was pretty pissed off and basically gave up on Corsair that day. I solved the problem by not installing iCue, which is a hot, buggy mess anyway. Don't believe me? Go read the Corsair forums. I use SIV to control my Corsair hardware. It's not as fancy as iCue (in terms of RGB control) but it serves my needs and is a great program for system monitoring. You can open a ticket with Corsair, but they are not gong to fix this. Good Luck!
 

Martin

HWiNFO Author
Staff member
Many developers were proposing the same method as SIV but gave up the same way...
Maybe if enough customers will start to complain, Corsair will listen one day...
 

Dodge-Gee

Member
Corsair did get back to me twice.
First saying it was "sent to a specialist to test", then 6 hours later got the reply "these will conflict with each other and you are not able to run them simultaneously. Thank you for choosing Corsair"... So that was unsuccessful...
So, I installed ICUE, did the setups for the fans connected to Commander Pro, then uninstalled it, and seems to keep the settings even without ICUE.
So I'm happy about that, so I can remove ICUE, and install HWInfo, and back to happy days.

Thanks for keeping on top of the development of HWiNFO Martin!
Great tool!
 

SpeedyIV

Active Member
You could use SIV to control your commander pro. SIV has a bit of a learning curve, but its fan control allows things like setting up "synthetics" which combine multiple temps for fan curve control points. SIV can also run concurrently with HWINFO because unlike iCue, they both use the proper interlocks to access system sensors without collisions. Also unlike iCue, SIV also puts very little load on the CPU. The only thing I ever use iCue for is to update firmware in my commander pro and lighting node pro. SIV cant' do that. If you are interested, here is a LINK. The author of SIV also runs a forum HERE.
 
Top