This article provides information on configuring Windows Server to generate a dump file in the event of a blue-screen (bugcheck). Dump files are often very useful when troubleshooting blue-screen/bugcheck events on Windows servers.The procedure for configuring a server to generate a dump file varies slightly among versions of Windows Server.
A kernel memory dump is typically the most useful type of dump file. Small memory dumps (minidumps) have the advantage of being very small, but they often contain insufficient data to pinpoint the cause of a bugcheck. Complete memory dumps, on the other hand, contain a lot of data but can be extremely large. A kernel dump represents a good balance between the two.
The Startup and Recovery Options window in Windows Server 2003 is shown below (Figure 1: (English Only)):
Figure 1: Startup and Recovery Options window in Windows Server 2003
There is a new option in the dropdown list in Server 2012: Automatic memory dump.
This option generates a kernel dump but allows for a smaller system-managed pagefile than if Kernel memory dump is selected in the dropdown list.
More information about the Automatic memory dump option is given in a TechNet blog entry titled Windows 8 and Windows Server 2012: Automatic Memory Dump.
Now that the server is configured to generate a dump file, it will do so the next time a bugcheck event (blue-screen) occurs. Tools such as WinDbg can be used to analyze the dump file in order to determine the cause of the bugcheck.
For basic instructions for using WinDbg, see Basic Windows Blue-Screen Troubleshooting with WinDbg .
Need more help? | |
![]() |
Find additional PowerEdge and PowerVault articles |
![]() |
Visit and ask for support in our Communities |
![]() |
Create an online support Request |
Identificación del artículo: SLN163973
Última fecha de modificación: 09/27/2016 10:30 AM
Muchas gracias por sus comentarios.