怎么修复win10系统蓝屏代码1000008E的办法?

怎么修复win10系统蓝屏代码1000008E的办法?？

很多对电脑不太懂的朋友留言询win10系统蓝屏代码1000008E的问题不知道解决，其实win10系统蓝屏代码1000008E处理起来不是很难，可是网上众多朋友还不知道怎么处理，小编今天希望大家学习到的是win10系统蓝屏代码1000008E比较容易操作的方法。你只用依照按照经过查看文件，了解到qutmdrv.sys引起的。qutmdrv.sys似乎是360的驱动，建议您卸载掉再查看问题是否存在。的步骤即可，还有不知道win10系统蓝屏代码1000008E么解决的朋友赶快来学习一下吧！
         问题反映：win10电脑在浏览网页时候出现蓝屏，使用的浏览器是iE 11，win10蓝屏代码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

　　windows10 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的驱动，建议您卸载掉再查看问题是否存在。