I get this BSOD at random times, sometimes it happen right away after waking the computer from sleep, and just last night I was probably on my machine for maube 2 hours and then it crashed with the BSOD 0xc00002a1. I am not sure what is causing. I looked at the dump file but I am not sure what I am suppose to be looking for to find the root problem. Any help would be appreciated.
PHP:
Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\073115-24968-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Machine Name:
Kernel base = 0xfffff801`0ca15000 PsLoadedModuleList = 0xfffff801`0ccee850
Debug session time: Fri Jul 31 22:39:40.842 2015 (UTC - 5:00)
System Uptime: 0 days 9:01:09.518
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C000021A, {ffffc0001c93d250, 0, 0, 0}
----- ETW minidump data unavailable-----
Probably caused by : ntkrnlmp.exe ( nt! ?? ::OKHAJAOM::`string'+269a )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: ffffc0001c93d250, String that identifies the problem.
Arg2: 0000000000000000, Error Code.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
----- ETW minidump data unavailable-----
ERROR_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x). The system has been shut down.
EXCEPTION_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x). The system has been shut down.
EXCEPTION_PARAMETER1: ffffc0001c93d250
EXCEPTION_PARAMETER2: 0000000000000000
EXCEPTION_PARAMETER3: 0000000000000000
EXCEPTION_PARAMETER4: 0
ADDITIONAL_DEBUG_TEXT: Windows must now restart because the DCOM Server Process Launcher service terminated unexpectedly
BUGCHECK_STR: 0xc000021a_DCOM_Terminated
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: services.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff8010cda0991 to fffff8010cb65ca0
STACK_TEXT:
ffffd000`326e36b8 fffff801`0cda0991 : 00000000`0000004c 00000000`c000021a ffffd000`31de33f8 ffffe000`21252160 : nt!KeBugCheckEx
ffffd000`326e36c0 fffff801`0cd9a4ea : ffffe000`23170d00 ffffd000`326e37d9 00000000`00000000 00000000`00000002 : nt!PopGracefulShutdown+0x2c9
ffffd000`326e3700 fffff801`0cb714b3 : ffffe000`23170880 fffff801`0cb52200 00000000`c0000004 fffff801`0cab9800 : nt! ?? ::OKHAJAOM::`string'+0x269a
ffffd000`326e3840 fffff801`0cb69900 : fffff801`0cfb0abb 00000000`00000001 ffffd000`326e3a58 00000000`c0000004 : nt!KiSystemServiceCopyEnd+0x13
ffffd000`326e39d8 fffff801`0cfb0abb : 00000000`00000001 ffffd000`326e3a58 00000000`c0000004 ffffd000`d17d4180 : nt!KiServiceLinkage
ffffd000`326e39e0 fffff801`0cee675f : 00000000`00000000 00000000`00000000 ffffd000`d17d4180 ffffe000`231709c0 : nt! ?? ::NNGAKEGL::`string'+0x70c0b
ffffd000`326e3aa0 fffff801`0caf1fba : fffff801`0caf1f00 00000000`00000000 00000000`00000002 fffff801`0ccc7340 : nt!PopPolicyWorkerAction+0x63
ffffd000`326e3b10 fffff801`0cac26bc : fffff801`00000002 fffff801`0ccd52a0 ffffe000`23170880 fffff801`0ccc7340 : nt!PopPolicyWorkerThread+0xba
ffffd000`326e3b50 fffff801`0cb1536c : 00000000`00000000 ffffe000`23170880 00000000`00000080 ffffe000`23170880 : nt!ExpWorkerThread+0x28c
ffffd000`326e3c00 fffff801`0cb6c2c6 : fffff801`0cd18180 ffffe000`23170880 ffffe000`1904e800 ffffe000`230dede8 : nt!PspSystemThreadStartup+0x58
ffffd000`326e3c60 00000000`00000000 : ffffd000`326e4000 ffffd000`326de000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::OKHAJAOM::`string'+269a
fffff801`0cd9a4ea cc int 3
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt! ?? ::OKHAJAOM::`string'+269a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 550f41a6
IMAGE_VERSION: 6.3.9600.17736
BUCKET_ID_FUNC_OFFSET: 269a
FAILURE_BUCKET_ID: 0xc000021a_DCOM_Terminated_nt!_??_::OKHAJAOM::_string_
BUCKET_ID: 0xc000021a_DCOM_Terminated_nt!_??_::OKHAJAOM::_string_
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xc000021a_dcom_terminated_nt!_??_::okhajaom::_string_
FAILURE_ID_HASH: {9ba00585-f32d-a134-4c58-327c0d8bed3f}
Followup: MachineOwner
---------
Facebook
Twitter