Discussion Locked

Msgsrv32 (not responding)?!

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

In my tech service work, I've come across a slight problem: On a Computer Running Windows 95 with a Cyrix 133 MHz processor and 64 MB RAM (oldie and not-so-goodie, apparently), when I first boot the computer, it hangs after the Win95 splash page ends and the desktop view starts. Ctrl-Alt-Del shows "Msgsrv32 (not responding)". End Task kills the msgsrv, but doesn't help the boot process. On restart the computer boots up fine. I've tried removing many background processes to no avail. What's happening here? Microsoft.com is of little use. HELP!
Thanks!

15 replies

by dmiles

Windows 32 bit VxD-Message Server
It can be located at C:\Windows\System
MSDOS MSGSVR332.EXE
It is a small application around 12KB,and once you locate it you can double click and reinstall the application

by masteri3aster

I run almost an identical system at home, also kinda not so good, and I have had this same problem. It has been best in my experience to to get your Windows 95 cd, and/or system disk, and to find and replace the Msgrsv32 fileand then to run the program as said.

by tony hogan

I had this problem with a motherboard that had on-board sound card. The drivers installed by auto-detect are not completely correct and caused the system to do exactly what you've described. I downloaded new drivers from the vendor website to resolve the problem. I think this was a PCChips motherboard with Crystal audio drivers.

-tony

by gary

Strangely enough, I have a problem similar on a system with a Cyrix chip and 32 MB RAM Win 98. I run this computer as a proxy server (so as not to overtax the system). Occasionally it will lock up with Msgsrv32 not responding error message.
I close the error message and all is working again. Go figure. Never have understood why I get the error. A reinstall would probably fix it, but I don't wish to.
Personally I'd never use another Cyrix chip as long as I live!

by mmccaskill69

SYMPTOMS
========
When your computer is idle for a period of time and then stops responding
(hangs), the Close Program dialog box may report that Msgsrv32 is not
responding.
CAUSE
=====
This behavior can occur when power management is enabled, and you have
issues
with programs not responding correctly to power management commands, for
example, screen saver programs.
RESOLUTION
==========
To work around this behavior, use the following steps:
1) Quit any running programs, and then test to determine if a specific
program is causing this behavior. If you quit all running programs and the issue
is resolved, one of the programs that was running is the cause of this
behavior.
If this does not resolve the issue, continue to step 2.
NOTE: This issue is often caused by screen saver programs.
2) Disable power management. To do so, click Start, point to Settings, click
Control Panel, and then double-click Power.
3) In the Power Management box, click Off (or click the "Allow windows to
manag

by mmccaskill69

Continued...
3) In the Power Management box, click Off (or click the "Allow windows to
manage power on this computer" check box to clear it).
4) Click OK.
5) Restart your computer.
If the behavior continues to occur, follow these additional steps:
1) In Control Panel, double-click System.
2) On the Device Manager tab, double-click the System Devices branch to expand it.
3) Double-click Advanced Power Management Support.
4) On the Settings tab, click the Enable Power Management Support check box
to clear it, and then click OK.
5) Click OK.
6) Restart your computer when you are prompted to do so.
\** If the steps listed earlier in this article do not resolve this issue,
you can try renaming the Win.ini file and then restarting your computer. Windows
will then create a new Win.ini file. Note that if you do so, all other
entries in the Win.ini file must be recreated, typically by reinstalling programs.
Good Luck!

This discussion is closed to new replies.