Random BSODs with multiple different error messages

Hey lovely people,
have this problem for quite a while now and can't seem to pinpoint it:
My PC works fine for a day or two and then on the second or third day just crashes randomly, sometimes only once, sometimes multiple times after each other until its tuck in a loop of rebooting and crashing while rebooting. Been like this for over half a year now. Sometimes it crashes while playing games, other times just after starting the PC with no real program running. Turning of the Power of the PC at the Power adapter over night fixes it ussually for one or two days, but only temporatrily, then a "bad" day or two happen again.
I've tried updating and reinstalling all major Drivers, using only one plug for the Power of the PC, flashing the BIOS, googling the error messages, running it without Anti Virus, but nothing helped. I concluded that it is probably a Driver problem, but I have no idea which one or how, so I tried debugging myself using WinDBG and your forum tutorials, but that didn't lead me anywhere either unfortunately, so I'm counting on you guys to help me with this, 'cause building it was rather expensive and I hoped to have this one for a long time.

Info:
OS: Windows 10 x64 Bit, Version 1909 (Build 18363.1016)
CPU: AMD Ryzen 7 2700X
GPU: Gigabyte Geforcte GTX1060 6GB
Motherboard: MSI B450 Gaming Plus
RAM: G.Skill DIMM 32 GB DDR4-2133 Kit

Here is some of the BSOD messages and info from WInDBG of the last week, I collected using the WinDBG Tutorial of your forum:

31.8.2020

ffffec8e`42d0b788 fffff804`1a086fe5Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ccad5caddc3a3d35\nvlddmkm.sys, Win32 error 0n2
Page 505ccf not present in the dump file. Type ".hh dbgerr004" for details
Page 505ccf not present in the dump file. Type ".hh dbgerr004" for details
nvlddmkm+0x206fe5

01.09.2020

ffffc281`68fbc5b8 fffff803`3b3bdbd2Unable to load image \??\C:\Program Files\Norton Security\NortonData\22.20.5.39\Definitions\BASHDefs\20200825.001\BHDrvx64.sys, Win32 error 0n2
BHDrvx64+0x4dbd2

01.09.2020

ffffdf8e`e42dc1b8 fffff800`7ad48439Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvlddmkm.sys, Win32 error 0n2
Page 506538 not present in the dump file. Type ".hh dbgerr004" for details
Page 506538 not present in the dump file. Type ".hh dbgerr004" for details
nvlddmkm+0x208439

01.09.2020 17:29

SYMBOL_NAME: nt!SmKmStoreDeleteWhenEmpty+c4

IMAGE_NAME: hardware

ffff9283`54fd2688 fffff802`26db2997Unable to load image \SystemRoot\System32\drivers\rt640x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rt640x64.sys
rt640x64+0x82997

01.09.2020 18.15

SYMBOL_NAME: nt!KiFastFailDispatch+d0

MODULE_NAME: nt

ffffda8a`b41c9938 fffff805`41c98439Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvlddmkm.sys, Win32 error 0n2
Page 50c9a7 not present in the dump file. Type ".hh dbgerr004" for details
Page 50c9a7 not present in the dump file. Type ".hh dbgerr004" for details
nvlddmkm+0x208439

02.09.2020 17:05 SYSTEM_SERVICE_EXCEPTION (3b)

SYMBOL_NAME: nt!MiTerminateWsleCluster+d0

MODULE_NAME: nt

ffffa486`ce4f3dd0 fffff805`28fc7268Unable to load image \SystemRoot\System32\drivers\NGCx64\1614050.027\SRTSP64.SYS, Win32 error 0n2
SRTSP64+0x27268

ffffa486`ce4f3e28 fffff805`26a5cb2fUnable to load image \??\C:\WINDOWS\system32\Drivers\SYMEVENT64x86.SYS, Win32 error 0n2
SYMEVENT64x86+0xcb2f


04.09.2020 10:43 DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

FAULTING_SOURCE_LINE: minkernel\wdf\framework\shared\core\fxrequestapi.cpp

FAULTING_SOURCE_FILE: minkernel\wdf\framework\shared\core\fxrequestapi.cpp

FAULTING_SOURCE_LINE_NUMBER: 3508

FAULTING_SOURCE_CODE:
No source found for 'minkernel\wdf\framework\shared\inc\private\common\fxhandle.h'

SYMBOL_NAME: Wdf01000!imp_WdfRequestMarkCancelableEx+12

MODULE_NAME: hardware

IMAGE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

fffff805`1b8629f8 fffff805`27b08439Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvlddmkm.sys, Win32 error 0n2
Page 504d5c not present in the dump file. Type ".hh dbgerr004" for details
Page 504d5c not present in the dump file. Type ".hh dbgerr004" for details
nvlddmkm+0x208439

fffff805`1b864048 fffff805`243506b1Unable to load image \??\C:\Program Files\Norton Security\NortonData\22.20.5.39\Definitions\IPSDefs\20200903.001\IDSvia64.sys, Win32 error 0n2
IDSvia64+0xc06b1


Thanks in Advance for any help,
Rian

Update BIOS - Wsparcie dla B450 GAMING PLUS | Motherboard - The world leader in motherboard design | MSI Polska

MrPepka said:

Update BIOS - Wsparcie dla B450 GAMING PLUS | Motherboard - The world leader in motherboard design | MSI Polska

I flashed it and got another BSOD just after restarting, !thread analysis points to nvlddmkm.sys again. I will see though how the system stability developes over the next couple days. For clarifgication, I flashed the Bios last year, when I first build the PC and earlier this year, also after the BSODs kept occuring.

WinDBG !analyze -v:
CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffffd802cb851080, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------

Page 504a05 not present in the dump file. Type ".hh dbgerr004" for details

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3624

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-F4N9GRB

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 3830

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

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: ef

BUGCHECK_P1: ffffd802cb851080

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME: svchost.exe

CRITICAL_PROCESS: svchost.exe

ERROR_CODE: (NTSTATUS) 0xcf069080 - <Unable to get error code text>

CRITICAL_PROCESS_REPORTGUID: {6a708aad-19aa-401e-a16f-da52739f5e6f}

IMAGE_NAME: ntdll.dll

MODULE_NAME: ntdll

FAULTING_MODULE: 00007ffd42960000 ntdll

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

STACK_TEXT:
fffffe06`254c3938 fffff805`228cbea9 : 00000000`000000ef ffffd802`cb851080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffffe06`254c3940 fffff805`227cb82d : ffffd802`cb851080 fffff805`220d6c55 ffffd802`cb851080 fffff805`220d6cd0 : nt!PspCatchCriticalBreak+0x115
fffffe06`254c39e0 fffff805`2265ca50 : ffffd802`00000000 00000000`00000000 ffffd802`cb851080 ffffd802`cb851080 : nt!PspTerminateAllThreads+0x16d431
fffffe06`254c3a50 fffff805`2265c679 : ffffffff`ffffffff fffffe06`254c3b80 ffffd802`cf04d080 00000000`00000a01 : nt!PspTerminateProcess+0xe0
fffffe06`254c3a90 fffff805`221d3c18 : 0000022d`00000298 ffffd802`cf069080 ffffd802`cb851080 00007ffd`35e0cb78 : nt!NtTerminateProcess+0xa9
fffffe06`254c3b00 00007ffd`429fc5f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000034`b037ee58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!NtTerminateProcess+0x14


SYMBOL_NAME: ntdll!NtTerminateProcess+14

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 14

FAILURE_BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_cf069080_ntdll.dll!LdrpICallHandler_ntdll!NtTerminateProc ess

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {01b38096-c230-ba9c-88d5-c1d885cdf858}

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

- - - Updated - - -

After updating BIOS to newest Version errors still occured, PC won't boot without BSOD today anymore, will try again tomorrow and post new logs.

Can you get the system to boot into Safe Mode?

Boot into Safe Mode on Windows 10

philc43 said:

Can you get the system to boot into Safe Mode?

Boot into Safe Mode on Windows 10

Good day to everyone,
I could not get my PC to start into any mode on Friday, even during the "advanced settings and repairs" menu, when I wanted to boot into safe mode, it crashed. However, today after two days without electricity, it runs seemingly fine... so far. Attached is the current WinDBG analysis and the new V2 Log. If needed I can also upload dump files, however currently I only have Mini dumps, if that helps.

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff802229d10e7, The address that the exception occurred at
Arg3: ffff900797302038, Exception Record Address
Arg4: ffff900797301880, Context Record Address

Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 4030
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-F4N9GRB
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 4128
Key : Analysis.Memory.CommitPeak.Mb
Value: 80
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: 19h1_release
Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z
Key : WER.OS.Version
Value: 10.0.18362.1

ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff802229d10e7
BUGCHECK_P3: ffff900797302038
BUGCHECK_P4: ffff900797301880
EXCEPTION_RECORD: ffff900797302038 -- (.exr 0xffff900797302038)
ExceptionAddress: fffff802229d10e7 (luafv!LuafvPreWrite+0x0000000000000047)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000000ff
Attempt to read from address 00000000000000ff

CONTEXT: ffff900797301880 -- (.cxr 0xffff900797301880)
rax=0000000000007666 rbx=ffffac8dff422a88 rcx=ffffac8dfbdfdaff
rdx=ffff900797302328 rsi=00000000000000ff rdi=0000000000000001
rip=fffff802229d10e7 rsp=ffff900797302270 rbp=ffff900797302349
r8=ffff900797302308 r9=ffff900797302328 r10=0000fffff802229d
r11=ffffc1fb5b000000 r12=0000000010000004 r13=ffffac8dff3df010
r14=ffff900797302308 r15=ffffac8dff422a20
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206
luafv!LuafvPreWrite+0x47:
fffff802`229d10e7 663906 cmp word ptr [rsi],ax ds:002b:00000000`000000ff=????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
READ_ADDRESS: 00000000000000ff
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 00000000000000ff
EXCEPTION_STR: 0xc0000005

STACK_TEXT:
ffff9007`97302270 fffff802`156e4a5c : ffffac8d`ff422b28 ffffac8d`ff4229a0 ffffac8d`ff3df660 00000000`00000000 : luafv!LuafvPreWrite+0x47
ffff9007`973022a0 fffff802`156e45a0 : ffff9007`97302480 ffff9b0f`e3842000 ffffac8e`0066b804 00000000`00020000 : FLTMGR!FltpPerformPreCallbacks+0x2fc
ffff9007`973023b0 fffff802`156e4112 : 00000000`00000000 ffff9007`97302480 ffffac8e`0066b8f0 ffff9007`97302490 : FLTMGR!FltpPassThroughInternal+0x90
ffff9007`973023e0 fffff802`156e3efe : 00000001`00000000 fffff802`0000000f 00000000`00000000 00000000`00000000 : FLTMGR!FltpPassThrough+0x162
ffff9007`97302460 fffff802`11299ed9 : ffffac8e`0066b8f0 fffff802`11299f17 00000000`0000000c 00000000`00000004 : FLTMGR!FltpDispatch+0x9e
ffff9007`973024c0 fffff802`1132c1f3 : ffff9007`973026f0 ffffac8e`0066b8f0 ffffac8d`fbdfdab0 ffffac8d`f7a64d60 : nt!IofCallDriver+0x59
ffff9007`97302500 fffff802`1130a304 : 00000000`00000000 ffff9007`973025a0 ffffac8d`fbdfdab0 ffffac8d`fbdfdab0 : nt!IoSynchronousPageWriteEx+0x137
ffff9007`97302540 fffff802`1127b9c8 : 00000000`00000011 ffff9b0f`e3842050 00000000`00000000 ffffe200`0f25ec60 : nt!MiIssueSynchronousFlush+0x70
ffff9007`973025c0 fffff802`1121ef57 : ffff9007`97b72a90 ffffac8d`f73f76c8 00000000`00000000 00000000`00000000 : nt!MiFlushSectionInternal+0x868
ffff9007`97302890 fffff802`1121d39b : 00000000`00000000 ffffac8d`f3e0c140 00000000`00001000 00000000`00000000 : nt!MmFlushSection+0xcf
ffff9007`97302940 fffff802`1132ea39 : ffffac8d`f73f76c8 00000000`00000000 ffffac8e`00000001 ffff9007`97302ac8 : nt!CcFlushCachePriv+0x45b
ffff9007`97302a90 fffff802`11283965 : ffffac8d`f3d35300 00000000`00000000 7fffffff`ffffff00 ffff9007`97b72a90 : nt!CcWriteBehindInternal+0x209
ffff9007`97302b70 fffff802`1131e155 : ffffac8d`f3e0c140 00000000`00000080 ffffac8d`f3c85080 00000000`00000000 : nt!ExpWorkerThread+0x105
ffff9007`97302c10 fffff802`113c99c8 : fffff802`0f51f180 ffffac8d`f3e0c140 fffff802`1131e100 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff9007`97302c60 00000000`00000000 : ffff9007`97303000 ffff9007`972fd000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: luafv!LuafvPreWrite+47
MODULE_NAME: luafv
IMAGE_NAME: luafv.sys
STACK_COMMAND: .cxr 0xffff900797301880 ; kb
BUCKET_ID_FUNC_OFFSET: 47
FAILURE_BUCKET_ID: AV_luafv!LuafvPreWrite
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {b6548961-4647-5765-2aef-b8aa2ab0ba6c}
Followup: MachineOwner

