Windows Messenger crash on XP

[Fodor]

Help!

Whenever my computer starts, I get the following message:

msmsgs.exe - Application Error
The instruction at "0x77fc23cf" referenced memory at "0x1db40ff6". The
memory could not be "written".

Being a programmer, this tells that msmsgs.exe (Window Messenger) was
attempting to access a memory location outside of it's process space. Bad
Messenger! (slap on hand!)

The question is, how do I make it stop crashing? I'm out of contact with my
"exclusively Microsoft applications" company until I can get this problem
fixed.

I read a message about a conflict with DirectX 9, which I did recently
install. It would have been nice to know about the conflict before hand.
That just doesn't seem like it should be the problem, though. With all of
the DirectX 9 applications out there, how can so many people still be
running Windows Messenger?

Thanks,

Kevin

[Jonathan Kay [MVP]]

Greetings Kevin,

Actually the DirectX 9 issue is a problem with Direct X 9.0's DirectPlay Universal Plug and
Play (UPnP) files, the Internet Connection Firewall's UPnP support, and Messenger's UPnP
support. All of this was fixed in DirectX 9a (which would be the version you're using if you
just installed DirectX 9).

Another common cause of this error is is Norton Antivirus 2003. To fix it, open Norton
Antivirus (Right-click on the Norton Antivirus icon in the System Tray/Notification Area (by
the clock), choose 'Open Norton Antivirus'), click Options, then Instant Messenger then
uncheck MSN Instant Messenger and click OK. Then try running Messenger again.
____________________________________________
Jonathan Kay
Windows MVP, Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com

"Fodor" > wrote in message
news:681e29cec14d94f93fb5a73d6b7b3d21@TeraNews...
> Help!
>
> Whenever my computer starts, I get the following message:
>
> msmsgs.exe - Application Error
> The instruction at "0x77fc23cf" referenced memory at "0x1db40ff6". The
> memory could not be "written".
>
> Being a programmer, this tells that msmsgs.exe (Window Messenger) was
> attempting to access a memory location outside of it's process space. Bad
> Messenger! (slap on hand!)
>
> The question is, how do I make it stop crashing? I'm out of contact with my
> "exclusively Microsoft applications" company until I can get this problem
> fixed.
>
> I read a message about a conflict with DirectX 9, which I did recently
> install. It would have been nice to know about the conflict before hand.
> That just doesn't seem like it should be the problem, though. With all of
> the DirectX 9 applications out there, how can so many people still be
> running Windows Messenger?
>
> Thanks,
>
> Kevin
>
>

[Fodor]

Hi Jonathan,

Yikes! The DirectX that was installed directly off of the Microsoft/Digital
Anvil Freelancer CD was infact DirectX 9, not DirectX 9a. I was very
surprised to see DirectX 9a come up when I went to Windows Update. I
installed it and am now connected again. You the man!

Thanks!

Kevin

