Reasons Why PCS Crash

REASONS WHY PCS CRASH
Fatal error: the system has become unstable or is busy," it says. "Enter to return to Windows or press Control-AltDelete to restart your computer. If you do this you will lose any unsaved information in all open applications."
You have just been struck by the Blue Screen of Death. Anyone who uses Mcft Windows will be familiar with this.
What can you do? More importantly, how can you prevent it happening?
1 HARDWARE CONFLICT
The number one reason why Windows crashes is hardware conflict. Each hardware device communicates to
other devices through an interrupt request channel (IRQ). These are supposed to be unique for each device.
For example, a printer usually connects internally on IRQ 7. The keyboard usually uses IRQ 1 and the floppy disk
drive IRQ 6. Each device will try to hog a single IRQ for itself.
If there are a lot of devices, or if they are not installed properly, two of them may end up sharing the same IRQ
number. When the user tries to use both devices at the same time, a crash can happen. The way to check if your
computer has a hardware conflict is through the following route:
* Start-Settings-Control Panel-System-Device Manager.
Often if a device has a problem a yellow '!' appears next to its description in the Device Manager. Highlight
Computer (in the Device Manager) and press Properties to see the IRQ numbers used by your computer. If the
IRQ number appears twice, two devices may be using it.
Sometimes a device might share an IRQ with something described as 'IRQ holder for PCI steering'. This can be
ignored. The best way to fix this problem is to remove the problem device and reinstall it.
Sometimes you may have to find more recent drivers on the internet to make the device function properly. A good
resource is www.driverguide.com. If the device is a soundcard, or a modem, it can often be fixed by moving it to a
different slot on the motherboard (be careful about opening your computer, as you may void the warranty).
When working inside a computer you should switch it off, unplug the mains lead and touch an unpainted metal
surface to discharge any static electricity.
To be fair to Mcft, the problem with IRQ numbers is not of its making. It is a legacy problem going back to the first
PC designs using the IBM 8086 chip. Initially there were only eight IRQs. Today there are 16 IRQs in a PC. It is
easy to run out of them. There are plans to increase the number of IRQs in future designs.
1|CPIC-CHS
2 BAD RAM
Ram (random-access memory) problems might bring on the blue screen of death with a message saying Fatal
Exception Error. A fatal error indicates a serious hardware problem. Sometimes it may mean a part is damaged
and will need replacing.
But a fatal error caused by Ram might be caused by a mismatch of chips. For example, mixing 70-nanosecond
(70ns) Ram with 60ns Ram will usually force the computer to run all the Ram at the slower speed. This will often
crash the machine if the Ram is overworked.
One way around this problem is to enter the BIOS settings and increase the wait state of the Ram. This can make
it more stable. Another way to troubleshoot a suspected Ram problem is to rearrange the Ram chips on the
motherboard, or take some of them out. Then try to repeat the circumstances that caused the crash. When
handling Ram try not to touch the gold connections, as they can be easily damaged.
Parity error messages also refer to Ram. Modern Ram chips are either parity (ECC) or non parity (non-ECC). It is
best not to mix the two types, as this can be a cause of trouble.
EMM386 error messages refer to memory problems but may not be connected to bad Ram. This may be due to
free memory problems often linked to old Dos-based programmes.
3 BIOS SETTINGS
Every motherboard is supplied with a range of chipset settings that are decided in the factory. A common way to
access these settings is to press the F2 or delete button during the first few seconds of a boot-up.
Once inside the BIOS, great care should be taken. It is a good idea to write down on a piece of paper all the
settings that appear on the screen. That way, if you change something and the computer becomes more unstable,
you will know what settings to revert to.
A common BIOS error concerns the CAS latency. This refers to the Ram. Older EDO (extended data out) Ram
has a CAS latency of 3. Newer SDRam has a CAS latency of 2. Setting the wrong figure can cause the Ram to
lock up and freeze the computer's display.
Mcft Windows is better at allocating IRQ numbers than any BIOS. If possible set the IRQ numbers to Auto in the
BIOS. This will allow Windows to allocate the IRQ numbers (make sure the BIOS setting for Plug and Play OS is
switched to 'yes' to allow Windows to do this.).
4 HARD DISK DRIVES
2|CPIC-CHS
After a few weeks, the information on a hard disk drive starts to become piecemeal or fragmented. It is a good
idea to defragment the hard disk every week or so, to prevent the disk from causing a screen freeze. Go to
* Start-Programs-Accessories-System Tools-Disk Defragmenter
This will start the procedure. You will be unable to write data to the hard drive (to save it) while the disk is
defragmenting, so it is a good idea to schedule the procedure for a period of inactivity using the Task Scheduler.
The Task Scheduler should be one of the small icons on the bottom right of the Windows opening page (the
desktop).
Some lockups and screen freezes caused by hard disk problems can be solved by reducing the read-ahead
optimisation. This can be adjusted by going to
* Start-Settings-Control Panel-System Icon-Performance-File System-Hard Disk.
Hard disks will slow down and crash if they are too full. Do some housekeeping on your hard drive every few
months and free some space on it. Open the Windows folder on the C drive and find the Temporary Internet Files
folder. Deleting the contents (not the folder) can free a lot of space.
Empty the Recycle Bin every week to free more space. Hard disk drives should be scanned every week for errors
or bad sectors. Go to
* Start-Programs-Accessories-System Tools-ScanDisk
Otherwise assign the Task Scheduler to perform this operation at night when the computer is not in use.
5 FATAL OE EXCEPTIONS AND VXD ERRORS
Fatal OE exception errors and VXD errors are often caused by video card problems.
These can often be resolved easily by reducing the resolution of the video display. Go to
* Start-Settings-Control Panel-Display-Settings
Here you should slide the screen area bar to the left. Take a look at the colour settings on the left of that window.
For most desktops, high colour 16-bit depth is adequate.
If the screen freezes or you experience system lockups it might be due to the video card. Make sure it does not
have a hardware conflict. Go to
3|CPIC-CHS
* Start-Settings-Control Panel-System-Device Manager

Here, select the + beside Display Adapter. A line of text describing your video card should appear. Select it (make
it blue) and press properties. Then select Resources and select each line in the window. Look for a message that
says No Conflicts.
If you have video card hardware conflict, you will see it here. Be careful at this point and make a note of
everything you do in case you make things worse.
The way to resolve a hardware conflict is to uncheck the Use Automatic Settings box and hit the Change Settings
button. You are searching for a setting that will display a No Conflicts message.
Another useful way to resolve video problems is to go to
* Start-Settings-Control Panel-System-Performance-Graphics
Here you should move the Hardware Acceleration slider to the left. As ever, the most common cause of problems
relating to graphics cards is old or faulty drivers (a driver is a small piece of software used by a computer to
communicate with a device).
Look up your video card's manufacturer on the internet and search for the most recent drivers for it.
6 VIRUSES
Often the first sign of a virus infection is instability. Some viruses erase the boot sector of a hard drive, making it
impossible to start. This is why it is a good idea to create a Windows start-up disk. Go to
* Start-Settings-Control Panel-Add/Remove Programs
Here, look for the Start Up Disk tab. Virus protection requires constant vigilance.
A virus scanner requires a list of virus signatures in order to be able to identify viruses. These signatures are
stored in a DAT file. DAT files should be updated weekly from the website of your antivirus software manufacturer.
An excellent antivirus programme is McAfee VirusScan by Network Associates ( www.nai.com). Another is Norton
AntiVirus 2000, made by Symantec ( www.symantec.com).
7 PRINTERS
4|CPIC-CHS
The action of sending a document to print creates a bigger file, often called a postscript file.
Printers have only a small amount of memory, called a buffer. This can be easily overloaded. Printing a document
also uses a considerable amount of CPU power. This will also slow down the computer's performance.
If the printer is trying to print unusual characters, these might not be recognised, and can crash the computer.
Sometimes printers will not recover from a crash because of confusion in the buffer. A good way to clear the buffer
is to unplug the printer for ten seconds. Booting up from a powerless state, also called a cold boot, will restore the
printer's default settings and you may be able to carry on.
8 SOFTWARE
A common cause of computer crash is faulty or badly-installed software. Often the problem can be cured by
uninstalling the software and then reinstalling it. Use Norton Uninstall or Uninstall Shield to remove an application
from your system properly. This will also remove references to the programme in the System Registry and leaves
the way clear for a completely fresh copy.
The System Registry can be corrupted by old references to obsolete software that you thought was uninstalled.
Use Reg Cleaner by Jouni Vuorio to clean up the System Registry and remove obsolete entries. It works on
Windows 95, Windows 98, Windows 98 SE (Second Edition), Windows Millennium Edition (ME), NT4 and
Windows 2000.
Read the instructions and use it carefully so you don't do permanent damage to the Registry. If the Registry is
damaged you will have to reinstall your operating system. Reg Cleaner can be obtained from www.jv16.org
Often a Windows problem can be resolved by entering Safe Mode. This can be done during start-up. When you
see the message "Starting Windows" press F4. This should take you into Safe Mode.
Safe Mode loads a minimum of drivers. It allows you to find and fix problems that prevent Windows from loading
properly.
Sometimes installing Windows is difficult because of unsuitable BIOS settings. If you keep getting SUWIN error
messages (Windows setup) during the Windows installation, then try entering the BIOS and disabling the CPU
internal cache. Try to disable the Level 2 (L2) cache if that doesn't work.
Remember to restore all the BIOS settings back to their former settings following installation.
9 OVERHEATING
5|CPIC-CHS
Central processing units (CPUs) are usually equipped with fans to keep them cool. If the fan fails or if the CPU
gets old it may start to overheat and generate a particular kind of error called a kernel error. This is a common
problem in chips that have been overclocked to operate at higher speeds than they are supposed to.
One remedy is to get a bigger better fan and install it on top of the CPU. Specialist cooling fans/heatsinks are
available from www.computernerd.com or www.coolit.com
CPU problems can often be fixed by disabling the CPU internal cache in the BIOS. This will make the machine
run more slowly, but it should also be more stable.
10 POWER SUPPLY PROBLEMS
With all the new construction going on around the country the steady supply of electricity has become disrupted. A
power surge or spike can crash a computer as easily as a power cut.
If this has become a nuisance for you then consider buying a uninterrupted power supply (UPS). This will give you
a clean power supply when there is electricity, and it will give you a few minutes to perform a controlled shutdown
in case of a power cut.
It is a good investment if your data are critical, because a power cut will cause any unsaved data to be lost.
ELEVEN TIPS FOR TROUBLESHOOTING SOFTWARE

