Process has locked pages

Mar 15, 2018
1
0
10
Hello i've started to get this BSOD almost every other day for the past two weeks. Heres the crash dump


is
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 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.24024.amd64fre.win7sp1_ldr.180112-0600
Machine Name:
Kernel base = 0xfffff800`03209000 PsLoadedModuleList = 0xfffff800`03448a90
Debug session time: Thu Mar 15 08:24:42.496 2018 (UTC - 4:00)
System Uptime: 0 days 15:15:48.214
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS (cb)
Caused by a driver not cleaning up completely after an I/O.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff80003614969, The calling address in the driver that locked the pages or if the
IO manager locked the pages this points to the dispatch routine of
the top driver on the stack to which the IRP was sent.
Arg2: 0000000000000000, The caller of the calling address in the driver that locked the
pages. If the IO manager locked the pages this points to the device
object of the top driver on the stack to which the IRP was sent.
Arg3: fffffa800db7fa30, A pointer to the MDL containing the locked pages.
Arg4: 0000000000000004, The number of locked pages.

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

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

FAULTING_IP:
nt!MmProbeAndLockProcessPages+59
fffff800`03614969 eb06 jmp nt!MmProbeAndLockProcessPages+0x61 (fffff800`03614971)

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xCB

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8000357eecc to fffff800032af2a0

STACK_TEXT:
fffff880`0412b998 fffff800`0357eecc : 00000000`000000cb fffff800`03614969 00000000`00000000 fffffa80`0db7fa30 : nt!KeBugCheckEx
fffff880`0412b9a0 fffff800`034e518e : 00000000`00000001 fffffa80`0cd71040 fffffa80`00000000 fffffa80`00000004 : nt! ?? ::NNGAKEGL::`string'+0x131ac
fffff880`0412b9e0 fffff800`0325e3d4 : 00000000`00000000 fffffa80`0ccd1c90 fffffa80`12c975c0 fffff800`03509b9b : nt!PspProcessDelete+0x1a2
fffff880`0412ba40 fffff800`034e530b : fffffa80`12c975f0 00000000`00000001 fffffa80`0cd71040 fffff800`0323472c : nt!ObfDereferenceObject+0xd4
fffff880`0412baa0 fffff800`0325e3d4 : 00000000`00000000 00000000`00000000 fffffa80`0ccd1b40 fffffa80`12c99030 : nt!PspThreadDelete+0xe3
fffff880`0412bae0 fffff800`03396550 : 00000000`00000000 00000000`00000000 00000000`00000000 80000003`f666d963 : nt!ObfDereferenceObject+0xd4
fffff880`0412bb40 fffff800`03240001 : fffff800`033964a0 fffff800`0341f650 fffffa80`0cd71040 00000000`00000000 : nt!PspReaper+0xb0
fffff880`0412bb70 fffff800`03551a3c : 00000000`00000000 fffff880`03dca180 00000000`00000080 fffffa80`0cd36b00 : nt!ExpWorkerThread+0x111
fffff880`0412bc00 fffff800`032b5716 : fffff880`03dca180 fffffa80`0cd71040 fffff880`03dd7240 00000000`00000000 : nt!PspSystemThreadStartup+0x140
fffff880`0412bc40 00000000`00000000 : fffff880`0412c000 fffff880`04126000 fffff880`0412b8a0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!MmProbeAndLockProcessPages+59
fffff800`03614969 eb06 jmp nt!MmProbeAndLockProcessPages+0x61 (fffff800`03614971)

SYMBOL_NAME: nt!MmProbeAndLockProcessPages+59

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 5a58dc54

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xCB_nt!MmProbeAndLockProcessPages+59

BUCKET_ID: X64_0xCB_nt!MmProbeAndLockProcessPages+59

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

 
Solution
There is a driver installed which is incompatible with your system.
Use "system restore" to turn the hard drive back to the time before the driver was updated.
Then turn automatic updates OFF (or the same problem will install itself again).
Check manufacturer for list of incompatible updates...

nicolatesla

Distinguished
Nov 3, 2009
78
0
18,710
There is a driver installed which is incompatible with your system.
Use "system restore" to turn the hard drive back to the time before the driver was updated.
Then turn automatic updates OFF (or the same problem will install itself again).
Check manufacturer for list of incompatible updates...
 
Solution