WIN8.1企业版，迅雷下载过程中突然蓝屏，请有条件的帮忙分析下蓝屏文件

yege0201

ren1989 发表于 2013-12-27 10:21
我的电脑也是默认设置的没有修改过，不过印象中有些蓝屏文件没有生成核心存储，以小内存存储在minidump里 ...

蓝屏过后我只是在启动时以及启动后的几分钟内觉得系统反应比以往迟缓一些~不过之后就没觉得了~

公司的电脑不敢轻易装最新系统~家里的电脑装了Win8.1~

有能力的话当然分析DUMP文件最好了~这样可以省去以后很多的麻烦~

可是WinDbg虽然专业但是瓶颈太高~而且一定要设置好Symbol不然分析不准确~

而傻瓜的工具虽然人人都可用~但是准确率却不那么尽如人意了~

唉~

ren1989

yege0201 发表于 2013-12-27 10:31
蓝屏过后我只是在启动时以及启动后的几分钟内觉得系统反应比以往迟缓一些~不过之后就没觉得了~

公司的 ...

恩，公司的电脑也是轻易不动系统的事情。刚好昨天蓝的是个人的电脑，感觉自己有些强迫症，不装就是心理不舒服，说的是就是symbol难设置，这次我把WDK8.1里的东东全给下载下来了，等下看看怎么设置

yege0201

ren1989 发表于 2013-12-27 10:41
恩，公司的电脑也是轻易不动系统的事情。刚好昨天蓝的是个人的电脑，感觉自己有些强迫症，不装就是心理不 ...

symbol可以配置在线的（随用随下）~也可以下载后配置成本地的~网上以搜索就有很多教程~

下载地址如下：
http://msdn.microsoft.com/en-us/windows/hardware/gg463028.aspx

下载时候一定要选对了平台~不然还是会出错~

如果有retail和checked两个版本的话~一般下载retail的就可以了~

ren1989

yege0201 发表于 2013-12-27 10:49
symbol可以配置在线的（随用随下）~也可以下载后配置成本地的~网上以搜索就有很多教程~

下载地址如下： ...

恩，谢谢提醒。我是直接在debug里设置关联的微软的symbol服务器里，不过提示有一个驱动的cnnctfy2的symbol文件没有找到，这驱动看文件名应该是我有的WIFI共享程序Connectify NDIS Driver的驱动，debug的结果提示可能是驱动NETIO.SYS的蓝屏的原因，这个驱动跟迅雷有关的就是迅雷下载会因为速度快和下载东西大，然后就是TCP的半开连接数过大与网卡驱动导致，下面是结果：

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


Loading Dump File [C:\Users\LH\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*D:\Program Files (x86)\Windows Kits\symbol*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*D:\Program Files (x86)\Windows Kits\symbol*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16452.x86fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0x8146d000 PsLoadedModuleList = 0x81666218
Debug session time: Fri Dec 27 00:20:12.894 2013 (UTC + 8:00)
System Uptime: 8 days 8:54:55.333
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80833000, 0, 0}

