0xc000021a, after/while update reboot

Hello,
I have now for a while a problem:
after an update you need to reboot and my notebook booted in a BSOD.
If there isn't any updates to install, he is booting normally, without any issues.
I had this problem beginning on Win 10, after a clean (I formatted even all partitions) reinstall the issue was still there. I tried now Win 7 and it got a bit better, bc I needed on Win 10 more than 10 minutes to start it, after a BSOD and I got on Win 10 some more BSOD: pcw.sys and critical process died, but they didn't occurred on Win 7. I got no minidump files on Win 10, and I could only start Win 10 with disable driver signature enforcement.
On Win 7 I got some minidump files
The issue occurred on a HDD with Win 10 in mine notebook as well.
I installed all drivers and all windows updates now I'm checking the drivers with the verifier.
sfc /scannow never helped and chkdsk /f as well.
Edit: I'ts a L540 20AU and the BIOS is up to date.
I hope someone can help me.

Hi Shellingf,

Welcome to 7Forums :)

Rdvgkmd.sys is not crucial.

I noticed you ran driver verifier, unfortunately it didn't find any driver.

Code:

2: kd> !verifier

Verify Flags Level 0x00000dbb

  STANDARD FLAGS:
    [X] (0x00000000) Automatic Checks
    [X] (0x00000001) Special pool
    [X] (0x00000002) Force IRQL checking
    [X] (0x00000008) Pool tracking
    [X] (0x00000010) I/O verification
    [X] (0x00000020) Deadlock detection
    [X] (0x00000080) DMA checking
    [X] (0x00000100) Security checks
    [X] (0x00000800) Miscellaneous checks

  ADDITIONAL FLAGS:
    [ ] (0x00000004) Randomized low resources simulation
    [ ] (0x00000200) Force pending I/O requests
    [X] (0x00000400) IRP logging

    [X] Indicates flag is enabled


Summary of All Verifier Statistics

  RaiseIrqls           0x0
  AcquireSpinLocks     0x4ac
  Synch Executions     0x4a
  Trims                0x18b0

  Pool Allocations Attempted             0x661d
  Pool Allocations Succeeded             0x661d
  Pool Allocations Succeeded SpecialPool 0x661d
  Pool Allocations With NO TAG           0x0
  Pool Allocations Failed                0x0

  Current paged pool allocations         0x14 for 00045730 bytes
  Peak paged pool allocations            0x16 for 00046740 bytes
  Current nonpaged pool allocations      0x11ad for 00C3AA3C bytes
  Peak nonpaged pool allocations         0x11af for 014A1A4C bytes

I also noticed there are different memory modules used, did you seat either of them?

Code:

[Memory Device (Type 17) - Length 34 - Handle 0006h]
  Physical Memory Array Handle  0005h
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          8192MB
  Form Factor                   0dh - SODIMM
  Device Set                    [None]
  Device Locator                ChannelA-DIMM0
  Bank Locator                  BANK 0
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1600MHz
  Manufacturer                  1315
  Serial Number                         
  Asset Tag Number                        
  Part Number                   CT102464BF160B.C16
[Memory Device (Type 17) - Length 34 - Handle 0007h]
  Physical Memory Array Handle  0005h
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          8192MB
  Form Factor                   0dh - SODIMM
  Device Set                    [None]
  Device Locator                ChannelB-DIMM0
  Bank Locator                  BANK 2
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1600MHz
  Manufacturer                  Micron
  Serial Number                         
  Asset Tag Number                        
  Part Number                   16KTS1G64HZ-1G6E1

It seems the system crashed because smss (System Manager SubSystem) couldn't do its job.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: fffff8a000e9b700, String that identifies the problem.
Arg2: 0000000000000000, Error Code.
Arg3: ffffffffc0000001
Arg4: 00000000000107a8


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.

2: kd> !error ffffffff`c0000001
Error code: (NTSTATUS) 0xc0000001 (3221225473) - {Operation Failed}  The requested operation was unsuccessful.


2: kd> !da fffffa8012252e80
The initial session process or system process terminated unexpectedly with a status of 0x00000000 (0xc0000001 0x000107a8).
The system has been shut down.

Smss plays an important role in booting your system, if it is being blocked or modified by anything it will close itself and Windows will crash with a 0x21A.
Smss closing itself is very often the result of bad RAM or problems with the hard drive. Please run the following tests in the order posted.

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

Diagnostics Test

 HDD TEST

   Note

Please run HDTune first, in the order posted!

Run HDTune to

• check the health,
• scan for errors, no quick scan but full scan
• run a benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the health,
• the error scan,
• the benchmark incl. following
  
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run the long test.

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Make a photo of the result and post it.

Run chkdsk
Disk Check - Windows 7 Help Forums
Use option TWO with parameter /r
Upload the chkdsk log Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums