Error 0x800cccd2 and other problems

don't worry about the finnish in screenshot, pertinent info at top of error
screen)

As seen I have a problem: the screenshot situation get's up everytime I try
to send and e-mail.
~"WLM has encountered a problem and needs to close"

Also, when reading news and want to forward or reply and/or (to group) ,
nothing happens even though I see the button getting pressed. And even that
doesn't happen anymore if I press a second time..


OS: WinXp SP2
WLM 12.0.1606 (installed yesterday) (DIDN'T import anything automatically
from IE)
IE7 (and OE6 still (luckily usable)

Mailccounts on both IE and WLM: Hotmail, Gmail and 2 others (all but Hotmail
IMAP)
Newsaccounts: local ISP (news.24online.fi) and news.microsoft.com, total
about 20 newsgroups followd



--
Tumppi
=================================
A lot learned from these newsgroups
Helsinki, FINLAND
(translations from/to FI not always accurate
=================================

"Windows live mail has encountered a problem and needs to close....."

I was having the same issue and I think I resolved it. WLM was crashing
randomly then after a few hours it happened everytime I started the program.
Since we have 3 computers all with Windows Live Mail and 2 were working
perfectly I was able to compare settings between them. The offending one had
different security settings than the other 2.

I went to: Tools>Safety Options>Security and set Virus Protection to
"Internet zone" & "Warn me when other applications try to send mail as me."
These are the only 2 selections turned on.

Strangely enough, when WLM said it needed to shut down I was still able to
ignore the message and open the Tools menu.

It has been several hours since I did this and so far perfect.

I hope this works for you. This has been very frustrating for me.

"Thomas Wendell" wrote:

"Thomas Wendell" <tumppiw_nospam@xxxxxx> wrote in message
news:#$L0xDtpIHA.3860@xxxxxx

(attachment shows crash is in module ntdll.dll)

Most likely cause is an incompatible third-party program.
Additional symptom information would be the
Stack Back Trace related to this crash
and a list of the modules loaded at the time.
E.g. ntdll.dll is likely a victim of a bad call
or some other kind of interference with it.


---