1. Free up RAM by closing other open programs.
Every piece of software that's installed on your machine needs Random Access Memory (RAM) in
order to run. The more software that's running on your computer at once, the more RAM it will
consume. So if a certain program refuses to load or is running sluggishly, the first step you should
take is to close all other open applications. This can be especially important if your nonprofit uses
older machines that don't have a large amount of RAM.
If you want to investigate which open applications might be hogging much of your computer's RAM,
both Windows and Macintosh operating systems (OS) provide tools that display this information. In
Windows, you can locate RAM-usage statistics by hitting Ctrl+Alt+Delete, then choosing the Task
Manager option. From the window that appears, click the Processes tab, then click the menu item
labeled "Mem Usage," which arranges all open applications according to the amount of RAM they're
using. You can shut down a process or application by clicking the End Task button, but before you
do so, you may want to perform a Web search on the name of the process or application; that way
you won't accidentally stop a process or program that's necessary in order for your system to run.
Mac OS X displays RAM-usage information with a tool called the Process Viewer, which you can
access by going to Applications > Utilities. Once you've called up the Process Viewer, you sort
programs by RAM usage by clicking the column labeled Real Memory.
2. Restart the software.
If you've closed all applications that are running on your computer and the software still runs
slowly, crashes, or returns error messages, try shutting down the problematic program and
immediately restarting it. Sometimes, software problems stem from a conflict with other programs
6|CPIC-CHS
or simply encounter difficulties starting up, so restarting the software can often resolve these
issues.
3. Shut down and restart your computer.
Sometimes, a glitch in your computer's OS or a hardware mishap can cause software problems. If
restarting the actual application doesn't resolve the issue, try rebooting your computer. Once the
computer has fully restarted, re-launch the application in question and see if the problem has
resolved itself.
4. Use the Internet to find help.
No matter what piece of software is misbehaving or what specific problems you encounter, chances
are, it's happened to someone else. And as long as you're not having issues with a custom-built
piece of software, there's a good chance that you can find help on the Internet.
When conducting online troubleshooting research using Google or your search engine of choice,
include the most important information, such as the software program's name, the type of problem
you've encountered, and the circumstances under which it occurs. If the program is returning a
specific error message, write it down and type it into the search engine's search box along with the
application's name.
Although using a search engine can be a quick way to find information regarding very specific
software error messages or crashes, take a look at the manufacturer's site for more general
troubleshooting advice. Most major software manufacturers provide at least some form of productspecific help on their official sites, such as a list of frequently asked questions, product
documentation, or discussion forums where users can swap tips.
You might also run across the solution to your software woes at one of the many other Web sites
dedicated to providing technical help. TechSoup's article Use the Web to Find Free Tech Support
lists a number of Web sites that offer technology troubleshooting tutorials, articles, and discussion
forums.
5. Undo any recent hardware or software changes.
As mentioned, some software problems arise from conflicts with other software. For example, as
this information technology article from the Johns Hopkins Institutions points out, Symantec Norton
Antivirus can often conflict with competing antivirus products. So, if one of your organization's
staffers has installed another antivirus program and Norton Antivirus no longer works correctly,
uninstalling the other antivirus problem could very well solve your problem.
If you are troubleshooting one of your staff members' computers and suspect that they have
tinkered with the OS's settings, it's possible that they have inadvertently made changes that are
causing their current software problems. For instance, Windows XP's Start Menu contains an option
called "Set Program Access and Defaults," which allows you to disable access to certain
applications. If the user accidentally unchecked the box next to a program, this may be the reason
it won't run. Ask the user whether he has recently changed any of their computer's settings; if he
can remember what changes he made, undo them and try launching the software again.
Similarly, software problems can sometimes be caused by new or improperly configured hardware
peripherals, including scanners and printers. If you've recently connected new hardware to one of
your organization's computers, try disconnecting it and see if that corrects the software issue.
6. Uninstall the software, then reinstall it.
Sometimes, a certain piece of software will fail to run properly because crucial application files have
been removed or deleted. For instance, many Windows applications use Dynamic Link Library (DLL)
files to perform certain tasks. Oftentimes, several applications will need the same DLL file to
7|CPIC-CHS
operate properly, so if you've recently removed one program from your computer along with all of
its DLL files, another application may become unstable or nonfunctional.
One step you can take to ensure that the problematic software has all of its necessary files intact is
to completely uninstall it, then reinstall it on your computer. Even if you remove a program using
its built-in uninstall wizard (if it includes one), it's still a safe move to check your hard drive's
Program Files folder usually located on the C drive for any remnants of the program and
delete any files or folders you find.
Next, check to see if there's a new version of the program available (the vendor or developer might
have introduced bug fixes that address the issue you're having) download and install the new
version if it's ready. If not, locate your installation CD or download the most current version of the
software and repeat the installation process.
7. Look for software patches.
Though some software vendors will correct major problems with their products by releasing entirely
new versions, other vendors may fix minor bugs by issuing patches, small software updates that
address problems detected by developers or users. Even if you're sure that you have installed the
most current version of the software, you might still want to visit the manufacturer or developer's
Web site to check for new updates, as the vendor may have chosen to quickly correct a recently
discovered problem with a patch rather than a new version.
8. Scan for viruses and malware.
Viruses, spyware, and other forms of malicious software (commonly referred to as malware) can
not only compromise your nonprofit's privacy, they can also cause other applications on your
computer especially Web browsers and email clients to freeze, crash, or quit working entirely
If tips 1 through 8 haven't helped solve your software problem, you may want to scan the machine
using both antivirus and anti-malware applications, programs designed to find and remove viruses
and malware. When running one of these programs, it's a good idea to use the most thorough scan
mode available; also, remember to shut down and restart your machine if the antivirus or antimalware program does find and remove threats from the computer.
For more information on getting rid of viruses and malware including advice on antivirus and
anti-malware applications read TechSoup's article Removing Viruses, Spyware, and Other Forms
of Malware. It's worth noting that, currently, the majority of viruses and malware attacks target
Windows computers, although there have been occasional instances of malware threats for the Mac
OS.
9. Check for a firewall conflict.
Many nonprofits do not have the budget to purchase a centralized hardware or software-based
firewall and may instead choose to install personal firewall software such as ZoneAlarm Free
on each computer in their office. Though personal firewalls can be an important line of defense
against hackers and other security threats, they might also confuse users, since they frequently
display messages asking users whether to allow a program to run or whether to block it.
Its possible that you may be experiencing software problems because youve accidentally
instructed the personal firewall to block the program in question, most likely by responding to one
of the aforementioned messages. You may want to check the firewalls settings to see if the
problematic software has inadvertently been added to its list of programs to block. If so, change
the firewalls settings to allow the software to run, then check to see if youre still having issues.
10. Boot up in Safe Mode.
As mentioned, some software malfunctions can be caused due to OS settings or other system
problems. Windows and Mac operating systems both feature a troubleshooting environment known
8|CPIC-CHS
as Safe Mode, which disables applications and processes that are not crucial to the system,
theoretically making it easier to isolate problems.
Most Windows computers allow you to enter Safe Mode by pressing the F8 key as your computer is
booting up. If youre using a Mac, you can enter Safe Mode by pressing the Shift key while or
directly after your computer boots up. Once your computer is in Safe Mode, launch the problematic
software application and attempt to replicate the problem you encountered while your computer
was in normal mode. If you dont encounter the same problem, theres a good chance that the
issue is being caused by your OS or another program rather than the application you are
troubleshooting.
11. Defragment your hard drive.
As a final troubleshooting step, you might choose to defragment your computers hard drive, the
process of rearranging its file structure so that the system runs more efficiently. Defragmenting a
hard drive will probably prove most useful if youre experiencing extreme software sluggishness, as
this process is meant to make your entire system run faster. Note that defragmenting a hard drive
applies only to Windows-based computers, as the Macintosh OS automatically optimizes the hard
drives file structure.
Windows 98, ME, 2000, and XP OSs all include a built-in disk-defragmentation tool, which you can
launch by going to Start > Programs > Accessories > System Tools > Disk Defragmenter. Be aware
that defragmenting a hard drive can be a time-consuming process especially if the drive
contains many files so make sure to perform this task when you (or the user) will be away from
their computer for a few hours.
If the tips listed above havent solved your software problem, it may be time to bite the bullet and
call the tech-support hotline. One final tip? If you do end up having to place a tech-support call,
you may want to invest in a hands-free headset; it will likely make the time you spend on hold both
more comfortable and convenient.
9|CPIC-CHS
COMMON ERRORS AND HOW TO FIX THEM

