Article ID: 294301 - View products that this article applies to.
This article was previously published under Q294301
Moderate: Requires basic macro, coding, and interoperability skills.
For a Microsoft Access 2003 version of this article, see 825444This article applies to a Microsoft Access database (.mdb) and to a Microsoft Access project (.adp).
This article discusses the causes of fatal system errors in Microsoft Access 2002 when Access 2002 is running on Microsoft Windows 2000. This article first discusses a new error reporting tool in Microsoft Office XP that you can use to report errors that you experience in Access 2002 to Microsoft. Then, this article discusses the types of fatal errors that you may experience in Access 2002. You can use the steps that are discussed in this article to troubleshoot these errors.
Note This is a general article. The Microsoft Knowledge Base may have a specific article that addresses the exact error that you are experiencing. To see if a specific article exists, search the Microsoft Knowledge Base on the exact text of the error message. To search the Microsoft Knowledge Base, visit the following Microsoft Web site:
http://support.microsoft.com/search/?adv=1For more information about how to troubleshoot fatal system errors on Microsoft Windows Millennium Edition, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/284152/ )How to troubleshoot fatal system errors in Access 2002 running on Windows Millennium
New Error Reporting toolMost fatal errors that involve Access 2002 result in the following error message:
When you receive this error message, Access 2002 allows you to collect and send the error information to Microsoft.
Microsoft Access has encountered a problem and needs to close. We are sorry for the inconvenience.
If you were in the middle of something, the information you were working on might be lost.
Please tell Microsoft about this problem.
We have created an error report that you can send to help us improve Microsoft Access. We will treat this report as confidential and anonymous.
To see what data this error report contains, click here.
The error message contains an error signature that records such information as the program name, the error name, and the module name. Microsoft uses this information to further develop and improve Microsoft products.
If you have an Internet connection that is active when you receive this error message, you can send this information directly to Microsoft by using the Office Application Error Reporting tool. If you choose to report this information, the tool verifies whether a solution to the problem is available. If a solution is available, Microsoft sends the solution information back to you.
If you choose not to use the Office Application Error Reporting tool, you can use the information in the error signature to search the Microsoft Knowledge Base directly. For more information about how to use the error reporting dialog box, click the following article number to view the article in the Microsoft Knowledge Base:
289508For more information about end-user reporting and privacy, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/289508/ )How to view error signatures if an Office program experiences a serious error and quits
283768This rest of this article describes how you can determine the exact problem description when you receive this error message. This article also discusses how to troubleshoot the error. Additionally, this article discusses some instances where a fatal error may not result in this message.
Fatal system errorsUsually, a fatal system error, which may be an invalid page fault, a STOP error, a fatal exception error, or an application exception error, will cause a Windows-based application such as Access 2002 to stop responding or to fail. This article focuses on such errors in Windows 2000. In some rare cases, such an error may cause your operating system to stop responding. Overall, there are two basic causes for fatal errors:
Confirmed bug in Access 2002Sometimes, a fatal system error can be caused a bug in an application. When this problem occurs, you may receive an error message that is similar to the following:
You can view details about the error by clicking the text click here. When you do this, you will see information such as what file was involved in the error and the memory offset at which the error occurred.
Microsoft Access has encountered a problem and needs to close. We are sorry for the inconvenience.
You can find more information about any known Microsoft Access problems that may cause fatal system errors by searching on the following words in the Microsoft Knowledge Base:
page faultFor additional information about examining error messages in Windows 2000, click the article numbers below to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/228753/EN-US/ )Troubleshooting 'Stop 0x00000077' or 'KERNEL_STACK_INPAGE_ERROR'
(http://support.microsoft.com/kb/256004/ )How to troubleshoot "STOP 0x0000003F" and "STOP 0x000000D8" error messages in Windows Server 2003, Windows XP, and Windows 2000
137539Note You can paste most Windows 2000 error messages to the Clipboard in a text format by pressing CTRL+C. Pressing CTRL+C converts the error message to text and copies it to the Clipboard. You can then paste the message into another program, such as Notepad. Note that you may not be able to capture all error messages. Also, you may not be able to capture dialog boxes that contain graphics.
(http://support.microsoft.com/kb/137539/ )General causes of STOP 0x0000007F errors
Damaged or fragmented databaseIf the fatal system error occurs only when you open or use a particular database file (*.mdb), try to use the Compact and Repair Database command in Access 2002 to correct any potential problems that have been caused by damage to the database or by excessive fragmentation of the database structure. To do this, follow these steps:
If the database still behaves unpredictably after you run the Compact and Repair Database command, or if you receive a fatal system error, either immediately or after continued use, try the additional troubleshooting steps that are described in this article to find the cause of the page fault.
Corrupted databaseIf the Compact and Repair Database command does not solve unpredictable behavior or application-related fatal system errors, try to create a new database. Import objects from the old database into the new database. Then, compile all the modules in the new database.
Note This method is not recommended if your database is a replica in a replica set. If your replica is corrupted, you should create a new replica from the Design Master.
To create a new database and to import objects from the old database, follow these steps:
If a damaged, fragmented, or corrupted database was the cause of the unpredictable behavior or of the application-related fatal error, you should not see these problems the next time that you run Access 2002 and you open the new database. If you see the same problems in the new database, try the additional troubleshooting steps that are described in this article to determine the cause of the problem.
For more information about how to repair Access 2002 databases, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/283849/ )How to troubleshoot and to repair a damaged Access 2002 or later database
Damaged installationThe problems that you are seeing may be related to the way that Access 2002 is installed on your computer. If you have another computer available that has Access 2002 installed, try your database there. If you suspect that the cause of a fatal system error or of unpredictable behavior in Microsoft Access is related to the application and not to any particular database, the problems may result from such things as incorrect settings in the registry or from one or more missing or corrupted Microsoft Office XP files. To see if this is the case, try to repair your installation. If repairing the installation does not solve the problem, try to remove and then reinstall your installation.
Repair the installation
Remove and then reinstall the installationIf repairing the installation did not solve the problem, try to remove and then reinstall Access 2002 or Office XP.
Note If you have Microsoft Visual Basic with Microsoft SourceSafe installed, you do not have to remove the Visual Basic program. You only have to remove the SourceSafe component.
To remove and then reinstall the installation, follow these steps:
System-related problemsThis section discusses system-related causes for fatal system errors in Windows 2000.
Memory conflictA common cause of fatal system errors is a memory conflict that involves a device driver, a system component, or some other loaded file. To troubleshoot a memory conflict, the first step is to restart the computer in Safe Mode.
Safe Mode bypasses startup files, including the registry, the Config.sys file, the Autoexec.bat file, and the [Boot] and [386Enh] sections of the System.ini file. Additionally, Safe Mode provides you with access to the configuration files. Only essential system files and device drivers, such as the mouse pointing device driver, the keyboard driver, and the standard VGA driver, are loaded. Therefore, Safe Mode is useful for isolating and solving memory conflicts.
To start Windows in Safe Mode, follow these steps:
Temp folder issuesYou can sometimes experience unpredictable behavior in Microsoft Access when you do not have enough disk space for temporary files. You should periodically remove any leftover temporary files on your system. Also, make sure that you have at least 8 to 10 megabytes (MB) of free space on the hard disk that is available to your temporary (Temp) folder. You must first determine the location of your Windows Temp folder as well as verify the validity or your TMP and TEMP environment variables. To do this, follow these steps:
Disk Cleanup utilityIn Windows 2000, you can delete many unused or temporary files with the Disk Cleanup utility. Disk Cleanup searches your hard disk, and then shows you temporary files, Internet cache files, and unnecessary program files that you can safely delete. You can direct Disk Cleanup to delete some or all of those files. To open the utility, click Start, point to Programs, point to Accessories, point to System Tools, and then click Disk Cleanup.
Video problemOccasionally in Microsoft Access, you can experience page faults or unpredictable screen behavior because of a video driver conflict or an incorrect graphics hardware setting for your system.
Video driver conflictTo troubleshoot a video driver conflict, change your system's video adapter to Standard VGA, which should work with most monitors. To do this, follow these steps:
Printer driver problemIf you receive a fatal error or experience printing problems when you try to print in Microsoft Access, try to use the Generic/Text Only driver. To do this, follow these steps:
Incorrect virtual memory settingsYou can occasionally receive unexpected behavior in Microsoft Access when the virtual memory setting is too low for your system. Windows uses a dynamic virtual memory manager to handle swap file duties. You should use the default virtual memory settings whenever possible.
However, if you suspect that the unexpected behavior in Microsoft Access is caused by low virtual memory, you can try to manually change the virtual memory settings. If the maximum setting for virtual memory is already set, you may need to choose a different hard disk or remove files from the current hard disk to increase the amount of disk space reserved for extra memory. To increase the amount of hard disk space reserved for virtual memory, follow these steps:
Hard disk fragmentation or errorsA fatal system error may be the result of disk fragmentation or hard disk errors. If this is the case, try to run one of the following tools to correct the problem.
The Disk Error-Checking toolThis tool checks for file system errors and bad sectors on your hard disk. To run the tool, follow these steps:
The Disk DefragmenterThis tool analyzes your disk to determine the level of defragmentation, and can also defragment it. To use this tool, follow these steps:
For more information about fatal exception errors, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/150314/ )What are fatal exception errors