Jump to content

System Inspector crash on load (0xc000005)

Recommended Posts

Windows 10 1903


Sysinspector v10.7.79.0

I have discovered that the Sysinspector tool in ESSP (and possibly other versions of ESET software that include the tool) crashes on load. It can create sysinspector logs, but you can not view them. according to the windows event viewer, the sysinspector is crashing with a 0xc000005 error, with the faulting module being listed as the sysinspector program it self (an internal program error?)


The stand alone version of the sysinspector downloaded from the eset site works, but is an older version and takes forever to come up.


Fault bucket 2243708203262627270, type 4

Event Name: APPCRASH

Response: Not available

Cab Id: 0


Problem signature:

P1: SysInspector.exe


P3: 5ca726a7

P4: SysInspector.exe


P6: 5ca726a7

P7: c0000005

P8: 00000000000399aa




Attached files:







These files may be available here:



Analysis symbol:

Rechecking for solution: 0

Report Id: 89c9e574-29d7-4838-bb51-ea278453d03c

Report Status: 268435456

Hashed bucket: 662e45029cc2e6d16f2340b923194dc6

Cab Guid: 0


Faulting application name: SysInspector.exe, version:, time stamp: 0x5ca726a7

Faulting module name: SysInspector.exe, version:, time stamp: 0x5ca726a7

Exception code: 0xc0000005

Fault offset: 0x00000000000399aa

Faulting process id: 0x5860

Faulting application start time: 0x01d5265210dec022

Faulting application path: C:\Program Files\ESET\ESET Security\SysInspector.exe

Faulting module path: C:\Program Files\ESET\ESET Security\SysInspector.exe

Report Id: 89c9e574-29d7-4838-bb51-ea278453d03c

Faulting package full name:

Faulting package-relative application ID:



- <System>
  <Provider Name="Application Error" />
  <EventID Qualifiers="0">1000</EventID>
  <TimeCreated SystemTime="2019-06-19T03:50:31.823535500Z" />
  <Security />
- <EventData>
  <Data>C:\Program Files\ESET\ESET Security\SysInspector.exe</Data>
  <Data>C:\Program Files\ESET\ESET Security\SysInspector.exe</Data>
  <Data />
  <Data />
Edited by cybot
Link to comment
Share on other sites

  • Administrators

Under HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Error Reporting\LocalDumps, create a DWORD value DumpType and set it to 2. Next reboot the machine and reproduce the crash.

While the notification about the crash being displayed on the screen, compress the dump, upload the archive here.

Link to comment
Share on other sites

  • Administrators

We were able to reproduce it with high-DPI scaling when connected through RDP. The change causing the issue was made in 2017. It will be fixed in the final v12.2.

Link to comment
Share on other sites

I don't know if I have High DPI enabled on my system, but it's good too know that it's a recognized issue that is due to be fixed 

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...