JSI Tip 4908. How do I troubleshoot Windows 2000 STOP 0x0000003F or STOP 0x000000D8 errors?

This tip will help your troubleshoot either of the following BSODs:

STOP: 0x0000003F (0xA,0xB,0xC,0xD) NO_MORE_SYSTEM_PTES

STOP: 0x000000D8 (0xW,0xX,0xY,0xZ) DRIVER_USED_EXCESSIVE_PTES

NO_MORE_SYSTEM_PTES

This is generally the result of a driver that is not cleaning up after itself. The (0xA,0xB,0xC,0xD) parameters will vary from computer to computer, but have the following meaning:

0xA - Page Table Entry (PTE) type: 0=system expansion, 1=non-paged pool expansion.

0xB - Requested size.

0xC - Total free system PTEs.

0xD - Total system PTEs.

To find the misbehaving driver:

1. Use Regedt32 to navigate to:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession ManagerMemory Management.

2. Edit or Add Value name TrackPtes, a REG_DWORD data type, and set the data value to 1.

NOTE: This registry value will cause the system to save stack traces, so you can identify the driver.

DRIVER_USED_EXCESSIVE_PTES

This is generally the result of running out of PTEs. The (0xW,0xX,0xY,0xZ) parameters will vary from computer to computer, but have the following meaning:

0xW - If not null, it contains the name of the driver, possibly in unicode.

0xX - If not null, it contains the number of PTEs used by the driver.

0xY - Total free system PTEs.

0xZ - Total system PTEs.

Either replace the driver or increase the number of PTEs. See Microsoft Knowledge Base article Q247904 - How to Configure the Paged Address Pool and System PTE Memory.