DPC Watchdog Violation ntkrnlmp.exe bsod

Anonim
2023-06-20T21:50:47+00:00

Hello, I **** having a bsod problem on my nitro 5 an515-45. After giving it once, it gives 3-4 more times in a row. Then it doesn't come for 20 days and 1 month. And then it starts coming again. It moves in a loop. I tested the rams with Memtest86 and did not encounter any errors. I put my video card in a 4-hour test with furmark and I didn't encounter any problems with it. I get these bsods mostly in games, for example gta 5 or astroneer. What should I do?

Merhaba nitro 5 an515-45 cihazımda bir bsod sorunu yaşıyorum. Bir defa verdikten sonra art arda 3-4 defa daha veriyor. Sonra 20 gün 1 ay boyunca gelmiyor. Ve sonra tekrar başlıyor gelmeye. Döngü şeklinde ileriyor. Memtest86 ile ramleri test ettim herhangi bir hata ile karşılaşmadım. Ekran kartımı furmark ile 4 saatlik bir teste soktum onda da herhangi bir sorunla karşılaşmadım. Daha çok oyun içinde alıyorum bu bsodları örneğin gta 5 veya astroneer. Ne yapmalıyım?

*                                                                             *
*                        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: fffff80430d1c340, 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: 2750

    Key  : Analysis.Elapsed.mSec
    Value: 3087

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    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_DPC_nt!KeAccumulateTicks

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

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

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80430d1c340

FILE_IN_CAB:  061923-10109-01.dmp

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

DUMP_FILE_ATTRIBUTES: 0x1808
  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:  000000000000000b

STACK_TEXT:  
fffff804`328f4a28 fffff804`302df06d     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff804`328f4a30 fffff804`302de74c     : 000019b3`0882d62f 00000000`00085f55 00000000`00085f54 00000000`00000202 : nt!KeAccumulateTicks+0x3cd
fffff804`328f4a90 fffff804`302dbd23     : 00000000`0000000c 00000000`00001388 00000000`00085f00 00000000`0004fd86 : nt!KiUpdateRunTime+0xcc
fffff804`328f4c00 fffff804`302dc968     : 00000000`00000000 00000000`00000000 fffff804`2b78c180 00000000`00000000 : nt!KiUpdateTime+0x613
fffff804`328f4ea0 fffff804`302dc219     : fffff804`30c5fe60 00000000`00000001 00000000`00000001 00000000`00000002 : nt!KeClockInterruptNotify+0x228
fffff804`328f4f40 fffff804`3031757c     : 00000013`f61d2f3c fffff804`30d0d0f0 fffff804`30d0d1a0 fffff804`3042e17b : nt!HalpTimerClockInterrupt+0x109
fffff804`328f4f70 fffff804`3042e3da     : fffff804`328e51e0 fffff804`30d0d0f0 fffff804`2b78c180 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
fffff804`328f4fb0 fffff804`3042ec47     : 00000000`80000000 fffff804`3042ec54 00000000`32d76d37 fffff804`328e5328 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff804`328e5160 fffff804`30246250     : 00000000`80000000 fffff804`30585032 00000000`fffff804 00000000`00fffff8 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff804`328e52f0 fffff804`30585032     : 00000000`fffff804 00000000`00fffff8 00000000`0000ffff 00000013`00000000 : nt!KeYieldProcessorEx+0x20
fffff804`328e5300 fffff804`30336964     : fffff804`30d1f9e0 ffffbc03`54d1c000 fffff804`328e53e0 fffff804`328e53e8 : nt!KiConfigureHeteroProcessorsTarget+0x72
fffff804`328e5390 fffff804`303e923e     : 00000000`0000000c 0000000c`00000001 fffff487`a92d7570 00000000`00000000 : nt!KiInitiateGenericCallDpc+0xa4
fffff804`328e53e0 fffff804`302a7a4c     : 00000000`00000000 fffff804`328e5a50 00000000`00000001 fffff804`2b78f4d0 : nt!KiGenericCallDpcInitiatorDpc+0x2e
fffff804`328e5410 fffff804`302a6a3a     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x42c
fffff804`328e5950 fffff804`3043107e     : 00000000`00000000 fffff804`2b78c180 fffff804`30d4c6c0 ffffbc03`62156080 : nt!KiRetireDpcList+0x1ba
fffff804`328e5c00 00000000`00000000     : fffff804`328e6000 fffff804`328df000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e

STACK_COMMAND:  ~11 ; .cxr ; kb

SYMBOL_NAME:  nt!KeAccumulateTicks+3cd

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1848

BUCKET_ID_FUNC_OFFSET:  3cd

FAILURE_BUCKET_ID:  0x133_DPC_nt!KeAccumulateTicks

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------
Windows Ev | Windows 11 | Performans ve sistem hataları

Kilitli Soru. Bu soru Microsoft Destek Topluluğu’ndan aktarıldı. Yararlı olup olmadığını belirtmek için oy verebilirsiniz ancak yorum veya yanıt ekleyemez ya da soruyu takip edemezsiniz.

0 yorum

27 yanıt

Sıralama ölçütü: En Eski
En yararlı En Yeni En Eski
  1. Igor Leyko 112.4K Saygınlık puanı Bağımsız Danışman
    2023-06-20T22:27:04+00:00

    Hi,

    My name is Igor, it's a pleasure for me to help others and I'll do all my best to help you.

    Please reinstall graphic drivers, repair system files by

    DISM.exe /Online /Cleanup-Image /RestoreHealth

    command from Windows Terminal (admin) environment.

    If the problem persists, share memory dumps to OneDrive for analysis.

    https://answers.microsoft.com/en-us/windows/for...

    Bu yanıt yardımcı oldu mu?

    0 yorum
  2. Anonim
    2023-06-20T22:30:52+00:00

    Hello, first of all, thank you for your reply. After doing what you said, as I mentioned, I don't get the error for about 1 month, then it starts again. I don't want to deal with such things all the time. I **** looking for a definitive solution, if there is a document you want, I would like to share it now.

    Bu yanıt yardımcı oldu mu?

    0 yorum
  3. Igor Leyko 112.4K Saygınlık puanı Bağımsız Danışman
    2023-06-20T22:47:39+00:00

    Sorry but it is needed to make a diagnosis before suggesting a solution. Can you tell me what exactly is wrong with your system? I suppose, the answer is no.

    So I suggest to update files, run Windows memory diagnostic tool and switch it to extended mode when it starts (F1 key). Note, test hang at ~21% for more than 2-3 hours means memory error too.

    Turn off XMP mode in BIOS if it is turned on.

    Or you may check your PC in Acer service center.

    P.S. Could it be you've installed a graphic driver not from Acer site?

    Bu yanıt yardımcı oldu mu?

    0 yorum
  4. Anonim
    2023-06-20T22:57:40+00:00

    I think the problem is from last source windows so last resort I will factory reset my computer. I tested with memtest86, which is said to give more reliable results than the Windows tool, and I didn't get any errors. The installed graphics driver is probably not available on the Acer website because I **** using the latest driver released by nvidia.

    Bu yanıt yardımcı oldu mu?

    0 yorum
  5. Igor Leyko 112.4K Saygınlık puanı Bağımsız Danışman
    2023-06-20T23:22:12+00:00

    Did you use Memtest Free or Memtest Pro? Free version skips some tests.

    Please reinstall graphic driver from Acer site, it may be more correct than general driver.

    Bu yanıt yardımcı oldu mu?

    0 yorum