NO_MORE_SYSTEM_PTES

Code: 0x3f (63)

As HRESULT:

S: 0 (Success)
C: 0 (Microsoft-defined)
N: 0 (Not an NTSTATUS value)
Facility: 0x000 (FACILITY_NULL: Default)
Code: 0x003f (63)

As NTSTATUS:

Sev: 0 (STATUS_SEVERITY_SUCCESS)
C: 0 (Microsoft-defined)
Facility: 0x000 (Default)
Code: 0x003f (63)

Parameters

Parameter	Description
1	0: system expansion PTE type 1: nonpaged pool expansion PTE type
2	Size of memory request
3	Total free system PTEs
4	Total system PTEs

Description

The NO_MORE_SYSTEM_PTES bug check has a value of 0x0000003F. This is the result of a system which has performed too many I/O actions. This has resulted in fragmented system page table entries (PTE).

Important
This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

Cause

In almost all cases, the system is not actually out of PTEs. Rather, a driver has requested a large block of memory, but there is no contiguous block of sufficient size to satisfy this request.

Often video drivers will allocate large amounts of kernel memory that must succeed. Some backup programs do the same.

Resolution

A possible work-around: Modify the registry to increase the total number of system PTEs. If this does not help, remove any recently-installed software, especially backup utilities or disk-intensive applications.

Debugging the problem: The following method can be used to debug bug check 0x3F.

First, get a stack trace, and use the !sysptes 3 extension command.

Then set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\TrackPtes equal to DWORD 1, and reboot. This will cause the system to save stack traces.

This allows you to display more detailed information about the PTE owners. For example:

0: kd> !sysptes 4

0x2c47 System PTEs allocated to mapping locked pages

VA       MDL     PageCount  Caller/CallersCaller
f0e5db48 eb6ceef0        1 ntkrpamp!MmMapLockedPages+0x15/ntkrpamp!IopfCallDriver+0x35
f0c3fe48 eb634bf0        1 netbt!NbtTdiAssociateConnection+0x1f/netbt!DelayedNbtProcessConnect+0x17c
f0db38e8 eb65b880        1 mrxsmb!SmbMmAllocateSessionEntry+0x89/mrxsmb!SmbCepInitializeExchange+0xda
f8312568 eb6df880        1 rdbss!RxCreateFromNetRoot+0x3d7/rdbss!RxCreateFromNetRoot+0x93
f8363908 eb685880        1 mrxsmb!SmbMmAllocateSessionEntry+0x89/mrxsmb!SmbCepInitializeExchange+0xda
f0c54248 eb640880        1 rdbss!RxCreateFromNetRoot+0x3d7/rdbss!RxCreateFromNetRoot+0x93
f0ddf448 eb5f3160        1 mrxsmb!MrxSmbUnalignedDirEntryCopyTail+0x387/mrxsmb!MRxSmbCoreInformation+0x36
f150bc08 eb6367b0        1 mrxsmb!MrxSmbUnalignedDirEntryCopyTail+0x387/mrxsmb!MRxSmbCoreInformation+0x36
f1392308 eb6fba70        1 netbt!NbtTdiOpenAddress+0x1fb/netbt!DelayedNbtProcessConnect+0x17c
eb1bee64 edac5000      200 VIDEOPRT!pVideoPortGetDeviceBase+0x118/VIDEOPRT!VideoPortMapMemory+0x45
f139b5a8 edd4b000       12 rdbss!FsRtlCopyWrite2+0x34/rdbss!RxDriverEntry+0x149
eb41f400 ede92000       20 VIDEOPRT!pVideoPortGetDeviceBase+0x139/VIDEOPRT!VideoPortGetDeviceBase+0x1b
eb41f198 edf2a000       20 NDIS!NdisReadNetworkAddress+0x3a/NDIS!NdisFreeSharedMemory+0x58
eb41f1e4 eb110000       10 VIDEOPRT!pVideoPortGetDeviceBase+0x139/VIDEOPRT!VideoPortGetDeviceBase+0x1b
......

If the system runs out of PTEs again after the TrackPtes registry value has been set, bug check 0xD8 (DRIVER_USED_EXCESSIVE_PTES) will be issued instead of 0x3F. The name of the driver causing this error will be displayed as well.

Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.

Associated Modules

Module	Code	Found in	Description
EventCreate.exe	0x3f	78.11011	%1
KernelBase.dll	0x3f	78.1	Your file waiting to be printed was deleted.
WinMgmtR.dll	0x3f	1011	A provider, %1, has been registered in the Windows Management Instrumentation namespace %2 to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.
cipher.exe	0x3f	78.11011	Key Information: Algorithm: %1 Key Length: %2!d! Key Entropy: %3!d!
dsreg.dll	0x3f	1011	Unable to send WinHTTP request. Error: %1
dssec.dll	0x3f	78.11011	Migrate SID history
ehepgres.dll	0x3f	7	%1
hvloader.dll	0x3f	11	Hypervisor launch failed; The hypervisor was unable to initialize successfully (phase %1), and was not started. This initialization failure may be the result of a platform configuration or firmware issue. Contact your system vendor for more information or updated firmware.
hvservice.sys	0x3f	10	Hypervisor launch failed; The hypervisor was unable to initialize successfully (phase %1), and was not started. This initialization failure may be the result of a platform configuration or firmware issue. Contact your system vendor for more information or updated firmware.
kernel32.dll	0x3f	78.11011	Your file waiting to be printed was deleted.
nslookup.exe	0x3f	78.11011	Success
ntdll.dll	0x3f	78.11011	STATUS_WAIT_63
reagentc.exe	0x3f	11	A recovery test mode run was last completed on: %1!s! %2!s!
webservices.dll	0x3f	78.11011	The same parameter appeared more than once in the content type.
wevtutil.exe	0x3f	78.11011	Uninstall event publishers and logs from manifest. Usage: wevtutil { um \| uninstall-manifest } File path to an event manifest. All publishers and logs defined in the manifest will be uninstalled. To learn more about event manifests and using this option, consult the Windows Eventing SDK on Microsoft Developers Network (MSDN) at http://msdn.microsoft.com. Example: The following example uninstalls publishers and logs from the myManifest.man manifest file. wevtutil um myManifest.man
15 entries