XP Blue screen on undock ntkrpamp.exe

Hello All,

I have a dell latitude D620 2gb RAM. XP sp2 installed. When undocking the laptop xp bsod's. I have attached debug info below. Please HELP..
I suspect its bad memory as its pointing to ntkrpamp.exe


Any help would be greatly appreciated


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


Loading Dump File [C:\Documents and Settings\amar.vadher\Desktop\Mini041207-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\tmp*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.061219-0311
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Wed Apr 11 17:41:31.414 2007 (GMT+1)
System Uptime: 0 days 9:00:02.615
Loading Kernel Symbols
........................................................................................................................................................
Loading User Symbols
Loading unloaded module list
........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {bad0b158, 0, 805bad71, 2}


Could not read faulting driver name
Probably caused by : ntkrpamp.exe ( nt!ObpCloseHandleTableEntry+13 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: bad0b158, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 805bad71, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: bad0b158

FAULTING_IP:
nt!ObpCloseHandleTableEntry+13
805bad71 83b9a800000000 cmp dword ptr [ecx+0A8h],0

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: DSAgnt.exe

LAST_CONTROL_TRANSFER: from 805baf49 to 805bad71

STACK_TEXT:
b9240cfc 805baf49 e298add0 e291f800 00000400 nt!ObpCloseHandleTableEntry+0x13
b9240d44 805bb081 00000400 00000001 00000000 nt!ObpCloseHandle+0x87
b9240d58 805409ac 00000400 0298fb40 7c90eb94 nt!NtClose+0x1d
b9240d58 7c90eb94 00000400 0298fb40 7c90eb94 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0298fb40 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ObpCloseHandleTableEntry+13
805bad71 83b9a800000000 cmp dword ptr [ecx+0A8h],0

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ObpCloseHandleTableEntry+13

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45880f61

FAILURE_BUCKET_ID: 0x50_BADMEMREF_nt!ObpCloseHandleTableEntry+13

BUCKET_ID: 0x50_BADMEMREF_nt!ObpCloseHandleTableEntry+13

Followup: MachineOwner

 

Hello eezer and welcome to the Board,

Test the RAM: http://oca.microsoft.com/en/windiag.asp

Regards - Charles