Dump file for Windows 2000 Server SP4 - please shed some light

Below is a copy of a dump file I have on a server which has failed
several times over the last few months, could someone please
enlighten me as to where there may be a problem...


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


Loading Dump File [C:\IC Dump Files\G6_2006_03_26_MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

************************************************************************
WARNING: Dump file has inconsistent set-bit count. Data may be missing.
************************************************************************
Symbol search path is: C:\WINNT\SYMBOLS
Executable search path is:
Windows 2000 Kernel Version 2195 (Service Pack 4) MP (4 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Kernel base = 0x80400000 PsLoadedModuleList = 0x80484520
Debug session time: Sun Mar 26 01:41:00.328 2006 (GMT+1)
System Uptime: 4 days 10:54:00.603
Loading Kernel Symbols
............................................................................................................
Loading User Symbols
PEB address is NULL !
Loading unloaded module list
..................................................
The call to LoadLibrary(ext) failed, Win32 error 127
"The specified procedure could not be found. "
Please check your debugger configuration and/or network access.
The call to LoadLibrary(ext) failed, Win32 error 127
"The specified procedure could not be found. "
Please check your debugger configuration and/or network access.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Bugcheck code 0000000A
Arguments 00000000 0000001c 00000001 8042c2b9

ChildEBP RetAddr Args to Child
f6473c68 8042c2b9 8046cd17 00000000 00473ca4 nt!KiTrap0E+0x284
f6473cfc bfe88c57 87f6f568 00000000 00000000 nt!KeWaitForSingleObject+0x13b
*** ERROR: Module load completed but symbols could not be loaded for LANPkt.sys
f6473d20 f655eb91 87f6f568 00000000 bec36ba0 NDIS!NdisWaitEvent+0x37
WARNING: Stack unwind information not available. Following frames may be wrong.
f6473d5c 804af55a 86cc0ad0 bec36ba0 8047747c LANPkt+0xb91
f6473d78 80417481 bec36ba0 00000000 00000000 nt!IopLoadUnloadDriver+0x14
f6473da8 80455a82 bec36ba0 00000000 00000000 nt!ExpWorkerThread+0xaf
f6473ddc 8046b012 804173d2 00000001 00000000 nt!PspSystemThreadStartup+0x54
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

0: kd> !analyze -show
The call to LoadLibrary(ext) failed, Win32 error 127
"The specified procedure could not be found. "
Please check your debugger configuration and/or network access.
No export analyze found

 

Hii,

Finding
1) Crash at KeWaitForSingleObject is the sign of faulty ram
2) Maybw it is software error of LANPkt (RealTek Modem Driver)

Suggestion
1) Run memtest to stress test the ram
2) Upgrade LANPkt
3) One minidump is insufficient to confirm the culprit. Attach more debug report if you have. The system event 1001/1003 is also very useful to determine the root cause of the problem.


Stack Trace of your minidump
f6473cfc bfe88c57 87f6f568 00000000 00000000 nt!KeWaitForSingleObject+0x13b
f6473d20 f655eb91 87f6f568 00000000 bec36ba0 NDIS!NdisWaitEvent+0x37
f6473d5c 804af55a 86cc0ad0 bec36ba0 8047747c LANPkt+0xb91

 

Possible conflict with Netgear network hardware

Thanks for the reply.
The problem may be a cause of a new netgear network card installed on the server.
Thanks for looking into this, though.

Wazza