BSOD Random (once a day) Hiccups

I've been getting random BSOD where my system hiccups when it's doing something, i.e., netflix or browsing the web, or playing various video games. The hiccups happen where the computer freezes on a distinct purring sound before restarting with a blue screen. Attached below is the dump file, thanks you guys.

System:

CPU - Xeon W3520
Ram - 6GB 1600 DDR3 Patriot memory
Motherboard - Asus P6T deluxe
Graphic card - GTX 560Ti

Thanks again!

Reduce items at start-up:

• How to Change, Add, or Remove Startup Programs in Windows 7

Perform a clean boot:

• How to Troubleshoot a Problem by Performing a Clean Startup in Windows 7 or Vista

dtsoftbus01.sys Fri Jan 13 19:45:46 2012 (4F10358A)
Daemon Tools driver [br] Possible BSOD issues in Win7
Driver Reference Table - dtsoftbus01.sys
Daemon Tools/Alchohol is known to cause Blue Screens. Please remove it:

• How to remove sptd.sys from system
• Registry and SPTD problems

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable!:-

ASACPI.sys Mon Mar 28 08:30:36 2005 (42476C4C)
Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities (Win8 versions available from Windows Update as an Optional Update - but check Asus first!)
Driver Reference Table - ASACPI.sys

UltraMonUtility.sys Fri Nov 14 07:10:30 2008 (491CD006)
UltraMon multi-monitor
Driver Reference Table - UltraMonUtility.sys

netr28x.sys Fri Mar 27 13:25:49 2009 (49CC7F7D)
Ralink RT2860 series Wireless LAN Card (you may have a different manufacturer)
Driver Reference Table - netr28x.sys

NvStreamKms.sys Thu May 22 22:43:14 2014 (537E2922)
nVidia Streaming Kernel service - may cause BSOD in Win8.1 systems (found in May 2014). Date/TimeStamp: Tue Apr 29 20:59:44 2014 (53604B00) MAY NOT BE A PROBLEM, this is a tenative posting
Driver Reference Table - NvStreamKms.sys

To perform a clean install of a driver, follow this tutorial:

• How to Clean Left Over Driver Files with Driver Sweeper

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows you to remove leftover registry:-

• Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• How to Repair Windows 7 System Files with System File Checker

Post a screenshot of your Hard Drive(s) using Crystal Disk Info software:

• CrystalDiskInfo - Software - Crystal Dew World

Run a Hard Drive test:

• How to Use SeaTools for DOS and Windows Disk Check Utility

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• How to Run Disk Check in Windows 7

Check for heating issues using Speccy or HWmonitor

Upload a screen shot:

• Screenshots and Files - Upload and Post in Seven Forums

Code:

Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Debug session time: Thu Jun 26 06:37:59.232 2014 (UTC + 6:00)
System Uptime: 0 days 12:55:15.200
BugCheck 50, {fffffaa2d328481b, 0, fffff800032c9bef, 5}
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+425 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Debug session time: Thu Jun 12 08:04:37.865 2014 (UTC + 6:00)
System Uptime: 0 days 7:27:57.722
BugCheck 1A, {41284, 7691001, 12774, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Debug session time: Sat Jun  7 00:08:52.754 2014 (UTC + 6:00)
System Uptime: 1 days 0:18:40.722
BugCheck 4E, {99, 90393, 1, 160a13}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  Diablo III.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Debug session time: Tue Jun  3 10:35:22.847 2014 (UTC + 6:00)
System Uptime: 6 days 11:05:07.815
BugCheck 1A, {41284, 11f70001, 3374, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.