BSOD Code 133: DPC Watchdog Violation while playing Apex Legends

Question

BSOD Code 133: DPC Watchdog Violation while playing Apex Legends

Anonymous

Hello everyone, I'm having issues playing Apex Legends (so far no other games but I have not given hardly any time to other games since building this system). It takes hours, but eventually I will get a BSOD with code 133 for DPC Watchdog Violation. Also, each time it seems that a minidump creation is failed, but I do get a MEMORY.dmp. That analysis is listed below, but unless I am doing something wrong it seems inconclusive, at least to my untrained eyes. I have tried Memory Debugging, dskchk, checking all drivers, redownloading Radeon drivers, even returned and replaced the NVMe boot drive with a clean install of Windows as of yesterday, but last night I got the BSOD again. This is really bugging me as it is a new machine that works wonderfully otherwise. My specs are below as well as the WinDbg analysis of the MEMORY.dmp file. If you need any other information, please let me know and I will do my best to gather it for you.

System Specs:

CPU: Intel i9-10850K

MOBO: Asus Z490-A Prime

GPU: Asus Radeon RX 6900 XT Reference

RAM: G.Skill Ballistix 2x16GB 3600 CL16

SSD: Inland 1TB QLC NVMe SSD

PSU: EVGA 750GT

COOLER: Noctua NH-D15S

CASE: Fractal Meshify S2

WinDbg MEMORY.dmp Analysis:

Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64

