So I have recently yet again encountered a black screen issue and am at wits end at this point trying to narrow it down. I used to have this issue when playing Star Citizen and narrowed that down to RAM issues which I ended up resolving by manually setting timings, voltage, and speed (my fault for using DOCP instead first) and staying on a bios that contains AGESA V2 PI 1.2.0.3 Patch C; However the issue has started to crop up again months later for some reason, specifically whenever I play Resident Evil 4 Remake or Hell Let Loose, sometimes Valheim as well. I'm sure there's more I can add to the list but I'm to frustrated to test any other games trying to resolve this issue. 

List of things tried so far:
-Driver update and rollback (With DDU obviously)
-Studio Drivers, Game Ready Drivers
-SFC, DISM, and Check Disk Scans
-Precision X1 closed and open
-Windows 10 Refresh
 
Specs are as follows:
CPU - AMD R9 3900XT (Stock settings)
RAM - G. Skill Trident Z F4-3600C16D-16GTZRC x2 (8gb x 4) (Slightly looser timings and lower speed for stability, closer to JEDEC Standard)
GPU - EVGA RTX 3070 FTW3 Ultra Gaming (Stock Settings)
MOBO - ASUS TUF GAMING X570-PRO (WI-FI)
PSU - Corsair RM850x (2021 Model I believe)
 
I'll post the WinDbg log below as well for any who are curious.
 

