Microsoft KB Archive/162926

From BetaArchive Wiki
Knowledge Base


STOP: 0x0x0000000A After Call to GlobalAddAtom()

Article ID: 162926

Article Last Modified on 11/1/2006



APPLIES TO

  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 4.0 Standard Edition



This article was previously published under Q162926

SYMPTOMS

When you write applications for Windows NT version 4.0 that make Win32 calls to GlobalAddAtom(), Windows NT may trap with a STOP: 0x0000000A error message after a call to GlobalAddAtom(), when adding a string longer than 256 bytes. The error may not occur until a call to ExitProcess() is made.

CAUSE

An uninitialized variable may cause this Stop message.


RESOLUTION

Apply the hotfix to the Windows NT 4.0 Workstation or Server that the Stop message occurs on.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. This problem was corrected in the latest Microsoft Windows NT 4.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K



Additional query words: prodnt 0xa ntoskrnl

Keywords: kbnetwork KB162926