LD Player WATCHDOG VIOLATION Mavi Ekran Hatası

İşletim sistemi
Windows 11

Memolica

Kilopat
Katılım
25 Ocak 2015
Mesajlar
152
Çözümler
1
Daha fazla  
Cinsiyet
Erkek
RAM
Trident Z5 6200 Dual 16GB
SSD veya HDD modeli
Samsung 980 Pro 1TB M.2
Ekran kartı
MSI SUPRIM X 4070 TI Driver Güncel
Anakart
MSI X670E CARBON WI-FI
İşlemci
AMD 7900X
Merhaba. Bilgisayarımda sadece LD Player kullanırken dpc-watchdog-violation hatası alıyorum. Çok nadir LD Player kullandığım ve sadece LD Player açtığım zamanlarda bu hatayı aldığım için kaynağın bu olduğuna eminim.

Merhaba. Diğer emulator programlar da dahil kullanırken bir problem olmuyor. Ancak, emulator çalışırken başka bir uygulama açmaya çalışırken aynı sorunu almaya devam ediyorum. aşağıya bir minidump eklmeye çalıştım.

Teşekkürler.


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

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

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


Loading Dump File [C:\Windows\Minidump\031224-20718-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 (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff804`1e200000 PsLoadedModuleList = 0xfffff804`1ee13510
Debug session time: Tue Mar 12 21:36:07.193 2024 (UTC + 3:00)
System Uptime: 0 days 13:24:34.781
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............................................
Loading User Symbols

Loading unloaded module list
..........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`1e617380 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff804`2276f9f0=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: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff8041ef1c340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding this single DPC timeout

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

    Key  : Analysis.Elapsed.mSec
    Value: 8172

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

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

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

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

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

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

    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_DPC_nt!KeAccumulateTicks

    Key  : Failure.Hash
    Value: {88dc98ce-f842-4daa-98d0-858621db6b0f}


BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8041ef1c340

FILE_IN_CAB:  031224-20718-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

FAULTING_THREAD:  0000000000000017

STACK_TEXT: 
fffff804`2276f9e8 fffff804`1e476ad5     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff804`2276f9f0 fffff804`1e4761a1     : 00001ecc`c5e4044a 00000000`002f24b2 00000000`002f24b1 00000000`00000000 : nt!KeAccumulateTicks+0x3d5
fffff804`2276fa50 fffff804`1e4737af     : 00000000`00000018 00000000`00001388 00000000`002f2400 00000000`001c1980 : nt!KiUpdateRunTime+0xd1
fffff804`2276fc00 fffff804`1e474398     : 00000000`00000000 00000000`00000000 fffff804`1b1b4180 00000000`00000000 : nt!KiUpdateTime+0x63f
fffff804`2276fea0 fffff804`1e473c5a     : fffff804`1ee5fe58 00000000`00000001 00000000`00000001 00000000`00000002 : nt!KeClockInterruptNotify+0x228
fffff804`2276ff40 fffff804`1e523f3c     : 00000070`669caa3a fffff804`1ef0d4b0 fffff804`1ef0d560 fffff804`1e6192db : nt!HalpTimerClockInterrupt+0x10a
fffff804`2276ff70 fffff804`1e61953a     : fffff804`2275fbe0 fffff804`1ef0d4b0 fffff804`2275fda8 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
fffff804`2276ffb0 fffff804`1e619de7     : 00000000`00000000 00001f80`006102f4 00000000`58f55055 fffff804`2275fd58 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff804`2275fb60 fffff804`1e427ab0     : 00000000`80000000 fffff804`1e58cfdf 00000000`00000000 ffffb786`5ee56ad0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff804`2275fcf0 fffff804`1e58cfdf     : 00000000`00000000 ffffb786`5ee56ad0 00000000`00000001 00000000`00000000 : nt!KeYieldProcessorEx+0x20
fffff804`2275fd00 fffff804`1e54829b     : 00000000`00000000 fffff804`58fd045c fffff804`2275fda8 00000000`00000000 : nt!ExpGetPoolTagInfoTarget+0xff
fffff804`2275fd50 fffff804`1e5c3c2e     : fffff804`00000018 00000018`00000001 00000000`00000000 ffffb786`5ee56ad0 : nt!KiInitiateGenericCallDpc+0x97
fffff804`2275fda0 fffff804`1e42957c     : 00000000`00000000 fffff804`22760410 00000000`00000001 fffff804`a9193c4b : nt!KiGenericCallDpcInitiatorDpc+0x2e
fffff804`2275fdd0 fffff804`1e42a831     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x42c
fffff804`22760310 fffff804`1e61c2ae     : 00000000`00000000 fffff804`1b1b4180 fffff804`1ef4c700 ffff800f`f80f0080 : nt!KiRetireDpcList+0x1b1
fffff804`227605c0 00000000`00000000     : fffff804`22761000 fffff804`2275a000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


STACK_COMMAND:  ~23 ; .cxr ; kb

SYMBOL_NAME:  nt!KeAccumulateTicks+3d5

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.3235

BUCKET_ID_FUNC_OFFSET:  3d5

FAILURE_BUCKET_ID:  0x133_DPC_nt!KeAccumulateTicks

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {88dc98ce-f842-4daa-98d0-858621db6b0f}

Followup:     MachineOwner
---------
 
Son düzenleme:

Geri
Yukarı