General Protection Fault and Freeze-up Problems (C5 Errors)

 

17.3.1 General protection fault errors and freeze up problems can be caused by:

 

Insufficient RAM memory

Insufficient hard disk space

Insufficient swap file size

Hard disk corruption

Too many programs running at the same time or two programs are conflicting

Insufficient Resources

Memory leakage

Poorly written drivers (screen, print, etc.)

Conflicting hardware addresses and interrupts

Video driver conflict

Driver and or program conflicts in upper memory

Marginal network hardware

Invalid temp directory

Corrupt program or database files (exe, dbf, idx, mem, frx, frt)

Fragmented hard disk (local and or remote)

Print Spooler is turned off

 

17.3.2 Insufficient RAM Memory

 

pc/MRP for Windows requires a minimum of 8 Megs of RAM. You can check how much RAM your PC has  go to the Start Button, select settings, select control panel, select help and then select about Windows.

 

17.3.3 Insufficient hard disk space

 

Windows 95 require a minimum of at least 20 Megs of hard disk space be available for temporary files, print buffering and RAM memory overflow (swap file). You can check how much RAM your PC has by going to the MSDOS prompt and entering the command CHKDSK[Rtn]. Once you have typed CHKDSK [Rtn] your screen will indicate the amount of bytes on your hard disk available to your PC. If your PC has less then 20,000,000 bytes available on disk, delete non-essential files on the hard disk to increase the space available on your hard disk.

 

17.3.4 Insufficient swap file size

 

Windows 95 requires at least 20 Megs of hard disk space for a swap file.   To check and or set your swap file size with Windows 95 you would select start, select settings, select control panel, select systems, select performance, and select virtual memory. If the free hard disk space is less than 20 Megabytes, you should remove unnecessary files from your hard disk to free up a minimum of 20 Megabytes. Be sure the radio button allowing Windows to manage memory is selected.

 

17.3.5 Hard disk corruption

 

You can use Microsoft's program called SCANDISK to check for hard disk corruption. If SCANDISK finds errors it can correct the errors, unfortunately in some cases the damage may have already been done (cross-linked files), and one or more files may be permanently damaged. Only re-installing the damaged file would correct the problem.

 

To run SCANDISK from Windows 95, exit Windows and go to the DOS prompt. Change to the Windows command directory by entering CD\WINDOWS\COMMAND[Rtn] and then SCANDISK[Rtn].

 


17.3.6 Too many programs running at the same time or two programs are conflicting

 

Windows can crash if too many programs are running at the same time taking up additional resources. Users have a tendency to load up programs (anti-virus, screen savers, office, etc.) in their start up file and run them in the background. Try running pc/MRP by itself to see if the frequency of crashing and or freeze ups is reduced. When programs are placed in the startup menu, these programs are drawing valuable resources even though they are not being used. Remove all programs from your startup menu and see if the frequency of crashes and freeze ups are reduced.

 

To check the number of programs running with Windows, press the Control ALT and DEL buttons, select Task Manager, and Applications.

 

Virus checkers that remain active during normal activation can cause problems. Deactivate the active virus checker and run the virus checker whenever you want to check your files but not while you are running other programs.

 

Older models of HP printers now came with a printer status programs that can cause problems. Disable the printer status program.

 

17.3.7 Memory leakage

 

Some Windows programs display memory leakage. Going into and out of various programs will result in Windows losing memory resources as most programs do not give back the original amount of memory they used after they have been run for awhile. If crashes are occurring in the afternoon, check the computers resources, if they are down, consider rebooting at lunchtime as a matter of routine precaution to recover lost memory.

 

17.3.8 Conflicting hardware addresses and interrupts

 

PC devices that occupy the same address or interrupt as another device can cause general protection fault and freeze up problems.  

 

To check for hardware device conflicts with Windows, select start, select settings, select control panel, select system, select device manager. If any of the devices display a ! in a yellow triangle, click on properties to see the conflict.

 

17.3.9 Video driver conflict

 

Non-standard OEM video drivers can cause problems with FoxPro for Windows. Install Window's standard 16-color VGA driver and see if that fixes the problem.

 

To install the standard 16-color VGA driver in Windows 95 select settings, select setup, select options, select change system settings, select display, select VGA. If that clears up the problem, use the standard VGA or SVGA driver in the future.

 

Try running Window 95 in a "safe" mode (no program is allowed to use upper memory). Turn on the PC and press the F8 key when you see the words "Starting Windows 95". Select the "Safe mode". The safe mode does not use config.sys, autoexec.bat, command.com, windows drivers, print drivers, network drivers, or the start up programs. It uses Window's own generic 16-color VGA driver.

 


17.3.10 Driver and or program conflicts in upper memory

 

Drivers and or programs can conflict with other drivers and or programs in the upper memory area.

 

Try running Window 95 in a "safe" mode (no program is allowed to use upper memory). Turn on the PC and press the F8 key when you see the words "Starting Windows 95". Select the "Safe mode". The safe mode does not use config.sys, autoexec.bat, command.com, windows drivers, print drivers, network drivers, or the start up programs. It uses Window's own generic 16-color VGA driver.

 

17.3.11 Marginal network hardware

 

Marginal network cards and or cables can cause intermittent crashes. To stress test the network, go to each workstation and copy the contents of a large directory from the server to the workstation. The directory copy should take at least 5 minutes to test the network card, hub and cable adequately. As a final test copy (not move) a directory on the server to another directory on the server. If the last test fails, the network card on the server may be bad.

 

17.3.12 Invalid temp directory

 

At the command prompt, type ?SYS(2023), MSG(GETTEMPPATH()), or Select Configuration, About pc/MRP, and press F1. See if the TEMP variable points to a valid (existing) directory.

 

The BEST method would to run Windows Explorer and enter %temp% in the address bar and press GO. This method will give you the full path name.

 

You must then create such a directory if it does not exist.

 

17.3.13 Corrupt program files or data base files

 

Corrupt index files can cause general protection, illegal operation errors. Use the Configuration menu and select, "Re-index all files", to see if that corrects the problem. If you get a stack fault error or Internal Inconsistency Error message, delete the associated idx files and re-index.   

 

Data base files can become corrupt by exporting the dbf file to Excel, editing the data and importing the Excel file back into pc/MRP (Excel can change the structure of a column on its own based on the contents of the column).

 

17.3.14 Sleep Mode

 

Disable

 

17.3.15 Fragmented Hard Disk

 

Defrag your local hard drive.

 

17.3.16 Print Spooler is turned off

 

Select Control Panel, Printers (and Faxes), right-click on the default printer, and select Properties. Select “Print to spooler”, not “Printer”.