BSOD whilst playing any game ranging from L4D2 to LoL

hello DJundertaker25, welcome to Seven Forums. I will try to help you with this problem, if I can. First, I would like you to complete your system specs in a little more detail if you would. Sometimes we need to look up a particular part and need the Manufacturer and model number. I would also like to know your PSU and CPU cooler and case can sometimes help. The instructions I give others may help you do that.

Please fill out your System Specs

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. System Info - See Your System Specs

As far as your dump files, The latest is about a month old, which striles me as unusual. so please make sure your system is configured for Small Memory Dumps Dump Files - Configure Windows to Create on BSOD.

Almost all of the latest 6 or seven dump files were fairly consistent. Of the 7 I looked at, 5 of them blamed this:

Code:

e22w7x64
start             end                 module name
fffff880`03e56000 fffff880`03e80000   e22w7x64 T (no symbols)           
    Loaded symbol image file: e22w7x64.sys
    Image path: \SystemRoot\system32\DRIVERS\e22w7x64.sys
    Image name: e22w7x64.sys
    Timestamp:        Wed Dec 05 10:43:48 2012 (50BF79C4)
    CheckSum:         00035FA2
    ImageSize:        0002A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

That is your Killer e2200 PCI-E Gigabit Ethernet Controller which is most likely a part of your Motherboard drivers. Please go to the Motherboard Manufacturer's site and see if you can find an updated driver.

Also blamed was

Code:

atikmdag
start             end                 module name
fffff880`0f03f000 fffff880`0ff4f000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Thu Apr 17 21:13:16 2014 (53508A3C)
    CheckSum:         00EAEEE6
    ImageSize:        00F10000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Which of course your graphics card. perhaps updating to a newer driver could help. Please update the card like this.
I am going to give you some links that will help you get a good clean install and not have any drivers you don't need that will conflict with other drivers. Download a WHQL driver from https://www.sevenforums.com/graphic-c...ndows-7-a.html . Once you have them downloaded, uninstall you current driver from control panel. next clean up any left over drivers from following this tutorial Drivers - Clean Left over Files after Uninstalling and select only ATI Display Drivers. After you have done that and rebooted, install the new driver, only select custom install and install only what you have to. Very few people need most of what they include. You do not need the audio/HDMI drivers as you already have that in your Motherboard drivers. Unless there is some reason you need them, the only thing you really need is the Display Driver.

You also got on 1 dump file and Ox124 which is a generic hardware fault that is very general and gives no information of what it is. So, we will wait until you update the above drivers and see if that helps. In the mean time, if you are overclocking anything, please set it back to default levels. I am not opposed to overclocking, but an unstable system will never have a stable overclock. So, please set everything to default levels, at least until we can get you stable.

After you have completed the above please open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

We got the same thing with no info.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa800cdcd028, be000000, 800400}
Probably caused by : GenuineIntel
Followup: MachineOwner

Please tell me what causes the BSODs. Is there some activity you do or some application you run that causes them? Also, how often do they happen. Can you give me a timeline?

Ok, I realize what a pain it is, but I think we need to run memtest. I know you said you have eliminated it, but the tests are pretty fickle and ram is the one thing that will keep the debugger from getting accurate results.

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask

It could be the fact that you are running an Asus OEM_SLP version of Windows on an MSI Retail Motherboard in a Custom Build. An OEM_SLP Key is only Legal on the computer it was installed on when shipped from the Factory. The only way it can be Validated is by using a loader which alters System Files, which causes the OS to act in unexpected and unpredictable ways.

Counterfeit installations such as yours contain heavily modified code that causes the installation to behave it unexpected ways. Analyzing BSOD's and determining their causes on these sorts of installations is very unreliable. For this reason, many analysts won't attempt it.

My recommendation is to install a genuine Windows 7. This will minimize the problems you are experiencing, and make subsequent diagnosis of BSOD's far more reliable. Once you are running a Genuine Windows 7 installation, and are still experiencing BSOD's, we will be happy to help you solve them