Please set up your debugger with the correct symbols.
–
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
“ganesh pashupathi” wrote in message
news:xxxxx@ntfsd…
Hi,
With my mini-filter loaded my machine crashed with the following dump ( In the
dump there are no entries corresponding to my filter driver. But it is surely
my driver that is causing the problem):
0: kd> !analyze -v
ERROR: Module load completed but symbols could not be loaded for mvfs50.sys
****************************************************************************
*
Bugcheck Analysis
***************************************************************************
Unknown bugcheck code (0)
Unknown bugcheck description
Arguments:
Arg1: 00000000
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
ERROR: Symbol file could not be found. Defaulted to export symbols for -
ERROR: Symbol file could not be found. Defaulted to export symbols for -
ERROR: Symbol file could not be found. Defaulted to export symbols for -
FAULTING_IP:
nt!KeBugCheck+14
804f9c12 5d pop ebp
EXCEPTION_RECORD: ffffffff – (.exr ffffffffffffffff)
ExceptionAddress: 804f9c12 (nt!KeBugCheck+0x00000014)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000001
NumberParameters: 0
EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are
invalid
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x0
LAST_CONTROL_TRANSFER: from f78bb100 to 804f9c12
STACK_TEXT:
f60394ac f78bb100 00000000 00000000 00000000 nt!KeBugCheck+0x14
WARNING: Stack unwind information not available. Following frames may be wrong.
f6039ac8 f78bb2d9 815e2ba0 82606de0 815e2ba0 mvfs50+0x1f100
f6039b18 804eeeb1 815e2ba0 82606de0 806e4428 mvfs50+0x1f2d9
f6039b28 80656128 00000000 82606de0 fad2fda0 nt!IopfCallDriver+0x31
f6039b4c bae46e9b 815b21e0 82606de0 8157b928 nt!IovCallDriver+0xa0
f6039b70 bae4706b f6039b90 815b21e0 00000000
fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x20b
f6039ba8 804eeeb1 815b21e0 82606de0 806e4428 fltmgr!FltpDispatch+0x11f
f6039bb8 80656128 82606df0 82606de0 faf988c0 nt!IopfCallDriver+0x31
f6039bdc 805827b4 faf988a8 faf98898 00000000 nt!IovCallDriver+0xa0
f6039c14 805b9e25 00f988c0 00000000 faf988a8 nt!IopDeleteFile+0x132
f6039c30 805257b8 faf988c0 00000000 00000000 nt!ObpRemoveObjectRoutine+0xdf
f6039c48 80574f64 f6039d64 00000000 00000000 nt!ObfDereferenceObject+0x4c
f6039ca8 805757ae 06c1f644 00100001 06c1f5e8 nt!IopCreateFile+0x534
f6039d04 80578f6d 06c1f644 00100001 06c1f5e8 nt!IoCreateFile+0x8e
f6039d44 8054060c 06c1f644 00100001 06c1f5e8 nt!NtOpenFile+0x27
f6039d44 7c90eb94 06c1f644 00100001 06c1f5e8 nt!KiFastCallEntry+0xfc
06c1f8b4 7c813817 7ffabc00 00000000 06c1f8f4 ntdll!KiFastSystemCallRet
06c1fb48 7c357056 08236448 06c1fc88 00000003 kernel32!FindFirstFileA+0x3e
06c1fd5c 072b1310 1031d9f0 072b1310 08222e30 MSVCR71!stat+0x97
00000000 00000000 00000000 00000000 00000000 0x72b1310
FOLLOWUP_IP:
mvfs50+1f100
f78bb100 55 push ebp
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: mvfs50+1f100
MODULE_NAME: mvfs50
IMAGE_NAME: mvfs50.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 40d99987
STACK_COMMAND: kb
BUCKET_ID: 0x0_mvfs50+1f100
Followup: MachineOwner
---------
~ganesh