Loading Dump File [C:\Users\Alex\Desktop\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

************* Path validation summary **************

Response Time (ms) Location

Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols

Executable search path is:

Missing image name, possible paged-out or corrupt data.

*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000

*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000

Unable to add module at 00000000`00000000

WARNING: .reload failed, module list may be incomplete

Debugger can not determine kernel base address

Windows 10 Kernel Version 19041 MP (20 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

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

Machine Name:

Kernel base = 0xfffff80074000000 PsLoadedModuleList = 0xfffff80074c2a2f0

Debug session time: Sun Jan 17 22:41:14.929 2021 (UTC - 5:00)

System Uptime: 0 days 3:30:21.625

Missing image name, possible paged-out or corrupt data.

*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000

*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000

Unable to add module at 00000000`00000000

WARNING: .reload failed, module list may be incomplete

Debugger can not determine kernel base address

Loading Kernel Symbols

Missing image name, possible paged-out or corrupt data.

.*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000

*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000

Unable to add module at 00000000`00000000

Unable to read KLDR_DATA_TABLE_ENTRY at 00000000`00000000 - HRESULT 0x80004002

Loading unloaded module list

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

WARNING: .reload failed, module list may be incomplete

GetContextState failed, 0xD0000147

CS descriptor lookup failed

GetContextState failed, 0xD0000147

For analysis of this file, run !analyze -v

GetContextState failed, 0xD0000147

0: kd> !analyze -v

GetContextState failed, 0xD0000147

Unable to get program counter

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

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

* *

* 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: fffff80074cfa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

additional information regarding this single DPC timeout

Debugging Details:

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec

Value: 0

Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on DESKTOP-BB3O6KO

Key : Analysis.DebugData

Value: CreateObject

Key : Analysis.DebugModel

Value: CreateObject

Key : Analysis.Elapsed.Sec

Value: 0

Key : Analysis.Memory.CommitPeak.Mb

Value: 41

Key : Analysis.System

Value: CreateObject

BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80074cfa320

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

STACK_TEXT:

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x133

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {13e3c9ef-8526-da41-b41d-06d8277b0319}

Followup: MachineOwner

GetContextState failed, 0xD0000147

0: kd> lmvm Unknown_Module

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Browse full module list

start end module name

GetContextState failed, 0xD0000147

0: kd> lmDv

start end module name

Unloaded modules:

fffff80072ab0000 fffff80072ca2000 EasyAntiCheat.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 001F2000

fffff80072630000 fffff8007263c000 umpass.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 0000C000

fffff800728b0000 fffff80072aa2000 EasyAntiCheat.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 001F2000

fffff800726b0000 fffff800728a2000 EasyAntiCheat.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 001F2000

fffff80072cb0000 fffff80072ea2000 Unknown_Module_fffff800`72cb0000

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 001F2000

fffff80072ab0000 fffff80072ca2000 EasyAntiCheat.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 001F2000

fffff800728b0000 fffff80072aa2000 EasyAntiCheat.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 001F2000

fffff800726b0000 fffff800728a2000 EasyAntiCheat.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 001F2000

fffff80072670000 fffff8007268d000 EhStorClass.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 0001D000

fffff800725f0000 fffff8007260d000 EhStorClass.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 0001D000

fffff8007a0c0000 fffff8007a0dd000 EhStorClass.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 0001D000

fffff8008d400000 fffff8008d40f000 dump_storport.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 0000F000

fffff8008e400000 fffff8008efe6000 dump_iaStorAC.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 00BE6000

fffff8008f010000 fffff8008f02e000 dump_dumpfve.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 0001E000

fffff80090470000 fffff8009048c000 dam.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 0001C000

fffff80079050000 fffff80079061000 WdBoot.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 00011000

fffff8007ac90000 fffff8007aca1000 hwpolicy.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 00011000

GetContextState failed, 0xD0000147

0: kd> lmDvsm

start end module name

Unloaded modules:

fffff80072ab0000 fffff80072ca2000 EasyAntiCheat.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 001F2000

fffff80072630000 fffff8007263c000 umpass.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 0000C000

fffff800728b0000 fffff80072aa2000 EasyAntiCheat.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 001F2000

fffff800726b0000 fffff800728a2000 EasyAntiCheat.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 001F2000

fffff80072cb0000 fffff80072ea2000 Unknown_Module_fffff800`72cb0000

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 001F2000

fffff80072ab0000 fffff80072ca2000 EasyAntiCheat.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 001F2000

fffff800728b0000 fffff80072aa2000 EasyAntiCheat.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 001F2000

fffff800726b0000 fffff800728a2000 EasyAntiCheat.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 001F2000

fffff80072670000 fffff8007268d000 EhStorClass.sys

Timestamp: unavailable (00000000)

Checksum: 00000000

ImageSize: 0001D000

fffff800725f0000 fffff8007260d000 EhStorClass.sys

Timestamp: unavailable

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Answer 1

Hi,

Thank you for writing to Microsoft Community Forums.

We understand your concern as you are receiving Blue Screen of Death. The analysis of the dump file indicates that the faulty module is Unknown_Module

The DPC_WATCHDOG_VIOLATION bug check has a value of 0x00000133. This bug check indicates that the DPC watchdog executed, either because it detected a single long-running deferred procedure call (DPC), or because the system spent a prolonged time at an interrupt request level (IRQL) of DISPATCH_LEVEL or above. The value of Parameter 1 indicates whether a single DPC exceeded a timeout, or whether the system cumulatively spent an extended period of time at IRQL DISPATCH_LEVEL or above. DPCs should not run longer than 100 microseconds and ISRs should not run longer than 25 microseconds, however the actual timeout values on the system are set much higher.

Let us try few steps.

Step 1: Run Driver verifier

Driver Verifier monitors Windows kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject Windows drivers to a variety of stresses and tests to find improper behavior. You can configure which tests to run, which allows you to put a driver through heavy stress loads or through more streamlined testing. Please refer this article: Driver verifier

Step 2: Remove and reinstall the driver.

We would recommend you to****create a restore point before you proceed with the steps, refer the article to Create a system restore point.

1. Press Windows + X key and select Device Manager from the context menu.

2. Spot and expand the Display adapters & Human Interface Devices.

3. Right click on the driver and select “Uninstall”

4. Check the box beside “Delete the driver software for this device”

5. Then download and install the latest version of the driver again from Asus website

Additionally, refer the steps as mention in this article: Troubleshoot blue screen errorsrefer**(While using my device)**

Let us know the results. If the issue persists, we will certainly assist you further.

Aditya Roy

Microsoft Community – Moderator

Share via

BSOD Code 133: DPC Watchdog Violation while playing Apex Legends

1 answer