Ekran donması ve VIDEO_SCHEDULER_INTERNAL_ERROR mavi ekran hatası

Cnegzo

Cnegzo

Kilopat
Katılım
6 Aralık 2017
Mesajlar
184
İyi forumlar arkadaşlar. Yeni topladığım sistemde değiştirmediğim 2 parça mevcut güç kaynağı ve ekran kartı. Steam destekli oyunlarda ekran donması oluşuyor. (Oluştuğunda arka planda sesli sohbet yapabiliyorum, elde silah varsa ateş edip şarjör değiştirebiliyorum fakat görüntü donuk halde.) bugün ise mavi ekran hatası verdi. Minidump dosyasını okuyabilecek bilgisi olanlardan rica etsem bir bakabilir mi acaba?

082720-6421-01.dmp

drive.google.com drive.google.com
 
Son düzenleyen: Moderatör:
Tarihe göre sırala Puana göre sırala

Rehber: DDU ile Sürücü Kaldırma Rehberi

Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...
www.technopat.net www.technopat.net

DDU ile ekran kartı sürücüsünü kaldırıp sitesinden WHQL olan sürümünü indirip kurun. HDD Tune ile Bad Sector testi yapın. Sonuçları bizimle paylaşın.

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
İn 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: 0000000000000001, The Driver has reported an invalid fence ID.
Arg2: 000000000038D847
Arg3: 000000000038D84B
Arg4: FFFFC48BB0B6B000

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

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

KEY_VALUES_STRING: 1

Key: Analysis. CPU. MSec
Value: 4828

Key: Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007E on DESKTOP-5DL7M86

Key: Analysis. DebugData
Value: CreateObject

Key: Analysis. DebugModel
Value: CreateObject

Key: Analysis. Elapsed. MSec
Value: 109378

Key: Analysis. Memory. CommitPeak. MB
Value: 88

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: 1

BUGCHECK_P2: 38D847

BUGCHECK_P3: 38D84B

