BSOD playing Borderlands 2, multiple BSOD's

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff6fc1004a780, 0, fffff80004c9b7a1, 2}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiDispatchFault+d1 )

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

1: 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: fffff6fc1004a780, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80004c9b7a1, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80004eae100
GetUlongFromAddress: unable to read from fffff80004eae1c0
 fffff6fc1004a780 Nonpaged pool

FAULTING_IP: 
nt!MiDispatchFault+d1
fffff800`04c9b7a1 4b8b1c1c        mov     rbx,qword ptr [r12+r11]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88007f53820 -- (.trap 0xfffff88007f53820)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=f820094f02b00400 rbx=0000000000000000 rcx=00000000f820094f
rdx=00000000ffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80004c9b7a1 rsp=fffff88007f539b0 rbp=fffff683ff7491e8
 r8=fffff820094f02b0  r9=0000000000000000 r10=0000000fffffffff
r11=fffff68000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiDispatchFault+0xd1:
fffff800`04c9b7a1 4b8b1c1c        mov     rbx,qword ptr [r12+r11] ds:fffff680`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80004c258e0 to fffff80004c7efc0

STACK_TEXT:  
fffff880`07f536b8 fffff800`04c258e0 : 00000000`00000050 fffff6fc`1004a780 00000000`00000000 fffff880`07f53820 : nt!KeBugCheckEx
fffff880`07f536c0 fffff800`04c7d0ee : 00000000`00000000 fffff6fc`1004a780 fffff880`07f53700 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x437f6
fffff880`07f53820 fffff800`04c9b7a1 : 00000000`0031bcff 000007fe`e92b63d0 fffff683`ff7495b0 fffffa80`0d0e8c48 : nt!KiPageFault+0x16e
fffff880`07f539b0 fffff800`04c8b549 : 00000000`00000000 000007fe`e923dff3 fffff700`01080000 00000000`00000000 : nt!MiDispatchFault+0xd1
fffff880`07f53ac0 fffff800`04c7d0ee : 00000000`00000008 000007fe`e923dff3 00000000`ffffff01 00000000`00000000 : nt!MmAccessFault+0x359
fffff880`07f53c20 000007fe`e923dff3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`01d5c480 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`e923dff3


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiDispatchFault+d1
fffff800`04c9b7a1 4b8b1c1c        mov     rbx,qword ptr [r12+r11]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiDispatchFault+d1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiDispatchFault+d1

BUCKET_ID:  X64_0x50_nt!MiDispatchFault+d1

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

According to Carrona.org, STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

Let us check them one by one.

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.

Run SFC /SCANNOW Command - System File Checker

Which antivirus Do you use? Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

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.

There is a little Hint of NTFS corruption.

Code:

fffff880`07f53748  fffff880`01224020 Ntfs!NtfsInitializeIrpContext+0x60
fffff880`07f53798  fffff880`012affee Ntfs!NtfsCopyReadA+0x20e
fffff880`07f53a18  fffff880`01110541 fltmgr!FltpFastIoRead+0xe

Do some disc checks.

1. Update your SSD's Firmware (Skip it, if it is not a SSD)
2. Re-seat the sata and power.
   
3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
4. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Finally, you may search for any available update for your BIOS.

Code:

BIOS Version/Date    American Megatrends Inc. 0402, 5/16/2011

But if you are not sure how to do it, and what to do, ask us.

One more thing .... uninstall it.

Code:

Start Menu\Programs\Free Window Registry Repair

Such a program is not only unnecessary but also harmful. It may damage windows 7's file and registry system beyond repair.

Let us know the results.

My best suggestion for you is to use the free version of MBAM only, and for the real time protection use MSE. Ntfs.sys and fltmgr.sys may be failed by this programs filtering mechanism, too.

EDIT. Stop memtest.
Go to the Part 3: If You Have Errors:
Follow it. It will help you to determine which stick is corrupted. Otherwise, you may get an all new kit.

Make it sure that all the RAM sticks are of equal FSB. Otherwise, it will use the average RAM only, which will cause the system run slow.