win7蓝屏问题

[lss520qs]

小弟联想y50c的笔记本，最近不时出现蓝屏的问题，想请教各位大神，部分的bmp文件如下：
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
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`05a04000 PsLoadedModuleList = 0xfffff800`05c46750
Debug session time: Thu Nov 2 23:27:09.602 2017 (GMT+8)
System Uptime: 0 days 0:00:14.944
*********************************************************************
* 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
*** 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
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8005bb3fc0, ffff, 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 ***



Probably caused by : ntoskrnl.exe ( nt+70e00 )

[超黑胖子]

笔记本的话别乱升级驱动，就用官方的，如果换过硬件，比如加过内存条的话，就要检查下兼容性了

当然最好的还是做个一键GHOST备份，系统感觉不行就还原一次，与其浪费时间去查找原因还不如这个方便

[夜鹰]

出现问题有规律吗？或是运行某个程序时才有？ 由ntoskrnl.exe引起的蓝屏故障比较常见，但原因很多，目前相对简单的处理方法有一下几点： 1.重新安装硬件驱动程序； 2.查杀病毒；（断网） 3.chkdsk /f 检查磁盘；（建议安全模式下） 4.检查所有启动项并停用不必要的项目，或者卸载没用的软件； 5.用原版安装镜像升级或修复安装（并非全新安装） 6.检查机器散热部件是否存在异常。 以上方法均无效的话只能备份数据，用笔记本自带的恢复程序恢复出厂或者自己完全重装系统，但一定要用原版镜像安装，这点非常重要。

[lss520qs]

引用 1楼夜鹰 的回复:

出现问题有规律吗？或是运行某个程序时才有？ 由ntoskrnl.exe引起的蓝屏故障比较常见，但原因很多，目前相对简单的处理方法有一下几点： 1.重新安装硬件驱动程序； 2.查杀病毒；（断网） 3.chkdsk /f 检查磁盘；（建议安全模式下） 4.检查所有启动项并停用不必要的项目，或者卸载没用的软件； 5.用原版安装镜像升级或修复安装（并非全新安装） 6.检查机器散热部件是否存在异常。 以上方法均无效的话只能备份数据，用笔记本自带的恢复程序恢复出厂或者自己完全重装系统，但一定要用原版镜像安装，这点非常重要。

磁盘内存都没问题，现在在重新装个系统试试

[北京老男孩儿]

排查硬件没问题就重新安装系统