Update:
So, last week my PC completely stopped working: Whenever I want to boot it, it turns to the "Automatic repair menu" and from that I can't do anything else. If I want to boot into safe mode, it also just boots into the "automatic repair menu" again. I have no idea what to do, but my guess now is that I have to fresh install windows again and then somehow test my hardware because it doesn't seem software related to me at least anymore? I could really use some expertise one this...

- - - Updated - - -

Update: Got a report "The system couldn't be loaded because a critical system driver is missing or causes errors. \windows\system32\drivers\evbda.sys

So, I clean installed Win 10 x64 from an external USB-Drive, while doing so I conducted the memory check that is offered in the installing menu and found out that apprently some memory sticks are faulty. I identified the two faulty ones, the other two were okay on the check, and ran my system with only the two okay ones (All 4 were newly bough "F4-2133C15Q-32GRR" from G.Skill and compatible with Motherboard and CPU). I clean installed Windows, installed current drivers and some programs and everything seemed to be fine until yesterday. Then the BSODs started happening again after two days of running fine. Yet, the only thing that I installed the day before was Adobe Acrobat Reader DC. No Windows updates, no drivers, nothing.

New V2 Log attached.

- - - Updated - - -

Ztruker said:

evbda.sys is part of Broadcom NetXtreme II 10 GigE and developed by Broadcom Corporation.

Can you boot to Safe Mode now? If so, do that then uninstall the Broadcom NetXtreme II from Device Manager. Reboot normally and see if the system will boot up. It should then discover the NIC, reload the driver and you should be okay.

I would try that, but I don't have this card in my system. I have the Realtek® 8111H Gigabit LAN network card as it is the standard for my msi b450 Gaming Plus Motherboard. I also couldn't find anything related to Broadcom on my device manager or drivers.

Your memory was purchased as a quad memory kit. That means all four sticks are guaranteed to work together as matched units. If you have identified 2 that are faulty you should be able to return all four and get a new matching set under warranty. The latest crash dumps are consistent with memory defects, the defects are in specific memory locations, sometimes they do not cause problems other times they do - that is why it tends to be random.

philc43 said:

Your memory was purchased as a quad memory kit. That means all four sticks are guaranteed to work together as matched units. If you have identified 2 that are faulty you should be able to return all four and get a new matching set under warranty. The latest crash dumps are consistent with memory defects, the defects are in specific memory locations, sometimes they do not cause problems other times they do - that is why it tends to be random.

I bought 4 new RAM sticks from Corsair this time, 32 Gb DDR4 again, I checked prehand that they are compatible with Mainboard and CPU (although the other ones were also) and put them in 3 days ago. Since then: No more Bluescreens. So apparently these G.Skill Memory sticks that I bought new at the time had some kind of defect, I sent them all back now and hopefully get a refund. Anyway, after more than a year of troubles my system finally works fine without crashing. Thanks guys for your help.