Savedump Does Not Write Event Log Message with Event ID 1000

ID: Q235999

The information in this article applies to:

Microsoft Windows NT Server version 4.0 SP5
Microsoft Windows NT Workstation version 4.0 SP5

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.

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.

RESOLUTION

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/windows/servicepacks/

Q152734 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://www.microsoft.com/support/supportnet/overview/overview.asp

STATUS

Microsoft has confirmed this to be a problem in Windows NT 4.0. This problem was first corrected in Windows NT 4.0 Service Pack 6.

Additional query words: Bluescreen

Keywords : kbbug4.00 kbfix4.00 NT4SP6Fix
Version : winnt:4.0 SP5
Platform : winnt
Issue type : kbbug