VIDEO_SCHEDULER_INTERNAL_ERROR mavi ekran hatası

Katılım
26 Eylül 2019
Mesajlar
1.255
Çözümler
15
Minidump :



Wİndows 10 64 bit
GTX 1070
i7 - 6700K
16 GB DDR4 2400 Mhz

2 gün önce ekran kartı sürücüsünü DDU ile kaldırıp temiz kurulum yaptım. Ondan önce de benzer sorunlar oldu.

Not : 2-3 haftadır, ara ara farklı isimlerde mavi ekranlar almaya başladım. Hala uğraşıyorum.
 
Son düzenleme:
MSI, Intel(R) Extreme Tuning Utility Performance Tuning programlarını kaldır.
BIOS'a gir Load Defaults yap kaydet çık.

DDU ile ekran kartı sürücüsünü kaldır tekrar yükle.
Kod:
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: fffff90741ebf860
Arg4: ffff870f41a21490

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.18362.657 (WinBuild.160101.0800)

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

DUMP_TYPE:  2

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: fffff90741ebf860

BUGCHECK_P4: ffff870f41a21490

CPU_COUNT: 4

CPU_MHZ: fa8

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x119

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-24-2020 16:18:07.0605

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff803d47d419b to fffff8075c47f510

STACK_TEXT: 
fffff907`41ebf788 fffff803`d47d419b : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffff907`41ebf860 : nt!KeBugCheckEx
fffff907`41ebf790 fffff803`d8e6abf3 : 00000000`00000000 ffff870f`41a1e000 ffff870f`41a1e000 ffff870f`41a21490 : watchdog!WdLogEvent5_WdCriticalError+0xdb
fffff907`41ebf7d0 fffff803`d8ec8684 : ffff870f`00000000 ffff870f`41a21490 ffff870f`3fa83000 ffff870f`46191010 : dxgmms2!VidSchiSendToExecutionQueue+0x14a03
fffff907`41ebf900 fffff803`d8ed9ad5 : ffff870f`3fa7e030 ffff870f`3fa83000 00000000`00000000 ffff870f`43011010 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
fffff907`41ebfa80 fffff803`d8ed994a : ffff870f`3fa83400 fffff803`d8ed9880 ffff870f`3fa83000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
fffff907`41ebfad0 fffff807`5c3e87b5 : ffff870f`3f328080 fffff803`00000001 ffff870f`3fa83000 000024ef`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
fffff907`41ebfb10 fffff807`5c486b5a : fffff807`5b1a1180 ffff870f`3f328080 fffff807`5c3e8760 80c731ae`67688865 : nt!PspSystemThreadStartup+0x55
fffff907`41ebfb60 00000000`00000000 : fffff907`41ec0000 fffff907`41eb9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


THREAD_SHA1_HASH_MOD_FUNC:  3c3aefa711a40e43478598e53abd6873e0c9ed57

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  b0798598a3d0c0aacb26e6081fa232ada8a3b240

THREAD_SHA1_HASH_MOD:  8bc3a1490ebecb3d757d5cd2041e6cd7da5819c4

