CI.dll page_fault_in_nonpaged_area BSOD - Happens when I run a game

Here's a link to my dump file.

Basic System Specs:
OS: Windows 7 64 bit
CPU: Intel 2500k
GPU Nvidia 980ti
RAM: 8gb

Basically I get a BSOD if I try to run a few different programs (MSI Afterburner, a video game executable, etc) and I'm not sure what's causing it. I tried to download the windows SDK to view the dump file myself... but that gave me a BSOD too. I'm at a loss as to why it's happening since there's really no rhyme or reason on which program will trigger it. It also happens so rarely that I end up forgetting about it. I'm pretty peeved right now because it's happening with the new Tomb Raider game. Some games are fine, but others are not.

Anyway can someone take a look and help me? Like I said I can't view the dump file myself so I decided to upload it instead. Much appreciated everyone

Hello Theblueman123 and welcome to 7forums! :)

Please don't bump in the future, remember most of us here are not employed to help, we do it at our spare time!

Bumping your posts to get attention is not advised for the follwing reasons:

It is against forum rules to bump your posts early and/or excessively - Rule #2
Bumping your post removes your thread from the Unanswered Threads List, this will lessen the chance of someone looking in.
Posting multiple times in your own thread will give the appearance you're receiving help, again reducing the chance of someone looking in.

Most of the BSODs in your file were caused by Bug check 0x50 and it can occur after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

I would recommend that you follow this tutorial for MemTest86+:

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

Cheers, Boris :)