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.
http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html
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 http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html.
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: [COLOR=red]Wed Dec 05 10:43:48 2012[/COLOR] (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\[COLOR=red]atikmdag.sys
[/COLOR] 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
http://www.sevenforums.com/graphic-cards/329659-latest-amd-catalyst-video-driver-windows-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
http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html 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.
