With the exception of one specific driver, most of your .dmp files are pointing to core Windows 7 files, and it is doubtful that they are to blame...
The specific driver that is blamed is ssidrv.sys. This is a driver for SpySweeper (Antivirus & Anti Spyware Security Software for Home & Business | Webroot) Delete this program and replace it with another product
SuperAntiSpyware is used by a great many users and comes highly recommended...
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa8007ca7b30, fffffa8007ca7e10, fffff80002bcb240}
Probably caused by : Winlogon.exe
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Winlogon
IMAGE_NAME: Winlogon.exe
FAILURE_BUCKET_ID: X64_0xF4_taskmgr.exe_IMAGE_Winlogon.exe
BUCKET_ID: X64_0xF4_taskmgr.exe_IMAGE_Winlogon.exe
Followup: MachineOwner
---------
_________________________________________________________________________
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff96000188e2b, fffff8800be5ec80, 0}
Probably caused by : win32k.sys ( win32k!GetStyleWindow+13 )
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck BE, {fffff96000056b5e, 737000003478e021, fffff88002583810, b}
Probably caused by : win32k.sys ( win32k!xxxInternalDoSyncPaint+99 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xBE
PROCESS_NAME: explorer.exe
CURRENT_IRQL: 0
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 135, {ffffffffc0000005, fffff8800a6118d0, fffff88000e69334, fffff8a00028a9a0}
Unable to load image \SystemRoot\system32\DRIVERS\ssidrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ssidrv.sys
*** ERROR: Module load completed but symbols could not be loaded for ssidrv.sys
Probably caused by : ssidrv.sys ( ssidrv+7f14 )
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8003d69028, be000000, 800400}
Probably caused by : hardware
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 135, {ffffffffc0000005, fffff8800b6938d0, fffff88000e69334, fffff8a0002bb730}
Unable to load image \SystemRoot\system32\DRIVERS\ssidrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ssidrv.sys
*** ERROR: Module load completed but symbols could not be loaded for ssidrv.sys
Probably caused by : ssidrv.sys ( ssidrv+7f14 )
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 135, {ffffffffc0000005, fffff88009a7e8d0, fffff88000e73334, fffff8a00023c310}
Unable to load image \SystemRoot\system32\DRIVERS\ssidrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ssidrv.sys
*** ERROR: Module load completed but symbols could not be loaded for ssidrv.sys
Probably caused by : ssidrv.sys ( ssidrv+7f14 )
Followup: MachineOwner
---------
You also have an outdated driver that should be updated...
Code:
fffff880`049fa000 fffff880`049fe980 Lycosa Lycosa.sys Fri Jan 18 03:51:42 2008 (4790689E) Please uninstall the software and drivers for your Razer Tarantula Keyboard
Once you have done this enable driver verifier ...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"
- 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).
Quote