AbstractProcess virtual address spaceWhat you need to know about an application's virtual address spaceIdentifying applications that run out of virtual address spaceHow to determine the maximum virtual address space for an applicationIdentifying application virtual address space problems using performance monitor and the application event logIdentifying application virtual address space problems using the PAL toolInvestigating application virtual address space problems using VMMapAbout debugdiagPreparing for a call with microsoft supportDealing with 32-bit applications that run out of virtual address spaceIdentifying and adding large address awareThe concept and advantages of virtual memory32-bit (× 86) virtual address space64-bit (× 64) virtual address spaceMany processes, one kernelHow can each application have a private 8 TB on a system with 4 GB of physical memory?Virtual memory and paging filesReserved, committed, and free memoryIdentifying application out of virtual address space conditionsRead this if you are considering /3GB or IncreaseUserVaIdentifying processes leaking system committed memoryTroubleshooting processes leaking system committed memory using Sysinternals VMMapTroubleshooting processes leaking system committed memory using debug dumpsTreating the symptoms of process committed memory leaksConclusion