I. HOW DO I FIX ILLEGAL OPERATIONS?
Issue:
1. HOW DO I FIX ILLEGAL OPERATIONS?
Cause:
Illegal Operations can be caused by several different factors. Below is a listing of the more
commonly known reasons for getting an Illegal Operations.
a. TSR's or Third-party programs causing memory conflicts or other types of conflicts with the
program or programs attempting to be run.
b. Data not being read properly from source. Running a program or game with a dirty CD can
cause the CD to be read improperly causing Illegal Operations. Floppy diskettes which may
contain errors can cause illegal operations.
c. Installing a program or game on a hard disk drive that has errors or is highly fragmented.
d. Corrupt files.
e. Memory managers.
f.
Bad, incorrect or not the latest video drivers.
g. Computer Virus.
h. Added hardware
i.
Error in program coding
j.
Corruption or problem within Windows.
k. Bad Memory, invalid bits or physically bad memory.

Solution:
a. TSR's or Third-party programs:
TSR's or Third-party programs running in the background are one of the more commonly found
reasons for Illegal Operations. If you are receiving an Illegal Operation when attempting to run a
game or program it is recommend that you temporarily remove or disable programs running and
TSR's running in the background, ensuring that these programs are not causing your issues.
If, after removing these programs, you run the program or game and no longer receive the Illegal
Operations, it is recommend that you reboot the computer and disable or End Task each program
or TSR one at a time to attempt to determine which program is causing the Illegal Operation.
b. Data not being read properly from source:
10 | C P I C - C H S
When running a program or game from a CD you receive an Illegal Operation, verify that the CD is
clean.
If you are running a game from a floppy diskette or other floppy media such as a zip diskette or
LS120, verify that the diskette does not have physical errors with it by running a scandisk or a disk
drive utility included with the drive.
c. Installing a program or game on a hard disk drive that has errors or is highly
fragmented:
When installing a program or game onto a hard disk drive it is recommended if you receive errors
after installing that program or game that you attempt to uninstall that program or game, run a
scandisk, then a defrag, and finally attempt to install the program or game again.
If errors exist on the hard disk drive, they will cause the program or game to run improperly and
can cause Illegal Operations.
d. Corrupt files:
Corrupt, bad or missing files can cause Illegal Operations. It is recommended that you attempt to
uninstall and or reinstall the program causing the Illegal Operation to verify that any corrupt, bad
or missing files are replaced or repaired during the reinstallation.
e. Memory managers:
If you are running a memory manager that is used to obtain more memory or handle the computer
memory in replace of Windows, it is recommended you temporarily disable or uninstall this
program to verify it is not the memory manager causing the Illegal Operations.
f.
Bad, incorrect or not the latest video drivers:
Bad, incorrect or not the latest video drivers may cause Illegal Operations when performing such
tasks as moving the mouse or dragging data from one source to another as high demands are
placed onto the video card. Attempt to decrease the video settings to 640 x 480, 256 colors to
verify if the program or game being run is having errors because of the current video settings.
If, after attempting to adjust the video settings, you still encounter the same issue, verify the
computer is utilizing the latest video card drivers by visiting our Video drivers section.
g. Computer Virus:
Because computer viruses are loaded into memory and can change the data of program files when
infecting a computer, ensure that a virus protection utility is installed on the computer and that you
have the latest Virus Definition.
h. Added hardware:
If added hardware has been recently installed onto the computer it is likely that either the
hardware is conflicting with other hardware devices on the computer or that the drivers used to
install that hardware is causing issues with other hardware or software installed on the computer.
If added hardware has recently been added to the computer, it is recommended that you
temporarily remove that added hardware and the software associated with it to ensure it is not
causing your issues.
11 | C P I C - C H S
i.
Error in program coding:
If you are receiving Illegal Operations only when running a particular program, verify that the
program is compatible with the Version of Windows you are running and ensure no available
patches or software are available that may fix errors made during the development stages.
j.
Corruption or problem within Windows:
Because Windows controls the memory operations as well as the file structure and association, it is
possible for Windows or files associated with Windows to become corrupted, causing Illegal
Operations or other errors. It is recommended you reinstall Windows if you are experiencing Illegal
Operations in Windows or more than one program trying to be run on the computer.
k. Bad Memory, invalid bits or physically bad memory:
It is possible that bad memory can cause Illegal Operations. If you have recently added memory to
the computer, it is recommended that it first be removed to verify that you are not experiencing
conflicts with the recently installed memory.
If no memory has been recently added to the computer and you have tried all the above
recommendations you have to isolate what particular memory module that causes the error by trial
and error or substitution method.
Additional information:
An Illegal Operation is an operation requested to be performed by either the Operating System or
CPU that is not understood and therefore is Illegal.
II. MY COMPUTER IS RUNNING SLOW WHAT STEPS CAN I DO TO FIX IT?
Issue:
My computer is running slow what steps can I do to fix it?
Cause:
This issue can be caused by any of the below possibilities.
a. Hard disk drive is short on available disk space.
b. Several software programs have been installed/uninstalled leaving behind bad files and/or
confusing the software.
c. Data Corruption.
d. Computer is overheating.
e. Bad Hardware.
PC Solution:
Below are steps for Microsoft Windows that should help speed up the computer or determine why
the computer is running slow.
a. Not enough hard disk drive space
If you have a hard disk drive that is 2GB or smaller, ensure that there is at least 200MB of hard
disk drive space free. If you have a hard drive larger than this size, verify that there is at least
12 | C P I C - C H S
500MB of free hard disk space. This available space allows the computer to have room for the swap
file to increase in size as well as room for temporary files.
b. Hard drive corrupted or fragmented
Run Scandisk or something equivalent to help ensure that there is nothing physically wrong with
the computer hard disk drive.
Run Defrag to help ensure that data is arranged in the best possible order.
c. Background programs
Remove or disable any TSRs or programs that automatically start each time the computer boots.
d. Hardware conflicts
Verify that the Device Manager has no conflicts, but if conflicts are present, resolve them.
e. Issues with Windows XP prefetch
If you have Windows XP try deleting all files in the prefetch directory. These are prefetch files and
can lower system resources if loading programs no longer being used.
f.
Issues in Windows 95 / 98 autoexec.bat / config.sys
If you are using Microsoft Windows 95 or Windows 98 and do not plan on running any MS-DOS
programs from MS-DOS, click Start / Run / type command and press enter. In the MS-DOS window
type cd\ to get to C:\> then type "ren autoexec.bat autoexec.ch" and "ren config.sys config.ch".
This will rename your autoexec.bat and config.sys and help make sure memory is being optimized
through Windows.
III. Computer or processor is overheating

Make sure your computer and processor is not overheating, excessive heat can cause a significant
decrease in computer performance some processors will even lower the speed of the processor
automatically to help compensate for the heat related issues.
What temperature should my processor be running at?
Question:
What temperature should my processor be running at?
Answer:
Depending on the type of processor, the manufacturer, how fast it runs, where the sensor is
located, and what programs it is currently running will determine the temperature of what the
processor should be. However, this document should give you a general idea of what the processor
should be running at as well as what is acceptable and what is not.
The majority of today's desktop processors should not exceed temperatures of 95C and most will
run between 70-90C. Below are some charts of many of the processors and their average
temperatures. Keep in mind this is only to give our users a general idea of what their processor
should be running at. If you believe your computer is running to hot, you may wish to skip to the
bottom of this document for additional details on how to get exact information about what your
processor should be running at.
Processors
13 | C P I C - C H S
Average temperature
AMD Athlon
90C - 95C
AMD Athlon64
65C - 70C
AMD Athlon64 Mobile
95C - 100C
AMD Athlon MP
90C - 95C
AMD Athlon XP
85C - 90C
AMD Duron
85C - 95C
AMD Opteron
65C - 71C
AMD Sempron
90C - 95C
AMD K5
60C - 70C
AMD K6
65C - 70C
AMD K6 Mobile
80C - 85C
AMD K7 Thunderbird
70C - 95C
Intel Pentium II
65C - 75C
Intel Pentium III
60C - 85C
Intel Celeron
67C - 85C
Intel Pentium Mobile
100C
Intel Pentium Pro
80C - 85C
How will I know if my processor is running too hot?

If a processor gets too hot you will notice one or more of the below situations. Often these issues
will be encountered when running programs or especially when playing an advanced game.
1. Computer runs much slower
2. Computer restarts
3. Computer turns off
Continuing to use a computer that has a processor that is exceeding its temperature will reduce the
life expectancy of the processor.
Note: It's possible that with some computer configurations that the thermal sensors may not be
positioned in an optimal location, causing the temperature to be reported cooler or hotter than it
actually is. If your temperature is close to exceeding the maximum temperature or you are
experiencing the above issues, you may want to continue reading the below recommendations for
getting your computer cooler.
What can I do to get my processor cooler?
The cooler the processor runs the more performance you are going to get out of it. Therefore, if
you're looking to overclock your processor or if it's getting too hot, you may need to consider any
or all of the below recommendations.
Improve computer's environment - Make sure the computer is running in a good location.
The computer should not be in an enclosed space such as a drawer or cabinet unless there
14 | C P I C - C H S
is plenty of ventilation such as the back of the drawer or cabinet is removed. The computer
should not be in a tight space, there should be at least a two-inch space on both sides of
the computer as well as in the front and back of the computer.
Verify fans - Make sure all fans in the computer are properly working. Some motherboards
and computers have fan monitors that will display the RPM of each of the major fans in the
computer and if they are operating properly. Otherwise, you will need to check each of the
fans and look for any type of spinning issues or listen for any abnormal noises to determine
if the fans are properly working.
More fans - Consider installing additional fans into the computer. Almost all computers will
come included with a heatsink and fan, as well as a case fan. However, most cases will have
the availability to install a second case fan that can help bring in additional air and help keep
the computer cool. Computer enthusiasts and many overclockers may also create their own
air ducts with fans to help bring in additional air or take out more of the hot air.
Better fans - Many computers and processors will come with cheap fans to help bring down
the overall cost of the computer. Installing improved fans and/or heatsinks that can move
the heat away from the processor better and faster can keep the processor cool.
Alternative solutions - More advanced users or users who are overclocking may also wish to
consider alternative solutions such as water cooled solutions to keep their processors cool.
IV. HOW TO FIX AN INVALID PAGE FAULT.

