Microsoft KB Archive/924439

= Error message on a computer that has a large L3 cache and that is running Windows Server 2003 or Windows 2000: &quot;STOP 0x0000001E&quot; or &quot;STOP 0x0000008E&quot; =

Article ID: 924439

Article Last Modified on 10/29/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows 2000 Professional Edition
 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Datacenter Server

-



SYMPTOMS
On a Microsoft Windows Server 2003-based computer, you receive an error message that resembles the following:

STOP 0x0000008E

KERNEL_MODE_EXCEPTION_NOT_HANDLED

On a Microsoft Windows 2000-based computer, you receive an error message that resembles the following:

STOP 0x0000001E

KERNEL_MODE_EXCEPTION_NOT_HANDLED

This problem occurs if the computer uses a very fast processor, and the computer has a large L3 cache.



CAUSE
This problem occurs because of a hard-coded breakpoint in the Afd.sys process. This breakpoint occurs because the processor continues to run code before an asynchronous procedure call (APC) occurs. This timing problem occurs only on very fast processors when they are used together with earlier operating systems.

Note The APC is queued in the Afd.sys process.

After the APC is queued, a series of commands are run. These commands include a check to determine the following:
 * Whether the event in the IO Request Packet (IRP) is signaled
 * Whether the return from the IoCallDriver routine was &quot;non-error&quot;

If the event is not signaled, and if the IoCallDriver routine returns a &quot;non-error&quot; status, a code section is implemented that calls the DbgBreakPoint routine. The DbgBreakPoint routine is implemented when either the event or the IoCallDriver routine behaves incorrectly. When the DbgBreakPoint routine is called in this area of code, this resembles a situation in which the BugCheck routine is called. In both situations, the code should not continue to run past the point that is specified in the instructions if the assumption of incorrect behavior is true.

A stack trace of the failure shows that the event is signaled at the time that the DbgBreakPoint routine occurs. However, the DbgBreakPoint routine occurs because the event was not signaled at the time of the check.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



Windows Server 2003
This problem was fixed in Windows Server 2003 Service Pack 1 (SP1). For more information about how to obtain the latest service pack for Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003

Additional query words: AfdIssueDeviceControl bugcheck bug check race condition stop bluescreen blue screen

Keywords: kbqfe kbbug kberrmsg kbexpertiseinter KB924439

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.