Çözüldü "Bu bilgisayar bir hata denetiminde yeniden başlatıldı" hatası

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: fffffe80cdb4f960
Arg4: ffffbd0fe83a5590

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5780

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-G25IS1E

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 30150

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: fffffe80cdb4f960

BUGCHECK_P4: ffffbd0fe83a5590

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffffe80`cdb4f888 fffff804`87643ad0     : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffffe80`cdb4f960 : nt!KeBugCheckEx
fffffe80`cdb4f890 fffff804`8983bba1     : 00000000`00000000 ffffbd0f`e83a2000 fffffe80`cdb4f999 ffffbd0f`e83a2000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffffe80`cdb4f8d0 fffff804`898a30bd     : ffffbd0f`00000000 ffffbd0f`e83a5590 ffffbd0f`e829d000 ffffbd0f`f19f4010 : dxgmms2!VidSchiSendToExecutionQueue+0x12761
fffffe80`cdb4fa00 fffff804`898aae8a     : ffffbd0f`f19f4010 ffffbd0f`e829d000 00000000`00000000 ffffbd0f`ee4e44e0 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
fffffe80`cdb4fb80 fffff804`898aacfa     : ffffbd0f`e829d400 fffff804`898aac30 ffffbd0f`e829d000 ffffa201`944cf100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
fffffe80`cdb4fbd0 fffff804`7a0a29a5     : ffffbd0f`e680b080 fffff804`00000001 ffffbd0f`e829d000 000f8067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
fffffe80`cdb4fc10 fffff804`7a1fc868     : ffffa201`944cf180 ffffbd0f`e680b080 fffff804`7a0a2950 e3c558a8`c64cbee2 : nt!PspSystemThreadStartup+0x55
fffffe80`cdb4fc60 00000000`00000000     : fffffe80`cdb50000 fffffe80`cdb4a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+12761

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.1124

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  12761

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9a11bf9c-270e-962e-7a82-3efdab93c10e}

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