Çözüldü "VIDEO_MEMORY_MANAGEMENT_INTERNAL" hatası

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.

KeremAkyuz

Decapat
Katılım
5 Eylül 2020
Mesajlar
12
Çözümler
1
Merhaba,
HP Omen 15 RTX 3070'li sisteme sahibim. Bilgisayarı şarjda kullanırken sorun yok ancak pilde kullanırken bir süre sonra mavi ekran alıyorum. Güç tasarrufu moduna aldığımda mavi ekranı daha sık görmeye başlıyorum. MSI yazılımları ve r6Siege vardı, eski konularda onları kaldırınca sorun çözülmüş. Kaldırmama rağmen hala sorun çözülmedi. DDU ile NVIDIA ekran kartı sürücümü kaldırıp tekrardan kurulum da gerçekleştirdim.
.dmp dosyaları.
IMG_20211016_124921.jpg
 
Çözüm
Cihaz BIOS'unu sıfırlayın ve Ryzen 7 5800H ile gelen GPU sürücüsünü DDU ile kaldırıp kurun. Sorun devam ederse ya da çözülürse belirtirseniz sevinirim. İyi akşamlar, kolay gelsin.

[CODE title="Dökümler"]*******************************************************************************
* *
* 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: ffffa004f7c793b0
Arg3: ffffa004f2e362b0
Arg4: ffffde8bf03a6fa0

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 9436

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 43665

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

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

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

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 10e

BUGCHECK_P1: 2d

BUGCHECK_P2: ffffa004f7c793b0

BUGCHECK_P3: ffffa004f2e362b0

BUGCHECK_P4: ffffde8bf03a6fa0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffde8b`f03a6f28 fffff807`7ee03ad0 : 00000000`0000010e 00000000`0000002d ffffa004`f7c793b0 ffffa004`f2e362b0 : nt!KeBugCheckEx
ffffde8b`f03a6f30 fffff807`805f93e1 : ffffa004`f2e362b0 00000000`00000001 00000000`00000001 fffff807`676079f3 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffde8b`f03a6f70 fffff807`8067f0b5 : ffffa004`f2e362b0 ffffa004`f7c793b0 ffffa004`f7c793b0 00000000`00000000 : dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange+0x24d
ffffde8b`f03a6ff0 fffff807`80674c07 : ffffa004`f7c16560 ffffde8b`f03a7100 00000000`00000000 ffffde8b`f03a71d8 : dxgmms2!VIDMM_GLOBAL::BuildMdlForAllocInCpuHostAperture+0xe5
ffffde8b`f03a7030 fffff807`8064d484 : 00000000`00000000 00000000`00000002 ffff840f`bdc14000 ffffa004`f7c16560 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress+0x27763
ffffde8b`f03a7070 fffff807`806507ea : 00000000`00000000 ffffa004`f2e364d0 00000000`00000002 ffff840f`b5eb5910 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetDriverUpdateAddress+0xb8
ffffde8b`f03a7100 fffff807`80674f8a : 00000000`00000000 00000000`00000000 00000000`00000002 ffffde8b`f03a7620 : dxgmms2!VIDMM_PAGE_TABLE::UpdatePageTableInvalidate+0x4a
ffffde8b`f03a71d0 fffff807`8064b8bd : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0x279a2
ffffde8b`f03a7270 fffff807`80673dce : 00000000`00000002 ffffa004`f81ee2e0 ffffe001`8a544101 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x77d
ffffde8b`f03a73e0 fffff807`8064ab7a : 00000000`00000000 ffffa004`f81ee2e0 00000000`00001000 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x28c8e
ffffde8b`f03a7550 fffff807`8067de98 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x2f6
ffffde8b`f03a76d0 fffff807`80675920 : 00000000`00000000 00000000`00000000 00000000`00000076 ffffa005`0a0750c0 : dxgmms2!VIDMM_GLOBAL::InitPagingProcessVaSpace+0x183c8
ffffde8b`f03a7840 fffff807`8065cc62 : ffffa004`f81ed890 ffffde8b`00000001 00000000`00000001 ffffa004`f80ee8b0 : dxgmms2!VIDMM_GLOBAL::processSystemCommand+0x277d4
ffffde8b`f03a79c0 fffff807`80666809 : ffffa004`f80ee840 ffff840f`bdb16201 ffffde8b`ef780300 00000000`07618500 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x1462
ffffde8b`f03a7ba0 fffff807`67755855 : ffff840f`bdb16280 fffff807`80666800 ffffa004`f80ee840 000fe067`bcbbbdff : dxgmms2!VidMmWorkerThreadProc+0x9
ffffde8b`f03a7bd0 fffff807`677fe808 : ffffe001`8ab06180 ffff840f`bdb16280 fffff807`67755800 ec8148c9`246c8d48 : nt!PspSystemThreadStartup+0x55
ffffde8b`f03a7c20 00000000`00000000 : ffffde8b`f03a8000 ffffde8b`f03a1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange+24d

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.1261

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 24d

FAILURE_BUCKET_ID: 0x10e_2d_dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e24407bd-c019-66cd-5bed-5339a6b0e6f7}

