TMEEJM_WND not responding error

[Graham]

Hi,

We have a Toshiba Portege R100 running XP pro, with the latest critical
updates applied.

Since last weekend, we have started to have a problem when shutting
down. The process/program TMEEJM_WND is not responding.

Does anyone know what this process is ? Is is part of XP ?

It seems to coincide with having had previous problems with Outlook
opening an Excel or other office attachment, but that may be complete
separate issue and nothing to do with the TMEEJM issue.

I have searched for other references to this process and can find a
couple of people asking the same question on other forums but no answers
so far.

Any help/suggestions gratefully received. Is there an easy way for me to
see which application/executable/dll is the source of TMEEJM_WND ?

Cheers

Graham

 

[Rick \Nutcase\ Rogers]

Hi,

A short search reveals only a few instances of similar error messages, and
they all seem to be related to various Toshiba products. I would speculate
that a system-specific process (this does not appear to be a Windows
process) is not terminating properly. I would suspect it is a Toshiba driver
file that is causing the problem. You might try manually killing processes
before shutting down to see if you can isolate it, or you may also want to
contact Toshiba support to see if this is a known issue.

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Windows
Windows isn't rocket science! That's my other hobby!

Associate Expert - WinXP - Expert Zone

 

[Graham]

Hi,

Hi,

A short search reveals only a few instances of similar error messages, and
they all seem to be related to various Toshiba products.

Yes, I got a similar impression..

I would speculate
that a system-specific process (this does not appear to be a Windows
process) is not terminating properly. I would suspect it is a Toshiba driver
file that is causing the problem. You might try manually killing processes
before shutting down to see if you can isolate it, or you may also want to
contact Toshiba support to see if this is a known issue.

I should probably have said in the first post that I had contacted them
and am waiting to hear back ...
I'll post here when I hear from them.

Thanks for the response.. if anyone else knows what this is I would
appreciate knowing

Cheers

Graham