System crash when ending FC 2009.02 / 02a

[samiel]

Hi Marek,

I'm using FC 2009.02 / 02a, Windows XP SP3.

When closing the FC application (both 2009.02 and 02a) by using the red X in the upper right corner, it happens that my system crashes, i.e. when FC has been running for a while (min. 15 min.).

One of the minidump crash files is attached for your analysis.

_____________________________________________________
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8056c4de, The address that the exception occurred at
Arg3: f77ad4a0, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden.

FAULTING_IP:
nt!ExpLookupHandleTableEntry+15
8056c4de 3b5138 cmp edx,dword ptr [ecx+38h]

TRAP_FRAME: f77ad4a0 -- (.trap 0xfffffffff77ad4a0)
ErrCode = 00000000
eax=00000092 ebx=00000000 ecx=00000000 edx=00000248 esi=8629e938 edi=f77ad6d0
eip=8056c4de esp=f77ad514 ebp=f77ad514 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!ExpLookupHandleTableEntry+0x15:
8056c4de 3b5138 cmp edx,dword ptr [ecx+38h] ds:0023:00000038=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: FreeCommander.e

LAST_CONTROL_TRANSFER: from 8056c527 to 8056c4de

STACK_TEXT:
f77ad514 8056c527 00000000 00000248 f77ad5bc nt!ExpLookupHandleTableEntry+0x15
f77ad528 8056c598 00000000 00000248 f77ad700 nt!ExMapHandleToPointerEx+0x1b
f77ad54c 8058a2e4 00000248 00000000 00000000 nt!ObReferenceObjectByHandle+0xe9
f77ad624 804dd99f 00000248 00000000 f77ad6d0 nt!NtQueryObject+0x99
f77ad624 804e3f4f 00000248 00000000 f77ad6d0 nt!KiFastCallEntry+0xfc
f77ad6b0 ae0e8a49 00000248 00000000 f77ad6d0 nt!ZwQueryObject+0x11
WARNING: Stack unwind information not available. Following frames may be wrong.
f77ad764 ae0cca23 00000248 000005f0 f77ad8a4 vsdatant+0x66a49
f77ad82c 8056fc4b e2cfd3c8 000001dc 00000040 vsdatant+0x4aa23
f77ad880 804dd99f 00000248 00000248 ffffffff nt!ExpAllocateHandleTableEntry+0xe3
f77ad880 7c91e514 00000248 00000248 ffffffff nt!KiFastCallEntry+0xfc
0147fc0c 00000000 00000000 00000000 00000000 0x7c91e514


STACK_COMMAND: kb

FOLLOWUP_IP:
vsdatant+66a49
ae0e8a49 ?? ???

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: vsdatant+66a49

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: vsdatant

IMAGE_NAME: vsdatant.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4abaceba

FAILURE_BUCKET_ID: 0x8E_vsdatant+66a49

BUCKET_ID: 0x8E_vsdatant+66a49

Followup: MachineOwner
---------
________________________________________

Your tool is great, would be helpful to get your opinion on this, thx.