VIDEO_SCHEDULER_INTERNAL_ERROR mavi ekran hatası

Emorti

Kilopat
Katılım
25 Şubat 2017
Mesajlar
134
Çözümler
1
Yer
İstanbul
Daha fazla  
Cinsiyet
Erkek
Merhabalar;

Sistem özellikleri
-TUF B550 Plus
-Ryzen 5600x
-TUF 3070OC
-Ballistick 2x8GB (3200 CL16)
-Corsair RM750w

Müzik dinlerken Netflix'i açıp 4k mevcut bir filme tıkladım(HEVC uzantısı kurmuştum). Film bir süre siyah ekranda kaldı ve sonrasında mouse teklemeye başladı. En sonunda da mavi ekran vererek reset attı. Daha önceleri masaüstündeyken veya Chrome'da sosyali gezerken bu tarz teklemeler olup ekranın gidip geldiğine, devamında ekran kartının RGB'sinin söndüğüne ve hatta bazen görüntü varken tamamen donup kalmasına şahit olmuştum. Görev yöneticisinde performans sekmesinde 3D grafiğinin %100ün üzerine çıktığını gösteriyor her takılmada. Sıcaklıklarda hiç anormal bir durum görmedim.

Minidump dosyasını açıp analiz ettirdim ve aşağıdaki sonucu verdi fakat Arg2, 3 ve 4 bir anlam ifade ediyor mu emin olamadım. Yaklaşık 1.5 ay önce DDU ile sürücüleri geçmiş versiyona çevirmiştim ve sonrasında 3 kez NVIDIA experience ile güncelleme yaptım. Şu an 461.92 sürücüsü kurulu. İlk kez Netflix'te bu sorunu yaşadım. Tekrar DDU gerekmiyordur umarım. Fikri olan arkadaşlar, tecrübe etmiş olanlar, yardımcı olabilirseniz sevinirim.

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: fffffe052db5f920
Arg4: ffffcf8c517b8210

Debugging details:

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3686

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 43679

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

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

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

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


BUGCHECK_CODE: 119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: fffffe052db5f920

