Random, sporadic stop error (BSOD)

Please help,
Debug Memory Dump, (figure out what is causing a BSOD), see below.

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini111508-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.080814-1236
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Nov 15 11:37:06.679 2008 (GMT-5)
System Uptime: 0 days 3:19:14.675
Loading Kernel Symbols
...........................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {40, 0, 80000000, 0}

Unable to load image vsdatant.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for vsdatant.sys
*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
Probably caused by : vsdatant.sys ( vsdatant+2fc9a )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000040, Attempt to free usermode address to kernel pool
Arg2: 00000000, Starting address
Arg3: 80000000, Start of system address space
Arg4: 00000000, 0

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


FAULTING_IP:
nt!NtSetInformationFile+724
8057b734 8b450c mov eax,dword ptr [ebp+0Ch]

BUGCHECK_STR: 0xc2_40

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: vsserv.exe

LAST_CONTROL_TRANSFER: from 80548c2d to 804f9f43

STACK_TEXT:
a9fbbbac 80548c2d 000000c2 00000040 00000000 nt!KeBugCheckEx+0x1b
a9fbbbec 8054b49a 00000000 88ab91e8 00000000 nt!MiFreePoolPages+0x8b
a9fbbc2c 8057b734 00000000 00000000 01fdf138 nt!ExFreePoolWithTag+0x1ba
a9fbbcbc ad1acc9a 00000400 01cb0008 01cb0010 nt!NtSetInformationFile+0x724
WARNING: Stack unwind information not available. Following frames may be wrong.
a9fbbd30 8054162c 01fdf160 c0100080 01fdf100 vsdatant+0x2fc9a
a9fbbd30 7c90e4f4 01fdf160 c0100080 01fdf100 nt!KiFastCallEntry+0xfc
01fdf158 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
vsdatant+2fc9a
ad1acc9a ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: vsdatant+2fc9a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: vsdatant

IMAGE_NAME: vsdatant.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4874da4c

FAILURE_BUCKET_ID: 0xc2_40_vsdatant+2fc9a

BUCKET_ID: 0xc2_40_vsdatant+2fc9a

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

1: kd> lmvm vsdatant
start end module name
ad17d000 ad1dc0e0 vsdatant T (no symbols)
Loaded symbol image file: vsdatant.sys
Image path: vsdatant.sys
Image name: vsdatant.sys
Timestamp: Wed Jul 09 11:33:32 2008 (4874DA4C)
CheckSum: 00068FDC
ImageSize: 0005F0E0
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0

Thanks.
GMM