The driver is mismanaging system PTEs.

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.

This solution may not be available if you can't boot into Windows!

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.

A some of the most popular driver download sites:

• CPU and Chipset Drivers: AMD, Intel, Via
• Video Drivers: AMD/ATI, Intel, Nvida
• Computer and other hardware manufacturers

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+)

1. Press the Windows Key and X together, then  Control Panel, then Programs and Features.
2. Select the software to uninstall and select Uninstall.

 For removal of an application (Windows 7 & Vista):

1. Click on Start, Control Panel, then Programs and Features.
2. Select the software to uninstall and select Uninstall.

For removal of an application (Windows XP):

1. Click on Start, Control Panel, then Add or Remove Programs.
2. Select the software to uninstall and select Remove.

To disable a driver:

1. 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.

2. Click on the left side option Advanced system settings (7/Vista only).
3. In System Properties, select the Hardware tab, then click on Device Manager button.
4. Find the hardware/driver of interest (you may need to expand a choice at the "plus" graphic) and double click the choice.
5. 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.
6. Click OK to exit, then close the Device Manager and other previously opened dialogs.

Check out what others say about this issue and review or add your own comments and solutions!

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.

Parameter 2 depends on the value of Parameter 1.

Parameter 3 depends on the value of Parameter 1.

Parameter 4 depends on the value of Parameter 1.