if you are not sure of what drives you have, you can look in device manager under Disk drives, it should tell you there.
i got KERNEL_DATA_INPAGE_ERROR, this stopcode rarely happen. This is what i found on mini dump file
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\103020-23515-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
* Path validation summary
**
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800
23a00000 PsLoadedModuleList = 0xfffff800
23e48150
Debug session time: Fri Oct 30 02:15:43.415 2020 (UTC + 8:00)
System Uptime: 0 days 2:32:25.137
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800
23bc14e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff680
1eef4450=000000000000007a
5: kd> !analyze -v
***
***
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: ffff8f05e6d520e0, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2874
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-BI74IFM
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 3004
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 7a
BUGCHECK_P1: 20
BUGCHECK_P2: ffffffffc000000e
BUGCHECK_P3: ffff8f05e6d520e0
BUGCHECK_P4: 0
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
DISK_HARDWARE_ERROR: There was error with disk hardware
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff680
1eef4448 fffff800
23c15485 : 00000000
0000007a 00000000
00000020 ffffffff
c000000e ffff8f05
e6d520e0 : nt!KeBugCheckEx
fffff680
1eef4450 fffff800
23b323fb : 00000000
00000000 00000000
c000000e 00000000
00000000 00000000
00100000 : nt!MiWriteComplete+0x18ffb5
fffff680
1eef4500 fffff800
23a3e26d : ffff8f05
e6d36080 ffff8f05
ee87b088 00000000
00000000 00000000
00000000 : nt!IopCompletePageWrite+0x4b
fffff680
1eef4530 fffff800
23a48c32 : 00000000
00000000 00000000
00000000 ffff8f05
00000000 00000000
00000000 : nt!KiDeliverApc+0x19d
fffff680
1eef45f0 fffff800
23aa555d : ffffd001
1d29e180 ffff8f05
00000191 ffffd001
1d29e101 00000000
00000000 : nt!KiExitDispatcher+0x282
fffff680
1eef4650 fffff800
23a4848f : fffff680
1eef4700 ffff8f05
ee87b010 ffff8f05
e507f801 ffff8f05
00000001 : nt!KeInsertQueueApc+0x14d
fffff680
1eef46f0 fffff800
23a476a7 : 00000000
00000000 ffff8f05
e1f2b801 ffff8f05
e50f3010 ffff8f05
e51d8180 : nt!IopfCompleteRequest+0xdcf
fffff680
1eef4800 fffff800
26a932ec : ffff8f05
e1f17a40 fffff680
1eef4959 ffff8f05
e1f178f0 00000000
00000000 : nt!IofCompleteRequest+0x17
fffff680
1eef4830 fffff800
23a31f79 : fffff680
1eef4959 fffff800
27631d78 ffff8f05
ee87b010 ffff8f05
e6d36080 : volmgr!VmReadWrite+0x22dc
fffff680
1eef4870 fffff800
276239f0 : ffff8f05
e51d8180 fffff680
1eef4959 ffff8f05
ee87b010 fffff680
1eef48f0 : nt!IofCallDriver+0x59
fffff680
1eef48b0 fffff800
2762305c : 00000201
00000000 00100000
00000000 00380000
00000000 ffff8f05
e51d8180 : fvevol!FveFilterRundownReadWrite+0x920
fffff680
1eef49c0 fffff800
23a31f79 : 0065006c
0067006f 00640070
0055005c 005c0065
00740061 00650069
006c0043 : fvevol!FveFilterRundownWrite+0x4c
fffff680
1eef4a60 fffff800
277e3ca3 : 00000000
00000000 ffff8f05
e1e2da20 00000000
00000100 00000000
00000000 : nt!IofCallDriver+0x59
fffff680
1eef4aa0 fffff800
277e4f2d : 00000000
00000002 fffff680
1eef4be0 00000000
00000000 00844cb8
00855100 : iorate!IoRateIssueAndRecordIo+0x7f
fffff680
1eef4ae0 fffff800
277e5120 : 00000000
00000000 00000000
000a6045 00000000
00000000 00000000
00000000 : iorate!IoRateProcessIrpWrapper+0x19d
fffff680
1eef4c20 fffff800
23a31f79 : ffffe970
c6fe8325 00000000
00000000 ffff8f05
e50a7a40 ffff8f05
ee87b010 : iorate!IoRateDispatchReadWrite+0x80
fffff680
1eef4c60 fffff800
277612d5 : 00000000
00000000 00000000
00006021 fffff680
1eef4d19 00000000
00000100 : nt!IofCallDriver+0x59
fffff680
1eef4ca0 fffff800
27761099 : 00000043
0083b498 ffffffff
ffffffff 00000000
00000000 ffff8f05
e50a7a40 : rdyboost!SmdProcessReadWrite+0x1f5
fffff680
1eef4d80 fffff800
23a31f79 : 00000003
33abc000 ffff8f05
e51da190 ffff8f05
e51da1a8 0008e89f
11c91ceb : rdyboost!SmdDispatchReadWrite+0x89
fffff680
1eef4db0 fffff800
276e1033 : ffff8f05
e50994e0 fffff800
276f4340 000004d2
00000000 fffff800
2773ac04 : nt!IofCallDriver+0x59
fffff680
1eef4df0 fffff800
23a31f79 : ffff8f05
e51da190 fffff800
2770e294 00000000
00000000 ffff8f05
ee87b368 : volume!VolumePassThrough+0x23
fffff680
1eef4e20 fffff800
276f127d : 00000003
33abc000 ffff8f05
e51da190 ffff8f05
e51da1a8 00000000
00000000 : nt!IofCallDriver+0x59
fffff680
1eef4e60 fffff800
276f1143 : 00000000
00000000 00869148
00000000 fffff680
1c461300 0800bc6a
80bce79c : volsnap!VolsnapWriteFilter+0x11d
fffff680
1eef4ee0 fffff800
23a31f79 : 00000000
00000000 00000000
00000001 00000000
00000000 00000000
00000000 : volsnap!VolSnapWrite+0x13
fffff680
1eef4f10 fffff800
26d4327c : 00000000
00000000 00000000
00000000 00000000
00000000 00000043
00000000 : nt!IofCallDriver+0x59
fffff680
1eef4f50 fffff800
23bc4dae : 00000000
00000000 00000000
00000000 00000000
00000000 00000000
00000000 : Ntfs!NtfsStorageDriverCallout+0x1c
fffff680
1eef4f80 fffff800
23bc4d6c : 00000000
00000000 00000000
00000000 00000000
00000000 00000000
00000000 : nt!KxSwitchKernelStackCallout+0x2e
fffff680
1c4612a0 00000000
00000000 : 00000000
00000000 00000000
00000000 00000000
00000000 00000000
00000000 : nt!KiSwitchKernelStackContinue
SYMBOL_NAME: volmgr!VmReadWrite+22dc
MODULE_NAME: volmgr
IMAGE_NAME: volmgr.sys
IMAGE_VERSION: 10.0.18362.592
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 22dc
FAILURE_BUCKET_ID: 0x7a_c000000e_volmgr!VmReadWrite
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {926fffaa-ca3b-a1ec-ad21-fa8bab592dfc}
Followup: MachineOwner
---------
5: kd> !blackboxbsd
Stream size mismatch (expected = 192, read = 168)