Solved!
Go to SolutionWindows 10 installation SYSTEM_PTE_MISUSE BSOD
I have 2 laptops, a Dell Inspiron 5559, and a Dell Inspiron 15 5000 2-in-1. I need to reinstall Windows 10 on the 5559, so I decided to make a Windows 10 installation disk. Since the only other laptop I have right now is the 15 5000 2-in-1, so I made an install disk on that. Since the 15 5000 2-in-1 doesn't have a disk drive, I decided to make a bootable Windows 10 install USB. I made sure the USB has the proper files for the Windows 10 install on it. But when I try to boot to the installation USB on the 5559, the Windows 10 boot screen shows up with the spinning loading indicator beneath it, and before it loads the installer, it gives me a BSOD with the error code SYSTEM_PTE_MISUSE. Help would be very much appreciated.
34717
0
Posted September 9th, 2019 18:00
I just attempted the steps in the link and they did not work. Also, I did use the official Media Creation Tool to make the Windows 10 install flash drive
34723
0
Posted September 9th, 2019 18:00
The following might help.
https://www.thewindowsclub.com/fix-system_pte_misuse-bluescreen-of-death-error
Also make sure you download the media creation tool from MS to create the bootable USB drive.
I am not a Dell employee...I am forum volunteer
Serious work on an E5430 and constantly building and working on an i5-6500 Desktop
34683
0
Posted September 10th, 2019 04:00
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.
Cause
The error is indicated by the value of Parameter 1.
A stack trace will identify the driver that caused the error.
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xda--system-pte-misuse
SYSTEM_PTE_MISUSE Parameters
Parameter 1 indicates the type of violation. The meaning of the other parameters depends on the value of Parameter 1.
Parameter 1 Parameter 2 Parameter 3 Parameter 4 Cause of Error0x01
The 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.
0x02
The 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.
0x03
The 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.
0x04
The 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.
0x05
The 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.
0x06
The 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.
0x07
The initial mapping
The number of mappings
Reserved
(Windows 2000 only) The mapping range is being double-allocated.
0x08
The 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.
0x09
The initial mapping
The number of mappings that the caller is freeing
The 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.
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.
The number of mappings that the caller is allocating
The type of mapping pool requested
(Windows 2000 only) The caller is asking to allocate zero mappings.
0x0B
The corrupt mapping
The number of mappings that the caller is allocating
The 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.
0x0C
The corrupt mapping
The number of mappings that the caller is allocating
The 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.
0x0D
The initial mapping
The number of mappings that the caller is freeing
The type of mapping pool
(Windows 2000 only) The caller is trying to free zero mappings.
0x0E
The initial mapping
The number of mappings that the caller is freeing
The type of mapping pool
(Windows 2000 only) The caller is trying to free mappings, but the guard mapping has been overwritten.
0x0F
The non-existent mapping
The number of mappings that the caller is trying to free
The 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.
0x10
The non-existent mapping
The number of mappings the caller is trying to free
The 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.
0x11
The non-existent mapping
The number of mappings that the caller is trying to free
The 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.
0x100
The number of mappings being requested
The caller's identifying tag
The address of the routine that called the caller of this routine
The caller requested 0 mappings.
0x101
The first mapping address
The caller's identifying tag
The owner's identifying tag
A caller is trying to free a mapping address range that it does not own.
0x102
The first mapping address
The caller's identifying tag
Reserved
The mapping address space that the caller is trying to free is apparently empty.
0x103
The address of the invalid mapping
The caller's identifying tag
The number of mappings in the mapping address space
The mapping address space that the caller is trying to free is still reserved. MmUnmapReservedMapping
must be called before MmFreeMappingAddress.
0x104
The first mapping address
The caller's identifying tag
The owner's identifying tag
The caller is attempting to map an MDL to a mapping address space that it does not own.
0x105
The first mapping address
The caller's identifying tag
Reserved
The caller is attempting to map an MDL to an invalid mapping address space. The caller has mostly likely specified an invalid address.
0x107
The first mapping address
The address of the non-empty mapping
The last mapping address
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
0x108
The first mapping address
The caller's identifying tag
The owner's identifying tag
The caller is attempting to unmap a locked mapping address space that it does not own.
0x109
The first mapping address
The caller's identifying tag
Reserved
The caller is attempting to unmap a locked virtual address space that is apparently empty.
0x10A
The first mapping address
The number of mappings in the locked mapping address space
The number of mappings to unmap
The caller is attempting to unmap more mappings than actually exist in the locked mapping address space.
0x10B
The first mapping address
The caller's identifying tag
The number of mappings to unmap
The caller is attempting to unmap a portion of a locked virtual address space that is not currently mapped.
0x10C
The first mapping address
The caller's identifying tag
The number of mappings to unmap
The caller is not unmapping the entirety of the locked mapping address space.
0x200
The first mapping address
0
0
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
One of the mappings that the caller is attempting to reserve has already been reserved.
0x300
The first mapping address to release
0
0
The caller is attempting to release a mapping address space that contains no mappings.
0x301
The address of the mapping
0
0
The caller is attempting to release a mapping that it is not permitted to release.
0x302
The address that the caller is trying to release.
Reserved
Reserved
The caller is attempting to release a system address that is not currently mapped.
0x303
The first mapping address
The number of mappings to release
0
The caller is attempting to release a mapping address range that was not reserved.
0x304
The first mapping address
The number of mappings to release
0
The caller is attempting to release a mapping address range that begins in the middle of a different allocation.
0x305
The first mapping address
The number of mappings that the caller is trying to release
The number of mappings that should be released
The caller is attempting to release the wrong number of mappings.
0x306
The first mapping address
The free mapping address
The number of mappings to release
One of the mappings that the caller is attempting to release is already free.
0x400
The base address of the I/O space mapping
The number of pages to be freed
0
The caller is trying to free an I/O space mapping that the system is unaware of.
13330
0
Posted May 3rd, 2021 02:00
I am facing the same issue with the same unit. I cannot proceed into the setup it show a blue screen with dashed lines.
ethb
5 Posts
34704
0
Posted September 9th, 2019 21:00
Nevermind, I fixed it, I just went into the BIOS settings and disabled PTT security