Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa800673be30, fffff80000ba2748, fffffa8006c483f0}
*** WARNING: Unable to verify timestamp for dwvkbd64.sys
*** ERROR: Module load completed but symbols could not be loaded for dwvkbd64.sys
Probably caused by : ntkrnlmp
Followup: MachineOwner
Hi,
all your dump files are the same and point to a driver not completing it's job effectively. The above mentioned dwvkbd64.sys is on every dump file and it's possible that this could be the source of the issue.
dwvkbd64.sys Wed Apr 11 22:22:37 2007: DameWare Virtual Keyboard Driver? If the driver isn't needed try uninstalling it otherwise you could try either updating or at worse re-installing.
I also noticed the BSOD was occurring when the os was running some core systems and you may have some corruption which could affect the driver..
Find command prompt in the start menu, right click on it, choose properties and then run as admin. Type:
sfc /scannow
Press enter and await results.
DamewareMini.sys Sun Mar 16 18:42:28 2008: DameWare Development Mirror Display Driver possibly linked with the above virtual keyboard driver? Treat as above.
Other than the Dameware stuff your drivers don't look too bad date wise. Some are not exactly bang up to date but close enough..
Post any new dump files.