Fix Windows Registry Errors    |    SYSTEM_PTE_MISUSE    |    Repair Windows Error 0x000000DA


STOP 0x000000DA : SYSTEM_PTE_MISUSE

STOP Errors are usually the result of a hardware malfunction or device driver issue. It is also possible to receive a Blue Screen Error due to bad system memory, malfunctioning power supply, components overheating, or hardware overclocked beyond its specification. In older versions of the Windows OS you may also receive Blue Screen Errors due to incompatible DLL files.

Since the only option when receiving a Blue Screen Error is to reboot, any unsaved data is lost. With that in mind, it is very important to eliminate these errors to protect your data.

Basic Troubleshooting

Troubleshooting STOP Errors can be a difficult and time consuming process. Try these basic steps to fix your own Blue Scree Error. We hope it will help you avoid an expensive service call and provide a rewarding experience of solving the problem on your own.

Advanced Troubleshooting

The following details are for advanced users. These are provided for your convenience and may help those with advanced knowledge discover the root cause of their STOP Error.


Stop 0xDA: SYSTEM_PTE_MISUSE

The SYSTEM_PTE_MISUSE stop error code has a value of 0x000000DA. This indicates that a page table entry (PTE) routine has been used in an improper way.

Parameters

The following parameters are displayed on the blue screen. Parameter 1 indicates the type of violation. The meaning of the other parameters depends on the value of Parameter 1.

Parameter 1Parameter 2Parameter 3Parameter 4Cause of Error
0x01The address of the internal lock tracking structure The address of the memory descriptor list The address of the duplicate internal lock tracking structure The mapping being freed is a duplicate.
0x02The address of the internal lock tracking structure The number of mappings that the system expects to free The number of mappings that the driver is requesting to free The number of mappings being freed is incorrect.
0x03The address of the first internal tracking structure found The mapping address that the system expects to free The mapping address that the driver is requesting to free The mapping address being freed is incorrect.
0x04The address of the internal lock tracking structure The page frame number that the system expects should be first in the MDL The page frame number that is currently first in the MDL The first page of the mapped MDL has changed since the MDL was mapped.
0x05The address of the first internal tracking structure found The virtual address that the system expects to free The virtual address that the driver is requesting to free The start virtual address in the MDL being freed has changed since the MDL was mapped.
0x06The MDL specified by the driver The virtual address specified by the driver The number of mappings to free (specified by the driver)The MDL being freed was never (or is currently not) mapped.
0x07The initial mapping The number of mappings Reserved (Windows 2000 only) The mapping range is being double-allocated.
0x08The initial mapping The number of mappings the caller is freeing The number of mappings the system thinks should be freed(Windows 2000 only) The caller is asking to free an incorrect number of mappings.
0x09The initial mapping The number of mappings that the caller is freeingThe mapping index that the system thinks is already free(Windows 2000 only) The caller is asking to free several mappings, but at least one of them is not allocated.
0x0A1: The driver requested "stop error code on failure" in the MDL.

0: The driver did not request "stop error code on failure" in the MDL.

The number of mappings that the caller is allocatingThe type of mapping pool requested(Windows 2000 only) The caller is asking to allocate zero mappings.
0x0BThe corrupt mappingThe number of mappings that the caller is allocatingThe type of mapping pool requested(Windows 2000 only) The mapping list was already corrupt at the time of this allocation. The corrupt mapping is located below the lowest possible mapping address.
0x0CThe corrupt mappingThe number of mappings that the caller is allocatingThe type of mapping pool requested(Windows 2000 only) The mapping list was already corrupt at the time of this allocation. The corrupt mapping is located above the lowest possible mapping address.
0x0DThe initial mapping The number of mappings that the caller is freeingThe type of mapping pool(Windows 2000 only) The caller is trying to free zero mappings.
0x0EThe initial mapping The number of mappings that the caller is freeingThe type of mapping pool(Windows 2000 only) The caller is trying to free mappings, but the guard mapping has been overwritten.
0x0FThe non-existent mappingThe number of mappings that the caller is trying to freeThe type of mapping pool being freed(Windows 2000 only) The caller is trying to free a non-existent mapping. The non-existent mapping is located below the lowest possible mapping address.
0x10The non-existent mappingThe number of mappings the caller is trying to freeThe type of mapping pool being freed(Windows 2000 only) The caller is trying to free a non-existent mapping. The non-existent mapping is located above the highest possible mapping address.
0x11The non-existent mapping The number of mappings that the caller is trying to freeThe type of mapping pool being freed(Windows 2000 only) The caller is trying to free a non-existent mapping. The non-existent mapping is at the base of the mapping address space.
0x100The number of mappings being requested The caller's identifying tag The address of the routine that called the caller of this routine (Windows XP and later only) The caller requested 0 mappings.
0x101The first mapping address The caller's identifying tag The owner's identifying tag (Windows XP and later only) A caller is trying to free a mapping address range that it does not own.
0x102The first mapping address The caller's identifying tag Reserved (Windows XP and later only) The mapping address space that the caller is trying to free is apparently empty.
0x103The address of the invalid mapping The caller's identifying tag The number of mappings in the mapping address space (Windows XP and later only) The mapping address space that the caller is trying to free is still reserved. MmUnmapReservedMapping

