Knowledge Base

Windows Server 2003 systems using IPsec tunnel-mode functionality may experience problems after you install the original version of 893066

Article ID: 898542

Article Last Modified on 9/20/2006

APPLIES TO

Microsoft Windows Server 2003, Web Edition
Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems

SYMPTOMS

After you install the original RTMQFE version of security update 893066 on a Microsoft Windows Server 2003-based computer that is running a firewall product that uses Internet Protocol security (IPsec) tunnel mode functionality, you may experience one or more of the following symptoms.

Note An example of of a firewall product that uses IPsec tunnel mode functionality is Microsoft Internet Security and Acceleration Server.

Your computer automatically restarts.
After you log on, you receive the following error message:

Microsoft Windows
The system has recovered from a serious error.
A log of this error has been created.
Please tell Microsoft about this problem.
We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous.
To see what data this error report contains, click here .

If you click the click here link at the bottom of this error message dialog box, error signature information that is similar to the follow is displayed:
```
BCCode : 0000008E BCP1 : c0000005 BCP2 : ba9be697 BCP3 : ba077a1c 
BCP4 : 00000000 OSVer : 5_2_3718 SP : 0_0 Product : 272_3
```
Note The four BCP# parameters that are included in this error signature information may vary according to the configuration of the computer.
You receive the following stop error message on a blue screen:
A problem has been detected and Windows has been shut down to prevent damage to your computer...
Technical information:
- - - STOP: 0x0000008E (0xc0000005, 0xba9be697, 0xba077a1c, 0x00000000)
KERNEL_MODE_EXCEPTION_NOT_HANDLED
Note The four parameters that are included inside the parentheses of the technical information for this stop error may vary according to the configuration of the computer.
When you view the System log in Event Viewer, you notice an entry for event ID 1003 that is similar to the following:

Date: date
Source: System
Error Time: time
Category: (102)
Type: Error
Event ID: 1003
User: N/A
Computer: COMPUTER
Description: Error code 0000008E, parameter1 c0000005, parameter2 ba9be697, parameter3 ba077a1c, parameter4 00000000. For more information, see Help and Support Center at http://support.microsoft.com. Data: 0000: 53 79 73 74 65 6d 20 45 System E 0008: 72 72 6f 72 20 20 45 72 rror Er 0010: 72 6f 72 20 63 6f 64 65 ror code 0018: 20 30 30 30 30 30 30 35 000008E 0020: 30 20 20 50 61 72 61 6d 0 Param 0028: 65 74 65 72 73 20 66 66 eters ff 0030: 66 66 66 66 64 31 2c

Notes

The symptoms of a stop error vary according to the system failure options of the computer. For more information about how to configure system failure options, click the following article number to view the article in the Microsoft Knowledge Base:

307973 How to configure system failure and recovery options in Windows
Not all "Stop 0x0000008E" errors are caused by the problem that is described in this article.
This problem will not occur if you have installed the version of security update 893066v2 that was re-released on June 14, 2005. Install the security update 893066v2 on all computers. If you do not have this security update installed on all computers, we recommend that you install the broadly-available security update 893066v2 instead of this hotfix.

CAUSE

This problem is caused by a kernel-mode exception in the Tcpip.sys file that can occur in scenarios that use IPsec tunnel mode.

RESOLUTION

Security update information

Security update 893066 has been updated to correct this issue. Security update 893066 was released in security bulletin MS05-19. For more information, visit the following Microsoft Web site:

http://www.microsoft.com/technet/security/bulletin/ms05-019.mspx

Prerequisites

No prerequisites are required to install this hotfix.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Windows Server 2003, 64-bit Itanium-based versions

    Date         Time   Version       Size     File name
   ----------------------------------------------------
   25-May-2005  19:10  5.2.3790.336  977,920  Tcpip.sys

Windows Server 2003, 32-bit versions

   Date         Time   Version       Size     File name
   ----------------------------------------------------
   25-May-2005  19:21  5.2.3790.336  336,896  Tcpip.sys

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was corrected in Windows Server 2003 Service Pack 1.

MORE INFORMATION

This problem may occur as a spontaneous restarting with system, so this behavior is not configured to capture a crash dump. Event logs may not show crash parameters. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional query words: bugcheck bug check crash kernel bluescreen 0x0000008E

Keywords: kberrmsg kbfix kbqfe kbwinserv2003presp1fix kbocabucket kbhotfixserver KB898542

Microsoft KB Archive/898542

Contents