Non resident virus

A computer virus that does not store or execute itself from the computer memory. Executable viruses are an example of a non resident virus.

Stealth virus

A stealth virus hides itself from anti-virus software after infection, either by making the computer appear as though it has not lost any memory or that the file size has not changed.

Divide error

Note: This document also applies to the error messages "Divide by Zero", "Divide by 0" or "Divide Overflow" error messages.

The divide error messages are caused when the computer or software attempts run a process that attempts to perform a mathematical division by zero, which is an illegal operation. This error message could also be caused by a computer or software limitation or conflict with computer memory.

Hardware or software incompatibility

This issue can occur if software is being run on a computer that has hardware that is incompatible with the software. For example, this issue may occur with restore software designed for a specific computer and is being run on another computer or on the correct computer that has added hardware within it.

Ensure that the software that is being run on the computer is compatible with the computer and that the computer meets the system requirements and determine if there are updates or replacements to the software being used.

Error with autoexec.bat or config.sys

Users who are running Microsoft Windows 3.x can temporarily remark or remove any additional lines that may not be required in the autoexec.bat and config.sys

Users who are running Microsoft Windows 95 or Windows 98, it is recommended that they temporarily rename the autoexec.bat and config.sys to ensure that these files are not causing the issue. To do this, follow the instructions below:

1. Click Start, Shutdown, and Restart the computer in an MS-DOS mode.
2. Once at the MS-DOS mode, type:
   
   cd\ <press enter>
   ren autoexec.bat autoexec.ch <press enter>
   ren config.sys config.ch <press enter>
3. Once the files have been renamed, reboot the computer.

Additional help and information with the autoexec.bat and config.sys can be found on our autoexec.bat and config.sys page.

Note: if you are unable to get to an MS-DOS prompt or to Windows to rename or edit the files, boot the computer to an MS-DOS mode only.

Driver issue

If you are encountering a divide error within Windows, ensure that all computer hardware devices, such as the computer video card, sound card, network card or modem have the latest drivers and patches.

You can find a listing of computer drivers on our driver page.

Software issue

If the divide error is occurring while in a computer game or software program and the above recommendations does not resolve your issue, ensure that all software patches and upgrades have been obtained and applied.

In addition, ensure that another program that may be running in the background, such as a Virus protection program, is not causing your issue by End Tasking all background programs and TSRs.

External cache or 2nd level cache

If you are encountering the divide error in an older software program or game it can be caused by compatibility issues with External or 2nd level cache. Temporarily disabling this feature in CMOS Setup may resolve your issue.

Improper calculation

If you are performing a calculation in any program and experience a divide error, ensure that the calculation being performed is possible. Some programs are not capable of verifying the accuracy of a calculation and may perform an illegal instruction.

However, many programs, such as Microsoft Excel, will generate a #DIV!0 error indicating the formula or calculation is invalid or you are attempting to divide by zero.

Operating system issue

If you continue to experience a divide error while in Windows or in a particular software program and have followed each of the above recommendations, ensure that the issue is not being caused by the operating system by attempting to reinstall the operating system.

Hardware issue

Finally, if none of the above recommendations resolve or help to determine the cause of your issue the computer may have a hardware issue. When a Divide Error is encountered because of hardware it is caused by an issue with the computer Processor (CPU).

Vaccine

Alternatively referred to as inoculate, vaccine when referring to computers is another name for a software utility designed to protect computers from computer viruses. These software programs are more commonly known as an antivirus and anti-malware program

80486

 

A computer processor developed by Intel as an upgrade to the 386 processor series and commonly referred to as the 486 or i486. The 80486 has 8k of memory cache built into the processor with 32-bit databus architecture and was available in clock rates ranging from 20MHz to 33MHz. The 486 was available as either a DX or SX, the DX features a built-in coprocessor, the SX does not. In addition to the 486SX, a 486SX2 was also available and was capable of doubling the speed. The picture is an example of the Intel i486 SX processor with the OverDrive socket.

• In 1990 the 486SL was introduced and utilized less power than the 486 and is mainly used in portable computers.
• On April 1991 Intel released the 890486SX (codenamed P45 and P23) for $258.00 that ran at 16MHz, 20MHz, 25MHz, or 33MHz, a lower clock speeds than the DX.
• On March 2, 1992 the 486DX2 (codenamed P24 and P24S) was introduced and ran at double the clock rate of a 486. Thus, a DX2 on a system with a 33MHz bus would run at 66MHz. Alternatively referred to as the i486DX2.
• In 1994 the 486DX4 (codenamed P24C and P24CT) was introduced, it tripled the clock rate of the 486 and has doubled the cache (16k). If you had a 33MHz it would make it a 100MHz. Note: there is no 486SX4.

Issues relating to msgsrv32

• Tip: If you are unable to boot into Windows because of the MSGSRV32 error, follow the steps below in Windows Safe Mode.

Resource conflict or issue

Before attempting any of the below recommendations, verify the computer has no conflicts or errors in Windows Device Manager. If conflicts or errors are present, it is highly recommended that they be fixed first, as they could be causing your issue.

TSRs or other running programs

If you are encountering the MSGSRV32 error when attempting to open a program or perform a particular task on a computer, verify startup programs or other TSRs are not causing your issues by End Tasking all TSRs and closing all programs before running or performing the task generating your MSGSRV32 error.

Sound driver or sound card issues

Verify the correct audio devices in Multimedia by following the steps below:

1. Click Start, Settings, Control Panel, and then double-click the multimedia icon.
2. Verify that the playback device is set to the audio device in the computer.

Second, verify that your sound card has the latest drivers and updates installed from the computer or motherboard manufacturer (if onboard sound). A listing of computer sound drivers can be found on our sound card drivers page.

Onboard sound or video issue

• Troubleshooting on-board audio.
• Issues with adding new video card to computer that has on-board video.

MIDI device or codec issues

Verify that the computer has the proper MIDI codec and that no more than 11 MIDI devices are installed. To check this, follow the steps below:

1. Click Start, Settings, and then Control Panel
2. Double-click the Multimedia icon
3. Select the Advanced or Devices tab
4. Click the + next to "MIDI Devices and Instruments"
5. Verify that the correct codec is installed according to the sound card installed in the computer. In addition, verify that no more than 11 MIDI devices are listed below this category.

If more than 11 MIDI devices are installed or the improper codec appears to be installed, remove the improper codec or one of the MIDI devices. Note: if MIDI Express XT driver is installed, you may also want to remove this codec to help free up available space for additional MIDI devices.

Power Management or screensaver issue

If you are experiencing issues with MSGSRV32 after recovering from power management or when the computer has been idle for over 10 minutes, your computer may have issues with Power Management. To resolve these issues, try the below recommendations.

1. If any screensavers or CPU sharing programs such as SETI are running on the computer, temporally disable these programs to ensure they are not causing your issue.
2. If your issues persist, disable Power Management by clicking Start, Settings, Control Panel, and then Power. In the Power menu, disable or set the power settings to Off or Never. Once set, click ok or Apply and reboot the computer.

Microsoft Find Fast related issue

Ensure that Microsoft Find Fast is not being loaded in the startup group by clicking Start, Programs, and then Startup. If "Find Fast" or "Microsoft Find Fast" is listed, remove this program from automatically loading each time your computer boots; follow the steps below:

1. Click Start, Settings, and then Taskbar & Start Menu
2. Click Start Menu Programs tab
3. Click the Advanced button
4. Click the + next to Programs and then the + next to startup
5. Highlight the Find Fast icon and press the delete key on the keyboard.
6. Once removed, close out of all windows and reboot the computer to see if issue has been resolved.

Memory manager being used

If the computer has a memory manager installed such as QEMM, temporarily uninstall this program from the computer to ensure it is not causing your issue.

