No More System PTEs BSOD Fix Windows 11: Steps to Try
No More System PTEs is the blue-screen bug check with value 0x0000003F. It usually indicates that the system has performed too many I/O actions, resulting in fragmented system page table entries (PTE), and in almost all cases the machine is not actually out of PTEs. Start by checking the last change, then move through driver and debugger-based checks before replacing hardware. Ignore it, and the PC can fall into a crash loop or hide a failing part until data is lost. This guide walks through the fastest checks in the order most likely to isolate the fault and get Windows booting normally again.
This guide is part of our Windows BSOD stop codes: full list and fixes series.
What No More System PTEs means in Windows 11
Windows stops with a blue screen when it hits a fatal system error, then shuts the system down to avoid more damage. Windows 10 and 11 usually show a stop code in text or hexadecimal, and the screen may also include a QR code you can scan. This bug check is typically caused by a driver requesting a large block of memory when there is no contiguous block of sufficient size to satisfy it. Often video drivers allocate large amounts of kernel memory that must succeed, and some backup programs do the same.
What to write down from the blue screen before rebooting
Note the exact stop code, any driver name, whether a QR code appears, and whether the PC reboots once or loops. That small record often decides whether the next step is Safe Mode, driver rollback, or memory testing.
When a QR code or driver name matters
A named driver on the crash screen is a strong clue. A QR code usually points back to Microsoft help pages, but the useful part is still the stop text and any driver shown beside it.
According to How to Fix Windows Blue Screen of Death (BSOD)? — Windows 10 and 11 BSODs show a specific stop code in text or hexadecimal.
What should I do first after a No More System PTEs blue screen?
First, stop changing settings at random and check whether the crash followed a driver, update, or new device. If the desktop still loads, save the stop code and minidump path before making repairs. If Windows keeps rebooting, go straight to Advanced startup and Safe Mode, because that separates startup-driver faults from deeper system trouble much faster.
Quick triage checklist
- Write down the stop code and any driver name shown on the blue screen.
- Open
C:\Windows\Minidump\and note the newest file name if Windows still opens. - Check Event Viewer > Windows Logs > System for repeated bug check or driver errors.
- If the PC loops, go to Settings > System > Recovery > Advanced startup > Restart now.
| Observed symptom | What it usually suggests | Next move |
|---|---|---|
| One crash, then normal boot | Recent driver or update | Check minidumps and Device Manager |
| Crash loop before desktop | Startup driver, service, or memory fault | Boot Safe Mode |
| Blue screen under gaming or load | Driver or large kernel-memory request | Test drivers first |
| Stop code after update or install | Corrupt driver or system file | Rollback, then run SFC |
Likely causes, ranked by how often they show up
Most often, No More System PTEs comes from a driver that asks for a large block of kernel memory and cannot get a contiguous block large enough to satisfy the request. Video drivers are a common trigger, and some backup programs can also cause it. The problem is usually fragmentation of system PTEs after too many I/O actions, rather than a literal shortage of PTEs.
Buggy graphics, storage, or chipset drivers
Video drivers are a frequent suspect because they can ask for large blocks of kernel memory that must succeed. Storage and chipset drivers matter too, especially if the crash began after a driver update, new GPU install, docking station change, or BIOS update.
RAM instability or a bad stick
If the system fails under load, crashes at random, or changes behavior after moving DIMMs, memory can still be a factor in the broader crash pattern. Test one stick at a time so you can isolate a bad module if memory errors appear.
Paging or memory-pressure problems
A misconfigured pagefile can add stress, but the main issue for this bug check is still fragmented system PTEs and a request that cannot fit contiguously. Check the pagefile if the crash happens during heavy I/O, large transfers, or backups.
Corrupted Windows files or a damaged system image
If the same stop code returns after driver work and memory checks pass, repair the Windows image next. SFC and DISM are the right pair when the operating system itself may be damaged.