BUGCHECK_P4: ffffcf8c517b8210

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffffe05`2db5f848 fffff807`786c3ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffffe05`2db5f920 : nt!KeBugCheckEx
fffffe05`2db5f850 fffff807`7a1fb3cb : 00000000`00000000 ffffcf8c`517b5000 ffffcf8c`51851010 ffffcf8c`517b5546 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffffe05`2db5f890 fffff807`7a264b6d : ffffcf8c`00000000 ffffcf8c`517b8210 ffffcf8c`516fc000 ffffcf8c`55db0010 : dxgmms2!VidSchiSendToExecutionQueue+0x1306b
fffffe05`2db5f9c0 fffff807`7a26cd1a : ffffcf8c`55db0010 ffffcf8c`516fc000 00000000`00000000 ffffcf8c`517a3720 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
fffffe05`2db5fb40 fffff807`7a26cb8a : ffffcf8c`516fc400 fffff807`7a26cac0 ffffcf8c`516fc000 ffffa680`70500100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
fffffe05`2db5fb90 fffff807`6a317e85 : ffffcf8c`51755380 fffff807`00000001 ffffcf8c`516fc000 000fe067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
fffffe05`2db5fbd0 fffff807`6a3fd2a8 : ffffa680`70500180 ffffcf8c`51755380 fffff807`6a317e30 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffffe05`2db5fc20 00000000`00000000 : fffffe05`2db60000 fffffe05`2db59000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+1306b

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.868

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1306b

FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner
 
Tarihe göre sırala Puana göre sırala

Thank you very much for the kind words and reply!

I see some similarities here (namely, playing with settings prior to launching Netflix and the refresh rate being set at 120Hz). That's interesting!

I think, however, that this is definitely worth worth figuring out. Launching usermode applications should never result in a BSOD. If this is a software (or a driver) bug, then it should be fixed. It might be not an issue specific to Netfix; it is just that we only see it with Netflix at present.

If you encounter more BSODs, please share the details. I'd love to get to the bottom of this!

P.S. Would it be okay for me to quote what you wrote in this thread on NVIDIA forum?
 
Artı 0 Eksi

Can I take your minidump files please? Maybe I can help you.
 
Artı 0 Eksi
Enes3078 dedi:
Can I take your minidump files please? Maybe I can help you.
Genişletmek için tıkla...

I'D rather not share minidump files, because they may contain sensitive Memory content. Rest assured that analyzing such dumps is a part of my Professional competence (I do low level software engineering for a living). For the sake of completion, have a look below.

Here's some dump information for One BSoD, from March 27:

Kod: 
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: 0000000000000002, The driver failed upon the submission of a command.
Arg2: FffffffFC000000D
Arg3: FfFF808D9Bdea920
Arg4: FfFF98866A9bbbb0

[...]

PROCESS_NAME: System

STACK_TEXT:
Ffff808D'9bdea848 fffff806'8C6C3ad0: 00000000'00000119 00000000'00000002 ffffffff'C000000D ffff808D'9bdea920: Nt! KeBugCheckEx
Ffff808D'9bdea850 fffff806'9212B3CB: 00000000'00000000 ffff9886'6A9B8000 ffff9886'6A9D0a20 ffff9886'6A9b850e: Watchdog! WdLogEvent5_WdCriticalError+0Xe0
Ffff808D'9bdea890 fffff806'92194B6D: Ffff9886'00000000 ffff9886'6A9bbbb0 ffff9886'6A91F000 ffff9886'7fdac010: Dxgmms2! VidSchiSendToExecutionQueue+0x1306b
Ffff808D'9bdea9C0 fffff806'9219CD1A: Ffff9886'7fdac010 ffff9886'6A91F000 00000000'00000000 ffff9886'6A9b2620: Dxgmms2! VidSchiSubmitPagingCommand+0x2ed
Ffff808D'9bdeaB40 fffff806'9219CB8A: Ffff9886'6A91F400 fffff806'9219CAC0 ffff9886'6A91F000 ffff8800'44AC2100: Dxgmms2! VidSchiRun_PriorityTable+0x17A
Ffff808D'9bdeaB90 fffff806'7C117E85: Ffff9886'6A968380 fffff806'00000001 ffff9886'6A91F000 000FE067'bcbbbdff: Dxgmms2! VidSchiWorkerThread+0xca
Ffff808D'9bdeabd0 fffff806'7C1fd2a8: Ffff8800'44AC2180 ffff9886'6A968380 fffff806'7C117E30 11001E80'C0a071CF: Nt! PspSystemThreadStartup+0x55
Ffff808D'9bdeac20 00000000'00000000: Ffff808D'9bdeB000 ffff808D'9bde4000 00000000'00000000 00000000'00000000: Nt! KiStartSystemThread+0x28

SYMBOL_NAME: Dxgmms2! VidSchiSendToExecutionQueue+1306b

Here's another One, from April 3:

Kod: 
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: 0000000000000002, The driver failed upon the submission of a command.
Arg2: FffffffFC000000D
Arg3: FFFFB00199A7F920
Arg4: FFFFE78869C0C210

[...]

STACK_TEXT:
Ffffb001'99a7F848 fffff801'8CF13ad0: 00000000'00000119 00000000'00000002 ffffffff'C000000D ffffb001'99a7F920: Nt! KeBugCheckEx
Ffffb001'99a7F850 fffff801'91e9b44b: 00000000'00000000 ffffe788'69C09000 ffffb001'99a7F959 ffffe788'69C09000: Watchdog! WdLogEvent5_WdCriticalError+0Xe0
Ffffb001'99a7F890 fffff801'91F0518D: Ffffe788'00000000 ffffe788'69C0C210 ffffe788'69b76000 ffffe788'76e8a010: Dxgmms2! VidSchiSendToExecutionQueue+0x130eb
Ffffb001'99a7F9C0 fffff801'91F0D42a: Ffffe788'76e8a010 ffffe788'4da90180 00000000'00000000 fffff801'91F0D1D0: Dxgmms2! VidSchiSubmitPagingCommand+0x2ed
Ffffb001'99a7fB40 fffff801'91F0D29a: Ffffe788'69b76400 fffff801'91F0D1D0 ffffe788'69b76000 ffffd181'83a00100: Dxgmms2! VidSchiRun_PriorityTable+0x17A
Ffffb001'99a7fB90 fffff801'7F317E85: Ffffe788'69bad380 fffff801'00000001 ffffe788'69b76000 000FE067'bcbbbdff: Dxgmms2! VidSchiWorkerThread+0xca
Ffffb001'99a7fbd0 fffff801'7F3fd408: Ffffd181'83a00180 ffffe788'69bad380 fffff801'7F317E30 00000088'00000040: Nt! PspSystemThreadStartup+0x55
Ffffb001'99a7fc20 00000000'00000000: Ffffb001'99a80000 ffffb001'99A79000 00000000'00000000 00000000'00000000: Nt! KiStartSystemThread+0x28

SYMBOL_NAME: Dxgmms2! VidSchiSendToExecutionQueue+130eb

----

I think that the picture is pretty clear here. One noteworthy point is the difference in stack offsets between these dumps (0x1306b in the first One, as opposed to 0x130eb in the second One). The reason is that the dxgmms2.sys module was updated in KB5000842 (released on March 29). The Update was applied in the interim, and hence the difference in stack offsets.

Have a look here to see how 0x119 bugchecks are being triggered:

DXGKDDI_SUBMITCOMMAND (d3dkmddi.h) - Windows drivers

Learn more about the DxgkDdiSubmitCommand callback function.
docs.microsoft.com

In both dumps, the second parameter is an NTSTATUS, which happens to be STATUS_INVALID_PARAMETER. Take the second dump for example. The Third argument is a pointer to a DXGARG_SUBMITCOMMAND data structure. If you look closely, you will see that the fourth bugcheck argument of 0xffffe78869c0c210 is a pointer to a scheduler data structure that was submitted at dxgmms2! VidSchiSubmitPagingCommand+0x2ed. The crash then happens One step down the call stack.

Now, given the NTSTATUS that is returned (as evident from these dumps), it might be reasonable to assume that for some reason, a driver incorrectly handles some Edge case during a DXGKDDI_SUBMITCOMMAND callback, thereby triggering a 0x119 bugcheck. This is as far as I can assume.
 
Artı 0 Eksi
Can you try another language NVIDIA driver? And I think you can share your dumps. You know, that's not a MEMORY.dmp. We can't access your any private information.

Or you can try another version driver for graphic card.

And my English is not very well. Sometimes I have trouble understanding English.
 
Artı 0 Eksi
Your English is very good, no worries. English is not my first language either.

This issue has persistent through (at least) two driver versions now (v461.92 and v465.89). I don't think different languages should matter as the kernel mode component (the .sys driver file itself) should not differ between locales. I might be wrong though.
 
Artı 0 Eksi
Two days ago I got blue screen error too. v465.89 was installed and I downgraded it to v461.40.
The issue is solved now. Could you try downgrade to v461.40?

Btw, I don't have any knowledge about BSOD analyzing. Just a driver version suggestion.

My GPU: GTX 1660Ti
 
Artı 0 Eksi

I think it's worth a try. I would like to invite @Recep Baltaş to the topic.
 
Artı 0 Eksi
Seeing that minidump would definitely be very, very interesting!
 
Artı 0 Eksi
Mesaj yazmak için giriş yapmalı ya da kaydolmalısınız.

Benzer konular

S
  • Soru
VIDEO_SCHEDULER_INTERNAL_ERROR mavi ekran hatası
Mesaj
6
Görüntüleme
170
Serhatkaan.s
S
  • Soru
VIDEO_SCHEDULER_INTERNAL_ERROR mavi ekran hatası
Mesaj
7
Görüntüleme
254
0verlord23
J
  • Soru
VIDEO_SCHEDULER_INTERNAL_ERROR mavi ekran hatası
Mesaj
2
Görüntüleme
378
JcMaxwell
J
  • Soru
VIDEO_SCHEDULER_INTERNAL_ERROR mavi ekran hatası
2 3
Mesaj
24
Görüntüleme
784
serkanxa
  • Soru
VIDEO_SCHEDULER_INTERNAL_ERROR mavi ekran hatası
Mesaj
2
Görüntüleme
268
srfayhn
Menü
Giriş yap
Kaydol
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…