VIDEO_SCHEDULER_INTERNAL_ERROR Mavi Ekran Hatası

Katılım
15 Şubat 2014
Mesajlar
1.333
Makaleler
2
Yer
İzmir
Daha fazla  
Cinsiyet
Erkek
Merhabalar. Uzun süredir kullandığım sistemde ilk defa böyle bir sorunla karşılaştım. CSGO oynarken belirli bir süre sonra ekranda çıkan VRAM artifactları ile başlıyor ardından da mavi ekrana geçebiliyor. Sistemde makine öğrenmesinden tutun mining'e kadar her şeyi yaptım, ama hiç bir zaman sıcaklıkların 75'in üzerine çıkmasına izin vermedim. Ekran kartına OC de yaptım, ancak hata verildiğinde sistem stok ayarlardaydı. Yeniden başlatıp tekrar stok ayarlar aldığımda da aynı ekran izleri ve mavi ekran ile karşılaştım zaten. 021021-6546-01. Sistemim aşağıdaki gibi:
  • Ryzen 7 1800X - Kraken X62 ile soğutuluyor
  • Asus Crosshair VI Hero
  • 32GB (4x8GB) 3000MHz TridentZ RAM (böyle tek SKEU var sanırım, ancak daha fazla detay gerekirse modeline bakabilrim)
  • Samsung 960 EVO 500GB SSD (CrystalDiskInfo 96% sağlıkta gösteriyor)
  • ASUS ROG Standart (Advanced veya OC modeli değil) GTX1080Ti
Ne olur ne olmaz temiz kurulum yapıyorum şimdi. Her şeyi kurduktan sonra tekrar CSGO deneyip sorun duruyor mu belirtirim. Her türlü yardımınız için şimdiden teşekkürler.
 
Son düzenleyen: Moderatör:
Dosyalarınızı inceledim. Ekran kartı sürücünüzden veri alınamamış. Ekran kartı sürücüsü sıkıntı çıkarmış. DDU ile kaldırıp yeniden yükleyelim. OC yaptıysanız ekran kartındaki OCyi kaldırınız, o da uyumsuzluk yapmış olabilir.
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\hazar\Downloads\021021-6546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`46a00000 PsLoadedModuleList = 0xfffff805`4762a390
Debug session time: Wed Feb 10 19:53:35.491 2021 (UTC + 3:00)
System Uptime: 0 days 0:16:16.204
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`46df5a80 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff805`4d449930=0000000000000119
0: 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: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 00000000000182d3
Arg3: 00000000000182f2
Arg4: ffff9c8c3e2f6000

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

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on VOSTRO-5468

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 84557

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

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: 182d3

BUGCHECK_P3: 182f2

BUGCHECK_P4: ffff9c8c3e2f6000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff805`4d449928 fffff805`53f23ad0 : 00000000`00000119 00000000`00000001 00000000`000182d3 00000000`000182f2 : nt!KeBugCheckEx
fffff805`4d449930 fffff805`552ddc8c : ffff9c8c`3e438000 00000000`000182d3 00000000`00000001 fffff805`587f9fe8 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffff805`4d449970 fffff805`552cd351 : ffff9c8c`000182d3 00000000`00000000 ffff9c8c`3e2f6000 00000000`00000002 : dxgmms2!VidSchDdiNotifyInterruptWorker+0x108fc
fffff805`4d4499d0 fffff805`53b83f33 : ffff9c8c`3ab9a030 ffff7c1d`151dfe57 00000000`00000000 00000000`00000000 : dxgmms2!VidSchDdiNotifyInterrupt+0xd1
fffff805`4d449a20 fffff805`586a9d42 : ffff9c8c`3ab9a030 fffff805`4d449b29 fffff805`4d449c40 ffff9c8c`3aee1000 : dxgkrnl!DxgNotifyInterruptCB+0x93
fffff805`4d449a50 ffff9c8c`3ab9a030 : fffff805`4d449b29 fffff805`4d449c40 ffff9c8c`3aee1000 fffff805`586a9cd2 : nvlddmkm+0x79d42
fffff805`4d449a58 fffff805`4d449b29 : fffff805`4d449c40 ffff9c8c`3aee1000 fffff805`586a9cd2 ffff9c8c`3aee1000 : 0xffff9c8c`3ab9a030
fffff805`4d449a60 fffff805`4d449c40 : ffff9c8c`3aee1000 fffff805`586a9cd2 ffff9c8c`3aee1000 00000000`00000000 : 0xfffff805`4d449b29
fffff805`4d449a68 ffff9c8c`3aee1000 : fffff805`586a9cd2 ffff9c8c`3aee1000 00000000`00000000 00000000`00000000 : 0xfffff805`4d449c40
fffff805`4d449a70 fffff805`586a9cd2 : ffff9c8c`3aee1000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff9c8c`3aee1000
fffff805`4d449a78 ffff9c8c`3aee1000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x79cd2
fffff805`4d449a80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff9c8c`3ab9a030 : 0xffff9c8c`3aee1000


SYMBOL_NAME: dxgmms2!VidSchDdiNotifyInterruptWorker+108fc

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.804

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 108fc

FAILURE_BUCKET_ID: 0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_dxgmms2!VidSchDdiNotifyInterruptWorker

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e32b2fe8-e096-c4b1-c64b-19a0c6065af9}

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

