积极答复者
蓝屏，重启...求高手分析原因!正文附电脑硬件信息,minidump解析后信息.谢谢啦！
问题
-
电脑型号 联想 IdeaPad Y460 笔记本电脑
操作系统 Windows 7 家庭普通版 32位 ( DirectX 11 )
处理器 英特尔 Core i3 M 380 @ 2.53GHz 双核笔记本处理器
主板 联想 KL2 (英特尔 HM55 Express 芯片组)
内存 2 GB ( 镁光 DDR3 1067MHz )
主硬盘 西数 WDC WD5000BEVT-24A0RT0 ( 500 GB )
显卡 Nvidia GeForce GT 425M ( 1 GB / 联想 )
显示器 三星 SEC3049 ( 14.7 英寸 )
光驱 日立-LG DVDRAM GT30N DVD刻录机
声卡 瑞昱 ALC272 @ 英特尔 5 Series/3400 Series Chipset 高保真音频
网卡 博通 BCM57780 NetLink Gigabit Ethernet / 联想*********************************************************************
*********************************************************************
minidump下载地址：
http://cid-86662dba38806934.office.live.com/browse.aspx/.Documents?permissionsChanged=1&1
*********************************************************************
*********************************************************************
minidump用Debugging Tools for Windows分析结果如下：
Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\kk\Desktop\050711-20046-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\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Kernel base = 0x8463b000 PsLoadedModuleList = 0x84783810
Debug session time: Sat May 7 13:53:40.471 2011 (GMT+8)
System Uptime: 0 days 3:59:58.703
*********************************************************************
* 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\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
............................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.......
*** WARNING: Unable to verify timestamp for halmacpi.dll
*** ERROR: Module load completed but symbols could not be loaded for halmacpi.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {1000018, 2, 0, 846089e9}
*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
*** WARNING: Unable to verify timestamp for athr.sys
*** ERROR: Module load completed but symbols could not be loaded for athr.sys
*** WARNING: Unable to verify timestamp for vwififlt.sys
*** ERROR: Module load completed but symbols could not be loaded for vwififlt.sys
*** WARNING: Unable to verify timestamp for nwifi.sys
*** ERROR: Module load completed but symbols could not be loaded for nwifi.sys
*** WARNING: Unable to verify timestamp for pacer.sys
*** ERROR: Module load completed but symbols could not be loaded for pacer.sys
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for tdx.sys
*** ERROR: Module load completed but symbols could not be loaded for tdx.sys
*** WARNING: Unable to verify timestamp for nltdi.sys
*** ERROR: Module load completed but symbols could not be loaded for nltdi.sys
*** 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 afd.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Probably caused by : athr.sys ( athr+16584 )
Followup: MachineOwner
---------
答案
-
ATHR.SYS 引起的驱动程序故障，请重新安装 Atheros 网络适配器驱动程序。--Alexis Zhanghttp://mvp.support.microsoft.com/profile/jiehttp://blogs.itecn.net/blogs/alexis推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。本帖是回复帖，原帖作者是楼上的 "moonshine0.0"BugCheck A, {1000018, 2, 0, 846089e9}Probably caused by : athr.sys ( athr+16584 )
- 已标记为答案 Leo HuangModerator 2011年5月11日 7:27
