/Windows 10 BSOD 0xC000021A > Memory Corruption (via WindowsKernel.com)
Windows 10 BSOD 0xC000021A > Memory Corruption

Windows 10 BSOD 0xC000021A > Memory Corruption (via WindowsKernel.com)


Windows 10 BSOD 0xC000021A > Memory Corruption >> Looking for thoughts on the cause of this (Occurs at time of OS boot):

Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       http://msdl.microsoft.com/download/symbols
Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff803`31800000 PsLoadedModuleList = 0xfffff803`31c480b0
Debug session time: Wed Nov 13 10:26:56.759 2019 (UTC – 6:00)
System Uptime: 0 days 0:00:24.499
Loading Kernel Symbols
……………………..……….……….……….…….
……………………..……….……….……….……..
……………………..……….……….…..
Loading User Symbols
Loading unloaded module list
……..
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C000021A, {ffff9b80ed455520, ffffffffc0000428, 0, 29adff60000}

—– ETW minidump data unavailable—–
Probably caused by : memory_corruption

Followup: memory_corruption
———

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: ffff9b80ed455520, String that identifies the problem.
Arg2: ffffffffc0000428, Error Code.
Arg3: 0000000000000000
Arg4: 0000029adff60000

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:  ffff9b80ed455520

EXCEPTION_PARAMETER2:  ffffffffc0000428

EXCEPTION_PARAMETER3:  0000000000000000

EXCEPTION_PARAMETER4: 29adff60000

ADDITIONAL_DEBUG_TEXT:  initial session process or

BUGCHECK_STR:  0xc000021a_c0000428__HASH_INVALID

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  smss.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80331daeb0a to fffff803319c1410

STACK_TEXT:  
fffffc89`33d1d4a8 fffff803`31daeb0a : 00000000`0000004c 00000000`c000021a fffffc89`3437f2f8 ffffc486`53eea410 : nt!KeBugCheckEx
fffffc89`33d1d4b0 fffff803`31d99fad : 00000000`00000000 fffffc89`33d1d570 00000000`00000000 fffffc89`33d1d570 : nt!PopGracefulShutdown+0x29a
fffffc89`33d1d4f0 fffff803`31d9f14c : ffff9b80`e9fffb01 fffff803`00000006 00000000`00000004 ffff9b80`ed559030 : nt!PopTransitionSystemPowerStateEx+0x11f1
fffffc89`33d1d5b0 fffff803`319d2d15 : 00000000`00000000 fffff803`3184109b 00000000`00000010 00000000`00040086 : nt!NtSetSystemPowerState+0x4c
fffffc89`33d1d790 fffff803`319c5250 : fffff803`31f9c02d 00000000`c0000004 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
fffffc89`33d1d928 fffff803`31f9c02d : 00000000`c0000004 00000000`00000000 00000000`00000000 fffff803`31c45800 : nt!KiServiceLinkage
fffffc89`33d1d930 fffff803`31f21989 : ffffc486`3cbc4080 fffff803`318bd96c fffff803`356fe7e0 ffffc486`00000000 : nt!PopIssueActionRequest+0x7a581
fffffc89`33d1d9d0 fffff803`3192890f : 00000000`00000001 00000000`00000002 00000000`00000000 fffff803`31c45800 : nt!PopPolicyWorkerAction+0x79
fffffc89`33d1da40 fffff803`318bd4b5 : ffffc486`00000001 ffffc486`3cbc4080 fffff803`31928880 ffffc486`39693940 : nt!PopPolicyWorkerThread+0x8f
fffffc89`33d1da70 fffff803`3192a7a5 : ffffc486`3cbc4080 00000000`00000080 ffffc486`396c2080 000025ef`bd9bbfff : nt!ExpWorkerThread+0x105
fffffc89`33d1db10 fffff803`319c8a5a : ffffb280`f6bce180 ffffc486`3cbc4080 fffff803`3192a750 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffffc89`33d1db60 00000000`00000000 : fffffc89`33d1e000 fffffc89`33d17000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a

STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80331de3ce8-fffff80331de3ce9  2 bytes – nt!PfpPfnPrioRequest+a8
      [ 80 fa:00 94 ]
2 errors : !nt (fffff80331de3ce8-fffff80331de3ce9)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup: memory_corruption
———

This is a syndicated post. Read the original post at Source link .