VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e) mavi ekran hatası nasıl çözülür?

İşletim sistemi
Windows 11

Mustafa İnan

Yoctopat
Katılım
23 Ocak 2025
Mesajlar
3
Daha fazla  
Cinsiyet
Erkek
System model: Excalibur G770.
Operating System: Windows 11 Home Single Language 64-bit
BIOS: CP221 (type: UEFI)
Processor: 12th gen Intel(R) Core(tm) i5-12450H (12 cpus), ~2.5GHz
Memory: 8192MB RAM.
Available OS Memory: 7934MB RAM.
Card name: NVIDIA GeForce GTX 1650.
Display Memory: 7903 MB.

Aralık ayında son ekran kartı güncellemesinden sonra Chrome da gezinirken 1 ay içinde 5-6 kere mavi ekran hatası aldım. Her zaman vermiyor ama arada Chrome gezinirken bu hatayı alıyorum. Herhangi bir şey denemedim.
 
Son düzenleyen: Moderatör:
@Mustafa İnan Minidump dosyası indirilemiyor. DDU ile dahili ve harici ekran kartı sürücülerini kaldırıp tekrar kurun.


2025-01-23_21-46-39.png
 
Son düzenleme:
@Mustafa İnan Minidump dosyası indirilemiyor. DDU ile dahili ve harici ekran kartı sürücülerini kaldırıp tekrar kurun.


Eki Görüntüle 2405706

Bütün minidump hatalarında "VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)" ve
"MODULE_NAME: dxgmms2"

"IMAGE_NAME: dxgmms2.sys" bunlar ortak olarak yazıyor

************* 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.047 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:\Windows\Minidump\012325-27250-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 26100 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff807`75400000 PsLoadedModuleList = 0xfffff807`762f4870
Debug session time: Thu Jan 23 16:43:07.343 2025 (UTC + 3:00)
System Uptime: 0 days 0:10:56.404
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....................................
Loading User Symbols

Loading unloaded module list
..............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`758b85d0 48894c2408 mov qword ptr [rsp+8],rcx ss:fffffc87`e1e16f00=000000000000010e
0: 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: 000000000000002d, The subtype of the BugCheck:
Arg2: ffffd50ab138e670
Arg3: ffffd50ab1723640
Arg4: fffffc87e1e16ff8

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1359

Key : Analysis.Elapsed.mSec
Value: 6122

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

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

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

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: 0x10e

Key : Bugcheck.Code.TargetModel
Value: 0x10e

Key : Dump.Attributes.AsUlong
Value: 21808

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

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

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: 0x10e_2d_dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress

Key : Failure.Hash
Value: {ca00cb12-3ce5-2e41-c763-7f0f8a8fbadd}

Key : Hypervisor.Enlightenments.ValueHex
Value: 7417df84

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 55185662

Key : Hypervisor.Flags.ValueHex
Value: 34a10fe

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 3f7


BUGCHECK_CODE: 10e

BUGCHECK_P1: 2d

BUGCHECK_P2: ffffd50ab138e670

BUGCHECK_P3: ffffd50ab1723640

BUGCHECK_P4: fffffc87e1e16ff8

FILE_IN_CAB: 012325-27250-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump

FAULTING_THREAD: ffffaf887e3c7180

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffffc87`e1e16ef8 fffff807`08a21316 : 00000000`0000010e 00000000`0000002d ffffd50a`b138e670 ffffd50a`b1723640 : nt!KeBugCheckEx
fffffc87`e1e16f00 fffff807`28e7d60e : ffffd50a`b16f6800 ffffd50a`c8ceca90 00000000`00000000 ffffaf88`7e3c7180 : watchdog!WdLogSingleEntry5+0x156
fffffc87`e1e16f90 fffff807`28e4b88a : ffffaf88`00010000 fffff807`75676499 fffffc87`e1e171a0 ffffd50a`c1e3c910 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress+0x9de
fffffc87`e1e17070 fffff807`28e4b0a4 : 00000000`00000001 00000000`00000002 00000000`00000200 ffffaf88`7e869000 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetDriverUpdateAddress+0x66
fffffc87`e1e170e0 fffff807`28e70483 : ffffd50a`b14a32b0 ffffd50a`b14a32b0 fffffc87`e1e17620 00000000`00000000 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0x4c4
fffffc87`e1e171f0 fffff807`28e701ef : ffffd50a`b131dc30 ffffd50a`b14a32b0 fffffc87`e1e17620 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x683
fffffc87`e1e173a0 fffff807`28e54bc4 : ffffd50a`b131ddc0 ffffd50a`b14a32b0 fffffc87`e1e17620 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x3ef
fffffc87`e1e17550 fffff807`28e99a2b : 00000000`00000000 ffffaf88`7e3c7aa0 00000000`00000000 00000000`00000000 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x994
fffffc87`e1e176e0 fffff807`28e43d38 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000010 : dxgmms2!VIDMM_GLOBAL::InitPagingProcessVaSpace+0x213
fffffc87`e1e17880 fffff807`28e4532c : ffffaf88`7e869000 ffffd50a`b14a34c0 ffffd50a`b14a34c0 fffffc87`e1e179e8 : dxgmms2!VIDMM_GLOBAL::processSystemCommand+0x500
fffffc87`e1e17980 fffff807`7585585a : ffffd50a`b165f000 fffff807`28e44901 ffffe780`32ca9100 066fe47f`b19bbd02 : dxgmms2!VidMmWorkerThreadProc+0x9cc
fffffc87`e1e17b30 fffff807`75a7ae54 : ffffe780`32ca9180 ffffaf88`7e3c7180 fffff807`75855800 00720063`0069004d : nt!PspSystemThreadStartup+0x5a
fffffc87`e1e17b80 00000000`00000000 : fffffc87`e1e18000 fffffc87`e1e11000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME: dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress+9de

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.26100.2454

STACK_COMMAND: .process /r /p 0xffffaf88634bf040; .thread 0xffffaf887e3c7180 ; kb

BUCKET_ID_FUNC_OFFSET: 9de

FAILURE_BUCKET_ID: 0x10e_2d_dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ca00cb12-3ce5-2e41-c763-7f0f8a8fbadd}

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

Technopat Haberler

Yeni konular

Geri
Yukarı