Ryzen 5 1600 ve GTX 1050 Ti sistem, anakart değişikliği sonrası "Video scheduler internal error" hatası

Daha demin hem underclock hem overclock denedim bir sonuca ulaşamadım. İlginç olan ise GPU boştayken 600 MHz de çalışıyor. Eskiden hep 1303 MHz de çalışırdı yükte 1800MHz olurdu. Bu ekran siyah olurken yani nvlddmkm hatası olurken 1303 MHz ye anlık çıkıp inmesi de bir garip.
Eğer Afterburner ile ayarları geri döndürsen bile mavi ekran almaya devam ediyorsan DDU ile sürücüyü kaldır tekrar yükle.
11W'lık fark ile problem olacağını sanmıyorum.
 
Önereceğim bir versiyon yok, eğer overclock veya underclock yapılmadığı halde mavi ekran veriyorsa kart arızalı olabilir
Neden eskiden vermiyor diye sorarsanız, "G4560" baya güçsüz bir işlemci, kart bu işlemci ile darboğaz yaşadığı için kart hiçbir zaman tam gücünde çalışmamış olabilir.
 
Önereceğim bir versiyon yok, eğer overclock veya underclock yapılmadığı halde mavi ekran veriyorsa kart arızalı olabilir
Neden eskiden vermiyor diye sorarsanız, "G4560" baya güçsüz bir işlemci, kart bu işlemci ile darboğaz yaşadığı için kart hiçbir zaman tam gücünde çalışmamış olabilir.
Tam mavi ekran olmuyor dediğimde gene başladı. Güvenli modda girmek zorunda kaldım.
Kartı sistem ile birlikte itopyadan 19-06-2017 de aldım. Faturası kayboldu ama elimde olsaydı bile garantisinin kalacağını düşünmüyorum. O yüzden bu durum bir çıkmaz sokak galiba
 
Olabilir, maalesef farklı bir çözüm yolu bilmiyorum.
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: fffffe895fe7b960
Arg4: ffffad8a063f7bd0

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

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

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:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME:  B450M S2H

SYSTEM_SKU:  Default string

SYSTEM_VERSION:  Default string

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  F41

BIOS_DATE:  07/22/2019

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  B450M S2H

BASEBOARD_VERSION:  x.x

DUMP_TYPE:  2

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: fffffe895fe7b960

BUGCHECK_P4: ffffad8a063f7bd0

CPU_COUNT: c

CPU_MHZ: c7a

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

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:  12-27-2019 22:26:13.0560

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff8054b1d41a0 to fffff805403c14e0

STACK_TEXT: 
fffffe89`5fe7b888 fffff805`4b1d41a0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffffe89`5fe7b960 : nt!KeBugCheckEx
fffffe89`5fe7b890 fffff805`4de0abf8 : 00000000`00000000 ffffad8a`063f5000 fffffe89`5fe7b999 ffffad8a`063f5000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffffe89`5fe7b8d0 fffff805`4de68684 : ffffad8a`00000000 ffffad8a`063f7bd0 ffffad8a`0632e000 ffffad8a`0808e9a0 : dxgmms2!VidSchiSendToExecutionQueue+0x14a08
fffffe89`5fe7ba00 fffff805`4de79ad5 : ffffad8a`062db9a0 ffffad8a`0632e000 00000000`00000000 ffffad8a`063c3620 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
fffffe89`5fe7bb80 fffff805`4de7994a : ffffad8a`0632e400 fffff805`4de79880 ffffad8a`0632e000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
fffffe89`5fe7bbd0 fffff805`4032a7a5 : ffffad8a`0638a680 fffff805`00000001 ffffad8a`0632e000 00000067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
fffffe89`5fe7bc10 fffff805`403c8b2a : ffff9881`4b7a0180 ffffad8a`0638a680 fffff805`4032a750 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffffe89`5fe7bc60 00000000`00000000 : fffffe89`5fe7c000 fffffe89`5fe76000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


THREAD_SHA1_HASH_MOD_FUNC:  3c3aefa711a40e43478598e53abd6873e0c9ed57

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  2831a16f72eb580b94422779b5b1b484064cfb6f

THREAD_SHA1_HASH_MOD:  8bc3a1490ebecb3d757d5cd2041e6cd7da5819c4

