Random BSODs starting since jun 18 2013 0x0000000a

I recently built this computer on april 12 of this year and had absolutely no problems with it from then on, i started adding extra accessories almost each month after it, When i first built the computer it had the following components first: AS Rock LGA1155 Intel Z77 PROFESSIONAL-M - motherboard, Corsair Vengeance 8 GB ( 2 x 4 GB ) DDR3 1600 MHz - Ram, Windows 7 Home Premium SP1 64bit (OEM) System Builder DVD 1 Pack - OS, Intel Core i7-2700K Quad-Core Processor, WD Blue 1 TB Desktop Hard Drive: 3.5 Inch, 7200 RPM, evga 550ti graphics card, and an 850 watt corsair power supply. On April 25, I Upgraded to the EVGA nvidia 660ti graphics card., On May 10, I Installed a second EVGA nvidia 660ti graphics card., On May 24, I installed another set of Corsair Vengeance 8 GB ( 2 x 4 GB ) DDR3 1600 MHz to add a total of 16gb in total., I doubt it matters but on June 18 i got a new 24 inch monitor for my computer my old bein a 19 inch computer but strangely my issues popped up after i just installed that but i highly doubt its because of the monitor. Thats about it in all hardware changes, I hope you guys can help me out since these bsods are messing me up when im either just surfin the web or just watchin shows Also most of the bsods happen when i have multiple stuff going on at once whether it be music, firefox with 10 tabs, and minecraft all at once. I attached my dmp files too

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

You need to update Asmedia 106x SATA Controller, as it is old.

Code:

fffff880`00c76000 fffff880`00c85000   asahci64   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\asahci64.sys
    Image name: asahci64.sys
    Timestamp:        Wed Sep 21 15:12:57 2011 (4E79B1A1)
    CheckSum:         00010EE2
    ImageSize:        0000F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Get it from ASMEDIA drivers & firmwares .

Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know the results.

Please dont alter the original post. Supply the subsequent zips in subsequent posts. It close the way of comparison if needed. It affects the chronological recording of the issue, too.

Your crash dumps are not showing any finite probable cause.

Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If both the above comes clean, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.