Issue:
How to fix an invalid page fault.
An invalid page fault is caused when the operating system or a software program attempts to store
or call a segment or block of the computer's memory that does not exist. Because of the invalid
call, the program will generate an invalid page fault error message and terminate the program or
process to prevent additional issues.
Cause:
There are several reasons a computer may generate an Invalid Page fault error. Below are few of
those possibilities.
1. Incompatibility or issue with the software programs.
2. Issues with the computer memory.
Solution:
Remove all TSRs
Disable or unload any TSRs or programs currently running before running the program causing the
GPF.
Delete all program temporary files
Delete all temporary files that may still be residing on the hard disk drive from currently or
previously running programs.
15 | C P I C - C H S
Run Scandisk / Defrag

Attempt to run scandisk / defrag on the hard disk drive as it could be possible your hard disk drive
may have an issue causing the swap file or data files to become corrupt or invalid
Update software or check for software patches
If you are experiencing invalid page faults in only one program, verify that the software program is
compatible with the operating system you are running the program within. Also verify with the
manufacturer or vendor of the software program that there are no available patches or updates for
the program that may help or resolve your issue.
Recently installed software / hardware
If you have recently installed new software or hardware, attempt to uninstall or reinstall that
software / hardware to verify it is not causing your issue.
Bad Memory, invalid bits or physically bad memory
It is possible that bad memory can cause Illegal Operations. If you have recently added memory to
the computer it is recommended that it first be removed to verify that you are not experiencing
conflictions with the recently installed memory.
If no memory has been recently added to the computer it is recommended you follow all other
steps found on this page before replacing the memory within the computer.
V. How to fix a fatal exception error.
Issue:
How to fix a fatal exception error.
Windows and software now commonly use exceptions which allow Windows or other software to
communicate in layers and communicate errors or exceptions. If a program is given an exception
which is invalid or unknown, the program or operating system will generate a fatal exception. Fatal
exceptions are also commonly referred to as a Fatal OE, as the OE error is one of the more
commonly experienced fatal exception error messages.
Fatal exception error messages are generated when one of the below situations occur.
Access to an illegal software instruction has occurred.
Invalid data or code has been accessed.
The privilege level of an operation is invalid.
When a fatal exception is encountered the error will be in the below format.
A fatal exception <YZ> has occurred at xxxx:xxxxxxxx
In the above example of the fatal exception the YZ represents the actual processor exception, this
can range from 00 to 0F. Each of theses processor exceptions are explained under Extended
information.
After the processor exception is the enhanced instruction pointer to the code segment and the 32bit address. This is exactly where the error exception has occurred.
Cause:
16 | C P I C - C H S
Fatal exception errors are generally caused by programs' incompatibility, not written properly, heat
related issues or other hardware / software issues. Because of the wide range of possibilities, we
have created this document to help determine or resolve your issue.
Solution:
Remove all TSRs
Disable or unload any TSRs or programs currently running before running the program or
attempting to recreate the error.
.
may have an issue causing the swap file or data files to become corrupt or invalid
Disable External Cache in CMOS
If the option is available, attempt to enter your computer's CMOS setup and disable the external
cache. If this resolves your issue it is likely that you are encountering a heat related issue.
Heat related issue
Verify that all fans in and on your computer are properly working. Possibly attempt to add an
additional case fan, if there is available space.
Overclocked computer
If you have overclocked any component within the computer, set the computer to its factory
settings to verify that the overclocked component is not causing the issue.
Update software or check for software patches
If you are experiencing invalid page faults in only one program, verify that the software program is
compatible with the operating system you are running the program within. Also verify with the
manufacturer or vendor of the software program that there are no available patches or updates for
the program that may help or resolve your issue.
Verify your computer has more than 200 MB available
If your computer is running low on hard disk space, your Windows swap file will be unable to
increase in size when needed, causing programs to be swapped between memory and the hard disk
drive more frequently. When this occurs it is more likely that a GPF can occur.
If you have recently installed new software or hardware attempt to uninstall or reinstall that
CPU Core Voltage
If available, verify within your CMOS or by jumper that your CPU core voltage is set to factory
specification. This may require that you consult your documentation or motherboard manufacturer.
17 | C P I C - C H S
Bad Memory, invalid bits or physically bad memory

It is possible that bad memory can cause a Fatal Exception. If you have recently added memory to
the computer, it is recommended that it first be removed to verify that you are not experiencing
conflicts with the recently installed memory.
If no memory has been recently added to the computer and you have tried all the above
recommendations you can used the trial and error method to find out the defected component.
Extended Information:
Below is a listing of the more commonly experienced processor exceptions ranging from 00 to 0F.
00 = Divide Fault
Occurs if division by zero is attempted or if the result of the operation does not fit in the destination
operand.
02=NMI interrupt
Interrupt 2 is reserved for the hardware Non-Maskable-Interrupt condition. No exceptions trap
through interrupt 2.
04=Overflow trap
Occurs after an INTRO instruction has executed and the OF bit is set to 1.
05=Bounds Check fault
The array Index is out of range
06=Invalid Opcode fault
This error can be caused by one of the below conditions.
1. Processor attempting to decode a bit pattern that does not correspond to any legal
computer instruction.
2. Processor attempts to execute an instruction that contains invalid operands.
3. Processor attempts to execute a protected-mode instruction while running in virtual 8086
mode.
4. Processor attempts to execute a LOCK prefix with an instruction that cannot be locked.
07=Copressor not available fault.
This error can occur if no math coprocessor is present. This error can also occur when the math
coprocessor is used and a task switch is executed.
08=Double Fault.
This error occurs when processing an exception triggers a second exception.
09(OD)=Copressor Segment Overrun.
Floating point operand is outside the segment.
10(0Ah/0A)=Invalid Task State Segment Fault
Can be caused by a number of possibilities as Task State Segment contains a number of
descriptors.
18 | C P I C - C H S
11(0Bh)=Not Present Fault

The Not Present interrupt allows the operating system to implement virtual memory through the
segmentation mechanism. 0B fault occurs when this segment is not available.
12(0Ch)=Stack Fault
Occurs when instruction refers to memory beyond the limit of the stack segment.
13(Odh)=General Protection Fault
Caused by any condition that is not covered by any of the other processor exceptions. The
exception indicates that this program has been corrupted in memory generally resulting in the
immediate termination of the program. Also see document CH000224 for additional information
about GPFs.
14(Oeh)=Page Fault
Occurs when a paging protection rule is violated (when the retrieve fails, data retrieved is invalid or
the code that issued the fault broke the protection rule for the processor).
16(10h)=Coprocessor error fault
Occurs when an unmasked floating-point exception has signaled a previous instruction.
17(11h)=Alignment Check Fault
Only used on 80486 computers. Caused when code executing at ring privilege 3 attempts to access
a word operand that is not divisible by four, or a long real or temp real whose address is not
divisible by eight.
VI. HOW TO FIX A GENERAL PROTECTION FAULT.

Issue:
How to fix a general protection fault.
Cause:
There are several possibilities and reasons a computer receives a General Protection Fault error,
below is a listing of some of the more common reasons.
1. The program being used is calling a section of memory that is already being used by
another program or TSR.
2. The program has not been programmed properly or is still in testing and is calling an invalid
portion of memory.
Solution:
The following are recommendations into finding the cause of a GPF and or resolving a GPF. It is
important to know that GPFs are always likely to occur on the computer and if you are experiencing
a GPF rarely such as once every few weeks to not worry about attempting to locate the root cause
of that GPF. However, if you are experiencing GPF error messages often it is recommended you
follow the following recommendations to help resolve your issues.
Remove all TSRs
Disable or unload any TSRs or programs currently running before running the program causing the
GPF.
19 | C P I C - C H S

may have an issue causing the swap file or data files to become corrupt or invalid.
Verify your computer has more than 200 MB available
If your computer is running low on hard disk space, your Windows swap file will be unable to
increase in size when needed, causing programs to be swapped between memory and the hard disk
drive more frequently. When this occurs it is more likely that a GPF can occur.
If you have recently installed new software or hardware attempt to uninstall or reinstall that
Disable external cache
If your CPU utilizes external cache attempt to disable it temporarily to verify if it is causing your
GPF error messages. If available, you will be able to disable your external cache through CMOS.
If this resolves your issue it is recommended that you contact your manufacturer or motherboard /
CPU manufacturer for additional recommendations and/or BIOS updates that may resolve your
issue.
Disable Power Management / Screen savers
If you are receiving GPFs when away from the computer or during durations when your computer is
inactive, attempt to disable power management and screen savers to ensure that they are not
causing your issue.
Operating System issue
It is possible for Windows or an overwritten Windows related file to cause a General Protection
fault. Most commonly the General Protection Fault with Explorer and KRNL386.EXE. Attempt to
reinstall your operating system to resolve the issue.
Bad memory or other bad hardware
If you have followed all of the above recommendations and continue to experience GPFs it's
possible hardware inside your computer may also be bad. Often bad memory is the primary cause
for random GPFs.
VII. Runtime errors.
Issue:
Runtime errors.
A runtime error, in general, is an error generated during the time at which the computer is
running a software application and experiences an issue. Below is additional information and
help in resolving an actual runtime error.
Cause:
The runtime or run-time error message can be caused by:
20 | C P I C - C H S
1. Confliction with TSR or other running program

