通过

Windows10蓝屏VIDEO MEMORY MANAGEMENT INTERNAL

李泽 夏 20 信誉分
2024-09-07T10:21:27.0533333+00:00

WinDbg检测结果，求求了请耐心看完：

************* 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.031 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: 29

Microsoft (R) Windows Debugger Version 10.0.26100.1 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\090724-18078-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 19041 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Edition build lab: 19041.1.amd64fre.vb_release.191206-1406

Kernel base = 0xfffff80230400000 PsLoadedModuleList = 0xfffff8023102a830

Debug session time: Sat Sep 7 17:41:03.235 2024 (UTC + 8:00)

System Uptime: 0 days 0:53:29.214

Loading Kernel Symbols

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

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

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

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

Loading User Symbols

Loading unloaded module list

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

For analysis of this file, run !analyze -v

4: kd> !analyze -v

  •                                                                         *

  •                    Bugcheck Analysis                                    *

  •                                                                         *

VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)

The video memory manager encountered a condition that it can't recover from. By crashing,

the video memory manager is attempting to get enough information into the minidump such that

somebody can pinpoint what lead to this condition.

Arguments:

Arg1: 000000000000001d, The subtype of the BugCheck:

Arg2: ffff8381cf1d9210

Arg3: 0000000000000000

Arg4: 0000000000000000

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec

Value: 4640

Key  : Analysis.Elapsed.mSec

Value: 37625

Key  : Analysis.IO.Other.Mb

Value: 10

Key  : Analysis.IO.Read.Mb

Value: 3

Key  : Analysis.IO.Write.Mb

Value: 21

Key  : Analysis.Init.CPU.mSec

Value: 8405

Key  : Analysis.Init.Elapsed.mSec

Value: 167792

Key  : Analysis.Memory.CommitPeak.Mb

Value: 101

Key  : Bugcheck.Code.LegacyAPI

Value: 0x10e

Key  : Failure.Bucket

Value: 0x10e_1d_dxgmms2!VIDMM_GLOBAL::UpdatePageTable

Key  : Failure.Hash

Value: {71cfaed7-afd6-912e-e10e-336c7c7acd87}

Key  : WER.OS.Branch

Value: vb_release

Key  : WER.OS.Version

Value: 10.0.19041.1

BUGCHECK_CODE: 10e

BUGCHECK_P1: 1d

BUGCHECK_P2: ffff8381cf1d9210

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB: 090724-18078-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:

fffff486b8bbe048 fffff80248703ad0 : 000000000000010e 000000000000001d ffff8381cf1d9210 0000000000000000 : nt!KeBugCheckEx

fffff486b8bbe050 fffff80251262ea8 : 0000000000000000 ffff8381cf2a2000 ffff8381cb2e5560 fffff80251d7cb9b : watchdog!WdLogEvent5_WdCriticalError+0xe0

fffff486b8bbe090 fffff80251252373 : 0000000000000000 0000000000000000 0000000000000000 fffff80251b26ef2 : dxgmms2!VIDMM_GLOBAL::UpdatePageTable+0x188

fffff486b8bbe320 fffff80251264057 : 0000000000000002 0000000000006000 0000000000000000 ffff8381cedc9460 : dxgmms2!VIDMM_PAGE_TABLE::UpdatePageTableInvalidate+0xf3

fffff486b8bbe3f0 fffff80251261f42 : 0000000000000002 fffff486b8bbe5a0 ffff970d917836e0 0000000000000000 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0x2bf

fffff486b8bbe490 fffff802512620d6 : 0000000000000002 ffff970d8d7f3d30 fffff486b8bbe8a0 0000000000000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x872

fffff486b8bbe630 fffff802512610fe : 0000000000000005 ffff970d8d7f3d30 fffff486b8bbe8a0 0000000000000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0xa06

fffff486b8bbe7d0 fffff802512605a4 : ffff8381cb24c510 ffff970d00000002 0000000000000000 0000000000000000 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x2f6

fffff486b8bbe950 fffff8025125203f : fffff486b8bbeab0 fffff486b8bbebd0 fffff486b8bbebd0 0000000000000000 : dxgmms2!VIDMM_GLOBAL::PageInOneAllocation+0x3b4

fffff486b8bbea70 fffff80251263fd3 : 0000000000000002 000000004d52564e 0000000000000000 0000000000000527 : dxgmms2!VIDMM_PAGE_TABLE::CommitPageTable+0x6f

fffff486b8bbeac0 fffff80251261f42 : 0000000000000002 fffff486b8bbec70 ffff970d917836e0 0000000000000000 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0x23b

