Skip to content
PCDecoder
0x000000DASYSTEM_PTE_MISUSEStop codeWidely reported

SYSTEM_PTE_MISUSE (0xDA): what it means and how to fix it

Updated Oct 26, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

SYSTEM_PTE_MISUSE indicates that a driver called a page table entry routine incorrectly while managing system memory. A faulty or outdated device driver is almost always the root cause. Start by inspecting Device Manager for malfunctioning devices and checking recent driver updates.

What it means

Bug check 0x000000DA indicates that a system routine handling page table entries (PTEs) was executed improperly. Windows relies on page table entries to connect the virtual memory used by software to the physical memory installed on the motherboard. When drivers manage system buffers or coordinate memory transfers, they call memory manager functions such as MmMapLockedPagesWithReservedMapping or MmUnmapReservedMapping. If a routine receives invalid parameters or violates kernel memory rules, Windows halts the operating system immediately to prevent memory corruption.

Why PTE misuse happens

Kernel-mode drivers must strictly follow rules when mapping and releasing memory descriptor lists (MDLs). The crash report records specific violation types through parameter values. Frequent triggers include a driver attempting to free a memory range that it does not own, trying to unmap memory that was never mapped, or releasing a duplicate mapping. Other violations happen when a caller attempts to release zero mappings, specifies the wrong number of mappings to free, or attempts to free an I/O space mapping that the system is unaware of. When any of these illegal requests occur, the kernel triggers a bug check because continuing execution could corrupt operating system structures.

Identifying the component responsible

Drivers for graphics cards, network adapters, storage controllers, and low-level system utilities interact heavily with memory descriptor lists. If a driver contains programming bugs or conflicts with another driver, it can submit malformed addresses into memory management routines. A stack trace generated during crash analysis pinpoints the exact driver file involved in the failure. Users report encountering 0x000000DA during computer startup or intermittently while working in Windows. Checking Event Viewer logs and verifying recent driver updates will help identify which driver triggered the stop code.

Common causes

  • A device driver requested an improper memory mapping or unmapping routine.
  • A driver attempted to release or unmap a virtual memory range that it does not own.
  • A driver tried to free a memory descriptor list that was never mapped.
  • Corrupted system files damaged internal kernel memory tracking structures.
  • Incompatible or recently added hardware created driver-level memory management conflicts.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Inspect Device Manager for driver warnings

    Use this first to check if Windows has flagged a malfunctioning hardware driver.

    1. Right-click the Start menu button and select Device Manager.
    2. Scan the hardware list for any device displaying a yellow exclamation point (!).
    3. Right-click the flagged device and select Properties.
    4. Review the device status and events log on the Driver tab.
    5. Select Update Driver to check for a newer version, or select Roll Back Driver if the crash started after a recent update.
    Did this fix it?

  2. Run the System File Checker

    Use this when damaged Windows files might be interfering with memory management routines.

    1. Right-click the Start menu button and select Terminal (Admin) or Command Prompt (Admin).
    2. Type SFC /scannow and press Enter.
    3. Wait for the utility to complete the verification phase and apply any repairs.
    4. Restart the computer once the scan reaches 100 percent completion.
    Did this fix it?

  3. Inspect Event Viewer for critical errors

    Use this to identify which driver or service failed immediately before the crash occurred.

    1. Right-click the Start menu button and select Event Viewer.
    2. Expand Windows Logs in the left sidebar and click System.
    3. Look through the log for Critical or Error events recorded in the same time window as the blue screen.
    4. Read the event details to identify any specific driver file names or device identifiers associated with the crash.
    5. Update or remove the driver matching the name found in the log.
    Did this fix it?

  4. Disconnect recently added hardware

    Use this if the blue screen began appearing shortly after installing new components or peripherals.

    1. Shut down the computer completely.
    2. Disconnect any recently attached external devices, expansion cards, or internal storage drives.
    3. Power on the computer to see if the crash reoccurs.
    4. Check the hardware manufacturer website for updated firmware, patches, or compatibility requirements before reconnecting the hardware.
    Did this fix it?

  5. Run hardware diagnostics and update system firmware

    Use this if driver updates do not resolve the crash and underlying hardware issues are suspected.

    1. Restart the computer and press the manufacturer setup key to enter the UEFI or BIOS menu.
    2. Run the built-in hardware diagnostics supplied by your computer manufacturer.
    3. Visit the PC manufacturer support website to check for updated system BIOS or firmware releases.
    4. Install any recommended firmware updates following the manufacturer instructions.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this. Most recent activity:

Checked Oct 26, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

What does PTE stand for in Windows?

PTE stands for Page Table Entry. It is a data structure used by the Windows memory manager to map virtual memory addresses to physical memory addresses.

How do I identify the exact driver causing 0x000000DA?

A kernel crash dump analyzed with WinDbg will display a stack trace that points directly to the driver responsible. You can also inspect the System log in Event Viewer for critical errors logged at the exact time of the crash.

Can malware cause a SYSTEM_PTE_MISUSE blue screen?

Yes. Malicious software can infect system files or disk structures such as the Master Boot Record, resulting in memory corruption that triggers kernel bug checks. Running a full antivirus scan will check for and eliminate these infections.

More stop codes decoded