GPF's & Other Protection Faults

What Are General Protection Faults?

Each application running under Windows is assigned a block of memory in which it is permitted to operate. If an application tries to access memory outside its permitted block, the processor inside your computer will "trap" the request, ignore it, and raise this error message.

An application is not permitted to make such a request. If it does so this suggests that the application is "out of control". Probably a defect or corruption in the application has caused the problem.

What Happens If I Get a General Protection Fault (GPF) When Running CAPITAL?

There are two broad types of GPF fault:

1. Those that come and go randomly. It is hard to predict when the next one will occur.

Generally speaking, these are typically caused by hardware problems, configuration or compatibility problems between software and hardware and applications sitting in the "background" which may be conflicting with foreground applications. (Applications you see "up front".)

2. Those that can be consistently reproduced.

These types are usually easier to resolve. A certain set number of steps will produce the problem. This usually indicates a problem in the application (a defect or bug) or the corruption of the data that the application is working with.

It should be kept in mind that these are rules of thumb. Type 2 problems might look like type 1 problems and type 1 problems might look type 2 problems. Only use these broad categories as an initial guide to trouble-shoot the problem.

When attempting to resolve a GPF problem keep in mind that the application or program module that generates the error may not be the application that caused the error.

If you experience a GPF error when running CAPITAL always carry out these two steps before proceeding with any further steps:

1. Close Windows and re-start.

2. Run Scandisk to fix errors on your hard disk.

3. Do a Database Maintenance inside CAPITAL.

4. If you are using CAPITAL GL Controller, do a Database Maintenance inside the general ledger as well.

Carrying out these 4 steps can resolve many GPF problems related to data corruption. Further trouble-shooting will usually need to be carried out by a computer consultant. The broad areas that commonly cause problems are listed below:

    Incompatible or faulty video drivers or video cards

    Incompatible or faulty printer drivers

    Corrupted or defective background applications such as virus checkers, etc.

    Corrupted databases too badly damaged to be repaired using Database Maintenance. (A restore from back-up may be required.)

    Corrupted or damaged program files. (Usually DLL and EXE files.) Applications may need to be reloaded or restored from back-ups.

    Corrupted or damaged configuration and reporting files.

10/05/2001