7950X3D sistemde "VIDEO_SCHEDULER_INTERNAL_ERROR" ve "SYSTEM_SERVICE_EXCEPTION" mavi ekran hatası

İşletim sistemi
Windows 11
Katılım
19 Mayıs 2020
Mesajlar
9
RAM
GSKILL 32GB (2x16GB) TRIDENT Z5 SİYAH DDR5 6400MHz CL32 1.4V RGB Dual Kit R
SSD veya HDD modeli
Samsung 2TB 990 PRO NVMe2.0 SSD
Ekran kartı
ASUS TUF Gaming GeForce RTXTM 4080 16GB GDDR6X OC
Anakart
MEG X670E ACE
İşlemci
AMD Ryzen 9 7950X3D 16-Core Processor, 420
Bilgisayarı 2 ay önce topladım ve son iki haftadır bilgisayarda mavi ekran hataları alıyorum: "VIDEO_SCHEDULER_INTERNAL_ERROR" (önceliğim bu hata). Hatayı, bu mesajı yazdığım tarihte de aldım. Bu hatalardan önce işlemci ve anakart sıcaklığım boşta 35-40 derecelerde seyrediyordu. Hatalardan sonra bilgisayarda hafif kasma, donmalar, gecikmeler ve geç açılmalar meydana geldi ve işlemci sıcaklığım boşta 50 derecelere yaklaştı. Bu mesajı yazdığım an itibarıyla işlemci sıcaklığım 50 dereleri gördü. RTX 4080 ekran kartım boşta maksimum 30 derecelerde, işlemcimin AMD Radeon dahili grafik birimi ise 36 derecelerde. Son iki gündür ise bilgisayarda garip sesler geliyor cızırtı gibi ama tam olarak cızırtı sesine benzemiyor. Sürekli bir ses değil aralıklı bir ses, kaynağını çözemedim ama fanın sesi de olabilir. Hatta fanlar birkaç gündür bilgisayar boştayken bile yüksek devirde dönüyor.

Araştırmalarım sonucu "VIDEO_SCHEDULER_INTERNAL_ERROR" hatasının ekran kartı ile ilgili bir sorun olduğunu öğrendim ama hatanın neden ve nasıl kaynaklandığını bilmiyorum. Harici ekran kartından da oluşan bir hata olabilir (işlemcinin dahili grafik biriminden de olabilir). Hatta Technopat forumda bu hatayla ilgili bir konuda hatanın monitörden kaynaklanabileceğini de söylediler.

RDR2'yi yanlışlıkla üst üste 3-4 defa açarken bilgisayar dondu ve "SYSTEM_SERVICE_EXCEPTION" hatası oluştu. Hatanın kaynağını tam olarak bilmiyorum.

VIDEO_SCHEDULER_INTERNAL_ERROR hatasını birden fazla aldım SYSTEM_SERVICE_EXCEPTION hatasını tek bir defa aldım.
VIDEO_SCHEDULER_INTERNAL_ERROR hatası donanımsal mı yazılımsal mı bilmiyorum. Temennim yazılımsal olması.
@Ali Güngör rica etsem MiniDump dosyalarını analiz edebilir misiniz?
İnternetteki neredeyse tüm yolları denedim ama sonuç alamadım, minidump dosyalarını paylaşıyorum, yardımlarınızı bekliyorum.
Not: Sistem Win11 Pro
MiniDump

VIDEO_SCHEDULER_INTERNAL_ERROR Kodları:
Kod:
************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : false
   AllowNugetExeUpdate : false
   AllowNugetMSCredentialProviderInstall : false
   AllowParallelInitializationOfLocalRepositories : true

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Veysel\Desktop\MiniDump\122623-13343-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Empty Dump Data Extension block was ignored

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff804`4fc00000 PsLoadedModuleList = 0xfffff804`508134a0
Debug session time: Tue Dec 26 20:33:04.962 2023 (UTC + 3:00)
System Uptime: 0 days 20:41:42.746
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............................
Loading User Symbols

Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`50016b70 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffe10a`54952140=0000000000000119
2: 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: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: ffffe10a549522a0
Arg4: ffffce0f571526a0

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1265

    Key  : Analysis.Elapsed.mSec
    Value: 1339

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x119

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

    Key  : Failure.Hash
    Value: {9a11bf9c-270e-962e-7a82-3efdab93c10e}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 4853999

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffffe10a549522a0

BUGCHECK_P4: ffffce0f571526a0

