cybot 1 Posted June 19, 2019 Share Posted June 19, 2019 (edited) Windows 10 1903 ESSP 12.1.34.0 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 P2: 10.7.79.0 P3: 5ca726a7 P4: SysInspector.exe P5: 10.7.79.0 P6: 5ca726a7 P7: c0000005 P8: 00000000000399aa P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC914.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC982.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC9A2.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC9A4.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC9D4.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_SysInspector.exe_8bf46cbe28d02d14db50a662d67fcf6d511f96c2_ee6e4bfc_223d13f8-a307-4797-a8bb-ad1273023770 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: 10.7.79.0, time stamp: 0x5ca726a7 Faulting module name: SysInspector.exe, version: 10.7.79.0, 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: - <Event xmlns="hxxp://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="2019-06-19T03:50:31.823535500Z" /> <EventRecordID>7953</EventRecordID> <Channel>Application</Channel> <Computer>MSI</Computer> <Security /> </System> - <EventData> <Data>SysInspector.exe</Data> <Data>10.7.79.0</Data> <Data>5ca726a7</Data> <Data>SysInspector.exe</Data> <Data>10.7.79.0</Data> <Data>5ca726a7</Data> <Data>c0000005</Data> <Data>00000000000399aa</Data> <Data>5860</Data> <Data>01d5265210dec022</Data> <Data>C:\Program Files\ESET\ESET Security\SysInspector.exe</Data> <Data>C:\Program Files\ESET\ESET Security\SysInspector.exe</Data> <Data>89c9e574-29d7-4838-bb51-ea278453d03c</Data> <Data /> <Data /> </EventData> </Event> Edited June 19, 2019 by cybot Link to comment Share on other sites More sharing options...
Administrators Marcos 5,404 Posted June 19, 2019 Administrators Share Posted June 19, 2019 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 More sharing options...
itman 1,786 Posted June 19, 2019 Share Posted June 19, 2019 Might be a problem with Win 10 1903. SysInspector works fine on Win 10 1809. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,404 Posted June 21, 2019 Administrators Share Posted June 21, 2019 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 More sharing options...
cybot 1 Posted June 23, 2019 Author Share Posted June 23, 2019 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 More sharing options...
Recommended Posts