New
#1
Restoring at least once a week because of BSOD
So I keep getting the BSOD once a week now and when I do a system restore everything works fine for a while but then when I restart my laptop I am greeted with a blue screen. See my log below.
Windows 10 Version 22H2 (OS Build 19045.2364)
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\test\Desktop\010823-11156-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 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`83c00000 PsLoadedModuleList = 0xfffff803`8482a290
Debug session time: Sun Jan 8 16:47:49.415 2023 (UTC - 5:00)
System Uptime: 0 days 0:00:11.147
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`83ff92a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe600`4bb4d5a0=000000000000004c
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: ffffae800102a370, String that identifies the problem.
Arg2: ffffffffc0000428, Error Code.
Arg3: 0000000000000000
Arg4: 00000209e04c0000
Debugging Details:
------------------
ETW minidump data unavailable
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 10656
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 20731
Key : Analysis.IO.Other.Mb
Value: 10
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 30
Key : Analysis.Init.CPU.mSec
Value: 1577
Key : Analysis.Init.Elapsed.mSec
Value: 111303
Key : Analysis.Memory.CommitPeak.Mb
Value: 93
Key : Bugcheck.Code.DumpHeader
Value: 0xc000021a
Key : Bugcheck.Code.Register
Value: 0x4c
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: 010823-11156-01.dmp
ERROR_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x
EXCEPTION_CODE_STR: c000021a
EXCEPTION_PARAMETER1: ffffae800102a370
EXCEPTION_PARAMETER2: ffffffffc0000428
EXCEPTION_PARAMETER3: 0000000000000000
EXCEPTION_PARAMETER4: 209e04c0000
BUGCHECK_CODE: c000021a
BUGCHECK_P1: ffffae800102a370
BUGCHECK_P2: ffffffffc0000428
BUGCHECK_P3: 0
BUGCHECK_P4: 209e04c0000
PROCESS_NAME: smss.exe
ADDITIONAL_DEBUG_TEXT: initial session process or
IMAGE_NAME: ntkrnlmp.exe
MODULE_NAME: nt
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
CUSTOMER_CRASH_COUNT: 1
STACK_TEXT:
ffffe600`4bb4d598 fffff803`845b235a : 00000000`0000004c 00000000`c000021a ffffe600`4c1b63f0 ffffe70e`bf6e8e50 : nt!KeBugCheckEx
ffffe600`4bb4d5a0 fffff803`8459334d : ffffe600`4bb4d6c0 ffffe600`4bb4d660 ffffe600`4bb4d6c0 ffffe600`4bb4d660 : nt!PopGracefulShutdown+0x29a
ffffe600`4bb4d5e0 fffff803`84599ffc : 00000000`00000001 fffff803`00000006 00000000`00000005 00000000`00000000 : nt!PopTransitionSystemPowerStateEx+0x1249
ffffe600`4bb4d6a0 fffff803`8400caf8 : ffffe70e`00000001 fffff803`83ffde80 00000000`00000010 00000000`00000001 : nt!NtSetSystemPowerState+0x4c
ffffe600`4bb4d880 fffff803`83ffde80 : fffff803`84447a09 00000000`00000014 ffffffff`ffffff00 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
ffffe600`4bb4da18 fffff803`84447a09 : 00000000`00000014 ffffffff`ffffff00 00000000`00000000 fffff803`84823b40 : nt!KiServiceLinkage
ffffe600`4bb4da20 fffff803`8436c9c9 : 00000000`00000000 ffffe70e`bf2e2a60 00000000`00000000 00000000`00000000 : nt!PopIssueActionRequest+0xdaf21
ffffe600`4bb4dac0 fffff803`83f55794 : 00000000`00000001 00000000`00000000 ffffffff`ffffffff fffff803`84823b00 : nt!PopPolicyWorkerAction+0x79
ffffe600`4bb4db30 fffff803`83e52bc5 : ffffe70e`00000001 ffffe70e`bf4c6040 fffff803`83f55700 ffffe70e`00000000 : nt!PopPolicyWorkerThread+0x94
ffffe600`4bb4db70 fffff803`83e71d85 : ffffe70e`bf4c6040 00000000`00000080 ffffe70e`bf2a0040 00000000`00000000 : nt!ExpWorkerThread+0x105
ffffe600`4bb4dc10 fffff803`84001ed8 : ffffbf80`3ede3180 ffffe70e`bf4c6040 fffff803`83e71d30 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffe600`4bb4dc60 00000000`00000000 : ffffe600`4bb4e000 ffffe600`4bb48000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nt!PopTransitionSystemPowerStateEx+1249
IMAGE_VERSION: 10.0.19041.2364
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 1249
FAILURE_BUCKET_ID: 0xc000021a_SmpDestroyControlBlock_smss.exe_Terminated_c0000428_nt!PopTransitionSystemPowerStateEx
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {11c026a4-042b-4c24-02dc-2da456397475}
Followup: MachineOwner
---------
Quote