电脑蓝屏了？？求解释！！！（重装系统勿进）

[流浪若相惜]

昨晚运行了一组数据结果今天早上开机便蓝屏了，收拾了一上午没弄好！求解释！
内存条试了，我有两个，无论怎么试都是蓝屏，我估计内存条坏的可能性比较小，windows的内存检测我也试了，没有检测出错误来！

附上截图一张：


下边是我用Debug tool 查看的最小内存储文件的内容：发现问题在ntoskrnl.exe，但我不知道如何解决求大神们帮忙

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\sunny\桌面\121213-22230-01\121213-22230-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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\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
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Machine Name:
Kernel base = 0xfffff800`0445e000 PsLoadedModuleList = 0xfffff800`046a16d0
Debug session time: Thu Dec 12 09:52:53.829 2013 (GMT+8)
System Uptime: 0 days 0:03:06.109
*********************************************************************
* 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\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 C4, {10, 3235, 0, 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 *** *** ***

[流浪若相惜]

************************************************************************* unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd ************************************************************************* *** *** *** *** *** 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!_POOL_HEADER *** *** *** ************************************************************************* unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd ************************************************************************* *** *** *** *** *** 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!_POOL_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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!_POOL_TRACKER_BIG_PAGES *** *** *** ************************************************************************* Cannot get _POOL_TRACKER_BIG_PAGES type size ************************************************************************* *** *** *** *** *** 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 : ntoskrnl.exe ( nt+75b80 ) Followup: MachineOwner ---------

[吉普赛的歌]

其实你错得离谱了， 如果真的是硬件问题， 你不重装系统根本是没有办法判断出来的。 只能重装系统， 如果重装了系统， 还这么搞， 那就换硬件吧

[流浪若相惜]

引用 3 楼 yenange 的回复:

其实你错得离谱了， 如果真的是硬件问题， 你不重装系统根本是没有办法判断出来的。 只能重装系统， 如果重装了系统， 还这么搞， 那就换硬件吧

windows系统检测了内存是没有问题的，在安全模式下进入也是没有问题的，你认为是硬件问题吗？

[lasesiwen]

看LZ贴出来的那些提示。似乎是某个驱动程序的问题，说实话以前没遇到过，分析不出来什么原因，LZ就以安全模式进去吧，进去之后再找找，看能不能找到原因

[吉普赛的歌]

引用 4 楼 ztzi321 的回复:

[quote=引用 3 楼 yenange 的回复:] 其实你错得离谱了， 如果真的是硬件问题， 你不重装系统根本是没有办法判断出来的。 只能重装系统， 如果重装了系统， 还这么搞， 那就换硬件吧

windows系统检测了内存是没有问题的，在安全模式下进入也是没有问题的，你认为是硬件问题吗？[/quote] 你可以先想一想， 你电脑坏之前， 是否有安装过其它硬件，或者虚拟光驱之类的东西。 如果能进安全模式， 先把虚拟光驱和新添加的硬件给卸载了吧。

[流浪若相惜]

引用 6 楼 yenange 的回复:

[quote=引用 4 楼 ztzi321 的回复:] [quote=引用 3 楼 yenange 的回复:] 其实你错得离谱了， 如果真的是硬件问题， 你不重装系统根本是没有办法判断出来的。 只能重装系统， 如果重装了系统， 还这么搞， 那就换硬件吧

windows系统检测了内存是没有问题的，在安全模式下进入也是没有问题的，你认为是硬件问题吗？[/quote] 你可以先想一想， 你电脑坏之前， 是否有安装过其它硬件，或者虚拟光驱之类的东西。 如果能进安全模式， 先把虚拟光驱和新添加的硬件给卸载了吧。[/quote]安全模式下是无法卸载的！！

[吉普赛的歌]

引用 7 楼 ztzi321 的回复:

[quote=引用 6 楼 yenange 的回复:] [quote=引用 4 楼 ztzi321 的回复:] [quote=引用 3 楼 yenange 的回复:] 其实你错得离谱了， 如果真的是硬件问题， 你不重装系统根本是没有办法判断出来的。 只能重装系统， 如果重装了系统， 还这么搞， 那就换硬件吧

windows系统检测了内存是没有问题的，在安全模式下进入也是没有问题的，你认为是硬件问题吗？[/quote] 你可以先想一想， 你电脑坏之前， 是否有安装过其它硬件，或者虚拟光驱之类的东西。 如果能进安全模式， 先把虚拟光驱和新添加的硬件给卸载了吧。[/quote]安全模式下是无法卸载的！！[/quote] 别纠结了， 行不？ 重装也不会死人的！

[时光清浅]

楼主最近有更新软件，或者打补丁么？ 你在网上查一下你的蓝屏代码。

[流浪若相惜]

引用 8 楼 yenange 的回复:

[quote=引用 7 楼 ztzi321 的回复:] [quote=引用 6 楼 yenange 的回复:] [quote=引用 4 楼 ztzi321 的回复:] [quote=引用 3 楼 yenange 的回复:] 其实你错得离谱了， 如果真的是硬件问题， 你不重装系统根本是没有办法判断出来的。 只能重装系统， 如果重装了系统， 还这么搞， 那就换硬件吧

windows系统检测了内存是没有问题的，在安全模式下进入也是没有问题的，你认为是硬件问题吗？[/quote] 你可以先想一想， 你电脑坏之前， 是否有安装过其它硬件，或者虚拟光驱之类的东西。 如果能进安全模式， 先把虚拟光驱和新添加的硬件给卸载了吧。[/quote]安全模式下是无法卸载的！！[/quote] 别纠结了， 行不？ 重装也不会死人的！[/quote]http://blog.csdn.net/ztzi321/article/details/17305239

[吉普赛的歌]

引用 10 楼 ztzi321 的回复:

[quote=引用 8 楼 yenange 的回复:] [quote=引用 7 楼 ztzi321 的回复:] [quote=引用 6 楼 yenange 的回复:] [quote=引用 4 楼 ztzi321 的回复:] [quote=引用 3 楼 yenange 的回复:] 其实你错得离谱了， 如果真的是硬件问题， 你不重装系统根本是没有办法判断出来的。 只能重装系统， 如果重装了系统， 还这么搞， 那就换硬件吧

windows系统检测了内存是没有问题的，在安全模式下进入也是没有问题的，你认为是硬件问题吗？[/quote] 你可以先想一想， 你电脑坏之前， 是否有安装过其它硬件，或者虚拟光驱之类的东西。 如果能进安全模式， 先把虚拟光驱和新添加的硬件给卸载了吧。[/quote]安全模式下是无法卸载的！！[/quote] 别纠结了， 行不？ 重装也不会死人的！[/quote]http://blog.csdn.net/ztzi321/article/details/17305239[/quote] 牛B！ 结贴吧！