SYSTEM_PTE_MISUSE blue screen in Windows: causes and fixes

Applies to: Windows 11 and Windows 10, on desktops and laptops.

What SYSTEM_PTE_MISUSE means

Windows keeps page table entries (PTEs) that tell the processor where each piece of memory lives. Microsoft’s documentation describes bug check 0xDA as a PTE routine being used in an improper way. In plain terms, something running at the lowest level of Windows, usually a driver, handled that memory incorrectly, so Windows stopped to protect your data.

The blue screen itself rarely names the culprit. In practice, people run into it in two different situations, and the fix depends on which one you have.

Which fix to start with

When it happens	Most likely cause	Start with
While installing Windows, or at every boot	Firmware: the BIOS version or the TPM / Intel PTT security chip setting	Fix 1, then Fix 2
Right after a BIOS update or BIOS setting change	A firmware setting that changed	Fix 2
Randomly while using Windows, gaming or waking from sleep	A driver, often the graphics driver	Fix 3, then Fix 4
After a Windows update or new software	A new driver or damaged system files	Fix 3 and Fix 5

If Windows won’t start: use Safe Mode

If the PC crashes before you can sign in, let it fail to start two or three times, or hold Shift while selecting Restart on the sign-in screen. In the blue recovery menu, go to Troubleshoot > Advanced options > Startup Settings, select Restart, then press 4 for Safe Mode or 5 for Safe Mode with Networking.

Safe Mode loads only basic drivers, so it often starts even when a faulty driver crashes normal Windows. Our guide to “Your PC couldn’t start properly” covers the recovery menu in more detail.

Fix 1: Update the BIOS or UEFI firmware

When SYSTEM_PTE_MISUSE appears during Windows setup or on every boot, outdated firmware is a frequent cause, especially on laptops. Firmware updates often fix how the security chip and memory are set up before Windows loads.

1. Find your exact model on the sticker under the laptop or in Settings > System > About.
2. Open the support page for that model on the PC or motherboard maker’s website (Dell, HP, Lenovo, ASUS, Acer, MSI and so on).
3. Download the latest BIOS or UEFI update for your model only, and follow the maker’s instructions.
4. Plug a laptop into power and don’t turn the PC off while the update runs.

Many makers also offer an update app (such as Dell SupportAssist, HP Support Assistant or Lenovo Vantage) that installs firmware updates from inside Windows. If BitLocker is on, the maker’s tool may suspend it for you; if not, suspend it first (see Fix 2).

Fix 2: Check the TPM and PTT settings

Several reports tie this error, especially during a Windows installation, to the firmware TPM security chip. On Intel PCs the firmware TPM is called PTT (Platform Trust Technology); other names include TPM Embedded Security or Security Chip. Turning it off temporarily is a test, not a long-term fix, so read the warnings first.

Before you change anything:

• If BitLocker or Device Encryption is on, suspend BitLocker first and make sure you have the recovery key. Changing TPM settings can otherwise ask for the key at the next start; see how to find a BitLocker recovery key.
• Windows 11 needs TPM 2.0. Turning it off can affect BitLocker, Windows Hello sign-in and some security features, so turn it back on once you’re done testing.

To test the setting:

1. Open the firmware settings: go to Settings > System > Recovery, select Restart now next to Advanced startup, then choose Troubleshoot > Advanced options > UEFI Firmware Settings. You can also press the setup key at power-on (often F2, F10, Del or Esc).
2. Look on the Security tab (sometimes Advanced) for the TPM, PTT or Security Chip option.
3. First try the option to reset or clear the TPM to defaults if there is one. Clearing it deletes keys stored in the chip, which is why BitLocker must be suspended first.
4. If the error continues, set the TPM or PTT option to Disabled (or Hidden), save and exit, and test again.
5. If that stops the crash, update the BIOS (Fix 1), then turn the TPM or PTT option back on and check that the error doesn’t return.

Option names and locations vary a lot between makers. If you can’t find them, the support page for your model usually lists them.

Fix 3: Update or roll back drivers

When the crash happens randomly in a working Windows, a driver is the most likely cause, and the graphics driver is a common one. Start with what changed most recently.

1. Right-click Start and open Device Manager.
2. Expand Display adapters (and any other device you updated recently), right-click the device and choose Properties.
3. On the Driver tab, select Roll Back Driver if the crashes started after a driver update. Otherwise, install the latest driver from NVIDIA, AMD, Intel or your PC maker.
4. Restart and use the PC normally to see if the crash returns.

Also check Settings > Windows Update > Advanced options > Optional updates for driver updates, and remove recently installed software that adds its own drivers, such as VPN, antivirus, RGB lighting or fan control tools, to test whether one of them is the cause.

Fix 4: Find the driver in the crash dump

If the crashes keep coming, the crash dump can tell you which driver was involved. Windows usually saves small dump files in C:\Windows\Minidump (and a larger one at C:\Windows\MEMORY.DMP).

1. Install WinDbg from the Microsoft Store.
2. Run it as administrator, choose File > Open dump file and open the newest file in C:\Windows\Minidump.
3. Type !analyze -v in the command box and press Enter.
4. Look for MODULE_NAME or IMAGE_NAME near the end. A file such as nvlddmkm.sys (NVIDIA graphics) points to that driver; search the file name to find which product it belongs to.

If the result names only a Windows file such as ntoskrnl.exe, the real cause is still usually a driver or hardware problem, and Fixes 3 and 5 are the next steps.

Fix 5: Repair Windows files and undo recent changes

Open Terminal (Admin) or Command Prompt as administrator and run these two commands, one at a time:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Restart when both finish. If the crashes began after a Windows update, uninstall it from Settings > Windows Update > Update history > Uninstall updates. If they began after other changes, use System Restore: press Windows + R, type rstrui and pick a restore point from before the problem.

If none of this helps and the error appears even during a fresh Windows installation with up-to-date firmware, contact the PC maker; a hardware or firmware fault is then more likely than a Windows problem.

Related guides

• Your PC couldn’t start properly: how to fix it
• BitLocker suspended: what it means and how to resume it
• How to find your BitLocker recovery key
• New CPU installed, fTPM NV corrupted: what to choose

Official sources: for more detail, see these Microsoft pages:

• Microsoft Learn: Bug Check 0xDA SYSTEM_PTE_MISUSE
• Microsoft Support: Troubleshooting Windows unexpected restarts and stop code errors

Frequently asked questions

Is SYSTEM_PTE_MISUSE a hardware failure?

Usually not. It’s most often a driver or firmware problem. Hardware becomes more likely if the error continues after a BIOS update, a clean Windows installation and current drivers.

Is it safe to leave TPM or PTT turned off?

Only for testing. Windows 11 expects TPM 2.0, and BitLocker and Windows Hello rely on it. Use the test to confirm the cause, then update the firmware and turn it back on.

Why does it happen only when installing Windows?

During setup, Windows works with the firmware and security chip before any updated drivers are installed. An old BIOS or an unusual TPM setting can cause the crash at that stage, which is why Fixes 1 and 2 come first.

Will reinstalling Windows fix it?

It can if the cause is a damaged driver or system files, but not if the cause is firmware. Try the fixes above first, and keep a backup of your files before reinstalling.