| Event Id | 1001 |
| Source | Save Dump |
| Description | The computer has rebooted from a bugcheck. The bugcheck was: %1. A dump was saved in: %2. |
| Event Information | Explanation : The system restarted from a bug check. The message contains the details of the bug check. You can use this information to learn more about the bug check. Resolution: Configure Windows to write an event log message with bugcheck information: 1. Click Start, and then click Control Panel. 2. Double-click System, and then click the Advanced tab. 3. In the Startup and Recovery section, click Settings, and then select the Write an event to the system log check box. An event log message is written to the system log. The description and format of the event log differs from the Memory.dmp file format, but most of the information is the same. This message from newsgroup may help you: -------------------------------------------------------------------------------- "In some cases, windows will report incorrect memory information. Remove one of the modules and try if the problem still happening, remove the module and try with the second Memory Module." "Make sure the memories used are in QVL list of the motherboard and check for updated device drivers. Update the OS with latest patches and updates." "Try the diagnosing utility form the link "Memtest86 - A Stand-alone Memory Diagnostic". Even this utility may report no errors, you have to confirm memory dump error by inserting one of the modules one at a time and check system still having the problem of stop error". --------------------------------------------------------------------------------. |
| Reference Links | Gathering
Blue Screen Information After Memory Dump in Windows 2000 or Windows NT Poor Program and Service Performance During Crash Dump Transfer How to gather information after a memory dump in Windows XP Your Windows Server 2003-based terminal server that uses the UPHClean utility to unload user profiles when users log off may suddenly stop responding How to Enable a Memory.dmp File Capture Using the Graphical User Interface or the Registry "Stop 0x00000054" Error Message in Windows 2000 "STOP 0x000000D1" When Passing Fragmented Packets Without NAT Windows 2000 Auditing and Intrusion Detection Memtest86 - A Stand-alone Memory Diagnostic WINDOWS STOP MESSAGES |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.