*** ERROR: Module load completed but symbols could not be loaded for cnnctfy2.sys
Probably caused by : NETIO.SYS ( NETIO!KfdDiagnoseEvent+76 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80833000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR:  0x7f_8

TSS:  00000028 -- (.tss 0x28)
eax=884ac702 ebx=00000200 ecx=00000001 edx=00000001 esi=81678120 edi=81678120
eip=814198b8 esp=82848fe8 ebp=82849024 iopl=0         nv up di ng nz ac pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010096
hal!KeQueryPerformanceCounter+0x8:
814198b8 53              push    ebx
Resetting default scope

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  1c

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from 814de96e to 814198b8

STACK_TEXT:  
82849024 814de96e 00000000 81678120 81678120 hal!KeQueryPerformanceCounter+0x8
82849074 814daced 8166bd58 00000002 80000000 nt!KiUpdateTimeAssist+0x26
828490c0 815e77a7 828491b4 ffd0e300 00000002 nt!KiUpdateTime+0x33
82849110 8141b4ae 814e836e 82849130 828492c8 nt!KeClockInterruptNotify+0x67
82849120 8142b993 00000002 000000d1 9a329aef hal!HalpTimerClockInterruptCommon+0x3e
82849120 814e836e 00000002 000000d1 9a329aef hal!HalpTimerClockInterrupt+0x1cb
828492c8 814fb00f 83e0aae0 00000019 00000000 nt!KeWaitForSingleObject+0x10e
82849368 814fab09 83e0aae0 00000000 83e0aad8 nt!KeExpandKernelStackAndCalloutInternal+0x4ef
82849380 81ef9e2d 81ef6903 82849400 00002400 nt!KeExpandKernelStackAndCalloutEx+0x1f
828493b4 89087ee5 82849400 0000002c 85345878 NETIO!KfdDiagnoseEvent+0x76
828496ac 8907e0e9 85345878 82849908 00000000 tcpip!IndicateDropAudit+0x4ca
828498d8 8903957b 828499fc 85345878 866d0b48 tcpip!ShimIndicateDiscard+0x91
82849918 8904b286 0000002c 828499fc 85345878 tcpip!WfpShimIndicateDiscardGeneral+0x53
82849948 8908db02 866d0b48 00000000 82849973 tcpip!WfpAleClassify+0xbe
82849b10 8908e615 8916bb78 00000002 00000011 tcpip!WfpAlepAuthorizeReceive+0xd3a
82849d2c 89084595 00000011 86910a18 84462020 tcpip!WfpAleAuthorizeReceive+0x2c7
82849e20 890860df 00000002 0000c124 0000539c tcpip!ProcessALEForTransportPacket+0x379
8284a260 89084d1c 0000c124 0000539c 84462020 tcpip!WfpProcessInTransportStackIndication+0x955
8284a2e4 890874bc 00000011 0000c124 0000539c tcpip!InetInspectReceiveDatagram+0xd4
8284a3a8 890868ec 00000000 00000000 853d9000 tcpip!UdpBeginMessageIndication+0x4f
8284a468 89083896 853d9000 8284a4bc 8284a4a4 tcpip!UdpDeliverDatagrams+0x11d
8284a52c 89083de5 8284a568 89083e2f 8284a54c tcpip!UdpReceiveDatagrams+0x1fc
8284a534 89083e2f 8284a54c 891730b0 89173314 tcpip!UdpNlClientReceiveDatagrams+0x12
8284a568 89081a89 00000011 00000000 891730b0 tcpip!IppDeliverListToProtocol+0x41
8284a5b0 89081007 8284a604 8284a5fc 8284a610 tcpip!IppProcessDeliverList+0x60
8284a638 890827c8 ffffffff 86daa008 8ddcc89c tcpip!IppReceiveHeaderBatch+0x1cd
8284a74c 89081e3e 81e1cf01 00000000 8284a7d4 tcpip!IppFlcReceivePacketsCore+0x776
8284a75c 8ddca12e 849e1998 866d0b48 81e1cf00 tcpip!IpFlcReceivePackets+0x15
8284a7d4 81e1f05f 0cabb1e4 86eb7018 00000000 wanarp!WanNdisReceivePackets+0x211
8284a83c 81e1cce9 00000000 00000001 00000002 ndis!ndisMIndicateNetBufferListsToOpen+0x21b
8284a88c 81e5955b 86953270 86eb7018 00000000 ndis!ndisMTopReceiveNetBufferLists+0xffff941d
8284a920 81e3d7b5 00000001 00000002 86953270 ndis!ndisInvokeNextReceiveHandler+0x26
8284a96c 81e1fa4a 86d83388 86eb7018 00000000 ndis!ndisFilterIndicateReceiveNetBufferLists+0x1dd48
8284a98c 8dcbb1e7 86d83388 86eb7018 00000000 ndis!NdisFIndicateReceiveNetBufferLists+0x28
8284a9cc 81e1ba63 86d03b68 86eb7018 00000000 pacer!PcFilterReceiveNetBufferLists+0xb9
8284aa20 81e275db 8dcbb12e 86d03b68 86eb7018 ndis!ndisCallReceiveHandler+0x2a4
8284aa40 814faea5 8284ab08 7804b949 00000002 ndis!ndisDataPathExpandStackCallback+0x24
8284aad0 814fab09 00001000 00000004 00000000 nt!KeExpandKernelStackAndCalloutInternal+0x385
8284aae8 81e2756d 81e275b7 8284ab08 00001000 nt!KeExpandKernelStackAndCalloutEx+0x1f
8284ab00 81e275ac 8284ab5c 86d03b68 8dcbb12e ndis!ndisExpandStack+0x11
8284ab28 81e59e2a 00000001 00000002 86d03b68 ndis!ndisExpandDataPathStack+0x39
8284abc4 81e3d7b5 00000001 00000002 86d83388 ndis!ndisInvokeNextReceiveHandler+0x8f6
8284ac10 81e1fa4a 8570ad38 86eb7018 00000000 ndis!ndisFilterIndicateReceiveNetBufferLists+0x1dd48
8284ac30 8dcecbba 8570ad38 86eb7018 00000000 ndis!NdisFIndicateReceiveNetBufferLists+0x28
WARNING: Stack unwind information not available. Following frames may be wrong.
8284ac58 8dceda22 85e25a68 00000000 840cc008 cnnctfy2+0x1bba
8284ac80 8dcec69e 85e25a68 840cc008 00000001 cnnctfy2+0x2a22
8284aca4 8dcec769 00e25a68 84530ce0 00000000 cnnctfy2+0x169e
8284accc 81e1ba63 85e25a68 00000000 00000000 cnnctfy2+0x1769
8284ad20 81e1b1bd 8dcec6bc 85e25a68 84530ce0 ndis!ndisCallReceiveHandler+0x2a4
8284ae14 97be989b 86953270 84530ce0 00000000 ndis!NdisMIndicateReceiveNetBufferLists+0x5cf
8284ae80 97bd5cbd 858be462 00000046 863858e0 ndiswan!IndicateRecvPacket+0x475
8284aea8 97be9bd7 858be460 00000048 863858e0 ndiswan!ApplyQoSAndIndicateRecvPacket+0x1b8
8284aee8 97be9e64 00000000 863858e0 85ff8008 ndiswan!ProcessPPPFrame+0x140
8284af00 97bd32fe 86e4bab8 863858e0 86787d40 ndiswan!ReceivePPP+0xbb
8284af44 81e54614 85a469e8 00000037 858be2b8 ndiswan!ProtoCoReceiveNetBufferListChain+0x359
8284af78 81e54889 8496fe60 858be2b8 00000001 ndis!ndisMCoIndicateReceiveNetBufferListsToNetBufferLists+0xb4
8284af90 9e40bdd8 8496fe60 858be2b8 00000001 ndis!NdisMCoIndicateReceiveNetBufferLists+0x18
8284b5ac 9e40fa1e 85ece920 00000001 86f088e0 raspppoe!MpRecvPacket+0x22b
8284b5ec 81e1f05f 85e4e600 86f088e0 00000000 raspppoe!PrReceiveNetBufferListChain+0x244
8284b654 81e659df 00000000 00000001 00000002 ndis!ndisMIndicateNetBufferListsToOpen+0x21b
8284b688 81e23b7d 86f088e0 86f088e0 00000002 ndis!ndisIndicateAllNetBufferLists+0x65
8284b6c8 81e5955b 8593f0e8 86f088e0 00000000 ndis!ndisMTopReceiveNetBufferLists+0x2b9
8284b75c 81e3d7b5 00000001 00000002 8593f0e8 ndis!ndisInvokeNextReceiveHandler+0x26
8284b7a8 81e1fa4a 86195c70 86f088e0 00000000 ndis!ndisFilterIndicateReceiveNetBufferLists+0x1dd48
8284b7c8 8dcecbba 86195c70 86f088e0 00000000 ndis!NdisFIndicateReceiveNetBufferLists+0x28
8284b7f0 8dceda22 86197778 00000000 84137008 cnnctfy2+0x1bba
8284b818 8dcec69e 86197778 84137008 00000001 cnnctfy2+0x2a22
8284b83c 8dcec769 00197778 85a69c48 00000000 cnnctfy2+0x169e
8284b864 81e1ba63 86197778 00000000 00000000 cnnctfy2+0x1769
8284b8bc 81e1b1bd 8dcec6bc 86197778 85a69c48 ndis!ndisCallReceiveHandler+0x2a4
8284b9b0 8eef3d3f 8593f0e8 85a69c48 00000000 ndis!NdisMIndicateReceiveNetBufferLists+0x5cf
8284bab4 8eee38f9 009c8000 859c8001 00000400 Rt630x86!MpHandleRecvIntPriVLanJumbo+0x7b5
8284bae8 81e1ec75 859c8001 00000000 8284bb28 Rt630x86!MPHandleInterrupt+0x2bd
8284bb68 814cc496 85a87aec 85a87ad8 00000000 ndis!ndisInterruptDpc+0x27a
8284bc20 814cc0a6 8284bc68 00000000 866e1040 nt!KiExecuteAllDpcs+0x216


STACK_COMMAND:  .tss 0x28 ; kb

FOLLOWUP_IP:
NETIO!KfdDiagnoseEvent+76
81ef9e2d 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  NETIO!KfdDiagnoseEvent+76

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  52158eda

BUCKET_ID_FUNC_OFFSET:  76

FAILURE_BUCKET_ID:  0x7f_8_NETIO!KfdDiagnoseEvent

BUCKET_ID:  0x7f_8_NETIO!KfdDiagnoseEvent

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x7f_8_netio!kfddiagnoseevent

FAILURE_ID_HASH:  {2da70781-d8bb-f757-2c67-70c9f5ae6914}

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

gemini09

ren1989 发表于 2013-12-27 10:02
谢谢帮忙了，图片上检测的结果是没有检测出什么驱动导致的吗？现在用的WIN8.1驱动程序基本上是微软update ...

没检测出什么驱动导致，应该是迅雷与8.1系统不兼容导致蓝屏了

ren1989

gemini09 发表于 2013-12-27 14:01
没检测出什么驱动导致，应该是迅雷与8.1系统不兼容导致蓝屏了

刚下载了win8.1的debug程序，是系统的一个网络驱动导致的，可能跟迅雷还有WIFI共享的几个驱动有关系，楼上是详细的debug信息

恋爱的夏娜

ren1989 发表于 2013-12-27 14:43
刚下载了win8.1的debug程序，是系统的一个网络驱动导致的，可能跟迅雷还有WIFI共享的几个驱动有关系，楼上 ...

迅雷不加载驱动吧？出问题的是网卡驱动本身啊。

ren1989

恋爱的夏娜 发表于 2013-12-27 19:05
迅雷不加载驱动吧？出问题的是网卡驱动本身啊。

不是迅雷的驱动，是本身网卡的驱动，但是跟迅雷的设置有关，还有说是下载速度过快，下载文件过大，蓝屏几率就上去了

恋爱的夏娜

ren1989 发表于 2013-12-27 22:09
不是迅雷的驱动，是本身网卡的驱动，但是跟迅雷的设置有关，还有说是下载速度过快，下载文件过大，蓝屏几 ...

我以前也是这种情况……现在似乎不是在这方面出问题就没太关注了。