STOP 0XA Caused by Race Condition in VDM and Process Delete

This article was previously published under Q178471
This article has been archived. It is offered "as is" and will no longer be updated.
When running 16-bit programs that require the Virtual DOS Machine (VDM).the following STOP error may occur:

Stop 0x0000000A (0x00000084, 0x00000002, 0x00000001, 0x80003D4A)

This problem is most likely to occur on systems with more than oneprocessor.
A race condition exists between process delete and delayed virtualinterrupt processing. This causes a NULL parameter to be passed to theHardware Abstraction Layer (HAL) acquire spin lock routine.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

Apply Ntoskrnl.exe if the target computer has only one processor.

Apply Ntoskrnlmp.exe if the target computer is a multiprocessor system.

NOTE: After copying Ntkrnlmp.exe to the target computer, rename it toNtoskrnl.exe.
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
4.00 patch prodnt multi uni uniprocessor

Article ID: 178471 - Last Review: 10/07/2013 16:19:54 - Revision: 2.2

Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbqfe KB178471