BSOD with various applications - caused by various drivers

I am seeking some assistance with multiple BSODs caused by application errors, generally the most frequent cause is video games.

Drivers that I see reported as causes:
null.sys
npfs.sys
beep.sys
ndproxy.sys
ntfs.sys
null.sys

Remedies attempted so far:
3x wipes
sfc scan - no issues
memtest - no issues (I only ran the general test, no errors reported)
tried removing and using 1 graphic card at a time
monitored tempratures - no issues there

**Update to original Post**
Attempted to run verifier.exe with no windows drivers selected. OS wouldn't boot and got a BSOD during the boot cycle. Cycled through two boot attempts then restored it to get the OS back up.

For what it is worth, this all started when I moved the box so it is most likely a hardware issue vs driver, but I am unsure on how to narrow down the source. 7forum dump is attached to the post.

Any help whatsoever is greatly appreciated, I am at ends length trying to troubleshoot this on my own. Relare

Welcome

What antivirus are you using? I see none listed.

Software concerns:

Code:

Start Menu\Programs\COMODO\COMODO Firewall    Public:Start Menu\Programs\COMODO\COMODO Firewall    Public

Comodo Firewall is known to cause BSoDs on systems. Please uninstall it.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880048ef35c, fffff8800583ebd0, 0}

Unable 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
Probably caused by : cmdguard.sys ( cmdguard+1935c )

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

I and many members on our forum recommend Microsoft security essentials with
a great combination of Malware Bytes.

Microsoft Security Essentials - Free Antivirus for Windows
Malwarebytes - The Free version
Good and Free system security combination.

Run a full scan with both (separately) once downloaded, installed and updated.

Your ASIX AX88772/AX88772A Network Driver needs updating.
Source ax88772.sys ASIX AX88772/AX88772A Network Driver
ASIX AX88772 - USB2.0 LAN Controller

Code:

2: kd> lmvm ax88772
start             end                 module name
fffff880`03db0000 fffff880`03dca000   ax88772  T (no symbols)           
    Loaded symbol image file: ax88772.sys
    Image path: ax88772.sys
    Image name: ax88772.sys
    Timestamp:        Wed Jun 01 12:18:22 2011 (4DE5D9AE)
    CheckSum:         00014ABF
    ImageSize:        0001A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

Start Menu\Programs\Uniblue\SystemTweaker    Public:Start Menu\Programs\Uniblue\SystemTweaker    Public
Start Menu\Programs\Uniblue\Powersuite    Public:Start Menu\Programs\Uniblue\Powersuite    Public

Please refrain from using system tweakers like "Uniblue system tweaker".
They cause damage to windows that are beyond repair.

Please uninstall them using the free version of Revo Uninstallers advanced mode to clear the
programs remaining registries:
Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems


Run the system file checker for any damaged files within windows:
SFC /SCANNOW Command - System File Checker

To make sure your hard drive is good run:
Disk Check

Do these and post back results. We'll do more troubleshooting if need.

Those dumps don't give a probable cause, so lets enable driver verifier rule out buggy drivers.

Driver Verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in verifier and press Enter
- Select Create custom settings (for code developers) and click Next
- Select Select individual settings from a full list and click Next
- Select everything EXCEPT FOR Low Resource Simulation and click Next
- Select Select driver names from a list and click Next
Then select all drivers NOT provided by Microsoft and click Next
- Select Finish on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Capt.Jack Sparrow said:

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Okay.

How does your computer act in safe mode?

Advanced Boot Options