Windows 10: Does anyone know what caused this bsod and how to fix it?

I've been getting a lot of bsod's lately. Mainly from driver "ntoskrnl.exe" I've checked from Blue screen view

I've done !analyze command for the latest one:

For analysis of this file, run !analyze -v

3: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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



PAGE_FAULT_IN_NONPAGED_AREA 50

Invalid system memory was referenced. This cannot be protected by try-except.

Typically the address is just plain bad or it is pointing at freed memory.

Arguments:

Arg1: fffff80600000000, memory referenced.

Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.

Arg3: fffff80676340e54, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 0000000000000002, reserved



Debugging Details:

------------------





KEY_VALUES_STRING: 1



Key : Analysis.CPU.Sec

Value: 2



Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on KALOYANPC



Key : Analysis.DebugData

Value: CreateObject



Key : Analysis.DebugModel

Value: CreateObject



Key : Analysis.Elapsed.Sec

Value: 2



Key : Analysis.Memory.CommitPeak.Mb

Value: 75



Key : Analysis.System

Value: CreateObject





BUGCHECK_CODE: 50



BUGCHECK_P1: fffff80600000000



BUGCHECK_P2: 2



BUGCHECK_P3: fffff80676340e54



BUGCHECK_P4: 2



READ_ADDRESS: fffff80600000000



MM_INTERNAL_CODE: 2



BLACKBOXBSD: 1 !blackboxbsd





BLACKBOXNTFS: 1 !blackboxntfs





BLACKBOXPNP: 1 !blackboxpnp





BLACKBOXWINLOGON: 1



PROCESS_NAME: wallpaper32.exe



TRAP_FRAME: ffffa606af124fa0 -- .trap 0xffffa606af124fa0

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=ffffbc887fab0080

rdx=ffffbc88793f5db8 rsi=0000000000000000 rdi=0000000000000000

rip=fffff80676340e54 rsp=ffffa606af125130 rbp=ffffa606af1252a0

r8=ffffa606af125180 r9=0000000000000014 r10=fffff80676340d40

r11=fffff806ad2c0000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

nt!ExTryAcquirePushLockExclusiveEx+0x114:

fffff806`76340e54 f0480fba2e00 lock bts qword ptr [rsi],0 ds:00000000`00000000=????????????????

Resetting default scope



STACK_TEXT:

ffffa606`af124cf8 fffff806`7641ebbb : 00000000`00000050 fffff806`00000000 00000000`00000002 ffffa606`af124fa0 : nt!KeBugCheckEx

ffffa606`af124d00 fffff806`7620c960 : ffffbc88`856d4588 00000000`00000002 ffffa606`af125020 00000000`00000000 : nt!MiSystemFault+0x1f43ab

ffffa606`af124e00 fffff806`76403c5e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x400

ffffa606`af124fa0 fffff806`76340e54 : ffffbc88`7fab0080 ffffbc88`793f5db8 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e

ffffa606`af125130 fffff806`ad33d5fc : ffffbc88`793f5db8 ffffbc88`00000001 00000000`00000000 00000000`00000000 : nt!ExTryAcquirePushLockExclusiveEx+0x114

ffffa606`af125170 fffff806`ad2c7b66 : ffffbc88`77339000 00000000`0009e462 00000000`00000000 ffffa606`af125290 : dxgmms2!VIDMM_DEVICE::EnsureSchedulable+0x5c

ffffa606`af1251a0 fffff806`a608acf1 : 00000000`00000000 ffffa606`af1254f8 00000000`00000014 ffffa606`af125558 : dxgmms2!VidSchSignalSyncObjectsFromGpu+0x6c6

ffffa606`af1253e0 fffff806`a60d86fe : 00000000`073de710 00000000`00000001 ffffffff`ffffffff ffffbc88`772e9000 : dxgkrnl!SignalSynchronizationObjectInternal+0xcf1

ffffa606`af125810 fffff806`a6065ace : ffff958e`9aebadf0 ffffbc88`7fab0080 00007ffe`0c1b7560 00000000`00000020 : dxgkrnl!DxgkSignalSynchronizationObjectInternal+0x22e

ffffa606`af125ad0 fffff806`764074b8 : ffffbc88`7fab0080 ffffbc88`7fab0080 00007ffe`0c1b9170 00000000`00000020 : dxgkrnl!DxgkSignalSynchronizationObject+0xe

ffffa606`af125b00 00007ffe`0c1c4974 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28

00000000`073de558 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`0c1c4974





SYMBOL_NAME: dxgmms2!VIDMM_DEVICE::EnsureSchedulable+5c



MODULE_NAME: dxgmms2



IMAGE_NAME: dxgmms2.sys



IMAGE_VERSION: 10.0.19041.789



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: 5c



FAILURE_BUCKET_ID: AV_INVALID_dxgmms2!VIDMM_DEVICE::EnsureSchedulable



OS_VERSION: 10.0.19041.1



BUILDLAB_STR: vb_release



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {bea646d8-5ee6-e736-4c3c-1104f142a141}



Followup: MachineOwner

---------



.dmp file link:

https://gofile.io/d/VBwnTB

:)

 

BSOD issue after fixing another BSOD error

Hi Williams,

There are several reasons why BSOD occur, which has different resolution. To check for any corruption or the integrity of your computer's Windows, we suggest that you perform a
Check Disk by following these steps:

• Type cmd in the search bar.
• Right-click on the Command Prompt, then Run as administrator.
  
• Type chkdsk x: /r, the /r command will fix errors found on the disk.

Let us know if you need further assistance.

 

BSOD Hardware Caused???

they do weird things like that, which all seem like something else is failing.
One of the worst things to diagnose, they seem to only quit when they want to.

Memtest is a good next step, if you rule out RAM and Power Supply make sure you disconnect all unnecessary peripherals and try to start the system with as little hardware as possible, if it works then, you can narrow down the culprit by trial and error.

the follow was taken from some website:

It's very difficult to determine if a failure is caused by the CPU because many other components can cause the same symptom when they fail.

1. System fails to boot
2. System re-boots intermittently
3. General Protection Fault
4. Illegal Operation
5. Stop Error, or BSoD (Blue Screen OfDeath)

Actually, CPUs rarely fail, and about the only way to determine if the CPU is causing the failure is to swap it out with a known working CPU of the same type and speed. Since this is difficult, the best bet is to first rule out every other possibility.

Before suspecting the CPU, rule out all the possibilities listed below.

1. The Operating System
2. A peripheral port device
3. A bad memory module
4. The hard disk drive
5. The power supply
6. The motherboard

If you have ruled out out all the other possibilities, investigate the items listed below.

1. Overheating
2. A short circuit
3. ESD

 

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.