FILE_IN_CAB:  122623-13343-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffe10a`54952138 fffff804`53775685     : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffe10a`549522a0 : nt!KeBugCheckEx
ffffe10a`54952140 fffff804`bde254fa     : 00000000`00000000 ffffce0f`4e688a80 ffffce0f`4e688a88 ffffce0f`4e688a90 : watchdog!WdLogSingleEntry5+0x3b45
ffffe10a`549521f0 fffff804`bdeab79a     : ffffce0f`00000000 ffffce0f`57152600 ffffce0f`57078000 ffffce0f`571526a0 : dxgmms2!VidSchiSendToExecutionQueue+0x1c08a
ffffe10a`549523c0 fffff804`bdf05c1c     : ffffce0f`571526a0 ffffe10a`54952479 ffffce0f`57078000 fffff804`bde07bbc : dxgmms2!VidSchiSendToExecutionQueueWithWait+0x5a
ffffe10a`549523f0 fffff804`bdedd6a2     : fffff804`957a0000 ffffce0f`4e6af010 ffffce0f`4ded1010 ffffce0f`57156820 : dxgmms2!VidSchiSubmitPagingCommand+0x358
ffffe10a`549524e0 fffff804`bdeb877a     : 00000000`00000000 fffff804`bdeb86b0 ffffce0f`57078000 00000000`00050217 : dxgmms2!VidSchiRun_PriorityTable+0x24ed2
ffffe10a`54952530 fffff804`4ff07167     : ffffce0f`57130480 fffff804`00000001 ffffce0f`57078000 005fe07f`b8bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffe10a`54952570 fffff804`5001bc04     : ffff9881`03517180 ffffce0f`57130480 fffff804`4ff07110 6e6f4379`7265766f : nt!PspSystemThreadStartup+0x57
ffffe10a`549525c0 00000000`00000000     : ffffe10a`54953000 ffffe10a`5494c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+1c08a

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.22621.2915

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1c08a

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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

SYSTEM_SERVICE_EXCEPTION Kodları
Kod:
************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : false
   AllowNugetExeUpdate : false
   AllowNugetMSCredentialProviderInstall : false
   AllowParallelInitializationOfLocalRepositories : true

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.000 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Veysel\Desktop\MiniDump\122323-22093-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 22621 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff802`59600000 PsLoadedModuleList = 0xfffff802`5a2134a0
Debug session time: Sat Dec 23 18:16:51.337 2023 (UTC + 3:00)
System Uptime: 0 days 0:26:42.118
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`002a6018).  Type ".hh dbgerr001" for details
Loading unloaded module list
....................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`59a16b70 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffc685`9e240b00=000000000000003b
25: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff802b67995eb, Address of the instruction which caused the BugCheck
Arg3: ffffc6859e241450, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1327

    Key  : Analysis.Elapsed.mSec
    Value: 1315

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {7eea5677-f68d-2154-717e-887e07e55cd3}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 4853999

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff802b67995eb

BUGCHECK_P3: ffffc6859e241450

BUGCHECK_P4: 0

FILE_IN_CAB:  122323-22093-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

CONTEXT:  ffffc6859e241450 -- (.cxr 0xffffc6859e241450)
rax=0072006f00000000 rbx=fffff802b6ba6800 rcx=ffff838fb208f000
rdx=ffff838fb208f000 rsi=ffff838fb208f000 rdi=ffff838fb208f000
rip=fffff802b67995eb rsp=ffffc6859e241e78 rbp=ffffc6859e241f09
 r8=ffffc6859e241f10  r9=fffff802b6a544f8 r10=0000fffff802b6ba
r11=ffff98fddaa00000 r12=fffff8025a30c638 r13=0000000000000000
r14=ffff838faeff4fa0 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nvlddmkm+0x8d95eb:
fffff802`b67995eb 488b8018230000  mov     rax,qword ptr [rax+2318h] ds:002b:0072006f`00002318=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  RDR2.exe

STACK_TEXT:
ffffc685`9e241e78 fffff802`b6ba6844     : 00000000`00000000 fffff802`b6a544f8 00000000`00000000 fffff802`5a0ac2b0 : nvlddmkm+0x8d95eb
ffffc685`9e241e80 00000000`00000000     : fffff802`b6a544f8 00000000`00000000 fffff802`5a0ac2b0 00000000`00000000 : nvlddmkm+0xce6844


SYMBOL_NAME:  nvlddmkm+8d95eb

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr 0xffffc6859e241450 ; kb

BUCKET_ID_FUNC_OFFSET:  8d95eb

FAILURE_BUCKET_ID:  AV_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7eea5677-f68d-2154-717e-887e07e55cd3}

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

Foto.jpg
 
Son düzenleyen: Moderatör:
Aynı durumla karşı karşıyayım.
Bazen ,açılış yüklemesinde Beyaz çizgilenmeler oluyor. En son mavi ekran hatası aldım.
Sanırım Onboard ekran kartıyle , Pci express slota takılı Nvidia ekran kartı arasında bir sorun var gibi.
Memtest86 sonucu sıfır error ile bitti. 7000 mhz. 16x2 CL32 Patriot Venom Viper Kit
 

Technopat Haberler

Yeni konular

Geri
Yukarı