Article ID: 2927158 - View products that this article applies to.
Consider the following scenario:
Hyper-V implements the Dynamic Memory by using HotAdd Memory. The Operating System has to set aside memory structures to manage the possible addition of this Memory. If you also increase PagedPoolSize, this structure may use too much space and collide.
You have configured Memory Manager Settings inside the Windows Server 2003 VM according to http://support.microsoft.com/kb/935649
Limit DynamicMemory inside your Windows Server 2003 VM to at least 63 GB. See also http://support.microsoft.com/kb/913568
Actually you can limit it to the Maximum RAM you configured for your VM. However, you need to adjust this in case you increase the Maximum RAM for the VM at a later time.
Windows Server 2003 SP1 Standard Edition supports a Maximum of 4GB physical memory, so a DynamicMemory value of 4 is sufficient.
Windows Server 2003 SP1 Enterprise and Datacenter Edition support a maximum of 64GB physical Memory. To avoid this problem you should configure the DynamicMemory value to 63 or less. If you configure it to the Maximum RAM you intend to run, you gain the benefit of freeing up more System PTE's
You may also see Stop code DRIVER_CORRUPTED_SYSPTES (db) inside the VM. The same Resolution applies here.
Article ID: 2927158 - Last Review: February 11, 2014 - Revision: 1.0