BugCheck 3B, {c0000005, fffff960000d4acb, fffff88002e7f0c0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960000d4acb, Address of the instruction which caused the bugcheck
Arg3: fffff88002e7f0c0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BugCheck 1E, {ffffffffc0000005, fffff880066011aa, 0, 0}
*** WARNING: Unable to verify timestamp for SbieDrv.sys
*** ERROR: Module load completed but symbols could not be loaded for SbieDrv.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
BugCheck D1, {783fe98, 2, 8, 783fe98}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
