当前位置:重装系统 > 系统教程 >

教你恢复win7系统蓝屏代码1000008e的步骤介绍

时间:2023-12-02 17:39:06 作者:win7蓝屏,蓝屏 来源:本站整理

我们在使用win7系统的过程中,经常需要对win7系统蓝屏代码1000008E的问题,有很多人清楚如何处理,但是对于新接触的伙伴们,win7系统蓝屏代码1000008E到底该如何设置?其实解决win7系统蓝屏代码1000008E的方案,其实只需要按照经过查看文件,了解到qutmdrv.sys引起的。qutmdrv.sys似乎是360的驱动,建议您卸载掉再查看问题是否存在。就可以了。下面小编就给大家介绍一下win7系统蓝屏代码1000008E的方案如下:
         问题反映:win7电脑在浏览网页时候出现蓝屏,使用的浏览器是IE 11,win7蓝屏代码008e,附上蓝屏日志信息,请帮助解决。

  蓝屏日志如下:

  代码如下:

  Microsoft (R) Windows Debugger Version 6.11.0001.404 X86

  Copyright (c) Microsoft Corporation. All rights reserved.

  Loading Dump File [C:Documents and SettingsAdministrator桌面�71614-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

  ---------

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

以上就是小编为大家带来的win7系统蓝屏代码1000008e的解决方法大家都会操作了吗?还有不明白的小伙伴可以留言给小编来帮你们解惑。

Tags: 蓝屏


热门教程
//