BUGCHECK_P4: FFFFC48BB0B6B000

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
Fffff800'29479868 fffff800'33F23AD0: 00000000'00000119 00000000'00000001 00000000'0038D847 00000000'0038D84B: Nt! KeBugCheckEx
Fffff800'29479870 fffff800'353DDC7D: 00000000'0038D84B 00000000'00000000 00000000'0038D84B fffff800'29479B40: Watchdog! WDLOGEVENT5_WDCRITICALERROR+0xe0
Fffff800'294798B0 fffff800'353cdccb: Ffffc48b'AF4bfbf0 ffffc48b'B0BAC000 ffffc48b'00000001 00000000'00000000: Dxgmms2! VidSchiProcessIsrCompletedPacket+0xfc7D
Fffff800'29479950 fffff800'353cdad1: Ffffc48b'0038D847 ffffc48b'B22242B0 ffffc48b'B0B6B000 fffff800'366DAF17: Dxgmms2! VidSchDdiNotifyInterruptWorker+0x1BB
Fffff800'294799B0 fffff800'33B83633: Ffffc48b'AAF5A030 fffff800'29479A80 ffffc48b'B22242B0 00000000'00000000: Dxgmms2! VidSchDdiNotifyInterrupt+0xd1
Fffff800'29479A00 fffff800'363bdca3: Ffffc48b'AAF5A030 fffff800'29479B09 fffff800'29479C30 ffffc48b'AF002000: Dxgkrnl! DxgNotifyInterruptCB+0x93
Fffff800'29479A30 ffffc48b'AAF5A030: Fffff800'29479B09 fffff800'29479C30 ffffc48b'AF002000 fffff800'363BDC33: Nvlddmkm+0xfdca3
Fffff800'29479A38 fffff800'29479B09: Fffff800'29479C30 ffffc48b'AF002000 fffff800'363BDC33 ffffc48b'AF002000 : 0xffffc48b`aaf5a030
Fffff800'29479A40 fffff800'29479C30: Ffffc48b'AF002000 fffff800'363BDC33 ffffc48b'AF002000 00000000'00000000 : 0xfffff800`29479b09
Fffff800'29479A48 ffffc48b'AF002000: Fffff800'363BDC33 ffffc48b'AF002000 00000000'00000000 00000000'00000000 : 0xfffff800`29479c30
Fffff800'29479A50 fffff800'363BDC33: Ffffc48b'AF002000 00000000'00000000 00000000'00000000 00000000'00000000 : 0xffffc48b`af002000
Fffff800'29479A58 ffffc48b'AF002000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: Nvlddmkm+0xfdc33
Fffff800'29479A60 00000000'00000000: 00000000'00000000 00000000'00000000 00000000'00000000 ffffc48b'AAF5A030 : 0xffffc48b`af002000

SYMBOL_NAME: Dxgmms2! VidSchiProcessIsrCompletedPacket+FC7D

MODULE_NAME: Dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.450

STACK_COMMAND:. Thread;. Cxr; KB

BUCKET_ID_FUNC_OFFSET: FC7D

FAILURE_BUCKET_ID: 0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_dxgmms2!VidSchiProcessIsrCompletedPacket

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: VB_RELEASE

OSPLATFORM_TYPE: X64

OSNAME: Windows 10

FAILURE_ID_HASH: {28A4E202-EBF8-4B22-8D65-8483A0926371}

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

DirectX'i kaldırıp aşağıdaki linkten yeni sürümü kurun. Sorun devam ederse ekran kartınızı servise gönderin.
 
Son düzenleme:
Artı 0 Eksi
Sorun devam ederse kartınızı servise gönderin.

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: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 000000000038d847
Arg3: 000000000038d84b
Arg4: ffffc48bb0b6b000

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6452

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 68790

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

    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: 1

BUGCHECK_P2: 38d847

BUGCHECK_P3: 38d84b

BUGCHECK_P4: ffffc48bb0b6b000

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
fffff800`29479868 fffff800`33f23ad0     : 00000000`00000119 00000000`00000001 00000000`0038d847 00000000`0038d84b : nt!KeBugCheckEx
fffff800`29479870 fffff800`353ddc7d     : 00000000`0038d84b 00000000`00000000 00000000`0038d84b fffff800`29479b40 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffff800`294798b0 fffff800`353cdccb     : ffffc48b`af4bfbf0 ffffc48b`b0bac000 ffffc48b`00000001 00000000`00000000 : dxgmms2!VidSchiProcessIsrCompletedPacket+0xfc7d
fffff800`29479950 fffff800`353cdad1     : ffffc48b`0038d847 ffffc48b`b22242b0 ffffc48b`b0b6b000 fffff800`366daf17 : dxgmms2!VidSchDdiNotifyInterruptWorker+0x1bb
fffff800`294799b0 fffff800`33b83633     : ffffc48b`aaf5a030 fffff800`29479a80 ffffc48b`b22242b0 00000000`00000000 : dxgmms2!VidSchDdiNotifyInterrupt+0xd1
fffff800`29479a00 fffff800`363bdca3     : ffffc48b`aaf5a030 fffff800`29479b09 fffff800`29479c30 ffffc48b`af002000 : dxgkrnl!DxgNotifyInterruptCB+0x93
fffff800`29479a30 ffffc48b`aaf5a030     : fffff800`29479b09 fffff800`29479c30 ffffc48b`af002000 fffff800`363bdc33 : nvlddmkm+0xfdca3
fffff800`29479a38 fffff800`29479b09     : fffff800`29479c30 ffffc48b`af002000 fffff800`363bdc33 ffffc48b`af002000 : 0xffffc48b`aaf5a030
fffff800`29479a40 fffff800`29479c30     : ffffc48b`af002000 fffff800`363bdc33 ffffc48b`af002000 00000000`00000000 : 0xfffff800`29479b09
fffff800`29479a48 ffffc48b`af002000     : fffff800`363bdc33 ffffc48b`af002000 00000000`00000000 00000000`00000000 : 0xfffff800`29479c30
fffff800`29479a50 fffff800`363bdc33     : ffffc48b`af002000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffc48b`af002000
fffff800`29479a58 ffffc48b`af002000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0xfdc33
fffff800`29479a60 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffc48b`aaf5a030 : 0xffffc48b`af002000


SYMBOL_NAME:  dxgmms2!VidSchiProcessIsrCompletedPacket+fc7d

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.450

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  fc7d

FAILURE_BUCKET_ID:  0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_dxgmms2!VidSchiProcessIsrCompletedPacket

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {28a4e202-ebf8-4b22-8d65-8483a0926371}

Followup:     MachineOwner
---------
 
Artı 0 Eksi
Etandaloth dedi:

Rehber: DDU ile Sürücü Kaldırma Rehberi

Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...
www.technopat.net www.technopat.net

DDU ile ekran kartı sürücüsünü kaldırıp sitesinden WHQL olan sürümünü indirip kurun. HDD Tune ile Bad Sector testi yapın. Sonuçları bizimle paylaşın.

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
İn 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: 0000000000000001, The Driver has reported an invalid fence ID.
Arg2: 000000000038D847
Arg3: 000000000038D84B
Arg4: FFFFC48BB0B6B000

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

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

KEY_VALUES_STRING: 1

Key: Analysis. CPU. MSec
Value: 4828

Key: Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007E on DESKTOP-5DL7M86

Key: Analysis. DebugData
Value: CreateObject

Key: Analysis. DebugModel
Value: CreateObject

Key: Analysis. Elapsed. MSec
Value: 109378

Key: Analysis. Memory. CommitPeak. MB
Value: 88

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: 1

BUGCHECK_P2: 38D847

BUGCHECK_P3: 38D84B

BUGCHECK_P4: FFFFC48BB0B6B000

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
Fffff800'29479868 fffff800'33F23AD0: 00000000'00000119 00000000'00000001 00000000'0038D847 00000000'0038D84B: Nt! KeBugCheckEx
Fffff800'29479870 fffff800'353DDC7D: 00000000'0038D84B 00000000'00000000 00000000'0038D84B fffff800'29479B40: Watchdog! WDLOGEVENT5_WDCRITICALERROR+0xe0
Fffff800'294798B0 fffff800'353cdccb: Ffffc48b'AF4bfbf0 ffffc48b'B0BAC000 ffffc48b'00000001 00000000'00000000: Dxgmms2! VidSchiProcessIsrCompletedPacket+0xfc7D
Fffff800'29479950 fffff800'353cdad1: Ffffc48b'0038D847 ffffc48b'B22242B0 ffffc48b'B0B6B000 fffff800'366DAF17: Dxgmms2! VidSchDdiNotifyInterruptWorker+0x1BB
Fffff800'294799B0 fffff800'33B83633: Ffffc48b'AAF5A030 fffff800'29479A80 ffffc48b'B22242B0 00000000'00000000: Dxgmms2! VidSchDdiNotifyInterrupt+0xd1
Fffff800'29479A00 fffff800'363bdca3: Ffffc48b'AAF5A030 fffff800'29479B09 fffff800'29479C30 ffffc48b'AF002000: Dxgkrnl! DxgNotifyInterruptCB+0x93
Fffff800'29479A30 ffffc48b'AAF5A030: Fffff800'29479B09 fffff800'29479C30 ffffc48b'AF002000 fffff800'363BDC33: Nvlddmkm+0xfdca3
Fffff800'29479A38 fffff800'29479B09: Fffff800'29479C30 ffffc48b'AF002000 fffff800'363BDC33 ffffc48b'AF002000 : 0xffffc48b`aaf5a030
Fffff800'29479A40 fffff800'29479C30: Ffffc48b'AF002000 fffff800'363BDC33 ffffc48b'AF002000 00000000'00000000 : 0xfffff800`29479b09
Fffff800'29479A48 ffffc48b'AF002000: Fffff800'363BDC33 ffffc48b'AF002000 00000000'00000000 00000000'00000000 : 0xfffff800`29479c30
Fffff800'29479A50 fffff800'363BDC33: Ffffc48b'AF002000 00000000'00000000 00000000'00000000 00000000'00000000 : 0xffffc48b`af002000
Fffff800'29479A58 ffffc48b'AF002000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: Nvlddmkm+0xfdc33
Fffff800'29479A60 00000000'00000000: 00000000'00000000 00000000'00000000 00000000'00000000 ffffc48b'AAF5A030 : 0xffffc48b`af002000

