Microsoft KB Archive/139084

= ACC2: Troubleshooting GPFs in MS Access 2.0 under Windows 95 =

Article ID: 139084

Article Last Modified on 6/25/2002

-

APPLIES TO


 * Microsoft Access 2.0 Standard Edition
 * Microsoft Windows 95

-



This article was previously published under Q139084



Novice: Requires knowledge of the user interface on single-user computers.



SYMPTOMS
When you run Microsoft Access version 2.0 under Microsoft Windows 95, you may receive a general protection (GP) fault error message, such as the following:

MSACCESS caused a GP Fault in module KRNL386.EXE at 0001:00001a2a.



CAUSE
A GP fault signifies that something unexpected has happened within the Windows environment, typically an improper memory access. For example, a program or a Windows component may try to read or write to a memory location that has not been allocated to it, potentially overwriting and corrupting other program code in that area of memory.

Another situation where a GP fault may occur involves the passing of parameters between programs and the Windows environment. Invalid parameters can cause invalid instructions to be executed, resulting in GP faults. This is usually the result of a program's internal program code incorrectly passing specific data that could not be correctly interpreted by Windows or a Windows-based program.



RESOLUTION
To resolve a GP fault error message under Windows 95, try these troubleshooting steps:

 Restart Windows in Safe Mode so that the operating system uses its default settings, such as VGA monitor, no network, Microsoft mouse driver, and the minimum device drivers.

To restart Windows in Safe Mode, follow these steps:

 Restart your computer by clicking the Start button, clicking Shut Down, and then clicking Restart The Computer. When you see the message "Starting Windows 95," press F5.

After restarting Windows, run Microsoft Access and try to reproduce the GP fault. If you cannot reproduce the problem in safe mode, then the cause is probably a Windows configuration issue. To test for a Windows configuration issue, you can step through the startup process to see if any device drivers or terminate-and-stay- resident programs (TSR) cause problems with Microsoft Access.

To step through the Windows startup process, follow these steps:

 Restart your computer by clicking the Start button, clicking Shut Down, and then clicking Restart The Computer.</li> When you see the message "Starting Windows 95," press F8.</li> Press 5 to select the Step-by-Step Confirmation option.</li>  When you are asked to confirm Startup options, respond as follows:

<pre class="fixed_text">        Option                                             Response ===========================================================

Load DriveSpace Driver? Y        Process the system registry? Y        Create a startup log file (Bootlog.txt)? Y        Process your startup device drivers (Config.sys)? Y        Device= \Himem.sys? Y        Device= \Ifshlp.sys? Y        Device= \Dblbuff.sys? Y        Device= \Setver.exe? Y        Process your startup command file (Autoexec.bat)? Y        Load the Windows graphical user interface? Y        Load all Windows Drivers? Y </li></ol>

NOTE: When processing the startup device drivers (Config.sys) and startup command file (Autoexec.bat), Windows will ask you to confirm each setting. You can choose not to load individual files as a way of finding out which one is causing the configuration problem.

For more information about using Step-by-Step Confirmation when starting Windows 95, please see the following article in the Microsoft Knowledge Base:

136337 Troubleshooting Windows 95 Startup Problems and Error Messages

</li> If you installed a beta version of Windows 95 on your computer and used the same folder for the final retail version, you can try reinstalling Windows 95 to a new, clean folder. This eliminates any problems caused by beta version files which may have remained on your system.</li> If you installed Microsoft Access before you installed Windows 95, try reinstalling Microsoft Access to a new, clean folder.</li> To find out if the GP fault is display-related, you can try changing the way Windows 95 uses your video card.

To change how Windows uses your graphics hardware, follow these steps:

 Click the Start button, point to Settings, and then click Control Panel.</li> Double-click the System icon.</li> Click the Performance tab, and then click the Graphics button in the Advanced Settings section.</li> Move the Hardware Acceleration slider to the None setting (all the way to the left), and then click OK.</li> In the System Properties box, click OK.

For more information about troubleshooting video problems, please see the following article in the Microsoft Knowledge Base:

127139 Troubleshooting Video Problems in Windows 95

</li></ol> </li> You can try installing the Microsoft Access version 2.0 Service Pack, which replaces existing files in your current Microsoft Access version 2.0 installation. The Service Pack includes the following updated files:

<ul> The Microsoft Jet database engine (version 2.5).</li> The OLE dynamic-link libraries (version 2.02).</li> <li>Btrieve, Paradox, and xBASE installable ISAM drivers.</li></ul>

For more information about how to obtain the Microsoft Access version 2.0 Service Pack, please see the following article in the Microsoft Knowledge Base:

122927 WX1124: Microsoft Access Version 2.0 Service Pack

</li> <li>If you are using the Calendar, Scroll Bar, or Data Outline custom control at the time you receive the GP fault, you need to install the Microsoft Access Developer's Toolkit (ADT) Custom Controls Service Pack.

For more information about how to obtain the Microsoft Access Developer's Toolkit (ADT) Custom Controls Service Pack, please see the following article in the Microsoft Knowledge Base:

133341 ACC2: WX1200: Microsoft ADT Custom Controls Service Pack

</li> <li>You can run the Make Compatible utility (Mkcompat.exe), which enables you to specify environment settings for Windows 3.x programs.

To run the Mkcompat.exe file, follow these steps:

<ol style="list-style-type: lower-alpha;"> <li>Click the Start button, and then click Run.</li> <li>In the Open box, type mkcompat, and then click OK.</li> <li>On the File menu, click Choose Program.</li> <li>In the Choose Program box, locate Msaccess.exe.</li> <li>In the Make Compatible box, select options that may affect the operation you were performing when the GP fault occurred. For example, try selecting "Lie about Windows version number" or "Give application more stack space."</li> <li>On the File menu, click Save.</li> <li>On the File menu, click Advanced Options.</li> <li>Again, select options that may affect the operation you were performing when the GP fault occurred.</li> <li>On the File menu, click Save.</li> <li>On the File menu, click Exit.</li></ol> </li></ol>

<div class="references_section">