SYSTEM_SERVICE_EXCEPTION BSOD after a few weeks of no BSODs

Another crash occurred today, but this time I didn't see a bluescreen show up. I checked BluescreenView though, and like the other recent crashes BluescreenView shows the cause as ntoskrnel.exe, which from what I've read shows up as a cause but isn't the likely culprit. When I check Event Viewer, a critical issue called Kernel Power with the Event ID of 41 also shows up. A few settings I've changed recently include enabling XMP so my memory timings match, because I have two different sticks of ram, updating my AMD graphics card drivers, and uninstalling manufacturer's software for my wireless adapter because it looked like there was the Windows generic version installed on my PC.

My friend says he has extra ram I can borrow. I'll try driver verifier again with that ram installed because driver verifier seemed to most consistently cause BSODs.

I didn't manage to swap out my RAM yet, but I got a memory management BSOD today.

I still haven't been able to swap out any ram, but I've been getting plenty of BSODS, and I personally analyzed the minidump file for the last one and found this, but I don't know if it means the RAM, motherboard, or CPU are at fault:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8036dea9bf0, The address that the exception occurred at
Arg3: fffff8898ee96d08, Exception Record Address
Arg4: fffff8898ee96550, Context Record Address

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


KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: H81M-S1

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: To be filled by O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: FH

BIOS_DATE: 08/10/2015

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: H81M-S1

BASEBOARD_VERSION: x.x

DUMP_TYPE: 2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8036dea9bf0

BUGCHECK_P3: fffff8898ee96d08

BUGCHECK_P4: fffff8898ee96550

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP:
nt!MiDemoteCombinedPte+40
fffff803`6dea9bf0 498378f001 cmp qword ptr [r8-10h],1

EXCEPTION_RECORD: fffff8898ee96d08 -- (.exr 0xfffff8898ee96d08)
ExceptionAddress: fffff8036dea9bf0 (nt!MiDemoteCombinedPte+0x0000000000000040)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff8898ee96550 -- (.cxr 0xfffff8898ee96550)
rax=ffff82c160b05000 rbx=0000000000000231 rcx=ffffd88d93e24580
rdx=ffff82812e21b1d8 rsi=ffff82812e21b1d8 rdi=ffff82812e21b1d8
rip=fffff8036dea9bf0 rsp=fffff8898ee96f40 rbp=ffffbd8000000000
r8=8000000000000000 r9=0000000000000000 r10=0000000fffffffff
r11=0000000000000000 r12=ffff82c160b057f8 r13=ffffbd8000000000
r14=8000000000000000 r15=ffffd88d93e24580
iopl=0 nv up ei ng nz na po cy
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010287
nt!MiDemoteCombinedPte+0x40:
fffff803`6dea9bf0 498378f001 cmp qword ptr [r8-10h],1 ds:002b:7fffffff`fffffff0=????????????????
Resetting default scope

CPU_COUNT: 4

CPU_MHZ: c79

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 22'00000000 (cache) 22'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: chrome.exe

CURRENT_IRQL: 2

FOLLOWUP_IP:
nt!MiDemoteCombinedPte+40
fffff803`6dea9bf0 498378f001 cmp qword ptr [r8-10h],1

BUGCHECK_STR: AV

READ_ADDRESS: Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
ffffffffffffffff

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

ANALYSIS_SESSION_HOST: DESKTOP-Q2RD7E8

ANALYSIS_SESSION_TIME: 07-17-2018 02:18:20.0194

ANALYSIS_VERSION: 10.0.17134.1 x86fre

LAST_CONTROL_TRANSFER: from fffff8036dff0a0c to fffff8036dea9bf0

