No firm blame assessed by the memory dumps. We'll have to see what happens after doing the following.
Please update or remove 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 current drivers:
Quote:
How To Find Updated 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.
- some driver links are on this page:
http://www.carrona.org/drvrdown.html
Here's the older drivers. I am very concerned with the drivers from 2003:
Code:
STK016W1.SYS Fri Oct 03 12:08:35 2003 - Syntek.USBDCam,USB\VID_05e1&PID_0895
STK016W2.sys Fri Oct 03 12:08:41 2003 - Syntek.USBDCam,USB\VID_05e1&PID_0895
000.fcl Fri Sep 26 09:11:12 2008 - CyberLink FCL Driver
adfs.SYS Thu Aug 14 10:57:15 2008 - Adobe File System Driver
Gt51Ip.sys Mon Jul 09 08:17:34 2007 - possibly T-Mobile UMTS USB Stick driver
gt72ubus.sys Tue Jun 26 07:38:45 2007 - Globetrotter 3g or Option Icon 225 USB data stick from Orange
gtptser.sys Fri Mar 30 07:38:12 2007 - Option N.V.
nvBridge.kmd Sun Sep 27 19:56:53 2009 - NVIDIA Compatible Windows Vista Kernel Mode Driver,
nvm62x32.sys Fri Oct 17 17:00:39 2008 - NVIDIA nForce Networking Controller
wtsmpadap.sys Wed Apr 23 13:07:48 2008 - WtSmpAdap NDIS Miniport Driver - Sesam virtual adapter - Swisscom Mobile
wtsmpflt.sys Wed Apr 23 13:11:57 2008 - Sesam intermediate driver - Sesam filter driver - Swisscom Mobile
afsub99l.SYS Wed Dec 03 13:18:18 2008 - unknown driver, please search your hard drive for this and submit it to http://virusscan.jotti.org Also, please right click on it, select Properties, then select Details - and let us know of any information there about the writer of this driver.
Pleaese post back if the BSOD's continue after doing all of this. We'll have some more tests to run.
Here's the summary of the BSOD's:
Code:
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat Jan 23 01:28:14.336 2010 (GMT-5)
System Uptime: 0 days 0:38:04.287
BugCheck 9F, {4, 258, 852cb4c0, 82d69b24}
Probably caused by : cdrom.sys ( cdrom!DeviceSendPowerProcessRequest+15b )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat Jan 23 06:09:31.421 2010 (GMT-5)
System Uptime: 0 days 3:03:43.371
*** WARNING: Unable to verify timestamp for gt72ubus.sys
*** ERROR: Module load completed but symbols could not be loaded for gt72ubus.sys
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat Jan 23 06:31:02.841 2010 (GMT-5)
System Uptime: 0 days 0:20:53.791
*** WARNING: Unable to verify timestamp for gt72ubus.sys
*** ERROR: Module load completed but symbols could not be loaded for gt72ubus.sys
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System