HWINFO64 Crash Windows Server 2022 (Closing)

[renanlofiego]

Hello, I have a problem with my Windows Server, an HP where I use the environment sensor to monitor the ambient temperature from afar, it always closes HWINFO64 at a random time and I lose connection with the sensor. It's been happening for some time but it's only now that it's been updated to version 8.0 that I decide to make contact, I tried to open it in debug mode but I don't know if it's stuck, it seems to be heavy and freezing and then I had the idea of going to the Windows event viewer and I found some things there... I'll post the logs below in the body of the post.

###########################################

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2024-04-07T23:35:55.8356762Z" />
<EventRecordID>4370454</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>SERVER</Computer>
<Security />
</System>
- <EventData>
<Data>1343344230871704425</Data>
<Data>5</Data>
<Data>BEX64</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>HWiNFO64.EXE</Data>
<Data>8.0.5400.0</Data>
<Data>6603dbc4</Data>
<Data>HWiNFO64.EXE</Data>
<Data>8.0.5400.0</Data>
<Data>6603dbc4</Data>
<Data>00000000005344fd</Data>
<Data>c0000409</Data>
<Data>0000000000000002</Data>
<Data />
<Data>\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.149e7292-8124-4a1a-b917-4e66707f63f8.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.89963fc6-042a-4fdd-b238-7a53aa24c62f.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.94cb0591-2922-412e-a85c-726b0835ac3b.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d0e44ea1-d7f9-400b-9b67-b41ebd4da37a.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1b3999c3-9290-4798-b410-37f3efd85158.tmp.txt</Data>
<Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_HWiNFO64.EXE_6dfdb7c8ca30911c51cc9aa4322d481fbb7f4fa0_a139382a_89879376-7f06-45e7-b907-14d76a7388fe</Data>
<Data />
<Data>0</Data>
<Data>4c6bf80b-2914-411b-b661-5cf855afeb0a</Data>
<Data>268435456</Data>
<Data>d2f456e1ca8c3cbd22a48475ec2da369</Data>
<Data>0</Data>
</EventData>
</Event>

###############################

Faulting application name: HWiNFO64.EXE, version: 8.0.5400.0, time stamp: 0x6603dbc4
Faulting module name: HWiNFO64.EXE, version: 8.0.5400.0, time stamp: 0x6603dbc4
Exception code: 0xc0000409
Fault offset: 0x00000000005344fd
Faulting process id: 0x2d04
Faulting application start time: 0x01da8942bb9a56c9
Faulting application path: C:\Program Files\HWiNFO64\HWiNFO64.EXE
Faulting module path: C:\Program Files\HWiNFO64\HWiNFO64.EXE
Report Id: 4c6bf80b-2914-411b-b661-5cf855afeb0a
Faulting package full name:
Faulting package-relative application ID:

##################################

 

[renanlofiego]

I disabled PresentMon Support to test and I was able to debug and in less than 1 minute there was a problem...

 

[Martin]

Please try this build and let me know if it fixes the problem: www.hwinfo.com/beta/hwi64_801_5412.zip
If not, please send me a full DBG file of crash.

 

[renanlofiego]

Please try this build and let me know if it fixes the problem: www.hwinfo.com/beta/hwi64_801_5412.zip
If not, please send me a full DBG file of crash.

It seems to have been resolved, it's been working normally for 1 hour. I'll leave it running normal and until tomorrow to confirm if it's been resolved. Anything return here.

Thanks

 

[renanlofiego]

Hello, stopping by to thank you and say that everything is OK, stopped closing!

Now another question about some sensors or almost all of them pointing out negative temperatures and peak hours of 192º, I know that it may be some kind of problem or something that can be done here. That machine is an HP Desktop server.

I made some red arrow notes.

 

[Martin]

Those erratic values seem to be due to a failure to read them. Is there perhaps some other software accessing the IPMI? Another suggestion might be to install the IPMI driver.

 

[renanlofiego]

Those erratic values seem to be due to a failure to read them. Is there perhaps some other software accessing the IPMI? Another suggestion might be to install the IPMI driver.

I use ZABBIX to monitor my entire network and there it also makes these readings but there it doesn't return these values, but there is also a shorter response time, these values here it is like millisecond peaks that HWINFO64 can pick up, I believe that even if it's a problem ZABBIX wouldn't pick it up. That IPMI driver, name now I'm not remembering. Thank you

 

[Martin]

Try without ZABBIX if you will then observe those invalid peaks. If yes, then the problem is a collision between them.

 

[renanlofiego]

Try without ZABBIX if you will then observe those invalid peaks. If yes, then the problem is a collision between them.

I disabled ZABBXI but it still kept giving the random read errors... I hadn't noticed if before the problem that was closing it showed these reading errors like this but anyway, I think I would have noticed it because I use it on my desktop of my personal PC, I keep monitoring it as you can see in one of the photos I'm forwarding.

About IPMI I found it installed as generic on my Windows Server.