Windows messenger suddenly crashing with an Event ID 1000 & 1001

[tknight@ix.nonetspamcom.com]

Within the last two days my windows messenger has crashed and had to
close twice, both times leaving this error in the application event
log:

Event ID: 1000
Faulting application msmsgs.exe version 4.7.0.2009 faulting module
msmsgs.exe version 4.7.0.2009, fault address 0x000d0cb2.

There's also an accompanying Event ID: 1001 following the 1000.

At the time I had only messenger (one conversation) and IE6 running.
Messenger had also been running for several hours, in case that's
relevant, although I've been connected for even longer and with
several conversations and up to three IE windows open at once in the
past without any problems other than the very occasional involuntary
logoff. The only software I've added recently was the last three
critical patches from windows update I needed (821557, 822925,
KB824105) and this didn't start happening until a few days after I'd
applied those.

The crash report states there's no resolution but suggests upgrading
to version 5, which I know will lose me the MSN add-ins which I'm
currently using with messenger to monitor my hotmail inbox. Will
upgrading get rid of this error? Messenger has been as stable as a
rock up to now.

I'm running XP home with all critical patches and hotfixes applied,
DirectX 8.1 (haven't updated that yet).

Thanks in advance for any help.

T.

[Jonathan Kay [MVP]]

Greetings,

I know this sounds completely and totally ridiculous, but have you rebooted recently? A
simple log off/log on or reboot might fix this problem.

As a "quick fix" if this still occurs, you may just want to use System Restore. To do so,
click Start, then Help & Support, then "Undo changes to my computer using System Restore" and
restore back to three days ago when the problem didn't exist.
____________________________________________
Jonathan Kay
Windows MVP, Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com

> wrote in message ...
> Within the last two days my windows messenger has crashed and had to
> close twice, both times leaving this error in the application event
> log:
>
> Event ID: 1000
> Faulting application msmsgs.exe version 4.7.0.2009 faulting module
> msmsgs.exe version 4.7.0.2009, fault address 0x000d0cb2.
>
> There's also an accompanying Event ID: 1001 following the 1000.
>
> At the time I had only messenger (one conversation) and IE6 running.
> Messenger had also been running for several hours, in case that's
> relevant, although I've been connected for even longer and with
> several conversations and up to three IE windows open at once in the
> past without any problems other than the very occasional involuntary
> logoff. The only software I've added recently was the last three
> critical patches from windows update I needed (821557, 822925,
> KB824105) and this didn't start happening until a few days after I'd
> applied those.
>
> The crash report states there's no resolution but suggests upgrading
> to version 5, which I know will lose me the MSN add-ins which I'm
> currently using with messenger to monitor my hotmail inbox. Will
> upgrading get rid of this error? Messenger has been as stable as a
> rock up to now.
>
> I'm running XP home with all critical patches and hotfixes applied,
> DirectX 8.1 (haven't updated that yet).
>
> Thanks in advance for any help.
>
> T.

[tknight@spamix.nenotcom.com]

Yes, I have rebooted - I shut down and turn it off every night. This
crashing doesn't happen every day (didn't happen yesterday), I was
just concerned because it never used to happen at all and I was
wondering if it were possibly a known issue with the last three
critical patches I installed. Some conflict between msmsgs 4.7
expecting an older version of a system file that got replaced by one
of them or something.

Might it have anything to do with the userenv 1517 warnings I've
started getting since installing sp1a? I get one of those every time I
shut down now, but didn't mention it before because KB 810616
basically said it was supposed to do that (behavior is by design). At
about the same time information events about something called EAPOL
stopped being logged too, and there were always some every day before
sp1a.

T.

On Wed, 10 Sep 2003 12:34:00 -0400, "Jonathan Kay [MVP]"
> wrote:

>Greetings,
>
>I know this sounds completely and totally ridiculous, but have you rebooted recently? A
>simple log off/log on or reboot might fix this problem.
>
>As a "quick fix" if this still occurs, you may just want to use System Restore. To do so,
>click Start, then Help & Support, then "Undo changes to my computer using System Restore" and
>restore back to three days ago when the problem didn't exist.
>____________________________________________
>Jonathan Kay
>Windows MVP, Messenger
>Associate Expert
>http://www.microsoft.com/windowsxp/expertzone/
>Messenger Resources - http://messenger.jonathankay.com
>
> wrote in message ...
>> Within the last two days my windows messenger has crashed and had to
>> close twice, both times leaving this error in the application event
>> log:
>>
>> Event ID: 1000
>> Faulting application msmsgs.exe version 4.7.0.2009 faulting module
>> msmsgs.exe version 4.7.0.2009, fault address 0x000d0cb2.
>>
>> There's also an accompanying Event ID: 1001 following the 1000.
>>
>> At the time I had only messenger (one conversation) and IE6 running.
>> Messenger had also been running for several hours, in case that's
>> relevant, although I've been connected for even longer and with
>> several conversations and up to three IE windows open at once in the
>> past without any problems other than the very occasional involuntary
>> logoff. The only software I've added recently was the last three
>> critical patches from windows update I needed (821557, 822925,
>> KB824105) and this didn't start happening until a few days after I'd
>> applied those.
>>
>> The crash report states there's no resolution but suggests upgrading
>> to version 5, which I know will lose me the MSN add-ins which I'm
>> currently using with messenger to monitor my hotmail inbox. Will
>> upgrading get rid of this error? Messenger has been as stable as a
>> rock up to now.
>>
>> I'm running XP home with all critical patches and hotfixes applied,
>> DirectX 8.1 (haven't updated that yet).
>>
>> Thanks in advance for any help.
>>
>> T.
>
>