积极答复者
win7频繁蓝屏请高手帮忙看看

问题
-
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\huangling\Desktop\022711-21606-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: C:\temp;SRV*c:\temp*http://msdl.microsoft.com/download/symbols
Executable search path is:
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 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x8443a000 PsLoadedModuleList = 0x84584850
Debug session time: Sun Feb 27 20:47:59.235 2011 (UTC + 8:00)
System Uptime: 0 days 0:04:19.265
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
.Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\system32\DRIVERS\nwifi.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nwifi.sys
*** ERROR: Module load completed but symbols could not be loaded for nwifi.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************Use !analyze -v to get detailed debugging information.
- 已编辑 huangling2000 2011年2月27日 13:59
答案
-
这是我的电脑的配置
常规
电脑: 技嘉 945PL-S3P 台式电脑
操作系统: Windows 7 旗舰版 ( 32位 / SP1 / DirectX 11 )
硬件
处理器: 英特尔 Pentium(奔腾) D 2.80GHz 双核
主板: 技嘉 945PL-S3P ( 英特尔 945G - ICH7 Family )
芯片组: 英特尔 945G - ICH7 Family
内存: 2 GB ( 金邦 DDR2 800MHz )
主硬盘: 希捷 ST3500630NS ( 500 GB )
显卡: Nvidia GeForce GTX 460 ( 1 GB / 索泰 )
显示器: 惠普 HWP26FC HP L2245w ( 22 英寸 )
声卡: 瑞昱 ALC888 @ 英特尔 82801G(ICH7) 高保真音频
网卡: Atheros AR5007UG Wireless Network Adapter- 已编辑 huangling2000 2011年2月27日 13:58
- 已标记为答案 Shirley Long 2011年3月31日 9:12
-
我看了一下你上传的dump中的第一个,发现了如下的结果:
1: 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: 00000000, Machine Check Exception
Arg2: 8e4cb1e4, Address of the WHEA_ERROR_RECORD structure.
Arg3: b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 1040080f, Low order 32-bits of the MCi_STATUS value.Debugging Details:
------------------
BUGCHECK_STR: 0x124_GenuineIntelCUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 1f
上网查了一下,很大可能性是主板不稳定。有人说换过主板就好了。(当然,我只看了第一个。)
- 已建议为答案 Rein XuModerator 2011年3月29日 12:16
- 已标记为答案 Shirley Long 2011年3月31日 9:13
全部回复
-
这是我的电脑的配置
常规
电脑: 技嘉 945PL-S3P 台式电脑
操作系统: Windows 7 旗舰版 ( 32位 / SP1 / DirectX 11 )
硬件
处理器: 英特尔 Pentium(奔腾) D 2.80GHz 双核
主板: 技嘉 945PL-S3P ( 英特尔 945G - ICH7 Family )
芯片组: 英特尔 945G - ICH7 Family
内存: 2 GB ( 金邦 DDR2 800MHz )
主硬盘: 希捷 ST3500630NS ( 500 GB )
显卡: Nvidia GeForce GTX 460 ( 1 GB / 索泰 )
显示器: 惠普 HWP26FC HP L2245w ( 22 英寸 )
声卡: 瑞昱 ALC888 @ 英特尔 82801G(ICH7) 高保真音频
网卡: Atheros AR5007UG Wireless Network Adapter- 已编辑 huangling2000 2011年2月27日 13:58
- 已标记为答案 Shirley Long 2011年3月31日 9:12
-
BugCheck D1, {400001c, 2, 0, a01b87b4}
*** 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 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 afd.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
*** WARNING: Unable to verify timestamp for Hookport.sys
*** ERROR: Module load completed but symbols could not be loaded for Hookport.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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : nwifi.sys ( nwifi+87b4 )Followup: MachineOwner
--------- -
有高手帮忙看下嘛??什么问题造成的有解决方案吗?dmp文件在这个链接里下载:http://cid-f14873861c26aee1.office.live.com/self.aspx/%e5%85%ac%e5%85%b1%e6%96%87%e4%bb%b6%e5%a4%b9/Minidump.rar
-
我看了一下你上传的dump中的第一个,发现了如下的结果:
1: 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: 00000000, Machine Check Exception
Arg2: 8e4cb1e4, Address of the WHEA_ERROR_RECORD structure.
Arg3: b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 1040080f, Low order 32-bits of the MCi_STATUS value.Debugging Details:
------------------
BUGCHECK_STR: 0x124_GenuineIntelCUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 1f
上网查了一下,很大可能性是主板不稳定。有人说换过主板就好了。(当然,我只看了第一个。)
- 已建议为答案 Rein XuModerator 2011年3月29日 12:16
- 已标记为答案 Shirley Long 2011年3月31日 9:13
-
几点建议: 1、通过执行AIDA64稳定性测试等项目确定硬件可靠性; 2、尝试暂时性移除(虽然我更建议永久移除360嗯)防护软件并观察问题是否仍然存在
你的方法我试过了,AIDA64不怎么会用反馈的信息太多了,找半天也没看见自己需要的信息,接着就移除了360安全卫士,但是360的杀毒我没卸载,问题依旧频繁蓝屏,接着又拔掉了无线网卡,卸载了驱动还是随机蓝屏.已经不知该怎么办解决了,可能真的像楼下的朋友说的,可能主板不稳定吧.请问还有朋友有建设性意见吗?