These were all related to a driver taking too long to respond. Best bet is that in your case it is Norton that is the culprit. Also of note, one crash was directly related to your VMNetSrv.sys
I would remove and replace Norton at least to test and update the below old drivers.
Symantec is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST
http://us.norton.com/support/kb/web_...080710133834EN Microsoft Security Essentials - Free Antivirus for Windows Norton 360 How to uninstall
Old drivers
Code:
pfc.sys 9/19/2003 7:45:46 PM
dne2000.sys 1/24/2007 3:17:24 AM
VMNetSrv.sys 1/24/2007 8:05:29 AM
CVPNDRVA.sys 4/3/2007 8:17:07 PM
rimsptsk.sys 7/29/2007 9:42:56 PM
rixdptsk.sys 7/29/2007 10:54:01 PM
itecir.sys 12/18/2007 5:12:11 AM
dfmirage.sys 1/11/2008 5:03:51 PM
rimmptsk.sys 2/15/2008 5:01:16 AM
adfs.SYS 8/14/2008 10:57:15 AM
OA001Ufd.sys 3/6/2009 3:30:08 AM
OA001Vid.sys 3/8/2009 8:57:13 PM
bcmwl6.sys 3/26/2009 8:58:48 PM
vmm.sys 5/15/2009 8:27:51 AM
stwrt.sys 6/29/2009 1:51:26 PM
IntcHdmi.sys 7/10/2009 9:44:50 AM
How To Find 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 Reference Table
- - Driver manufacturer links are on this page:
Drivers and Downloads