當(dāng)我們?cè)诓僮?/span>win7系統(tǒng)的時(shí)候難免會(huì)碰到藍(lán)屏的問題，比如最近有用戶反映說(shuō)他在win7旗艦版系統(tǒng)下使用IE瀏覽器瀏覽網(wǎng)頁(yè)的時(shí)候，系統(tǒng)突然出現(xiàn)藍(lán)屏，并提示錯(cuò)誤代碼1000008E，導(dǎo)致無(wú)法繼續(xù)使用，為什么會(huì)出現(xiàn)這樣的問題呢，又該如何解決，下面針對(duì)這個(gè)問題給大家?guī)?lái)具體的原因分析及解決方法如下。
一、藍(lán)屏日志如下
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
---------
二、原因分析
出現(xiàn)這樣的原因是由于電腦感染病毒，硬件出現(xiàn)問題或是軟件與驅(qū)動(dòng)沖突導(dǎo)致的，經(jīng)過分析是系統(tǒng)中的qutmdrv.sys文件引起的，這個(gè)似乎是360的驅(qū)動(dòng)。
三、解決方法
1、需要系統(tǒng)自帶的還原功開機(jī)F11——高級(jí)——將系統(tǒng)恢復(fù)到過去某個(gè)時(shí)間，也就是出現(xiàn)這個(gè)問題的前一天和前幾天都可以，幾分鐘就可以搞定，別的方法無(wú)法從根本上解決你的問題。
2、可以開機(jī)按F8進(jìn)安全模式，選擇系統(tǒng)還原；
3、建議開機(jī)歡迎畫面，按F8進(jìn)安全模式然后進(jìn)行還原，因?yàn)樵诎踩Ｊ较虏黄饎?dòng)除系統(tǒng)以外的軟件，快的話幾分鐘就可以搞定。
關(guān)于Win7旗艦版系統(tǒng)下使用IE11出現(xiàn)藍(lán)屏并提示錯(cuò)誤代碼1000008E的解決妙招就為大家介紹到這邊了，經(jīng)過上述分析，Windows7瀏覽網(wǎng)頁(yè)藍(lán)屏代碼1000008E的主要因素還是軟件與驅(qū)動(dòng)的沖突，用戶可以通過上面的方法進(jìn)行解決，希望可以幫助到你。
閩公網(wǎng)安備 35020302033304號(hào)
網(wǎng)友評(píng)論