Windows 10: BSOD AV_nt!KxWaitForLockOwnerShip

Hello, recently my computer has been having a large amount of blue screens. These blue screens have only occurred whenever I am playing a game. This is the info from my most recent blue screen from the mini dump files, any help is very much appreciated.

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 1000007eThis is a very common bugcheck. Usually the exception address pinpointsthe driver/function that caused the problem. Always note this addressas well as the link date of the driver/image that contains this address.Some common problems are exception code 0x80000003. This means a hardcoded breakpoint or assertion was hit, but this system was booted/NODEBUG. This is not supposed to happen as developers should never havehardcoded breakpoints in retail code, but ...If this happens, make sure a debugger gets connected, and thesystem is booted /DEBUG. This will let us see why this breakpoint ishappening.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff8020568c9de, The address that the exception occurred atArg3: fffffa05703e9518, Exception Record AddressArg4: ffffa38143058930, Context Record AddressDebugging Details:------------------KEY_VALUES_STRING: 1 Key : AV.Fault Value: Read Key : Analysis.CPU.Sec Value: 2 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on TAC-MECH Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 3 Key : Analysis.Memory.CommitPeak.Mb Value: 68 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage DumpBUGCHECK_CODE: 7eBUGCHECK_P1: ffffffffc0000005BUGCHECK_P2: fffff8020568c9deBUGCHECK_P3: fffffa05703e9518BUGCHECK_P4: ffffa38143058930EXCEPTION_RECORD: fffffa05703e9518 -- .exr 0xfffffa05703e9518ExceptionAddress: fffff8020568c9de nt!KxWaitForLockOwnerShip+0x000000000000000e ExceptionCode: c0000005 Access violation ExceptionFlags: 00000000NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffffAttempt to read from address ffffffffffffffffCONTEXT: ffffa38143058930 -- .cxr 0xffffa38143058930rax=0000000000000000 rbx=fffffa05703e9860 rcx=fffffa05703e9860rdx=2000000000000000 rsi=000000000027c9c7 rdi=ffffd58204f864c8rip=fffff8020568c9de rsp=fffffa05703e9750 rbp=fffffa05703e9889 r8=0000000000000004 r9=0000000000000000 r10=7ffffffffffffffcr11=0000000000000000 r12=ffffd582061af420 r13=ffffc78001237dd0r14=fffff80205a6a3c0 r15=00000000ffffffffiopl=0 nv up ei ng nz na po nccs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286nt!KxWaitForLockOwnerShip+0xe:fffff802`0568c9de 48890a mov qword ptr [rdx],rcx ds:002b:20000000`00000000=????????????????Resetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemREAD_ADDRESS: fffff80205b733b8: Unable to get MiVisibleStateUnable to get NonPagedPoolStartUnable to get NonPagedPoolEndUnable to get PagedPoolStartUnable to get PagedPoolEndfffff80205a2a3c8: Unable to get Flags value from nt!KdVersionBlockfffff80205a2a3c8: Unable to get Flags value from nt!KdVersionBlockunable to get nt!MmSpecialPagesInUse ffffffffffffffff ERROR_CODE: NTSTATUS 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.EXCEPTION_CODE_STR: c0000005EXCEPTION_PARAMETER1: 0000000000000000EXCEPTION_PARAMETER2: ffffffffffffffffEXCEPTION_STR: 0xc0000005STACK_TEXT: fffffa05`703e9750 fffff802`0571778d : ffffd582`0e39e5e0 ffffd582`0e39e5f0 00000000`00000001 00000000`007f9b00 : nt!KxWaitForLockOwnerShip+0xefffffa05`703e9780 fffff802`05749f5e : ffffd582`04f863e0 ffffd582`05df0028 00000000`0027c9c7 00000000`0027c9c6 : nt!KeAcquireInStackQueuedSpinLock+0x7dfffffa05`703e97b0 fffff802`0574aa18 : ffffd582`061af420 fffffa05`00000001 00000000`0027c9c7 00000000`00000000 : nt!MiStoreWriteModifiedPages+0x376fffffa05`703e98f0 fffff802`0579168a : ffffd582`061af420 00000000`00000100 fffff802`0003280e ffffd582`00000100 : nt!MiGatherPagefilePages+0x44cfffffa05`703e99f0 fffff802`0566bce5 : ffffd582`03a40600 ffffd582`03a40600 00000000`00000080 fffff802`05791430 : nt!MiModifiedPageWriter+0x25afffffa05`703e9c10 fffff802`057c99ca : fffff802`04023180 ffffd582`03a40600 fffff802`0566bc90 7c416752`f64110a2 : nt!PspSystemThreadStartup+0x55fffffa05`703e9c60 00000000`00000000 : fffffa05`703ea000 fffffa05`703e4000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2aSYMBOL_NAME: nt!KxWaitForLockOwnerShip+eMODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeIMAGE_VERSION: 10.0.18362.720STACK_COMMAND: .cxr 0xffffa38143058930 ; kbBUCKET_ID_FUNC_OFFSET: eFAILURE_BUCKET_ID: AV_nt!KxWaitForLockOwnerShipOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {724b07b1-4226-85fe-f372-16d33b9a3b93}Followup: MachineOwner---------

