Interestingly, the last BSOD is caused by your Marvell Yukon network adaptor - which is disabled!
Just because of the sheer numbers, I'd have to suspect the libusb0.sys file and would recommend uninstalling it from your system (I recall one other issue with it from another topic also). This is some sort of USB utility that enables the access of USB devices.
Here's the summary of the BSOD's:
Code:
Built by: 6001.18226.x86fre.vistasp1_gdr.090302-1506
Debug session time: Mon May 11 22:13:45.365 2009 (GMT-4)
System Uptime: 0 days 0:17:22.323
BugCheck D1, {2, 2, 0, 8cc69efb}
*** WARNING: Unable to verify timestamp for Apfiltr.sys
*** ERROR: Module load completed but symbols could not be loaded for Apfiltr.sys
Probably caused by : Apfiltr.sys ( Apfiltr+3efb ) (Alps touchpad driver)
PROCESS_NAME: svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6000.16551.x86fre.vista_gdr.070828-1515
Debug session time: Sat May 24 16:03:12.687 2008 (GMT-4)
System Uptime: 0 days 0:00:29.499
BugCheck A, {7c, 1b, 0, 81cad9bb}
Probably caused by : dump_iaStor. ( dump_iaStor+5cca4 ) (Intel Storage Matrix drivers)
PROCESS_NAME: csrss.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Fri Jun 5 19:59:48.715 2009 (GMT-4)
System Uptime: 0 days 0:08:31.602
BugCheck 1000007E, {c0000005, 9121e013, 8b711b68, 8b711864}
*** WARNING: Unable to verify timestamp for libusb0.sys
*** ERROR: Module load completed but symbols could not be loaded for libusb0.sys
Probably caused by : libusb0.sys ( libusb0+428c ) (? http://libusb-win32.sourceforge.net/ )
PROCESS_NAME: System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Sat Jun 6 13:27:35.708 2009 (GMT-4)
System Uptime: 0 days 17:27:23.841
BugCheck 1000007E, {c0000005, 90a2b013, 805ccb68, 805cc864}
*** WARNING: Unable to verify timestamp for libusb0.sys
*** ERROR: Module load completed but symbols could not be loaded for libusb0.sys
Probably caused by : libusb0.sys ( libusb0+428c ) (? http://libusb-win32.sourceforge.net/ )
PROCESS_NAME: System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Sat Jun 6 18:47:46.839 2009 (GMT-4)
System Uptime: 0 days 5:19:38.763
BugCheck 1000007E, {c0000005, 8f263013, 9c851b68, 9c851864}
*** WARNING: Unable to verify timestamp for libusb0.sys
*** ERROR: Module load completed but symbols could not be loaded for libusb0.sys
Probably caused by : libusb0.sys ( libusb0+428c ) (? http://libusb-win32.sourceforge.net/ )
PROCESS_NAME: System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Tue Jun 9 02:39:50.957 2009 (GMT-4)
System Uptime: 0 days 11:10:02.152
BugCheck 1000007E, {c0000005, 8fe60013, a9722b68, a9722864}
*** WARNING: Unable to verify timestamp for libusb0.sys
*** ERROR: Module load completed but symbols could not be loaded for libusb0.sys
Probably caused by : libusb0.sys ( libusb0+428c ) (? http://libusb-win32.sourceforge.net/ )
PROCESS_NAME: System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6000.16575.x86fre.vista_gdr.071009-1548
Debug session time: Thu Jun 12 19:06:58.023 2008 (GMT-4)
System Uptime: 0 days 13:50:33.983
BugCheck D1, {88a9820c, 2, 8, 88a9820c}
Probably caused by : monitor.sys ( monitor+120c ) (Windows system driver)
PROCESS_NAME: Idle
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6001.18000.x86fre.longhorn_rtm.080118-1840
Debug session time: Tue Jun 24 23:10:05.884 2008 (GMT-4)
System Uptime: 7 days 7:38:00.663
BugCheck 9F, {3, 84c64578, 86575030, 8646a808}
*** WARNING: Unable to verify timestamp for yk60x86.sys
*** ERROR: Module load completed but symbols could not be loaded for yk60x86.sys
Probably caused by : yk60x86.sys (Marvell Yukon network driver)
PROCESS_NAME: System
__________________
aka John MVP Windows - Desktop Experience
"There are very few problems in life that can't be fixed by the proper application of high explosives"
If I haven't replied in 48 hours, please send me a PM.