BSOD's once a weekend with 0x00000050, for no apparent reason.

The crash dump you uploaded does not show any probable finite cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

If both of the tests comes free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions. Also upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

_______________________________________________________________________
BSOD ANALYSIS:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff60001080004, 0, fffff8000329090f, 7}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+43781 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff60001080004, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8000329090f, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034bb100
GetUlongFromAddress: unable to read from fffff800034bb1c0
 fffff60001080004 Nonpaged pool

FAULTING_IP: 
nt!MmAccessFault+aef
fffff800`0329090f 8b5004          mov     edx,dword ptr [rax+4]

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800bd7a7f0 -- (.trap 0xfffff8800bd7a7f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff60001080000 rbx=0000000000000000 rcx=0000000000004557
rdx=000fffffffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000329090f rsp=fffff8800bd7a980 rbp=fffff8800bd7aa00
 r8=0000000000000004  r9=00000000001df678 r10=fffffa80065d2f80
r11=fffff8800bd7aae0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MmAccessFault+0xaef:
fffff800`0329090f 8b5004          mov     edx,dword ptr [rax+4] ds:fffff600`01080004=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000330052b to fffff80003283c00

STACK_TEXT:  
fffff880`0bd7a688 fffff800`0330052b : 00000000`00000050 fffff600`01080004 00000000`00000000 fffff880`0bd7a7f0 : nt!KeBugCheckEx
fffff880`0bd7a690 fffff800`03281d2e : 00000000`00000000 fffff600`01080004 00000000`0047db00 80000001`df678867 : nt! ?? ::FNODOBFM::`string'+0x43781
fffff880`0bd7a7f0 fffff800`0329090f : fffffa80`059e3680 fffff880`0bd7aa00 ffffffff`a0050e57 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0bd7a980 fffff800`03281d2e : 00000000`00000001 00000000`02ba0000 00000000`060ea501 00000000`043cb648 : nt!MmAccessFault+0xaef
fffff880`0bd7aae0 00000000`5dd740aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0047db58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5dd740aa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+43781
fffff800`0330052b cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+43781

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+43781

BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+43781

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

Weekendgamer said:

Thanks for the suggestions! I wasn't sure it it was the drivers, either. I guessed it wouldn't be my RAM because I've run my system at 90% usage before and it didn't hit a bad bit.

TDSSKiller is error free

You have options to test. Test them all as suggested and be sure. No need to guess :)

Run it as you planned.

OK ... go for driver verifier.