immediate hwinfo crash

speedfixer

New Member
Ryzen 5 3600x
Gigabyte B450 Aorus M
16G mem
ssd
GTX 1060 6G
all stock/auto settings - no tweaks

ZERO load

hwinfo ran once on install, then would not run - even before reboot

immediate crash: win event 1000


Obviously - can't set debug mode in interface.
Reason to try hwinfo: see temperature load during Division2 to see if I may better cooling.


What to do to make hwinfo run.
(Obviously I can try other software to see temps.)



david
 

Martin

HWiNFO Author
Staff member
Does the crash happen before the welcome screen with Run / Settings buttons?
 

speedfixer

New Member
No.
Nothing - not even a screen flicker.
Just the cursor implying an attempt to start the program - more like some kind of timeout.

I will examine all the logs more carefully to see if I can find something.

david
 

speedfixer

New Member
I had time to try again.

I do not have Riot Vanguard.

When I click on the desktop shortcut, I am asked to allow Hwinfo64 permission to change the system, then nothing.

System log entries:

Log Name: Application
Source: Application Error
Date: 5/14/2020 4:53:23 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Oakup
Description:
Faulting application name: HWiNFO64.EXE, version: 6.24.4120.0, time stamp: 0x5e7502c5
Faulting module name: HWiNFO64.EXE, version: 6.24.4120.0, time stamp: 0x5e7502c5
Exception code: 0xc0000417
Fault offset: 0x0000000000218434
Faulting process id: 0x2018
Faulting application start time: 0x01d62a4ad8e66031
Faulting application path: C:\Program Files (open)\HWiNFO64\HWiNFO64.EXE
Faulting module path: C:\Program Files (open)\HWiNFO64\HWiNFO64.EXE
Report Id: 1ee27247-08db-4740-95ab-8a99170df512
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-05-14T23:53:23.258275500Z" />
<EventRecordID>2459</EventRecordID>
<Channel>Application</Channel>
<Computer>Oakup</Computer>
<Security />
</System>
<EventData>
<Data>HWiNFO64.EXE</Data>
<Data>6.24.4120.0</Data>
<Data>5e7502c5</Data>
<Data>HWiNFO64.EXE</Data>
<Data>6.24.4120.0</Data>
<Data>5e7502c5</Data>
<Data>c0000417</Data>
<Data>0000000000218434</Data>
<Data>2018</Data>
<Data>01d62a4ad8e66031</Data>
<Data>C:\Program Files (open)\HWiNFO64\HWiNFO64.EXE</Data>
<Data>C:\Program Files (open)\HWiNFO64\HWiNFO64.EXE</Data>
<Data>1ee27247-08db-4740-95ab-8a99170df512</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>


----------------------------------
Log Name: Application
Source: Application Error
Date: 5/14/2020 4:53:23 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Oakup
Description:
Faulting application name: HWiNFO64.EXE, version: 6.24.4120.0, time stamp: 0x5e7502c5
Faulting module name: HWiNFO64.EXE, version: 6.24.4120.0, time stamp: 0x5e7502c5
Exception code: 0xc0000417
Fault offset: 0x0000000000218434
Faulting process id: 0x2018
Faulting application start time: 0x01d62a4ad8e66031
Faulting application path: C:\Program Files (open)\HWiNFO64\HWiNFO64.EXE
Faulting module path: C:\Program Files (open)\HWiNFO64\HWiNFO64.EXE
Report Id: 1ee27247-08db-4740-95ab-8a99170df512
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-05-14T23:53:23.258275500Z" />
<EventRecordID>2459</EventRecordID>
<Channel>Application</Channel>
<Computer>Oakup</Computer>
<Security />
</System>
<EventData>
<Data>HWiNFO64.EXE</Data>
<Data>6.24.4120.0</Data>
<Data>5e7502c5</Data>
<Data>HWiNFO64.EXE</Data>
<Data>6.24.4120.0</Data>
<Data>5e7502c5</Data>
<Data>c0000417</Data>
<Data>0000000000218434</Data>
<Data>2018</Data>
<Data>01d62a4ad8e66031</Data>
<Data>C:\Program Files (open)\HWiNFO64\HWiNFO64.EXE</Data>
<Data>C:\Program Files (open)\HWiNFO64\HWiNFO64.EXE</Data>
<Data>1ee27247-08db-4740-95ab-8a99170df512</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

-------------------------------------

Log Name: Application
Source: Application Error
Date: 5/14/2020 4:53:23 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Oakup
Description:
Faulting application name: HWiNFO64.EXE, version: 6.24.4120.0, time stamp: 0x5e7502c5
Faulting module name: HWiNFO64.EXE, version: 6.24.4120.0, time stamp: 0x5e7502c5
Exception code: 0xc0000417
Fault offset: 0x0000000000218434
Faulting process id: 0x2018
Faulting application start time: 0x01d62a4ad8e66031
Faulting application path: C:\Program Files (open)\HWiNFO64\HWiNFO64.EXE
Faulting module path: C:\Program Files (open)\HWiNFO64\HWiNFO64.EXE
Report Id: 1ee27247-08db-4740-95ab-8a99170df512
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-05-14T23:53:23.258275500Z" />
<EventRecordID>2459</EventRecordID>
<Channel>Application</Channel>
<Computer>Oakup</Computer>
<Security />
</System>
<EventData>
<Data>HWiNFO64.EXE</Data>
<Data>6.24.4120.0</Data>
<Data>5e7502c5</Data>
<Data>HWiNFO64.EXE</Data>
<Data>6.24.4120.0</Data>
<Data>5e7502c5</Data>
<Data>c0000417</Data>
<Data>0000000000218434</Data>
<Data>2018</Data>
<Data>01d62a4ad8e66031</Data>
<Data>C:\Program Files (open)\HWiNFO64\HWiNFO64.EXE</Data>
<Data>C:\Program Files (open)\HWiNFO64\HWiNFO64.EXE</Data>
<Data>1ee27247-08db-4740-95ab-8a99170df512</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>


david
 

Martin

HWiNFO Author
Staff member
Please unpack the attached ZIP file into the HWiNFO folder, then run it and see if it produced a HWiNFO64.DBG file. If yes, please attach it here.
 

Attachments

Top