求大佬指导一下，蓝屏 dump 文件是什么问题？

dump 文件的结果，看不懂，请问大佬们是硬件还是软件原因，怎么解决呢？

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000099, Attempt to free pool with invalid address (or corruption in pool header)
Arg2: ffffe689935a2f34, Address being freed
Arg3: 0000000000000000, 0
Arg4: 0000000000000000, 0

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1874

Key : Analysis.Elapsed.mSec
Value: 14683

Key : Analysis.IO.Other.Mb
Value: 15

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 31

Key : Analysis.Init.CPU.mSec
Value: 109

Key : Analysis.Init.Elapsed.mSec
Value: 36574

Key : Analysis.Memory.CommitPeak.Mb
Value: 100

Key : Bugcheck.Code.LegacyAPI
Value: 0xc2

Key : Dump.Attributes.AsUlong
Value: 8

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Failure.Bucket
Value: 0xc2_99_nt!ExFreeToNPagedLookasideList

Key : Failure.Hash
Value: {3d385702-d56e-9abd-dc80-91fc25783fcf}


BUGCHECK_CODE: c2

BUGCHECK_P1: 99

BUGCHECK_P2: ffffe689935a2f34

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB: 011824-6906-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffcb82`c4e97128 fffff804`5cead096 : 00000000`000000c2 00000000`00000099 ffffe689`935a2f34 00000000`00000000 : nt!KeBugCheckEx
ffffcb82`c4e97130 fffff804`5c67a1ea : ffff8004`cb9831b0 ffffcb82`c4e97690 00000000`00002bf3 ffffcb82`c4e972c0 : nt!ExFreePool+0x3d6
ffffcb82`c4e97170 fffff804`5c70cc40 : fffff804`600569c0 ffff8004`cb9831b0 00000000`00000000 00000000`00000000 : nt!ExFreeToNPagedLookasideList+0x2a
ffffcb82`c4e971a0 fffff804`5ffd7b60 : ffffe689`93e55980 00000000`00000000 ffff8004`cb984ee8 ffffe689`85c99920 : nt!FsRtlUninitializeBaseMcb+0x20
ffffcb82`c4e971d0 fffff804`6010cf2d : ffffcb82`c4e97308 ffffcb82`c4e97690 00000000`00000705 ffffe689`92ea8460 : Ntfs!NtfsUninitializeNtfsMcb+0xf0
ffffcb82`c4e97200 fffff804`6010c4c1 : ffffe689`93e556e0 ffffe689`00000000 ffffe601`01000000 00001f80`93a2f700 : Ntfs!NtfsDeleteScb+0xbd
ffffcb82`c4e972a0 fffff804`5ffd730d : ffffe689`93e55800 ffffe689`93e55800 ffffe689`93e556a0 ffffe689`93e55800 : Ntfs!NtfsRemoveScb+0xad
ffffcb82`c4e97300 fffff804`6010c210 : ffffe689`93e556a0 00000000`00000000 ffffcb82`c4e97690 ffffe689`93e55800 : Ntfs!NtfsPrepareFcbForRemoval+0x5d
ffffcb82`c4e97340 fffff804`5ffd7012 : ffffcb82`c4e97690 ffff8004`cb9831b0 ffffe689`93e55b00 ffffe689`93e556a0 : Ntfs!NtfsTeardownStructures+0xa0
ffffcb82`c4e973c0 fffff804`6010b903 : ffffcb82`c4e97588 ffffcb82`c4e97a40 ffffcb82`c4e97588 ffffe689`93e55600 : Ntfs!NtfsDecrementCloseCounts+0xe2
ffffcb82`c4e97420 fffff804`6010b302 : ffffcb82`c4e97690 ffffe689`93e55800 ffffe689`93e556a0 ffff8004`cb9831b0 : Ntfs!NtfsCommonClose+0x423
ffffcb82`c4e974f0 fffff804`600e5cf8 : ffffa340`b4f01600 ffff8004`cb9831b0 ffffcb82`c4e97a40 ffff8004`c56b3ab0 : Ntfs!NtfsFspCloseInternal+0x252
ffffcb82`c4e97650 fffff804`5c634f85 : ffff8004`c56b3ab0 ffff8004`c56b3a00 fffff804`00000000 ffffffff`00000000 : Ntfs!NtfsFspClose+0x88
ffffcb82`c4e97940 fffff804`5c707167 : ffff8004`d4cce040 00000000`000001be ffff8004`d4cce040 fffff804`5c634e30 : nt!ExpWorkerThread+0x155
ffffcb82`c4e97b30 fffff804`5c81bb94 : ffffd100`ea611180 ffff8004`d4cce040 fffff804`5c707110 00000000`00000246 : nt!PspSystemThreadStartup+0x57
ffffcb82`c4e97b80 00000000`00000000 : ffffcb82`c4e98000 ffffcb82`c4e91000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME: nt!ExFreeToNPagedLookasideList+2a

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.3007

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 2a

FAILURE_BUCKET_ID: 0xc2_99_nt!ExFreeToNPagedLookasideList

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {3d385702-d56e-9abd-dc80-91fc25783fcf}

Followup: MachineOwner