2. Software issue
3. Computer Virus
4. Memory issue
Solution:
Before following the below recommendations for troubleshooting your runtime error if you're
getting a runtime error with a runtime error code and error message such as "Runtime error 75
path/file access error", skip to the below runtime error listing for a listing of runtime error codes
and additional information and causes for these errors.
Confliction with TSR or other running program
If you are encountering a runtime error message while in Windows or above ensure that the issue
is not being caused by a third-party program or TSR by end tasking all open programs.
If, after end tasking all TSRs, you continue to experience the same issue and are running Windows
95 or Windows 98, verify that no utility or program is being loaded in the autoexec.bat / config.sys
that is causing your issue by temporally renaming the files. To do this, follow the below
instructions.
1. Boot to a MS-DOS prompt.
2. Once at the MS-DOS prompt, type:
cd\ <press enter>
ren autoexec.bat autoexec.ch <press enter>
ren config.sys config.ch <press enter>
Once completed, reboot the computer.
Software issue
If your issue persists it is possible that the program, utility or game causing the runtime error may
have issues. Verify through the developer's web site that all updates or patches that may be
available have been downloaded and applied.
If no patches or updates are available, attempt to uninstall and/or reinstall the program that is
causing the issue. If you are having a runtime error in your operating system, reinstall the
operating system.
Add-on, plug-in, or other extra software
Many runtime errors are also caused by other add-ons, plug-ins, or other extra software that has
been installed onto the computer and is associated with the program generating the error. If you
have any extra software installed that is associated with the program generating the error make
sure there are no available updates for the programs and/or try uninstalling each of them to verify
they're not the cause of your issue.
Computer virus
Because computer viruses are capable of tampering with the system settings / memory it is
possible for a computer virus to generate a runtime error. If you are currently running a virus
protection program on your computer ensure it has the latest updated patch or .dat file.
21 | C P I C - C H S
If you do not have a computer virus protection program it is recommended one be purchased or
that a demo be temporarily downloaded to scan your computer hard disk drive for viruses.
Memory issue
Finally, if you have followed all of the above recommendations, it is possible that you may be
encountering a hardware / memory related issue. We recommend that you first contact the
developer of the program causing the issue for any possible solutions. If no solutions are found, we
recommend you contact the computer or motherboard manufacturer for additional
recommendations and/or service.
Runtime error listings
Below is a listing of Microsoft Windows and Windows software runtime error codes and related
Runtime error messages. If you're encountering one of the below runtime error codes and have a
matching runtime error message see the associated additional information column for causes and
information about that runtime. If the additional information does not help resolve your issue try
the recommendations under the above solution section.
Runtime
error code
Runtime error message
Illegal function call
Overflow
Out of memory
Subscript out of range
10
Duplicate definition
11
Division by zero
13
Type Mismatch
14
Out of string space
19
No Resume
22 | C P I C - C H S
Additional information
Program error, verify the program has all the latest
updates. If updated try reinstalling the program. If you
continue to have the same errors contact the software
developer.
developer.
This issue can be caused when the computer does not
meet the programs system requirements or to much
memory is already being used for the program to run.
If your computer meets the requirements try first
reinstalling the program to make sure it's not an issues
with the program installation
developer.
developer.
Problem with a math formula in the program or the
programs code. Verify no software updates are
available for the program causing this error.
Make sure your system regional settings are setup
correctly and that the program you're running is made
for your version of Windows.
developer.
20
Resume without error
28
Out of stack space
35
Sub or Function not defined
48
Error in loading DLL
52
Bad file name or number
53
File not found
54
Bad file mode
55
File already open
58
File already exists
61
Disk full
62
Input past end of file
63
Bad record number
64
Bad file name
68
Device unavailable
70
Permission denied
23 | C P I C - C H S

developer.
developer.
This issue can be caused by a program or memory
error..
developer.
This issue is often caused with a bad installation or an
issue caused after another program has been installed
that replaced the programs DLL. Close all programs
and TSRs and try installing the program again.
developer.
File required by the program to run is not found.
Program needs to be reinstalled or missing file(s) need
to be copied back to the computer.
developer.
Program or file associated with program is being used
and program does not have access to use it. Try
closing all open programs and run program again.
developer.
The disk, for example, the hard disk drive does not
have enough space for the program to run or for
associated files to be copied to. Free up disk space on
the computer hard drive.
updates. If updated try reinstalling the program.
developer.
developer.
A hardware device or necessary requirement for the
program is not being found. Verify all hardware and
software required by the program is installed. If you
continue to have the same issues verify the latest
updates are installed for the program as well as any
hardware device the program needs.
The location of where the program is being copied to
does not have proper rights. Or a file that is trying to
71
74
75
76
91
93
94
102
339
429
438
439
440
901
be copied over because it's currently being used. Try

closing all programs and TSRs and running/installing
the program again. Additional information about
closing TSRs can also be found on document CHTSR.
Verify you have proper rights to the location you are
Disk not ready
attempting to install the program to.
Can't rename with differentupdates. If updated try reinstalling the program. If you
drive
developer.
Program does not have rights or access to a file. Often
this is caused when a program is trying to access a
network file it doesn't have proper access to either
Path/File access error
because of network privileges or something is blocking
the program. This issue can also be caused when the
file is being used by another program or is read-only.
Directory of where the program needs to be copied to
Path not found
or files associated with the program need to be copied
to is missing. Try reinstalling the program.
Object variable set to Nothing
developer.
Invalid pattern
developer.
Illegal use of NULL
developer.
Command failed
developer.
An associated program file is missing or corrupt. Try
A file is missing or invalid
reinstalling the program.
Program is corrupted, try reinstalling the program
Object creation failed
generating the runtime error.
No such property or method
developer.
Argument type mismatch
developer.
Object error
developer.
Input buffer would be largerProgram error, verify the program has all the latest
than 64K
24 | C P I C - C H S
902
903
904
905
906
1001
1025
developer.
Verify the program is compatible with your version of
Operating system error
Windows and/or has any software updates.
External procedure not found
developer.
Global variable type mismatch
developer.
A setting either in the program shortcut or being
User-defined type mismatch defined by the user is correct. Try running just the
program without any additional settings or variables.
External procedure interfaceupdates. If updated try reinstalling the program. If you
mismatch
developer.
This issue can be caused when the computer does not
meet the programs system requirements or to much
memory is already being used for the program to run.
If your computer meets the requirements try first
Out of memory
reinstalling the program to make sure it's not an issue
with the program installation.
DLL is not supported
This issue is often caused with a bad installation or an

issue caused after another program has been installed
that replaced the programs DLL. Close all programs
and TSRs and try installing the program again.
VIII. DIVIDE ERROR.

Issue:
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.
Cause:
1. Hardware / software incompatibility
2. Error with autoexec.bat / config.sys
3. Driver issue
4. Software issue
25 | C P I C - C H S
5. External Cache / 2nd level Cache

6. Improper calculation
7. Operating System issue
8. Hardware issue
Solution:
Hardware / 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/or determine if there are updates or
replacements to the software being used.
Error with autoexec.bat / 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 / 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 below instructions:
1. Click Start / Shutdown and restart the computer in a 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.
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/or patches.
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/or 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 third-party programs / TSRs.
26 | C P I C - C H S
External cache / 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 / 2nd level cache. Temporarily disabling this feature in CMOS may
resolve your issue.
Improper calculation
If you are performing a calculation in any type of 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 an error such as #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
it is possible that your computer may have a hardware issue. Generally, when a Divide Error is
encountered because of hardware it is caused by an issue with the computer Processor (CPU).
IX. ISSUES RELATING TO MSGSRV32.

Issue:
Issues relating to msgsrv32.
Note: It is known that users may confuse msgsrv32 with msgrv32. While msgrv32 is a spelling
error, it is related to this document.
The file Microsoft msgsrv32.exe or msgsrv32.dll is a file located in the C:\Windows\SYSTEM
directory placed on the computer during the Windows installation. The description of this file is
"Windows 32-bit VxD Message Server" and is responsible for such Windows tasks as:
Handle Plug and Play messages between various parts of the operating system.
Handle responses to and from setup programs.
Display the initial logon dialog box if a network is present or profiles are enabled.
Play the system startup and shutdown sounds.
Load the Windows drivers at startup and then unload them at shutdown.
Run the shell program.
Cause:
Errors or issues relating to msgsrv32 can be caused by any of the below possibilities.
1. Resource conflict or issue
27 | C P I C - C H S
2. TSRs or other running programs

