I use Wintop, the free little program that shows you all the running processes on your windows machine, how much percentage of the CPU they are using, the path to their executable, etc. Anyway, for years when I was doing nothing on the computer, a high 90ish % of the CPU would be listed as the "Idle" process, meaning not used. But now, msgsrv32.exe is consistantly using up whatever any other programs are not using. If I dont do anythign else, msgsrv32 uses an average of 97% of my CPU and won't stop. I know a little about what msgsrv32 does, so I'm not looking for an explanation on that. I am looking for why the heck its using so much processing power suddenly and how to make it stop doing so. It never used to do this. What can I try doing? Many thanks in advance.

http://www.computergripes.com/Windows98.html http://www.evolution-at-home.net/Tools/wintop.txt http://www.windows-help.net/windows98/troub-25.shtml And try a www.google.com search for: msgsrv32.exe low resources

Did you ever resolve this problem? I just recently had the same thing happen on my computer and am looking for a fix. Thanks

I sent the other message yesterday. Since then I did some checking on the web and found that SoundBlaster can cause this problem. I have SoundBlaster Live! and did a complete reload of the program. Since then, my MSGSRV32.exe file has been very quiet. If you're running a SoundBlaster program you might want to try a reload. I found a web page where a whole bunch of people were talking about the same problem and they were all blaming SoundBlaster. Good luck!!

Had this problem. I just cured it! Found corrupt Setupx.dll system file. Replaced with original Setupx.dll off of Win98SE disk from WIN98 directory. MSGSRV32.exe usage went from 31-91% right down to 0.18-0.36%. Use the system file checker under System Information Tools selection to verify corrupt Setupx.dll file.

A P.S. on the above posting. I am using the SoundBlaster Live! Value card and this was not the problem! No reload of any drivers was needed. Only needed to change Setupx.dll file back to original. I severely question those blaming the SoundBlaster Live! card.