Lots of BSOD problems lately

Hello Johnny006, welcome to Seven Forums. You have quite a few dump files. I looked through most of them. Almost every error was a different big check and most were listed as different causes. Most of the time if you get those type of results, the problem lies in your memory or system files have been tampered with or corrupted. What I found the closer to the first one is what could be the real problem

Code:

BugCheck D1, {ffffffffc00000bb, 2, 1, fffff88007bbe0e6}
Probably caused by : hardware ( intelppm!ValidatePStateCapability+16 )
Followup: MachineOwner

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 4E, {2, 97f4, 21dfff, 1}
*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+8d )

Code:

BugCheck 3B, {c0000005, fffff80002ea97e0, fffff8800cb87850, 0}
Probably caused by : memory_corruption ( nt!MiAllocatePagedPoolPages+14 )
Followup: MachineOwner

Code:

 atikmpag
start             end                 module name
fffff880`07915000 fffff880`079b8000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Thu Apr 17 20:07:07 2014 (53507ABB)
    CheckSum:         000A6939
    ImageSize:        000A3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please make sure your Firmware on your SSD is up to date and all Motherboard drivers are updated from your Motherboards Web Site.

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.

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

Just in case you would like to see some of the other errors I found I will post them, but I think these may be the victims of the errors I posted above and not the cause.

Code:

 Loaded symbol image file: dump_iaStorA.sys
 Image path: \SystemRoot\System32\Drivers\dump_iaStorA.sys
 
Image name: dump_iaStorA.sys
 
Timestamp:        Fri May 02 18:06:56 2014 (53642510)

CheckSum:         000B0574
ImageSize:        002C9000
Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
 
 
 
 
 
 
 
HIDCLASS
 
start             end                 module name

fffff880`08c12000 fffff880`08c2b000   HIDCLASS (pdb symbols)          c:\symcache\hidclass.pdb\908D3A09383140B98D64BBD8D1B041711\hidclass.pdb
Loaded symbol image file: HIDCLASS.SYS
Mapped memory image file: c:\symcache\HIDCLASS.SYS\51D3A2F119000\HIDCLASS.SYS
Image path: \SystemRoot\system32\DRIVERS\HIDCLASS.SYS
Image name: HIDCLASS.SYS
Timestamp:        Tue Jul 02 23:05:05 2013 (51D3A2F1)
CheckSum:         00016FD9
ImageSize:        00019000
File version:     6.1.7601.18199
Product version:  6.1.7601.18199
File flags:       0 (Mask 3F)
File OS:          40004 NT Win32
File type:        2.0 Dll
File date:        00000000.00000000
Translations:     0409.04b0
CompanyName:      Microsoft Corporation
ProductName:      Microsoft® Windows® Operating System
InternalName:     hidclass.sys
OriginalFilename: hidclass.sys
ProductVersion:   6.1.7601.18199
FileVersion:      6.1.7601.18199 (win7sp1_gdr.130702-1534)
FileDescription:  Hid Class Library
LegalCopyright:   © Microsoft Corporation. All rights reserved.
 
 
 
 
 
 
 
 
CLASSPNP
 
start             end                 module name

fffff880`01d6d000 fffff880`01d9d000   CLASSPNP   (pdb symbols)          c:\symcache\classpnp.pdb\09E4EA6804D54FD3A6D8DAD298C55FCD2\classpnp.pdb
Loaded symbol image file: CLASSPNP.SYS
Mapped memory image file: c:\symcache\CLASSPNP.SYS\4CE7929B30000\CLASSPNP.SYS
Image path: \SystemRoot\system32\DRIVERS\CLASSPNP.SYS
Image name: CLASSPNP.SYS
Timestamp:        Sat Nov 20 03:19:23 2010 (4CE7929B)
CheckSum:         000318BE
ImageSize:        00030000
File version:     6.1.7601.17514
Product version:  6.1.7601.17514
File flags:       0 (Mask 3F)
File OS:          40004 NT Win32
File type:        3.7 Driver
File date:        00000000.00000000
Translations:     0000.04b0
CompanyName:      Microsoft Corporation
ProductName:      Microsoft® Windows® Operating System
InternalName:     Classpnp.sys
OriginalFilename: Classpnp.sys
ProductVersion:   6.1.7601.17514
FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
FileDescription:  SCSI Class System Dll
LegalCopyright:   © Microsoft Corporation. All rights reserved.

No, you don't need to watch it. If you happen to see an error, stop it. It won't hurt to keep running it, but after an error it isn't necessary. Even 1 error is a fail. But, no need to watch it.

If you are overclocking anything, set everything back to default levels. check your hard drives for errors. Western Digital's diagnostic test is Data Lifeguard for DOS (WD Support / Downloads / SATA & SAS / WD Black) they have 2 tests, one for DOS which you boot into the CD or USB drive you create or one that installs. The one for dos will give you a more thorough test as the hard drive is not in use, if you have trouble with that use the Data Lifeguard for Windows. You need to run the short and the long test on your Western Digital drive. Does the Kingston SSD have a tool box that will tell you the drive health and condition?
Also, if you don't already have it, please download and install CPUz ( CPU-Z CPUID - System & hardware benchmark, monitoring, reporting ) and install it. Post screenshots of the CPU, Mainboard, Memory and SPD tabs. On the SPD tabs in the upper left you can select each Dimm Slot. I only need the Dimm Slots that are populated with Ram. This will show you how to post screenshots here on Seven Forums.
Screenshots and Files - Upload and Post in Seven Forums

I need you to also monitor your CPU and GPU temps. If you don't already have programs to do that I can give you some suggestions.