3. Sound driver or sound card issues
4. Onboard sound or video issue
5. MIDI device or codec issues
6. Power Management or screensaver issue
7. Microsoft Find Fast related issue
8. Memory manager being used
9. Issue with shell
10. Computer virus or back orifice
11. Bad hardware
Solutions:
NOTE: If you are unable to boot into Windows because of the MSGSRV32 error, attempt to follow
the below steps in Windows Safe Mode.
Resource conflict or issue
Before attempting any of the below recommendations, ensure that 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 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
First, ensure that you have the correct audio devices in Multimedia by following the below steps:
1. Click Start / Settings / Control Panel 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/or updates installed from the
computer or motherboard manufacturer (if onboard sound).
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 below steps:
1. Click Start / Settings / Control Panel
2. Double-click the Multimedia icon
28 | C P I C - C H S
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 wish 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, it is possible that your computer may have issues
with Power Management. To attempt to resolve these issues, please 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, attempt to disable Power Management by clicking Start / Settings /
Control Panel / 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
/ Startup. If "Find Fast" or "Microsoft Find Fast" is listed, remove this program from automatically
loading each time your computer boots; follow the below steps:
1. Click Start / Settings / 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), it is possible that the
msgsrv32 error is being encountered because of the third-party shell. Temporarily disable or
remove the third-party shell and attempt to use the standard Windows explorer.
29 | C P I C - C H S
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.
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, it is possible your computer may have another type of software or
data corruption causing the issue.
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, it is possible that 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 / 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 below instructions.
1. Click Start / Find / 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.
30 | C P I C - C H S
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.
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.
X. WHY DO WINDOWS PROGRAMS STOP RESPONDING.

Issue:
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.
Solution:
To recover from a program that has stopped responding, a user can generally press the CTRL + ALT
+ DEL keys on his or her keyboards to open the "Close Program" window or open the "Task
Manager" window 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.
It is important to realize that when a program stops responding any work that has not been saved
will more than likely be lost when end tasking a program. Unfortunately, there is no alternative.
XI. REGAINING COMPUTER HARD DISK DRIVE SPACE.
Issue:
Regaining computer hard disk drive space.
Answers:
Microsoft Windows 95, 98, ME, 2000, and XP users
Users can regain computer hard disk space by performing any or all of the below steps.
1. Click Start, Search or Find, in the text field for a file type *.tmp and make sure the
computer is looking in the C: drive or the drive that contains your Operating System. Delete
each of the temporary files that are found.
2. Perform the same steps as number one except search for *.chk and delete any of the files
that are found.
31 | C P I C - C H S
3. Uninstall software programs; additional information about how to do this can be found in
document CH000347.
Additional tip for Windows 98 SE, Windows ME, Windows 2000, and Windows XP users:
These versions of Microsoft Windows include a "Disk Cleanup" feature that can help you
clean up any unnecessary files; below are the steps to perform this operation.
1. Open My Computer
2. Right click on the hard disk drive that you wish to regain hard disk drive space. For
example, right click on the C: drive.
3. Click Properties.
4. Within the General tab, click the "Disk Cleanup" button located next to the pie chart.
5. Within the Disk Cleanup window you will be able to perform various steps to help gain
additional hard disk drive space as well as information to how much you will gain by
performing each of the steps.
When performing the above steps, our only recommendation would be to be familiar with the
implications of compressing your hard disk drive. If at all possible, we recommend users do not
compress their hard disk drive and/or compress their old files.
Additional suggestion for Windows 2000 and Windows XP users:
Window 2000 and Windows XP keeps all the necessary files needed to uninstall any of the
updates ever installed on your computer. Often this is several dozen updates that can take
up several hundred and sometimes over 1 gig of space on your hard disk drive. See
document CH000849 for additional information about these folders, how to locate them, and
delete them.
Final tip for Windows XP users:
Windows XP users can also decrease the default space utilized by Windows System Restore
and often gain several additional gigabytes of hard disk drive space. See the below steps in
customizing this feature.
1. Click Start, Programs, Accessories, System Tools, and open "System Restore".
2. Within the System Restore window, click "System Restore Settings".
3. Within the "System Restore" tab you can either check the "Turn off System Restore on all
drives" to completely disable this feature, or click the Settings button and decrease the
space usage, which we would recommend.
MS-DOS and Windows 3.x users
Users can regain computer hard disk drive space by performing any or all of the below steps.
1. From the MS-DOS prompt, type "del *.tmp /s" and "del *.chk /s". This command will delete
any temporary files or scandisk error files on the hard disk drive.
32 | C P I C - C H S
2. Delete any software programs or games you are no longer using from MS-DOS or from
Windows.
See our del command page or our deltree command page for additional information about each of
these commands.
Additional information about determining how much hard disk drive space you have can be
found on document CH000369.
See document CH000347 for additional information about uninstalling Windows software.
XII. WINDOWS RESTARTS WITHOUT WARNING.

Question:
Windows restarts without warning.
This document is about computers that are restarting or rebooting by themselves, if your computer
is turning off and remaining off please see document CH000689.
Some of the below steps in the answer require you open your computer and remove hardware
devices, while in the computer make sure you're aware of ESD.
.
Cause:
This issue could be caused by any of the below possibilities.
1. Software issue or error.
2. Hardware issue or error.
3. Heat related issue.
4. Computer virus.
5. Issue with operating system.
Answer:
Software issue or error
Errors generated by software programs can cause a computer to reboot unexpectedly or without
warning. If you are running Windows XP see the below section "For Windows XP users" before
continuing.
If you are not running Windows XP or following the below steps still cause your computer to reboot
without warning. Boot your computer into safe mode, and let the computer run in safe mode.
If the computer is still rebooting in safe mode the issue is likely not software related but something
else, skip to the next section. If the computer is not rebooting in safe mode it is likely you have
software related issue.
For Windows XP users
33 | C P I C - C H S
Windows XP is designed to automatically reboot each time an error occurs such as a BSoD.
Although this may be nice for errors that do not occur often, users who have a re-occurring error
may wish to identify the error to troubleshoot it. Below are the steps on how this feature can be
disabled and enabled in Windows XP.
1. From the desktop right click on My Computer.
2. Click the Properties option.
3. In the System Properties window click the Advanced tab.
4. In Advanced click the Settings button under Startup and Recovery.
5. In the Startup and Recovery window uncheck the Automatically restart check box.
6. Click Ok.
Now if the computer generates and error it should not automatically restart and enable you to
display any errors your computer may be experiencing.
Hardware issue or error
Any failing hardware component in your computer could cause your computer to unexpectedly
generate an error and/or reboot without warning. If you have recently attempted to add a new
hardware device, remove that device to make sure it is not causing your issues.
Make sure you are not encountering any hardware conflicts by viewing Device Manager for errors.
New drivers can also cause this issue, if you have recently performed any hardware driver updates
you may wish to try an earlier version of the drivers.
If you have updated drivers and removed any hardware that could be causing this issue and
continue to experience random reboots, it's possible that the memory is bad in the computer.
Finally, hardware devices that are not installed properly in the computer can also cause random
reboots. Make sure all the cables and expansion cards are connected properly to the computer. The
best way to determine this is to disconnect and reconnect all cables and expansion cards.
Computer virus
Computer viruses such as the blaster virus are written to reboot your computer without warning.
Usually these viruses will make the computer reboot ever 5, 10, 15 or 30 minutes after the
computer has booted.
If you believe your computer may be infected with a virus or are uncertain if your computer is
infected with a virus make sure your virus scanner definitions are up to date.
Heat related issue
Many computer today are designed to turn off or automatically reboot if the computer, processor, or
other device in your computer gets to hot. If you have heard any abnormal noises coming from
your computer recently such as a high squealing this could indicate a fan may be failing in your
computer.
You can first start by verifying the fan on the power supply is working by examining the back of the
computer and seeing if the fan is moving and moving smoothly. For all other fans in the computer
you will need to either open the computer and make sure the fan are working (processor fan and
34 | C P I C - C H S
case fan) and/or if your BIOS monitors the RPM of the fans enter BIOS and make sure the BIOS
does not report any errors.
Users may also be able to determine how hot their computer is by onboard thermal sensors, if your
computer comes equipped with these sensors make sure your CPU is not running to hot, additional
information about how hot your CPU should be running can be found on document CH000687.
Issue with operating system
If after following each of the above recommendations your computer still continues to reboot it is
likely that you are experiencing a Microsoft Windows operating system related issue that cannot be
explained. To help make sure this is the case please try the below steps.
1. Reboot the computer and enter CMOS setup as the computer is booting
2. After you have loaded the computer in CMOS setup let the computer sit.
If the computer does not reboot while letting the computer sit in CMOS it is likely that you are in
fact experiencing an issue with Microsoft Windows and it is recommend that if you have followed all
of the above recommendations that you reinstall your version of Microsoft Windows.
XIII. COMPUTER TURNS OFF WITHOUT WARNING.

