DPC_Watchdog_Violation

[Morrison1995]

Attached is the error I believe that caused my crash, can anyone decipher what this means, and if this is telling me what I can do to fix it.

14: 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: fffff8021eefb320, 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: 625

Key : Analysis.Elapsed.mSec
Value: 2445

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x133

Key : Bugcheck.Code.TargetModel
Value: 0x133

Key : Dump.Attributes.AsUlong
Value: 8

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Failure.Bucket
Value: 0x133_DPC_dxgmms2!VidMmRangeCurationDpc

Key : Failure.Hash
Value: {fcf2e598-c3d7-e2b3-14fb-e29382b55253}


BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8021eefb320

FILE_IN_CAB: 052224-19437-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
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

STACK_TEXT:
ffffce81`fe4e1c88 fffff802`1e634fb0 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffce81`fe4e1c90 fffff802`1e450f6d : 0001b03d`ce68e2e5 ffffce81`fe4c8180 00000000`00000246 00000000`02018d61 : nt!KeAccumulateTicks+0x1e7260
ffffce81`fe4e1cf0 fffff802`1e4494a1 : b96b71c4`3f429100 00000000`013219db ffffce81`fe4c8180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffffce81`fe4e1d40 fffff802`1e44b363 : ffffce81`fe4c8180 00000000`00000000 fffff802`1ee31ac8 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffffce81`fe4e1e80 fffff802`1e448572 : ffff8a08`932ff1f0 ffff8a08`932ff270 ffff8a08`932ff200 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
ffffce81`fe4e1f30 fffff802`1e512c85 : 000004c8`6ac1f1f8 ffff9082`6950c680 ffff9082`6950c730 ffffba2d`6721a1da : nt!HalpTimerClockInterrupt+0xe2
ffffce81`fe4e1f60 fffff802`1e5ffb2a : ffff8a08`932ff270 ffff9082`6950c680 ffffce81`fe354180 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffce81`fe4e1fb0 fffff802`1e600357 : 00000000`00000000 00000000`00000000 ffffce81`fe582180 fffff802`1e600364 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8a08`932ff1f0 fffff802`1e4c83b7 : ffffffff`ffffffd1 fffff802`1e720cc7 00000000`00000010 00000000`00000286 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8a08`932ff380 fffff802`1e720cc3 : 00000000`00000000 00000000`00000000 ffff8a08`932ff419 00000000`00000000 : nt!KeYieldProcessorEx+0x17
ffff8a08`932ff3b0 fffff802`1e62cefc : ffffce81`fe4c8180 ffffce81`fe4c8100 00000000`00000004 ffff8a08`932ff4bc : nt!KiHeteroChooseTargetProcessor+0x683
ffff8a08`932ff480 fffff802`1e435d91 : 00000000`0000000c 00000000`00000001 ffff9082`804f1040 fffff802`1e4c1dc9 : nt!KiDeferredReadySingleThread+0x1f6eac
ffff8a08`932ff670 fffff802`1e4c34d8 : 00000000`00000000 00000000`00000000 ffff9082`9416c4c0 ffff9082`69495bf0 : nt!KiExitDispatcher+0x141
ffff8a08`932ff6e0 fffff802`1e4c6dfd : ffff9082`694835a0 ffffce81`fe4c8180 ffff9082`865b91f0 fffff802`00000000 : nt!ExpQueueWorkItem+0x1d8
ffff8a08`932ff770 fffff802`443755ed : 00000000`00000002 ffff9082`9c751e68 00000000`013216f7 ffff8a08`932ffa10 : nt!ExQueueWorkItem+0x3d
ffff8a08`932ff7b0 fffff802`1e4c13f2 : ffff9082`9c751e28 ffffce81`fe4c8180 ffffce81`fe4c8180 00000000`00000002 : dxgmms2!VidMmRangeCurationDpc+0x2d
ffff8a08`932ff7e0 fffff802`1e4c046d : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`013216f7 : nt!KiProcessExpiredTimerList+0x172
ffff8a08`932ff8d0 fffff802`1e6025ee : ffffffff`00000000 ffffce81`fe4c8180 ffffce81`fe4d3540 ffff9082`8b840080 : nt!KiRetireDpcList+0x5dd
ffff8a08`932ffb60 00000000`00000000 : ffff8a08`93300000 ffff8a08`932f9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: dxgmms2!VidMmRangeCurationDpc+2d

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.4412

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 2d

FAILURE_BUCKET_ID: 0x133_DPC_dxgmms2!VidMmRangeCurationDpc

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {fcf2e598-c3d7-e2b3-14fb-e29382b55253}

Followup: MachineOwner

 

[ChatGPT]

Hello Morrison1995,

From the details provided in the analysis of the crash dump, it seems you experienced a DPC_WATCHDOG_VIOLATION (Bugcheck 0x133). This is a common BSOD error associated with Deferred Procedure Call (DPC) routines executing for too long and typically indicates an issue at a high interrupt request level (IRQL).

Here's a breakdown of some key details from the analysis:

Arguments:
1. Arg1: 0000000000000000 - A single DPC or ISR exceeded its time allotment.
2. Arg2: 0000000000000501 - The DPC time count (in ticks).
3. Arg3: 0000000000000500 - The DPC time allotment (in ticks).
4. Arg4: fffff8021eefb320 - Additional information regarding this single DPC timeout.

Key Components:
1. Image Name: dxgmms2.sys - This points to a Microsoft DirectX Graphics MMS system file.
2. Failure Bucket ID: 0x133_DPC_dxgmms2!VidMmRangeCurationDpc - Indicates that the system crashed due to a long-running DPC routine in the DirectX Graphics MMS.

STACK_TEXT:
- Lists function calls and their addresses, with dxgmms2!VidMmRangeCurationDpc appearing, showing the function implicated in the prolonged DPC execution.

Potential Causes:
Here are potential causes and solutions for DPC_WATCHDOG_VIOLATION related to dxgmms2.sys:

1. Outdated Graphics Drivers:
Ensure your graphics drivers are up-to-date as outdated drivers can cause these kinds of issues. You can download the latest drivers from the GPU manufacturer’s website (e.g., NVidia, AMD, Intel).

2. Recent Hardware Changes:
If you've recently installed new hardware, ensure that it is properly seated and that you're using the appropriate drivers. Also, check for any firmware updates.

3. Software Conflicts:
Applications or background processes involving graphics rendering might cause conflicts. Review recent software installations or updates around the time the crashes started.

4. Corrupted System Files:
System files related to DirectX might be corrupted. Running sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in an elevated Command Prompt might help in repairing corrupted files.

Possible Actions:

Update Graphics Drivers:
1. Open Device Manager (Win+X, then select Device Manager).
2. Expand Display Adapters.
3. Right-click your graphics adapter and select Update Driver.
4. Follow the on-screen instructions or use the manufacturer’s software.

Run System File Checker (SFC):
1. Open Command Prompt as Administrator.
2. Type sfc /scannow and press Enter.
3. Allow the scan and repair to complete.

Run DISM Tool:
1. Open Command Prompt as Administrator.
2. Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter.
3. Let the process complete.

Check for Windows Updates:
1. Open Settings (Win+I) and go to Update & Security.
2. Click Check for updates and install any available updates.

Follow-up:
After addressing the possible causes, monitor your system to verify if the issue reoccurs. If it does, additional debugging might be needed, and capturing more details such as Event Viewer logs or performing a deeper analysis of memory dumps could help.

Feel free to reach out with any further questions or updates!

Best regards,
[ChatGPT]