DPC_WATCHDOG_VIOLATION

teknisyenbey · 24 Kasım 2024

Merhaba,

DPC_WATCHDOG_VIOLATION hatası alıyorum.
Bazı oyunlarda oyun esnasında FPS düşmesi yapıyor ve bir anda oyun donup mavi ekran alıyorum. Oyun donar donmaz bazen Alt Tab vs yapabiliyorum hatta Görev Yöneticisi'nden oyunu kapatabiliyorum. Kapattıktan sonra ise bir süre sonra mavi ekrana düşüyorum. BIOS güncelledim ve sonrasında başka kodlu mavi ekran sorunu ile karşılaştım, VMD Controllerı değiştirdiğimde düzeldi. Fakat DPC_WATCHDOG_VIOLATION hatasına çözüme kavuşturamadım. Intel ekran kartı ve NVIDIA ekran kartım da güncel. Diğer tüm sürücülerim güncel. Minidump dosyalarını da paylaşıyorum. Windows 10 kullanıyordum Windows 11'e yükseltip denedim fakat çözüme ulaşamadım.
MiniDump

Kod:

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

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

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


Loading Dump File [C:\Windows\Minidump\112424-11343-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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff807`62600000 PsLoadedModuleList = 0xfffff807`632134f0
Debug session time: Sun Nov 24 00:41:09.463 2024 (UTC + 3:00)
System Uptime: 0 days 21:56:34.073
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............................
Loading User Symbols

Loading unloaded module list
....................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`62a14fa0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff807`673d5c90=0000000000000133
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff8076331d340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************
*** WARNING: Check Image - Checksum mismatch - Dump: 0x201482, File: 0x201504 - C:\ProgramData\Dbg\sym\BTHport.sys\9BFC3B54202000\BTHport.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 343

    Key  : Analysis.Elapsed.mSec
    Value: 7249

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    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: 0x133_ISR_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {f97493a5-ea2b-23ca-a808-8602773c2a86}

    Key  : Stack.Pointer
    Value: ISR


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8076331d340

BUGCHECK_P4: 0

FILE_IN_CAB:  112424-11343-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

FAULTING_THREAD:  fffff8076334d700

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff807`673d5c88 fffff807`62839779     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`6331d340 : nt!KeBugCheckEx
fffff807`673d5c90 fffff807`62838fe1     : 00002a47`adf832a7 00000000`004d2484 00000000`004d2483 00000000`00000000 : nt!KeAccumulateTicks+0x239
fffff807`673d5cf0 fffff807`62837071     : 00000000`00000000 ffffa880`8f4ff500 fffff807`5fcf5180 00000000`00000000 : nt!KiUpdateRunTime+0xd1
fffff807`673d5ea0 fffff807`62836b6a     : fffff807`6325ff38 ffffa880`8f4ff5b0 ffffa880`8f4ff5b0 00000000`0000000c : nt!KeClockInterruptNotify+0xc1
fffff807`673d5f40 fffff807`62915f9c     : 000000b7`eced09da fffff807`6330d4f0 fffff807`6330d5a0 ffffe287`09f9a000 : nt!HalpTimerClockInterrupt+0x10a
fffff807`673d5f70 fffff807`62a171aa     : fffff807`673c4680 fffff807`6330d4f0 ffffe287`08dfc470 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
fffff807`673d5fb0 fffff807`62a17a77     : 00000000`00000000 00000000`00000000 fffff807`6334d700 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff807`673c4600 fffff807`62823f8c     : fffff807`96bb3c79 ffffe287`00000000 00000000`000007f4 ffffe287`0ff57030 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff807`673c4798 fffff807`96bb3c79     : ffffe287`00000000 00000000`000007f4 ffffe287`0ff57030 ffffe287`09e6dd48 : nt!KzRaiseIrql+0xc
fffff807`673c47a0 ffffe287`00000000     : 00000000`000007f4 ffffe287`0ff57030 ffffe287`09e6dd48 00000000`00b81010 : nvlddmkm+0xe3c79
fffff807`673c47a8 00000000`000007f4     : ffffe287`0ff57030 ffffe287`09e6dd48 00000000`00b81010 fffff807`96bce477 : 0xffffe287`00000000
fffff807`673c47b0 ffffe287`0ff57030     : ffffe287`09e6dd48 00000000`00b81010 fffff807`96bce477 00000000`00000000 : 0x7f4
fffff807`673c47b8 ffffe287`09e6dd48     : 00000000`00b81010 fffff807`96bce477 00000000`00000000 00000000`00000000 : 0xffffe287`0ff57030
fffff807`673c47c0 00000000`00b81010     : fffff807`96bce477 00000000`00000000 00000000`00000000 00000000`00000040 : 0xffffe287`09e6dd48
fffff807`673c47c8 fffff807`96bce477     : 00000000`00000000 00000000`00000000 00000000`00000040 00000000`00000600 : 0xb81010
fffff807`673c47d0 00000000`00000000     : 00000000`00000000 00000000`00000040 00000000`00000600 ffffe286`f981bc30 : nvlddmkm+0xfe477


SYMBOL_NAME:  nvlddmkm+e3c79

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .process /r /p 0xfffff80763349f40; .thread 0xfffff8076334d700 ; kb

BUCKET_ID_FUNC_OFFSET:  e3c79

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

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

MiniDump

turko35408 · 24 Kasım 2024

@teknisyenbey Güvenli mod'da NVIDIA ekran kartı sürücülerini kaldırın.

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

En Yeni Resmi GeForce Sürücülerini İndirin

PC'deki oyun deneyiminizi geliştirmek ve uygulamaları daha hızlı çalıştırmak için en yeni resmi GeForce sürücülerini indirin.

www.nvidia.com

Windows 10 Güvenli Mod Nasıl Açılır?

Adım adım Windows 10 işletim sisteminin nasıl güvenli mod'da açılacağını açıklıyoruz. Güvenli mod, yıllardır aramızda ve çeşitli sorunlarda kullanıcıların

www.technopat.net

BIOS güncellemesi gelmiş güncelleyin.

https://tr.msi.com/Laptop/Katana-17-B12VX/support?sub_product=Katana-17-B12VGK

https://www.msi.com/support/technical_details/NB_BIOS_Update

teknisyenbey · 24 Kasım 2024

Bios güncellemesi yaptım yaparken INACCESSIBLE BOOT_DEVICE hatası ile karşılaştım, VMD Controller'ı disable yaptım. DDU ile sürücüleri kaldırdım ve tekrardan güncel olanları yükledim. Tekrardan aynı hata ile karşılaştım.
FPS im 120 den 50lere düşüp donuyor daha sonra DPC_WATCHDOG_VIOLATION mavi ekran hatası alıyorum.

Kod:

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- 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.031 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 42

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


Loading Dump File [C:\Windows\Minidump\112424-15765-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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff805`17800000 PsLoadedModuleList = 0xfffff805`184134f0
Debug session time: Sun Nov 24 22:39:16.863 2024 (UTC + 3:00)
System Uptime: 0 days 0:17:45.768
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............................
Loading User Symbols

Loading unloaded module list
...............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`17c14fa0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff805`1b7f7c90=0000000000000133
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff8051851d340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 31

    Key  : Analysis.Elapsed.mSec
    Value: 2043

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    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: 0x133_ISR_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {f97493a5-ea2b-23ca-a808-8602773c2a86}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    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

    Key  : Stack.Pointer
    Value: ISR


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8051851d340

BUGCHECK_P4: 0

FILE_IN_CAB:  112424-15765-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

FAULTING_THREAD:  fffff8051854d700

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
fffff805`1b7f7c88 fffff805`17a39779     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff805`1851d340 : nt!KeBugCheckEx
fffff805`1b7f7c90 fffff805`17a38fe1     : 000002e4`9683ed8d 00000000`00010a71 00000000`00010a70 00000000`00000000 : nt!KeAccumulateTicks+0x239
fffff805`1b7f7cf0 fffff805`17a37071     : 00000000`00000000 ffff9d81`6052e400 fffff805`13c34180 00000000`00000000 : nt!KiUpdateRunTime+0xd1
fffff805`1b7f7ea0 fffff805`17a36b6a     : fffff805`1845fed8 ffff9d81`6052e470 ffff9d81`6052e470 00000000`00000002 : nt!KeClockInterruptNotify+0xc1
fffff805`1b7f7f40 fffff805`17b15f9c     : 00000002`7b428bc1 fffff805`1850d4f0 fffff805`1850d5a0 00000000`ffffffff : nt!HalpTimerClockInterrupt+0x10a
fffff805`1b7f7f70 fffff805`17c171aa     : fffff805`1b7e66f0 fffff805`1850d4f0 ffff8c08`bae76d48 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
fffff805`1b7f7fb0 fffff805`17c17a77     : fffff805`1b7e6810 00000000`00000000 fffff805`1b7e6790 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff805`1b7e6670 fffff805`484fd9f3     : 00000000`00000000 fffff805`4852e5fa 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff805`1b7e6800 00000000`00000000     : fffff805`4852e5fa 00000000`00000000 00000000`00000000 00000000`0010a000 : nvlddmkm+0xcd9f3


SYMBOL_NAME:  nvlddmkm+cd9f3

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .process /r /p 0xfffff80518549f40; .thread 0xfffff8051854d700 ; kb

BUCKET_ID_FUNC_OFFSET:  cd9f3

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

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

Bilgisayarı servise verdim, testleri yaptıklarını ve bir sorun olmadığını gördüklerini söylediler.
Eve geldiğimde fps sınırlaması yaparak test ettim aynı şekilde hata verdi. Test esnasında fps sınırlamasını kapatmışlar. Sorun bundan kaynaklı olabilir mi? Ben de oyunlarda fps sınırlamasını kapatarak denedim sorun olmadı.

turko35408 · 1 Aralık 2024

Hocam yine ekran kartı hatası almışsınız. O şekilde sorun olmuyorsa bırakın kalsın. Ama bence bu durum normal değil.

teknisyenbey · 5 Aralık 2024

Servise verdim, GPU değiştirdiler. Şu anlık sıkıntı yok gözüküyor. Sadece aklıma takılan Aygıt Yöneticisi'nden Intel ekran kartını kapattığım zaman oyun menüsünde normalde 120 FPS alıyorken 5 FPS alıyorum. İntel ve Nvidia ekran kartları beraber mi çalıyorlar?

Tekrardan servise götürdüm, Aygıt Yöneticisi'nden yapıldığında MSI da sorun oluyormuş. Kendi uygulaması üzerinden kapattığımda sorun olmadı bilginiz olsun.
İyi günler.
Konu kapanabilir teşekkürler.

DPC_WATCHDOG_VIOLATION

Ayrıntılı düzenleme

teknisyenbey

Kilopat

turko35408

Zettapat

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

En Yeni Resmi GeForce Sürücülerini İndirin

Windows 10 Güvenli Mod Nasıl Açılır?

teknisyenbey

Kilopat

turko35408

Zettapat

teknisyenbey

Kilopat

Benzer konular

Technopat Haberler

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz