Question BSOD: VIDEO_MEMORY_MANAGEMENT_INTERNAL (10E) dxgmms2.sys ?

[Aquinoxbv]

Hello,

I have a problem with my Lenovo IdeaPad L340-15IRH laptop. It crashes and I get BSOD. Sometimes it's three times a day, sometimes is three times a week. It doesn't matter I'm playing games or just browsing Internet.

Config:
i5-9300H
Intel UHD Graphics 630
Nvidia GeForce GTX 1650
8 Gb RAM
Windows 10

What I already done is:
1. Reinstall graphics drivers with DDU
2. Updating windows
3. BIOS update
4. Fully reinstall windows 10 with disk format

After Windows 10 reinstall everything was fine for almost five days! And then again - BSOD. Anybody got idea? I think I got dammaged hardware. Can it be faulty or to small RAM? Thank you for your help.

Three Minidump files: https://files.fm/u/zdfbxvq6a4

Here is Minidump file (one of three):



*******************************************************************************
* *
* 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: ffffe28a26444830
Arg3: ffffe28a2b370610
Arg4: ffffb504bfe79e80

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

*** WARNING: Check Image - Checksum mismatch - Dump: 0x1bd2b, File: 0x1c0c9 - C:\ProgramData\Dbg\sym\monitor.sys\FD9A8F001b000\monitor.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5328

Key : Analysis.Elapsed.mSec
Value: 7477

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

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

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

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x10e

Key : Bugcheck.Code.TargetModel
Value: 0x10e

Key : Failure.Bucket
Value: 0x10e_2d_dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange

Key : Failure.Hash
Value: {e24407bd-c019-66cd-5bed-5339a6b0e6f7}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 10e

BUGCHECK_P1: 2d

BUGCHECK_P2: ffffe28a26444830

BUGCHECK_P3: ffffe28a2b370610

BUGCHECK_P4: ffffb504bfe79e80

FILE_IN_CAB: 031824-11843-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffb504`bfe79e08 fffff802`41b43ad0 : 00000000`0000010e 00000000`0000002d ffffe28a`26444830 ffffe28a`2b370610 : nt!KeBugCheckEx
ffffb504`bfe79e10 fffff802`54c192b1 : ffffe28a`2b370610 00000000`00000001 00000000`00000001 fffff802`294452a3 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffb504`bfe79e50 fffff802`54c9ec15 : ffffe28a`2b370610 ffffe28a`26444830 ffffe28a`26444830 00000000`00000000 : dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange+0x24d
ffffb504`bfe79ed0 fffff802`54c8ebe5 : ffffe28a`26425810 ffffb504`bfe79fe0 00000000`00000000 ffffb504`bfe7a0b8 : dxgmms2!VIDMM_GLOBAL::BuildMdlForAllocInCpuHostAperture+0xe5
ffffb504`bfe79f10 fffff802`54c61d84 : 00000000`00000000 00000000`00000002 ffffba0d`00dbf000 ffffe28a`26425810 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress+0x2ce41
ffffb504`bfe79f50 fffff802`54c51a1a : 00000000`00000000 ffffe28a`2b370830 00000000`00000002 ffffba0c`f704fe10 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetDriverUpdateAddress+0xb8
ffffb504`bfe79fe0 fffff802`54c8ef68 : 00000000`00000000 00000000`00000000 00000000`00000002 ffffb504`bfe7a560 : dxgmms2!VIDMM_PAGE_TABLE::UpdatePageTableInvalidate+0x4a
ffffb504`bfe7a0b0 fffff802`54c60092 : 00000000`00000002 ffffb504`bfe7a260 ffffe28a`266b1950 00000000`00000000 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0x2d080
ffffb504`bfe7a150 fffff802`54c60226 : 00000000`00000002 ffffe28a`2aff84f0 ffffb504`bfe7a560 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x872
ffffb504`bfe7a2f0 fffff802`54c5f24e : 00000000`00000000 ffffe28a`2aff84f0 ffffb504`bfe7a560 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0xa06
ffffb504`bfe7a490 fffff802`54c9d9f0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x2f6
ffffb504`bfe7a610 fffff802`54c8b7c2 : 00000000`00000000 00000000`00000000 00000000`00000076 ffffe28a`3358d810 : dxgmms2!VIDMM_GLOBAL::InitPagingProcessVaSpace+0x17470
ffffb504`bfe7a780 fffff802`54c7d712 : ffffe28a`2aff7730 ffffb504`00000001 00000000`00000001 ffffe28a`296a6f20 : dxgmms2!VIDMM_GLOBAL:rocessSystemCommand+0x34312
ffffb504`bfe7a900 fffff802`54c872b9 : ffffe28a`296a6eb0 ffffba0c`fe09b001 00000000`00000100 00000000`0668b600 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x1462
ffffb504`bfe7aae0 fffff802`295078c5 : ffffba0c`fe09b080 fffff802`54c872b0 ffffe28a`296a6eb0 000fa4ef`bd9bbfff : dxgmms2!VidMmWorkerThreadProc+0x9
ffffb504`bfe7ab10 fffff802`296067b8 : ffffcc01`88280180 ffffba0c`fe09b080 fffff802`29507870 0bb81800`94042a03 : nt!PspSystemThreadStartup+0x55
ffffb504`bfe7ab60 00000000`00000000 : ffffb504`bfe7b000 ffffb504`bfe74000 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.4170