0: kd> lmvm dxgmms2
Browse full module list
start end module name
fffff805`552c0000 fffff805`553a2000 dxgmms2 (pdb symbols) C:\ProgramData\Dbg\sym\dxgmms2.pdb\78943430616B97561C849D139B8D31C21\dxgmms2.pdb
Loaded symbol image file: dxgmms2.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\dxgmms2.sys\EB81CD48e2000\dxgmms2.sys
Image path: \SystemRoot\System32\drivers\dxgmms2.sys
Image name: dxgmms2.sys
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: EB81CD48 (This is a reproducible build file hash, not a timestamp)
CheckSum: 000E0779
ImageSize: 000E2000
File version: 10.0.19041.804
Product version: 10.0.19041.804
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: dxgmms2.sys
OriginalFilename: dxgmms2.sys
ProductVersion: 10.0.19041.804
FileVersion: 10.0.19041.804 (WinBuild.160101.0800)
FileDescription: DirectX Graphics MMS
LegalCopyright: © Microsoft Corporation. All rights reserved.
 
Dosyalarınızı inceledim. Ekran kartı sürücünüzden veri alınamamış. Ekran kartı sürücüsü sıkıntı çıkarmış. DDU ile kaldırıp yeniden yükleyelim. OC yaptıysanız ekran kartındaki OCyi kaldırınız, o da uyumsuzluk yapmış olabilir.
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\hazar\Downloads\021021-6546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`46a00000 PsLoadedModuleList = 0xfffff805`4762a390
Debug session time: Wed Feb 10 19:53:35.491 2021 (UTC + 3:00)
System Uptime: 0 days 0:16:16.204
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`46df5a80 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff805`4d449930=0000000000000119
0: 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: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 00000000000182d3
Arg3: 00000000000182f2
Arg4: ffff9c8c3e2f6000

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

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on VOSTRO-5468

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 84557

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

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: 182d3

BUGCHECK_P3: 182f2

BUGCHECK_P4: ffff9c8c3e2f6000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff805`4d449928 fffff805`53f23ad0 : 00000000`00000119 00000000`00000001 00000000`000182d3 00000000`000182f2 : nt!KeBugCheckEx
fffff805`4d449930 fffff805`552ddc8c : ffff9c8c`3e438000 00000000`000182d3 00000000`00000001 fffff805`587f9fe8 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffff805`4d449970 fffff805`552cd351 : ffff9c8c`000182d3 00000000`00000000 ffff9c8c`3e2f6000 00000000`00000002 : dxgmms2!VidSchDdiNotifyInterruptWorker+0x108fc
fffff805`4d4499d0 fffff805`53b83f33 : ffff9c8c`3ab9a030 ffff7c1d`151dfe57 00000000`00000000 00000000`00000000 : dxgmms2!VidSchDdiNotifyInterrupt+0xd1
fffff805`4d449a20 fffff805`586a9d42 : ffff9c8c`3ab9a030 fffff805`4d449b29 fffff805`4d449c40 ffff9c8c`3aee1000 : dxgkrnl!DxgNotifyInterruptCB+0x93
fffff805`4d449a50 ffff9c8c`3ab9a030 : fffff805`4d449b29 fffff805`4d449c40 ffff9c8c`3aee1000 fffff805`586a9cd2 : nvlddmkm+0x79d42
fffff805`4d449a58 fffff805`4d449b29 : fffff805`4d449c40 ffff9c8c`3aee1000 fffff805`586a9cd2 ffff9c8c`3aee1000 : 0xffff9c8c`3ab9a030
fffff805`4d449a60 fffff805`4d449c40 : ffff9c8c`3aee1000 fffff805`586a9cd2 ffff9c8c`3aee1000 00000000`00000000 : 0xfffff805`4d449b29
fffff805`4d449a68 ffff9c8c`3aee1000 : fffff805`586a9cd2 ffff9c8c`3aee1000 00000000`00000000 00000000`00000000 : 0xfffff805`4d449c40
fffff805`4d449a70 fffff805`586a9cd2 : ffff9c8c`3aee1000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff9c8c`3aee1000
fffff805`4d449a78 ffff9c8c`3aee1000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x79cd2
fffff805`4d449a80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff9c8c`3ab9a030 : 0xffff9c8c`3aee1000


SYMBOL_NAME: dxgmms2!VidSchDdiNotifyInterruptWorker+108fc

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.804

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 108fc

FAILURE_BUCKET_ID: 0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_dxgmms2!VidSchDdiNotifyInterruptWorker

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e32b2fe8-e096-c4b1-c64b-19a0c6065af9}

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

0: kd> lmvm dxgmms2
Browse full module list
start end module name
fffff805`552c0000 fffff805`553a2000 dxgmms2 (pdb symbols) C:\ProgramData\Dbg\sym\dxgmms2.pdb\78943430616B97561C849D139B8D31C21\dxgmms2.pdb
Loaded symbol image file: dxgmms2.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\dxgmms2.sys\EB81CD48e2000\dxgmms2.sys
Image path: \SystemRoot\System32\drivers\dxgmms2.sys
Image name: dxgmms2.sys
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: EB81CD48 (This is a reproducible build file hash, not a timestamp)
CheckSum: 000E0779
ImageSize: 000E2000
File version: 10.0.19041.804
Product version: 10.0.19041.804
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: dxgmms2.sys
OriginalFilename: dxgmms2.sys
ProductVersion: 10.0.19041.804
FileVersion: 10.0.19041.804 (WinBuild.160101.0800)
FileDescription: DirectX Graphics MMS
LegalCopyright: © Microsoft Corporation. All rights reserved.
Sıfırdan temiz kurulum yapmadan sizin dediğinizi deneyeyim dedim, memory artifacting görmesem de belirli bir süreden sonra Cyberpunk oynarken sistem çöktü. Fikriniz var mıdır başka?
 

Geri
Yukarı