3070 ekran kartlı sistemde mavi ekran hatası

*******************************************************************************
*                                                                             *
*                        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: 0000000000000017, Unexpected system command failure.
Arg2: ffffffffc000000d
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2031

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 33241

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

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

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

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x10e

    Key  : Bugcheck.Code.Register
    Value: 0x10e

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  041423-14609-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  10e

BUGCHECK_P1: 17

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: 0

BUGCHECK_P4: 0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffb90c`18bba868 fffff802`7f3b3ad0     : 00000000`0000010e 00000000`00000017 ffffffff`c000000d 00000000`00000000 : nt!KeBugCheckEx
ffffb90c`18bba870 fffff802`8dfba037     : ffffbb0e`65e2ff40 ffffbb0e`67f3a698 ffff8803`00000000 ffffbb0e`67f3a698 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffb90c`18bba8b0 fffff802`8dfba610     : ffffbb0e`65e2fe00 00000000`00000000 ffffbb0e`67f3a698 ffffb90c`18bba980 : dxgmms2!VIDMM_WORKER_THREAD::FlushEvictQueue+0x133
ffffb90c`18bba900 fffff802`8dfba37e     : ffff8803`ab9b4c60 ffff8803`ab9b4c60 00000000`00000000 ffffbb0e`65e2feb0 : dxgmms2!VIDMM_WORKER_THREAD::ProcessEvictQueues+0xcc
ffffb90c`18bba930 fffff802`8df9bb35     : ffffbb0e`a8688000 fffff802`8df443c8 ffffbb0e`a86880f0 00000000`00000000 : dxgmms2!VIDMM_WORKER_THREAD::HandleRecoverablePageInFailure+0xf6
ffffb90c`18bba9c0 fffff802`8df96839     : ffffbb0e`65e2feb0 ffff8803`ae4ce201 00000000`00000001 00000000`0661c400 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x10305
ffffb90c`18bbaba0 fffff802`6fc55485     : ffff8803`ae4ce280 fffff802`8df96830 ffffbb0e`65e2feb0 000fe067`bcbbbdff : dxgmms2!VidMmWorkerThreadProc+0x9
ffffb90c`18bbabd0 fffff802`6fe02d48     : ffffdf01`f788a180 ffff8803`ae4ce280 fffff802`6fc55430 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffb90c`18bbac20 00000000`00000000     : ffffb90c`18bbb000 ffffb90c`18bb4000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  dxgmms2!VIDMM_WORKER_THREAD::FlushEvictQueue+133

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.2311

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  133

FAILURE_BUCKET_ID:  0x10e_17_dxgmms2!VIDMM_WORKER_THREAD::FlushEvictQueue

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {8b70aac8-c9b8-15d4-254c-a3e0828fa53b}

Followup:     MachineOwner