Jump to content

Application Error ToastNotify.dll 8.0.319


Recommended Posts

In ESS 8.0.319.0 i get Event ID 1000 application error about ToastNotify.dll
at every boot. Just updated to 8.0.319.0 and this error was never present in 8.0 312.

 

I've tried repair and installing ESS 319 again, didn't fix it..

I tried Pre-release update and the error went away.

Just rebooted a couple of times but it looks like it went away.

 

I set it back to Regular update and the error comes back in event log.

 

I'm using ESS 8.0 319 and Windows 8.1 Pro x64 with all current updates installed.

 

The full error log:

 

Loggnamn:      Application
Källa:         Application Error
Datum:         2015-07-30 20:38:49
Händelse-ID:   1000
Aktivitetskategori:(100)
Nivå:          Fel
Nyckelord:     Klassiskt
Användare:     Saknas
Dator:         Cr
Beskrivning:
Felet uppstod i programmet med namn: egui.exe, version 8.0.319.0, tidsstämpel 0x559d2313
, felet uppstod i modulen med namn: ToastNotify.dll, version 8.0.319.0, tidsstämpel 0x559d2398
Undantagskod: 0xc0000005
Felförskjutning: 0x0000000000002f3e
Process-ID: 0x1328
Programmets starttid: 0x01d0caf693b63190
Sökväg till program: C:\Program Files\ESET\ESET Smart Security\egui.exe
Sökväg till modul: C:\Program Files\ESET\ESET Smart Security\ToastNotify.dll
Rapport-ID: 3766c2c2-36ea-11e5-8b6a-a0369f2d029b
Fullständigt namn på felaktigt paket:
Program-ID relativt till felaktigt paket:
Händelsens XML-data:
<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-07-30T18:38:49.000000000Z" />
    <EventRecordID>129512</EventRecordID>
    <Channel>Application</Channel>
    <Computer>CR</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>1328</Data>
    <Data>01d0caf693b63190</Data>
    <Data>C:\Program Files\ESET\ESET Smart Security\egui.exe</Data>
    <Data>C:\Program Files\ESET\ESET Smart Security\ToastNotify.dll</Data>
    <Data>3766c2c2-36ea-11e5-8b6a-a0369f2d029b</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Edited by Corso
Link to comment
Share on other sites

  • 2 weeks later...

Hi,

 

I get the same error everytime I'm shutting down my computer, which is a little bit odd.

 

Problem signature

APPCRASH

Application: egui.exe

Faulting module: ToastNotify.dll​

App version: 8.0.319.0​

Exception code: c0000005

 

c0000005 is a memory access error, mostly caused by a programming error (or a RAM error, but my RAM is fine). So I think it is an error within the application that can only be fixed by the development team of ESET. 

 

Link to comment
Share on other sites

I get it at boot, when windows 10 is starting.

Almost at every boot.

 

Using win 10 pro x64 with latest updates.

Link to comment
Share on other sites

  • ESET Insiders

I have the same issue using ESS version 8.0.319.0 using Win 8.1 Professional; the issue doesn't exist with the ESS Beta 9.0.117.0.

Edited by TJP
Link to comment
Share on other sites

  • Administrators

I confirm the issue is already fixed in v9 beta and will be fixed in v8.0.320 too in case there's another build of v8 released in the future.

Link to comment
Share on other sites

  • ESET Insiders

Let's wait until v9 is released or install v9 beta version. Currently there are no plans to build 8.0.320.

 

That is disappointing but understandable if version 9's release is very soon.

Link to comment
Share on other sites

Let's wait until v9 is released or install v9 beta version. Currently there are no plans to build 8.0.320.

 

 

I wouldn't recommend to use a beta version on a productive system or a workstation.

 

You can actually bypass the error reports by using a group policy of Windows (works only with Pro versions of Windows).

 

In Local Group Policy Editor switch to Computer Configuration -> Administrative Templates -> Windows Components ->  Advanced Error Reporting Settings

There just use the List of applications to be excluded template and add egui.exe to it.

 

To clarify things: This is not a fix for the error caused by ESET, it will just no longer produce error reports for this specific error.​​

Edited by marble
Link to comment
Share on other sites

  • 1 month later...
  • Administrators

When version 9 comes out , its been already too long for windows 10 

 

Soon. However, there's no connection between support for Windows 10 and the release of v9 as existing versions of our products are already Windows 10 compatible.

Link to comment
Share on other sites

  • 2 months later...

 

When version 9 comes out , its been already too long for windows 10 

 

Soon. However, there's no connection between support for Windows 10 and the release of v9 as existing versions of our products are already Windows 10 compatible.

 

2015 is coming to an end. Any news about v9 release?

 

Enjoy your holidays in this festive season!

Link to comment
Share on other sites

  • 1 month later...

 

Let's wait until v9 is released or install v9 beta version. Currently there are no plans to build 8.0.320.

 

 

I wouldn't recommend to use a beta version on a productive system or a workstation.

 

You can actually bypass the error reports by using a group policy of Windows (works only with Pro versions of Windows).

 

In Local Group Policy Editor switch to Computer Configuration -> Administrative Templates -> Windows Components ->  Advanced Error Reporting Settings

There just use the List of applications to be excluded template and add egui.exe to it.

 

To clarify things: This is not a fix for the error caused by ESET, it will just no longer produce error reports for this specific error.​​

 

thanks!

 

but now it's start with v9 too

Edited by mantra
Link to comment
Share on other sites

 

but now it's start with v9 too

 

Really? I haven't had any problems so far with version 9 and Windows 10.

 

I also see that there is a small error in my previous post: You can find the Advanced Error Reporting Settings at the same location but located in Windows Error Reporting folder.

Link to comment
Share on other sites

  • 3 months later...

i have this version of NOD, it says i'm uptodate and there is nothing about v9. what do i do about this toast error i'm getting under Win10?

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...