:)

 

Random BSoDs (nt!KxWaitForLockOwnerShip+14)

Hi,

I have had BSoD for a long time now, that are completely random in interval (sometimes multiple crashes a day, other times none for a week). Also they can't be tied to any specific activity, many happened during me being AFK.

Things I already tried:

Malwarebytes, sfc scannow, DISM, memtest (only 2 passes, will do more later), migrating the OS to an other device, putting the GPU in a different slot, using a different GPU, installing all drivers listed on the motherboard's manufacturer's support site,
reinstalling GPU driver with DDU, and finally: reinstalling windows (last time in january). After doing the latter things look fine for a few months, then the crashes start again (Maybe I make the same mistakes after every installation?).

The dump files:

report.rar

There are a few (all from a single day), so here is an excerpt of the contents (I was experimenting with verifier, but some "natural" BSoD-s got in the mix:

040618-5953-01 I used the verifier for this one. Says: unable to verify timestamp for vmulti.sys, VerifierExt.sys

IO_violation_type: 22e The caller has completed a successful IRP_MJ_PNP instead of passing it down.

during the BSOD it also mentioned wdf01000.sys

040618-7109-02 kmode exception not handled (1e)

probably caused by ntkrnlmp.exe (nt!KxWaitForLockOwnerShip+14)

Default_bucket_id: win8_driver_fault

process_name: MsMpEng.exe

exception code ffffffffc0000005

040618-6593-01 system service exception

probably caused by ntkrnlmp.exe (nt!KxWaitForLockOwnerShip+14)

exception code 00000000c0000005

default_bucket_id: win8_driver_fault

process_name: svchost.exe

040618-7312-01 kmode exception not handled (1e)

probably caused by ntkrnlmp.exe (nt!KxWaitForLockOwnerShip+14)

Default_bucket_id: win8_driver_fault

process_name: chrome.exe

exception code ffffffffc0000005

040618-6000-01 I used the verifier for this one. says: vmulti.sys

probably caused by ntkrnlmp.exe

iomanager violation (c9), type: 22e

040618-7203-01 sys thread exc not handled_M (1000007e)

unable to verify checksum for win32k.sys

exc code: c0000005 access violation

(nt!KxWaitForLockOwnerShipWithIrql+12)

Found out that vmulti is the driver for my graphics tablet. According to InstalledDriverList, error control is set to "ignore" for this driver.

Unticked vmulti, ran verifier again, to see what changes:

040618-6031-01 driver verifier detected violation (c4)

probably caused by: ntkrnlmp.exe (nt!VerifierBugCheckIfAppropriate+df)

default_bucket_id: verifier_enabled_vista_minidump

process name: system

Ran verifier with only null.sys checked, to see what happens. I didn't have a specific reason to pick null.sys, verifier didn't let

me start it with nothing being selected.

Checked verifier in cmd with querysettings, and it also checked ndis.sys and wdiwifi.sys without my consent

This, again resulted in a BSoD:

040618-7218-01 driver_irql_not_less_or_equal (d1)

probably caused by: NTFS.sys (NTFS!NtfsFsdDispatchSwitch$filt$0+0)

default_bucket_id: verifier_enabled_vista_minidump

process_name: MsMpEng.exe

Speccy report:

Speccy report - DESKTOP-63V2JON.pdf

Please help diagnosing this problem, I feel like I reached a dead end. The results seem completely random to me, and I have no idea what to make of all of this.

Kind thanks,

Peter

Edit: While I did not overclock anything, it seems like my CPU was running 100 MHz faster than specified. Strange. Prime 95 showed workers failing, so I disabled turbo, forcing the CPU to run at 4 GHz max, instead of 4.3 (The official boost speed was 4.2).
Now I see no workers failing, and I haven't crashed since then, but we'll see if that changes or not.

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.

 

7 different BSoD

Hey guys,

I have a serious problem. I make it as short as possible:

• system runs 100 % fine with the 10.12
• updatet to Catalyst 11.1 -> BSoD
• updatet to 11.1 Hotfix -> BSoD
• rollback to 10.12 -> BSoD
• removed ALL AMD files manually, installed 10.12 -> BSoD

• Temps are fine
• no sfc /scannow errors
• no chkdsk errors
• Prime, Furmark all fine
• regardless what driver I install -> BSoD
• I did no hw changes, no OC

Here are my BSoDs I receive:

• 0x0000010e
• 0x1000007e
• 0x0000007e
• 0x0000004e
• 0x0000003b
• dxgmms1.sys
• PFN_LIST_CORRUPT

They all refer to the GPU of course ...

From now on I receive a BSoD every time I try to play a game (especially BC2 and SC II) even if I completely remove the old driver and make a clean install.
Apparently the 11.1 damaged my system irreparable.

Any advice or info would be very much appreciated *Smile