Savedump Does Not Write Event Log Message with Event ID 1000

View products that this article applies to.

This article was previously published under Q235999

SYMPTOMS

When there is not enough free disk space to write a dump file, Savedump.exe does not write the following entry to the event log:

Event ID: 1000
Source: Save Dump
Description:
The computer has rebooted from a bugcheck.
The bugcheck was: 0xdeaddead (0x00000000, 0x00000000, 0x00000000, 0x00000000).
Microsoft Windows NT [v15.1381].
A full dump was not saved.

Back to the top

CAUSE

This behavior occurs because remote procedure call (RPC) returns an unanticipated error message when Savedump.exe attempts to get a handle to the registry (RegisterEventSource).

RPC returns RPC_S_UNKNOWN_IF (The interface is unknown. Error code 1717), but Savedump.exe checks only for a return code of RPC_S_SERVER_UNAVAILABLE (The RPC server is unavailable. Error code 1722). The return error code 1717 is ignored.

Back to the top

RESOLUTION

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

http://www.microsoft.com/downloads/details.aspx?familyid=E396D059-E402-46EF-B095-A74399E25737&displaylang=en/ (http://www.microsoft.com/Windows/ServicePacks/) -or-
152734 (http://support.microsoft.com/kb/152734/EN-US/ ) how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS (http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)

Back to the top

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

http://www.microsoft.com/downloads/details.aspx?familyid=E396D059-E402-46EF-B095-A74399E25737&displaylang=en/ (http://www.microsoft.com/Windows/ServicePacks/) -or-
152734 (http://support.microsoft.com/kb/152734/EN-US/ ) how to obtain the latest windows nt 4.0 service pack

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS (http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)

Back to the top

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 (http://support.microsoft.com/kb/152734/EN-US/ ) How to Obtain the Latest Windows NT 4.0 Service Pack

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 Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.

Back to the top