Çözüldü MSI GE67hx VIDEO_SCHEDULER_INTERNAL_ERROR (119) hatası

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

tanil gozdemir

Kilopat
Katılım
27 Kasım 2014
Mesajlar
158
Çözümler
1
Daha fazla  
Cinsiyet
Erkek
Meslek
Uzay ve Havacılık Mühendisliği Öğrencisi
RAM
SAMSUNG 32 GB(16x2) DDR5 ram
SSD veya HDD modeli
Samsung 980 pro(OEM varyantı)
Ekran kartı
RTX 3070 ti mobile(laptop)
İşlemci
i7 12800hx(laptop)
MSI GE67 12ugs laptopumda mavi ekran hatası aldım (daha önce de buna benzer mavi ekran hataları alıyordum). En son buna benzer bir hata aldığımda grafik kartının sürücüsünü DDU programı ile kaldırıp, NVIDIA'nın en son WHQL sürücüsünü kurmama rağmen yine bir mavi ekran hatası aldım.

Minidump dosyası: 061723-9203-01.dmp
 
Çözüm
BIOS sürümü aynı ama tarihi 2023 gözüküyor. Sizdeki sürüm. 109 olarak belirtilmiş sitesinde ise. 10A şeklinde bir BIOS bulunuyor.


Intel' e ait sürücüleri bu uygulama ile güncelleyin.


Thunderbolt sürücüsünü yükleyin.


Son olarak ekran kartı sürücüsünü yakın zamanda kaldıramadıysan tekrar DDU ile kaldırıp, tekrar indirip yükleyin.

Kod:
13: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: ffff910cf19207f0
Arg4: ffffa48e10f0aa00

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

*** WARNING: Check Image - Checksum mismatch - Dump: 0x629f6, File: 0x62ad2 - C:\ProgramData\Dbg\sym\srvnet.sys\43865A855a000\srvnet.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3608

    Key  : Analysis.Elapsed.mSec
    Value: 27890

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x119

    Key  : Failure.Bucket
    Value: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

    Key  : Failure.Hash
    Value: {9a11bf9c-270e-962e-7a82-3efdab93c10e}

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Version
    Value: 10.0.22000.1


BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffff910cf19207f0

BUGCHECK_P4: ffffa48e10f0aa00

FILE_IN_CAB:  061723-9203-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffff910c`f19206a8 fffff805`2d06529a     : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff910c`f19207f0 : nt!KeBugCheckEx
ffff910c`f19206b0 fffff805`4de11f58     : 00000000`00000008 00000000`00000000 00000000`00000000 ffffa48e`10f07000 : watchdog!WdLogSingleEntry5+0x39aa
ffff910c`f1920740 fffff805`4de84bcd     : ffffa48e`00000000 ffffa48e`10f0aa00 ffffa48e`10e4b000 ffffa48e`1e546050 : dxgmms2!VidSchiSendToExecutionQueue+0x1aee8
ffff910c`f1920910 fffff805`4de9e05a     : ffffa48e`1e546050 ffffa48e`10e4b000 00000000`00000000 ffffa48e`10f662e0 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffff910c`f1920aa0 fffff805`4de9deca     : ffffa48e`10e4b400 fffff805`4de9de00 ffffa48e`10e4b000 00000000`00050200 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffff910c`f1920af0 fffff805`12d647a5     : ffffa48e`10ec9480 fffff805`00000001 ffffa48e`10e4b000 006fe47f`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffff910c`f1920b30 fffff805`12e22644     : ffff8081`36240180 ffffa48e`10ec9480 fffff805`12d64750 796c646e`65697246 : nt!PspSystemThreadStartup+0x55
ffff910c`f1920b80 00000000`00000000     : ffff910c`f1921000 ffff910c`f191a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+1aee8

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.22000.2054

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1aee8

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------
BIOS sürümü aynı ama tarihi 2023 gözüküyor. Sizdeki sürüm. 109 olarak belirtilmiş sitesinde ise. 10A şeklinde bir BIOS bulunuyor.


Intel' e ait sürücüleri bu uygulama ile güncelleyin.


Thunderbolt sürücüsünü yükleyin.


Son olarak ekran kartı sürücüsünü yakın zamanda kaldıramadıysan tekrar DDU ile kaldırıp, tekrar indirip yükleyin.

Kod:
13: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: ffff910cf19207f0
Arg4: ffffa48e10f0aa00

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

*** WARNING: Check Image - Checksum mismatch - Dump: 0x629f6, File: 0x62ad2 - C:\ProgramData\Dbg\sym\srvnet.sys\43865A855a000\srvnet.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3608

    Key  : Analysis.Elapsed.mSec
    Value: 27890

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x119

    Key  : Failure.Bucket
    Value: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

    Key  : Failure.Hash
    Value: {9a11bf9c-270e-962e-7a82-3efdab93c10e}

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Version
    Value: 10.0.22000.1


BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffff910cf19207f0

BUGCHECK_P4: ffffa48e10f0aa00

FILE_IN_CAB:  061723-9203-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffff910c`f19206a8 fffff805`2d06529a     : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff910c`f19207f0 : nt!KeBugCheckEx
ffff910c`f19206b0 fffff805`4de11f58     : 00000000`00000008 00000000`00000000 00000000`00000000 ffffa48e`10f07000 : watchdog!WdLogSingleEntry5+0x39aa
ffff910c`f1920740 fffff805`4de84bcd     : ffffa48e`00000000 ffffa48e`10f0aa00 ffffa48e`10e4b000 ffffa48e`1e546050 : dxgmms2!VidSchiSendToExecutionQueue+0x1aee8
ffff910c`f1920910 fffff805`4de9e05a     : ffffa48e`1e546050 ffffa48e`10e4b000 00000000`00000000 ffffa48e`10f662e0 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffff910c`f1920aa0 fffff805`4de9deca     : ffffa48e`10e4b400 fffff805`4de9de00 ffffa48e`10e4b000 00000000`00050200 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffff910c`f1920af0 fffff805`12d647a5     : ffffa48e`10ec9480 fffff805`00000001 ffffa48e`10e4b000 006fe47f`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffff910c`f1920b30 fffff805`12e22644     : ffff8081`36240180 ffffa48e`10ec9480 fffff805`12d64750 796c646e`65697246 : nt!PspSystemThreadStartup+0x55
ffff910c`f1920b80 00000000`00000000     : ffff910c`f1921000 ffff910c`f191a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+1aee8

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.22000.2054

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1aee8

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------
 
Çözüm

Geri
Yukarı