Well your latest .dmp file indicates memory corruption which is generally caused by failing RAM.
Can you please run memtest86 for at least 8 passes to scan for errors.
Follow these instructions on how to run it.
RAM - Test with Memtest86+
If you have more than one RAM stick please move the RAM around the DIMM slots in the motherboard to determine whether it is a bad slot or bad RAM
.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff6fffe7e7e78, 0, fffff8000309a401, 2}
Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiDispatchFault+d1 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff6fffe7e7e78, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8000309a401, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
You also have graphics driver issues. Can you please update your ATI drivers to the latest version. Please remove the current ones via the control panel first.
follow these instructions on how to install AMD drivers.
How-To Install AMD Catalyst? Drivers For A Windows® Based System
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff8800f07ad80, fffff880078f2610, 0}
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+ed80 )
Code:
fffff880`0f06c000 fffff880`0fd5c000 atikmdag T (no symbols)
Loaded symbol image file: atikmdag.sys
Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
Image name: atikmdag.sys
Timestamp: Fri Dec 06 21:19:43 2013 (52A23F6F)
CheckSum: 00CA856E
ImageSize: 00CF0000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
You also appear to have HDD issues, can you please run a disk check to scan for bad sectors.
Please follow these instructions on how to run a disk check.
Disk Check
Can you then run Seatools for windows to test for a failing HDD.
Follow these instructions.
SeaTools for DOS and Windows - How to Use
EDIT: Do not run these two disk tests if you have an SSD. Let me know the results of the previous tests before doing these 2. I need to double check these tests are suitable for SSDs