Windows server 2003 蓝屏 debug 结果“Probably caused by : netbt.sys”

各位，

最近我有台win2003 DC蓝屏过2次，debug结果显示可能是netbt.sys 问题，下面是debug结果，请问这种问题该如何解决？谢谢！

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


Loading Dump File [D:\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

WARNING: Non-directory path: 'D:\\MEMORY.DMP'
Symbol search path is: SRV*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: D:\20110911\MEMORY.DMP
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: LanManNt, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.101019-0340
Machine Name:
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
Debug session time: Fri Jan 27 13:44:08.079 2012 (GMT+8)
System Uptime: 1 days 5:06:55.742
Loading Kernel Symbols
...............................................................
........................................................
Loading User Symbols

Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {54, d0000002, 1, b9d38984}

*** ERROR: Module load completed but symbols could not be loaded for bxnd52x.sys
*** ERROR: Module load completed but symbols could not be loaded for bxvbdx.sys
Probably caused by : netbt.sys ( netbt!NbtTryToIndicateUsingProviderBuffer+cc )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000054, memory referenced
Arg2: d0000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: b9d38984, address which referenced memory

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


WRITE_ADDRESS:  00000054 

CURRENT_IRQL:  2

FAULTING_IP: 
netbt!NbtTryToIndicateUsingProviderBuffer+cc
b9d38984 83605400        and     dword ptr [eax+54h],0

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Idle

TRAP_FRAME:  8089a000 -- (.trap 0xffffffff8089a000)
ErrCode = 00000002
eax=00000000 ebx=00000023 ecx=0001ffff edx=8089a168 esi=a24b9388 edi=8089a0ec
eip=b9d38984 esp=8089a074 ebp=8089a08c iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
netbt!NbtTryToIndicateUsingProviderBuffer+0xcc:
b9d38984 83605400        and     dword ptr [eax+54h],0 ds:0023:00000054=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from b9d38984 to 8088c9eb

STACK_TEXT:  
8089a000 b9d38984 badb0d00 8089a168 8089a04c nt!KiTrap0E+0x2a7
8089a08c b9d388c9 a4e21d08 014b9388 00000e20 netbt!NbtTryToIndicateUsingProviderBuffer+0xcc
8089a0d0 b9d38dbe a4e21d08 a24b9388 00000e20 netbt!IndicateBuffer+0x6d
8089a108 b9d834c4 a4e21d08 a24b9400 00000e20 netbt!TdiReceiveHandler+0xc5
8089a170 b9d81354 002d1280 00001850 a4e27b20 tcpip!IndicateData+0x300
8089a1bc b9d80ab0 2541030b 2541030b a4e27b20 tcpip!TcpFastReceive+0x301
8089a298 b9d7d101 a4e67b98 4100800a