BSOD Bad_Pool_Caller Error Help

I am getting the Bad_Pool_caller BSOD Error.
The following is the debug report. I came to know that ntkrpamp.exe is causing this problem. What is the solution

Loading Dump File [C:\WINDOWS\Minidump\Mini040808-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 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_qfe.070227-2300
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Tue Apr 8 01:16:41.390 2008 (GMT+6)
System Uptime: 0 days 8:13:14.149
Loading Kernel Symbols
...................................................................................................................................
Loading User Symbols
Loading unloaded module list
.................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, cd4, 2430001, 89a52df0}



Probably caused by : ntkrpamp.exe ( nt!ExFreePoolWithTag+2a3 )

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: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 02430001, Memory contents of the pool block
Arg4: 89a52df0, Address of the block of pool being deallocated

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




POOL_ADDRESS: 89a52df0

FREED_POOL_TAG: Ddk

BUGCHECK_STR: 0xc2_7_Ddk

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 8054a583 to 804f9f13

STACK_TEXT:
b6766cd4 8054a583 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b
b6766d24 805bfa86 89a52df0 00000000 89c23c40 nt!ExFreePoolWithTag+0x2a3
b6766d4c 805ba02b 00000000 89c23c58 00000001 nt!ObpFreeObject+0x142
b6766d64 805ba476 89c23c58 00000001 80561e80 nt!ObpRemoveObjectRoutine+0xe7
b6766d7c 80537aff 00000000 00000000 88af75f0 nt!ObpProcessRemoveObjectQueue+0x36
b6766dac 805cea08 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
b6766ddc 8054546e 80537a10 80000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExFreePoolWithTag+2a3
8054a583 8b45f8 mov eax,dword ptr [ebp-8]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!ExFreePoolWithTag+2a3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45e5484a

FAILURE_BUCKET_ID: 0xc2_7_Ddk__nt!ExFreePoolWithTag+2a3

BUCKET_ID: 0xc2_7_Ddk__nt!ExFreePoolWithTag+2a3

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