蓝屏又见蓝屏

显示全部楼层 · 发表于 2012-6-5 16:58:12

本帖最后由 angol 于 2012-6-6 16:25 编辑

这几天不知道是不是装了工行网银助手出事，系统开机都很正常，但是过了几分钟后，突然鼠标一卡，就进入蓝屏，然后重启，后来重装系统，觉得会不会是补丁有问题，于是把那个补丁删了，原以为没问题了，还是出事。求解！！
下面是蓝屏文件给出的信息：百度了不太了解怎么解决。。。。

显示全部楼层 · 发表于 2012-6-5 18:38:05

对于错误代码的解释：
内存溢出,是系统的问题.由于系统使用时间太长,或是系统运行过超过他本身能承受了的程序.让内存出错.
你可以这样解决.把内存拔下来,把店断了.过段时间插上看看是否还有这个原因.不行就把BIOS清空把内存拔掉再插上重新启动识辨一下.还不行就只能清空BIOS,内存拔了插上重起后重做系统,应该就没有问题了.如果还出现这样的问题,说明您的内存有问题了.

问题是内存溢出，一般是程序的问题，设计不规范，BUG什么的。你删除了什么补丁？

显示全部楼层 · 发表于 2012-6-5 18:51:22

能否把dump文件上传上来看看？

显示全部楼层 · 发表于 2012-6-5 19:54:36

应该还是需要dump来判断的，单纯这个只知道是由于ntoskrnl.exe引起的蓝屏，这个很蛋疼的说。。。

看看dump里面说的是什么？？？

显示全部楼层 · 发表于 2012-6-5 21:55:00

这里有这么一段话：
ntoskrnl.exe是系统正常运转、各种办公软件、游戏运行所不可或缺的重要文件！在木马病毒或是误操作的情况下，您的系统是否经常提示一些让您手足无措的信息，比如：“系统文件ntoskrnl.exe损坏或者找不到指定的系统ntoskrnl.exe文件”提示。立即下载金山卫士进行系统扫描可以轻松解决这类问题！
详细见http://file.ijinshan.com/exe_ntoskrnl_exe.shtml

显示全部楼层 · 发表于 2012-6-5 22:04:02

0x0000007F错误表示硬件设备遇到问题。这个错误一般是因为内存发生故障或CPU、内存、显卡等硬件设备超频过度引起的。如果遇到0x0000007F错误，建议首先检查一下CPU、内存、显卡等硬件设备是否经过了超频，如果是的话请将超频的设备恢复为默认的工作频率；其次请使用内存检测软件对内存进行稳定性及兼容性测试，推荐使用Windows Memory Diagnostic、MemTest等检测软件。

显示全部楼层 · 发表于 2012-6-5 22:07:56

GiBson 发表于 2012-6-5 18:51
能否把dump文件上传上来看看？

已经上传了麻烦你

显示全部楼层 · 发表于 2012-6-5 22:08:12

大号跳蚤发表于 2012-6-5 19:54
应该还是需要dump来判断的，单纯这个只知道是由于ntoskrnl.exe引起的蓝屏，这个很蛋疼的说。。。

看看du ...

已经上传了

显示全部楼层 · 发表于 2012-6-5 22:15:55

本帖最后由老机子于 2012-6-5 22:19 编辑

ntoskrnl.exe引起的系统蓝屏，没记错的你是第4个了！你用本版块的搜索功能，输入ntoskrnl.exe，一搜一大堆！网上也有很多，不敢说完美解决！当然，你也可参考看看！一般可能是杀软挂靠监控引起的！
——ntoskrnl.exe是NT内核之一，他本身不大可能会出问题，除非内核版本混乱（不合适的补丁），几乎所有的应用程序对硬件的驱动都是由nt内核来完成的（ntoskrnl.exe是其中之一），另外它虽然是一个exe的文件，但他不能单独以进程的方式运行，他只能以进程模块的方式，被主进程所加载，所以我们在看ntoskrnl.exe报错的时候，更应该看是由哪些外部原因引起nt内核出错，其中：中断性，勾子性的嵌入式的进程是引起nt出错的最多原因，，，，

显示全部楼层 · 发表于 2012-6-5 22:25:11

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

Loading Dump File [C:\Users\Rose\Desktop\060512-20077-01\060512-20077-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 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 (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x83e19000 PsLoadedModuleList = 0x83f624d0
Debug session time: Tue Jun  5 21:56:26.465 2012 (GMT+8)
System Uptime: 0 days 0:07:06.854
*********************************************************************
* 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 1000007F, {8, 807c7750, 0, 0}

*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** WARNING: Unable to verify timestamp for fltmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for fltmgr.sys
*** WARNING: Unable to verify timestamp for CBUFS.sys
*** ERROR: Module load completed but symbols could not be loaded for CBUFS.sys
*** WARNING: Unable to verify timestamp for SRTSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSP.SYS
*** WARNING: Unable to verify timestamp for NAVEX15.SYS
*** ERROR: Module load completed but symbols could not be loaded for NAVEX15.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                                  ***
***                                                                ***
*************************************************************************
*********************************************************************
* 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 : CBUFS.sys ( CBUFS+bad2 )

Followup: MachineOwner
---------

[已解决] 蓝屏又见蓝屏

本帖子中包含更多资源

本帖子中包含更多资源

浏览过的版块