您的位置:主页 > 系统教程 > 手把手解决win10系统使用iE11出现蓝屏并提示错误代码1000008E的问题

手把手解决win10系统使用iE11出现蓝屏并提示错误代码1000008E的问题

更新时间:2019-10-25 | 作者:Win10专业版系统 | 信息来源:http://www.hao802.com

今天和大家分享一下win10系统使用iE11出现蓝屏并提示错误代码1000008E问题的解决方法,在使用win10系统的过程中经常不知道如何去解决win10系统使用iE11出现蓝屏并提示错误代码1000008E的问题,有什么好的办法去解决win10系统使用iE11出现蓝屏并提示错误代码1000008E呢?小编教你只需要  1、需要系统自带的还原功开机F11——高级——将系统恢复到过去某个时间,也就是出现这个问题的前一天和前几天都可以,几分钟就可以搞定,别的方法无法从根本上解决你的问题。  2、可以开机按F8进安全模式,选择系统还原;就可以了;下面就是我给大家分享关于win10系统使用iE11出现蓝屏并提示错误代码1000008E的详细步骤::

win10系统使用iE11出现蓝屏并提示错误代码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

  ---------

  二、原因分析

  出现这样的原因是由于电脑感染病毒,硬件出现问题或是软件与驱动冲突导致的,经过分析是系统中的qutmdrv.sys文件引起的,这个似乎是360的驱动。

  三、解决方法

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

  2、可以开机按F8进安全模式,选择系统还原;

win10系统使用iE11出现蓝屏并提示错误代码1000008E的解决方法

  3、建议开机欢迎画面,按F8进安全模式然后进行还原,因为在安全模式下不起动除系统以外的软件,快的话几分钟就可以搞定。

  关于win10旗舰版系统下使用iE11出现蓝屏并提示错误代码1000008E的解决妙招就为大家介绍到这边了,经过上述分析,windows10浏览网页蓝屏代码1000008E的主要因素还是软件与驱动的冲突,用户可以通过上面的方法进行解决,希望可以帮助到你。

 

分享到:


本站发布的系统与软件仅为个人学习测试使用,不得用于任何商业用途,否则后果自负,请支持购买微软正版软件!

Copyright @ 2022 深度技术版权所有