[Ham-Computers] RE: COMPUTER LOCK UP

Wed, 27 Mar 2002 22:59:41 -0500

If you have a 'restore' CD, use it. If not, find a locally owned computer shop
and let them fix your computer. Unless you are very computer savvy, trying to
fix this yourself is apt to be nothing but more trouble. 

----------
From: wxfreqrs <[email protected]>
To: [email protected]
Subject: Re: [Ham-Computers] RE:  COMPUTER LOCK UP
Date: Wednesday, March 27, 2002 10:46 PM

ok its going to be a bugaboo however you have given me somewhere to start
thanks
don

Peace, Through Superior Firepower
----- Original Message -----
From: "Hsu, Aaron" <[email protected]>
To: <[email protected]>
Cc: <[email protected]>
Sent: Wednesday, March 27, 2002 9:18 PM
Subject: [Ham-Computers] RE: COMPUTER LOCK UP

Wow, this one's not going to be easy.  Being modular, Windows has components
that do dedicated jobs.  In this case MSGSRV32 is Windows' internal 32-bit
"Message Server".  From what I remember, MSGSRV32 handles messages passed
between various Windows components; all it is is a "middle man" - a courier
of sorts.  For example, some part of Windows (let's call it the "source")
needs to send some instructions to another part of Windows (the
destination).  The source sends the message to MSGSRV32.  MSGSRV32 then
forwards the message to the destination - at this point, MSGSRV32 has done
it's job and is sitting quietly idle.  However the source is probably
waiting for some type of response from the destination and it might not be
able to proceed until it does receives a response.  So, it might try sending
the message to MSGSRV32 again to be forwarded.  It might flood MSGSRV32 with
repeated messages.  On top of that, other Windows components might be trying
to send messages and can't because MSGSRV32 is busy handling the source's
request(s).  If you were to hit CTRL-ALT-DEL at this time, it would seem
that MSGSRV32 is not responding because it's *really* busy.  So, is MSGSRV32
really not responding?  Not really - the source or destination is really the
culprit.  But, Windows thinks that MSGSRV32 is to blame because it's too
busy to respond to Windows' request for a "pulse" so Windows tells you that
MSGSRV32 is not responding.

OK, where does that leave us.  Unfortunately, in many respects, SOL.  It's
hard to diagnose this particular issue because MSGSRV32 is not to blame.
The problem can be caused by faulty hardware drivers (MSGSRV32 handles PnP
messages), a bad or corrupt network configuration, poorly written apps that
don't cover all the possible responses expected, even corrupted media files
(.wav, .avi, .mpg, etc.).  Not an easy task at all.

The first thing I would do in diagnosing your system is to take a look at
your "startup" files.  This includes CONFIG.SYS, AUTOEXEC.BAT, WININIT.INI
(and .BAK), items in the STARTUP group, and the various "RUN" keys in the
registry.  I'd parse through info and remove any un-necessary startup items.
Many people have chat programs, media players, cursor enhancements,
screensavers, background image flippers, etc. that are extraneous to Windows
and can cause poential problems.  Temporarily removing these will help
narrow the  possibilities.  If the lock-ups still occur, check to make sure
the all OS patches are applied, especially security patches.  There are
*MANY* known security flaws in Windows that allow a mischieveous hacker to
remotely crash a system just by sending a few incorrectly formatted network
packets.  Another suggestion is to un-install any old programs or hardware
drivers that are no longer in use.  Windows does not automatically remove
the associated drivers when you physically remove a hardware component.

There's a *LOT* of info on MSGSRV32 and lock-ups available on Microsoft's
Knowledgebase and on the net.  Unfortunately, there's no one easy solution.
If you can provide additional information, someone might be able to assist
further.

73,

  - Aaron, NN6O

-----Original Message-----
From: wxfreqrs [mailto:[email protected]]
Sent: Wednesday, March 27, 2002 4:52 PM
To: [email protected]; [email protected];
HAM-COMPUTERS
Subject: [Ham-Computers] COMPUTER LOCK UP

My computer is about a yr old
it used to LOCK UP about once a week
now its up to a couple times a day
when I check to see why I get the following
msgsrv32 not responding
is this a file if so can I get it replaced if not what do I do to stop the
lock ups
don

Peace, Through Superior Firepower

--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---
_______________________________________________
Ham-Computers mailing list
[email protected]
http://mailman.qth.net/mailman/listinfo/ham-computers
_______________________________________________
Ham-Computers mailing list
[email protected]
http://mailman.qth.net/mailman/listinfo/ham-computers

_______________________________________________
Ham-Computers mailing list
[email protected]
http://mailman.qth.net/mailman/listinfo/ham-computers