Getting BSOD multiple times per day

[fsusnja]

Hi all,

Getting BSOD randomly multiple times per day. At the bottom of below minidump analysis it says that I might have memory corruption. I ran memtest86 and all seems to be fine.

This might have something to do with one of my drivers. Hopefully somebody can give me some advice on how to solve the issue.

Thanks in advance!


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 16299 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff803`9ba1a000 PsLoadedModuleList = 0xfffff803`9bd81110
Debug session time: Mon Mar 5 13:17:07.377 2018 (UTC - 5:00)
System Uptime: 1 days 5:25:01.056
*******************************************************************************
* *
* 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: ffffcf8e102c7580, Process address.
Arg3: 0000000000000006, 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

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x76

CURRENT_IRQL: 0

BAD_PAGES_DETECTED: 670c

LAST_CONTROL_TRANSFER: from fffff8039c03ab47 to fffff8039bb8f430

STACK_TEXT:
ffffcb03`9e6378a8 fffff803`9c03ab47 : 00000000`00000076 00000000`00000000 ffffcf8e`102c7580 00000000`00000006 : nt!KeBugCheckEx
ffffcb03`9e6378b0 fffff803`9ba3bfab : ffffcf8e`102c7580 ffffcf8e`102c7858 ffffcf8e`121c1700 ffffcf8e`102c7580 : nt!MmDeleteProcessAddressSpace+0x181467
ffffcb03`9e637900 fffff803`9bf4e0be : ffffcf8e`102c7858 ffffcf8e`102c7550 ffffcf8e`102c7858 00000000`00000000 : nt!PspProcessDelete+0x19b
ffffcb03`9e6379a0 fffff803`9ba65a36 : 00000000`00000000 00000000`00000000 ffffcf8e`102c7858 ffffcf8e`102c7580 : nt!ObpRemoveObjectRoutine+0x7e
ffffcb03`9e637a00 fffff803`9beb94e2 : 00000000`00000000 ffffcf8e`11622728 ffffcf8e`11622728 00000000`00000000 : nt!ObfDereferenceObjectWithTag+0xc6
ffffcb03`9e637a40 fffff803`9bf4e0be : fffff803`9baf5900 ffffcf8e`11622050 fffff803`9baf5900 ffffcf8e`11622050 : nt!PspThreadDelete+0x1d2
ffffcb03`9e637ab0 fffff803`9ba65a36 : 00000000`00000000 00000000`00000000 fffff803`9baf5900 ffffcf8e`11622080 : nt!ObpRemoveObjectRoutine+0x7e
ffffcb03`9e637b10 fffff803`9baf5972 : 00000000`00000000 00000000`00000000 ffffcf8e`0baff3d0 ffffcf8e`11622698 : nt!ObfDereferenceObjectWithTag+0xc6
ffffcb03`9e637b50 fffff803`9ba554d5 : ffffcf8e`121c1700 ffffcf8e`0baff3d0 ffffcf8e`0baff300 ffffcf8e`0baff3d0 : nt!PspReaper+0x72
ffffcb03`9e637b80 fffff803`9bb30b87 : ffffcf8e`121c1700 00000000`00000080 ffffcf8e`0ba9a040 ffffcf8e`121c1700 : nt!ExpWorkerThread+0xf5
ffffcb03`9e637c10 fffff803`9bb96be6 : fffff803`9ac33180 ffffcf8e`121c1700 fffff803`9bb30b40 00000000`00000004 : nt!PspSystemThreadStartup+0x47
ffffcb03`9e637c60 00000000`00000000 : ffffcb03`9e638000 ffffcb03`9e632000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

SYMBOL_NAME: PAGE_NOT_ZERO

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: PAGE_NOT_ZERO

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

*** Memory manager detected 26380 instance(s) of page corruption, target is likely to have memory corruption.

 

[SgtScream]

Nine times out of ten, a bluescreen can be resolved by updating your graphics drivers.