![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
蓝屏（Blue Screen）错误可能是Windows系统中比较常见的一种错误。而且对于我们大多数人来说，发生蓝屏之后可能就束手无策了。这里介绍一些发生蓝屏错误时的一些办法。办法很多，但是今天这部分，主要介绍如何用Windows Debugging Tool，或者叫Windbg，结合微软的论坛来处理问题的办法。
首先，要用WinDBG处理蓝屏问题，要确保系统有生成内存转储文件。
确认存在内存转储文件
默认配置的Windows 7，生成的可能是核心转储文件（Kernal Memory Dump）或是小内存转储文件（Minidump）。如果是核心转储文件，默认会存为C:\Windows\Memory.dmp，如果是小内存转储文件，相关文件会保存在C:\Windows\MiniDump目录下面。
所以，出现蓝屏后，请检查系统中有没有C:\Windows\Memory.dmp这个文件，或者是C:\Windows\MiniDump目录下面按照日期命名的文件。比如，Mini010810-01.dmp就是2010年1月8日的第一个小内存转储文件。
如果没有相应的内存转储文件，请参考有关文档。
安装Windows Debugging Tool （WinDBG）
接下来，我们要安装Windbg了。WinDBG可以在微软网站下载，32位的地址是http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx ，64位的地址是http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx 。注意WinDBG只有英文版的。你只要到这两个地方找一个最新的版本下载安装就可以了。如果你不是很懂英语，那就直接到这两个地址下载：32位：http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi，64位：
http://msdl.microsoft.com/download/symbols/debuggers/dbg_amd64_6.11.1.404.msi
http://msdl.microsoft.com/download/symbols/debuggers/dbg_ia64_6.11.1.404.msi。然后一路Next安转就可以了。WinDBG安转文件大小，大概在15-30兆左右。
配置Windows Debugging Tool （WinDBG）
在用WinDBG分析内存转储文件之前，我们要配置一下WinDBG。
首先，选一个临时目录存放Symbol文件。比如，建立一个目录叫C:\Temp
然后，打开WinDBG，在File菜单-〉选择Symbol File Path。在打开的对话框里输入：
SRV*c:\temp*http://msdl.microsoft.com/download/symbols
选择OK确定。WinDBG就配置好了。
用Windows Debugging Tool （WinDBG）分析内存转储文件
在WinDBG里面，在File菜单，选择Open Crash Dump，然后找到前面说的那个核心内存转储文件或者小内存转储文件，选择打开。等待一会儿，如果需要从微软网站下载Symbole文件的话，时间可能会比较长。如果不出现大量Warning，就说明设置是成功的。如果出现Your debugger is not using the correct symbols 之类的信息，说明配置有问题，到上一步再仔细检查一下。
一直等到出现Use !analyze -v to get detailed debugging information.字样和0: kd>提示符。
按照提示，输入!analyze -v命令。等待命令执行完成。
分析Windows Debugging Tool（WinDBG）结果
如果你的英文有一定基础，!analyze -v命令可能就告诉你很多信息了。如果看的不是很明白，就把结果贴出来让热心的网友给你分析一下吧。
http://shower-thunder.spaces.live.com/blog/cns!250DE47BD119587C!131.entry
锁定的问题。 此问题已从 Microsoft 支持社区迁移。 你可投票决定它是否有用，但不能添加评论或回复，也不能关注问题。
您好，
从您提供的蓝屏信息中可以查看到是由于EagleX64.sys、KartRider.exe文件导致的。
错误代码: 0x00000019，表示磁盘驱动器在磁盘找不到持定的扇区或磁道。
Eaglex64.sys 是安博士杀毒软件，可能是游戏自带的安全软件也有可能是您安装的该软件。
KartRider.exe是跑跑卡丁车这款游戏的进程，可能是该软件不兼容当前系统或与电脑上安装的应用软件存在冲突（特别是杀毒软件）。
建议您暂时卸载掉电脑上的安全防护类软件再确认问题（您安装了360和迅雷之类的应用了）。
这是我的查看结果 帮我分析一下 谢谢！！！！
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\100810-16005-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff80004655000 PsLoadedModuleList = 0xfffff80004892e50
Debug session time: Fri Oct 8 13:50:04.743 2010 (GMT+8)
System Uptime: 0 days 0:36:21.320
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.........
Unable to load image \SystemRoot\system32\drivers\Wdf01000.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Wdf01000.sys
*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000B8, {fffffa8006cfbb60, fffffa800187a060, 0, 0}
***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : Wdf01000.sys ( Wdf01000+843e0 )
Followup: MachineOwner
帮帮忙
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa800898f028, f6000480, 40150}
Probably caused by : hardware
Followup: MachineOwner
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800898f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f6000480, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000040150, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: setup.exe
CURRENT_IRQL: f
STACK_TEXT:
fffff8800496cb58 fffff80004805903 : 0000000000000124 0000000000000000 fffffa800898f028 00000000f6000480 : nt!KeBugCheckEx
fffff8800496cb60 fffff8000439d593 : 0000000000000001 fffffa8008942280 0000000000000000 fffffa80089422d0 : hal!HalBugCheckSystem+0x1e3
fffff8800496cba0 fffff800048055c8 : 0000000000000728 fffffa8008942280 fffff8800496cf30 fffff8800496cf00 : nt!WheaReportHwError+0x263
fffff8800496cc00 fffff80004804f1a : fffffa8008942280 fffff8800496cf30 fffffa8008942280 0000000000000000 : hal!HalpMcaReportError+0x4c
fffff8800496cd50 fffff80004804dd5 : 0000000000000008 0000000000000001 fffff8800496cfb0 0000000000000000 : hal!HalpMceHandler+0x9e
fffff8800496cd90 fffff800047f8e88 : fffff900c20e9650 fffff88003507b18 0000000000000000 0000000000000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff8800496cdc0 fffff80004285fec : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : hal!HalHandleMcheck+0x40
fffff8800496cdf0 fffff80004285e53 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KxMcheckAbort+0x6c
fffff8800496cf30 fffff960002c3574 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x153
fffff88003507a68 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : win32k!HwndLookupCompareTableData+0x8
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
Followup: MachineOwner
帮帮我呀
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 92a56d5b, The address that the exception occurred at
Arg3: 80c1382c, Trap Frame
Arg4: 00000000
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
FAULTING_IP:
+12a
92a56d5b ac lods byte ptr [esi]
TRAP_FRAME: 80c1382c -- (.trap 0xffffffff80c1382c)
ErrCode = 00000000
eax=84a80060 ebx=80c13950 ecx=849148c8 edx=00000000 esi=00000000 edi=820c173d
eip=92a56d5b esp=80c138a0 ebp=80c1393c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
92a56d5b ac lods byte ptr [esi] ds:0023:00000000=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8222849d to 92a56d5b
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
80c1393c 8222849d 00000000 80c13a40 00000000 0x92a56d5b
80c139a0 821e9363 80c139fc 80001a14 00000081 nt!PfpOpenHandleCreate+0xc5
80c13a18 821e9552 80c13aec b724b488 00000000 nt!PfpFileBuildReadSupport+0x93
80c13aac 821e9b51 00c13aec 80c13be4 00000001 nt!PfpPrefetchFilesTrickle+0xdf
80c13b00 821e9dee b724a000 e2d02230 80c13bf8 nt!PfpPrefetchRequestPerform+0x295
80c13b54 822098d2 80c13be4 94493701 e2d0257c nt!PfpPrefetchRequest+0x16e
80c13c18 822039b1 025df9e4 00000014 94493701 nt!PfSetSuperfetchInformation+0x182
80c13d50 820a69aa 0000004f 00000000 00000014 nt!NtSetSystemInformation+0x908
80c13d50 77045e74 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
025df9fc 00000000 00000000 00000000 00000000 0x77045e74
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!PfpOpenHandleCreate+c5
8222849d 3bc3 cmp eax,ebx
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!PfpOpenHandleCreate+c5
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c0e5573
FAILURE_BUCKET_ID: 0x8E_nt!PfpOpenHandleCreate+c5
BUCKET_ID: 0x8E_nt!PfpOpenHandleCreate+c5
Followup: MachineOwner
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*c:\temp*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x8444e000 PsLoadedModuleList = 0x84596810
Debug session time: Sun Oct 24 02:59:41.928 2010 (GMT+8)
System Uptime: 0 days 1:05:48.631
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {2, 2, 1, 83873afd}
*** ERROR: Module load completed but symbols could not be loaded for 360netmon.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwl6.sys
Probably caused by : nwifi.sys ( nwifi!IoctlCheckAdapter+613 )
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: 00000002, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 83873afd, address which referenced memory
Debugging Details:
WRITE_ADDRESS: 00000002
CURRENT_IRQL: 2
FAULTING_IP:
nwifi!IoctlCheckAdapter+613
83873afd 8901 mov dword ptr [ecx],eax
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: a8a6f794 -- (.trap 0xffffffffa8a6f794)
ErrCode = 00000002
eax=86f3b0d0 ebx=00000000 ecx=00000002 edx=00000000 esi=8a597cc8 edi=8387572d
eip=83873afd esp=a8a6f808 ebp=a8a6f824 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
nwifi!IoctlCheckAdapter+0x613:
83873afd 8901 mov dword ptr [ecx],eax ds:0023:00000002=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 83873afd to 8449482b
STACK_TEXT:
a8a6f794 83873afd badb0d00 00000000 8389e4c8 nt!KiTrap0E+0x2cf
a8a6f824 8a4a8adc 89766000 00000002 00000000 nwifi!IoctlCheckAdapter+0x613
a8a6f83c 92809af3 894235a8 86f3b0d0 00000000 ndis!NdisFReturnNetBufferLists+0x4c
a8a6f85c 92809b87 897bee00 86f3b0d0 00000001 vwififlt!FilterReturnNetBufferListsCommon+0x67
a8a6f880 8a4a8adc 897be448 86f3b0d0 00000000 vwififlt!FilterReturnNetBufferLists+0x55
a8a6f898 8a595d7d 89b88548 86f3b0d0 00000000 ndis!NdisFReturnNetBufferLists+0x4c
WARNING: Stack unwind information not available. Following frames may be wrong.
a8a6f8ac 83874837 89b88548 86f3b0d0 00000000 360netmon+0x4d7d
a8a6f8d4 83878497 89b88548 897bee50 897bee00 nwifi!Dot11IndicateRecvPackets+0x51
a8a6f8f4 8a4a8a87 89b84a00 86f3b0d0 00000000 nwifi!Pt6Receive+0x1d3
a8a6f910 8a4a8a21 894235a8 a147af00 00000000 ndis!ndisFilterIndicateReceiveNetBufferLists+0x46
a8a6f92c 92809c85 894235a8 a147af00 00000000 ndis!NdisFIndicateReceiveNetBufferLists+0x2f
a8a6f958 8a4cda2e 897be454 a147af00 00000000 vwififlt!FilterReceiveNetBufferLists+0xcf
a8a6f980 8a478c1e 895e70e0 a147af00 00000000 ndis!ndisMIndicateReceiveNetBufferListsInternal+0x62
a8a6f9a8 8a595d44 895e70e0 a147af00 00000000 ndis!NdisMIndicateReceiveNetBufferLists+0x52
a8a6f9d8 8361fa61 895e70e0 a147af00 00000000 360netmon+0x4d44
a8a6fa60 83640442 00000001 893763d8 00000000 bcmwl6+0x1ea61
a8a6fab0 8364442f 897764d8 86a204a8 00000000 bcmwl6+0x3f442
a8a6fb64 83645e60 897764d8 86a204a8 a8a6fbac bcmwl6+0x4342f
a8a6fc30 836473f5 897764d8 8941ce58 898ae0ac bcmwl6+0x44e60
a8a6fc58 836623f2 e07764d8 898ae7a8 897764d8 bcmwl6+0x463f5
a8a6fc7c 8366327e ffffffff 89766000 89766000 bcmwl6+0x613f2
a8a6fca4 83610e3f 007764d8 00000000 895d8bb8 bcmwl6+0x6227e
a8a6fcc4 8361ad1e 89766000 894d1a48 895e7028 bcmwl6+0xfe3f
a8a6fcdc 8a47830a 895d8bb8 893200c8 a8a6fd00 bcmwl6+0x19d1e
a8a6fcec 8466e815 895e7028 893200c8 871052c8 ndis!ndisDispatchIoWorkItem+0xf
a8a6fd00 844bbf3b 894d1a48 00000000 871052c8 nt!IopProcessWorkItem+0x23
a8a6fd50 8465c6d3 80000000 b781c0b8 00000000 nt!ExpWorkerThread+0x10d
a8a6fd90 8450e0f9 844bbe2e 80000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
nwifi!IoctlCheckAdapter+613
83873afd 8901 mov dword ptr [ecx],eax
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nwifi!IoctlCheckAdapter+613
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nwifi
IMAGE_NAME: nwifi.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc89f
FAILURE_BUCKET_ID: 0xD1_nwifi!IoctlCheckAdapter+613
BUCKET_ID: 0xD1_nwifi!IoctlCheckAdapter+613
Followup: MachineOwner
