Constant Crashing in Games that use Anti-Cheat Software

I read this has to do with a Windows 11 Security update last week, and game devs are defelcting to the Anti-Cheat makers, who are of course saying Microsoft needs to fix the issue.
I had the Kernel-Stack warning in Defender after updating, I dismissed it and it went away on reboot - I have SVM off in BIOS since I don't use Core Isolation or Memory Integrity since it takes away from gaming performance. Since this feature is dependent on Core Isolation, when I clicked on 'settings' in the warning pop-up in defender it could not find anything because SVM is off in BIOS (AMD).
Since then every game with Anti-Cheat freezes then crashes the entire PC, forcing reboot.
PC - 5800X3D, X570 Board, 32GB DDR4 @ 3600Mhz, RTX 4090

Can anyone advise what KB was related to this problem so I can try to uninstall?

Attaching analysis of MiniDump from WinDbg, which will show that it's the Nvidia driver that failed. However, that is just the symptom of the problem that caused the crash, as this driver has been working perfectly until the recent Windows Security update. I did try multiple other drivers (DDU in safe mode for each one) with the exact same result.

I have ran Firestrike Extreme Stress Test (20 loops) 5 or 6 times with perfect results, so it's not a GPU or driver issue as this test really hammers the GPU and finds instabilities if they are exist - of course 3D Mark doesn't user Anti-Cheat software!
Also ran memtest_vulkan for 2 hours with 100% pass - never used this app before but it does make the VRAM toasty with 80C highest temp (still well below Micron's max temps for GDDR6X).
Can anyone help?

For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`560293a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff801`5c6619b0=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: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff8015691c340, 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 ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2031

Key : Analysis.Elapsed.mSec
Value: 2615

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

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

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

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x133

Key : Failure.Bucket
Value: 0x133_ISR_nvlddmkm!unknown_function

Key : Failure.Hash
Value: {f97493a5-ea2b-23ca-a808-8602773c2a86}

Key : Hypervisor.Enlightenments.Value
Value: 0

Key : Hypervisor.Enlightenments.ValueHex
Value: 0

Key : WER.OS.Branch
Value: ni_release

Key : WER.OS.Version
Value: 10.0.22621.1


BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8015691c340

BUGCHECK_P4: 0

FILE_IN_CAB: 042423-7703-01.dmp

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME: fffff8015c651ec0 -- (.trap 0xfffff8015c651ec0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffb58a66dffa02
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80155e3556b rsp=fffff8015c652050 rbp=fffff8015c6521e0
r8=0000000000000000 r9=0000000000000000 r10=fffff8017b8acb40
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KzLowerIrql+0x1b:
fffff801`55e3556b 4883c420 add rsp,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff801`5c6619a8 fffff801`55ebb9af : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`5691c340 : nt!KeBugCheckEx
fffff801`5c6619b0 fffff801`55eba7f4 : 000006e9`b8edcd43 fffff801`542c8180 00000000`0002d8df 00000000`00000000 : nt!KeAccumulateTicks+0x23f
fffff801`5c661a10 fffff801`55eba6d3 : 00000000`00000010 00000000`00000000 fffff801`542c8180 00000006`c9c5eb00 : nt!KiUpdateRunTime+0xf4
fffff801`5c661bd0 fffff801`55eb88fe : 00000000`00000000 fffff801`542c8180 ffffffff`ffffffff 00000000`00000002 : nt!KiUpdateTime+0x13e3
fffff801`5c661e90 fffff801`55eb810a : fffff801`5685ffd8 fffff801`5690df20 fffff801`5690df20 00000000`00000000 : nt!KeClockInterruptNotify+0x3de
fffff801`5c661f40 fffff801`55f4b46e : 00000006`ca94d7bd fffff801`5690de70 fffff801`542c8180 00000000`00000000 : nt!HalpTimerClockInterrupt+0x10a
fffff801`5c661f70 fffff801`5602b4fa : fffff801`5c651f40 fffff801`5690de70 fffff801`5c6521e0 fffff801`5c6521e0 : nt!KiCallInterruptServiceRoutine+0x19e
fffff801`5c661fb0 fffff801`5602bd67 : fffff801`560252c0 fffff801`55f501fa 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff801`5c651ec0 fffff801`55e3556b : ffffb58a`67eb2000 00000000`00000f00 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff801`5c652050 fffff801`7acdbd23 : fffff801`5c6521e0 ffffb58a`735e8000 fffff801`5c6521e0 fffff801`55e261d1 : nt!KzLowerIrql+0x1b
fffff801`5c652080 fffff801`5c6521e0 : ffffb58a`735e8000 fffff801`5c6521e0 fffff801`55e261d1 fffff801`5c652230 : nvlddmkm+0xabd23
fffff801`5c652088 ffffb58a`735e8000 : fffff801`5c6521e0 fffff801`55e261d1 fffff801`5c652230 fffff801`7acdd637 : 0xfffff801`5c6521e0
fffff801`5c652090 fffff801`5c6521e0 : fffff801`55e261d1 fffff801`5c652230 fffff801`7acdd637 ffffb58a`67eb2000 : 0xffffb58a`735e8000
fffff801`5c652098 fffff801`55e261d1 : fffff801`5c652230 fffff801`7acdd637 ffffb58a`67eb2000 ffffb58a`735e8000 : 0xfffff801`5c6521e0
fffff801`5c6520a0 fffff801`7acca5f4 : ffffb58a`67eb2000 ffffb58a`735e8000 ffffb58a`67eb2000 ffffb58a`735e8000 : nt!KeInsertQueueDpc+0x11
fffff801`5c6520e0 ffffb58a`67eb2000 : ffffb58a`735e8000 ffffb58a`67eb2000 ffffb58a`735e8000 fffff801`00000004 : nvlddmkm+0x9a5f4
fffff801`5c6520e8 ffffb58a`735e8000 : ffffb58a`67eb2000 ffffb58a`735e8000 fffff801`00000004 fffff801`55e2341d : 0xffffb58a`67eb2000
fffff801`5c6520f0 ffffb58a`67eb2000 : ffffb58a`735e8000 fffff801`00000004 fffff801`55e2341d 000000ff`00000f00 : 0xffffb58a`735e8000
fffff801`5c6520f8 ffffb58a`735e8000 : fffff801`00000004 fffff801`55e2341d 000000ff`00000f00 00000000`00000001 : 0xffffb58a`67eb2000
fffff801`5c652100 fffff801`00000004 : fffff801`55e2341d 000000ff`00000f00 00000000`00000001 fffff801`5694c6c0 : 0xffffb58a`735e8000
fffff801`5c652108 fffff801`55e2341d : 000000ff`00000f00 00000000`00000001 fffff801`5694c6c0 00000000`00000000 : 0xfffff801`00000004
fffff801`5c652110 000002a6`ee367cd8 : 000002a6`ee367cd8 000002a7`479eabd8 00000000`00000000 00000000`00000000 : nt!PpmPerfQueueAction+0x4d
fffff801`5c652150 000002a6`ee367cd8 : 000002a7`479eabd8 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000002a6`ee367cd8
fffff801`5c652158 000002a7`479eabd8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000022`00000000 : 0x000002a6`ee367cd8
fffff801`5c652160 00000000`00000000 : 00000000`00000000 00000000`00000000 00000022`00000000 00000000`00000000 : 0x000002a7`479eabd8


SYMBOL_NAME: nvlddmkm+abd23

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: abd23

FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}

Followup: MachineOwner
---------

Globespy said:

I have SVM off in BIOS since I don't use Core Isolation or Memory Integrity since it takes away from gaming performance.

Click to expand...

I can't speak for "AMD" builds, only know Intel, but on my rig (see system spec), Memory Integrity is enabled and I've no game performance issues. Well, there was an issue as described below, but it had nothing to do with Core Isolation/Memory Integrity.

That said, I do note that you tested the GPU, and it passed tests So it appears the GPU is good?

Globespy said:

I have ran Firestrike Extreme Stress Test (20 loops) 5 or 6 times with perfect results, so it's not a GPU or driver issue as this test really hammers the GPU and finds instabilities if they are exist - of course 3D Mark doesn't user Anti-Cheat software!
Also ran memtest_vulkan for 2 hours with 100% pass - never used this app before but it does make the VRAM toasty with 80C highest temp (still well below Micron's max temps for GDDR6X).

Click to expand...

Anyway, It would help if you gave example of games. Example I know Division 2 uses Anti-Cheat as I'm currently playing the game now.

With that, and this probably won't apply to your, but.... I actually did have a massive issue with Division 2 constantly hard locking my PC. Turned out I couldn't play any game for more than 10-munites before the PC would hard lock. Long story short, it turned out to be my power supply. Basically, anytime the GPU was pushed, it would tax the power supply, which would then cause it to flake out and hard lock the PC. Swapping power supplies from my backup solved the issue, and now I can play Division 2 for hours without issue. Another tale-tell sign was my BIOS kept resetting if I powered off the PC (not just sign out or put it in sleep mode), but actually powered off the PC.

Point?
1) Game also uses Anti-Cheat system
2) Hard locks like you
3) Since replacing the PS two months ago, the issue disappeared

Again, this probably doesn't apply to you (based on your GPU tests), but it is something to note.

Good luck.

Before posting a BSOD thread, please read the instructions here: https://www.elevenforum.com/t/bsod-posting-instructions.103/

Dru2 said:

I can't speak for "AMD" builds, only know Intel, but on my rig (see system spec), Memory Integrity is enabled and I've no game performance issues. Well, there was an issue as described below, but it had nothing to do with Core Isolation/Memory Integrity.

That said, I do note that you tested the GPU, and it passed tests So it appears the GPU is good?


Anyway, It would help if you gave example of games. Example I know Division 2 uses Anti-Cheat as I'm currently playing the game now.

With that, and this probably won't apply to your, but.... I actually did have a massive issue with Division 2 constantly hard locking my PC. Turned out I couldn't play any game for more than 10-munites before the PC would hard lock. Long story short, it turned out to be my power supply. Basically, anytime the GPU was pushed, it would tax the power supply, which would then cause it to flake out and hard lock the PC. Swapping power supplies from my backup solved the issue, and now I can play Division 2 for hours without issue. Another tale-tell sign was my BIOS kept resetting if I powered off the PC (not just sign out or put it in sleep mode), but actually powered off the PC.

Point?
1) Game also uses Anti-Cheat system
2) Hard locks like you
3) Since replacing the PS two months ago, the issue disappeared

Again, this probably doesn't apply to you (based on your GPU tests), but it is something to note.

Good luck.

Click to expand...

How did you know it was your PSU? Were you seeing rail variances that were out of spec? On that subject, I've read many reports that the +12V rail often dips close to the 5% permissable by the ATX standard on the RTX 4090 cards. HWInfo64 shows everything within spec on mine, it's an EVGA G6 1000W 80+ Gold, less than 2 years old so I'm inclined to think it's not the PSU.

Globespy said:

How did you know it was your PSU?

Click to expand...

You quoted me but apparently missed this...

Dru2 said:

Another tale-tell sign was my BIOS kept resetting if I powered off the PC (not just sign out or put it in sleep mode), but actually powered off the PC.

Click to expand...

Anyway, that along with the hard locks (resulting in forced re-boots), and Windows indicating a "hardware" issue in Reliability History led me to look at the power supply.

Also looking in the BIOS, I noticed my 3.3 and 5+ voltages were a little low. The 3.3v was reading 3.1 and 5+ volt was reading 4.5. Switching power supplies, the voltages are now normal.... and my crashing issues are completely gone.



Initially I was pretty sure it was a GPU issue. I even took it apart and re-pasted / re-padded. Same issue. It was only when I started putting things together, especially why the BIOS kept resetting after the system was powered off, even though I changed the CMOS battery twice that I decided to look at the power supply. That turned out to be the problem.

All, that said, I'm not saying you have a PS issue. It could be something totally different. You just need to pay attention to everything that's happening with your PC to try and pinpoint the issue. Have you tried another game not using the Anti-Cheat system?

Also, have you looked at Reliability History? Could be very revealing. Simply type "Reliability History" in search to access it.

@Dru2
Thanks for the reply and tips.
The 5v that low would be concerning, the 3v less so unless you have a ton of hard drives.
The 12v is really the important one.
How old was the PSU that was causing your issues?

My post was merely about keeping an open mind. I was sure my issue was a GPU. It turned out to be a power supply.

Yours may be something else. I'm NOT saying your issue is a power supply, I'm saying don't focus on one thing - Anti-Cheat.

And the faulty power supply in question (purchased in 2019) can be seen in my system specs. It has since been swapped with a similar one (both EVGA 1000 watt) from my was in my backup system. And now my issues are gone.

Good luck.