Event ID 54 When You Stop Debugging a Program That Uses DirectX API

Article translations Article translations
Article ID: 290312 - View products that this article applies to.
This article was previously published under Q290312
Expand all | Collapse all

SYMPTOMS

When you stop debugging a program that uses the DirectX Application Programming Interface (API) in Developer Studio, the program may seem to stop responding (hang) for several minutes. During this time, you cannot end the program task in Task Manager, nor can you start a new instance of the program.

After several minutes, Event Viewer records multiple instances of the following message:
The description for Event ID ( 54 ) in Source ( wdmaud ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer.

CAUSE

This behavior occurs because the Windows Driver Model (WDM) audio driver (Wdmaud.sys) does not provide an I/O Request Packet (IRP) cancellation routine.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This problem was first corrected in Windows 2000 Service Pack 2.




Properties

Article ID: 290312 - Last Review: January 31, 2007 - Revision: 3.2
APPLIES TO
  • Microsoft Windows 2000 Service Pack 1
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Service Pack 1
Keywords: 
kbbug kbfix kbwin2000presp2fix kbenv kbprogramming KB290312

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com