msnmsgr_exe causing problem

[John's News 2]

I am not sure which patch installed to cause my problem, it started around 2
weeks ago.
SP2 had already been running for a couple of weeks, it did not
immediately cause this condition.

System W2000 updated, and IE6 updated. Kerio personal fire wall.
****************
I try to start OE and in the Task Manager msnmsgr.exe activates, this is
blocking OE from running.

The time clock is running like an attempt to start, just hung.
CPU Usage from 10 to 16 % then settles to 10 to 12 %.

The messenger is deactivated in System, ...
I can kill the msnmsg.exe ( PID 1956; CPU 00; CPU Time 0:00:00; Mem Usage
7,928K; Mem Delta 0 k; Handles 136; User Obje 9;....

Also running is ntvdm.exe [ 1888; 00; 0:00:00; Mem Usage 940-1244K; mem
delta 0; Handles 86; User Obje 4; ]
2 sub items monwow.exe and wowexec.exe. with no overhead....
(kill wowexec.exe nothing improved) 30 minutes pass.
(kill monwoe.exe nothing improved -- this action also dropped out the
NTVDM.EXE)

msnmsgr.exe is still on the Task Manager list, Kill it and the OE will
start up.

I have Messenger disabled, It seems you have to do this to kill some handle
in OE,
which is open trying to start messenger ahead of OE.

My outlook Express has been hanging, until I physically go in and kill the
running msnmsg.exe
Search of knowledge base did not find the msnmsgr Error message.
1. Error message big red X, (manmsgr.exe - Application Error) "The
exception Privileged instruction.
(0xc0000096) occurred in the application at location 0x011239d4
Click on OK to terminate the program.
2. (the more recent message) msnmsgr.exe Error;
The instructions at "0x01123a34 referenced memory at "0x00000112". The
memory could not be "written". Click on OK to terminate the program.


****************

 

[PA Bear]

See the Messenger-related part (bottom half) of
http://www.insideoe.com/problems/performance.htm#slowstart
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE/OE), AH-VSOP

WinXP SP2: What's New for Internet Explorer and Outlook Express
http://www.microsoft.com/windowsxp/sp2/ieoeoverview.mspx

What You Should Know About Spyware
http://www.microsoft.com/athome/security/spyware/default.mspx

There is no 'silver bullet' solution to hijackware
http://go.microsoft.com/fwlink/?LinkId=33131

 

[John's News 2]

Thanks, I have examined all these items, including security 360;
I have/had used S&D, Spyware blaster, and CWShredderr,
and virus protector, anti-hijacking. My computer is uptodate.
Cleaned and compacted messages, news.

MSNmessenger, and Windows messenger, are configured where neither
should activate,
unless, I go out there and execute them, moreover I only use the MSN
Messenger, then just occasionally.
I still think that what the main culprit is, some small file is still
executing to stand by (msn messenger) mainly because msnmsgr.exe is loaded.
However, you understand it only loads after/with, and/but ahead of when
the OE mail has been called up. I have checked this in Task Manager,
and procexp, also I see the msn 6.2 icon flash "in, then out", in the
tool tray upon calling the OE program.
It may be somewhere in the .net, or I may keep fooling with it till
I figure
how to edit the OE .dll, and maybe remove the calling of msnmsgr.exe
or were ever it might be.
thanks,
John Zachary

See the Messenger-related part (bottom half) of
http://www.insideoe.com/problems/performance.htm#slowstart
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE/OE), AH-VSOP

WinXP SP2: What's New for Internet Explorer and Outlook Express
http://www.microsoft.com/windowsxp/sp2/ieoeoverview.mspx

What You Should Know About Spyware
http://www.microsoft.com/athome/security/spyware/default.mspx

There is no 'silver bullet' solution to hijackware
http://go.microsoft.com/fwlink/?LinkId=33131

I am not sure which patch installed to cause my problem, it started around
2
weeks ago.
SP2 had already been running for a couple of weeks, it did not
immediately cause this condition.

System W2000 updated, and IE6 updated. Kerio personal fire wall.
****************
I try to start OE and in the Task Manager msnmsgr.exe activates, this is
blocking OE from running.

The time clock is running like an attempt to start, just hung.
CPU Usage from 10 to 16 % then settles to 10 to 12 %.

The messenger is deactivated in System, ...
I can kill the msnmsg.exe ( PID 1956; CPU 00; CPU Time 0:00:00; Mem Usage
7,928K; Mem Delta 0 k; Handles 136; User Obje 9;....

Also running is ntvdm.exe [ 1888; 00; 0:00:00; Mem Usage 940-1244K; mem
delta 0; Handles 86; User Obje 4; ]
2 sub items monwow.exe and wowexec.exe. with no overhead....
(kill wowexec.exe nothing improved) 30 minutes pass.
(kill monwoe.exe nothing improved -- this action also dropped out the
NTVDM.EXE)

msnmsgr.exe is still on the Task Manager list, Kill it and the OE will
start up.

I have Messenger disabled, It seems you have to do this to kill some
handle
in OE,
which is open trying to start messenger ahead of OE.

My outlook Express has been hanging, until I physically go in and kill the
running msnmsg.exe
Search of knowledge base did not find the msnmsgr Error message.
1. Error message big red X, (manmsgr.exe - Application Error) "The
exception Privileged instruction.
(0xc0000096) occurred in the application at location 0x011239d4
Click on OK to terminate the program.
2. (the more recent message) msnmsgr.exe Error;
The instructions at "0x01123a34 referenced memory at "0x00000112". The
memory could not be "written". Click on OK to terminate the program.


****************

 

[PA Bear]

What?

<paste>
Regedit and navigate to this key:

HKEY_CLASSES_ROOT
\CLSID
\{FB7199AB-79BF-11d2-8D94-0000F875C541}
\InProcServer32

In the right-hand pane, double-click on the (Default) value and delete
whatever is entered there, leaving it blank. Click OK. Now perform exactly
the same step with the key directly underneath, namely

HKEY_CLASSES_ROOT
\CLSID
\{FB7199AB-79BF-11d2-8D94-0000F875C541}
\LocalServer32

Once both (Default) values are empty, OE will open normally.
</paste>
--
~PA Bear

Thanks, I have examined all these items, including security 360;
I have/had used S&D, Spyware blaster, and CWShredderr,
and virus protector, anti-hijacking. My computer is uptodate.
Cleaned and compacted messages, news.

MSNmessenger, and Windows messenger, are configured where neither
should activate,
unless, I go out there and execute them, moreover I only use the MSN
Messenger, then just occasionally.
I still think that what the main culprit is, some small file is
still executing to stand by (msn messenger) mainly because msnmsgr.exe is
loaded. However, you understand it only loads after/with, and/but
ahead of when the OE mail has been called up. I have checked this in
Task Manager, and procexp, also I see the msn 6.2 icon flash "in, then
out", in the tool tray upon calling the OE program.
It may be somewhere in the .net, or I may keep fooling with it
till I figure
how to edit the OE .dll, and maybe remove the calling of msnmsgr.exe
or were ever it might be.
thanks,
John Zachary

See the Messenger-related part (bottom half) of
http://www.insideoe.com/problems/performance.htm#slowstart
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE/OE), AH-VSOP

WinXP SP2: What's New for Internet Explorer and Outlook Express
http://www.microsoft.com/windowsxp/sp2/ieoeoverview.mspx

What You Should Know About Spyware
http://www.microsoft.com/athome/security/spyware/default.mspx

There is no 'silver bullet' solution to hijackware
http://go.microsoft.com/fwlink/?LinkId=33131

I am not sure which patch installed to cause my problem, it started
around 2
weeks ago.
SP2 had already been running for a couple of weeks, it did not
immediately cause this condition.

System W2000 updated, and IE6 updated. Kerio personal fire wall.
****************
I try to start OE and in the Task Manager msnmsgr.exe activates,
this is blocking OE from running.

The time clock is running like an attempt to start, just hung.
CPU Usage from 10 to 16 % then settles to 10 to 12 %.

The messenger is deactivated in System, ...
I can kill the msnmsg.exe ( PID 1956; CPU 00; CPU Time 0:00:00; Mem
Usage 7,928K; Mem Delta 0 k; Handles 136; User Obje 9;....

Also running is ntvdm.exe [ 1888; 00; 0:00:00; Mem Usage 940-1244K;
mem delta 0; Handles 86; User Obje 4; ]
2 sub items monwow.exe and wowexec.exe. with no overhead....
(kill wowexec.exe nothing improved) 30 minutes pass.
(kill monwoe.exe nothing improved -- this action also dropped out
the NTVDM.EXE)

msnmsgr.exe is still on the Task Manager list, Kill it and the OE
will start up.

I have Messenger disabled, It seems you have to do this to kill some
handle
in OE,
which is open trying to start messenger ahead of OE.

My outlook Express has been hanging, until I physically go in and
kill the running msnmsg.exe
Search of knowledge base did not find the msnmsgr Error message.
1. Error message big red X, (manmsgr.exe - Application Error)
"The exception Privileged instruction.
(0xc0000096) occurred in the application at location 0x011239d4
Click on OK to terminate the program.
2. (the more recent message) msnmsgr.exe Error;
The instructions at "0x01123a34 referenced memory at "0x00000112". The
memory could not be "written". Click on OK to terminate the
program.


****************

 

[John's News 2]

thank you,
thank you,
That fixed the problem, Outlook Express is back to normal.
thanks again.
john zachary

What?

<paste>
Regedit and navigate to this key:

HKEY_CLASSES_ROOT
\CLSID
\{FB7199AB-79BF-11d2-8D94-0000F875C541}
\InProcServer32

In the right-hand pane, double-click on the (Default) value and delete
whatever is entered there, leaving it blank. Click OK. Now perform exactly
the same step with the key directly underneath, namely

HKEY_CLASSES_ROOT
\CLSID
\{FB7199AB-79BF-11d2-8D94-0000F875C541}
\LocalServer32

Once both (Default) values are empty, OE will open normally.
</paste>
--
~PA Bear

Thanks, I have examined all these items, including security 360;
I have/had used S&D, Spyware blaster, and CWShredderr,
and virus protector, anti-hijacking. My computer is uptodate.
Cleaned and compacted messages, news.

MSNmessenger, and Windows messenger, are configured where neither
should activate,
unless, I go out there and execute them, moreover I only use the MSN
Messenger, then just occasionally.
I still think that what the main culprit is, some small file is
still executing to stand by (msn messenger) mainly because msnmsgr.exe is
loaded. However, you understand it only loads after/with, and/but
ahead of when the OE mail has been called up. I have checked this in
Task Manager, and procexp, also I see the msn 6.2 icon flash "in, then
out", in the tool tray upon calling the OE program.
It may be somewhere in the .net, or I may keep fooling with it
till I figure
how to edit the OE .dll, and maybe remove the calling of msnmsgr.exe
or were ever it might be.
thanks,
John Zachary

See the Messenger-related part (bottom half) of
http://www.insideoe.com/problems/performance.htm#slowstart
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE/OE), AH-VSOP

WinXP SP2: What's New for Internet Explorer and Outlook Express
http://www.microsoft.com/windowsxp/sp2/ieoeoverview.mspx

What You Should Know About Spyware
http://www.microsoft.com/athome/security/spyware/default.mspx

There is no 'silver bullet' solution to hijackware
http://go.microsoft.com/fwlink/?LinkId=33131

John's News 2 wrote:
I am not sure which patch installed to cause my problem, it started
around 2
weeks ago.
SP2 had already been running for a couple of weeks, it did not
immediately cause this condition.

System W2000 updated, and IE6 updated. Kerio personal fire wall.
****************
I try to start OE and in the Task Manager msnmsgr.exe activates,
this is blocking OE from running.

The time clock is running like an attempt to start, just hung.
CPU Usage from 10 to 16 % then settles to 10 to 12 %.

The messenger is deactivated in System, ...
I can kill the msnmsg.exe ( PID 1956; CPU 00; CPU Time 0:00:00; Mem
Usage 7,928K; Mem Delta 0 k; Handles 136; User Obje 9;....

Also running is ntvdm.exe [ 1888; 00; 0:00:00; Mem Usage 940-1244K;
mem delta 0; Handles 86; User Obje 4; ]
2 sub items monwow.exe and wowexec.exe. with no overhead....
(kill wowexec.exe nothing improved) 30 minutes pass.
(kill monwoe.exe nothing improved -- this action also dropped out
the NTVDM.EXE)

msnmsgr.exe is still on the Task Manager list, Kill it and the OE
will start up.

I have Messenger disabled, It seems you have to do this to kill some
handle
in OE,
which is open trying to start messenger ahead of OE.

My outlook Express has been hanging, until I physically go in and
kill the running msnmsg.exe
Search of knowledge base did not find the msnmsgr Error message.
1. Error message big red X, (manmsgr.exe - Application Error)
"The exception Privileged instruction.
(0xc0000096) occurred in the application at location 0x011239d4
Click on OK to terminate the program.
2. (the more recent message) msnmsgr.exe Error;
The instructions at "0x01123a34 referenced memory at "0x00000112". The
memory could not be "written". Click on OK to terminate the
program.


****************

 

[PA Bear]

That was what I was referring to in...

YW.
--
~PA Bear

thank you,
thank you,
That fixed the problem, Outlook Express is back to normal.
thanks again.
john zachary

What?

<paste>
Regedit and navigate to this key:

HKEY_CLASSES_ROOT
\CLSID
\{FB7199AB-79BF-11d2-8D94-0000F875C541}
\InProcServer32

In the right-hand pane, double-click on the (Default) value and delete
whatever is entered there, leaving it blank. Click OK. Now perform
exactly the same step with the key directly underneath, namely

HKEY_CLASSES_ROOT
\CLSID
\{FB7199AB-79BF-11d2-8D94-0000F875C541}
\LocalServer32

Once both (Default) values are empty, OE will open normally.
</paste>
--
~PA Bear

Thanks, I have examined all these items, including security 360;
I have/had used S&D, Spyware blaster, and CWShredderr,
and virus protector, anti-hijacking. My computer is uptodate.
Cleaned and compacted messages, news.

MSNmessenger, and Windows messenger, are configured where neither
should activate,
unless, I go out there and execute them, moreover I only use the MSN
Messenger, then just occasionally.
I still think that what the main culprit is, some small file is
still executing to stand by (msn messenger) mainly because
msnmsgr.exe is loaded. However, you understand it only loads
after/with, and/but
ahead of when the OE mail has been called up. I have checked this
in Task Manager, and procexp, also I see the msn 6.2 icon flash
"in, then out", in the tool tray upon calling the OE program.
It may be somewhere in the .net, or I may keep fooling with it
till I figure
how to edit the OE .dll, and maybe remove the calling of msnmsgr.exe
or were ever it might be.
thanks,
John Zachary


See the Messenger-related part (bottom half) of
http://www.insideoe.com/problems/performance.htm#slowstart
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE/OE), AH-VSOP

WinXP SP2: What's New for Internet Explorer and Outlook Express
http://www.microsoft.com/windowsxp/sp2/ieoeoverview.mspx

What You Should Know About Spyware
http://www.microsoft.com/athome/security/spyware/default.mspx

There is no 'silver bullet' solution to hijackware
http://go.microsoft.com/fwlink/?LinkId=33131

John's News 2 wrote:
I am not sure which patch installed to cause my problem, it
started around 2
weeks ago.
SP2 had already been running for a couple of weeks, it did
not immediately cause this condition.

System W2000 updated, and IE6 updated. Kerio personal fire wall.
****************
I try to start OE and in the Task Manager msnmsgr.exe activates,
this is blocking OE from running.

The time clock is running like an attempt to start, just hung.
CPU Usage from 10 to 16 % then settles to 10 to 12 %.

The messenger is deactivated in System, ...
I can kill the msnmsg.exe ( PID 1956; CPU 00; CPU Time 0:00:00;
Mem Usage 7,928K; Mem Delta 0 k; Handles 136; User Obje 9;....

Also running is ntvdm.exe [ 1888; 00; 0:00:00; Mem Usage
940-1244K; mem delta 0; Handles 86; User Obje 4; ]
2 sub items monwow.exe and wowexec.exe. with no overhead....
(kill wowexec.exe nothing improved) 30 minutes pass.
(kill monwoe.exe nothing improved -- this action also dropped
out the NTVDM.EXE)

msnmsgr.exe is still on the Task Manager list, Kill it and the
OE will start up.

I have Messenger disabled, It seems you have to do this to kill
some handle
in OE,
which is open trying to start messenger ahead of OE.

My outlook Express has been hanging, until I physically go in and
kill the running msnmsg.exe
Search of knowledge base did not find the msnmsgr Error message.
1. Error message big red X, (manmsgr.exe - Application Error)
"The exception Privileged instruction.
(0xc0000096) occurred in the application at location 0x011239d4
Click on OK to terminate the program.
2. (the more recent message) msnmsgr.exe Error;
The instructions at "0x01123a34 referenced memory at
"0x00000112". The memory could not be "written". Click on OK
to terminate the program.


****************