Windows 10: DPC_WATCHDOG_VIOLATION 133 BSOD ntkrnlmp.exe

[COLOR=rgba96, 106, 116, 1] Hello There![/COLOR]

[COLOR=rgba96, 106, 116, 1]I would like to ask help, rather for a long time constant BOSD is my problem, and I do not manage to solve it.[/COLOR]

[COLOR=rgba96, 106, 116, 1]I receive a diverse mistake when I try to analyse the mistake, and i don't know what can I do.[/COLOR]

This is thi last one dump:

Loading Dump File [C:\Windows\Minidump\032221-4156-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available



Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 19041 MP 16 procs Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff806`66600000 PsLoadedModuleList = 0xfffff806`6722a490

Debug session time: Mon Mar 22 16:11:24.214 2021 UTC + 1:00

System Uptime: 0 days 1:11:32.422

Loading Kernel Symbols

...............................................................

................................................................

........................................................

Loading User Symbols

Loading unloaded module list

..........

For analysis of this file, run !analyze -v

8: 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. The offending component can usually be

identified with a stack trace.

Arg2: 0000000000001e00, The watchdog period.

Arg3: fffff806672fb320, 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 ***

*** ***

*************************************************************************

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



KEY_VALUES_STRING: 1



Key : Analysis.CPU.Sec

Value: 4



Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on DESKTOP-FTFPCQ1



Key : Analysis.DebugData

Value: CreateObject



Key : Analysis.DebugModel

Value: CreateObject



Key : Analysis.Elapsed.Sec

Value: 28



Key : Analysis.Memory.CommitPeak.Mb

Value: 80



Key : Analysis.System

Value: CreateObject





BUGCHECK_CODE: 133



BUGCHECK_P1: 1



BUGCHECK_P2: 1e00



BUGCHECK_P3: fffff806672fb320



BUGCHECK_P4: 0



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



STACK_TEXT:

ffff9080`30dd9e18 fffff806`66a3ac52 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`672fb320 : nt!KeBugCheckEx

ffff9080`30dd9e20 fffff806`6686f9a3 : 00000f3d`903ad0cf ffff9080`30dc0180 00000000`00000000 ffff9080`30dc0180 : nt!KeAccumulateTicks+0x1c8a52

ffff9080`30dd9e80 fffff806`6686f48a : ffffe58d`770d9b20 fffff908`e848bb10 00000000`00000000 ffff9080`30dc0180 : nt!KeClockInterruptNotify+0x453

ffff9080`30dd9f30 fffff806`66927f55 : ffffe58d`770d9b20 00000000`00000000 00000000`00000000 ffffec0e`c87fc2c7 : nt!HalpTimerClockIpiRoutine+0x1a

ffff9080`30dd9f60 fffff806`669f76fa : fffff908`e848bb10 ffffe58d`770d9b20 00000000`00000c7e 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5

ffff9080`30dd9fb0 fffff806`669f7c67 : ffff8586`10eaeae7 00000000`00000000 ffff9080`30dc0180 00000000`00000001 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

fffff908`e848ba90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37





SYMBOL_NAME: nt!KeAccumulateTicks+1c8a52



MODULE_NAME: nt



IMAGE_NAME: ntkrnlmp.exe



IMAGE_VERSION: 10.0.19041.867



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: 1c8a52



FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks



OS_VERSION: 10.0.19041.1



BUILDLAB_STR: vb_release



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}



Followup: MachineOwner

*******************


I try to reinstall the windows, but the problem is stay, i was able to change my RAM, but the mistake remain.


I ask their help and thank you.


Best regards

Sandor Olah

:)

 

BSOD UNEXPECTED_KERNEL_MODE_TRAP

Hi, OttOiToto

The problem is caused by (ntkrnlmp.exe)

Check this link, I hope it helps

https://www.thewindowsclub.com/fix-ntkrnlmp-exe...

Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised
on the site before you decide to download and install it.

Let us know if these steps help you to resolve the issue.

 

BSOD playing GuildWars2, DPC_WATCHDOG_VIOLATION


Your dump files are not very forthcoming. I can tell you that when ntkrnlmp or ntoskrnl is listed, that is not the cause. In looking at you dump files, I am getting a lot of these

Code:

Code:

Use !analyze -v to get detailed debugging information.  BugCheck 133, {1, 1e00, 0, 0}  Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )  Followup:     MachineOwner

What I do get is

Code:

Code:

Use !analyze -v to get detailed debugging information.  BugCheck 133, {1, 1e00, 0, 0}  Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+a480 )  Followup:     MachineOwner ---------  6: 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. The offending component can usually be     identified with a stack trace. Arg2: 0000000000001e00, The watchdog period. Arg3: 0000000000000000 Arg4: 0000000000000000  Debugging Details:

If you are overclocking anything, please set everything to default levels.. Please use software to keep a close watch on your CPU and GPU temps. Also, please go into BIOS and give me the temps of the CPU and motherboard. Also tell me the values of the +12V, +5V and + 3.3V.

Please let me know the results of the scan I asked you to do in the above post. If you have another BSOD, please upload the DM Log collector again. Also, did you do the upgrade in the past few days? If you don't know, please hold down the Windows Key and press R, in the run box type winver. If you did the upgrade it will say version 1511 (OS Build 10586.3) Also, how opposed are you to doing a clean install if it is necessary and do you have a spare hard drive?

 

Windows 10 build 10586 BSOD DPC_WATCHDOG_VIOLATION

Check (enable) it then do Step #5 & test.

The above notwithstanding...

Are you still getting the DPC_WATCHDOG_VIOLATION BSODs or...?