Frequent BSOD Every 2-3 hours (usually while gaming)

Daemon Tools/Alcohol %

Code:

DAEMON Tools Lite	"c:\program files (x86)\daemon tools lite\dtlite.exe"

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although we have seen dtsoftbus01.sys blamed on several occasions). Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

As an alternative many people recommend the use of Total Mounter or Magic ISO

Security App

Code:

Start Menu\Programs\avast! Free Antivirus

Avast! can be a possible cause of BSOD's. Remove Avast! and replace with Microsoft Security Essentials to see if it provides more stability. Uninstallers (removal tools) for common antivirus software

Microsoft Security Essentials and Malwarebytes are recommended from a strict BSOD perspective. They do not cause blue screens on the system as other AV products do.

Microsoft Security Essentials for Windows
MalwareBytes Free

   Information

• Do not start the free trial of MalwareBytes, unselect that option when prompted.
  
  
• Update and make full scans with both separately.

Hard Drive/Storage
Post disk summary using CrystalDiskInfo software - CrystalDiskInfo

For how to upload a screenshot or file, read here

Make a Hard Drive test from the mfg website: Hard Drive Diagnostic Procedure

For errors on your Hard drive(s): Disk Check

System Temperature

Ensure that there are no heat issues, For monitoring heat of the system use Piriform - Speccy or Hardware Monitor

Start up
Keep less stuff at the start-up. Only anti-virus, this helps avoid driver conflicts and improves time to log in to windows.

Performing a Clean Startup
Startup Programs - Change

SFC /scannow

1. Click Start
2. In the search box, type Command Prompt
3. In the list that appears, right-click on cmd.exe and choose Run as administrator
4. In the command window that opens, type

Code:

sfc /scannow

5. Hit enter
System File Checker

Memtest86+
Run Memtest86+ for at least 8-10 passes. It may take up to 20 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.
How to test and diagnose RAM issues with Memtest86+

   Note

Pay close attention to part 3 of the tutorial in order to rule the faulty RAM stick out.

   Tip

Do this test overnight.

BSOD BUGCHECK SUMMARY

Code:

Debug session time: Sun Jul  7 18:20:43.725 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:10:49.083
Probably caused by : csrss.exe
BugCheck F4, {3, fffffa800d73d600, fffffa800d73d8e0, fffff8000318e350}
BugCheck Info: CRITICAL_OBJECT_TERMINATION (f4)
Bugcheck code 000000f4
Arguments: 
Arg1: 0000000000000003, Process
Arg2: fffffa800d73d600, Terminating object
Arg3: fffffa800d73d8e0, Process image file name
Arg4: fffff8000318e350, Explanatory message (ascii)
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_IOERR
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe
BiosVersion = 0705
BiosReleaseDate = 08/22/2011
SystemManufacturer = To be filled by O.E.M.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Jul  7 18:08:20.330 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:27:22.385
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::LockAllocationBackingStore+65 )
BugCheck 1000007E, {ffffffffc0000005, fffff88007c32ce5, fffff88013a655b8, fffff88013a64e10}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Bugcheck code 1000007E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88007c32ce5, The address that the exception occurred at
Arg3: fffff88013a655b8, Exception Record Address
Arg4: fffff88013a64e10, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_SEGMENT::LockAllocationBackingStore+65
BiosVersion = 0705
BiosReleaseDate = 08/22/2011
SystemManufacturer = To be filled by O.E.M.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Jul  7 17:39:25.915 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:01:03.803
*** WARNING: Unable to verify timestamp for aswSnx.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.SYS
Probably caused by : aswSnx.SYS ( aswSnx+26199 )
BugCheck 1A, {5002, fffff781c0000000, b9c6, 2000b9c7fffffffe}
BugCheck Info: MEMORY_MANAGEMENT (1a)
Bugcheck code 0000001A
Arguments: 
Arg1: 0000000000005002, The subtype of the bugcheck.
Arg2: fffff781c0000000
Arg3: 000000000000b9c6
Arg4: 2000b9c7fffffffe
BUGCHECK_STR:  0x1a_5002
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_5002_aswSnx+26199
BiosVersion = 0705
BiosReleaseDate = 08/22/2011
SystemManufacturer = To be filled by O.E.M.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

THanks for letting us know.
Be sure to post if you have further issues.