dmp文件求助分析

我在玩永劫无间这款游戏时系统发生了频繁的重启问题，但我不了解dmp文件，无法分析出游戏奔溃的原因。我的设备在玩别的游戏比如荒野大镖客2时并没有出现系统崩溃的问题，我不确定这是不是电脑本身的问题导致永劫无间的崩溃。如果你能从百忙之中抽空帮助我分析dmp文件找到故障的真正原因，本人不胜感谢。我在截取代码后发现似乎只能上传一张图片，所以我会直接将代码文本复制在下边，再次感谢愿意伸出援手的你。Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\518\Desktop\080422-10343-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 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff802`44a00000 PsLoadedModuleList = 0xfffff802`4562a230
Debug session time: Thu Aug  4 22:33:37.929 2022 (UTC + 8:00)
System Uptime: 0 days 0:13:19.662
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:
fffff802`44df8590 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffcc81`1dfcd8f0=000000000000001e
2: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80244c3864c, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3264

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 17214

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x1e

    Key  : Bugcheck.Code.Register
    Value: 0x1e

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  080422-10343-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80244c3864c

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: fffff802456fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 ffffffffffffffff

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  NarakaBladepoi

TRAP_FRAME:  a009406c00000001 -- (.trap 0xa009406c00000001)
Unable to read trap frame at a009406c`00000001

STACK_TEXT: 
ffffcc81`1dfcd8e8 fffff802`44e35843     : 00000000`0000001e ffffffff`c0000005 fffff802`44c3864c 00000000`00000000 : nt!KeBugCheckEx
ffffcc81`1dfcd8f0 fffff802`44df9422     : 00000000`20014064 00000020`20024060 a009406c`00000001 54e24908`00000001 : nt!KiDispatchException+0x1df613
ffffcc81`1dfcdfb0 fffff802`44df93f0     : fffff802`44e0a6a5 fffff802`44df4680 fffff802`44d2397a 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffff8980`908f4478 fffff802`44e0a6a5     : fffff802`44df4680 fffff802`44d2397a 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
ffff8980`908f4480 fffff802`44e063e0     : ffffa78e`d5671180 00000000`00000000 00000000`00000122 ffffcc81`1dbd5440 : nt!KiExceptionDispatch+0x125
ffff8980`908f4660 fffff802`44c3864c     : 00000000`00000000 fffff802`44c37b7c 00000000`00000010 00000000`00050206 : nt!KiGeneralProtectionFault+0x320
ffff8980`908f47f0 00000000`00000001     : 00000000`00000000 00000000`0000001e ffffa78e`ea52f1c0 00000000`00000000 : nt!KiSelectReadyThread+0x8c
ffff8980`908f4880 00000000`00000000     : 00000000`0000001e ffffa78e`ea52f1c0 00000000`00000000 00000000`00000001 : 0x1


SYMBOL_NAME:  nt!KiSelectReadyThread+8c

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.1826

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  8c

FAILURE_BUCKET_ID:  AV_R_nt!KiSelectReadyThread

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {91cdf4f3-13d0-9338-532c-f253c43a0500}

Followup:     MachineOwner
---------欢迎咨询本站！。显示该游戏出现了异常。没有看到其他的驱动错误等。建议先升级到最新的系统，看下是否有好转。可以参考以下链接使用MediaCreationTool进行系统的无损修复/覆盖安装：（正常情况下文件、设置、应用等将保持原样，并将系统更新到最新的Windows10正式版。）https://answers.microsoft.com/zh-hans/windows/f.（相关视频教程：https://www.microsoft.com/en-us/videoplayer/emb.）
欢迎咨询本站！。显示该游戏出现了异常。没有看到其他的驱动错误等。建议先升级到最新的系统，看下是否有好转。可以参考以下链接使用MediaCreationTool进行系统的无损修复/覆盖安装：（正常情况下文件、设置、应用等将保持原样，并将系统更新到最新的Windows10正式版。）https://answers.microsoft.com/zh-hans/windows/f.（相关视频教程：https://www.microsoft.com/en-us/videoplayer/emb.）