我的电脑在升级到build 29500之后的版本之后，启动PUBG后就会蓝屏然后重启

Question

我的电脑在升级到build 29500之后的版本之后，启动PUBG后就会蓝屏然后重启

慕琴居士 20

这是dmp文件的分析结果。看起来像是navagio.sys在执行的时候出现了问题

居士ExtensionGallery settings after reading 'SOFTWARE\Microsoft\Debug Engine' registry:

ExtensionGallery ExtensionRepository: Implicit

************* Path validation summary **************

Response Time (ms) Location

Deferred srv*

************* Path validation summary **************

Response Time (ms) Location

Deferred srv*

************* Preparing the environment for Debugger Extensions Gallery repositories **************

ExtensionRepository : Implicit

UseExperimentalFeatureForNugetShare : true

AllowNugetExeUpdate : true

NonInteractiveNuget : true

AllowNugetMSCredentialProviderInstall : true

AllowParallelInitializationOfLocalRepositories : true

-- 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.031 seconds

----> Repository : UserExtensions, Enabled: true, Packages count: 0

----> Repository : LocalInstalled, Enabled: true, Packages count: 46

Microsoft (R) Windows Debugger Version 10.0.29617.1000 AMD64

Loading Dump File [C:\Windows\Minidump\062426-14093-01.dmp]

Could not open dump file [C:\Windows\Minidump\062426-14093-01.dmp], Win32 error 0n2

"系统找不到指定的文件。"

ExtensionGallery settings after reading 'SOFTWARE\Microsoft\Debug Engine' registry:

ExtensionGallery ExtensionRepository: Implicit

************* Path validation summary **************

Response Time (ms) Location

Deferred srv*

************* Path validation summary **************

Response Time (ms) Location

Deferred srv*

************* Preparing the environment for Debugger Extensions Gallery repositories **************

ExtensionRepository : Implicit

UseExperimentalFeatureForNugetShare : true

AllowNugetExeUpdate : true

NonInteractiveNuget : true

AllowNugetMSCredentialProviderInstall : true

AllowParallelInitializationOfLocalRepositories : true

-- 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.016 seconds

----> Repository : UserExtensions, Enabled: true, Packages count: 0

----> Repository : LocalInstalled, Enabled: true, Packages count: 46

Microsoft (R) Windows Debugger Version 10.0.29617.1000 AMD64