must be called before MmFreeMappingAddress.

0x104The first mapping address The caller's identifying tag The owner's identifying tag (Windows XP and later only) The caller is attempting to map an MDL to a mapping address space that it does not own.
0x105The first mapping address The caller's identifying tag Reserved (Windows XP and later only) The caller is attempting to map an MDL to an invalid mapping address space. The caller has mostly likely specified an invalid address.
0x107The first mapping address The address of the non-empty mapping The last mapping address (Windows XP and later only) The caller is attempting to map an MDL to a mapping address space that has not been properly reserved. The caller should have called MmUnmapReservedMapping prior to calling MmMapLockedPagesWithReservedMapping
0x108The first mapping address The caller's identifying tag The owner's identifying tag (Windows XP and later only) The caller is attempting to unmap a locked mapping address space that it does not own.
0x109The first mapping addressThe caller's identifying tag Reserved (Windows XP and later only) The caller is attempting to unmap a locked virtual address space that is apparently empty.
0x10AThe first mapping address The number of mappings in the locked mapping address space The number of mappings to unmap (Windows XP and later only) The caller is attempting to unmap more mappings than actually exist in the locked mapping address space.
0x10BThe first mapping address The caller's identifying tagThe number of mappings to unmap (Windows XP and later only) The caller is attempting to unmap a portion of a locked virtual address space that is not currently mapped.
0x10CThe first mapping address The caller's identifying tag The number of mappings to unmap (Windows XP and later only) The caller is not unmapping the entirety of the locked mapping address space.
0x200The first mapping address 00(Windows XP and later only) The caller is attempting to reserve a mapping address space that contains no mappings.
0x201
0x202
The first mapping address to reserve The address of the mapping that has already been reserved The number of mappings to reserve (Windows XP and later only) One of the mappings that the caller is attempting to reserve has already been reserved.
0x300The first mapping address to release 00(Windows XP and later only) The caller is attempting to release a mapping address space that contains no mappings.
0x301The address of the mapping00(Windows XP and later only) The caller is attempting to release a mapping that it is not permitted to release.
0x303The first mapping address The number of mappings to release 0(Windows XP and later only) The caller is attempting to release a mapping address range that was not reserved.
0x304The first mapping address The number of mappings to release 0(Windows XP and later only) The caller is attempting to release a mapping address range that begins in the middle of a different allocation.
0x305The first mapping address The number of mappings that the caller is trying to release The number of mappings that should be released (Windows XP and later only) The caller is attempting to release the wrong number of mappings.
0x306The first mapping address The free mapping address The number of mappings to release (Windows XP and later only) One of the mappings that the caller is attempting to release is already free.
0x400The base address of the I/O space mapping The number of pages to be freed 0(Windows XP and later only) The caller is trying to free an I/O space mapping that the system is unaware of.

Cause

The error is indicated by the value of Parameter 1.

A stack trace will identify the driver that caused the error.

Helpful Tools

The following products are free to try. We have found them to be of the highest quality and value. They have been extremely useful in our own pc troubleshooting and maintainance and we highly recommend trying them out for yourself.


Anti-Malware Pro

With a lightning fast free scan and the largest authentic spyware detection database we have seen, Anti-Malware Pro finds and removes threats to your PC stability and security. Download Anti-Malware Pro


DriverFinder

DriverFinder will scan your system for driver and software updates. Its easy to use interface makes keeping your drivers updated quick and simple. They will even send you an email notification when new driver updates are available for your system! It doesn't get any more convenient than this. Download DriverFinder





Browse STOP Error Codes:





Is a STOP error code missing?

Help us to make errorDecoder.com the best resource we possibly can by submitting you very own STOP error code details. If you have detailed information on any STOP error code please let us know by visiting the following link.

Submit Error Details Form

STOP 0x000000DA    |    SYSTEM_PTE_MISUSE    |    Fix Error Code 0x000000DA