Question:
Computer turns off without warning.
Cause:
2. Hardware issue or error.
3. Computer virus.
4. Issue with operating system.
5. Other failing hardware
This document is about computers that completely turn off;
Some of the below steps in the answer require you open your computer and remove hardware
devices. While in the computer, make sure you're aware of ESD.
Answer:
Heat related issue
A computer that turns off without warning is often a heat related issue. Many computers today are
designed to turn off or automatically reboot if the computer, processor, or other device in your
computer gets too hot. If you have heard any abnormal noises coming from your computer recently
such as a high squealing, this could indicate a fan may be failing in your computer.
35 | C P I C - C H S
computer and seeing if the fan is moving and moving smoothly. For all other fans in the computer,
case fans) and/or if your BIOS monitors the RPM of the fans, enter BIOS and make sure the BIOS
While inside the computer it's also a good idea to verify the processor heatsink is properly
connected by disconnecting and reconnecting the heatsink. If the processor heatsink is not properly
it will not keep the processor cool causing the computer to overheat.
Users may also be able to determine how hot their computer is by onboard thermal sensors. If your
computer comes equipped with these sensors, make sure your CPU is not running to hot;
Hardware issue or error
Any failing hardware component in your computer could cause your computer to unexpectedly turn
off without warning. If you have recently attempted to add a new hardware device, remove that
device to make sure it is not causing your issues.
Before attempting to remove any hardware, make sure you are not encountering this issue because
of hardware conflicts by viewing Device Manager for errors. Additional information about Device
Manager can be found on our Device Manager page.
If you have not recently installed any new hardware into the computer, the next best solution to
determining if this is a hardware issue would be remove any hardware on the computer that is not
needed. For example, remove your modem, network card, sound card, and any other expansion
cards that are not needed for the computer to operate. Run the computer without these cards to
see if they are the cause of your issue.
Computer virus
It's possible for your computer to be infected with a virus that is designed to shut down your
computer or turn it off. If your computer seems to be turning off when executing a certain program
at specific times in the day, it could be infected.
If you believe your computer may be infected with a virus or are uncertain if your computer is
infected with a virus, make sure your virus scanner definitions are up to date.
Issue with operating system
If after following each of the above recommendations your computer still continues to reboot, it is
likely that you are experiencing a Microsoft Windows operating system related issue that cannot be
explained. To help make sure this is the case, please try the below steps.
1. Reboot the computer and enter CMOS setup as the computer is booting. If you are not
familiar with how to enter CMOS,
2. After you have loaded the computer in CMOS setup, let the computer sit.
If the computer does not turn off while letting the computer sit in CMOS, it is likely that you are in
fact experiencing an issue with Microsoft Windows or your operating system and it is recommend
that if you have followed all of the above recommendations that you reinstall your version of
Microsoft Windows.
36 | C P I C - C H S
Other failing hardware

If after reinstalling your operating system, or during the installation of your operating system, your
computer turns off abnormally, it is very likely that other hardware is failing in the computer. Often
this is RAM, CPU, Motherboard, and/or Power Supply (in that order).
If you have extra available parts or have a friend or co-worker with a similar configuration that is
willing to allow you to test their hardware in your computer, try swapping these parts to determine
if they are at fault. Otherwise, you will need to have the computer serviced.
XIV. WINDOWS FREEZES OR STOPS RESPONDING FREQUENTLY.
Question:
Windows freezes or stops responding frequently.
Cause:
1. Software related issue.
2. Driver related issue.
3. Operating system related issue.
5. Hardware issue.
6. Serious issue with Windows
7. Hardware failure.
Answer:
This document contains recommendations on what to do if the computer frequently freezes or
completely halts. An easy way to determine if your computer is in this situation is by pressing the
Num Lock button on the keyboard and watching the Num Lock led to see if it turns off and/or on.
If you're able to get the light to turn off an on, press CTRL + ALT + DEL and attempt to end task
the program. Additional information about this can be found on document CHTSR. Otherwise
continue reading this document.
Software related issue
A computer locking up or freezing is often is caused by a software related issue. If you're
encountering lockups when the computer is opening a particular program, make sure you have all
the latest updates for that program. You can find the latest updates for your software through the
software developer or publisher.
Driver related issue
A computer lock up can also be caused by drivers. For example, if there is an issue that exists with
your video drivers a computer could lock up while playing a game or displaying any other type of
video. Make sure you have the latest drivers for all major devices in your computer (video, sound,
modem, and network).
Operating system related issue
Make sure your operating system has all of the latest updates installed on it.
37 | C P I C - C H S
Heat related issue

If the computer processor is getting too hot it can cause the computer to freeze. If you have heard
any abnormal noises coming from your computer recently such as a high squealing, this could
indicate a fan may be failing in your computer.
computer and seeing if the fan is moving and moving smoothly. For all other fans in the computer
case fan) and/or if your BIOS monitors the RPM of the fans, enter BIOS and make sure the BIOS
Users may also be able to determine how hot their computer is by onboard thermal sensors. If your
computer comes equipped with these sensors, make sure your CPU is not running too hot.
Hardware issue
In addition to software, hardware can also cause a computer to lock. If you have recently added
any new hardware into the computer, try temporarily removing it to make sure it is not the cause
of your issue.
Before attempting to remove any hardware, make sure you are not encountering this issue because
of hardware conflicts by viewing Device Manager for errors.
If you have not recently installed any new hardware into the computer, the next best solution to
determining if this is a hardware issue would be remove any hardware on the computer that is not
needed. For example, remove your modem, network card, sound card, and any other expansion
cards that are not needed for the computer to operate. Run the computer without these cards to
see if they are the cause of your issue.
Note: When opening the computer, make sure you are aware of ESD and its potential dangers. See
our ESD page for additional information.
Serious issue with Windows
If you have tried all the above recommendations and the computer continues to frequently lock up,
its possible that Windows may be seriously corrupt. Try running through the basic troubleshooting
steps for your version of Windows on our basic troubleshooting page. If these additional steps do
not resolve your issue, we suggest you backup all information and erase and reinstall Windows on
your computer.
Hardware failure
If after reinstalling your operating system, or during the installation of your operating system, your
computer turns off abnormally, it is very likely that other hardware is failing in the computer. Often
this is RAM, CPU, Motherboard, and/or Power Supply (in that order).
If you have extra available parts or have a friend or co-worker with a similar configuration that is
willing to allow you to test their hardware in your computer, try swapping these parts to determine
if they are at fault. Otherwise, you will need to have the computer serviced.
What should I do when a computer freezes?
Question:
What should I do when a computer freezes?
Answer:
This document contains recommendations on what to do if the computer frequently freezes or
completely halts. An easy way to determine if your computer is in this situation is by pressing the
38 | C P I C - C H S
Num Lock button on the keyboard and watching the Num Lock led (light) to see if it turns off
and/or on.
If you're able to get the light to turn off and on and are running Microsoft Windows, press CTRL +
ALT + DEL and attempt to end task the program.
Make sure the computer is really frozen
Although the above Num Lock trick is a good indication on whether or not the computer is really
frozen, it's still always a good recommendation to give the computer at least a minute before
turning it off.
Reboot the computer
After waiting a minute, reboot the computer; it's completely locked and will not recover. Keep in
mind that all work being worked on is going to be lost and cannot be recovered if the information
has not been saved or automatically saved.
XV. NOT A VALID WIN32 APPLICATION.
Question:
Not a valid Win32 application.
Often this error message will be similar to the below error message.
C:\Program Files\myprogram\program.exe is not a valid Win32 application.
Cause:
1. File is corrupt, bad, or missing.
2. File is not designed for your version of Windows.
3. File is a virus, worm, or other malware file.
4. Hardware incompatibility.
Answer:
File is corrupt, bad, or missing
If the file or program you're attempting to run is corrupt or missing, Windows will be unable to
execute the file properly and sometimes generate this error message.
Download files
If you downloaded this file and verified it is a file that will work with your version of Windows,
delete the file and try downloading and running it again. It's possible during the download that the
file became corrupted.
Finally, if the second download does not work, try downloading the file from a different webpage. It
is possible that the person or company maintaining the website mistakenly uploaded a corrupt
version of the file you're attempting download.
Installing a program from a CD or other disk
39 | C P I C - C H S
If you're attempting to install a program and are getting this error, verify that the CD is clean. If
the CD is dirty or bad, you could get this error during the install and/or get this error after the
program has been installed because it was not copied properly onto the computer.
Running a program from the computer
If you're running the program from a shortcut on the computer, verify that the program is still on
the computer. In some cases if the program is no longer installed on the computer you may get this
error.
If the hard disk drive is corrupted or bad it can also cause working programs to fail either because
not all the data can be read from the hard disk drive or because the program has become
corrupted while on the drive. Run scandisk and defrag on the hard disk drive to check for any
potential errors.
Long file name issue
Make sure the program or file you're attempting to run does not contain the same name as the
long file name directory it is contained in. For example, executing a file named "program" in the
"program files" directory can cause errors in some versions of Windows.
Additionally, if you're attempting to install a program and after the install the program does not
work, you may also want to try installing the program in a different directory.
Bad file
Any file can be changed or renamed to be a .exe file. If you're downloading the file, make sure the
file is supposed to be a .exe file and that it's not being changed. If you're attempting to create a
.exe, file make sure you're compiling the file for Windows and never just rename a file to a .exe
file. For example, renaming a .bat file to a .exe file will not make the file an executable file. For a
file to become an executable file it needs to either be compiled or converted through a software
program designed to convert the file.
File is not designed for your version of Windows
If you're trying to run a program that is not designed for your version of Windows you may get this
error. Although many older programs designed to work in older versions of Windows will work with
new versions of Windows, unfortunately, not all programs will work.
If the program is an older MS-DOS program or early Windows program you may get this
error.
If the program is designed for a 64-bit version of Windows and you're running it in a 32-bit
version of Windows, it will not work and generate this error.
FILE IS A VIRUS, WORM, OR OTHER MALWARE FILE

