通过

如何解决我的Windows pc 上的SYMBOL_NAME: dxgmms2!VIDMM_MEMORY_SEGMENT::EvictResource+35025问题

^^ AME 40 信誉分
2024-07-05T09:15:13.2966667+00:00 
************ Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true

   EnableRedirectToV8JsProvider : 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.015 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 41

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


Loading Dump File [C:\Windows\Minidump\070524-12562-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
Kernel base = 0xfffff803`74800000 PsLoadedModuleList = 0xfffff803`7542a360
Debug session time: Fri Jul  5 12:45:36.101 2024 (UTC + 8:00)
System Uptime: 0 days 22:51:19.515
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........................................
Loading User Symbols

Loading unloaded module list
....................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`74bfdb50 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff408`224d91e0=0000000000000139
5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff408224d9500, Address of the trap frame for the exception that caused the BugCheck
Arg3: fffff408224d9458, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1999

    Key  : Analysis.Elapsed.mSec
    Value: 7190

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x139

    Key  : Bugcheck.Code.TargetModel
    Value: 0x139

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : FailFast.Name
    Value: CORRUPT_LIST_ENTRY

    Key  : FailFast.Type
    Value: 3

    Key  : Failure.Bucket
    Value: 0x139_3_CORRUPT_LIST_ENTRY_dxgmms2!VIDMM_MEMORY_SEGMENT::EvictResource

    Key  : Failure.Hash
    Value: {cc828615-740d-ecfc-597f-d2f6932cfc77}


BUGCHECK_CODE:  139

BUGCHECK_P1: 3

BUGCHECK_P2: fffff408224d9500

BUGCHECK_P3: fffff408224d9458

BUGCHECK_P4: 0

FILE_IN_CAB:  070524-12562-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

TRAP_FRAME:  fffff408224d9500 -- (.trap 0xfffff408224d9500)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9482c17b9ea8 rbx=0000000000000000 rcx=0000000000000003
rdx=ffff9482c0b73e88 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8037369c565 rsp=fffff408224d9690 rbp=fffff408224d9700
 r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
r11=fffff80373642ac0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
dxgmms2!VIDMM_MEMORY_SEGMENT::EvictResource+0x35025:
fffff803`7369c565 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  fffff408224d9458 -- (.exr 0xfffff408224d9458)
ExceptionAddress: fffff8037369c565 (dxgmms2!VIDMM_MEMORY_SEGMENT::EvictResource+0x0000000000035025)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

ERROR_CODE: (NTSTATUS) 0xc0000409 - <Unable to get error code text>

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000003

EXCEPTION_STR:  0xc0000409

STACK_TEXT:  
fffff408`224d91d8 fffff803`74c123a9     : 00000000`00000139 00000000`00000003 fffff408`224d9500 fffff408`224d9458 : nt!KeBugCheckEx
fffff408`224d91e0 fffff803`74c12950     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff408`224d9320 fffff803`74c107f2     : ffff9482`c17b9f08 00000000`00000000 00000000`00000000 00000000`00020000 : nt!KiFastFailDispatch+0xd0
fffff408`224d9500 fffff803`7369c565     : ffff9482`c17b9d30 fffff408`224d9700 ffff9482`b84e6710 ffffd88f`1ac03000 : nt!KiRaiseSecurityCheckFailure+0x332
fffff408`224d9690 fffff803`7366e6ac     : ffffd88f`1ac0cc20 fffff408`224d97e0 ffffd88f`1ac03000 00000000`00000000 : dxgmms2!VIDMM_MEMORY_SEGMENT::EvictResource+0x35025
fffff408`224d96e0 fffff803`7368e418     : ffffd88f`1ac03000 ffffd88f`1ac0cc10 ffffd88f`1ac03000 ffffd88f`1ac03000 : dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+0xa9c
fffff408`224d9900 fffff803`736988a9     : ffff9482`aab65140 ffffd88f`1aacd200 00000000`00000000 00000000`08420f00 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xb78
fffff408`224d9ae0 fffff803`74b48da5     : ffffd88f`1aacd280 fffff803`736988a0 ffff9482`aab65140 000fa4ef`bd9bbfff : dxgmms2!VidMmWorkerThreadProc+0x9
fffff408`224d9b10 fffff803`74c06b58     : ffff8080`fa247180 ffffd88f`1aacd280 fffff803`74b48d50 0073005c`00250074 : nt!PspSystemThreadStartup+0x55
fffff408`224d9b60 00000000`00000000     : fffff408`224da000 fffff408`224d3000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  dxgmms2!VIDMM_MEMORY_SEGMENT::EvictResource+35025

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.4597

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  35025

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_dxgmms2!VIDMM_MEMORY_SEGMENT::EvictResource

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {cc828615-740d-ecfc-597f-d2f6932cfc77}

Followup:     MachineOwner
---------
Windows
Windows
Microsoft 操作系统系列，可跨个人计算机、平板电脑、笔记本电脑、手机、物联网设备、独立混合现实头戴显示设备、大型协作屏幕和其他设备运行。
375 个问题
0 个注释

1 个答案

排序依据： 非常有帮助
非常有帮助 最新 最早
  1. Wesley Li 9,335 信誉分
    2024-07-06T00:14:25.4533333+00:00

    您好，

    您似乎遇到了 KERNEL_SECURITY_CHECK_FAILURE (139) 错误，该错误通常与损坏的 LIST_ENTRY 有关，如您共享的错误代码和参数所示。此特定实例涉及 dxgmms2.sys 驱动程序，该驱动程序与 DirectX 图形有关。

    您可以采取以下一些步骤来尝试解决此问题：

    1.更新图形驱动程序：确保您的图形驱动程序是最新的。您可以通过设备管理器或从制造商的网站下载最新的驱动程序来执行此操作。

    2.运行系统文件检查器 (SFC) 和 DISM：

    以管理员身份打开命令提示符。

    运行 sfc /scannow 检查并修复损坏的系统文件。

    运行 DISM /Online /Cleanup-Image /RestoreHealth 修复 Windows 映像。

    3.检查 Windows 更新：确保您的 Windows 操作系统已完全更新。有时，更新包含对此类问题的修复。

    1. 启动至安全模式：启动至安全模式可以帮助您诊断问题是否由第三方软件或驱动程序引起。如果问题未在安全模式下出现，则可能与安全模式下未加载的软件或驱动程序有关。
    2. 禁用硬件加速：如果在使用某些应用程序时出现问题，请尝试禁用这些应用程序中的硬件加速。
    3. 全新安装图形驱动程序：有时，全新安装图形驱动程序可以解决问题。使用显示驱动程序卸载程序 (DDU) 等工具完全删除当前驱动程序，然后再重新安装它们。

    如果这些步骤无法解决问题，您可能需要考虑更高级的故障排除或寻求专业支持。

    0 个注释

你的答案

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