这些东西我真的不懂
不过在学校里是用iNode软件上网的，不是直接连接宽带
回家里改卫直接连接宽带了
不知道这是不是完整分析：
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: 00000008, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 87c2d85f, address which referenced memory
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
Unable to open image file: C:\Program Files\Debugging Tools for Windows (x86)\sym\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
ϵͳÕÒ²»µ½Ö¸¶¨µÄÎļþ¡£
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: pacer
FAULTING_MODULE: 81a04000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 47f6d426
WRITE_ADDRESS: 00000008
CURRENT_IRQL: 0
FAULTING_IP:
ndis!ndisXlateSendCompleteNetBufferListToPacket+36
87c2d85f c7400836434f4d mov dword ptr [eax+8],4D4F4336h
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from 87c2d85f to 81a5ed24
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8a1fee68 87c2d85f badb0d00 84e81a18 00000000 nt+0x5ad24
8a1feee4 87cd55fe 842d67b8 8a1fef04 8a1fef14 ndis!ndisXlateSendCompleteNetBufferListToPacket+0x36
8a1fef08 87cd441e 83feb008 00000000 00000001 ndis!ndisMSendNetBufferListsCompleteToNdisPackets+0x56
8a1fef3c 87c094f1 85ae70e8 842d67b8 00000001 ndis!ndisMSendCompleteNetBufferListsInternal+0xb8
8a1fef50 87be20ee 874015c0 842d67b8 00000001 ndis!NdisFSendNetBufferListsComplete+0x1a
8a1fef74 87cd44dd 87401318 00000000 00000001 pacer!PcFilterSendNetBufferListsComplete+0xba
8a1fef94 87f84175 85ae70e8 842d67b8 00000001 ndis!NdisMSendNetBufferListsComplete+0x70
8a1fefc8 87f7fbf5 00000000 00000000 00000000 Rtlh86+0x6175
8a1feff0 87f806e4 02c34690 00000000 00000000 Rtlh86+0x1bf5
8a1ff00c 87cd45c4 84c34690 842d67b8 00000000 Rtlh86+0x26e4
8a1ff034 87c09585 85ae70e8 842d67b8 00000000 ndis!ndisMSendNBLToMiniport+0xb4
8a1ff054 87c095a8 842d67b8 842d67b8 00000000 ndis!ndisFilterSendNetBufferLists+0x8b
8a1ff06c 87be24ab 874015c0 842d67b8 00000000 ndis!NdisFSendNetBufferLists+0x18
8a1ff0e8 87c09638 872ee980 002d67b8 00000000 pacer!PcFilterSendNetBufferLists+0x233
8a1ff104 87c31d9b 842d67b8 842d67b8 00000000 ndis!ndisSendNBLToFilter+0x87
8a1ff144 87c31cc7 85ae70e8 001ff1a8 00000001 ndis!ndisMSendPacketsToNetBufferLists+0x92
8a1ff180 87cd56db 83feb008 8a1ff1a8 00000001 ndis!ndisSendPacketsWithPause+0x236
8a1ff19c 8cbcffad 83feb008 84e81a18 83aa3008 ndis!ndisSendWithPause+0x48
8a1ff1b8 8cbcb654 9995c4f8 842cf870 85c310e8 raspppoe!PrSend+0x49
8a1ff1dc 87cd5299 83fc4018 00000001 83ffd900 raspppoe!MpWanSend+0x112
8a1ff200 8cbbc746 872e8958 00000001 83ffd900 ndis!ndisMWanSend+0x110
8a1ff22c 8cbbcf91 00000000 83feb888 00000001 ndiswan!SendOnLegacyLink+0x102
8a1ff298 8cbbd247 0000000e 83fa2828 83ffd8a0 ndiswan!FramePacket+0x35a
8a1ff2d0 8cbbd47b 83feb888 00000000 8a1ff304 ndiswan!SendFromProtocol+0xbb
8a1ff310 8cbbdc61 01feb888 8cbc2000 00000000 ndiswan!SendPacketOnBundle+0x17c
8a1ff338 8cbb6f29 872e7e10 00000000 84cf5d58 ndiswan!NdisWanQueueSend+0x4fa
8a1ff354 87cd78e1 872e7e10 8a1ff39c 00000001 ndiswan!MPSendPackets+0x54
8a1ff37c 87cd7707 8a1ff3a0 8a1ff39c 00000001 ndis!ndisMSendPacketsXToMiniport+0x141
8a1ff3e4 87c09585 85c2e0e8 8433de88 00000000 ndis!ndisMSendNetBufferListsToPackets+0x84
8a1ff404 87c095a8 8433de88 8433de88 00000000 ndis!ndisFilterSendNetBufferLists+0x8b
8a1ff41c 87be24ab 871b9190 8433de88 00000000 ndis!NdisFSendNetBufferLists+0x18
8a1ff498 87c09638 83fec008 0133de88 00000000 pacer!PcFilterSendNetBufferLists+0x233
8a1ff4b4 87cd464a 8433de88 8433de88 00000000 ndis!ndisSendNBLToFilter+0x87
8a1ff4d8 8d420969 8740c960 8433de88 00000000 ndis!NdisSendNetBufferLists+0x4f
8a1ff520 87e67d8c 9997af10 00000000 8a1ff6b4 wanarp!WanIpSendPackets+0x193
8a1ff560 87e6799b 87eccc68 00000000 00000000 tcpip!IppFragmentPackets+0x201
8a1ff598 87e6978b 87eccc68 8a1ff6b4 616c7049 tcpip!IppDispatchSendPacketHelper+0x252
8a1ff638 87e68bff 001ff6b4 00000000 8474c318 tcpip!IppPacketizeDatagrams+0x8fd
8a1ff798 87e61cab 00000000 00000004 87eccc68 tcpip!IppSendDatagramsCommon+0x5f9
8a1ff7b8 87e62b19 84dd2878 8a1ff8b4 843204e0 tcpip!IpNlpSendDatagrams+0x4b
8a1ffa00 87b9682f 85b074e0 84dd28a8 842cbfa0 tcpip!UdpSendMessages+0xc07
8a1ffa18 87bb3f80 843204e0 8a1ffa30 843204e0 afd!AfdTLSendMessages+0x27
8a1ffa68 87bb3d87 843204e0 842cbfa0 0da58c94 afd!AfdTLFastDgramSend+0x7d
8a1ffae4 87ba93d0 843204e0 8a1ffb7c 000000e6 afd!AfdFastDatagramSend+0x5ac
8a1ffc58 81c5098e 84290d01 00000001 0d0df508 afd!AfdFastIoDeviceControl+0x3c1
8a1ffd00 81c3aa5d 872da448 0000027c 00000000 nt+0x24c98e
8a1ffd34 81a5ba1a 00000280 0000027c 00000000 nt+0x236a5d
8a1ffd64 77a69a94 badb0d00 0d0df4c8 00000000 nt+0x57a1a
8a1ffd68 badb0d00 0d0df4c8 00000000 00000000 0x77a69a94
8a1ffd6c 0d0df4c8 00000000 00000000 00000000 0xbadb0d00
8a1ffd70 00000000 00000000 00000000 00000000 0xd0df4c8
STACK_COMMAND: kb
FOLLOWUP_IP:
pacer!PcFilterSendNetBufferListsComplete+ba
87be20ee 5b pop ebx
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: pacer!PcFilterSendNetBufferListsComplete+ba
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: pacer.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