fffff486b8bbeb60 fffff802512620d6 : 0000000000000002 ffff970d8d7f3d30 fffff486b8bbef70 0000000000000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x872

fffff486b8bbed00 fffff802512610fe : 0000000000000005 ffff970d8d7f3d30 fffff486b8bbef70 0000000000000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0xa06

fffff486b8bbeea0 fffff802512605a4 : ffff8381cb24c810 ffff970d00000002 0000000000000000 0000000000000000 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x2f6

fffff486b8bbf020 fffff8025125203f : fffff486b8bbf818 0000000000004000 ffff970d8ddd4090 0000000000000000 : dxgmms2!VIDMM_GLOBAL::PageInOneAllocation+0x3b4

fffff486b8bbf140 fffff80251263fd3 : 0000000000000002 ffff4d7b5eca90fe ffff970d8d76c400 fffff486b8bbf640 : dxgmms2!VIDMM_PAGE_TABLE::CommitPageTable+0x6f

fffff486b8bbf190 fffff80251261f42 : 0000000000000002 fffff486b8bbf340 ffff970d917836e0 0000000000000000 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0x23b

fffff486b8bbf230 fffff802512620d6 : 0000000000000002 ffff970d8d7f3d30 fffff486b8bbf640 0000000000000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x872

fffff486b8bbf3d0 fffff802512610fe : 0000000000000007 ffff970d8d7f3d30 fffff486b8bbf640 0000000000000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0xa06

fffff486b8bbf570 fffff802512643ac : 00000000ffffffff fffff486b8bbf7f8 0000000000000000 0000000000001001 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x2f6

fffff486b8bbf6f0 fffff802512590a9 : 0000000000000000 0000000000000071 fffff486b8bbf880 ffff970d8d7f3ec0 : dxgmms2!VIDMM_GLOBAL::CommitVirtualAddressRangeSystemCommand+0x188

fffff486b8bbf780 fffff8025127ed02 : ffff970d8d7f3e90 fffff48600000001 0000000000000001 ffff970d913fbce0 : dxgmms2!VIDMM_GLOBAL::ProcessSystemCommand+0x5a9

fffff486b8bbf900 fffff802512888a9 : ffff970d913fbc70 ffff8381cf1ea201 0000000000000000 000000000b112100 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x1462

fffff486b8bbfae0 fffff802307299a5 : ffff8381cf1ea280 fffff802512888a0 ffff970d913fbc70 000fa4efbd9bbfff : dxgmms2!VidMmWorkerThreadProc+0x9

fffff486b8bbfb10 fffff802308072a8 : ffffde0125740180 ffff8381cf1ea280 fffff80230729950 0000000000000000 : nt!PspSystemThreadStartup+0x55

fffff486b8bbfb60 0000000000000000 : fffff486b8bc0000 fffff486b8bb9000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: dxgmms2!VIDMM_GLOBAL::UpdatePageTable+188

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.4842

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 188

FAILURE_BUCKET_ID: 0x10e_1d_dxgmms2!VIDMM_GLOBAL::UpdatePageTable

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {71cfaed7-afd6-912e-e10e-336c7c7acd87}

Followup: MachineOwner

好了，后面没了，我每次都是在看视频的时候变成这样，已经被折磨好几次了，这是最后一次蓝屏的dmp分析结果

Windows 10
Windows 10
在个人计算机和平板电脑上运行的 Microsoft 操作系统。
152 个问题
接受的答案
  1. Molly Lu 846 信誉分 Microsoft 供应商
    2024-09-09T07:48:53.3+00:00

    您好、

    感谢您在 Microsoft Q&A 上发帖。

    根据您的描述，我知道您的问题与蓝屏方面有关。

    VIDEO_MEMORY_MANAGEMENT_INTERNAL 错误检查的值为 0x0000010E。 这表示视频内存管理器遇到了无法从中恢复的条件。此错误检查通常是由视频驱动程序行为不当引起的。

    跟据dump中的信息，出错的驱动名称是dxgmms2，dxgmms2.sys 文件与 DirectX 图形 MMS（内存管理系统）有关，是 DirectX 图形内核的一部分。

    尝试卸载重新安装这个驱动： dxgmms2.sys

    祝您愉快。

    Molly

    ============================================

    如果答案对您有帮助，请将其标记为 “接受的答案 ”。

    0 个注释

1 个其他答案

排序依据： 非常有帮助
非常有帮助 最新 最早
  1. TaoLi 0 信誉分
    2024-09-07T14:10:09.2433333+00:00

    您好，

    根据提供的信息dxgmms2.sys导致的蓝屏，dxgmms2.sys是显卡驱动，请尝试重新安装显卡驱动。

    0 个注释

你的答案

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