Partition Commander Now it's easy for anyone to safely partition their hard drive! You can reclaim waste disk space, organize files, even add new OSes.
Fix-It Utilities Make your PC run like new! Includes Anti-Virus, Anti-Spyware, hardware diagnostics, registry fixer, and more!
RadarSync Ensures you have the latest drivers and software updates to make your PC run better and safer.
The driver is mismanaging system PTEs.
STOP: 0x000000DA
Description
A device driver has a bug.
Some older versions of Windows may show the description as "SYSTEM_PTE_MISUSE".
This is a fatal Windows error, typically called a Stop message, Bug Check, or more commonly the Blue Screen of Death (BSoD). The system is in a forced reboot state. Any unsaved work is likely lost.
Sample Screen
A problem has been detected and Windows has been shut down to prevent damage to your computer.
The driver is mismanaging system PTEs.
If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:
Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.
Technical Information:
*** STOP: 0x000000DA
Beginning dump of physical memory
Physical memory dump complete.
Contact your system administrator or technical support group for further
assistance.
Text may appear differently depending on where the error occurs.
Additional technical information (hex values) specific to a machine are not shown.
Install the latest Windows software updates. Don't forget to check for non-critical updates too!
To manually get updates, open Internet Explorer (you can't use a non-Microsoft browser for updates).
For IE 8 and later: Click on Safety, then Windows Update. Follow the instructions.
For IE 7 and older: Click on Tools, then Windows Update. Follow the instructions.
FaultWire Staff Posted: 5-Oct-2008
Get the Latest Drivers
6
Check if you are using the latest hardware drivers, especially the chipset and video drivers. Older drivers are a common contributor to BSoD issues.
You can use a product like Driver Genius or Radar Sync to verify you have the latest drivers and help keep all your drivers up-to-date. If you're comfortable with driver installations, you can individually find and install current drivers.
If you can get the system up for more than a few minutes or can use safe mode, try removing the last installed software application or driver.
For removal of an application (Windows 8+)
Press the Windows Key and X together, then Control Panel, then Programs and Features.
Select the software to uninstall and select Uninstall.
For removal of an application (Windows 7 & Vista):
Click on Start, Control Panel, then Programs and Features.
Select the software to uninstall and select Uninstall.
For removal of an application (Windows XP):
Click on Start, Control Panel, then Add or Remove Programs.
Select the software to uninstall and select Remove.
To disable a driver:
Bring up the system information dialog:
On the keyboard, press the Windows key + Pause/Break.
or
Select Start, right click Computer and on the drop-down, select Properties.
Click on the left side option Advanced system settings(7/Vista only).
In System Properties, select the Hardware tab, then click on Device Manager button.
Find the hardware/driver of interest (you may need to expand a choice at the "plus" graphic) and double click the choice.
Select the Driver tab. Here you can perform a number of actions such as update the driver, roll Back the driver to an older version, disable or uninstall the driver.
Click OK to exit, then close the Device Manager and other previously opened dialogs.
A page table entry (PTE) routine has been used in an improper way.
After the Stop code will be 4 hex values: {Parameter 1, Parameter 2, Parameter 3, Parameter 4}.
Parameter 1 specifies the cause of the issue. The Windows column with a "-" means that version and older ones, where a "+" indicates that version and all newer ones. A blank indicates all versions.
Parameter 1
Windows
Cause
0x00000001
The mapping being freed is a duplicate.
0x00000002
The number of mappings being freed is incorrect.
0x00000003
The mapping address being freed is incorrect.
0x00000004
The first page of the mapped MDL has changed since the MDL was mapped.
0x00000005
The start virtual address in the MDL being freed has changed since the MDL was mapped.
0x00000006
The MDL being freed was never (or is currently not) mapped.
0x00000007
2000-
The mapping range is being double-allocated.
0x00000008
2000-
The caller is asking to free an incorrect number of mappings.
0x00000009
2000-
The caller is asking to free several mappings, but at least one of them is not allocated.
0x0000000A
2000-
The caller is asking to allocate zero mappings.
0x0000000B
2000-
The mapping list was already corrupt at the time of this allocation. The corrupt mapping is located below the lowest possible mapping address.
0x0000000C
2000-
The mapping list was already corrupt at the time of this allocation. The corrupt mapping is located above the lowest possible mapping address.
0x0000000D
2000-
The caller is trying to free zero mappings.
0x0000000E
2000-
The caller is trying to free mappings, but the guard mapping has been overwritten.
0x0000000F
2000-
The caller is trying to free a non-existent mapping. The non-existent mapping is located below the lowest possible mapping address.
0x00000010
2000-
The caller is trying to free a non-existent mapping. The non-existent mapping is located above the highest possible mapping address.
0x00000011
2000-
The caller is trying to free a non-existent mapping. The non-existent mapping is at the base of the mapping address space.
0x00000100
XP+
The caller requested 0 mappings.
0x00000101
XP+
A caller is trying to free a mapping address range that it does not own.
0x00000102
XP+
The mapping address space that the caller is trying to free is apparently empty.
0x00000103
XP+
The mapping address space that the caller is trying to free is still reserved. MmUnmapReservedMapping must be called before MmFreeMappingAddress.
0x00000104
XP+
The caller is attempting to map an MDL to a mapping address space that it does not own.
0x00000105
XP+
The caller is attempting to map an MDL to an invalid mapping address space. The caller has mostly likely specified an invalid address.
0x00000107
XP+
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.
0x00000108
XP+
The caller is attempting to unmap a locked mapping address space that it does not own.
0x00000109
XP+
The caller is attempting to unmap a locked virtual address space that is apparently empty.
0x0000010A
XP+
The caller is attempting to unmap more mappings than actually exist in the locked mapping address space.
0x0000010B
XP+
The caller is attempting to unmap a portion of a locked virtual address space that is not currently mapped.
0x0000010C
XP+
The caller is not unmapping the entirety of the locked mapping address space.
0x00000200
XP+
The caller is attempting to reserve a mapping address space that contains no mappings.
0x00000201
XP+
One of the mappings that the caller is attempting to reserve has already been reserved.
0x00000202
XP+
One of the mappings that the caller is attempting to reserve has already been reserved.
0x00000300
XP+
The caller is attempting to release a mapping address space that contains no mappings.
0x00000301
XP+
The caller is attempting to release a mapping that it is not permitted to release.
0x00000303
XP+
The caller is attempting to release a mapping address range that was not reserved.
0x00000304
XP+
The caller is attempting to release a mapping address range that begins in the middle of a different allocation.
0x00000305
XP+
The caller is attempting to release the wrong number of mappings.
0x00000306
XP+
One of the mappings that the caller is attempting to release is already free.
0x00000400
XP+
The caller is trying to free an I/O space mapping that the system is unaware of.
While BSoD fatal stop errors are identified by Microsoft Windows, they are often caused by
non-Microsoft applications, drivers and hardware issues.
Research this Issue
Getting search results...
Notes
While we believe this information up to date and accurate, FAQware is not responsible for any inaccuracies. If you find something that is out of date or inaccurate, please let us know at
so we can correct it.
