豆豆系统 - 收集提供最好的windows光盘下载 首页网站地图Win7激活工具专题设为首页加入收藏
当前位置:豆豆系统 > 故障 > win7系统故障 >

Win7系统浏览网页出现蓝屏1000008E分析及解决

  • 更新时间:2015-04-23
  • 来源:本站小编
  • 浏览:307次

  最近有用户在win7操作使用IE浏览器浏览网页时出现蓝屏问题,蓝屏错误代码1000008E,出现这种情况有很多因素,如电脑病毒感染、硬件问题、软件或驱动冲突等等,下面来看看蓝屏1000008E日志信息吧及解决建议吧。

Win7系统浏览网页出现蓝屏1000008E分析及解决

  蓝屏日志如下:

  代码如下:

  Microsoft (R) Windows Debugger Version 6.11.0001.404 X86

  Copyright (c) Microsoft Corporation. All rights reserved.

  Loading Dump File [C:\Documents and Settings\Administrator\桌面\071614-18203-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 (2 procs) Free x86 compatible

  Product: WinNt, suite: TerminalServer SingleUserTS

  Machine Name:

  Kernel base = 0x83e15000 PsLoadedModuleList = 0x83f5e5b0

  Debug session time: Wed Jul 16 02:24:00.417 2014 (GMT+8)

  System Uptime: 0 days 4:08:35.290

  *****************************************************************

  * 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 fltmgr.sys, Win32 error 0n2

  *** WARNING: Unable to verify timestamp for fltmgr.sys

  *** ERROR: Module load completed but symbols could not be loaded for fltmgr.sys

  ************************************************* Bugcheck Analysis ***  Use !analyze -v to get detailed debugging information.

  BugCheck 1000008E, {c0000005, 89bca885, 9edd2714, 0}

  *** WARNING: Unable to verify timestamp for qutmdrv.sys

  *** ERROR: Module load completed but symbols could not be loaded for qutmdrv.sys

  *** WARNING: Unable to verify timestamp for QQProtect.sys

  *** ERROR: Module load completed but symbols could not be loaded for QQProtect.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 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 : qutmdrv.sys ( qutmdrv+cd12 )

  Followup: MachineOwner

  ---------

  百度知道解决方法:

  1: 需要系统自带的还原功开机F11——高级——将系统恢复到过去某个时间,也就是出现这个问题的前一天和前几天都可以,几分钟就可以搞定.别的方法无法从根本上解决你的问题

  2:也可以开机按{F8进安全模式}选择系统还原.

  3:建议开机欢迎画面——{F8进安全模式}进行还原因为在安全模式下不起动除系统以外的软件,快的话几分钟就可以搞定,去试一下

  蓝屏修复助手:http://www.doudouxitong.com/tools/xiaogongju/2014/0519/1498.html

  豆豆系统分析及建议:经过查看文件,了解到qutmdrv.sys引起的。qutmdrv.sys似乎是360的驱动,建议您卸载掉再查看问题是否存在。

  可见浏览网页导致蓝屏蓝屏1000008E主要原因还是软件与驱动冲突所致,希望教程的日志分析及解决建议对大家有所帮助。

上一篇:联想笔记本win7 64位通过BIOS开启网卡详细教程   下一篇:WIN7系统开机出错提示WINSYS.VBS文件已损坏解决方法

版权声明:本站收录的文章及教程都是本站小编精心制作,仅供学习交流之用,如转载请注明出处。劳动最光荣,请尊重!

发表评论
请自觉遵守互联网相关的政策法规,严禁发布色情、暴力、反动的言论。
用户名: 验证码: 点击我更换图片
专题推荐