I need help analyzing .dmp files due to frequent BSODS

I built my first gaming rig in january 2013, and everything went well.

However about 2 days later i recieved my first BS0Ds, which was very dissapointing.

I neglected to fix the issues and now all these BSODS are driving me crazy.

I don't know how to analyze dmp files so any help would be much appreciated.

Besides the minidumps that windows collects i also have many errors & criticals in my event log but don't know how to resolve any. Any help with those will be appreciated. Thanks to all in advance.


For people who dont want zip files :
Text list of all dmp filese: https://dl.dropboxusercontent.com/u/58356634/dmp.txt

P.S.. My system is currently running on windows 8 but it was previously running on Win 7 and im getting the same issues which is why im posting in a win 7 forumn. Screenshot and dmp files attached.

hi ski3high


Lets start off with a memory test

RAM - Test with Memtest86+

Getting a lot of memory corruption along with these drivers

??\C:\Program Files (x86)\AMD\OverDrive\amd64\AODDriver2.sys
\??\C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys

Reinstall the AMD software.

BSOD date: Apr 10

Code:

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800939109a, The address that the exception occurred at
Arg3: fffff8800f8bf278, Exception Record Address
Arg4: fffff8800f8beab0, Context Record Address

caused by

Code:

SYMBOL_NAME:  atikmdag+f309a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50d225df

STACK_COMMAND:  .cxr 0xfffff8800f8beab0 ; kb

FAILURE_BUCKET_ID:  X64_AV_atikmdag+f309a

BUCKET_ID:  X64_AV_atikmdag+f309a

Followup: MachineOwner

Update the AMD driver. Just install the driver not the CCC application

Test each RAM on every slot. One RAM at a time. If you recently purchased the hardware you should have warranty on the memory and be able to send the bad one and they will ship you a new one.

Also run CHKDSK /F /R

Click on the button type CMD inside Search programs and files. Once CMD comes up under Programs(1) right click and choose Run as administrator . Once the User Access Control window comes up click on the Yes button . Command prompt should open up to this path C:\Windows\System32>_

Type in the command below inside the Command prompt

chkdsk /F /R

press <ENTER>

It will ask you " Do you want to schedule a scan on the next restart " Press the Y key and press <Enter> then restart the PC manually

Also run SFC /SCAN

Open up the command Prompt same way as above . Run the command below

SFC /SCANNOW

press <ENTER>

If you get any files that are corrupted upload the CBS.LOG file with your reply

If your ram errored out on one slot and passed a test in another ram ? You have a bad slot . That's a motherboard replacement .

Did you run SFC /scannow ?