FOLLOWUP_IP:
dxgmms2!VidSchiSendToExecutionQueue+14a08
fffff805`4de0abf8 cc              int     3

FAULT_INSTR_CODE:  b60f41cc

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+14a08

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:  14a08

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:  2019-12-27T19:17:30.000Z

OSBUILD:  18362

OSSERVICEPACK:  535

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  1980-01-11 18:53:20

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  820b

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
---------
 
Olabilir, maalesef farklı bir çözüm yolu bilmiyorum.
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: fffffe895fe7b960
Arg4: ffffad8a063f7bd0

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

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

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:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME:  B450M S2H

SYSTEM_SKU:  Default string

SYSTEM_VERSION:  Default string

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  F41

BIOS_DATE:  07/22/2019

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  B450M S2H

BASEBOARD_VERSION:  x.x

DUMP_TYPE:  2

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: fffffe895fe7b960

BUGCHECK_P4: ffffad8a063f7bd0

CPU_COUNT: c

CPU_MHZ: c7a

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

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:  12-27-2019 22:26:13.0560

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff8054b1d41a0 to fffff805403c14e0

STACK_TEXT:
fffffe89`5fe7b888 fffff805`4b1d41a0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffffe89`5fe7b960 : nt!KeBugCheckEx
fffffe89`5fe7b890 fffff805`4de0abf8 : 00000000`00000000 ffffad8a`063f5000 fffffe89`5fe7b999 ffffad8a`063f5000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffffe89`5fe7b8d0 fffff805`4de68684 : ffffad8a`00000000 ffffad8a`063f7bd0 ffffad8a`0632e000 ffffad8a`0808e9a0 : dxgmms2!VidSchiSendToExecutionQueue+0x14a08
fffffe89`5fe7ba00 fffff805`4de79ad5 : ffffad8a`062db9a0 ffffad8a`0632e000 00000000`00000000 ffffad8a`063c3620 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
fffffe89`5fe7bb80 fffff805`4de7994a : ffffad8a`0632e400 fffff805`4de79880 ffffad8a`0632e000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
fffffe89`5fe7bbd0 fffff805`4032a7a5 : ffffad8a`0638a680 fffff805`00000001 ffffad8a`0632e000 00000067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
fffffe89`5fe7bc10 fffff805`403c8b2a : ffff9881`4b7a0180 ffffad8a`0638a680 fffff805`4032a750 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffffe89`5fe7bc60 00000000`00000000 : fffffe89`5fe7c000 fffffe89`5fe76000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


THREAD_SHA1_HASH_MOD_FUNC:  3c3aefa711a40e43478598e53abd6873e0c9ed57

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  2831a16f72eb580b94422779b5b1b484064cfb6f

THREAD_SHA1_HASH_MOD:  8bc3a1490ebecb3d757d5cd2041e6cd7da5819c4

FOLLOWUP_IP:
dxgmms2!VidSchiSendToExecutionQueue+14a08
fffff805`4de0abf8 cc              int     3

FAULT_INSTR_CODE:  b60f41cc

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+14a08

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:  14a08

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:  2019-12-27T19:17:30.000Z

OSBUILD:  18362

OSSERVICEPACK:  535

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  1980-01-11 18:53:20

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  820b

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
---------
Sorunun kaynağını buldum galiba. RAM'im B450M S2H'ın 1. nesil destek listesinde var iken 2. nesil destek listesinde yok. Bendeki Ryzen 5 1600 revizyonlu 12nm model olduğu için 2. nesil geçiyor cpu z de. Bugün 1050 Ti'ı başka bir sistemde denemeye çalışacağım. Orada sorunsuz çalışırsa demekki sorunun kaynağının RAM olduğunu anlarız
Olabilir, maalesef farklı bir çözüm yolu bilmiyorum.
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: fffffe895fe7b960
Arg4: ffffad8a063f7bd0

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

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

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:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME:  B450M S2H

SYSTEM_SKU:  Default string

SYSTEM_VERSION:  Default string

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  F41

BIOS_DATE:  07/22/2019

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  B450M S2H

BASEBOARD_VERSION:  x.x

DUMP_TYPE:  2

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: fffffe895fe7b960

BUGCHECK_P4: ffffad8a063f7bd0

CPU_COUNT: c

CPU_MHZ: c7a

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

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:  12-27-2019 22:26:13.0560

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff8054b1d41a0 to fffff805403c14e0

STACK_TEXT:
fffffe89`5fe7b888 fffff805`4b1d41a0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffffe89`5fe7b960 : nt!KeBugCheckEx
fffffe89`5fe7b890 fffff805`4de0abf8 : 00000000`00000000 ffffad8a`063f5000 fffffe89`5fe7b999 ffffad8a`063f5000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffffe89`5fe7b8d0 fffff805`4de68684 : ffffad8a`00000000 ffffad8a`063f7bd0 ffffad8a`0632e000 ffffad8a`0808e9a0 : dxgmms2!VidSchiSendToExecutionQueue+0x14a08
fffffe89`5fe7ba00 fffff805`4de79ad5 : ffffad8a`062db9a0 ffffad8a`0632e000 00000000`00000000 ffffad8a`063c3620 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
fffffe89`5fe7bb80 fffff805`4de7994a : ffffad8a`0632e400 fffff805`4de79880 ffffad8a`0632e000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
fffffe89`5fe7bbd0 fffff805`4032a7a5 : ffffad8a`0638a680 fffff805`00000001 ffffad8a`0632e000 00000067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
fffffe89`5fe7bc10 fffff805`403c8b2a : ffff9881`4b7a0180 ffffad8a`0638a680 fffff805`4032a750 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffffe89`5fe7bc60 00000000`00000000 : fffffe89`5fe7c000 fffffe89`5fe76000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


THREAD_SHA1_HASH_MOD_FUNC:  3c3aefa711a40e43478598e53abd6873e0c9ed57

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  2831a16f72eb580b94422779b5b1b484064cfb6f

THREAD_SHA1_HASH_MOD:  8bc3a1490ebecb3d757d5cd2041e6cd7da5819c4

FOLLOWUP_IP:
dxgmms2!VidSchiSendToExecutionQueue+14a08
fffff805`4de0abf8 cc              int     3

FAULT_INSTR_CODE:  b60f41cc

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+14a08

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:  14a08

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:  2019-12-27T19:17:30.000Z

OSBUILD:  18362

OSSERVICEPACK:  535

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  1980-01-11 18:53:20

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  820b

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
---------
 
Son düzenleme:
Uyarı! Bu konu 6 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.

Technopat Haberler

Yeni konular

Geri
Yukarı