Followup: MachineOwner
---------[/CODE]
Cihaz BIOS'unu sıfırlayın ve Ryzen 7 5800H ile gelen GPU sürücüsünü DDU ile kaldırıp kurun. Sorun devam ederse ya da çözülürse belirtirseniz sevinirim. İyi akşamlar, kolay gelsin.

[CODE title="Dökümler"]*******************************************************************************
* *
* 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: ffffa004f7c793b0
Arg3: ffffa004f2e362b0
Arg4: ffffde8bf03a6fa0

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 9436

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 43665

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

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

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

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 10e

BUGCHECK_P1: 2d

BUGCHECK_P2: ffffa004f7c793b0

BUGCHECK_P3: ffffa004f2e362b0

BUGCHECK_P4: ffffde8bf03a6fa0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffde8b`f03a6f28 fffff807`7ee03ad0 : 00000000`0000010e 00000000`0000002d ffffa004`f7c793b0 ffffa004`f2e362b0 : nt!KeBugCheckEx
ffffde8b`f03a6f30 fffff807`805f93e1 : ffffa004`f2e362b0 00000000`00000001 00000000`00000001 fffff807`676079f3 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffde8b`f03a6f70 fffff807`8067f0b5 : ffffa004`f2e362b0 ffffa004`f7c793b0 ffffa004`f7c793b0 00000000`00000000 : dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange+0x24d
ffffde8b`f03a6ff0 fffff807`80674c07 : ffffa004`f7c16560 ffffde8b`f03a7100 00000000`00000000 ffffde8b`f03a71d8 : dxgmms2!VIDMM_GLOBAL::BuildMdlForAllocInCpuHostAperture+0xe5
ffffde8b`f03a7030 fffff807`8064d484 : 00000000`00000000 00000000`00000002 ffff840f`bdc14000 ffffa004`f7c16560 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress+0x27763
ffffde8b`f03a7070 fffff807`806507ea : 00000000`00000000 ffffa004`f2e364d0 00000000`00000002 ffff840f`b5eb5910 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetDriverUpdateAddress+0xb8
ffffde8b`f03a7100 fffff807`80674f8a : 00000000`00000000 00000000`00000000 00000000`00000002 ffffde8b`f03a7620 : dxgmms2!VIDMM_PAGE_TABLE::UpdatePageTableInvalidate+0x4a
ffffde8b`f03a71d0 fffff807`8064b8bd : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0x279a2
ffffde8b`f03a7270 fffff807`80673dce : 00000000`00000002 ffffa004`f81ee2e0 ffffe001`8a544101 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x77d
ffffde8b`f03a73e0 fffff807`8064ab7a : 00000000`00000000 ffffa004`f81ee2e0 00000000`00001000 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x28c8e
ffffde8b`f03a7550 fffff807`8067de98 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x2f6
ffffde8b`f03a76d0 fffff807`80675920 : 00000000`00000000 00000000`00000000 00000000`00000076 ffffa005`0a0750c0 : dxgmms2!VIDMM_GLOBAL::InitPagingProcessVaSpace+0x183c8
ffffde8b`f03a7840 fffff807`8065cc62 : ffffa004`f81ed890 ffffde8b`00000001 00000000`00000001 ffffa004`f80ee8b0 : dxgmms2!VIDMM_GLOBAL::processSystemCommand+0x277d4
ffffde8b`f03a79c0 fffff807`80666809 : ffffa004`f80ee840 ffff840f`bdb16201 ffffde8b`ef780300 00000000`07618500 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x1462
ffffde8b`f03a7ba0 fffff807`67755855 : ffff840f`bdb16280 fffff807`80666800 ffffa004`f80ee840 000fe067`bcbbbdff : dxgmms2!VidMmWorkerThreadProc+0x9
ffffde8b`f03a7bd0 fffff807`677fe808 : ffffe001`8ab06180 ffff840f`bdb16280 fffff807`67755800 ec8148c9`246c8d48 : nt!PspSystemThreadStartup+0x55
ffffde8b`f03a7c20 00000000`00000000 : ffffde8b`f03a8000 ffffde8b`f03a1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange+24d

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.1261

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 24d

FAILURE_BUCKET_ID: 0x10e_2d_dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e24407bd-c019-66cd-5bed-5339a6b0e6f7}

Followup: MachineOwner
---------[/CODE]
 
Çözüm
Ya sürücü sıkıntısı var, ya da donanımsal. Enes hocamın dediği gibi DDU ile yeniden kurulum yapın. Yine sorun yaşanırsa, sanırım donanımsal bir sorun var.
 
İşteyim şu an eve geçtiğim gibi yapıp dönüş yapacağım.
DDU ile sürücüyü kaldırıp geri kurdum. BIOS ayarlarımı varsayılanlara geri sıfırladım ancak hala sorun devam etmekte.
-------------------------
Sorunumu BIOS güncellemesi sonrası temiz kurulum yaparak çözdüm. Yüksek ihtimalle BIOS güncellemesi çözdü. Teşekkürler.
 
Son düzenleme:

Yeni konular

Geri
Yukarı