SYMBOL_NAME: Dxgmms2! VidSchiProcessIsrCompletedPacket+FC7D

MODULE_NAME: Dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.450

STACK_COMMAND:. Thread;. Cxr; KB

BUCKET_ID_FUNC_OFFSET: FC7D

FAILURE_BUCKET_ID: 0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_dxgmms2!VidSchiProcessIsrCompletedPacket

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: VB_RELEASE

OSPLATFORM_TYPE: X64

OSNAME: Windows 10

FAILURE_ID_HASH: {28A4E202-EBF8-4B22-8D65-8483A0926371}

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

DirectX'i kaldırıp aşağıdaki linkten yeni sürümü kurun. Sorun devam ederse ekran kartınızı servise gönderin.
Genişletmek için tıkla...

DDU ile kurulumu daha önce yapmıştım fakat mavi ekran hatası alıyordum. Bu yüzden sorunun bende olduğunu düşünerek ve temiz bir kurulum için yeni topladığım sistemi kasa dahil bilgisayarcıya vererek kurulum yaptırdım. DirectX'i kaldırmayı bilmiyorum ama araştırıp denerim. HDD taramasını yapmıştım yakın zamanda herhangi bir sorun çıkmadı. Teşekkürler ilgilendiğiniz için.
Recep Baltaş dedi:
Sorun devam ederse kartınızı servise gönderin.

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: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 000000000038d847
Arg3: 000000000038d84b
Arg4: ffffc48bb0b6b000

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6452

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 68790

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

    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: 1

