【求助】电脑经常蓝屏重启
e3-1231v3，华硕b85 pro gamer，索泰1060 6G，500W的长城电源，内存是一个8G一个4G的一起插的，硬盘一块240G的东芝的ssd，一块老的500G西数HDD，运行win7 64位sp1。之前用的一直好好的，一直到差不多上上周，wow小更新了一次以后，我玩wow的时候出现了死机现象，我重装过显卡驱动，重新插拔过显卡，内存，都不行，我又重装了系统。然后慢慢发现，不光是玩wow的时候会蓝屏，现在任何时刻都可能会蓝屏，我听广播刷网页看漫画的时候，或者dota2的时候，或者玩gal的时候，或者什么都没干的时候都出现过蓝屏。用鲁大师运行过压力测试，跑下来貌似也没什么问题。蓝屏的频率不固定，之前好几天没出现，但是今天一晚上又出现了三次。它蓝屏后，画面一闪就自动重启了，我都看不到蓝屏代码，然后重启以后又能正常使用，我实在搞不懂哪里可能有问题了，只能来请教一下各位菊苣，我贴一些蓝屏的信息吧，希望有头绪的帮忙支个招，谢谢。Microsoft (R) Windows Debugger Version 6.11.0001.404 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 ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`04256000 PsLoadedModuleList = 0xfffff800`044996d0
Debug session time: Wed Sep 21 23:46:10.495 2016 (GMT+8)
System Uptime: 0 days 0:01:33.354
*********************************************************************
* 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 ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff96000169006, fffff88008bcae60, 0}
Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 : win32k.sys ( win32k+99006 )
Followup: MachineOwner
---------
按照我那台破机的规律，
应该是内存松了。
欢迎界面都会蓝。
摆摆就好了。 Muarim 发表于 2016-9-22 03:25
按照我那台破机的规律，
应该是内存松了。
内存我换过插槽试过了，没用。总之我今天先把那根4G的拔下来了，再看看行不行。 ASDJKL 发表于 2016-9-22 04:33
换块硬盘多半能好
不是吧。我这块东芝q300端午节买的，才没用多久啊，而且扫描也没检查出坏块。 你这个符号表没下载完吧，建议直接把dump文件传到微软论坛，有人帮忙看 说起来我以前用技嘉的p43的时候经常会无故蓝屏 先把高级系统设置里的自动重启关掉吧 ASDJKL 发表于 2016-9-22 12:21
我想起来一个容易造成蓝屏的东西，win7以上的系统不开ahci好像挺容易蓝屏的，我以前就经常因为这个蓝屏 ...
开了achi的。虽然我是先ide装的系统，装好以后才改的achi，不过我之前一直这样用也没出过问题啊 kubikiri 发表于 2016-9-22 12:45
先把高级系统设置里的自动重启关掉吧
请问具体在哪里改设置呢？ sssfans 发表于 2016-9-22 13:37
请问具体在哪里改设置呢？
控制面板-系统-高级系统设置-高级-启动和恢复 我也觉得是硬盘的问题 硬盘有坏扇区居多,剩下可能就是电源不行了. 貌似找到原因了，我原来两根内存一根4G一根8G，是插成非对称双通道的。现在我把两根都插在一个通道上了，运行到现在正常没崩过，我再多观察一段时间的。原来双通道还有容易崩溃的问题啊
页:
[1]