none
又蓝屏了··大牛帮忙看一下·谢谢↖(^ω^)↗ RRS feed

  • 问题

  • 问题签名:
      问题事件名称: BlueScreen
      OS 版本: 6.0.6001.2.1.0.768.2
      区域设置 ID: 2052

    有关该问题的其他信息:
      BCCode: d1
      BCP1: 00000008
      BCP2: 00000002
      BCP3: 00000001
      BCP4: 87C2D85F
      OS Version: 6_0_6001
      Service Pack: 1_0
      Product: 768_1

    有助于描述该问题的文件:
      C:\Windows\Minidump\Mini080209-03.dmp
      C:\Users\Ernest\AppData\Local\Temp\WER-78920-0.sysdata.xml
      C:\Users\Ernest\AppData\Local\Temp\WERB0A8.tmp.version.txt

    2009年8月2日 8:37

答案

  • 我看了你以前的问题,应该是同样的蓝屏问题,你的网卡型号是什么?或者我帮你找,你重新安装网卡驱动试试。

    • 已标记为答案 程·alex 2009年8月4日 12:28
    2009年8月2日 8:47

全部回复

  • 请用windebug分析一下,把结果发上来,以便进一步分析.


    1、首先下载windebug
    http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
    2、 启动 windbg, windbg界面: file->symbol file path (ctrl+s) 输入:
    SRV*c:\temp*http://msdl.microsoft.com/download/symbols,然后确定
    3. windbg界面: file->open crash dump(ctrl+d),打开9. 打开例如C:\Windows\Minidump\Mini122208-01.dmp后,等待提示
    当出现 Use !analyze -v to get detailed debugging information. 字样后,在下面输入框
    !analyze -v
    4. 等待分析完毕,把结果发上来。
    2009年8月2日 8:42
  • 我看了你以前的问题,应该是同样的蓝屏问题,你的网卡型号是什么?或者我帮你找,你重新安装网卡驱动试试。

    • 已标记为答案 程·alex 2009年8月4日 12:28
    2009年8月2日 8:47
  • 你好!谢谢你的回复
    我的Minidump里有四个文件,分别是Mini070309-01.dmp   Mini080209-01.dmp   Mini080209-02.dmp   Mini080209-03.dmp
    但是我试图打开的时候,会提示没有权限打开
    至于我的网卡是Realtek RTL8101 Family PCI-E Fast Ethernet NIC (NDIS 6.0)

    2009年8月2日 9:08
  • 你的蓝屏问题是经常发生的吗?你到以下地址,并安装此网卡驱动:ftp://file12.mydrivers.com/netcard/realtek_rtl8168b_6225_vista.zip
    2009年8月2日 9:18
  • 你好!谢谢你的回复
    我的Minidump里有四个文件,分别是Mini070309-01.dmp   Mini080209-01.dmp   Mini080209-02.dmp   Mini080209-03.dmp
    但是我试图打开的时候,会提示没有权限打开
    至于我的网卡是Realtek RTL8101 Family PCI-E Fast Ethernet NIC (NDIS 6.0)

    需要管理員權限打開.

    開始菜單 - 所有程序  - Debugging Tools for Windows (x86) - WinDbg - 鼠標右鍵 - 需要 UAC 提升權限 - File 菜單 - Open Creash Dump... 菜單項 - 彈出打開文件對話框 - 定位到文件夾 C:\Windows\Minidump\  按照 BSOD 最新次序 建議打開文件 Mini080209-03.dmp, 待加載完成後按 !analyze -v 進行診斷分析

    另附:

    易宝典:Windows常见蓝屏故障分析(MVP 撰稿)
    http://support.microsoft.com/kb/972602/zh-cn
    Folding@Home
    2009年8月2日 9:33
  • 谢谢,我已经按你给的地址安装了驱动
    另外windebug的分析结果是:
    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

    2009年8月2日 15:39
  • 谢谢 分析的结果是:
    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

    2009年8月2日 15:41
  •  不是经常发生,以前在学校用的是校园网 最近一个月没有上网 今天把电脑拿回家连上宽带一段时间后就会蓝屏重启
    在学校快放假的时候重装过一次系统 应该还是网卡驱动的问题
    2009年8月2日 15:42
  • pacer.sys 是一個系統文件.

     pacer.sys这个文件的描述,谁知道?
    http://baike.360.cn/5028300/18178847.html

    雖然是該文件引起的藍屏, 但并不排除其與某個軟件有衝突造成的. 不知道你的校園網是否需要安裝特定的軟件才能上網?
    Folding@Home
    2009年8月2日 15:47
  • 建議你把完整的 BSOD 診斷報告貼上來.
    Folding@Home
    2009年8月2日 16:02
  • 這是依據你貼的部分 BSOD 診斷報告找到的相關帖子, 這個帖子可能并不適用於你所遇到的情況, 僅供參考.

    w500经常会蓝屏死,错误7f(问题初步已经找到,卡巴惹的祸)
    http://www.51nb.com/forum/viewthread.php?tid=729443
    Folding@Home
    2009年8月2日 16:05
  • 问题签名:
      问题事件名称: BlueScreen
      OS 版本: 6.0.6002.2.2.0.768.3
      区域设置 ID: 2052
    有关该问题的其他信息:
      BCCode: 1000008e
      BCP1: C0000005
      BCP2: 81C87073
      BCP3: 95C8BBA0
      BCP4: 00000000
      OS Version: 6_0_6002
      Service Pack: 2_0
      Product: 768_1
    有助于描述该问题的文件:
      C:\Windows\Minidump\Mini080109-01.dmp
      C:\Users\tianxiadiyitan\AppData\Local\Temp\WER-69953-0.sysdata.xml
      C:\Users\tianxiadiyitan\AppData\Local\Temp\WERA591.tmp.version.txt

    我也遇到这类问题,前几天重装系统后出现的,每天会有一两次,每次情况都可能跟上次不一样,重起,死机,蓝屏,以前重装系统就没这种情况,
    2009年8月2日 18:29
  • Pacer.sys 是新式的 NDIS 6.0 轻型筛选器驱动程序,用于监测Qos流量的。

    请把完整的分析报告贴出来,以进一步分析是否其它因素导致引起的。
    2009年8月2日 23:24
  • 这些东西我真的不懂
    不过在学校里是用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
    ---------

    2009年8月3日 2:49
  • 我在学校里是用iNode软件上网的
    回到家里是直接输入账号密码连接宽带的
    2009年8月3日 2:51
  • 建議你再把其他幾個 DMP 文件也進行分析, 看看藍屏原因是否都相同.
    Folding@Home
    2009年8月3日 4:18
  • 你已经安装了网卡驱动,建议再观察一些日子,如果没有再发生此蓝屏现象,估计就是网卡驱动引起的,而非其它因素。
    2009年8月3日 4:44
  • 嗯 我已经试过几天,没有再蓝屏了 非常感谢各位大牛!

    2009年8月4日 12:28
  • 呵呵, 不客氣.
    Folding@Home
    2009年8月4日 12:30