![](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和迅雷之类的应用了）。
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 86cd9510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 92584924, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000d, Optional internal context dependent data.
Debugging Details:
Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
FAULTING_IP:
atikmpag+5924
92584924 8bff mov edi,edi
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
9399db74 93155adb 00000116 86cd9510 92584924 nt!KeBugCheckEx+0x1e
WARNING: Stack unwind information not available. Following frames may be wrong.
9399db98 931568fa 92584924 00000000 0000000d dxgkrnl+0x8cadb
9399dbbc 9318692c 00000000 00000102 83548258 dxgkrnl+0x8d8fa
9399dc34 931b0a60 fffffcfb 000115ad 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
9399dc5c 931b1153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x96
9399dc98 9318d8f0 9399dc90 86a81828 8c1b3008 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
9399dd28 931b24b7 83548258 840903f1 83548258 dxgmms1!VidSchiScheduleCommandToRun+0xaa
9399dd3c 931b2573 83548258 00000000 8bb01d48 dxgmms1!VidSchiRun_PriorityTable+0xf
9399dd50 842626d3 83548258 8fd71235 00000000 dxgmms1!VidSchiWorkerThread+0x7f
9399dd90 841140f9 931b24f4 83548258 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
atikmpag+5924
92584924 8bff mov edi,edi
SYMBOL_NAME: atikmpag+5924
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4cef187b
FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys
BUCKET_ID: 0x116_IMAGE_atikmpag.sys
Followup: MachineOwner
麻烦帮忙分析一下 貌似是TDR侦测有问题
请高手帮忙看看，谢了
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000003, the pool freelist is corrupt.
Arg2: 87ae19c8, the pool entry being checked.
Arg3: 87ae19c7, the read back flink freelist value (should be the same as 2).
Arg4: 87ae19c8, the read back blink freelist value (should be the same as 2).
Debugging Details:
BUGCHECK_STR: 0x19_3
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 845698aa to 8456a996
STACK_TEXT:
84570960 845698aa 8457f8c0 00000000 8775b80c nt!ExDeferredFreePool+0x336
845709cc 844d2891 87a30008 00000000 00000064 nt!ExFreePoolWithTag+0x8a4
845709e8 8b8af3a0 878e0008 89cc6008 8b924a60 nt!RtlContractHashTable+0xb2
845709fc 8b8ac418 8b924a60 89cc6008 00000000 tcpip!IppRestructureHashTableUnderLock+0x49
84570a3c 8b8ac67e 00000000 00000000 89cc6008 tcpip!IppFlushNeighborSet+0x8a
84570ad4 8b8af60f 84570a7c 00000000 8b9196b4 tcpip!IppNeighborSetTimeout+0x159
84570af4 8b8aee91 89cc8560 8b913d00 00000000 tcpip!Ipv6pInterfaceSetTimeout+0xb2
84570b20 8b8ae952 8b916fa0 00000000 84570b7c tcpip!IppCompartmentSetTimeout+0x8a
84570b30 8b8ae93b 8b916fa0 844b404d 8b924b00 tcpip!IppProtocolTimeout+0xf
84570b38 844b404d 8b924b00 00000000 e68f47b0 tcpip!IppTimeout+0x4f
84570b7c 844b3ff1 84573d20 84570ca8 00000002 nt!KiProcessTimerDpcTable+0x50
84570c68 844b3eae 84573d20 84570ca8 00000000 nt!KiProcessExpiredTimerList+0x101
84570cdc 844b220e 0000befd c446c9c0 8457d280 nt!KiTimerExpiration+0x25c
84570d20 844b2038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
84570d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExDeferredFreePool+336
8456a996 cc int 3
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ExDeferredFreePool+336
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
FAILURE_BUCKET_ID: 0x19_3_nt!ExDeferredFreePool+336
BUCKET_ID: 0x19_3_nt!ExDeferredFreePool+336
Followup: Pool_corruption
我电脑上几个月蓝屏是好像8E还有7C，都是在看视频 还有下载的时候的，后来送去修也没测出，那些蓝屏文件也没了，拿回来一个多月也没蓝屏了，今天蓝屏是9C，能帮我分析吗？
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini110410-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: RV*c:\temp*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image 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 XP Kernel Version 2600 (Service Pack 3) MP (3 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d8000 PsLoadedModuleList = 0x805644c0
Debug session time: Thu Nov 4 20:39:53.609 2010 (GMT+8)
System Uptime: 0 days 8:06:55.418
Unable to load image 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
.................
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9C, {0, f7723050, b6004000, e000128}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+606ba )
Followup: MachineOwner
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 00000000
Arg2: f7723050
Arg3: b6004000
Arg4: 0e000128
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 ***
*** ***
*************************************************************************
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: nt
FAULTING_MODULE: 804d8000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4bd6ec86
BUGCHECK_STR: 0x9C_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
LAST_CONTROL_TRANSFER: from 80705bfb to 805386ba
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f7723028 80705bfb 0000009c 00000000 f7723050 nt+0x606ba
f7723154 80700c52 f771fd70 00000000 00000000 hal+0x5bfb
00000000 00000000 00000000 00000000 00000000 hal+0xc52
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+606ba
805386ba 5d pop ebp
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+606ba
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\102410-20576-01.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 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}
Unable to load image \SystemRoot\system32\DRIVERS\360netmon.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for 360netmon.sys
*** ERROR: Module load completed but symbols could not be loaded for 360netmon.sys
*** WARNING: Unable to verify timestamp for bcmwl6.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: GetPointerFromAddress: unable to read from 845b6718
Unable to read MiSystemVaType memory at 84596160
00000002
CURRENT_IRQL: 2
FAULTING_IP:
nwifi!IoctlCheckAdapter+613
83873afd 8901 mov dword ptr [ecx],eax
CUSTOMER_CRASH_COUNT: 1
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
0: kd> .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=????????
0: kd> lmvm nwifi
start end module name
83870000 838b6000 nwifi (pdb symbols) c:\temp\nwifi.pdb\5B124C39D9E84FE1937599CFBD1142B51\nwifi.pdb
Loaded symbol image file: nwifi.sys
Mapped memory image file: c:\temp\nwifi.sys\4A5BC89F46000\nwifi.sys
Image path: \SystemRoot\system32\DRIVERS\nwifi.sys
Image name: nwifi.sys
Timestamp: Tue Jul 14 07:51:59 2009 (4A5BC89F)
CheckSum: 00044C48
ImageSize: 00046000
File version: 6.1.7600.16385
Product version: 6.1.7600.16385
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.6 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: NWiFi.SYS
OriginalFilename: NWiFi.SYS
ProductVersion: 6.1.7600.16385
FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255)
FileDescription: NativeWiFi Miniport Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