Issue with shell

If your are using a shell other than explorer.exe (standard Windows shell), the msgsrv32 error is being encountered because of the third-party shell. Temporarily disable or remove the third-party shell and use the standard Windows explorer.

Computer virus or back orifice

Errors relating to msgsrv32 can be caused by computer viruses, and in some cases back orifice, which is a hack utility used to gain access to an individual's computer.

Verify that you have the latest updates for your computer virus scanner and that no viruses have been detected on your computer.

• Computer virus information and help.

Other Software corruption

If you have attempted each of the above recommendations and your issue is not listed in the below specific MSGSRV32.DLL errors, your computer may have another software or data corruption causing the issue.

If you have not already attempted the recommendations on our basic troubleshooting page, try those recommendations now.

If you continue to experience issues it is recommended you format and reinstall the computer operating system.

Bad hardware

If after reinstalling the operating system you immediately continue to experience the MSGSRV32 errors, the computer may have bad hardware. If your sound card is not an onboard sound card and you are familiar with ESD, you may want to consider temporarily physically removing the sound card or DVD decoder cards and see if the issue persists.

Specific MSGSRV32.DLL errors

MSGSRV32.DLL caused a general protection fault in CM8330SB.DRV
MSGSRV32.EXE caused a general protection fault in CM8330SB.DRV
EXPLORER caused a general protection fault in CM8330SB.DRV
Iexplorer caused a general protection fault in CM8330SB.DRV

This issue is related to the C-Media 8330 sound card chipsets included in various computer sound cards and some modems. Verify with the sound card manufacturer, modem manufacturer, or, if you have an onboard sound card, the motherboard manufacturer, to see if any updated drivers or patches are available for your sound card and modem.

MSGSRV32 caused an invalid page fault in module Kernel32.dll during Microsoft Network (MSN) login or when attempting to open Internet Explorer or Microsoft Outlook

This issue may be encountered when the MSN password file is corrupt. To resolve this issue, follow the instructions below.

1. Click Start, Find, and then Files or Folders
2. In the Named field type:
   
   *.pwl
3. Verify that the Look in field is looking in the C: drive
4. Click Find Now
5. If files are found click Edit and click Select All.
6. Once all the files are highlighted, press the delete key.
7. Once the files have been deleted, reboot the computer, when the computer reboots, the pwl files should be recreated and you should then be able to log into MSN.
8. If this resolves your issue and you are running Windows 95, download the file mspwlupd.exe from our Windows 95 download page.

MSGSRV32 caused a general protection fault in KRNL386.EXE during windows install

This issue may be caused by a problem with the dblbuff.sys file. Microsoft has released a support fix for this issue, but to obtain the file you must contact Microsoft.

When browsing or installing device drivers, one of the following error messages occurs:
Msgsrv32 caused a General Protection Fault in module Kernel32
Msgsrv32 caused an invalid page fault in Msgrv32.dll
MSGSRV32 caused an invalid page fault in module Kernel32.dll
Msgsrv32 caused a General Protection Fault in Msgsrv32.exe

This issue may be caused by a problem with the msgrv32.exe file. Microsoft has released a support fix for this issue, but to obtain the file you must contact Microsoft.

Why do Windows programs stop responding

A computer, operating system, software program or driver may stop responding or cause other programs to stop responding because of several possible reasons, such as a confliction of software or hardware resources between two programs, lack of system resources, or a bug in the software or drivers.

To recover from a program that has stopped responding, press the Ctrl + Alt + Del keys on his or her keyboards to open the "Close Program" or "Task Manager" window, highlight the program, and click the "End Task" button to terminate the program. If another window opens, click the "End Task" button again to confirm stopping that program.

Note: It is important to realize that when a program stops responding any work that has not been saved will be lost when end tasking a program.

If you continue to experience programs locking the computer or stop responding we recommend you review our General Troubleshooting page for recommendations on steps that can be performed to help stop this issue from occurring.