STACK_TEXT:
fffff889`8ee96f40 fffff803`6dff0a0c : ffff1cb0`b3833bde fffff803`6df17fe1 00000000`8ee97460 fffff889`8ee97099 : nt!MiDemoteCombinedPte+0x40
fffff889`8ee97010 fffff803`6df17b79 : fffff889`8ee970f9 00000000`00000231 fffff889`8ee970f9 ffff82c1`60a80ff8 : nt!MiResetAccessBitPte+0x37c
fffff889`8ee97080 fffff803`6df17f82 : fffff889`8ee97530 ffff8281`2e21b1d8 fffff889`00000000 ffff82c1`00000000 : nt!MiWalkPageTablesRecursively+0x299
fffff889`8ee97160 fffff803`6df17f82 : fffff889`8ee97530 ffff82c1`409710d8 fffff889`00000001 ffffffff`00000000 : nt!MiWalkPageTablesRecursively+0x6a2
fffff889`8ee97240 fffff803`6df17f82 : fffff889`8ee97530 ffff82c1`60a04b88 fffff889`00000002 ffff82c1`00000000 : nt!MiWalkPageTablesRecursively+0x6a2
fffff889`8ee97320 fffff803`6df16497 : fffff889`8ee97530 ffff82c1`60b05020 00000000`00000003 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x6a2
fffff889`8ee97400 fffff803`6dff640b : fffff889`8ee97530 fffff803`00000001 fffff803`00000000 fffff889`00000000 : nt!MiWalkPageTables+0x1e7
fffff889`8ee974f0 fffff803`6df15685 : 00000000`00000000 ffffd88d`93e24580 ffffd88d`93e24580 ffffd88d`9332d640 : nt!MiCaptureAndResetWorkingSetAccessBits+0xe3
fffff889`8ee977e0 fffff803`6df13fa3 : 00000000`00000000 fffff889`8ee979b0 ffffd88d`8e890010 fffff803`00000000 : nt!MiTrimOrAgeWorkingSet+0x6f5
fffff889`8ee978b0 fffff803`6dea63b7 : fffff803`6e278000 00000000`ffffffff 00000000`00000098 ffffd88d`8e890010 : nt!MiProcessWorkingSets+0x233
fffff889`8ee97a60 fffff803`6e003881 : 00000000`00000002 00000000`00000002 00000000`ffffffff 00000000`00000001 : nt!MiWorkingSetManager+0x9f
fffff889`8ee97b20 fffff803`6df81cd7 : ffffd88d`8e988040 00000000`00000080 fffff803`6e0035d0 00000425`bd9bbfff : nt!KeBalanceSetManager+0x2b1
fffff889`8ee97c10 fffff803`6e03c8d6 : ffffac01`58425180 ffffd88d`8e988040 fffff803`6df81c90 f0000049`b3c00000 : nt!PspSystemThreadStartup+0x47
fffff889`8ee97c60 00000000`00000000 : fffff889`8ee98000 fffff889`8ee92000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC: bd4b2c54165eed9b20fb5e9e6220fe9b2f907bee

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 1144a3cb5446d056ab42a585878e74cd8102445f

THREAD_SHA1_HASH_MOD: 7f608ac2fbce9034a3386b1d51652e4911d30234

FAULT_INSTR_CODE: f0788349

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiDemoteCombinedPte+40

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 5b3f12f4

IMAGE_VERSION: 10.0.17134.165

STACK_COMMAND: .cxr 0xfffff8898ee96550 ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 40

FAILURE_BUCKET_ID: AV_nt!MiDemoteCombinedPte

BUCKET_ID: AV_nt!MiDemoteCombinedPte

PRIMARY_PROBLEM_CLASS: AV_nt!MiDemoteCombinedPte

TARGET_TIME: 2018-07-17T05:16:27.000Z

OSBUILD: 17134

OSSERVICEPACK: 165

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-07-06 02:57:56

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: 22fb

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!midemotecombinedpte

FAILURE_ID_HASH: {c577c73b-79a7-0c44-6c62-58e1d697b6d8}

Followup: MachineOwner

Would a bent motherboard pin be a possible reason for this? I accidentally bent some of the socket pins when I first assembled this computer, but I was able to bend them back to their original position.