Paradym Forums  

Go Back   Paradym Forums > Support FAQs > Error Messages

Thread Tools Display Modes
Old 09-27-2001, 03:09 PM
rmoss rmoss is offline
VT Support and Training
Join Date: Sep 2001
Location: VisualTour Corporate Office
Posts: 739
Default General Protection Faults (GPF)

The General Protection Fault (GPF) error is generated by Windows when two programs are conflicting in memory. If the conflict is not eliminated, it is possible that the entire computer could lock up, and unsaved files in all open programs could be lost. The GPF, therefore, tries to shut down one of the two conflicting items before a lock up (and associated data loss) can occur.

The key to fixing a GPF is to determine what two items are conflicting. To make that determination, carefully examine the error message and look for a DETAILS button. You might have to click CLOSE before you will see the that button. When you find the DETAILS button, click it and look for a sentence at the beginning that looks something like this one.

VTMAIN.EXE caused a General Protection Fault in Module GeForce256 at (and then it lists seemingly endless numbers).

In this case, the conflict is between VTMAIN.EXE, which is a module of the VisualTour software, and GeForce256, which is a video driver (files ending in numbers like 16 and 256 are often video drivers). Since VTMAIN.EXE must be running to use VisualTour software, the solution is to get the other file not to run (or to at least run in a different manner) at the same time. To accomplish that task, we would change the video driver to an alternate setting or install a completely new video driver. Many general protection faults are video related, so it is always a good idea to try altering the video settings (Control Panel-Display-Settings) when the source of the GPF cannot be determined.

If the error is in VBRUN300.DLL, follow these steps.
  1. Click START - Find - Files and Folders, and do a search for vbrun300.dll.

  2. Rename every copy it finds. Use any name you want. You are just trying to hide the files from Windows. If Windows does not allow you to rename the file because it is in use, then restart Windows before renaming it.

  3. Restart Windows after renaming the file(s).

  4. Reinstall the VisualTour software (as a new installation - it will leave your existing data alone as long as you choose the same location for the new installation as you had before). The VBRUN300.DLL file(s) that you renamed will get replaced.

  5. Start the VisualTour software to ensure you are fixed.

If the error is in another module, try these steps.

Turning off background applications:
  1. Close other open programs.

  2. Right click items in the System Tray (the smaller icons next to the clock on the Windows task bar)

  3. If you recognize the module named in the error message, try shutting down that application whenever possible.

  4. If you do not recognize the module named in the error message, press CTRL-ALT-DEL and End Task on all items on the task list except for Explorer and Systray. If that fixes the problem, try just ending task on a few items until you determine which one is conflicting.
Safe Mode (a diagnostic mode of Windows):
Reboot your computer in safe mode (if you keep pressing the F8 key while rebooting, a menu will appear offering safe mode as an option). If the error goes away, you know the problem is related to video or some other hardware driver.

Replacing the Conflicting File:
Locate the file(s) mentioned in the error message using Start - Find - File or Folders, and rename it. In Windows sees that the file is in use, it will not let you rename it, in which case you will have to restart Windows before renaming it. Now try to run all your software. Whichever program fails to run is likely to include that file on its installation CD, so reinstall that program to get a fresh copy.

If you are running Windows 95/98/ME...
  1. Right click the My Computer icon on the desktop, and choose Properties.

  2. Click the Performance tab.

  3. Click GRAPHICS, move the Hardware Acceleration slider all the way to the left, and click OK.

  4. Still on the Performance tab, click FILE SYSTEM, choose the Troubleshooting tab, and check everything on the list except the one that refers to disabling all 32-bit protected mode disk drivers.

  5. Click OK or CLOSE to finish working in the Performance area. Windows will probably want to reboot.

  6. If those steps fix the problem, then go back and gradually reset the different items one by one to the old settings to see which one made the problem go away, thus telling you what caused the error.

For more information about General Protection Faults, visit Microsoft's Web Site and click SEARCH at the top of the page.
Reply With Quote

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is On

Forum Jump

All times are GMT -5. The time now is 03:20 AM.

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.