BSOD watching videos off the net.

I'd say that the video card is OK - maybe the VMT test was a fluke?

I've started on the last 7 dump files (there was 20 days between them and the next most recent). ewusbnet.sys is blamed in 5 of them.

Your ewusbnet.sys driver is probably the issue. There have been quite a few of these in the last week or so, so I suspect that they've run afoul of a Windows Update and have become incompatible. I would suggest obtaining the latest software/drivers for your mobile USB "Air card" from the phone company that provides the card.

If the phone company doesn't help, then we'll need the exact model of the USB device so that we can figure out what to try. There are 2 things we'll need:
- any numbers on the case of the device
- the hardware ID of the device from Device Manager
Those will help us to choose the correct drivers. More info on Huawei products is here: Technical Support - Welcome to Huawei.com

If you are able to get a link for newer drivers, be sure that they're from later than Oct 2009 - those are the dates of your current drivers.

BSOD BUGCHECK SUMMARY

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Nov  6 07:52:53.413 2010 (UTC - 5:00)
System Uptime: 1 days 10:59:21.910
*** WARNING: Unable to verify timestamp for ewusbnet.sys
*** ERROR: Module load completed but symbols could not be loaded for ewusbnet.sys
Probably caused by : ewusbnet.sys ( ewusbnet+31180 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
Bugcheck code 00000050
Arguments fffff880`09fe913e 00000000`00000000 fffff880`06df2180 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Nov  4 06:11:02.460 2010 (UTC - 5:00)
System Uptime: 0 days 1:12:13.896
*** WARNING: Unable to verify timestamp for ewusbnet.sys
*** ERROR: Module load completed but symbols could not be loaded for ewusbnet.sys
Probably caused by : ewusbnet.sys ( ewusbnet+27b6 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`0606d7b6 fffff880`03d838b8 fffff880`03d83110
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Nov  1 13:12:49.713 2010 (UTC - 5:00)
System Uptime: 0 days 0:23:33.759
*** WARNING: Unable to verify timestamp for ewusbnet.sys
*** ERROR: Module load completed but symbols could not be loaded for ewusbnet.sys
Probably caused by : ewusbnet.sys ( ewusbnet+27b6 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`06a027b6 fffff880`08e758b8 fffff880`08e75110
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Oct 28 04:32:35.404 2010 (UTC - 5:00)
System Uptime: 1 days 22:02:49.930
*** WARNING: Unable to verify timestamp for ewusbnet.sys
*** ERROR: Module load completed but symbols could not be loaded for ewusbnet.sys
Probably caused by : ewusbnet.sys ( ewusbnet+27b6 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`0638f7b6 fffff880`087a48b8 fffff880`087a4110
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Oct 23 10:03:38.133 2010 (UTC - 5:00)
System Uptime: 0 days 2:22:19.569
*** WARNING: Unable to verify timestamp for ewusbnet.sys
*** ERROR: Module load completed but symbols could not be loaded for ewusbnet.sys
Probably caused by : ewusbnet.sys ( ewusbnet+27b6 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`05c7c7b6 fffff880`03b588b8 fffff880`03b58110
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Oct 20 03:41:24.114 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:36.550
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avgcsrva.exe
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`01f682a0 00000000`0000ffff 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Oct 20 03:38:20.531 2010 (UTC - 5:00)
System Uptime: 0 days 0:01:19.967
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  drvinst.exe
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`0195dc20 00000000`0000ffff 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  

Your's will be the the USB device (VID_ and PID__) from this canned speech of mine:

Obtaining Hardware ID's to help Identify Hardware
- Go to Start and type in "devmgmt.msc" (without the quotes) and press Enter
- Expand the Network Adapters category by clicking on the + sign to the left of it
- Right click on the network adapter (if there's more than one, do this for all of them) and select Properties.
- Then select the Details tab.
- In the dropdown box, select "Hardware IDs" - and match the info to one of the following descriptions:
- - If the Hardware IDs description contains VEN_ and DEV_, then let us know the 4 characters immediately after the VEN_ and the 4 characters immediately after the DEV_
this is a PCI device and we'll look up the information at http://www.pcidatabase.com
- - If the Hardware IDs description contains VID_ and PID_, then let us know the 4 characters immediately after the VID_ and the 4 characters immediately after the PID_
this is a USB device and we'll look up the information at http://www.linux-usb.org/usb.ids
If you don't have those items in the Hardware IDs description, copy down the entire string of the first entry and include that with your next post.