The Explorer.exe process may unexpectedly quit when you try to search for a file in Windows XP or in Windows Server 2003

On a computer that is running Microsoft Windows XP or Microsoft Windows Server 2003, the Explorer.exe process may unexpectedly quit when you try to search for a file. Before this problem occurs, you may experience the following symptoms:

1. The task bar of Windows desktop disappears for a moment.
2. Desktop is redrawn.
3. The title bar of Windows Explorer appears again.

After you restart the computer, you may receive the following error message: In Windows XP, the following error-signature information is displayed when you view the data that the error report contains.In Windows Server 2003, the following error-signature information is displayed when you view the data that the error report contains.

This problem occurs because the Rkadmin.dll file is copied to the System32 folder when you install the Microsoft Windows 2000 Resource Kit. The Rkadmin.dll file may cause an access violation after you run a file search operation several times.

To work around this problem, uninstall the Microsoft Windows 2000 Resource Kit.

The Windows Error Reporting dialog box appears when an error causes a fatal event in the program. This dialog box includes a button that lets you send information about the fatal event to Microsoft. Microsoft gathers information about these types of events in a database to try to identify the cause of the problem.If you disable error reporting, you do not receive notification when a fatal event occurs. However, the following files may be created, depending upon the system configuration:

• Drwtsn32.log
• User.dmp

For more information about how to disable error reporting, click the following article numbers to view the articles in the Microsoft Knowledge Base: For more information about the Drwtsn32.log file and about the User.dmp file, click the following article number to view the article in the Microsoft Knowledge Base: When this problem occurs in Windows XP, the following information appears in the Application log:

Date: Date
Time: Time
Type: Error
User: N/A
Computer: Computer name
Source: Application Error
Category: None
Event ID: 1000
Description: Faulting application explorer.exe, version 6.0.2900.2180, faulting module rkadmin.dll, version 1.0.0.10, fault address 0x0000d8d9.

Date: Date
Time: Time
Type: Error
User: N/A
Computer: Computer name
Source: Application Error
Category: None
Event ID: 1001
Description: Fault bucket 129792005.

When this problem occurs in Windows Server 2003, the following information appears in the Application log:

Date: Date
Time: Time
Type: Error
User: N/A
Computer: Computer name
Source: Application Error
Category: None
Event ID: 1000
Description: Faulting application explorer.exe, version 6.0.3790.1830, faulting module rkadmin.dll, version 1.0.0.10, fault address 0x0000d8d9.

Date: Date
Time: Time
Type: Error
User: N/A
Computer: Computer name
Source: Application Error
Category: None
Event ID: 1001
Description: Fault bucket 192723101.

Notes

• IT administrators can use the Corporate Error Reporting (CER) tool to manage error reports and error messages that are created by an error-reporting client. Error-reporting clients include the Windows Error Reporting client in Microsoft Windows XP and in Microsoft Windows Server 2003. If an error-reporting client is configured to work with CER 2.0, error reports are redirected to a CER shared folder. The error reports are not sent to Microsoft. For more information, visit the following Microsoft Web site:
  http://download.microsoft.com/download/5/9/2/592d2308-a6a2-48ad-ae8f-72f888b9d361/CER_Implementation_Plan.pdf (http://download.microsoft.com/download/5/9/2/592d2308-a6a2-48ad-ae8f-72f888b9d361/cer_implementation_plan.pdf)
• If you are using the CER tool, you do not see Event ID 1001.

For more information about event ID 1000 and about event ID 1001, visit the following Microsoft Web site: