最近电脑总是重启,请帮我分析下DMP文件,谢谢

YUXIN LIU 20 信誉分
2025-06-21T01:05:17.55+00:00

重新上传了一遍文件

通过网盘分享的文件:062125-8265-01.dmp

链接: https://pan.baidu.com/s/1ZhIuSZdvf4hPRyMHj5udVw 提取码: pj22

************* 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.016 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 44

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


Loading Dump File [E:\062125-8265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 26100 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff802`75000000 PsLoadedModuleList = 0xfffff802`75ef4a60
Debug session time: Sat Jun 21 08:35:32.553 2025 (UTC + 8:00)
System Uptime: 0 days 7:29:30.152
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000000d`8a817018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`755017d0 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffffd90a`5b276c60=000000000000000a
11: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000000d`8a817018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000018, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80275346039, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 968

    Key  : Analysis.Elapsed.mSec
    Value: 6531

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Bugcheck.Code.TargetModel
    Value: 0xa

    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_nt!MiReplenishPageSlist

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

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

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

    Key  : Failure.Hash
    Value: {e1780c1b-c7ae-f629-f6fa-ba2f8fe42756}


BUGCHECK_CODE:  a

BUGCHECK_P1: 18

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff80275346039

FILE_IN_CAB:  062125-8265-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffc90720a450c0

WRITE_ADDRESS: fffff80275fc44c0: 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
 0000000000000018 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  taskhostw.exe

STACK_TEXT:  
ffffd90a`5b276c58 fffff802`756b95e9     : 00000000`0000000a 00000000`00000018 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffd90a`5b276c60 fffff802`756b48a8     : ffffd90a`5b277340 fffff802`082e7c34 00000000`00000000 ffffc907`211b28e0 : nt!KiBugCheckDispatch+0x69
ffffd90a`5b276da0 fffff802`75346039     : 00000000`00070053 00000000`00000000 00000000`003ecf53 00000000`00000293 : nt!KiPageFault+0x468
ffffd90a`5b276f30 fffff802`753343a7     : ffffe040`00004300 00000000`00000000 00000000`00000139 ffffd90a`5b277070 : nt!MiReplenishPageSlist+0x1f9
ffffd90a`5b277030 fffff802`75334c67     : 00000000`00000011 ffffd90a`5b2771a8 00000000`00000000 00000000`00000053 : nt!MiGetPerfectColorHeadPage+0x3f7
ffffd90a`5b277140 fffff802`753335bc     : ffffe040`000053c8 ffffd90a`00000051 00000219`00000100 00000000`00000000 : nt!MiRemovePageAnyColor+0x267
ffffd90a`5b2771f0 fffff802`753140b4     : 8a000002`25c50867 00000000`00000000 00000001`00000000 00000000`00000039 : nt!MiGetPage+0xdac
ffffd90a`5b277330 fffff802`75314c3d     : 00000000`00000000 00000000`00000000 ffffd90a`5b2774e0 ffffd90a`5b277990 : nt!MiGetPageChain+0x154
ffffd90a`5b2773e0 fffff802`753139ad     : 00000001`00000009 00000000`00000000 ffffffff`ffffffff ffffc907`227b54c0 : nt!MiResolvePrivateZeroFault+0x54d
ffffd90a`5b2775a0 fffff802`75312237     : ffffd90a`5b2778e0 ffffd90a`5b277840 00000000`00000000 fffff17f`ffffffff : nt!MiResolveDemandZeroFault+0x22d
ffffd90a`5b277740 fffff802`7522964c     : 000001e3`8b40504c ffff8000`00000004 000001e3`8b40604c 00000000`00000000 : nt!MiDispatchFault+0x4c7
ffffd90a`5b2778b0 fffff802`756b47cb     : 000001e3`8a194138 00000000`00000000 000001e3`8a331500 00000000`00000080 : nt!MmAccessFault+0x20c
ffffd90a`5b277a20 00007ffb`323fae22     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x38b
0000000d`8ac7e000 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`323fae22


SYMBOL_NAME:  nt!MiReplenishPageSlist+1f9

MODULE_NAME: nt

IMAGE_VERSION:  10.0.26100.4351

STACK_COMMAND: .process /r /p 0xffffc907227b50c0; .thread 0xffffc90720a450c0 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  1f9

FAILURE_BUCKET_ID:  AV_nt!MiReplenishPageSlist

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e1780c1b-c7ae-f629-f6fa-ba2f8fe42756}

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

* 移动自 [Microsoft System Center / System Center Orchestrator]

Windows 商业版 | 面向 IT 专业人士的 Windows 客户端 | 用户体验 | 其他
{count} 票

接受的答案
  1. Ling Gao 971 信誉分
    2025-06-22T01:00:06.7433333+00:00

    上午好,YUXIN LIU

    已分析您分享的 DMP 日志,没有找到疑似导致电脑蓝屏的第三方软件 / 驱动程序,目前倾向于 Windows 11 系统损坏电脑硬件存在异常。推荐优先排查软件层面的问题:

    1. 在终端 (管理员) 中运行以下四个命令,修复 Windows 系统:
    SFC /scannow
    DISM /Online /Cleanup-Image /CheckHealth
    DISM /Online /Cleanup-Image /ScanHealth
    DISM /Online /Cleanup-Image /RestoreHealth
    

    使用系统文件检查器工具修复丢失或损坏的系统文件

    1. 按下 WIN + R,输入 mdsched.exe,进行 Windows 内存诊断。
    2. 执行 chkdsk C: /f /r /x 命令,诊断电脑硬盘。看到 “该卷正被另一进程使用” 提示时,输入 “Y”,回车,重启电脑即可诊断并修复硬盘中的错误。
    3. 更新 BIOS、芯片组等驱动,提高硬件环境的稳定性。

    如果以上三个步骤没有效果,请到 “设置”>“系统”>“恢复” 菜单使用 “使用 Windows 更新修复问题” 功能 (如下图),覆盖安装一次系统,修复所有 Windows 组件,看看能否解决蓝屏问题。

    通过重新安装当前版本的 Windows 修复问题

    使用 Windows 更新修复问题

    顺颂 时祺
    - Ling

    0 个注释 无注释

0 个其他答案

排序依据: 非常有帮助

你的答案

问题作者可以将答案标记为“接受的答案”,这有助于用户了解已解决作者问题的答案。