NOD32 vs Win10 Tech Preview

[mjmcmahon67 0]

Let me start by saying that I understand that Windows 10 is a Technical Preview and that it's expected that there may be some compatibility issues with existing software.  That said, I'm a long time customer and proponent of ESET's products and I wanted to bring the apparent incompatibility to their attention.

 

I'm running Windows 10 Build 10074 and am having regular crashes of the ESET GUI.  The issue doesn't appear to be critical (the GUI resets itself), but it warrants attention.  Windows crashlog is as follows:

 

Log Name:      Application
Source:        Application Error
Date:          05/03/2015 20:00:01
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Lenovo-V570
Description:
Faulting application name: egui.exe, version: 8.0.312.0, time stamp: 0x54c8de34
Faulting module name: MSVCR110.dll, version: 11.0.51106.1, time stamp: 0x5098826e
Exception code: 0xc0000005
Fault offset: 0x000000000005ebe4
Faulting process id: 0x17f8
Faulting application start time: 0x01d0860d3f2faca9
Faulting application path: C:\Program Files\ESET\ESET NOD32 Antivirus\egui.exe
Faulting module path: C:\Program Files\ESET\ESET NOD32 Antivirus\MSVCR110.dll
Report Id: 581f7aa6-1aa5-437e-b85d-aa42599e5dfd
Faulting 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="2015-05-04T02:00:01.000000000Z" />
    <EventRecordID>766</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Lenovo-V570</Computer>
    <Security />
  </System>
  <EventData>
    <Data>egui.exe</Data>
    <Data>8.0.312.0</Data>
    <Data>54c8de34</Data>
    <Data>MSVCR110.dll</Data>
    <Data>11.0.51106.1</Data>
    <Data>5098826e</Data>
    <Data>c0000005</Data>
    <Data>000000000005ebe4</Data>
    <Data>17f8</Data>
    <Data>01d0860d3f2faca9</Data>
    <Data>C:\Program Files\ESET\ESET NOD32 Antivirus\egui.exe</Data>
    <Data>C:\Program Files\ESET\ESET NOD32 Antivirus\MSVCR110.dll</Data>
    <Data>581f7aa6-1aa5-437e-b85d-aa42599e5dfd</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

 

I'm happy to provide additional data if necessary.  I'm aware of the required changes to the HIPS setting and it is disabled.  I've also enabled pre-release builds, but they've been unsuccessful in obtaining a working version.  I've seen this on the last few Windows 10 builds.

 

Thanks,

 

Mike

[rugk 397]

We've already discussed this here. Please follow the instructions there to set the settings to generate memory dumps.

Although you're using ESET NOD32 Antivirus the steps are the same.

Edited May 11, 2015 by rugk

[mjmcmahon67 0]

We've already discussed this here. Please follow the instructions there to set the settings to generate memory dumps.

Although you're using ESET NOD32 Antivirus the steps are the same.

rugk -

 

I'd seen that thread but had discarded it since it was for ESS rather than NOD32.  I will generate the memory dumps and submit as you suggested.

 

Thanks!

 

Mike

[yeoldfart 143]

strange, not a glitch whatsoever here on W10 TP 10074 x64

[mjmcmahon67 0]

Interestingly, I was all prepared to submit dumps tonight but (knock on wood) I haven't seen a crash yet.  I'll keep my eyes peeled and I've got the instructions from the other thread to submit dumps.

 

Thanks all,

 

Mike