电脑总出现蓝屏 这是代码 大家帮看看 谢谢

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\042715-12948-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 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 = 0xfffff80004607000 PsLoadedModuleList = 0xfffff8000484c890 Debug session time: Mon Apr 27 22:58:44.231 2015 (GMT+8) System Uptime: 0 days 1:37:13.229 *********************************************************************
  • 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 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 .................... Unable to load image usbhub.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for usbhub.sys *** ERROR: Module load completed but symbols could not be loaded for usbhub.sys *******************************************************************************
  • *
  • Bugcheck Analysis *
  • * *******************************************************************************

se !analyze -v to get detailed debugging information.

BugCheck FE, {8, 6, 5, fffffa8006c68160}

***** 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 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 argument when starting the debugger. *
  • using .sympath and .sympath+ * ********************************************************************* Probably caused by : usbhub.sys ( usbhub+12a5c ) 这是后面部分

重装系统，看看是否还有故障，如果没有是软件问题，如果有是硬件问题，拔下所有外部硬件看看是否还有问题，测内存、更换主板、cpu。

建议格式化硬盘并重装

重装系统，看看是否还有故障，如果没有是软件问题，如果有是硬件问题，拔下所有外部硬件看看是否还有问题，测内存、更换主板

喔，南屏问题也是很头疼的问题，我们同学买的电脑，他好像是因为驱动不对，一直南屏，后面再官网上去下载系统，驱动什么的安装，现在好多了，
楼主可以试一试

蓝屏是电脑的自我保护机制，经常出现蓝屏说明电脑出现了问题，需要维护了。电脑出现问题无外乎两种：软件和硬件。软件方面来看，注意检查驱动和操作系统
有没有问题，硬件的话，自己用鲁大师去测一下，看是硬盘的问题还是什么其他的问题。建议你先去百度下，自己解决不了的话，去电脑维修点问问。

一般是驱动的问题 可以检测一下驱动是否要更新

先从软件方面考虑，先检测一下，看看是什么问题，如果软件安装没有问题，就是是硬件了

看一下dump file，或许能找到引起蓝屏的原因