BSOD while running SF Diagnostic tool

Search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. Zip them and upload those.

Also upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

Well, Have a look at these, one by one.

COMODO Firewall Pro Sandbox Driver is failing here, and causing the BSOD.

Code:

fffff880`0a185228  fffff880`050edbabUnable to load image cmdguard.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cmdguard.sys
*** ERROR: Module load completed but symbols could not be loaded for cmdguard.sys
 cmdguard+0x1abab

Description here: Driver Reference Table - cmdguard.sys

Uninstall Comodo. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Also, it is saying that the Synaptic Touch Pad Driver is also failing, and here is the proof.

Code:

fffff880`091d9698  fffff880`04d8c73bUnable to load image SynTP.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SynTP.sys
*** ERROR: Module load completed but symbols could not be loaded for SynTP.sys
 SynTP+0x1e73b

It is a rare event. The Touchpad driver usually dont fail. But here as the antivirus failed to work, there is a fair possibility that the touchpad driver got infected. So scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

When done, update the touchpad driver from Drivers | Synaptics


The display driver is also failing here.

Code:

fffff880`091d94b8  fffff880`04d1e38aUnable to load image atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
 atikmpag+0x538a

And it is somehow old.

Code:

fffff880`04d19000 fffff880`04d6e000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Thu Apr 05 16:43:32 2012 (4F7D7E5C)
    CheckSum:         000531C1
    ImageSize:        00055000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update your ATI/AMD display driver.
You can get it from the link in our forum, Latest AMD Catalyst Video Driver for Windows 7, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.


During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.

A lot of unnecessary startup entries are there. Free up the startup.

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.

And finally, there is some evidence of Memory Corruption. And a corrupted RAM may cause any sort of problem, including all those in the current analysis.

Code:

STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
22 errors : !nt (fffff80001ed8441-fffff80001ed84f9)
fffff80001ed8440  03 *00  85  3d  80  ef  22  00  0f *00  39  a3  f8  ff  f3  90 ...=.."...9.....
fffff80001ed8450  8b *00  84  c0  78  ea  f0  0f  ba *00  07  72  e3  4c  8d  05 ....x......r.L..
fffff80001ed8460  9c *70  f8  ff  e9  f5  fe  ff  ff *06  90  90  90  90  90  90 .p..............
fffff80001ed8470  48 *00  5c  24  08  48  89  6c  24 *00  48  89  74  24  18  57 H.\$.H.l$.H.t$.W
fffff80001ed8480  41 *00  41  55  41  56  41  57  48 *8b  ec  d0  00  00  00  65 A.AUAVAWH......e
fffff80001ed8490  48  8b  34  25  20  00  00  00  80 *a3  26  ec  22  00  00  45 H.4% .....&."..E
fffff80001ed84a0  0f *48  e0  4c  8b  e9  8b  fa  0f *1c  a8  2f  fd  ff  48  8b .H.L......./..H.
fffff80001ed84b0  cf  48  b8  14  00  00  00  80  f7 *00  ff  48  8b  00  48  03 .H.........H..H.
fffff80001ed84c0  c8 *89  8b  c1  48  c1  e8  20  a3 *10  00  00  00  80  f7  ff ....H.. ........
fffff80001ed84d0  ff *0b  8b  c1  48  a3  14  00  00 *90  80  f7  ff  ff  48  b8 ....H.........H.
fffff80001ed84e0  08 *03  00  00  80  f7  ff  ff  48 *2b  08  48  03  cf  8b  fa ........H+.H....
fffff80001ed84f0  48 *fd  c1  48  c1  e8  20  f7  df *84  10  00  00  00  80  f7 H..H.. .........

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

This may be done by the failing antivirus, or by a physical RAM issue. Dont be uncertain. 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.


Stress test the CPU. It is also needed.
Hardware - Stress Test With Prime95

Let us know the results.

__________________________________________________
Crash Dump Analysis:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {55, d, 1, fffff80001ed8480}

Probably caused by : memory_corruption

Followup: memory_corruption
----------------------------------------------------------------------------------------------------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff881ede03408, 0, fffff80001faa25f, 5}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
-----------------------------------------------------------------------------------------------------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, 0, 8, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+487ed )

Followup: MachineOwner
---------

It is crashed by Acronis Try&Decide and Restore Points Volume Filter Driver.

Code:

fffff880`0ace6168  fffff880`01d3b992Unable to load image tdrpman.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tdrpman.sys
*** ERROR: Module load completed but symbols could not be loaded for tdrpman.sys
 tdrpman+0xba992

Sorry to say, but in such a situation (experienced the same earlier too, many a times) the only workable solution is to abandon Acronis, despite of its greatness and wide usefulness. It is causing some storage access block, and generates a lot of ntfs.sys errors. See some examples:

Code:

fffff880`0ace57a8  fffff880`012bcebd Ntfs!TxfAccessCheck+0x32d
fffff880`0ace5898  fffff880`012bcebd Ntfs!TxfAccessCheck+0x32d
fffff880`0ace5918  fffff880`012b9006 Ntfs!NtfsAccessCheck+0xf85
fffff880`0ace5a08  fffff880`012b9006 Ntfs!NtfsAccessCheck+0xf85
fffff880`0ace5b68  fffff880`012b75f5 Ntfs!NtfsOpenAttribute+0x525

Your Qualcomm Atheros AR9485WB-EG Wireless Network Adapter's driver is also failing.

Code:

fffff880`0ace61d8  fffff880`066a9a73Unable to load image athrx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
 athrx+0x25ca73

Update it from ATHEROS Wireless drivers for Windows

The display driver is also failing here. May be it is my fault that I haven't told you to not install a beta.

Code:

fffff880`0ace74e8  fffff880`0531aaf7Unable to load image atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0x108af7
-----------------------------------------------------------------------------------------------------
fffff880`050f1000 fffff880`05183000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Tue Mar 19 06:59:26 2013 (5147BF76) => BETA
    CheckSum:         0008D4B1
    ImageSize:        00092000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Uninstall the display driver from control panel> Programs and features. Then follow Drivers - Clean Left over Files after Uninstalling
Now go to Latest AMD Catalyst Video Driver for Windows 7, get the latest WHQL only, and install it.

   Information

WHQL
Release Date: January 17th 2013
Version: 13.1
In Device Manager: 9.012

What is the result of Memtest and prime 95 test? Stress test the Graphics Card using Furmark, too.
Video Card - Stress Test with Furmark

Let us know the results.
_________________________________________
Crash Dump Analysis:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F  , {8, 80050031, 406f8, fffff80001e8fc22}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 ) 

Followup: MachineOwner 
---------

RAM may go corrupt at a time, once it worked fine that does not necessarily mean that it will work as it is forever. It is simply normal.

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.

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.