BSOD while gaming, FAULT_PAGE_IN_NON_PAGED_AREA and x050 and more.

Hey guys, I keep getting BSOD about 3 to 5 times a day, mostly related to when I'm gaming, this usually happens when I'm playing League Of Legends or some other game like Sniper Elite V2, etc.

Editted to add that both Chrome, Skype and sometimes the AMD Catalyst Control Center will crash, although it doesn't BSOD right away, it is kind of like a signal that I will get one unless I restart.
System Specs:

Operating System
Windows 7 Home Premium 64-bit SP1
CPU
Intel Core i5 2500 @ 3.30GHz 55 °C
Sandy Bridge 32nm Technology
RAM
6.00GB Dual-Channel DDR3 @ 665MHz (9-9-9-24)
Motherboard
Dell Inc. 0Y2MRG (CPU 1) 47 °C
Graphics
T24B350 (1920x1080@60Hz)
3072MB ATI AMD Radeon HD 7900 Series (XFX Pine Group) 52 °C
Storage
465GB Western Digital WDC WD5000AAKX-753CA1 (SATA) 45 °C
Optical Drives

HL-DT-ST DVD+-RW GH70N

Audio
Sound Blaster X-Fi Xtreme Audio

Hope you guys can help me out!

I just updated the file with some more files.

Unfortunately the zip file doesn't contain all the necessary information to help you.

Please follow this, and don't interrupt the process until its complete:

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file created on your desktop, and upload it here in your next reply.

Unfortunately there aren't any .dmp files present to analyse.

Check C:\Windows\Minidump - are there any .dmp files present there?

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff6868e908180, 0, fffff800031bc3a6, 5}


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

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

Run a minimum of 8 passes, preferably overnight, or until errors occur using MemTest86+.

Use this tutorial to help you use MemTest86+:
RAM - Test with Memtest86+

Hi Fuzwipper.

Have you followed this advice by Golden? What is the result?
___________________________________

Code:

BugCheck 3B, {c0000005, fffff80002cc0b65, fffff8800626d7c0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )

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