Article ID: 10055, created on Mar 10, 2011, last review on Aug 1, 2016

  • Applies to:
  • Virtuozzo containers for Windows

Table of contents:

Memory dump configuration:

Users are strongly encouraged to configure memory dump generation properly to facilitate the troubleshooting of crashes (BSoDs) on Parallels Virtuozzo Containers for Windows servers.


  • Paging file must be at least 1 x RAM size plus 257 MB.
  • The configured partition to store the dump should have enough space (the amount of RAM on the server must be as large as the size of the dump).
  • Full/Complete memory dump must be enabled.

Once requirements are met, move on to the dump configuration:

  1. Enable complete crash dump generation:

    C:\>reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v CrashDumpEnabled /t REG_DWORD /d 1 /f
  2. (For Windows 2008 and Windows 2008 R2 only) If the system drive (C:) does not have enough disk space to store the dump file, it is possible to store the file on another drive. The following command will configure the memory dump to be stored on drive D:

    C:\>reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v Dumpfile /t REG_EXPAND_SZ /d "D:\MEMORY.DMP" /f

More details can be found in the following Microsoft articles:

Limiting available RAM for Hardware Node

Sometimes hardware node has far more RAM than it needs, and it might cause difficulties during memory dump generation - e.g. diskspace shortage. For this occasions it's possible to limit amount of RAM available on the host using following instructions:

  • Windows Server 2003 only:

    1. Set RAM limit:

      C:\>bootcfg /addsw /MM <RamInMb> /ID 1

      Where <RamInMb> should be replaced with amount of RAM in Mb you want to use

    2. Reboot the host
  • Windows Server 2008 and newer:

    In Windows Server 2008 and newer concept is different from Windows Server 2003 - instead of limiting RAM we set amount of RAM to be disabled.

    1. Remove extra memory

      C:\>bcdedit /set {current} removememory 1536

      Command above disables 1.5 Gb of ram out of total X Gb of RAM. If you have 160 Gb and want to use only 20 Gb - you have to remove 140*1024 Mb.

    2. Reboot the host

More details can be found in the following Microsoft article:

Testing configuration

In order to test configuration it's necessary to trigger a system crash and check whether dump was collected successfully or not. In order to enable keyboard shortcuts for system crash following settings should be applied:

  • USB keyboard:

    C:\>reg add "HKLM\System\CurrentControlSet\Services\kbdhid\Parameters" /v CrashOnCtrlScroll /t REG_DWORD /d 1 /f
  • PS/2 keyboard:

    C:\>reg add "HKLM\System\CurrentControlSet\Services\i8042prt\Parameters" /v CrashOnCtrlScroll /t REG_DWORD /d 1 /f

System should be restarted for these settings to take effect.

After the restart, the keyboard crash can be initiated by holding the right CTRL key and pressing the SCROLL LOCK key twice.

Validating dump

It is a good idea to validate memory dump before sending it to support. Here is how to do so:

- Download and install Windows Debugging Tools ([x64]( or [x86](

- Run this command:

    "C:\Program Files\Debugging Tools for Windows (x86)\dumpchk.exe"  <dumpfile>

    If you see one or more of the following strings in the output, the dump is bad.

    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    KdDebuggerDataBlock is not present or unreadable.
    Unable to read PsLoadedModuleList
    Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Search Words


bsod virtuozzo

blue screen of death

Virtuozzo vznetif container stop

vzcore.sys blue screen


node crashes


memory dump

rebooted unexpectedly


d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223 965b49118115a610e93635d21c5694a8

Email subscription for changes to this article
Save as PDF