All games Crashing "<application> Has encountered an error and needs to close"

That board has onboard video, can you remove the graphics card and plug your monitor into one of the onboard ports, make sure you have the graphics drivers for the onboard graphics, chipset, etc. installed and see if you still have the problem. If not, it's a card issue. If so, we'll move on to another step. Also, does that graphics card have a connector for a PCI power cable on it and if so do you have one plugged into it?

Ok, sounds good.

Ok, so reinstall your graphics card, it's probably not the problem. Pull whichever memory module isn't in the #1 slot and try it again. I know you're going to take a little bit of a performance hit with 4GB less memory but if one of the modules is the problem you can figure it out this way. If it still does it, swap it for the other module and try it again. Let me know.

Ok, so it's probably not a memory issue. Can you post the minidump? I should be in C:/Windows/Minidump.dmp

Also, don't forget to put your modules back in the correct locations for your dual channel to operate. Make sure they are installed in the two darker sockets as those are the A1 and B1 locations for running in dual channel mode.

I know you said your drivers are up to date, but just for a matter of covering the basics, please read try the following and see if it doesn't maybe resolve your issue.

I'd go into control panel and right click on your display adapter then select uninstall. Make sure to check the box that says "uninstall device driver" too. Then go into programs and features and uninstall any applications related to the card including the AMD catalyst control manager and the AMD Vision engine if they are there. Use the express feature when uninstall begins and uninstall everything. Prior to doing this though go to the Catalyst website and download the 14.4 driver package (Don't download the beta 14.6 or 14.7 package) so you already have it to install afterwards. Then reboot and reinstall the AMD 14.4 CCC but choose the custom install option and don't install the optional gaming enhancement at this time or the Quickstream option, if either of those are there or checked, uncheck them. Install, reboot and try it again. http://support.amd.com/en-us/download/desktop?os=Windows+7+-+64#amd-catalyst-packages

Is the SSD your boot drive? If so you should get all your information backed up asap in case and before it fails completely. If that is the drive you're using for applications and games then yes, it could definitely be a problem. Also, if it's not but you're using it for cache, scratch or disk image access it could also be the problem. Is your HDD just storage? Also, did you find the dump file?

Were you playing Battlefield 4 when this happened?

Analyzing the dumps isn't my strong suit. I'm trying to find somebody on the boards that can take a look. If there's anybody who's a decent debugger that can give this guy an idea of what's causing him to crash according to the dumps it would be appreciated.

Ok, so I contacted johnbl as he has shown a lot of knowledge in this area on threads I've seen before. I'm just trying to learn to analyze the dumps myself right now so hopefully he will have a chance to take a look at them for you and give us an idea of what's going on.

I'm guessing he's probably busy, it was worth a shot, but I did post a thread asking for some help with the debugging so we'll see if anybody has any feedback on the dump files. I'm tryin' bro, I'm tryin'. Did you get any further results on the drive testing?

For anybody who can help and doesn't have a google account to look at the dump files they can be downloaded from here:
www.puebloallpro.com/dumpfiles.zip

"Download HWInfo and run Sensors. Popst the results - usually 3 screenshots in TinyPic or similar. Just to see what his hardware is doing." -i7baby

Here's what Whocrashed reported on the dumps I analyzed.


On Thu 7/31/2014 4:23:47 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\073014-12526-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12903)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004815028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 7/30/2014 3:50:06 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\073014-13228-01.dmp
This was probably caused by the following module: igdkmd64.sys (igdkmd64+0x97CA7)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800FE97CA7, 0x0, 0x8)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: igdkmd64.sys .
Google query: igdkmd64.sys KMODE_EXCEPTION_NOT_HANDLED



On Mon 7/28/2014 8:20:01 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\072814-13634-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12903)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800786A028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 7/26/2014 5:20:14 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\072514-13806-01.dmp
This was probably caused by the following module: hal.dll (hal+0x126E0)
Bugcheck code: 0x9C (0x0, 0xFFFFF880009F6B70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

your bugcheck indicated problems generated directly from the CPU.
Most often due to overclocking, or overheating but can also be due to incorrect voltages and clocks applied to the CPU.

If they occur during a 3 D game I would suspect the graphics card is pulling too much power from your system.
That and in conjunction with the fact that your system seems to be running two copies of MSI afterburner software I would suspect that the graphics processor pulled too much power and caused your CPU voltages to drop and your CPU generated a error.

suggest:
turn off overclocking to your CPU (current speed =3517MHz )
remove MSI afterburner (do not overclock your GPU for now).
-You are running a very old version of windows 7 release to manufacturing: apply the service packs and updates
- after you apply the SP and updates reboot and apply the intel chipset updates directly from intel
- Also, current graphics drivers require the windows update fixes in order to run correctly (or they will bugcheck in the OS)

- update your ASMHU3 drivers(2011). these old drivers will cause lots of bugchecks (memory corruption)
your Intel(R) 82579V Gigabit Network Connection driver is also old Jul 20 09:37:53 2011 and has known issues
update them directly from intel https://downloadcenter.intel.com/default.aspx

------
memory dump file 072514-13806-01.dmp
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
System Uptime: 0 days 1:33:46.612
Debug session time: Fri Jul 25 22:20:14.332 2014 (UTC - 7:00)
072514-13806-01.dmp
BugCheck 9C, {0, fffff880009f6b70, 0, 0}

BIOS Release Date 11/09/2012
BIOS Version 3603
Manufacturer ASUSTeK Computer INC.
Product P8Z68-V PRO
Version Rev 1.xx
Socket Designation LGA1155
Processor Version Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
Processor Voltage 8ah - 1.0V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 3517MHz

memory:
bank 0 EMPTY
bank 1:
Device Locator ChannelA-DIMM1
Bank Locator BANK 1
Speed 1333MHz
Manufacturer 04CD
Part Number F3-12800CL9-4GBSR2
bank 3:
bank 4:
Bank Locator BANK 3
Speed 1333MHz
Manufacturer 04CD
Serial Number
Asset Tag Number
Part Number F3-12800CL9-4GBSR2

Were you able to complete the long tests on the SSD? Regardless, between failing the test and Windows running stable with no games crashing on a secondary HDD it's extremely probable that the crashes were related to the SSD although johnbl has indicated there may be some other issues.