通过

玩永劫会闪退，日志找不出原因，求解决

匿名
2024-11-12T17:30:22+00:00

************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.032 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 42

Microsoft (R) Windows Debugger Version 10.0.27725.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\32084\Desktop\111224-7796-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 22621 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff806`71000000 PsLoadedModuleList = 0xfffff806`71c13510
Debug session time: Tue Nov 12 22:43:16.756 2024 (UTC + 8:00)
System Uptime: 0 days 0:39:45.403
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`002ee018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`71415df0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffcf0b`6e80e440=0000000000000050
11: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffaf3a2a9ed590, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the processor decided the fault was due to a corrupted PTE.
bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff80673e909ce, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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

*** WARNING: Check Image - Checksum mismatch - Dump: 0x32e793, File: 0x33218e - C:\ProgramData\Dbg\sym\Ntfs.sys\6D17756A333000\Ntfs.sys

KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 781

    Key  : Analysis.Elapsed.mSec
    Value: 1590

    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: 78

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Bugcheck.Code.TargetModel
    Value: 0x50

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_R_(null)_Ntfs!NtfsFindPrefixHashEntry

    Key  : Failure.Hash
    Value: {a39cef8c-a660-06bd-6b36-7c7d87cba5d9}

BUGCHECK_CODE:  50

BUGCHECK_P1: ffffaf3a2a9ed590

BUGCHECK_P2: 0

BUGCHECK_P3: fffff80673e909ce

BUGCHECK_P4: 2

FILE_IN_CAB:  111224-7796-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff928ad42dd080

READ_ADDRESS: fffff80671d1c4a8: 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
 ffffaf3a2a9ed590 

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  NarakaBladepoi

TRAP_FRAME:  ffffcf0b6e80e660 -- (.trap 0xffffcf0b6e80e660)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=000000000000014e
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80673e909ce rsp=ffffcf0b6e80e7f0 rbp=ffff928acecb0cb0
 r8=000000000ba2c94e  r9=ffffcf0b6e80e750 r10=fffff80671342620
r11=ffffcf0b6e80e918 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
Ntfs!NtfsFindPrefixHashEntry+0x1de:
fffff806`73e909ce 44394310        cmp     dword ptr [rbx+10h],r8d ds:00000000`00000010=????????
Resetting default scope

STACK_TEXT:  
ffffcf0b`6e80e438 fffff806`714dd2da     : 00000000`00000050 ffffaf3a`2a9ed590 00000000`00000000 ffffcf0b`6e80e660 : nt!KeBugCheckEx
ffffcf0b`6e80e440 fffff806`71347efc     : 00000000`00000001 00000000`00000000 00000000`00000000 ffffaf3a`2a9ed590 : nt!MiSystemFault+0x1bc19a
ffffcf0b`6e80e540 fffff806`7142707e     : ffff928a`d81c1010 00000000`00000000 ffffaf02`20052170 00000001`00000000 : nt!MmAccessFault+0x29c
ffffcf0b`6e80e660 fffff806`73e909ce     : ffff928a`cecb0cb0 00000000`00000001 00000000`00000000 ffffe681`cbf54180 : nt!KiPageFault+0x37e
ffffcf0b`6e80e7f0 fffff806`73e92236     : ffffcf0b`6e80ee00 ffff928a`cece4540 ffffaf02`20052170 00000000`00000001 : Ntfs!NtfsFindPrefixHashEntry+0x1de
ffffcf0b`6e80e920 fffff806`73e93c4d     : ffffcf0b`6e80ee00 ffff928a`d3a8c320 ffffcf0b`6e80ed10 ffffcf0b`6e80ebd0 : Ntfs!NtfsFindStartingNode+0x886
ffffcf0b`6e80e9f0 fffff806`73eb4ca8     : ffffcf0b`6e80ee00 ffffcf0b`6e80ed56 ffffcf0b`6e80edc8 ffff928a`cece3001 : Ntfs!NtfsCommonCreate+0x11fd
ffffcf0b`6e80ecb0 fffff806`73eb4b2c     : 00000000`00000000 00000000`00000000 00000000`00000030 ffff928a`cdb987e0 : Ntfs!NtfsCommonQueryOpen+0x168
ffffcf0b`6e80f0d0 fffff806`7312aba6     : ffffcf0b`6e80f910 00000000`00000000 ffffcf0b`6e80f1a8 ffff928a`00000038 : Ntfs!NtfsNetworkOpenCreate+0x1c
ffffcf0b`6e80f100 fffff806`73127a3e     : ffffcf0b`6e80f210 ffffcf0b`6e80f1a8 ffff928a`d17abb20 ffff928a`d17abc20 : FLTMGR!FltpPerformFastIoCall+0xe6
ffffcf0b`6e80f160 fffff806`73162906     : ffffcf0b`6e810000 ffffcf0b`6e809000 00000000`00000000 ffff0000`301b1001 : FLTMGR!FltpPassThroughFastIo+0x10e
ffffcf0b`6e80f1e0 fffff806`717045fe     : 00000000`cdd10000 00000000`00000000 ffffcf0b`6e80f520 00000000`00000000 : FLTMGR!FltpFastIoQueryOpen+0x126
ffffcf0b`6e80f280 fffff806`717bb219     : ffff928a`00000000 ffff928a`cdd148f0 ffff928a`d3a8c320 ffffcf0b`6e80f910 : nt!IopQueryInformation+0x18e
ffffcf0b`6e80f2e0 fffff806`717ecc11     : ffffcf0b`6e80f6d8 ffffaf02`1d07a9b8 ffffcf0b`6e80f5d0 ffffcf0b`6e80f6d0 : nt!IopParseDevice+0xc39
ffffcf0b`6e80f4b0 fffff806`717ebee2     : ffff928a`d3eb1701 ffffcf0b`6e80f6d0 00000000`00000040 ffff928a`c2bfa6c0 : nt!ObpLookupObjectName+0x7e1
ffffcf0b`6e80f640 fffff806`716a2f9e     : 00000000`00000000 00000002`5cdef460 00000000`00000001 00000002`5cdef430 : nt!ObOpenObjectByNameEx+0x1f2
ffffcf0b`6e80f770 fffff806`7142b405     : ffff928a`d42d0000 ffff928a`d095bb60 ffff928a`d42dd080 00000011`80cd6800 : nt!NtQueryFullAttributesFile+0x1ce
ffffcf0b`6e80fa20 00007ffb`4d5d2974     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000002`5cdef3d8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`4d5d2974

SYMBOL_NAME:  Ntfs!NtfsFindPrefixHashEntry+1de

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

IMAGE_VERSION:  10.0.22621.3930

STACK_COMMAND:  .process /r /p 0xffff928ad3d020c0; .thread 0xffff928ad42dd080 ; kb

BUCKET_ID_FUNC_OFFSET:  1de

FAILURE_BUCKET_ID:  AV_R_(null)_Ntfs!NtfsFindPrefixHashEntry

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a39cef8c-a660-06bd-6b36-7c7d87cba5d9}

Followup:     MachineOwner
---------

锁定的问题。 此问题已从 Microsoft 支持社区迁移。 你可投票决定它是否有用，但不能添加评论或回复，也不能关注问题。 为了保护隐私，对于已迁移的问题，用户个人资料是匿名的。

0 个注释
接受的答案
  1. 匿名
    2024-11-13T07:38:01+00:00

    此响应已自动翻译。 因此，可能存在语法错误或奇异的措辞。

    您好 先清 谢，

    感谢您在本论坛发帖。

    游戏闪退可能是因为多个原因导致的。根据你提供的信息，错误指示存在一个无效的系统内存被引用，这可能是由于硬件问题、驱动程序问题或者软件冲突导致的。以下是一些常见的解决方法：

    1. 检查和更新驱动程序（尤其是显卡驱动程序）：请访问显卡制造商的网站，下载并安装最新版本的驱动程序。

    2.打开命令提示符（管理员模式），运行以下命令：

    sfc /scannow

    这将扫描并修复系统文件中的问题。

    1. 检查硬件状况：使用Windows内存诊断工具来检查内存是否有问题，使用硬盘诊断工具（如chkdsk）来检查硬盘是否存在错误。
    2. 禁用不必要的启动项和服务：
    • 打开任务管理器，转到“启动”选项卡，禁用不必要的启动项。
    • 打开“运行”（Win+R），输入'msconfig'，在“服务”选项卡中选择“隐藏所有Microsoft服务”，然后禁用不必要的第三方服务。
    1. 有时，某些后台运行的应用程序可能会与游戏发生冲突。尝试关闭其他不必要的软件，尤其是那些与系统底层交互较多的软件，如杀毒软件、VPN等。
    2. 尝试卸载游戏并重新安装，同时确保安装所有必需的组件（如DirectX、Visual C++ Redistributable等）。
    3. 确保你的Windows系统是最新的，安装所有的更新补丁。

    希望对你有所帮助。

    诚挚的问候，

    蕾

    0 个注释

0 个其他答案

排序依据： 非常有帮助
非常有帮助 最新 最早