Hi KimK & Welcome to the forums ^_^,
I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-
So an attempt was made to access an address which is invalid or out of reach.
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arg1: 0000000000000049, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff802f1337230, address which referenced memory
So, according to this, the MiIdentifyPfn tried to lock the address in RED. Let's check the address for it's validity -
1: kd> .trap 0xffffd00023aaafe0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0a00000000000020 rbx=0000000000000000 rcx=0200000000000000
rdx=fffff802f13371e2 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802f1337230 rsp=ffffd00023aab170 rbp=0000000000000000
r8=00000000000d8e83 r9=0220000000136eee r10=8400ca0205420000
r11=0000000000000042 r12=0000000000000000 r13=0000000000000000
iopl=0 nv up ei pl zr na po nc
fffff802`f1337230 f0410fba6f481f lock bts dword ptr [r15+48h],1Fh ds:00000000`00000048=????????
So, as we can see that the address is not valid at all.
1: kd> !pte 00000000`00000048
PXE at FFFFF6FB7DBED000 PPE at FFFFF6FB7DA00000 PDE at FFFFF6FB40000000 PTE at FFFFF68000000000
contains 034000011A418867 contains 0000000000000000
GetUlongFromAddress: unable to read from fffff802f15df104
pfn 11a418 ---DA--UWEV not valid
I would suggest you to run Memtest using this **GUIDE** for no less than 8 passes and report back the result of it. Furthermore, till the time we are troubleshooting, kindly remove the Daemon Tools. Also disconnect any Razer Devices till the time we are troubleshooting.
Also, remove your Avast and replace it with MSE till the time we are troubleshooting. Use this **TOOL** to remove Avast completely.
Let me know how it goes ^_^