Hello abaloch05.
It is a stop 0x76, basically it is caused by some driver malfunctioning.
But the failing driver is not traced in the solitary crash dump that you uploaded.
Enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Information
Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.
How Can we know that DV is enabled:
It will make the system bit of slow, laggy.
Warning
Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using
CCleaner looking at Tools > System Restore.
If there is no points,
make a System Restore Point manually before enabling DV.
Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
________________________________________________________________________
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 76, {0, fffffa8010f2a060, 2, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+17dc6 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* 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: fffffa8010f2a060, 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:
------------------
PROCESS_NAME: smss.exe
DEFAULT_BUCKET_ID: DRIVER_FAULT_0x76
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x76
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002fb5ad9 to fffff80002c7ab80
STACK_TEXT:
fffff880`035e8998 fffff800`02fb5ad9 : 00000000`00000076 00000000`00000000 fffffa80`10f2a060 00000000`00000002 : nt!KeBugCheckEx
fffff880`035e89a0 fffff800`02f343f7 : fffffa80`10f2a060 fffffa80`0c6b5d10 fffffa80`00000000 fffffa80`00000002 : nt! ?? ::NNGAKEGL::`string'+0x17dc6
fffff880`035e89e0 fffff800`02c83e54 : 00000000`00000000 fffffa80`10f2a060 fffffa80`10f2a030 fffff800`02f31a9e : nt!PspProcessDelete+0x177
fffff880`035e8a40 fffff800`02f50463 : fffffa80`10f2a060 00000000`00000001 fffffa80`0c725660 fffffa80`117b9b20 : nt!ObfDereferenceObject+0xd4
fffff880`035e8aa0 fffff800`02c83e54 : 00000000`00000000 00000000`00000000 fffffa80`0c6b5bc0 fffffa80`10086b20 : nt!PspThreadDelete+0xe3
fffff880`035e8ae0 fffff800`02c59c70 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff6fc`4001ead8 : nt!ObfDereferenceObject+0xd4
fffff880`035e8b40 fffff800`02c84261 : fffff800`02c59bc0 fffff800`02e20330 fffffa80`0c725660 00000000`00000000 : nt!PspReaper+0xb0
fffff880`035e8b70 fffff800`02f18bae : 00000000`00000000 fffffa80`0c725660 00000000`00000080 fffffa80`0c713040 : nt!ExpWorkerThread+0x111
fffff880`035e8c00 fffff800`02c6b8c6 : fffff880`03389180 fffffa80`0c725660 fffff880`033940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`035e8c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::NNGAKEGL::`string'+17dc6
fffff800`02fb5ad9 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::NNGAKEGL::`string'+17dc6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 51db806a
FAILURE_BUCKET_ID: X64_0x76_smss.exe_nt!_??_::NNGAKEGL::_string_+17dc6
BUCKET_ID: X64_0x76_smss.exe_nt!_??_::NNGAKEGL::_string_+17dc6
Followup: MachineOwner
---------