BUGCHECK_P2: 38d847

BUGCHECK_P3: 38d84b

BUGCHECK_P4: ffffc48bb0b6b000

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff800`29479868 fffff800`33f23ad0     : 00000000`00000119 00000000`00000001 00000000`0038d847 00000000`0038d84b : nt!KeBugCheckEx
fffff800`29479870 fffff800`353ddc7d     : 00000000`0038d84b 00000000`00000000 00000000`0038d84b fffff800`29479b40 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffff800`294798b0 fffff800`353cdccb     : ffffc48b`af4bfbf0 ffffc48b`b0bac000 ffffc48b`00000001 00000000`00000000 : dxgmms2!VidSchiProcessIsrCompletedPacket+0xfc7d
fffff800`29479950 fffff800`353cdad1     : ffffc48b`0038d847 ffffc48b`b22242b0 ffffc48b`b0b6b000 fffff800`366daf17 : dxgmms2!VidSchDdiNotifyInterruptWorker+0x1bb
fffff800`294799b0 fffff800`33b83633     : ffffc48b`aaf5a030 fffff800`29479a80 ffffc48b`b22242b0 00000000`00000000 : dxgmms2!VidSchDdiNotifyInterrupt+0xd1
fffff800`29479a00 fffff800`363bdca3     : ffffc48b`aaf5a030 fffff800`29479b09 fffff800`29479c30 ffffc48b`af002000 : dxgkrnl!DxgNotifyInterruptCB+0x93
fffff800`29479a30 ffffc48b`aaf5a030     : fffff800`29479b09 fffff800`29479c30 ffffc48b`af002000 fffff800`363bdc33 : nvlddmkm+0xfdca3
fffff800`29479a38 fffff800`29479b09     : fffff800`29479c30 ffffc48b`af002000 fffff800`363bdc33 ffffc48b`af002000 : 0xffffc48b`aaf5a030
fffff800`29479a40 fffff800`29479c30     : ffffc48b`af002000 fffff800`363bdc33 ffffc48b`af002000 00000000`00000000 : 0xfffff800`29479b09
fffff800`29479a48 ffffc48b`af002000     : fffff800`363bdc33 ffffc48b`af002000 00000000`00000000 00000000`00000000 : 0xfffff800`29479c30
fffff800`29479a50 fffff800`363bdc33     : ffffc48b`af002000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffc48b`af002000
fffff800`29479a58 ffffc48b`af002000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0xfdc33
fffff800`29479a60 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffc48b`aaf5a030 : 0xffffc48b`af002000


SYMBOL_NAME:  dxgmms2!VidSchiProcessIsrCompletedPacket+fc7d

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.450

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  fc7d

FAILURE_BUCKET_ID:  0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_dxgmms2!VidSchiProcessIsrCompletedPacket

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {28a4e202-ebf8-4b22-8d65-8483a0926371}

Followup:     MachineOwner
---------
Genişletmek için tıkla...

Ekran kartını alalı yaklaşık 3 yıl oldu servis ilgileniyor mu bilgim yok ama araştırırım. Ekran kartımdan kaynaklanan herhangi bir sorun olup olmadığını nasıl anlarım acaba bir yolu var mı? FurMark stress testi gibi programlar ile tespit sağlanır mı? teşekkürler ilgilendiğiniz için.
 
Son düzenleme:
Artı 0 Eksi

Benzer konular

Kalanlı Bölme
  • Çözüldü
Çözüldü  Ekran donması ve mavi ekran sorunu
Mesaj
1
Görüntüleme
417
Kalanlı Bölme
Kalanlı Bölme
J
  • Soru
VIDEO_SCHEDULER_INTERNAL_ERROR mavi ekran hatası
Mesaj
2
Görüntüleme
126
JcMaxwell
J
serkanxa
  • Soru
VIDEO_SCHEDULER_INTERNAL_ERROR mavi ekran hatası
2 3
Mesaj
24
Görüntüleme
379
serkanxa
serkanxa
srfayhn
  • Soru
VIDEO_SCHEDULER_INTERNAL_ERROR mavi ekran hatası
Mesaj
2
Görüntüleme
166
srfayhn
srfayhn
Y
  • Soru
VIDEO_SCHEDULER_INTERNAL_ERROR mavi ekran hatası
Mesaj
5
Görüntüleme
186
EgeN7
EgeN7

Yeni konular

Yeni mesajlar

Geri
Yukarı