Loading Dump File [C:\Windows\Minidump\080426-14296-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

WARNING: TriageDumpDataExtArray.HeaderSize is 0

WARNING: Failed to read dump data exension data

************* Path validation summary **************

Response Time (ms) Location

Deferred srv*

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 29639 MP (20 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0xfffff803e6000000 PsLoadedModuleList = 0xfffff803e6edf6e0

Debug session time: Tue Aug 4 12:56:19.807 2026 (UTC + 8:00)

System Uptime: 0 days 3:55:12.470

Loading Kernel Symbols

...............................................................

................................................................

......

Loading User Symbols

Loading unloaded module list

.............

For analysis of this file, run !analyze -v

*** WARNING: Unable to verify timestamp for navagio.sys

navagio+0x56be51:

fffff8039912be51 4c8b8c116928fba1 mov r9,qword ptr [rcx+rdx-5E04D797h] ds:002b:d90e477bddb76784=????????????????

8: kd> !analyze -v

Loading Kernel Symbols

...............................................................

................................................................

......

Loading User Symbols

Loading unloaded module list

.............

Unable to load image navagio.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for navagio.sys

************* Symbol Loading Error Summary **************

Module name Error

navagio 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                                    *

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)

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: fffff8039912be51, The address that the exception occurred at

Arg3: ffffe00109417508, Exception Record Address

Arg4: ffffe00109416d30, Context Record Address

Debugging Details:

慕琴居士 20

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


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 1625

    Key  : Analysis.Elapsed.mSec
    Value: 47807

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29617.1000

    Key  : Analysis.Version.Description
    Value: 10.2604.29.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2604.29.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1000007e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x1000007e

    Key  : Dump.Attributes.AsUlong
    Value: 0x21008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_navagio!unknown_function

    Key  : Failure.Exception.Code
    Value: 0xc0000005

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff8039912be51

    Key  : Failure.Exception.IP.Module
    Value: navagio

    Key  : Failure.Exception.IP.Offset
    Value: 0x56be51

    Key  : Failure.Exception.Record
    Value: 0xffffe00109417508

    Key  : Failure.Hash
    Value: {6222815b-3cb3-3768-7909-4df0d79945f9}

    Key  : Faulting.IP.Type
    Value: Paged


BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8039912be51

BUGCHECK_P3: ffffe00109417508

BUGCHECK_P4: ffffe00109416d30

FILE_IN_CAB:  080426-14296-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff94038693f540

EXCEPTION_RECORD:  ffffe00109417508 -- (.exr 0xffffe00109417508)
ExceptionAddress: fffff8039912be51 (navagio+0x000000000056be51)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  ffffe00109416d30 -- (.cxr 0xffffe00109416d30)
rax=ffffe001094177b0 rbx=ffffe001094179e8 rcx=000000005e04d797
rdx=d90e477bddb76784 rsi=000000005e04d797 rdi=d90e477a62f7c210
rip=fffff8039912be51 rsp=ffffe00109417748 rbp=fffff8039912be35
 r8=0000000000000043  r9=ffffffffffffffff r10=fffff80399588d18
r11=e70497e78a0caa16 r12=0000000000000000 r13=60b51ab3e77af9e8
r14=000000000ec00687 r15=aba5519747407f46
iopl=0         nv up ei pl zr na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
navagio+0x56be51:
fffff803`9912be51 4c8b8c116928fba1 mov     r9,qword ptr [rcx+rdx-5E04D797h] ds:002b:d90e477b`ddb76784=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff803e6fbe510: Unable to get MiVisibleState
 ffffffffffffffff 

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p            0x%p                    %s

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

EXCEPTION_STR:  0xc0000005

IP_IN_PAGED_CODE: 
navagio+56be51
fffff803`9912be51 4c8b8c116928fba1 mov     r9,qword ptr [rcx+rdx-5E04D797h]

STACK_TEXT:  
ffffe001`09417748 ffffe001`09417a99     : 00000000`e105536e 38a9a69f`29c7b2e8 5d25dde8`3fceefc3 fffff803`98c02501 : navagio+0x56be51
ffffe001`09417750 00000000`e105536e     : 38a9a69f`29c7b2e8 5d25dde8`3fceefc3 fffff803`98c02501 60b51ab3`e77af9e8 : 0xffffe001`09417a99
ffffe001`09417758 38a9a69f`29c7b2e8     : 5d25dde8`3fceefc3 fffff803`98c02501 60b51ab3`e77af9e8 00000000`00000000 : 0xe105536e
ffffe001`09417760 5d25dde8`3fceefc3     : fffff803`98c02501 60b51ab3`e77af9e8 00000000`00000000 ffffe001`094179f0 : 0x38a9a69f`29c7b2e8
ffffe001`09417768 fffff803`98c02501     : 60b51ab3`e77af9e8 00000000`00000000 ffffe001`094179f0 00000000`00000000 : 0x5d25dde8`3fceefc3
ffffe001`09417770 60b51ab3`e77af9e8     : 00000000`00000000 ffffe001`094179f0 00000000`00000000 00000000`00000000 : navagio+0x42501
ffffe001`09417778 00000000`00000000     : ffffe001`094179f0 00000000`00000000 00000000`00000000 d90e477b`ddb76784 : 0x60b51ab3`e77af9e8


SYMBOL_NAME:  navagio+56be51

MODULE_NAME: navagio

IMAGE_NAME:  navagio.sys

STACK_COMMAND: .cxr 0xffffe00109416d30 ; kb

BUCKET_ID_FUNC_OFFSET:  56be51

FAILURE_BUCKET_ID:  AV_navagio!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {6222815b-3cb3-3768-7909-4df0d79945f9}

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

问题作者接受的答案

0 个其他答案

你的答案

Answer 1

此回复已自动翻译，因此可能存在语法错误或措辞生硬的情况。

您好慕琴居士，

我理解在 Windows 更新后游戏开始崩溃是多么令人担忧。不过，根据您分享的转储文件以及您自己的分析，问题直指 navagio.sys。这是一个非微软驱动程序，通常与《绝地求生》（PUBG）或游戏反作弊组件相关联。这很可能是第三方游戏或反作弊驱动程序的问题，而非 Windows 能直接修复的问题。不过，您仍可以尝试以下操作：

1 - 彻底卸载并重新安装游戏/反作弊组件

从 Steam 或您使用的平台卸载游戏 > 重启电脑。
检查并删除与游戏或反作弊相关的残留文件夹（如果存在），例如：
- C:\Program Files\Common Files\PUBG
- C:\Program Files\AntiCheatExpert
- 按 Win + R 键 > 输入：%localappdata%\TslGame
- 输入：%localappdata%\WELLBIA
再次重启，然后重新安装游戏。

2 - 确保所有内容均为最新版本

进入 设置 > Windows 更新 > 检查更新
然后进入 高级选项 > 可选更新
安装所有可用更新并重启。
此外，请访问电脑或主板制造商的网站：
- 下载显卡和芯片组驱动程序
- 安装所有驱动程序并重启电脑。

3 - 暂时移除可能冲突的底层软件

如果您运行了其他反作弊、游戏覆盖（overlay）、RGB 灯效控制、超频或安全软件，请暂时卸载或禁用它们以进行测试。
您可以尝试删除 navagio.sys 作为临时解决方案，但不要完全依赖此方法，因为下次启动游戏时，游戏或反作弊程序可能会重新安装该文件。

如果问题依然存在，且转储文件指向 navagio.sys，那么这已超出微软能完全解决的范围。Windows 故障排查有助于确认原因，但无法修复第三方的内核级驱动程序。建议您将转储文件及此分析结果发送给 PUBG/游戏官方支持团队或反作弊软件供应商，因为只有他们能够更新或修复该驱动程序。

此外，并非只有您一位 Insider 预览体验计划用户遇到了此类问题。在预览版构建中，内核变更往往最先影响到游戏反作弊驱动程序。您也可以通过 反馈中心（按 Win + F 键即可打开）提交相关反馈。

如果您觉得此答案对您有帮助，请将其标记为已接受。如果您对此答案还有其他疑问，请点击“添加评论”提问！

注意：如果您想启用并接收此主题的相关电子邮件通知，请按照我们文档中的步骤操作。

慕琴居士 20 信誉分

2026-08-04T09:55:55.7566667+00:00

Dear Lychee-Ng, thank you for your reply. Please excuse any issues, as I am using translation software.

I have already tried uninstalling the driver and reinstalling the game, but neither step resolved the issue.

I have attempted to update the system and graphics drivers, and I have done my best to ensure no other programs are interfering with the operation of navagio.sys, yet the problem persists.

I suspect this is a conflict between the driver and the Canary build 29500 series. Before updating to this series, I was able to run PUBG normally on the Canary 28000 series; the error only began appearing after I updated to this new series.

I will try to report this issue to the game developers. In any case, your answer was very helpful—thank you.
Lychee-Ng 28,915 信誉分 Microsoft 外部员工审查方

2026-08-04T10:20:30.48+00:00

感谢您分享最新情况，慕琴居士。别担心，我也在使用翻译工具，很高兴您能理解我的回答。确实，在 Insider 预览版（测试版）中，驱动程序兼容性问题时有发生，这并不罕见；毕竟这些版本主要用于测试，而游戏或程序开发商可能尚未针对最新更新发布适配版本。希望这个问题能尽快解决，让您能早日重返游戏！