FOLLOWUP_IP:
dxgmms2!VidSchiSendToExecutionQueue+14a03
fffff803`d8e6abf3 0f1f440000      nop     dword ptr [rax+rax]

FAULT_INSTR_CODE:  441f0f

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+14a03

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.18362.449

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  14a03

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

PRIMARY_PROBLEM_CLASS:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

TARGET_TIME:  2020-02-24T12:58:09.000Z

OSBUILD:  18362

OSSERVICEPACK:  657

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  2005-04-23 04:40:32

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.18362.657

ANALYSIS_SESSION_ELAPSED_TIME:  a8f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x119_2_driver_failed_submit_command_dxgmms2!vidschisendtoexecutionqueue

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

Followup:     MachineOwner
---------
 
MSI, Intel(R) Extreme Tuning Utility Performance Tuning programlarını kaldır.
BIOS'a gir Load Defaults yap kaydet çık.

DDU ile ekran kartı sürücüsünü kaldır tekrar yükle.
Kod:
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: fffff90741ebf860
Arg4: ffff870f41a21490

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.18362.657 (WinBuild.160101.0800)

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

DUMP_TYPE:  2

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: fffff90741ebf860

BUGCHECK_P4: ffff870f41a21490

CPU_COUNT: 4

CPU_MHZ: fa8

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x119

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-24-2020 16:18:07.0605

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff803d47d419b to fffff8075c47f510

STACK_TEXT:
fffff907`41ebf788 fffff803`d47d419b : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffff907`41ebf860 : nt!KeBugCheckEx
fffff907`41ebf790 fffff803`d8e6abf3 : 00000000`00000000 ffff870f`41a1e000 ffff870f`41a1e000 ffff870f`41a21490 : watchdog!WdLogEvent5_WdCriticalError+0xdb
fffff907`41ebf7d0 fffff803`d8ec8684 : ffff870f`00000000 ffff870f`41a21490 ffff870f`3fa83000 ffff870f`46191010 : dxgmms2!VidSchiSendToExecutionQueue+0x14a03
fffff907`41ebf900 fffff803`d8ed9ad5 : ffff870f`3fa7e030 ffff870f`3fa83000 00000000`00000000 ffff870f`43011010 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
fffff907`41ebfa80 fffff803`d8ed994a : ffff870f`3fa83400 fffff803`d8ed9880 ffff870f`3fa83000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
fffff907`41ebfad0 fffff807`5c3e87b5 : ffff870f`3f328080 fffff803`00000001 ffff870f`3fa83000 000024ef`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
fffff907`41ebfb10 fffff807`5c486b5a : fffff807`5b1a1180 ffff870f`3f328080 fffff807`5c3e8760 80c731ae`67688865 : nt!PspSystemThreadStartup+0x55
fffff907`41ebfb60 00000000`00000000 : fffff907`41ec0000 fffff907`41eb9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


THREAD_SHA1_HASH_MOD_FUNC:  3c3aefa711a40e43478598e53abd6873e0c9ed57

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  b0798598a3d0c0aacb26e6081fa232ada8a3b240

THREAD_SHA1_HASH_MOD:  8bc3a1490ebecb3d757d5cd2041e6cd7da5819c4

FOLLOWUP_IP:
dxgmms2!VidSchiSendToExecutionQueue+14a03
fffff803`d8e6abf3 0f1f440000      nop     dword ptr [rax+rax]

FAULT_INSTR_CODE:  441f0f

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+14a03

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.18362.449

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  14a03

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

PRIMARY_PROBLEM_CLASS:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

TARGET_TIME:  2020-02-24T12:58:09.000Z

OSBUILD:  18362

OSSERVICEPACK:  657

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  2005-04-23 04:40:32

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.18362.657

ANALYSIS_SESSION_ELAPSED_TIME:  a8f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x119_2_driver_failed_submit_command_dxgmms2!vidschisendtoexecutionqueue

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

Followup:     MachineOwner
---------
Şuan bilgisayar açılmadan hemen önce mavi ekran veriyor, sadece başlangıç kurtarma ve bios'a girebiliyorum. Güvenli modu da çalistiramadim. Hata kodu; "Critical Process Died". Format usb belleği ayarladim format atacam artik.
 
GPU ve kasa bakımı yapılmadıysa yapıp format sonrası kontrol edin.

Kasanin içi temiz, orijinal Windows son sürüm kurdum, şu an gıcır gıcır. Öncesinde kayıt defteri falan bayağı bir değişiklik yapmıştım. Bir de Windows crackli olunca hepsi patlak verdi sanırım.
 
Kasanin içi temiz, orijinal Windows son sürüm kurdum, şu an gıcır gıcır. Öncesinde kayıt defteri falan bayağı bir değişiklik yapmıştım. Bir de Windows crackli olunca hepsi patlak verdi sanırım.
Bir kaç gün kullanın, donanımsal sorun ise yine patlak verir zaten. O zaman ekran kartında sorun olabildiğini anlarsınız.
 
Uyarı! Bu konu 5 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Geri
Yukarı