SYSTEM_PTE_MISUSE
Code: 0xda (218)
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x00da (218)
- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x00da (218)
Parameters
| Parameter | Description |
|---|---|
| 0x01 | The address of the internal lock tracking structure |
| 0x02 | The address of the internal lock tracking structure |
| 0x03 | The address of the first internal tracking structure found |
| 0x04 | The address of the internal lock tracking structure |
| 0x05 | The address of the first internal tracking structure found |
| 0x06 | The MDL specified by the driver |
| 0x07 | The initial mapping |
| 0x08 | The initial mapping |
| 0x09 | The initial mapping |
| 0x0A | 1: The driver requested "bug check on failure" in the MDL. 0: The driver did not request "bug check on failure" in the MDL. |
| 0x0B | The corrupt mapping |
| 0x0C | The corrupt mapping |
| 0x0D | The initial mapping |
| 0x0E | The initial mapping |
| 0x0F | The non-existent mapping |
| 0x10 | The non-existent mapping |
| 0x11 | The non-existent mapping |
| 0x100 | The number of mappings being requested |
| 0x101 | The first mapping address |
| 0x102 | The first mapping address |
| 0x103 | The address of the invalid mapping |
| 0x104 | The first mapping address |
| 0x105 | The first mapping address |
| 0x107 | The first mapping address |
| 0x108 | The first mapping address |
| 0x109 | The first mapping address |
| 0x10A | The first mapping address |
| 0x10B | The first mapping address |
| 0x10C | The first mapping address |
| 0x200 | The first mapping address |
0x201 0x202 | The first mapping address to reserve |
| 0x300 | The first mapping address to release |
| 0x301 | The address of the mapping |
| 0x302 | The address that the caller is trying to release. |
| 0x303 | The first mapping address |
| 0x304 | The first mapping address |
| 0x305 | The first mapping address |
| 0x306 | The first mapping address |
| 0x400 | The base address of the I/O space mapping |
Description
The SYSTEM_PTE_MISUSE bug check has a value of 0x000000DA. This indicates that a page table entry (PTE) routine has been used in an improper way.
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
The error is indicated by the value of Parameter 1.
A stack trace will identify the driver that caused the error.
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 |
|---|---|---|---|
| ESENT.dll | 0xda | 8.11011 | %1 (%2) %3Error (%4) during copy or backup of file %5. |
| EventCreate.exe | 0xda | 78.11011 | %1 |
| KernelBase.dll | 0xda | 78.1 | The image file %1 is strong signed, unable to modify. |
| dsreg.dll | 0xda | 11 | Token binding AIK was successfully deleted. Key type: %1 IDP domain: %2 Tenant-based ID: %3 User SID: %4 |
| kernel32.dll | 0xda | 78.11011 | The image file %1 is strong signed, unable to modify. |
| webservices.dll | 0xda | 78.11011 | Unable to determine IP addresses for DNS host name '%1' and port '%2'. |
| wuaueng.dll | 0xda | 1011 | Commit Started: Windows has started committing the following update: %1 |
| wuauengcore.dll | 0xda | 11 | Commit Started: Windows has started committing the following update: %1 |
| 8 entries | |||