This error can be generated by a file that is a virus, worm, trojan, or other type of malware file.
Often, this will be caused because the virus scanner installed in the computer will not allow the file
to be installed or run. Try scanning the file to verify it is not a virus and/or infected.
If the file has been checked and is clean, it is still possible that the virus protection program and/or
another program installed on the computer is causing issues during the install or execution of the
program. Boot the computer into safe mode and try running the program; booting the computer
into safe mode will make sure nothing is running in the background that could be causing this
issue.
40 | C P I C - C H S
HARDWARE INCOMPATIBILITY
If you're getting this error during the installation of a program it's also possible that the CD-ROM
drive or the drive you're installing the program from is not compatible with Windows or has drivers
that are not compatible with Windows.
Download the latest drivers for your CD drive or other drive through our drivers page.
XVI. MISSING MICROSOFT WINDOWS .DLL FILES.
Question:
Missing Microsoft Windows .dll files.
Cause:
A missing or corrupt .dll file can be caused by any of the below possibilities.
1. Another program was uninstalled that removed a .dll file that was required by another
program or the operating system.
2. A program was installed that overwrote the .dll file with either an older version or a version
that is incompatible with other programs causing .dll errors.
3. A bad installation of a program corrupted one or more files causing the .dll errors.
4. Another user or program maliciously or mistakenly deleted the .dll file or an associated file.
5. A hardware issue exists with the computer, such as a bad hard disk drive, causing the data
on the drive to become corrupt, casing the .dll errors.
Answer:
This document is meant to be a solution for users who are encountering missing .dll errors or other
error messages related to .dll files. Before trying the recommended resolutions to resolving these
errors, we suggest if you're getting a single missing .dll error, that you search for that .dll file on
Computer Hope.
For example, if you're getting an error similar to "Internet Explorer encountered an error in
KERNEL32.DLL at 0137:BFF3191C", search for "kernel32.dll" to make sure a specific document has
not been created for your issue. In some situations a .dll file error may be caused by a specific
situation.
If the Computer Hope search does not return any results for your .dll file or you're encountering
issues with several different .dll files, continue reading our recommendations for resolving your
issue.
Downloading a .dll file
In some situations, it may be possible to download or copy a .dll file from another computer onto
your computer to resolve the issue. However, because .dll error messages are almost always a
more serious issue and/or replacing the missing .dll file with a replacement will cause additional
errors or report additional missing files, we suggest you try the below suggestions first.
If you still wish to try to download or copy a missing .dll file, unfortunately, Computer Hope does
not have a library of downloadable .dll files; however, there are several other sites that do offer this
service
41 | C P I C - C H S
Safe mode
If you're encountering .dll errors that are preventing you from getting into Windows, to
troubleshoot the computer, boot the computer into safe mode. Additional information and help with
getting into Windows safe mode can be found on document CHSAFE. Once successfully in safe
mode, you can continue with the below steps.
If your computer boots normally and/or you're able to bypass the .dll errors and still operate
Windows, you can continue following the below steps.
Microsoft Windows XP and Windows 2000 users
If you're a Microsoft Windows XP or Windows 2000 user, Microsoft has included some tools that can
help resolve .dll file errors relatively easily; before trying any of the below recommendations you,
may want to first try the below suggestions.
Windows XP users only
First, try restoring the computer back to an earlier date, this troubleshooting step is a quick and
easy recommendation that can resolve a lot of issues encountered with Microsoft Windows
computers.
Windows XP and Windows 2000 users
Use the Windows XP SFC command to have windows scan and repair files; to run this command,
follow the below steps.
Click Start
1. Click Run
2. Type "sfc /scannow" and press enter.
Once the above steps have been completed, Windows will verify that all protected windows files are
intact.
Issue with .dll files only with a specific program
If you're encountering the missing, corrupt, or other errors relating to .dll files only when you
attempt to open or run a program, it's likely an issue with that program. Thankfully, resolving
program-specific errors can be much easier than operating system related .dll errors.
If the program you're attempting to run has worked in the past on your computer and has only
recently started to get the .dll errors, reinstalling the program generating the errors will almost
always resolve your problem.
Additionally, while reinstalling the program, it's also a good idea to check if updates or patches
have been made available by the developer of your program. Updates are often found through the
developer's website.
Recently uninstalled program
If you have recently uninstalled a program on the computer, it is possible that the program may
have removed a .dll file that is necessary for Windows or a Windows program to work properly.
If you've already tried the above recommendations, you may wish to reinstall the program to get
whatever file has been deleted back on the computer. If this resolves your .dll error message and
42 | C P I C - C H S
you wish to uninstall the program again, during the uninstall process, make sure that you click "No"
or "No to all" when asked to delete a system file or any file that may be used by another program.
Recently installed program
If you have recently installed a program and after the installation began encountering your .dll
error messages, we suggest you first check if updates are available for the program. In some
situations, a program may need to be updated for it to work properly on your computer. Updates
are often found through the developer's website.
If no updates are available for the program, try uninstalling the program to resolve the issue. If
this does correct your issue, we suggest you contact the developer of the program for additional
support on getting the program installed on the computer without it causing errors.
Virus, spyware, or other malware installed on the computer causing your .dll error
It is possible for a virus, spyware, or other malware program to cause .dll errors; and therefore, we
suggest users make sure to run a full virus and spyware scan on your computer.
Windows .dll error message or .dll errors when trying to do something within Windows
and not a program
Microsoft Windows .dll errors or .dll error messages that occur when starting Windows or trying to
do something within Windows, such as opening the Control Panel, can be more serious and
unfortunately more difficult to resolve.
If running through these steps you encounter the same issues to resolve your .dll errors, it is likely
you'll need to reinstall or erase everything and reinstall Windows to resolve your errors.
If issues continue after windows has been reinstalled or errors occur during the installation of
Windows, it's possible that you may have a hardware issue that is the cause of all your problems.
XVII. SOFTWARE TROUBLESHOOTING.
Issue:
Basic software troubleshooting.
This document has been created as a location of general steps that can be taken to help you with
problems you may be experiencing with computer software programs and software utilities. Below
are some reasons why a user may follow the steps in this document.
1. Unknown or undocumented problem with a computer software program.
2. Issue opening and/or running a software program.
Solutions:
Unable to install a software program
1. Verify the diskettes or CD are readable by reading the files on the drive. For example,
Microsoft Windows users can explore the drive in Windows explorer. If the CD attempts to
AutoPlay, you may need to right click the drive and click Explore to browse the drive.
2. If the CD reads fine with no errors verify your computer meets the minimum requirements
of the software program. If your computer does not have enough disk drive space or does
not meet the requirements, the program will not install.
43 | C P I C - C H S
3. Make sure the program or utility you are installing is compatible with the version of
Operating System you have on your computer. For example, many older utilities such as a
virus protection program may only work with a specific version of Microsoft Windows.
4. If you are getting stopped at the CD-KEY or Serial Number verification, verify you are
entering your correct number. If you lost your number or key or it does not work, you will
need to contact the developer of the program. Computer Hope will not provide any users
with an alternate identification number.
Error during installation
1. Verify your computer meets the requirements of the program or utility. For example, if your
computer runs out of disk space during the installation, this would cause an error during the
installation.
2. If you are running Microsoft Windows 95 or higher try installing the program from safe
mode.
3. Verify the CD is clean and contains no significant scratches.
4. Program or utility does not load or has an error when it attempts to load
1. Verify the program or utility documentation makes no mention of the error you are
experiencing. Many times the error and explanation to how to resolve the error are already
documented.
2. Verify no patches or updates are available from the developer of the program or utility. In
some cases the software program may require an update before it can be successfully run
on your computer.
3. Make sure all other programs are closed when you attempt to run the program or utility. If
the program successfully runs after closing all other programs, it's possible that the program
may have issues with other programs.
4. Make sure the computer has been rebooted at least once after the program has been
installed. In some cases it may be required.
5. Verify your computer has the correct date. In some cases a program may rely on the date
and if that date is incorrectly set it may cause issues.
6. If following the above recommendations does not resolve your issues, attempt to reinstall
the program or utility.
44 | C P I C - C H S

Reasons Why PCS Crash

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Reasons Why PCS Crash

Загружено:

Авторское право:

Доступные форматы

REASONS WHY PCS CRASH

* Start-Settings-Control Panel-System-Device Manager

ELEVEN TIPS FOR TROUBLESHOOTING SOFTWARE

COMMON ERRORS AND HOW TO FIX THEM

Bad, incorrect or not the latest video drivers.

Error in program coding

Corruption or problem within Windows.

k. Bad Memory, invalid bits or physically bad memory.

Bad, incorrect or not the latest video drivers:

Error in program coding:

Corruption or problem within Windows:

Issues in Windows 95 / 98 autoexec.bat / config.sys

III. Computer or processor is overheating

AMD Athlon64 Mobile

Intel Pentium III

Intel Pentium Mobile

Intel Pentium Pro

How will I know if my processor is running too hot?

IV. HOW TO FIX AN INVALID PAGE FAULT.

Run Scandisk / Defrag

Access to an illegal software instruction has occurred.

Invalid data or code has been accessed.

The privilege level of an operation is invalid.

Bad Memory, invalid bits or physically bad memory

11(0Bh)=Not Present Fault

VI. HOW TO FIX A GENERAL PROTECTION FAULT.

Delete all program temporary files

1. Confliction with TSR or other running program

Runtime error message

Illegal function call

Subscript out of range

Out of string space

Resume without error

Out of stack space

Sub or Function not defined

Error in loading DLL

Bad file name or number

File not found

Bad file mode

File already open

File already exists

Input past end of file

Bad record number

Bad file name

continue to have the same errors contact the software

be copied over because it's currently being used. Try

DLL is not supported

This issue is often caused with a bad installation or an

VIII. DIVIDE ERROR.

5. External Cache / 2nd level Cache

External cache / 2nd level cache

IX. ISSUES RELATING TO MSGSRV32.

Handle responses to and from setup programs.

Play the system startup and shutdown sounds.

Run the shell program.

2. TSRs or other running programs

3. Select the Advanced or Devices tab

Computer virus or back orifice

X. WHY DO WINDOWS PROGRAMS STOP RESPONDING.

Final tip for Windows XP users:

XII. WINDOWS RESTARTS WITHOUT WARNING.

XIII. COMPUTER TURNS OFF WITHOUT WARNING.