Unable to reboot Windows 7 64bit system if HWiNFO was started

DanRaj

Member
Hi,

very weird issue, it took me a little while to narrow it down to HWiNFO. Using version 8.16 portable.

PC is equipped with ASUS P5E socket 775 motherboard, 2x2GB Corsair DDR2 RAM, HD5450 GPU. I use it to test/OC various CPUs/GPUs from time to time. Windows 7 x64 with recent Simplix update package applied, system is relatively fresh install. Drivers installed via Snappy Driver Installer Origin, for my convenience.

The issue is, the PC fails to boot/reboot if I started HWiNFO at any point in the Windows session. When attempting to reboot, the system would begin the power cycle, the keyboard and mouse would turn off the lights and then the monitor doesn't receive the signal anymore, while the PC is still apparently running (fans working etc.). I have to turn off the PSU switch and then the PC would boot to Windows.

If I do not start HWiNFO at all, the PC (re)boots without issue every time. If I start and close HWiNFO before rebooting the issue still occurs. I have tried both 32bit and 64bit versions of HWiNFO.

I do not know which additional information I should provide, hopefully I can help to narrow down this very weird issue.
 
Hmm, such issue is not easy to diagnose. As first, try to disable "SMBus Support" in HWiNFO if that might solve it.
 
Disabling "SMBus Support" solves the issue. I have another Socket 775 Windows 7 machine where I don't have issues with HWiNFO, so I'll try to figure out what's different there.
 
You might attach the HWiNFO Debug File with SMBus Support enabled. I can then check if I see anything suspicious.
 
Thanks. Please keep SMBus enabled and in the "SMBus Device Exclusion" section set the box belonging to address 0x19.
Then let me know if this solved the problem.
 
Hm, then it must be some other address but there are too many combinations to try.
Might be better to start with selecting entire rows and then go one by one...
 
Managed to find the right exclusions, it's 0x61. Thanks for helping me, really weird some motherboards don't like software reading those entries.
 
Great, thanks. Here's the sensor that appears after adding the exclusion: Nuvoton W83791SD/G

P.S the board is now cross-flashed to Rampage Formula, but the problem existed even on stock P5E BIOS

Capture.PNGCapture2.PNG
 
Well, for starters, Happy New Year!

And hints - electronics are the science of contacts, so just in case, check the contacts in the power cables, especially SATA - they like to get out of the connectors. I already ran into this by a couple of cars, although maybe when the installation I myself pulled too much the tapes (my PSU cable has tape) to the case chassis, but the fact - in two cases SATA, the cables partially crawled out of the nests, so it is outwardly not clear, But in the SATA firmware section - there was an optics and there is no - the port is empty and the cars are alive. :) One does not start creating the illusion of the system of the system HDD (I already thought of the backup to put), the second is launched, but more often the OS hungs on the start of the bootloader and click Reset.

In both cases, it turned out that the cables fell a little from the nests, the optics were not frightened and spoils the whole picture - well, the Intel C602 chipset does not like connected, but not involved in SATA cables or not powered devices on the ports and in such cases buggy.

And WHEA sensors do not catch such phenomena - only open the housing and check with your hands. Although other phenomena are caught, for example, overheating of the RAM, but if on the modules the temperature sensors are like on the RDIMM (REG ECC DIMM) or LRDIMM (Low-Reduced DIMM). Well, so they have it as a position - this is server memory modules. :)
 
Hello Guys,
I stumbled upon this thread because yesterday I had the same problem as DanRaj.

My System:

- OS: Win11 23H2
- MB: Gigabyte B650 Aorus Elite AX V2
- RAM: GSkill Trident Z5 Neo DDR5, EXPO enabled
- CPU: Ryzen 7 7800X3D
- CPU Cooler: NZXT Kraken
- GPU: RTX 4080 Super
- Drives: 3x Samsung NVME + Kingston Sata SSD

I was using my PC in this constellation with HWInfo installed for 7-8 months without any issues.
I always start HWInfo manually when I want to check something. Yesterday I saw that there was a new update V 8.20 so I installed it.
After that I checked some sensor readings and a message popped up that HWInfo detected a conflict with NZXT Cam (It never did this before but there was a CAM Update recently)
Next I decided to restart my PC.

Like DanRaj's System also mine wouldn't post this time so after 10 minutes I forced a shutdown pressing the power button on the case. After that the system booted without a problem.
I immediately thought it must be something related to HWInfo because this was the only change I made this day. I reproduced the problem a few times till i was certain I knew what it was.
For now i solved the problem by just not opening HWInfo. I did not try to install an older version of HWInfo.

I also checked event viewer and the only error I could find was this one with Event ID 2: Session "PerfDiag Logger" failed to start with the following error: 0xC0000035
But honestly I don't know if this has anything to do with this problem or if it was there always.

