Windows 7 Unexpected BSOD results in Crash Dump

[mlamtech]

Hello everyone,

I have recently had several crash dump files appear in c:\windows\minidump.

I am uploading it here, for those who may wish to review it. However, I cannot specify what the cause of this problem may have been.

 

[kemical]

*******************************************************************************
*                                                                             *
*                        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.

 

[mlamtech]

*******************************************************************************
*                                                                             *
*                        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.

Thank you I tried uninstalling the DameWare and reinstalling and the issue still occurred, I am currently doing a system restore but I would like to know how were you able to read the mini dumps and identify the probable cause.

 

[mlamtech]

[QUOTE

Post any new dump files.[/QUOTE]

This is the latest BSOD even after restoring the Pc.

 

[kemical]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800673fbb0, fffff80000b9c3d8, fffffa800a325010}

Unable to load image \SystemRoot\system32\DRIVERS\dwvkbd64.sys, Win32 error 0n2
*** 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,
looks like the driver was contained in the restore too:

dwvkbd64.sys Wed Apr 11 22:22:37 2007: Dameware keyboard driver. Try uninstalling again or doing a search for the above driver and renaming it to dwvkbd.old. Remove this driver too:
DamewareMini.sys Sun Mar 16 18:42:28 2008

You also need to update some Intel drivers. Please run the Intel update utility:
Link Removed

As mentioned in the above post i also believe you have some system corruption which is probably in the restore as well please run the SFC:
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.

Sometimes debugging can be a process of elimination and you can read dump files using the tools found here:
http://support.microsoft.com/kb/315263
Post any new dump files