Since a few weeks are we getting BSOD when the Windows server restarts, it gives the error 0xC000021a.
after diggin into the problem im kinda sure its a faulty driver but have no idea how to fix this.
At the moment the server runs in a state after the option "Disable driver signature enforcement" when pressing F7.
our server: Dell Poweredge R630
install OS: Windows server Standard 2016
Its a physical server and not a VM.
- i ran all the windows updates on the server
- updated driver pack from V16 to V18
- Disabling all non-microsoft services from MSconfig.exe
- Tried to run SFC /scannow and DISM tools but gives error.
This is the outcome of the minidump, hope someone can send me to the right direction.
Microsoft (R) Windows Debugger Version 10.0.22000.194 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [\\dc01\c$\Windows\Minidump\021922-37421-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (16 procs) Free x64
Product: LanManNt, suite: TerminalServer SingleUserTS
Edition build lab: 14393.0.amd64fre.rs1_release.160715-1616
Machine Name:
Kernel base = 0xfffff802`22876000 PsLoadedModuleList = 0xfffff802`22b7b060
Debug session time: Sat Feb 19 13:42:28.982 2022 (UTC + 1:00)
System Uptime: 0 days 0:00:29.798
Loading Kernel Symbols
...............................................................
.......................................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
8: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: ffffc805aec733f0, String that identifies the problem.
Arg2: ffffffffc0000428, Error Code.
Arg3: 0000000000000000
Arg4: 00000206548c0000
Debugging Details:
------------------
ETW minidump data unavailable
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1687
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 4343
Key : Analysis.Init.CPU.mSec
Value: 1655
Key : Analysis.Init.Elapsed.mSec
Value: 18909
Key : Analysis.Memory.CommitPeak.Mb
Value: 88
Key : WER.OS.Branch
Value: rs1_release
Key : WER.OS.Timestamp
Value: 2016-07-15T16:16:00Z
Key : WER.OS.Version
Value: 10.0.14393.0
ERROR_CODE: (NTSTATUS) 0xc000021a - {Onherstelbare systeemfout} Het systeemproces %hs is onverwacht afgebroken met de status: 0x
EXCEPTION_CODE_STR: c000021a
EXCEPTION_PARAMETER1: ffffc805aec733f0
EXCEPTION_PARAMETER2: ffffffffc0000428
EXCEPTION_PARAMETER3: 0000000000000000
EXCEPTION_PARAMETER4: 206548c0000
BUGCHECK_CODE: c000021a
BUGCHECK_P1: ffffc805aec733f0
BUGCHECK_P2: ffffffffc0000428
BUGCHECK_P3: 0
BUGCHECK_P4: 206548c0000
PROCESS_NAME: smss.exe
ADDITIONAL_DEBUG_TEXT: initial session process or
IMAGE_NAME: ntkrnlmp.exe
MODULE_NAME: nt
CUSTOMER_CRASH_COUNT: 1
STACK_TEXT:
ffffb481`e47d46b8 fffff802`22c51380 : 00000000`0000004c 00000000`c000021a ffffb481`e5e293f8 ffffd986`4246c810 : nt!KeBugCheckEx
ffffb481`e47d46c0 fffff802`22c49fe8 : ffffffff`80000454 00000000`00000002 ffffb481`e47d4800 00000000`00000002 : nt!PopGracefulShutdown+0x268
ffffb481`e47d4700 fffff802`229cac93 : ffff9b7c`00000004 00000000`00000001 00000000`c0000004 ffffb481`e47d4900 : nt! ?? ::OKHAJAOM::`string'+0xeb8
ffffb481`e47d4880 fffff802`229c3150 : fffff802`22e591e2 00000000`00000000 ffffb481`e47d4a98 00000000`00000014 : nt!KiSystemServiceCopyEnd+0x13
ffffb481`e47d4a18 fffff802`22e591e2 : 00000000`00000000 ffffb481`e47d4a98 00000000`00000014 00000000`00000000 : nt!KiServiceLinkage
ffffb481`e47d4a20 fffff802`22d8bc1d : 00000000`00000000 00000000`00000000 00000000`00000000 fffff802`22c33280 : nt! ?? ::NNGAKEGL::`string'+0x6bf92
ffffb481`e47d4ae0 fffff802`2292d289 : 00000000`00000001 fffff802`2292d21c 00000000`00000002 00000000`00000000 : nt!PopPolicyWorkerAction+0x69
ffffb481`e47d4b50 fffff802`228cdd79 : ffffd986`3f3ed040 fffff802`22b77b20 fffff802`00000000 fffff802`00000019 : nt!PopPolicyWorkerThread+0x6d
ffffb481`e47d4b80 fffff802`229124bd : 00000000`00000000 00000000`00000080 ffffd986`3f26c700 ffffd986`3f3ed040 : nt!ExpWorkerThread+0xe9
ffffb481`e47d4c10 fffff802`229c5456 : ffffb481`e43c0180 ffffd986`3f3ed040 fffff802`2291247c 00000000`00000000 : nt!PspSystemThreadStartup+0x41
ffffb481`e47d4c60 00000000`00000000 : ffffb481`e47d5000 ffffb481`e47cf000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_NAME: nt! ?? ::OKHAJAOM::`string'+eb8
IMAGE_VERSION: 10.0.14393.0
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: eb8
FAILURE_BUCKET_ID: 0xc000021a_SmpDestroyControlBlock_smss.exe_Terminated_c0000428_VRF_nt!_??_::OKHAJAOM::_string_
OS_VERSION: 10.0.14393.0
BUILDLAB_STR: rs1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {72632f6c-5f7c-0cc2-138b-705fc17eb4c0}
Followup: MachineOwner
---------
