[Miguelos]

Mam problem z moim Lenovo L340-15IRH. Losowo, czasami trzy razy na dzień, czasami trzy razy w tygodniu wyskakuje mi Blue Screen VIDEO MEMORY MANAGEMENT INTERNAL (10E) dxgmms2.sys. Bez znaczenia czy gram, czy przeglądam Internet.
Konfiguracja:
i5-9300H
Intel UHD Graphics 630
Nvidia GeForce GTX 1650
8 Gb RAM
Windows 10

Co zrobiłem to:
1.Przeinstalowanie sterowników do obu kart graficznych (DDU uninstaller również był próbowany)
2.Update Windowsa do najnowszych wersji
3.Update BIOSa
4.Kompletne przeinstalowanie systemu wraz z formatowaniem.

I już myślałem że jest dobrze po przeinstalowaniu, bo przez prawie pięć dni komputer działał poprawnie. I nagle znowu ten Blue Screen. Ktoś ma jakieś pomysł? Podejrzewam że mam uszkodzony hardware i pozostało mi kupić nowego laptopa...
Poniżej zamieszczam Minidump, a tu link do ściągnięcia pliku: https://files.fm/u/3arznx4ssh
Może ktoś ma jakiś pomysł, mi już brak sił... dzięki za pomoc.

*******************************************************************************
* *
* 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:
ffffb504bfe79e08 fffff80241b43ad0 : 000000000000010e 000000000000002d ffffe28a26444830 ffffe28a2b370610 : nt!KeBugCheckEx
ffffb504bfe79e10 fffff80254c192b1 : ffffe28a2b370610 0000000000000001 0000000000000001 fffff802294452a3 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffb504bfe79e50 fffff80254c9ec15 : ffffe28a2b370610 ffffe28a26444830 ffffe28a26444830 0000000000000000 : dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange+0x24d
ffffb504bfe79ed0 fffff80254c8ebe5 : ffffe28a26425810 ffffb504bfe79fe0 0000000000000000 ffffb504bfe7a0b8 : dxgmms2!VIDMM_GLOBAL::BuildMdlForAllocInCpuHostAperture+0xe5
ffffb504bfe79f10 fffff80254c61d84 : 0000000000000000 0000000000000002 ffffba0d00dbf000 ffffe28a26425810 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress+0x2ce41
ffffb504bfe79f50 fffff80254c51a1a : 0000000000000000 ffffe28a2b370830 0000000000000002 ffffba0cf704fe10 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetDriverUpdateAddress+0xb8
ffffb504bfe79fe0 fffff80254c8ef68 : 0000000000000000 0000000000000000 0000000000000002 ffffb504bfe7a560 : dxgmms2!VIDMM_PAGE_TABLE::UpdatePageTableInvalidate+0x4a
ffffb504bfe7a0b0 fffff80254c60092 : 0000000000000002 ffffb504bfe7a260 ffffe28a266b1950 0000000000000000 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0x2d080
ffffb504bfe7a150 fffff80254c60226 : 0000000000000002 ffffe28a2aff84f0 ffffb504bfe7a560 0000000000000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x872
ffffb504bfe7a2f0 fffff80254c5f24e : 0000000000000000 ffffe28a2aff84f0 ffffb504bfe7a560 0000000000000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0xa06
ffffb504bfe7a490 fffff80254c9d9f0 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x2f6
ffffb504bfe7a610 fffff80254c8b7c2 : 0000000000000000 0000000000000000 0000000000000076 ffffe28a3358d810 : dxgmms2!VIDMM_GLOBAL::InitPagingProcessVaSpace+0x17470
ffffb504bfe7a780 fffff80254c7d712 : ffffe28a2aff7730 ffffb50400000001 0000000000000001 ffffe28a296a6f20 : dxgmms2!VIDMM_GLOBAL::ProcessSystemCommand+0x34312
ffffb504bfe7a900 fffff80254c872b9 : ffffe28a296a6eb0 ffffba0cfe09b001 0000000000000100 000000000668b600 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x1462
ffffb504bfe7aae0 fffff802295078c5 : ffffba0cfe09b080 fffff80254c872b0 ffffe28a296a6eb0 000fa4efbd9bbfff : dxgmms2!VidMmWorkerThreadProc+0x9
ffffb504bfe7ab10 fffff802296067b8 : ffffcc0188280180 ffffba0cfe09b080 fffff80229507870 0bb8180094042a03 : nt!PspSystemThreadStartup+0x55
ffffb504bfe7ab60 0000000000000000 : ffffb504bfe7b000 ffffb504bfe74000 0000000000000000 0000000000000000 : 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
---------
#komputery #technologia #windows #windows10 #pomocy #pomoc #pustulkowelaptopy #laptopy #laptop #pytanie #pytaniedoeksperta #kiciochpyta

[vulcanitu]

@Miguelos: może i jakaś wada sprzętowa, brat ma ten sam model, u niego wywalało biały ekran przy grach, nie wykminiłem jak to naprawić niestety