TLDR: Every time HWInfo was started in one session the PC would not reboot on the next cycle. Solved the problem by not starting HWInfo at all.
 
Hello Guys,
I stumbled upon this thread because yesterday I had the same problem as DanRaj.

My System:

- OS: Win11 23H2
- MB: Gigabyte B650 Aorus Elite AX V2
- RAM: GSkill Trident Z5 Neo DDR5, EXPO enabled
- CPU: Ryzen 7 7800X3D
- CPU Cooler: NZXT Kraken
- GPU: RTX 4080 Super
- Drives: 3x Samsung NVME + Kingston Sata SSD

I was using my PC in this constellation with HWInfo installed for 7-8 months without any issues.
I always start HWInfo manually when I want to check something. Yesterday I saw that there was a new update V 8.20 so I installed it.
After that I checked some sensor readings and a message popped up that HWInfo detected a conflict with NZXT Cam (It never did this before but there was a CAM Update recently)
Next I decided to restart my PC.

Like DanRaj's System also mine wouldn't post this time so after 10 minutes I forced a shutdown pressing the power button on the case. After that the system booted without a problem.
I immediately thought it must be something related to HWInfo because this was the only change I made this day. I reproduced the problem a few times till i was certain I knew what it was.
For now i solved the problem by just not opening HWInfo. I did not try to install an older version of HWInfo.

I also checked event viewer and the only error I could find was this one with Event ID 2: Session "PerfDiag Logger" failed to start with the following error: 0xC0000035
But honestly I don't know if this has anything to do with this problem or if it was there always.

TLDR: Every time HWInfo was started in one session the PC would not reboot on the next cycle. Solved the problem by not starting HWInfo at all.

It could be this problem: https://www.overclock.net/threads/a...-occasional-0d-codes-failure-to-boot.1812272/
Wondering if it will happen also if you run HWiNFO without CAM.
 
It could be this problem: https://www.overclock.net/threads/a...-occasional-0d-codes-failure-to-boot.1812272/
Wondering if it will happen also if you run HWiNFO without CAM.
Hello Martin,

Thank you for your quick reply.

You are right, it seems to be the same problem. Not running CAM and only running HWInfo solves the problem, the PC will boot just fine.
Also only running CAM alone works.
As soon as i start both applications in one sessions the same thing happens again. Only using one of the two immediately solves the issue.
Also only disabling CAM from Autostart at Startup doesn't help.

EDIT: Maybe I should add that running afterburner + CAM works just fine.

I guess I have four options:

- Not using HWInfo at all because I need CAM for fan and pump speed.
- Just living with the problem since I only use HWInfo occasionally
- Go back to an air cooler
- You think updating the BIOS would solve something? I am running F30 from May 2024. I don't really want to update because it seems the new versions only do something for the ryzen 9000 series and I don't want to interfere in a perfectly running system (except for this little CAM/HWInfo problem).

Also thanks for your work on HWInfo and providing it to us for free.
 
The problem is most likely a collision between HWiNFO and CAM, that's why you also get the warning in new version.
HWiNFO (and several other tools) feature mechanisms to avoid such conflicts but CAM doesn't seem to have this. So a solution might be to report this to CAM and they fix it in their software. There's nothing more we can do on our side - HWiNFO supports the mechanism but the other app needs to support it as well.
 
The problem is most likely a collision between HWiNFO and CAM, that's why you also get the warning in new version.
HWiNFO (and several other tools) feature mechanisms to avoid such conflicts but CAM doesn't seem to have this. So a solution might be to report this to CAM and they fix it in their software. There's nothing more we can do on our side - HWiNFO supports the mechanism but the other app needs to support it as well.
I will report to NZXT/CAM and just wait and see what happens.
It seems like a lot of people are unhappy with the latest (CAM)update and the way it registers CPU Temps among other things.
Thanks again!
 
If anyone is interested, this is the answer i got from NZXT Support:

____________________________________________________________

Hi there,

I understand you're experiencing conflicts between CAM and HWiNFO that are causing system restart issues. We're aware of this compatibility concern and our development team is actively working on implementing better software coexistence mechanisms in CAM.

In the meantime, here are a few potential workarounds you can try:

1. Run HWiNFO in sensor-only mode while using CAM
2. Adjust the sensor polling rates in both applications to reduce conflicts
3. Consider using only one monitoring software at a time until we release an update

We'll be addressing this compatibility issue in an upcoming CAM update. For now, if you need to use both applications, we recommend closing one completely before launching the other to avoid system stability issues.

I've forwarded your report to our development team to help them better understand the impact of this issue.

Thanks,

Your friends at NZXT
 
Back
Top