itman 1,806 Posted August 2, 2016 Posted August 2, 2016 Eset SS ver 8 .319, Win 10. Just upgraded to Win 10. Been getting the below error at shutdown/restart ever since the upgrade. Noticed there was a thread on this issue back in Feb. w/no resolution as far as I can determine. I believe that posting was for ver. 9. Appears to be a memory violation. Log Name: ApplicationSource: Application ErrorDate: 8/1/2016 4:55:50 PMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: XXX-PCDescription:Faulting application name: egui.exe, version: 8.0.319.0, time stamp: 0x559d2313Faulting module name: ToastNotify.dll, version: 8.0.319.0, time stamp: 0x559d2398Exception code: 0xc0000005Fault offset: 0x0000000000002f3eFaulting process id: 0x1320Faulting application start time: 0x01d1ec0c21bff1e7Faulting application path: C:\Program Files\ESET\ESET Smart Security\egui.exeFaulting module path: C:\Program Files\ESET\ESET Smart Security\ToastNotify.dllReport Id: c35f5502-9822-490a-acf0-356cd0377d15Faulting package full name:Faulting package-relative application ID:Event Xml:<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="2016-08-01T20:55:50.000000000Z" /> <EventRecordID>2026</EventRecordID> <Channel>Application</Channel> <Computer>Don-PC</Computer> <Security /> </System> <EventData> <Data>egui.exe</Data> <Data>8.0.319.0</Data> <Data>559d2313</Data> <Data>ToastNotify.dll</Data> <Data>8.0.319.0</Data> <Data>559d2398</Data> <Data>c0000005</Data> <Data>0000000000002f3e</Data> <Data>1320</Data> <Data>01d1ec0c21bff1e7</Data> <Data>C:\Program Files\ESET\ESET Smart Security\egui.exe</Data> <Data>C:\Program Files\ESET\ESET Smart Security\ToastNotify.dll</Data> <Data>c35f5502-9822-490a-acf0-356cd0377d15</Data> <Data> </Data> <Data> </Data> </EventData></Event>
Most Valued Members shocked 60 Posted August 4, 2016 Most Valued Members Posted August 4, 2016 have you tried to export the settings of the application and then use the eset removal tool, to completely remove ESS and reinstall it again, and after that import the settings?
itman 1,806 Posted August 4, 2016 Author Posted August 4, 2016 have you tried to export the settings of the application and then use the eset removal tool, to completely remove ESS and reinstall it again, and after that import the settings? I re-read the old Eset thread on this issue. Appears Eset never intended to fix the issue in ver. 9 rel. .319. Issue isn't causing me any issues that I can observe other than generating the event log entry. I will probably try to upgrade(again) to ver.9 now that I am on Win 10 and I have simplified my HIPS rules. However ver. 9 is so buggy, it will take me some time to get the courage to try it again.
Recommended Posts