I've seen lot's of issues with Google Update recently. Try uninstalling it ( Uninstall the Updater : Removing the Updater - Google Pack and Updater Help ). Leave it off while testing, then update to the latest version if you want the software on your system.

I would also uninstall your video capture device driver (likely to be a webcam) - either in Control Panel...Programs...Uninstall a program - or from Device Manager. Once it's uninstalled, download and install a fresh driver from PC manufacturer's website. This device driver has caused at least one of the BSOD's on your system.

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system. Reference links included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

Code:

bcmwl6.sys      Wed Oct 22 20:41:24 2008 (48FFC834)
yk60x86.sys     Wed Jul 16 05:12:41 2008 (487DBB89)
GEARAspiWDM.sys Mon May 18 08:16:53 2009 (4A1151B5)
igdkmd32.sys    Wed Aug 25 15:31:24 2010 (4C756F8C)
stwrt.sys       Fri Feb 26 03:07:28 2010 (4B878140)
aswMonFlt.sys   Wed Feb 23 09:55:01 2011 (4D651FC5)
BCM42RLY.sys    Tue Nov 11 22:07:23 2008 (491A486B)
aswFsBlk.SYS    Wed Feb 23 09:54:54 2011 (4D651FBE)
avgntflt.sys    Thu Nov 11 10:54:47 2010 (4CDC11C7)

http://www.carrona.org/dvrref.html#bcmwl6.sys
http://www.carrona.org/dvrref.html#yk60x86.sys
http://www.carrona.org/dvrref.html#GEARAspiWDM.sys
http://www.carrona.org/dvrref.html#igdkmd32.sys
http://www.carrona.org/dvrref.html#stwrt.sys
http://www.carrona.org/dvrref.html#aswMonFlt.sys
http://www.carrona.org/dvrref.html#BCM42RLY.sys
http://www.carrona.org/dvrref.html#aswFsBlk.SYS
http://www.carrona.org/dvrref.html#avgntflt.sys

If all of this doesn't fix things, then I'd try running Driver Verifier according to these directions:

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: 6002.18327.x86fre.vistasp2_gdr.101014-0432
Debug session time: Mon Mar 21 16:44:07.488 2011 (UTC - 4:00)
System Uptime: 0 days 0:04:02.208
Probably caused by : ntkrpamp.exe ( nt!ObpCloseHandleTableEntry+6d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x8E
PROCESS_NAME:  AvastSvc.exe
FAILURE_BUCKET_ID:  0x8E_nt!ObpCloseHandleTableEntry+6d
Bugcheck code 1000008E
Arguments c0000005 009ce770 8ab43c50 00000000
BiosVersion = A05
BiosReleaseDate = 02/25/2009
CPUID:        "Intel(R) Core(TM)2 Duo CPU     T6400  @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.x86fre.vistasp2_gdr.101014-0432
Debug session time: Mon Mar 21 16:39:37.806 2011 (UTC - 4:00)
System Uptime: 1 days 17:34:41.069
Probably caused by : ntkrpamp.exe ( nt!CcGetVirtualAddressIfMapped+8c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xA_nt!CcGetVirtualAddressIfMapped+8c
Bugcheck code 0000000A
Arguments 10000008 00000002 00000000 81c4521b
BiosVersion = A05
BiosReleaseDate = 02/25/2009
CPUID:        "Intel(R) Core(TM)2 Duo CPU     T6400  @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.x86fre.vistasp2_gdr.101014-0432
Debug session time: Thu Mar 17 06:46:54.616 2011 (UTC - 4:00)
System Uptime: 0 days 13:27:52.069
Probably caused by : ntkrpamp.exe ( nt!KeWaitForGate+126 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  lsass.exe
FAILURE_BUCKET_ID:  0xA_nt!KeWaitForGate+126
Bugcheck code 0000000A
Arguments 00000060 0000001b 00000001 81c43435
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.x86fre.vistasp2_gdr.101014-0432
Debug session time: Tue Mar 15 08:41:17.748 2011 (UTC - 4:00)
System Uptime: 0 days 8:38:50.240
Probably caused by : ntkrpamp.exe ( nt!KiUnwaitThread+14 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  0xA_nt!KiUnwaitThread+14
Bugcheck code 0000000A
Arguments 00000000 0000001b 00000000 81cad5d5
BiosVersion = A05
BiosReleaseDate = 02/25/2009
CPUID:        "Intel(R) Core(TM)2 Duo CPU     T6400  @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18327.x86fre.vistasp2_gdr.101014-0432
Debug session time: Mon Mar 14 14:55:27.068 2011 (UTC - 4:00)
System Uptime: 0 days 13:47:42.951
*** WARNING: Unable to verify timestamp for OA009Vid.sys
*** ERROR: Module load completed but symbols could not be loaded for OA009Vid.sys
*** WARNING: Unable to verify timestamp for OA009Ufd.sys
*** ERROR: Module load completed but symbols could not be loaded for OA009Ufd.sys
Probably caused by : OA009Vid.sys ( OA009Vid+3ace3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xA_OA009Vid+3ace3
Bugcheck code 0000000A
Arguments 00000000 0000001b 00000001 81c65d9b
BiosVersion = A05
BiosReleaseDate = 02/25/2009
CPUID:        "Intel(R) Core(TM)2 Duo CPU     T6400  @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``