Errors in System Log

[Dave-H]

I'm seeing these errors in my system log.
It doesn't happen on every session, but has now been happening off and on for a while.
Windows 10 22H2 64 bit.

This is the first one -

Faulting application name: HWiNFO64.EXE, version: 7.66.5271.0, time stamp: 0x655251a9
Faulting module name: HWiNFO64.EXE, version: 7.66.5271.0, time stamp: 0x655251a9
Exception code: 0xc0000005
Fault offset: 0x000000000053d79e
Faulting process ID: 0x1248
Faulting application start time: 0x01da1cae054fa844
Faulting application path: C:\Program Files\HWiNFO64\HWiNFO64.EXE
Faulting module path: C:\Program Files\HWiNFO64\HWiNFO64.EXE
Report ID: 9af90158-1842-4a16-817a-fba812a27ef6
Faulting package full name:
Faulting package-relative application ID:

Followed by this -

The backing-file for the real-time session "HWiNFO64" has reached its maximum size. As a result, new events will not be logged to this session until space becomes available. This error is often caused by starting a trace session in real-time mode without having any real-time consumers.

The first is an application error, the second is reported by Kernel-EventTracing.

There is no sign that HWiNFO isn't working at any point, the tray icons show no problems.

 

[Martin]

Do you have PresentMon support enabled and the sensor monitored in HWiNFO? If yes, try to disable it.

 

[Dave-H]

Thanks for the quick reply Martin!

Yes, I have checked, and PresentMon Support was enabled.
I didn't do that, so I assume it's enabled by default.

The sensors were enabled as well, and they still appear to be even after I've disable the PresentMon Support, as you can see from the screen grab.
Do I need to disable them all manually?

 

[Martin]

Disable PresetMon support in Global Settings and then start HWiNFO or open sensors again.

 

[Dave-H]

Thanks.
Closing and reopening the sensors window didn't change anything, I already tried that, but closing and reopening HWiNFO did the trick, those sensors are no longer in the list.
I will keep monitoring and see if the event log errors now happen again.

 

[Dave-H]

Is it OK to try re-enabling this function now the program has updated to 7.68?

 

[Martin]

Some PresentMon-related issues were fixed in v7.68 but I'm not sure if this one as well. Try and see...

 

[Dave-H]

Hi Martin.
I hope you had a good Christmas!
Just to report, after trying it for a while, that the crashes are still happening if PresentMon is enabled.
It doesn't seem to be quite as often as before, it was happening almost every day, now there are days when it doesn't happen.

Source HWiNFO64 Summary Stopped working Date ‎29/‎12/‎2023 18:41 Status Report sent Description Faulting Application Path: C:\Program Files\HWiNFO64\HWiNFO64.EXE Problem signature Problem Event Name: APPCRASH Application Name: HWiNFO64.EXE Application Version: 7.68.5300.0 Application Timestamp: 658162c5 Fault Module Name: HWiNFO64.EXE Fault Module Version: 7.68.5300.0 Fault Module Timestamp: 658162c5 Exception Code: c0000005 Exception Offset: 0000000000540dce OS Version: 10.0.19045.2.0.0.256.48 Locale ID: 2057 Additional Information 1: 6343 Additional Information 2: 63435ec168c70e60163d0d4675f5ea13 Additional Information 3: 5757 Additional Information 4: 575741256acca1b46c5535f208373a53 Extra information about the problem Bucket ID: d7f7c3ebc8ec5582a4cfec7a1e7353eb (1499677210178704363)

I will disable it again.
Cheers,
Dave.

 

[Dave-H]

Hi again Martin.
Sorry to report it crashed again today, with PresentMon disabled.
Unlike the previous crashes, where it didn't disappear from the system tray, this time it completely closed and had to be manually restarted.
A different entry in the Windows event log this time.

Faulting application name: HWiNFO64.EXE, version: 7.68.5300.0, time stamp: 0x658162c5 Faulting module name: ntdll.dll, version: 10.0.19041.3636, time stamp: 0x9b64aa6f Exception code: 0xc0000374 Fault offset: 0x00000000000ff349 Faulting process ID: 0x1228 Faulting application start time: 0x01da3b3aac099e18 Faulting application path: C:\Program Files\HWiNFO64\HWiNFO64.EXE Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report ID: afd3b348-2eb3-4a86-aa66-1dabae9bb247 Faulting package full name: Faulting package-relative application ID:

Cheers, Dave.

 

[Martin]

Can you capture this crash in HWiNFO Debug File?

 

[Dave-H]

I will try to do that.
Do I just need to enable debug mode?

 

[Martin]

Yes

 

[Dave-H]

Thanks, done!
Where will I find the crashlog after the next crash, assuming that there is one?

 

[Martin]

In the same folder as HWiNFO executable. The filename is HWiNFO64.DBG

 

[Dave-H]

Thanks, that file is already there, and I've tried to attach it here, but it's too big (368MB).
Debug mode was not enabled when the last crash happened, so I don't know if it would be any use to you anyway.
Should I perhaps delete it, and let HWiNFO generate a new one, which hopefully won't grow so large before the next crash?

 

[Martin]

You need to create a new one that will capture the crash. Then compress it and if still too large, try to upload to some public sharing place.

 

[Dave-H]

OK, I will do that.

 

[Dave-H]

OK Martin, here we are!
HWiNFO crashed again and shut down.

Faulting application name: HWiNFO64.EXE, version: 7.68.5300.0, time stamp: 0x658162c5 Faulting module name: HWiNFO64.EXE, version: 7.68.5300.0, time stamp: 0x658162c5 Exception code: 0xc0000005 Fault offset: 0x0000000000540dce Faulting process ID: 0x1c80 Faulting application start time: 0x01da3b7bd450893f Faulting application path: C:\Program Files\HWiNFO64\HWiNFO64.EXE Faulting module path: C:\Program Files\HWiNFO64\HWiNFO64.EXE Report ID: fd27079d-2704-4b53-800c-6bc1d974b7d4 Faulting package full name: Faulting package-relative application ID:

I've attached the debug file.
Zipped up with 7-Zip.
Hope it helps.
Cheers,
Dave.

 

[Martin]

Thanks. I think I found the bug, it will be fixed in the next (Beta) build.
I can also see another problem that might be related to the initial issue and increased load, working on that...

 

[Dave-H]

Good to hear Martin, glad to have been able to help.
FWIW, I also use the same version of HWiNFO on Windows 98 and Windows XP on my multi-boot machine, and they show no sign of any problems.
They are using the 32 bit version of course, so I guess the issue is either only with Windows 10, or, more likely, only with the 64 bit version.
Cheers, Dave.