BSOD - process has locked pages

[fsusnja]

Getting BSOD with error message "PROCESS_HAS_LOCKED_PAGES" almost daily. Had enough and tried re-installing windows 10. Cannot get it to boot from USB or DVD. After selecting boot device, windows logo is showing and then just a black screen... nothing happens.

Tried changing BIOS to legacy, turned off secure boot.. same thing.

Please help me.

Minidump content below:

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff803`f0c0f000 PsLoadedModuleList = 0xfffff803`f0f5b660
Debug session time: Mon Nov 20 17:34:40.057 2017 (UTC - 5:00)
System Uptime: 0 days 5:17:08.709
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PROCESS_HAS_LOCKED_PAGES (76)
Caused by a driver not cleaning up correctly after an I/O.
Arguments:
Arg1: 0000000000000000, Locked memory pages found in process being terminated.
Arg2: ffffb3836aefb080, Process address.
Arg3: 0000000000000002, Number of locked pages.
Arg4: 0000000000000000, Pointer to driver stacks (if enabled) or 0 if not.
Issue a !search over all of physical memory for the current process pointer.
This will yield at least one MDL which points to it. Then do another !search
for each MDL found, this will yield the IRP(s) that point to it, revealing
which driver is leaking the pages.
Otherwise, set HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management\TrackLockedPages to a DWORD 1 value and reboot. Then the system
will save stack traces so the guilty driver can be easily identified.
When you enable this flag, if the driver commits the error again you will
see a different bugcheck - DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS (0xCB) -
which can identify the offending driver(s).

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

PROCESS_NAME: backgroundTask

DEFAULT_BUCKET_ID: DRIVER_FAULT_0x76

BUGCHECK_STR: 0x76

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff803f121a6ad to fffff803f0d7b580

STACK_TEXT:
ffffa301`ce1317c8 fffff803`f121a6ad : 00000000`00000076 00000000`00000000 ffffb383`6aefb080 00000000`00000002 : nt!KeBugCheckEx
ffffa301`ce1317d0 fffff803`f0cb69f8 : ffffb383`6aefb080 ffffb383`6aefb050 ffffb383`69b2b7c0 ffffb383`00000000 : nt!MmDeleteProcessAddressSpace+0x1458f9
ffffa301`ce131820 fffff803`f10bc32e : ffffb383`6aefb050 ffffb383`6aefb050 ffffb383`6aefb050 00000000`00000000 : nt!PspProcessDelete+0x198
ffffa301`ce1318c0 fffff803`f0c72f56 : 00000000`00000000 00000000`00000000 ffffb383`6aefb050 ffffb383`6aefb080 : nt!ObpRemoveObjectRoutine+0x7e
ffffa301`ce131920 fffff803`f10b2152 : ffffb383`66a85540 ffff9083`fef8b000 ffff9083`fef8b000 00000000`00000000 : nt!ObfDereferenceObjectWithTag+0xc6
ffffa301`ce131960 fffff803`f10b412b : 00000000`00000000 00000000`00000000 00000000`c0000001 ffffb383`69295f00 : nt!ObCloseHandleTableEntry+0x272
ffffa301`ce131aa0 fffff803`f0d86413 : ffffb383`69b2b7c0 00000284`87a66bb0 00000000`00000000 00000000`00000000 : nt!NtClose+0xcb
ffffa301`ce131b00 00007ff9`65105584 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000ef`5a07f758 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ff9`65105584


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MmDeleteProcessAddressSpace+1458f9
fffff803`f121a6ad cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MmDeleteProcessAddressSpace+1458f9

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 59fa9d38

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x76_backgroundTask_nt!MmDeleteProcessAddressSpace+1458f9

BUCKET_ID: X64_0x76_backgroundTask_nt!MmDeleteProcessAddressSpace+1458f9

Followup: MachineOwner
---------

 

[Colif]

if win 10 is still on the PC, one way to boot from USB is as follows:
go to settings/update & security/recovery
under advanced startup, click restart now button
will load into a blue menu
choose Use a device
Put USB in and choose from list. PC should restart and boot from USB

Can't say I ever seen this error before. Its obviously a driver but its not telling us which.
If you want to fix it instead of doing a clean install, can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

 

[fsusnja]

if win 10 is still on the PC, one way to boot from USB is as follows:
go to settings/update & security/recovery
under advanced startup, click restart now button
will load into a blue menu
choose Use a device
Put USB in and choose from list. PC should restart and boot from USB

Can't say I ever seen this error before. Its obviously a driver but its not telling us which.
If you want to fix it instead of doing a clean install, can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

Hi Colif, thanks for your answer. I didn't want to deal with it and wanted to just wipe everything and perform a clean windows install. Since booting from a Win10 USB/DVD caused it to just go to a black screen, I tried formatting everything with a Win7 clean install so I could attempt a Win10 install from there.

Both SSD and HDD are formatted now, EUFI/BIOS on default settings and Win7 installed. If I try to install Win10 from USB/DVD it just gets stuck again on black screen. Can't be a driver issue now as none are installed. I tested my memory before the format and everything was fine.

Now that drives are formatted I have eliminated the possibility of drivers or any other software being the cause. I have tried both USB and DVD to make sure none are damaged. Tried two different iso sources for the Win10 copy to eliminate possibility of the data being corrupted. If it's hardware related, I wouldn't know which component tbh. It seems to be working fine on Win7.

Getting a bit desperate now.

 

[Colif]

what are specs of PC?

Have you got the latest BIOS?

 

[Colif]

Bug Check 0x76: PROCESS_HAS_LOCKED_PAGES - The PROCESS_HAS_LOCKED_PAGES bug check has a value of 0x00000076. This bug check indicates that a driver failed to release locked pages after an I/O operation, or that it attempted to unlock pages that were already unlocked.

this appears to just be a software error. Unsure its related to the black screen, that sounds more like a graphics problem

 

[fsusnja]

what are specs of PC?

Have you got the latest BIOS?

i5 4670k
GA-Z87-HD3
GTX 760
8GB RAM

Not sure about the BIOS version, I'll check that as soon as I'm home. I can try flashing it to the newest version if it's outdated to eliminate that being the issue. But doubt it tbh. I see the latest version came out in 2014 and I've installed Win10 multiple times in the last few years.

I can maybe try disconnecting the GPU and have it run on the onboard one...

 

[Colif]

try bios and try onboard gpu. Glad you asked as it saved me looking up motherboard to see if you had onboard. I knew CPU did since I have an I5 4690K

Seems odd it works on win 7 but not 10. What GPU do you have?

Its not a common BSOD so I don't have a go to answer, or suggestion as to what cause is.

 

[fsusnja]

try bios and try onboard gpu. Glad you asked as it saved me looking up motherboard to see if you had onboard. I knew CPU did since I have an I5 4690K

Seems odd it works on win 7 but not 10. What GPU do you have?

Its not a common BSOD so I don't have a go to answer, or suggestion as to what cause is.

GPU is 760 GTX. Yeah I too find it odd.

Hope that's the issue. Will check when I'm off work later today.

 

[fsusnja]

what are specs of PC?

Have you got the latest BIOS?

It was the BIOS after all. Had version F6, latest one (2014 lol) is F8.

Flashed it and was able to continue with the Win10 install.

Thanks for your help