STACK_COMMAND: .cxr; .ecxr ; 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

 

[ubuysa]

Hello, and welcome to the forum!

All three dumps are identical and all fail because a call to the DdiMapCpuHostAperture function in the DirectX kernel driver dxgmms2.sys failed...

FAILURE_BUCKET_ID:  0x10e_2d_dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange

The problem here could either be a graphics card hardware error or a graphics driver error. Oe thing can see initially from the dumps is that this is a laptop...

[System Information (Type 1) - Length 27 - Handle 0001h]
  Manufacturer                  LENOVO
  Product Name                  81LK
  Version                       IdeaPad L340-15IRH Gaming
  Serial Number                 PF21HKS3
  UUID                          00000000-0000-0000-0000-000000000000
  Wakeup Type                   Power Switch
  SKUNumber                     LENOVO_MT_81LK_BU_idea_FM_IdeaPad L340-15IRH Gaming
  Family                        IdeaPad L340-15IRH Gaming

I can also see that the version of the Nvidia graphics driver that you have installed is very recent...

2: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff803`8f670000 fffff803`930c6000   nvlddmkm T (no symbols)          
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\System32\DriverStore\FileRepository\nvltig.inf_amd64_98aa0424e64f7757\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Mar  1 19:55:35 2024 (65E21697)
    CheckSum:         0393217E
    ImageSize:        03A56000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

That tells me that this is a generic driver downloaded from the Nvidia website and that may be the problem. Laptop vendors usually use customised versions of graphics drivers, both for power-saving reasons and for operability reasons. Generic graphics drivers from Nvidia (and Intel) do not contain the needed customisations and this does sometimes cause problems and BSODs.

The graphics drivers on the Lenovo website for you laptop are dated November 2020 (Nvidia) and November 2019 (Intel), and although these are old I strongly suggest that you install these drivers - both the Nvidia driver AND the Intel driver because these are guaranteed to be compatible with your laptop. On laptops the dGPU and iGPU generally work hand-in-hand, so it's important that both drivers are fully compatible.

I suggest you use DDU first to remove all traces of the existing Nvidia driver. Uninstall the Intel driver via Device Manager and reboot. Then install the Intel graphics driver and then the Nvidia graphics driver, both downloaded from the Lenovo website. If you no longer get BSODs then the problem was lack of the necessary customisations in the generic Nvidia (or Intel) graphics drivers.