Windows Live Mail crash

[stackz]

xp sp3

I'm currently using latest builds of ESS and Windows Live Mail, but this issue has occured with all v4 builds. The crash doesn't always happen, probably around 30/40% of the time. Basically I start WLM, it signs in and then instead of seeing the spam toolbar this is what I see (http://www.wilderssecurity.com/showthread.php?p=1562290#post1562290).

WLM's spam filtering is disabled.

I've got no other software installed that injects into WLM. Is there any work around or fix for this apart from disabling email client integration?

[stackz]

Is there anyone else experiencing this issue, or I am I just 'the chosen one'?

[stratoc]

im only using eav at the mo. but i have seen this twice on 64 bit 7.

[flipsen]

same problem here..

[stratoc]

i think the problem is with windows mail. i had the occaisonal crash with the following configs and solved it by moving back to thunderbird.
outpost pro (on its own)
outpost pro + eav
eset smart.

win 7 64 bit, yahoo mail

[Marcos]

Please do the following:

1, Click the link in the crash report message and, with the message kept open, look up the referenced log file. Make a backup copy of it, close the crash report message
2, create a SysInspector log while Windows Mail is running

Compress both files, put your nick in the archive's name, upload it to an ftp (if you don't have any I'll provide you one) and let me know when done. If possible, try to find out the pattern causing the problem to occur (e.g. when you receive / send email, when a spam email is recognized, etc).

Also please provide the following information:
1, what protocol you use (POP3/POP3S, IMAP,...)
2, which of the following makes a difference:
- disabling antispam protection
- disabling POP3 checking in the main setup tree (F5) -> Email client protection -> POP3,POP3S -> untick Enable POP3 checking
- disabling integration with the email client
- installing EAV instead of ESS (try if possible)
3, what version of ESS you use (in this case it's clear that you use the last one 4.0.467, but it's crucial information if anyone reports a problem now or in the future)

regards,

Marcos

[Davec2]

I'm using Windows Live Mail with Vista and ESS (latest version), and am seeing this crash once or twice per day.

Error log shows:
Problem Event Name: BEX
Application Name: wlmail.exe
Application Version: 14.0.8089.726
Application Timestamp: 4a6ce53d
Fault Module Name: MSMAIL.DLL
Fault Module Version: 14.0.8089.726
Fault Module Timestamp: 4a6ce58f
Exception Offset: 0000cf34
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.0.6002.2.2.0.768.2
Locale ID: 4105

I have just turned off WLM spam filtering and will see if it makes a difference.

[flipsen]

different one here:

Problem signature:
Problem Event Name: APPCRASH
Application Name: wlmail.exe
Application Version: 14.0.8089.726
Application Timestamp: 4a6ce53d
Fault Module Name: eplgOE.dll
Fault Module Version: 4.0.437.0
Fault Module Timestamp: 4a0c1bb2
Exception Code: c0000005
Exception Offset: 0001738d
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1043
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789


Using windows 7 x64 and EAV

[flipsen]

any updates?

[Marcos]

I've asked for some logs, but nobody has provided them yet. At least you can try installing the latest version 4.0.474 to see if it makes a difference, otherwise please provide the requested logs for perusal.

[flipsen]

Ok....
-{ Quote: "1, Click the link in the crash report message and, with the message kept open, look up the referenced log file. Make a backup copy of it, close the crash report message." }-

What link?

[Marcos]

When an application crashes, a Dr Watson warning with a link to the crash log shows up.

[flipsen]

-{ Quote: "When an application crashes, a Dr Watson warning with a link to the crash log shows up." }-

Not here on windows 7 x64... the only thing showing up is what i posted above.

[agoretsky]

Hello,

ESET Smart Security v4.0.474.0 was released earlier today. Can you confirm the behavior occurs with this build of the software?

Regards,

Aryeh Goretsky

[stackz]

I've got all the logs required including crash.dmp. Where do I send them to?

[stackz]

??? ???

[Davec2]

Well I turned off WLM spam filtering about one week ago and have not had WLM crash since. I am using version 4.0.467.0 with Windows 7.

[stackz]

Ive always had WLM spam filtering disabled. I'm on xp sp3 and the problems persist with the latest ESS build. I'm still waiting for feedback as to where to send the logs.

[Davec2]

Well, I thought it had gone away, but had two WLM crash in the past 5 days, and I am now running the latest ESS 4.0.474.0.
Both crash showing problem event name BEX. I really have no idea if this is caused by ESET as the fault module is showing msmail.dll

[evildust]

I always had this bug with all build of NOD32 4.xx and now with 4.2 beta

Windows 7 Ultimate x64

[bachor]

Oh I reported that bug to local eset distributor.. 2 months ago?!

I found a temporary solution - you need to enter BIOS and turn off XD-bit feature (on Intel processors).

But I think problem is somewhere deeper.. belive me 0xc0000005 error on wlmail is only a top of a huge mountain of problems with eset and 0x0000005 errors. - i'm on my way to check it.. :)

[evildust]

I have only a crash, no code of error. I have a AMD CPU.

[bachor]

Yes but on AMD processorss XD-bit feature is called Enhanced Virus Protection so you need to turn that feature off. (or NX-bit.. so many names for that same technology)

Solution no 2 - uninstall ESET Smart Security and install ESET nod32 (version 4 seems to be good) - test failed - crashing on nod32 too

[evildust]

I know this kind of options in bios but I have not it in my motherboard.

[bachor]

4.2.35 released - can anyone check this?
Crashing

<Event xmlns="http://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="2010-03-11T09:04:39.000000000Z" />
<EventRecordID>30308</EventRecordID>
<Channel>Application</Channel>
<Computer> </Computer>
<Security />
</System>
- <EventData>
<Data>wlmail.exe</Data>
<Data>14.0.8089.726</Data>
<Data>4a6ce53d</Data>
<Data>MSMAIL.DLL</Data>
<Data>14.0.8089.726</Data>
<Data>4a6ce58f</Data>
<Data>c0000005</Data>
<Data>0000cbf8</Data>
<Data>344</Data>
<Data>01cac0f9e0263bdc</Data>
<Data>C:\Program Files (x86)\Windows Live\Mail\wlmail.exe</Data>
<Data>C:\Program Files (x86)\Windows Live\Mail\MSMAIL.DLL</Data>
<Data>1ef78ffe-2ced-11df-8211-001de05f933f</Data>
</EventData>
</Event>

[bachor]

Ok, I worte to local support that in 4.2.35 is not working and as an anwser I get..

"You can download 4.2.35 from our site (it'll be available till next friday). It should be fixed in that version."

So can anyone confirm this bug under 4.2.35 too? *puppy*

[stackz]

Crash confirmed for ESS 4.2.35.0 on xp sp3 x86 and Win 7 x64.
Win 7 eventlog:
-{ Quote: "
Faulting application name: wlmail.exe, version: 14.0.8089.726, time stamp: 0x4a6ce53d
Faulting module name: MSMAIL.DLL, version: 14.0.8089.726, time stamp: 0x4a6ce58f
Exception code: 0xc0000005
Fault offset: 0x0000cf34
Faulting process id: 0x9cc
Faulting application start time: 0x01cac3e76a211a64
Faulting application path: C:\Program Files (x86)\Windows Live\Mail\wlmail.exe
Faulting module path: C:\Program Files (x86)\Windows Live\Mail\MSMAIL.DLL
" }-
Same problem I've had all along, I guess it's a result of timing/subclassing in that the WLMail menu is created twice, but no ESS menu.

I'm glad I've had it disabled. :D

[agoretsky]

Hello,

Can you please Marco the information he outlined in this (http://www.wilderssecurity.com/showpost.php?p=1578462&postcount=6) earlier message? That will be helpful in investigating the issue.

Regards,

Aryeh Goretsky


-{ Quote: "Crash confirmed for ESS 4.2.35.0 on xp sp3 x86 and Win 7 x64.
Win 7 eventlog:

Same problem I've had all along, I guess it's a result of timing/subclassing in that the WLMail menu is created twice, but no ESS menu.

I'm glad I've had it disabled. :D" }-

[bachor]

Twicely created WLMail menu and no ESET menu. It happends only with ESET EAV or SS installed (it's from my mails with eset support)

216803

Also please provide the following information:
1, what protocol you use (POP3/POP3S, IMAP,...)
A: POP3 / POP3S

2, which of the following makes a difference:
- disabling antispam protection
A: doesn't help

- disabling POP3 checking in the main setup tree (F5) -> Email client protection -> POP3,POP3S -> untick Enable POP3 checking
A: doesn't help

- disabling integration with the email client
A: doesn't help

- installing EAV instead of ESS (try if possible)
A: doesn't help

3, what version of ESS you use (in this case it's clear that you use the last one 4.0.467, but it's crucial information if anyone reports a problem now or in the future)
A: 4.0.467 (EN and PL / EAV and SS) and 4.2.35 (EN / EAV)

I provided files to local support (SysInspector only, dumps where 200mb+ and they gave up - didn't ask anymore). :lurking:

[bachor]

Version 4.2.40.10 (PL / EAV)
First thing after installing 4.2.40 and running WLM was.. 0xc0000005 error.
So I gave it second chance.. cold reboot.. running WLM and.. 0xc0000005 error.

Hopefully it's turning on.. without that error so I can check mails.. I bet in next version it will crash everytime I run WLM so I won't even be able to write an e-mail to support.. no case - no problem. :D ;D

Bot there's something new! Top menu is not anymore created twicely.. :argh:


Can anyone else confirm it too?

[bachor]

Ok I finally solved it!

My licence is out of date and I unsintalled nod. No more crashes :thumb: :argh:

Ach, and uninstaller seems to be f-_-ed up too, had to manualy remove eamonm.sys from services because my system at every boot up wasn't able to start that service (file was removed by uninstaller earlier). :thumbd:

-{ Quote: "00:18 < bachor> C:\Windows\system32>sc delete eamonm
00:18 < bachor> [SC] DeleteService SUKCES" }-