Given that even the Windows subsystem hasn't booted up yet, I'm almost certain this is a failing drive or other hardware failure.
ffffd000`23956638 fffff801`9a4a7dd0 nt!KeBugCheckEx
ffffd000`23956640 fffff801`9a3c779c nt!PspCatchCriticalBreak+0xa4
ffffd000`23956680 fffff801`9a232c11 nt!PspTerminateAllThreads+0xba4c
ffffd000`239566e0 fffff801`9a23299e nt!PspTerminateProcess+0xe5
ffffd000`23956720 fffff801`99fe79b3 nt!NtTerminateProcess+0x9e
ffffd000`23956790 fffff801`99fdfe00 nt!KiSystemServiceCopyEnd+0x13
ffffd000`23956928 fffff801`9a027b83 nt!KiServiceLinkage
ffffd000`23956930 fffff801`99f5bf04 nt!KiDispatchException+0x3b4d3
ffffd000`23957190 fffff801`99fdcadb nt!KiRaiseException+0x1a4
ffffd000`23957940 fffff801`99fe79b3 nt!NtRaiseException+0x7b
ffffd000`23957a80 00007ffe`bc8ad7fe nt!KiSystemServiceCopyEnd+0x13
00000026`13ddf330 00007ffe`bc903917 ntdll!RtlInitializeHistoryTable+0x66
00000026`13ddf360 00007ffe`bc8e34e8 ntdll!LdrpInitializeProcess+0x106f
00000026`13ddf680 00007ffe`bc85a65e ntdll!_LdrpInitialize+0x88e38
00000026`13ddf6f0 00000000`00000000 ntdll!LdrInitializeThunk+0xe
The Session Manager hasn't managed to create the Windows Subsystem (csrss.exe), or any user mode boot processes such as the Windows Initialization (wininit.exe).
01a8 smss.exe 33 ( 132 Kb)
0004 System 33 ( 132 Kb)
I won't go into detail as the boot process is quite detailed, but ntdll.dll expose the Native API system services that create native applications, until the Windows Subsystem is initialises to create Windows applications using the Win32 API.
Due the fact that the Session Manager hasn't done much work I'd say something has gone wrong with a piece of hardware that's caused it to terminate.
Without access to private symbols and information regarding the native system call services, which are mostly undocumented, it's very difficult to know what went wrong.
I would recommend testing your drive with SeaTools DOS, mount it to a CD or USB then boot into it and run the Long Generic Test on your C drive.
SeaTools for DOS | Seagate