PROCESS_HAS_LOCKED_PAGES blue screen

Ali lahko pomagate? Kaj bi tukaj bilo narobe.

Instant Online Crash Analysis, brought to you by OSR Open Systems Resources, Inc.
Hide DivPrimary Analysis

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 7600 MP (8 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82e4a000 PsLoadedModuleList = 0x82f92810
Debug session time: Fri Jun 18 10:02:10.690 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:35.674
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PROCESS_HAS_LOCKED_PAGES (76)
Caused by a driver not cleaning up correctly after an I/O.
Arguments:
Arg1: 00000000, Locked memory pages found in process being terminated.
Arg2: 8edae130, Process address.
Arg3: 00000033, Number of locked pages.
Arg4: 00000000, 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: svchost.exe

DEFAULT_BUCKET_ID: DRIVER_FAULT_0x76

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x76

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 830bd2ef to 82f26d10

STACK_TEXT:
a325fc7c 830bd2ef 00000076 00000000 8edae130 nt!KeBugCheckEx+0x1e
a325fca0 830ba2f7 8573c990 8edae118 00000000 nt!MmDeleteProcessAddressSpace+0x50
a325fcd4 8306b788 8edae130 00000000 8edae118 nt!PspProcessDelete+0x15d
a325fcec 830d4356 00000001 82f8bb90 87473d48 nt!ObpRemoveObjectRoutine+0x59
a325fd00 82eb7f3b 00000000 00000000 87473d48 nt!ObpProcessRemoveObjectQueue+0x36
a325fd50 830586d3 80000000 867f250a 00000000 nt!ExpWorkerThread+0x10d
a325fd90 82f0a0f9 82eb7e2e 80000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MmDeleteProcessAddressSpace+50
830bd2ef cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MmDeleteProcessAddressSpace+50

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x76_svchost.exe_nt!MmDeleteProcessAddressSpace+50

BUCKET_ID: 0x76_svchost.exe_nt!MmDeleteProcessAddressSpace+50

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