I got this blue screen once while logging into my Windows account and another time while using Process Explorer. The Dump file for it happening while using Process Explorer ended up being too big so I deleted it after seeing the stack as identical to the other dump. This is the stack of the dump of when I was logging in:
Loading Kernel Symbols
...............................................................
.........................Page 2008f1 not present in the dump file. Type ".hh dbgerr004" for details
.......................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
...............
Unable to load image \SystemRoot\system32\DRIVERS\Ext2Fsd.sys, Win32 error 0n2
************* Symbol Loading Error Summary **************
Module name Error
Ext2Fsd The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
FILE_SYSTEM (22)
Arguments:
Arg1: 00000000000a0043
Arg2: ffffde061b2456b8
Arg3: ffffde061b244ef0
Arg4: fffff80554c9c465
Debugging Details:
------------------
Unable to load image \SystemRoot\System32\drivers\btrfs.sys, Win32 error 0n2
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1843
Key : Analysis.Elapsed.mSec
Value: 2126
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 781
Key : Analysis.Init.Elapsed.mSec
Value: 3343
Key : Analysis.Memory.CommitPeak.Mb
Value: 85
Key : Analysis.Version.DbgEng
Value: 10.0.29547.1002
Key : Analysis.Version.Description
Value: 10.2602.27.2 amd64fre
Key : Analysis.Version.Ext
Value: 1.2602.27.2
Key : Bugcheck.Code.KiBugCheckData
Value: 0x22
Key : Bugcheck.Code.LegacyAPI
Value: 0x22
Key : Bugcheck.Code.TargetModel
Value: 0x22
Key : Failure.Bucket
Value: 0x22_Ext2Fsd!unknown_function
Key : Failure.Hash
Value: {85d38ab9-6d9a-9147-b67b-1a96ab2bb758}
Key : Hypervisor.Enlightenments.Value
Value: 77057948
Key : Hypervisor.Enlightenments.ValueHex
Value: 0x497cf9c
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 1
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1
Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1
Key : Hypervisor.Flags.MaxBankNumber
Value: 0
Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1
Key : Hypervisor.Flags.Phase0InitDone
Value: 1
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 1
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 4853999
Key : Hypervisor.Flags.ValueHex
Value: 0x4a10ef
Key : Hypervisor.Flags.VpAssistPage
Value: 1
Key : Hypervisor.Flags.VsmAvailable
Value: 1
Key : Hypervisor.RootFlags.AccessStats
Value: 1
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 1
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1
Key : Hypervisor.RootFlags.MceEnlightened
Value: 1
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1
Key : Hypervisor.RootFlags.Value
Value: 1015
Key : Hypervisor.RootFlags.ValueHex
Value: 0x3f7
Key : SecureKernel.HalpHvciEnabled
Value: 0
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
Key : WER.System.BIOSRevision
Value: 5.17.0.0
BUGCHECK_CODE: 22
BUGCHECK_P1: a0043
BUGCHECK_P2: ffffde061b2456b8
BUGCHECK_P3: ffffde061b244ef0
BUGCHECK_P4: fffff80554c9c465
FILE_IN_CAB: MEMORY.DMP
FAULTING_THREAD: ffff968ebd38f040
PROCESS_NAME: System
TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000
Resetting default scope
STACK_TEXT:
ffffde06`1b244688 fffff805`db162ff3 : 00000000`00000022 00000000`000a0043 ffffde06`1b2456b8 ffffde06`1b244ef0 : nt!KeBugCheckEx
ffffde06`1b244690 fffff805`db17f84d : fffff805`db182b48 00000000`00000000 00000000`00000000 ffffde06`1b2447e0 : Ext2Fsd+0x2ff3
ffffde06`1b2446d0 fffff805`54dd03d2 : fffff805`00000003 fffff805`db2150d8 ffffde06`1b240000 ffffde06`1b246000 : Ext2Fsd+0x1f84d
ffffde06`1b244700 fffff805`54e08922 : fffff805`db2150d8 ffffde06`1b244ce0 fffff805`db17d3b6 00000000`00000000 : nt!_C_specific_handler+0xa2
ffffde06`1b244770 fffff805`54c757e7 : ffffde06`1b244ce0 00000000`00000000 ffffde06`1b245930 fffff805`db162b7c : nt!RtlpExecuteHandlerForException+0x12
ffffde06`1b2447a0 fffff805`54c73486 : ffffde06`1b2456b8 ffffde06`1b2453f0 ffffde06`1b2456b8 00000000`00000070 : nt!RtlDispatchException+0x297
ffffde06`1b244ec0 fffff805`54e126ec : 00000000`00001000 ffffde06`1b245760 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
ffffde06`1b245580 fffff805`54e0df52 : 00000000`00000000 ffff968e`00000001 ffff968e`b3ce0f34 ffff968e`00501802 : nt!KiExceptionDispatch+0x12c
ffffde06`1b245760 fffff805`54c9c465 : fffff805`db174fec 968ee141`03500000 00000000`00000080 00000000`00000000 : nt!KiPageFault+0x452
ffffde06`1b2458f8 fffff805`db174fec : 968ee141`03500000 00000000`00000080 00000000`00000000 00000000`00000000 : nt!IoIsOperationSynchronous+0x15
ffffde06`1b245900 fffff805`db162b7c : ffff968e`e1652040 ffff968e`e1652040 00000000`0056c001 00000000`00000001 : Ext2Fsd+0x14fec
ffffde06`1b245930 fffff805`54d51a05 : 00000000`00000000 00000000`0056c008 00000000`00000000 ffffde06`1b245a10 : Ext2Fsd+0x2b7c
ffffde06`1b245970 fffff805`7da6e981 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x55
ffffde06`1b2459b0 fffff805`7dac8585 : ffffc580`0e9e8101 00000000`00000000 ffffc580`0e9e81e0 fffff805`7dac6b20 : btrfs!dev_ioctl+0xa1
ffffde06`1b245a40 fffff805`7dac6b2f : 00000000`00000000 00000000`00000100 fffff805`7dac6b20 ffffc580`0e9e81e0 : btrfs!volume_arrival+0xb5
ffffde06`1b245ad0 fffff805`54cef175 : 00000000`00000000 ffff968e`da73c8a0 ffff968e`bd2ebc90 fffff805`656c5030 : btrfs!do_pnp_callback+0xf
ffffde06`1b245b00 fffff805`54c41f65 : ffff968e`bd38f040 ffff968e`bd38f040 fffff805`54cef040 ffff968e`00000000 : nt!IopProcessWorkItem+0x135
ffffde06`1b245b70 fffff805`54cec175 : ffff968e`bd38f040 00000000`00000080 ffff968e`b3ce10c0 000f8067`b8bbbdff : nt!ExpWorkerThread+0x105
ffffde06`1b245c10 fffff805`54e06de8 : ffffad00`38600180 ffff968e`bd38f040 fffff805`54cec120 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffde06`1b245c60 00000000`00000000 : ffffde06`1b246000 ffffde06`1b240000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: Ext2Fsd+2ff3
MODULE_NAME: Ext2Fsd
IMAGE_NAME: Ext2Fsd.sys
STACK_COMMAND: .process /r /p 0xffff968eb3ce10c0; .thread /r /p 0xffff968ebd38f040 ; kb
BUCKET_ID_FUNC_OFFSET: 2ff3
FAILURE_BUCKET_ID: 0x22_Ext2Fsd!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {85d38ab9-6d9a-9147-b67b-1a96ab2bb758}
Followup: MachineOwner
---------
I don't have access to the symbols of this driver so I don't know where the relevant code of Ext2Fsd is.
I got this blue screen once while logging into my Windows account and another time while using Process Explorer. The Dump file for it happening while using Process Explorer ended up being too big so I deleted it after seeing the stack as identical to the other dump. This is the stack of the dump of when I was logging in:
I don't have access to the symbols of this driver so I don't know where the relevant code of Ext2Fsd is.