win7系统每天启动都要蓝屏几次才能正常使用，这是什么情况？？
本帖最后由 e5210809 于 2012-6-1 21:03 编辑win7系统每天启动都要蓝屏，然后就自动重启
这样重复几次，才可以正常使用！
检查了硬件也没有哪里坏，但是系统也是重新做的！
现在就搞不明白了！ 驱动问题吧。 先测试内存依次显卡、芯片、电源，最后主板········蓝屏内存的机率最大。 我也是用的XP系统。但是没有遇到你的情况啊 这个系统我没用过，相信这个论坛里的人也没有人用过，所以蓝屏就很正常了。 本帖最后由 4667028aa 于 2012-6-1 21:35 编辑
和你的内存有直接关系！！！！换内存吧
en .就是WIN7，，，我测试过硬件没问题。原来是双内存。后来坏了。就买了对新的换上
然后用不了一个月又坏了个。现在一直单内存！！！反正启动的时候都要蓝屏几次才正常！
要说驱动的话我都重新装系统了怎么还这样！！ 你的内存为什么坏的那么快? 不知道，我这人好像和内存有仇
以前那天电脑用了5年换了2次内存。别的没坏过
这次2年多了就换了次了。
我买的东西又不是杂牌！！主机就5000多！太衰了 先从系统开始排除 楼主你什么蓝屏代码 可能电脑缺钙，它说：补钙，我要蓝瓶的 蓝屏最下边有个0X000000XX这样的类似代码 你自己看看咯 Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File
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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x83e3c000 PsLoadedModuleList = 0x83f854d0
Debug session time: Wed May 30 22:40:47.579 2012 (GMT+8)
System Uptime: 0 days 0:00:41.124
*********************************************************************
* 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
.....
Unable to load image \SystemRoot\system32\DRIVERS\mv61xx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mv61xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv61xx.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {80000003, 89c2efb8, 83f639fc, 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 : mv61xx.sys ( mv61xx+1bfb8 )
Followup: MachineOwner
---------
上面的东西是在 C:\WINDOWS\Minidump\Mini010806-02.dmp
里面找的。我百度了下据说是上次蓝屏的记录，但是我不知道看。
是用windbg打开的！
拜托了。
你这个是系统问题，应该是打了补丁造成的蓝屏或者是主板驱动安装不正确。。。。。。。 尽量到主板的官网上下驱动，现在的主板太傲娇了 用安装版的WIN7吧，别用GHOST，补丁不可乱打噢。。。。。。
电脑型号 X86 兼容 台式电脑
操作系统 Windows 7 旗舰版 32位 SP1 ( DirectX 11 )
处理器 英特尔 酷睿2 四核 Q8200 @ 2.33GHz
主板 华硕 P5Q (英特尔 4 Series 芯片组 - ICH10R)
内存 2 GB ( 芝奇 DDR2 1000MHz )
主硬盘 希捷 ST3500418AS ( 500 GB / 7200 转/分 )
显卡 ATI Radeon HD 4850( 512 MB / HIS )
显示器 三星 SAM0274 SyncMaster ( 19.1 英寸 )
光驱 东芝-三星 DVD-ROM TS-H352D DVD光驱
声卡 ATI Radeon HD 48x0 Audio Device
网卡 鈺硕 AR8121/AR8113/AR8114 PCI-E Ethernet Adapter / 华硕
好像是3年前配的，也不知道现在算什么档次。不如果不是很爱玩游戏又必要升级什么的嘛？ 鲁大师哪里复制出来的。应该是有的吧！老式的。现在新内存好像不能插这个主板了 0x0000008E(等同于新式蓝屏表示代码 BCCode: 1000008E)
此错误可能的原因可能包括：
1.硬盘损坏
2.硬件配置问题
3.不兼容的软件
4.不兼容的驱动程序
5.操作系统内存在病毒
6.内存条不匹配或已损坏. (微软解释)
错误名称0x0000008E：KERNEL_MODE_EXCEPTION_NOT_HANDLED
故障分析0x0000008E错误表示内核程序遇到了问题，但Windows错误处理器无法准确捕获错误类型。这个错误的可能原因较多，一般遇到此错误时比较麻烦。 如果遇到0x0000008E错误，建议检查一下完整的蓝屏故障提示，看看有没有提到引起错误的具体是哪个文件，如果在蓝屏故障提示中看到某应用软件或某硬件设备驱动程序的文件名，问题一般与相应的应用软件或硬件设备有关;如果在蓝屏故障提示中没有显示引起错误的文件名,通常需要综合其它故障信息判断故障原因,建议检查一下Windows事件查看器,看看有没有相应的记录.
0x0000008E:KERNEL_MODE_EXCEPTION_NOT_HANDLED
◆错误分析:内核级应用程序产生了错误, 但Windows错误处理器没有捕获. 通常是硬件兼容性错误.
◇解决方案:升级驱动程序或升级BIOS.0x0000008E错误分析，度娘说的...........
页:
[1]