这是分析结果，谢谢。
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini080209-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\temp*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (3 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0x82c18000 PsLoadedModuleList = 0x82d2fc70
Debug session time: Sun Aug 2 21:16:08.451 2009 (GMT+8)
System Uptime: 0 days 9:00:14.423
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 8, 0}
Unable to load image \SystemRoot\system32\DRIVERS\HdFwLH.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for HdFwLH.sys
*** ERROR: Module load completed but symbols could not be loaded for HdFwLH.sys
Probably caused by : HdFwLH.sys ( HdFwLH+5979 )
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: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 00000000, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d4f868
Unable to read MiSystemVaType memory at 82d2f420
00000000
CURRENT_IRQL: 2
FAULTING_IP:
+65ce952f021bdce8
00000000 ?? ???
PROCESS_NAME: System
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
TRAP_FRAME: 8b9848bc -- (.trap 0xffffffff8b9848bc)
ErrCode = 00000010
eax=87d3a510 ebx=00000000 ecx=00000000 edx=00000000 esi=87d3a630 edi=8b984a90
eip=00000000 esp=8b984930 ebp=8b984aa8 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
00000000 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from 00000000 to 82c65fb9
FAILED_INSTRUCTION_ADDRESS:
+65ce952f021bdce8
00000000 ?? ???
STACK_TEXT:
8b9848bc 00000000 badb0d00 00000000 87c43018 nt!KiTrap0E+0x2e1
WARNING: Frame IP not in any known module. Following frames may be wrong.
8b98492c 937d8979 00000000 00000016 8b984b44 0x0
8b984aa8 936fe426 87d3a510 00000016 8b984b44 HdFwLH+0x5979
8b984bd0 83478b03 8766e5d0 8b984bf0 85fe2244 tdx!TdxEventReceiveMessagesTransportAddress+0x48e
8b984c08 83473eb3 00000000 00000001 00000000 tcpip!UdpDeliverDatagrams+0x23b
8b984c54 83473f00 87203b38 00d83b80 8b984c90 tcpip!UdpReceiveDatagrams+0x112
8b984c64 834736e3 8b984c78 c000023e 00000000 tcpip!UdpNlClientReceiveDatagrams+0x12
8b984c90 83473110 834c9008 8b984ce4 c000023e tcpip!IppDeliverListToProtocol+0x49
8b984cb0 83473560 834c8c90 00000011 8b984ce4 tcpip!IppProcessDeliverList+0x2a
8b984d08 83457e95 834c8c90 00000011 82d1a13c tcpip!IppReceiveHeaderBatch+0x1eb
8b984d30 82e25865 8692b4b8 004c8c90 855ab2d8 tcpip!IppLoopbackTransmit+0x52
8b984d44 82cbde22 872035a0 00000000 855ab2d8 nt!IopProcessWorkItem+0x23
8b984d7c 82dedc42 872035a0 d7ace31c 00000000 nt!ExpWorkerThread+0xfd
8b984dc0 82c56efe 82cbdd25 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
HdFwLH+5979
937d8979 ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: HdFwLH+5979
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: HdFwLH
IMAGE_NAME: HdFwLH.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 480805fe
FAILURE_BUCKET_ID: 0xD1_CODE_AV_NULL_IP_HdFwLH+5979
BUCKET_ID: 0xD1_CODE_AV_NULL_IP_HdFwLH+5979
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: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 00000000, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d4f868
Unable to read MiSystemVaType memory at 82d2f420
00000000
CURRENT_IRQL: 2
FAULTING_IP:
+65ce952f021bdce8
00000000 ?? ???
PROCESS_NAME: System
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
TRAP_FRAME: 8b9848bc -- (.trap 0xffffffff8b9848bc)
ErrCode = 00000010
eax=87d3a510 ebx=00000000 ecx=00000000 edx=00000000 esi=87d3a630 edi=8b984a90
eip=00000000 esp=8b984930 ebp=8b984aa8 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
00000000 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from 00000000 to 82c65fb9
FAILED_INSTRUCTION_ADDRESS:
+65ce952f021bdce8
00000000 ?? ???
STACK_TEXT:
8b9848bc 00000000 badb0d00 00000000 87c43018 nt!KiTrap0E+0x2e1
WARNING: Frame IP not in any known module. Following frames may be wrong.
8b98492c 937d8979 00000000 00000016 8b984b44 0x0
8b984aa8 936fe426 87d3a510 00000016 8b984b44 HdFwLH+0x5979
8b984bd0 83478b03 8766e5d0 8b984bf0 85fe2244 tdx!TdxEventReceiveMessagesTransportAddress+0x48e
8b984c08 83473eb3 00000000 00000001 00000000 tcpip!UdpDeliverDatagrams+0x23b
8b984c54 83473f00 87203b38 00d83b80 8b984c90 tcpip!UdpReceiveDatagrams+0x112
8b984c64 834736e3 8b984c78 c000023e 00000000 tcpip!UdpNlClientReceiveDatagrams+0x12
8b984c90 83473110 834c9008 8b984ce4 c000023e tcpip!IppDeliverListToProtocol+0x49
8b984cb0 83473560 834c8c90 00000011 8b984ce4 tcpip!IppProcessDeliverList+0x2a
8b984d08 83457e95 834c8c90 00000011 82d1a13c tcpip!IppReceiveHeaderBatch+0x1eb
8b984d30 82e25865 8692b4b8 004c8c90 855ab2d8 tcpip!IppLoopbackTransmit+0x52
8b984d44 82cbde22 872035a0 00000000 855ab2d8 nt!IopProcessWorkItem+0x23
8b984d7c 82dedc42 872035a0 d7ace31c 00000000 nt!ExpWorkerThread+0xfd
8b984dc0 82c56efe 82cbdd25 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
HdFwLH+5979
937d8979 ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: HdFwLH+5979
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: HdFwLH
IMAGE_NAME: HdFwLH.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 480805fe
FAILURE_BUCKET_ID: 0xD1_CODE_AV_NULL_IP_HdFwLH+5979
BUCKET_ID: 0xD1_CODE_AV_NULL_IP_HdFwLH+5979
Followup: MachineOwner
---------
肥嘟嘟左卫门
