BSOD multiple times the last couple of days

We can use the system specifications listed in the posting topic - Step 5
We can also use the specifications of your system (just fill in the "My System Spec" section of your profile)

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Please uninstall Daemon Tools. It is known to have issues with some Win7 installations.
Please uninstall Catalyst Control Center. It is known to have issues with some Win7 installations.
Feel free to reinstall these (if needed) after we're finished troubleshooting.

You also have the infamous 2005 version of the ASACPI.sys driver. This is a known cause of BSOD's and must be replaced. Visit the Asus support website and download the ATK0110 ACPI Utility driver for your motherboard/system and OS. It will be listed under the ATK or the Utility downloads.

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers (You can look them up here: Driver Reference ).
Please pay particular attention to any dated 2008 or earlier:

Code:

PxHlpa64.sys Mon Dec 10 18:49:01 2007 (475DD06D)
 - Sonic CD/DVD driver (used by many different CD/DVD programs)
 - Driver Reference

adfs.SYS     Thu Jun 26 16:52:37 2008 (48640195)
 - Adobe File System Driver
 - Driver Reference

rdpdispm.sys Fri Mar 21 01:06:22 2008 (47E3424E)
 - RDP Encoder Mirror Driver - Live Mesh
 - Driver Reference

nvm62x64.sys Fri Oct 17 17:01:06 2008 (48F8FD12)
 - nVidia Ethernet Networking Driver (nForce chipset driver)
 - Driver Reference

ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)
 - Asus ATK0110 ACPI Utility (a known BSOD maker).  Also a part of the Asus PCProbe and AISuite   Utilities
 - Driver Reference

wacommousefilter.sys Fri Feb 16 13:12:17 2007 (45D5F401)
 - Wacom(tablet) Mouse Filter
 - Driver Reference

The results of the dump file analysis' are, IMO, inconclusive. But it is highly suggestive of a hardware failure or an incompatibility.
There are 7 memory dumps
Which give 5 different BSOD errors
and they blame 5 different causes.

Please run Driver Verifier according to these instructions (not a critical test if this is a hardware problem):

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) 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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Oct 28 16:22:30.440 2010 (UTC - 4:00)
System Uptime: 0 days 0:12:17.282
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  consent.exe
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02cd680c 00000000`00000000 ffffffff`ffffffff
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Oct 28 14:35:08.415 2010 (UTC - 4:00)
System Uptime: 0 days 0:13:44.257
Probably caused by : Ntfs.sys ( Ntfs! ?? ::NNGAKEGL::`string'+c99c )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`031be768 fffff880`031bdfd0 fffff880`014a5fd2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Oct 28 14:19:46.595 2010 (UTC - 4:00)
System Uptime: 0 days 0:04:49.437
Probably caused by : win32k.sys ( win32k!HANDLELOCK::vLockHandle+10f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  chrome.exe
Bugcheck code 00000050
Arguments fffff900`d000d858 00000000`00000001 fffff960`00194537 00000000`00000002
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct 27 17:12:34.864 2010 (UTC - 4:00)
System Uptime: 0 days 0:37:58.581
*** WARNING: Unable to verify timestamp for MpNWMon.sys
*** ERROR: Module load completed but symbols could not be loaded for MpNWMon.sys
Probably caused by : NETIO.SYS ( NETIO! ?? ::FNODOBFM::`string'+6fad )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`0161d2cd fffff880`031eee88 fffff880`031ee6f0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct 27 16:28:52.088 2010 (UTC - 4:00)
System Uptime: 0 days 5:08:06.804
Probably caused by : Ntfs.sys ( Ntfs! ?? ::FNODOBFM::`string'+6967 )
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0b49c9a8 fffff880`0b49c210 fffff880`0147db93
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Oct 14 16:31:51.061 2010 (UTC - 4:00)
System Uptime: 0 days 4:37:01.902
Probably caused by : ntkrnlmp.exe ( nt!ObOpenObjectByPointerWithTag+85 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  avgrsa.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02f3c73d fffff880`02a8bcc0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 29 14:54:01.243 2010 (UTC - 4:00)
System Uptime: 0 days 2:48:33.084
Probably caused by : fltmgr.sys ( fltmgr! ?? ::FNODOBFM::`string'+1b8b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  AAWService.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`012fa4ef fffff880`0a9a6740 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``