"Jonathan Kay [MVP]" > wrote in message
...
> Greetings Kevin,
>
> Actually the DirectX 9 issue is a problem with Direct X 9.0's DirectPlay
Universal Plug and
> Play (UPnP) files, the Internet Connection Firewall's UPnP support, and
Messenger's UPnP
> support. All of this was fixed in DirectX 9a (which would be the version
you're using if you
> just installed DirectX 9).
>
> Another common cause of this error is is Norton Antivirus 2003. To fix it,
open Norton
> Antivirus (Right-click on the Norton Antivirus icon in the System
Tray/Notification Area (by
> the clock), choose 'Open Norton Antivirus'), click Options, then Instant
Messenger then
> uncheck MSN Instant Messenger and click OK. Then try running Messenger
again.
> ____________________________________________
> Jonathan Kay
> Windows MVP, Messenger
> Associate Expert
> http://www.microsoft.com/windowsxp/expertzone/
> Messenger Resources - http://messenger.jonathankay.com
>
> "Fodor" > wrote in message
> news:681e29cec14d94f93fb5a73d6b7b3d21@TeraNews...
> > Help!
> >
> > Whenever my computer starts, I get the following message:
> >
> > msmsgs.exe - Application Error
> > The instruction at "0x77fc23cf" referenced memory at "0x1db40ff6". The
> > memory could not be "written".
> >
> > Being a programmer, this tells that msmsgs.exe (Window Messenger) was
> > attempting to access a memory location outside of it's process space.
Bad
> > Messenger! (slap on hand!)
> >
> > The question is, how do I make it stop crashing? I'm out of contact with
my
> > "exclusively Microsoft applications" company until I can get this
problem
> > fixed.
> >
> > I read a message about a conflict with DirectX 9, which I did recently
> > install. It would have been nice to know about the conflict before hand.
> > That just doesn't seem like it should be the problem, though. With all
of
> > the DirectX 9 applications out there, how can so many people still be
> > running Windows Messenger?
> >
> > Thanks,
> >
> > Kevin
> >
> >
>
>

[Jonathan Kay [MVP]]

Hi Kevin,

Glad to hear it =).
____________________________________________
Jonathan Kay
Windows MVP, Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com


"Fodor" > wrote in message
news:973982dffefa1f53f2aac377cbafa49a@TeraNews...
> Hi Jonathan,
>
> Yikes! The DirectX that was installed directly off of the Microsoft/Digital
> Anvil Freelancer CD was infact DirectX 9, not DirectX 9a. I was very
> surprised to see DirectX 9a come up when I went to Windows Update. I
> installed it and am now connected again. You the man!
>
> Thanks!
>
> Kevin
>
> "Jonathan Kay [MVP]" > wrote in message
> ...
> > Greetings Kevin,
> >
> > Actually the DirectX 9 issue is a problem with Direct X 9.0's DirectPlay
> Universal Plug and
> > Play (UPnP) files, the Internet Connection Firewall's UPnP support, and
> Messenger's UPnP
> > support. All of this was fixed in DirectX 9a (which would be the version
> you're using if you
> > just installed DirectX 9).
> >
> > Another common cause of this error is is Norton Antivirus 2003. To fix it,
> open Norton
> > Antivirus (Right-click on the Norton Antivirus icon in the System
> Tray/Notification Area (by
> > the clock), choose 'Open Norton Antivirus'), click Options, then Instant
> Messenger then
> > uncheck MSN Instant Messenger and click OK. Then try running Messenger
> again.
> > ____________________________________________
> > Jonathan Kay
> > Windows MVP, Messenger
> > Associate Expert
> > http://www.microsoft.com/windowsxp/expertzone/
> > Messenger Resources - http://messenger.jonathankay.com
> >
> > "Fodor" > wrote in message
> > news:681e29cec14d94f93fb5a73d6b7b3d21@TeraNews...
> > > Help!
> > >
> > > Whenever my computer starts, I get the following message:
> > >
> > > msmsgs.exe - Application Error
> > > The instruction at "0x77fc23cf" referenced memory at "0x1db40ff6". The
> > > memory could not be "written".
> > >
> > > Being a programmer, this tells that msmsgs.exe (Window Messenger) was
> > > attempting to access a memory location outside of it's process space.
> Bad
> > > Messenger! (slap on hand!)
> > >
> > > The question is, how do I make it stop crashing? I'm out of contact with
> my
> > > "exclusively Microsoft applications" company until I can get this
> problem
> > > fixed.
> > >
> > > I read a message about a conflict with DirectX 9, which I did recently
> > > install. It would have been nice to know about the conflict before hand.
> > > That just doesn't seem like it should be the problem, though. With all
> of
> > > the DirectX 9 applications out there, how can so many people still be
> > > running Windows Messenger?
> > >
> > > Thanks,
> > >
> > > Kevin
> > >
> > >
> >
> >
>
>