Seemingly Random BSOD

Welcome to the forum Hellsrage,

Free up the start-up, nothing except the antivirus is usually needed.

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup

Make scans with the following:

Kaspersky TDSSKiller

• Anti-rootkit utility TDSSKiller

ESET online scanner:

• Free Online Virus Scanner | ESET

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:

• Click on the
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker

Code:

Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Tue Jul  8 07:19:46.018 2014 (UTC + 6:00)
System Uptime: 0 days 10:51:00.533
BugCheck A, {18, 2, 0, fffff80001c6f54b}
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+12b )
BUGCHECK_STR:  0xA
PROCESS_NAME:  ts3client_win6
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Mon Jul  7 03:48:38.416 2014 (UTC + 6:00)
System Uptime: 0 days 1:53:10.932
BugCheck A, {3, 2, 1, fffff80001c86e65}
Probably caused by : ntkrnlmp.exe ( nt!SwapContext_PatchXSave+b5 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  AssassinsCreed
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Sun Jul  6 06:17:32.066 2014 (UTC + 6:00)
System Uptime: 0 days 8:45:10.566
BugCheck A, {4, 2, 1, fffff80001c83e65}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!SwapContext_PatchXSave+b5 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Sat Jul  5 06:18:32.114 2014 (UTC + 6:00)
System Uptime: 0 days 8:38:02.614
BugCheck 1000007E, {ffffffffc0000005, fffff88005929dbb, fffff88008db2228, fffff88008db1a80}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+c7dbb )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Check for updates on the driver(s) below:

xusb21.sys Fri Aug 14 04:10:17 2009 (4A848F49)
XBox USB wireless controller [br] BSOD issues in Win7 with 2009 driver (found in mid-2012)
Driver Reference Table - xusb21.sys

Rt64win7.sys Tue Sep 27 20:50:33 2011 (4E81E2B9)
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
Driver Reference Table - Rt64win7.sys

Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program: How to Clean Left Over Driver Files with Driver Sweeper

• Drivers - Clean Left over Files after Uninstalling

Remove the following software, they tend to cause BSOD's.

RTCore64.sys Mon Mar 11 11:32:06 2013 (513D6C56)
RivaTuner/EVGA Precision/MSI Afterburner (known BSOD issues w/Win7)
Driver Reference Table - RTCore64.sys

AODDriver2.sys Tue Feb 11 17:06:52 2014 (52FA044C)
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7[br][br]Part of AMD Fuel[br][br]Location: C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys
Driver Reference Table - AODDriver2.sys

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 Disk Check on your Hard Drive for file system errors and bad sectors on it:

• How to Run Disk Check in Windows 7

Upload a screenshot of your hard disk using Crystal Disk Info:

• CrystalDiskInfo - Software - Crystal Dew World
• Screenshots and Files - Upload and Post in Seven Forums

Make a hard drive test from the hard drive manufacturers website:

• Hard Drive Diagnostic Procedure

Test your Hard Drive with SeaTools:

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

Check for heating issues using Speccy or HWMonitor. Upload a screen shot with either of the tools:

• Speccy - System Information - Free Download
• HWMonitor CPUID - System & hardware benchmark, monitoring, reporting
• Screenshots and Files - Upload and Post in Seven Forums

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

Memtest should be done overnight.

Looks fine..thanks :)

Could you uninstall MSI afterburner and Riva Tuner.

Have you tested RAM?