Aplication terminates

Chike

Active Member
I had vers. 5.02-2575 terminated unexpectedly ywice already in couple of hours.
Code:
Faulting application name: HWiNFO64.exe, version: 5.0.2.0, time stamp: 0x55aca891
Faulting module name: HWiNFO64.exe, version: 5.0.2.0, time stamp: 0x55aca891
Exception code: 0xc0000005
Fault offset: 0x0000000000026a47
Faulting process id: 0x16e4
Faulting application start time: 0x01d0c3bab56306ca
Faulting application path: ...\hw64_502\HWiNFO64.exe
Faulting module path: ...\hw64_502\HWiNFO64.exe
Report Id: 9ce427b8-2fb1-11e5-a847-d43d7eba52c7
 
What have you been running when it crashed, sensors?
Did it crash after some while, or immediately after start?
Please describe your HWiNFO configuration and attach the respective HWiNFO Debug File capturing the crash.
 
Three threads of Prime95 and other programs like IE, same as always.
It did happen after a while, can't say exactly when, no notification, I just noticed the one sensor I have (CPU Package temperature) is gone.
Been a while and it haven't happened again, I set debug mode and will send it if it happens again.
Fault offset was the same in both cases it happened.

EDIT: about Debug Write Direct(checked), few minutes after I launch HWiNFO and file size is still 0
 
Don't worry about the DBG file size - after you close HWiNFO (or when it crashes) and you refresh the folder contents, the file will have the correct size.
 
So finally after quite some time I have noticed HWiNFO is not running today.
I han't say the machine is 100% (under clocked/volted) so it may have something to do with it.

The forum didn't make it easy to attach a file this size...
 

Attachments

  • HWiNFO64.001.zip
    5 MB · Views: 3
  • HWiNFO64.002.zip
    4.1 MB · Views: 2
I don't see anything suspicious there.
Has the system also reported that HWiNFO64 was terminated or it did just disappear ?
Are you sure there's nothing in the system that could kill it ?
If you have HWiNFO automatically starting during boot, you might check in the Windows Task Scheduler whether the HWiNFO task doesn't have a maximum run time limit ("Stop the task if it runs longer than:").
 
Faulting application name: HWiNFO64.exe, version: 5.0.2.0, time stamp: 0x55aca891
Faulting module name: HWiNFO64.exe, version: 5.0.2.0, time stamp: 0x55aca891
Exception code: 0xc0000005
Fault offset: 0x0000000000026a47
Faulting process id: 0x1388
Faulting application start time: 0x01d0df416232c0db
Faulting application path:...\hw64_502\HWiNFO64.exe
Faulting module path: ...\hw64_502\HWiNFO64.exe
Report Id: e2e26a04-4cdb-11e5-a0f6-d43d7eba52c7
 
I have checked and don't see anything wrong there. Are you sure the machine is stable and no other applications fail ?
It might be interesting to see another DBG from another crash if possible.
 
Martin said:
I have checked and don't see anything wrong there. Are you sure the machine is stable and no other applications fail ?
It might be interesting to see another DBG from another crash if possible.
Nope, can't say it's 100% stable, but the offset is the same for all occurrences.
I'll keep testing and update if it happens again
 
Back
Top