Msgsrv32 not Responding
Msgsrv32 is a process that is started by Microsoft ME and Windows 9x and it acts as a Windows 32-bit message server running in the background and performing background support and functionalities. Msgsrv32 will not appear on the task manager process tab when the program is running normally.
It is responsible in ensuring windows drivers are loaded at startup and runs the explorer.exe shell program. It also ensures the integrity of windows files after a setup program is run. If windows files have been overwritten in the process, it restores them to their original formats. At logon it is responsible for displaying the logon dialog box and playing the system startup & shutdown sounds.
Sometimes, when the computer is left to run idle for a period of time, it may hang and a dialog box appears reporting that msgsrv32 not responding. Sometimes, this behavior is experienced in systems that have the power management option enabled. As a result of this, some programs will stop responding when they are given power management commands. One example of programs that cause these errors when left idle is screen savers. To resolve the problem, quit all running programs and disable the power management feature. Instead, allow windows to manage power on the local machine as opposed to networked systems.
Being a generic windows process, msgsrv32 will usually be called by a number of applications. Thus an msgsrv32 not responding error means an application accessing the program has failed. Checking the event logs will usually alert one to program that is responsible for that error message. If information has not been saved lately, the appearance of the ‘msgsrv32 not responding’ report will mean losing data currently being on in some instances.
Msgsrv32 errors may also be caused by resource conflicts or TSR programs running in the computer memory. Disabling these programs from running at startup will usually resolve the problem. Assigning unique addresses to resources will also enable the operating system to identify each resource distinctly. A failing hardware may also bring about the msgsrv32 not responding message. In such a case, testing each component via the device manager will likely reveal the culprit. Computer viruses and Trojans residing in the main memory are also known to cause the ‘msgsrv32 not responding’ message. An updated anti-virus program can help to remove malware causing the errors. If the above solutions fail, then performing a system restore or reinstalling windows will usually be the last option.
Leave a Reply