Loading Dump File [C:\Windows\Minidump\033023-12234-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`2f400000 PsLoadedModuleList = 0xfffff805`3002a310
Debug session time: Thu Mar 30 16:47:29.217 2023 (UTC - 7:00)
System Uptime: 0 days 1:36:10.869
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`2f7fa110 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff870c`b4bb0dc0=0000000000000050
9: 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: ffffcb0146040000, memory referenced.
Arg2: 0000000000000002, X64: bit 0 set if the fault was due to a not-present PTE.
	bit 1 is set if the fault was due to a write, clear if a read.
	bit 3 is set if the processor decided the fault was due to a corrupted PTE.
	bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
	- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
	bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff8054ed5b7a6, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Write

    Key  : Analysis.CPU.mSec
    Value: 4233

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 20472

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

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

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

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x50

    Key  : Bugcheck.Code.Register
    Value: 0x50

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  033023-12234-01.dmp

BUGCHECK_CODE:  50

BUGCHECK_P1: ffffcb0146040000

BUGCHECK_P2: 2

BUGCHECK_P3: fffff8054ed5b7a6

BUGCHECK_P4: 0

READ_ADDRESS: fffff805300fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 ffffcb0146040000 

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffff870cb4bb1060 -- (.trap 0xffff870cb4bb1060)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffcb014603f000 rbx=0000000000000000 rcx=0000000000000400
rdx=000000000000f3ff rsi=0000000000000000 rdi=0000000000000000
rip=fffff8054ed5b7a6 rsp=ffff870cb4bb11f0 rbp=0000000000000000
 r8=0000000000002614  r9=000000000000e012 r10=0000000000000000
r11=ffff870cb4bb1230 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nvlddmkm+0x7fb7a6:
fffff805`4ed5b7a6 893488          mov     dword ptr [rax+rcx*4],esi ds:ffffcb01`46040000=????????
Resetting default scope

STACK_TEXT:  
ffff870c`b4bb0db8 fffff805`2f87476f     : 00000000`00000050 ffffcb01`46040000 00000000`00000002 ffff870c`b4bb1060 : nt!KeBugCheckEx
ffff870c`b4bb0dc0 fffff805`2f6a4d70     : 00000000`00000005 00000000`00000002 ffff870c`b4bb10e0 00000000`00000000 : nt!MiSystemFault+0x1b19cf
ffff870c`b4bb0ec0 fffff805`2f809bd8     : fffff805`4097160d 00000000`00000001 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x400
ffff870c`b4bb1060 fffff805`4ed5b7a6     : ffff8f04`8d40b0b0 00000000`00000028 fffff805`4ed8cf29 fffff805`4ed50100 : nt!KiPageFault+0x358
ffff870c`b4bb11f0 ffff8f04`8d40b0b0     : 00000000`00000028 fffff805`4ed8cf29 fffff805`4ed50100 00000000`00000080 : nvlddmkm+0x7fb7a6
ffff870c`b4bb11f8 00000000`00000028     : fffff805`4ed8cf29 fffff805`4ed50100 00000000`00000080 00000000`0005a237 : 0xffff8f04`8d40b0b0
ffff870c`b4bb1200 fffff805`4ed8cf29     : fffff805`4ed50100 00000000`00000080 00000000`0005a237 00000000`00000003 : 0x28
ffff870c`b4bb1208 fffff805`4ed50100     : 00000000`00000080 00000000`0005a237 00000000`00000003 00000000`0000000c : nvlddmkm+0x82cf29
ffff870c`b4bb1210 00000000`00000080     : 00000000`0005a237 00000000`00000003 00000000`0000000c ffff8f04`8d40b003 : nvlddmkm+0x7f0100
ffff870c`b4bb1218 00000000`0005a237     : 00000000`00000003 00000000`0000000c ffff8f04`8d40b003 fffff805`4f1aacc2 : 0x80
ffff870c`b4bb1220 00000000`00000003     : 00000000`0000000c ffff8f04`8d40b003 fffff805`4f1aacc2 00000000`00000001 : 0x5a237
ffff870c`b4bb1228 00000000`0000000c     : ffff8f04`8d40b003 fffff805`4f1aacc2 00000000`00000001 ffff8f04`8d40b0b0 : 0x3
ffff870c`b4bb1230 ffff8f04`8d40b003     : fffff805`4f1aacc2 00000000`00000001 ffff8f04`8d40b0b0 00000000`00000003 : 0xc
ffff870c`b4bb1238 fffff805`4f1aacc2     : 00000000`00000001 ffff8f04`8d40b0b0 00000000`00000003 00000000`00000000 : 0xffff8f04`8d40b003
ffff870c`b4bb1240 00000000`00000001     : ffff8f04`8d40b0b0 00000000`00000003 00000000`00000000 00000000`00000000 : nvlddmkm+0xc4acc2
ffff870c`b4bb1248 ffff8f04`8d40b0b0     : 00000000`00000003 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
ffff870c`b4bb1250 00000000`00000003     : 00000000`00000000 00000000`00000000 00000000`00000000 00000001`00000000 : 0xffff8f04`8d40b0b0
ffff870c`b4bb1258 00000000`00000000     : 00000000`00000000 00000000`00000000 00000001`00000000 00000000`00000000 : 0x3


SYMBOL_NAME:  nvlddmkm+7fb7a6

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  7fb7a6

FAILURE_BUCKET_ID:  AV_W_(null)_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {838100fa-f28b-2ef7-d702-e31713cb338c}

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

Sajin
0x50 could be a few things…

#1 A degraded cpu. Increasing the main voltage of the cpu (vcore) could help fix the issue if it’s a degraded cpu. Usually increasing the main voltage (vcore) of a cpu could help fix the degradation for awhile until it gets worse, and then you’ll need more voltage again or rma.

#2 Cpu integrated memory controller (imc) unstable due to running higher ram frequencies than your cpu officially supports. Increasing the cpu imc voltage could resolve the issue if running higher ram frequencies than your cpu supports. I would recommend just running the correct ram frequencies for max stability which in your case is 3200mhz.

#3 Incorrectly set ram frequencies, timings & voltage/overclocked ram/faulty ram.

Since the system is also rebooting itself the psu or gpu could be the problem. Testing the gpu in another known good working system is the best way to know for certain that your gpu isn’t the issue. Other ways to test the gpu in your system would be to underclock the gpu to see if the issue will go away. Do the fans on your gpu spin up to max speed when the black screen occurs?

Sorry for the late reply, was going to be even later til I had more test results but that's going to be a minute (probably tomorrow) as I have a broken foot an mobility is a bit difficult right now 
 
#1 I'm going to run Y-Cruncher tonight for an overnight run to make sure it's not degraded or unstable. However I think that would've shown up either during the numerous temp and stability tests I did with Prime95, or my crash run ins with Star Citizen (as it is VERY CPU/RAM heavy and sensitive, at least before the new Gen 12 Renderer)
 
#2 I am using already 3200mhz but with the rated timings according to G. Skill (16-19-19-39), as well as 1.35v which I'll raise to see if it helps at all tonight, as well as dialing back timing more.
 
CPU-Z Mem:
 
 Y-Cruncher (2.5 minutes tests)

 
Like I said though I'll run more tests overnight tonight and post the results tomorrow sometime if I get anything. Thank you for your suggestions so far, just hope I don't have to full replace the RAM as it's on the QVL list for the mobo.

Sajin
No problem. So the fans on your gpu don’t spin up to max speed when the black screen occurs?

No they don't spin up but I've encountered something which has thrown me through a loop now. I got it to crash again around the 10 minute mark (No picture or audio) just in the main menu, and hit what I thought was power (it was sleep actually, I'm using a media keyboard from bed) after it crashed. Everything went to sleep, then I powered it back up thinking it had already turned off. Put it back to sleep (because I didn't know and thought it was power) and powered it back up. Tried to power it off via the case and it wouldn't respond, I would push power and it would still be on 5-10 minutes later. Had to hard power it off by holding down the button, and now for some reason Resident Evil 4 Remake didn't crash out in the main menu, and I sat there for about roughly 25 minutes. I then loaded in and still no crash after 10 minutes of running around an area where it previously crashed the system. At this point I'm kind of confused and this has thrown me through a loop as I was able to replicate it numerous times prior to today. Regardless I'm still going to run Y-cruncher overnight and Prime-95 in the morning to see if it still passes as "stable".
 
I'd try the GPU in another system but the only one I have is packed away. It's also worth noting ironically that said computer I packed away had blackscreen crashing issues that I couldn't narrow down for years until my new build. That card spit out WHEA errors in HWinfo64 where as this card doesn't so I'm inclined to believe it's not the card at the very least. If it is, maybe it's a bad solder job as this is a Non-LHR 3070 despite the fact it was advertised as a LHR card? I don't mine (don't know how to either, or care to) and it was factory new from AntOnline.

Glad to hear you figured it out. 👍