*******************************************************************************
*******************************************************************************
* *
* *
* Bugcheck Analysis *
* Bugcheck Analysis *
* *
* *
*******************************************************************************
*******************************************************************************
Use Use !analyze -v !analyze -v to get detailed debugging information.
to get detailed debugging information.
BugCheck BugCheck 1000007E1000007E, {, {ffffffffc0000005ffffffffc0000005, , fffff8000326d600fffff8000326d600, , fffff88003579a48fffff88003579a48, , fffff880035792a0fffff880035792a0}
}
Unable to load image Unable to load image \SystemRoot\system32\DRIVERS\klif.sys\SystemRoot\system32\DRIVERS\klif.sys, , Win32 error 0n2Win32 error 0n2
*** WARNING: Unable to verify timestamp for *** WARNING: Unable to verify timestamp for klif.sysklif.sys
*** ERROR: Module load completed but symbols could not be loaded for *** ERROR: Module load completed but symbols could not be loaded for klif.sysklif.sys
Probably caused by : Probably caused by : klif.sysklif.sys ( ( klif+97935klif+97935 )
)
Followup:
Followup: MachineOwnerMachineOwner
Debugging Details:
------------------
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
---------
---------