Win7藍(lán)屏代碼1000008E解決方法是什么
人們使用電腦時(shí)候最不想看到的事情之一就是藍(lán)屏了，無論是工作還是玩游戲時(shí)候都很不爽。這篇文章主要介紹了Win7藍(lán)屏代碼1000008E解決方法,本文藍(lán)屏問題是在使用IE 11時(shí)出現(xiàn)的,需要的朋友可以參考下
問題反映：
win7電腦在瀏覽網(wǎng)頁時(shí)候出現(xiàn)藍(lán)屏，使用的瀏覽器是IE 11，win7藍(lán)屏代碼008e，附上藍(lán)屏日志信息,請幫助解決。藍(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
---------
補(bǔ)充：電腦經(jīng)常性藍(lán)屏是什么原因
一、 屏幕顯示系統(tǒng)忙，請按任意鍵繼續(xù)……
1、 虛擬內(nèi)存不足造成系統(tǒng)多任務(wù)運(yùn)算錯(cuò)誤。
虛擬內(nèi)存是WINDOWS系統(tǒng)所特有的一種解決系統(tǒng)資源不足的方法，其一般要求主引導(dǎo)區(qū)的硬盤剩余空間是其物理內(nèi)存的2-3倍。而一些發(fā)燒友為了充分利用空間，將自己的硬盤塞到滿滿的，忙記了WINDOWS這個(gè)苛刻的要求。結(jié)果導(dǎo)致虛擬內(nèi)存因硬盤空間不足而出現(xiàn)運(yùn)算錯(cuò)誤，所以就出現(xiàn)藍(lán)屏。 要解決這個(gè)問題好簡單，盡量不要把硬盤塞得滿滿的，要經(jīng)常刪除一些系統(tǒng)產(chǎn)生的臨時(shí)文件、交換文件，從而可以釋放空間?；蚩梢允謩优渲锰摂M內(nèi)存，選擇高級，把虛擬內(nèi)存的默認(rèn)地址，轉(zhuǎn)到其他的邏輯盤下。這樣就可以避免了因虛擬內(nèi)存不足而引起的藍(lán)屏。
2、 CPU超頻導(dǎo)致運(yùn)算錯(cuò)誤
超頻對于發(fā)燒友來說是常事，所以由超頻所引起的各種故障也就在所難免了。超頻，就本身而言就是在原有的基礎(chǔ)上完成更高的性能，但由于進(jìn)行了超載運(yùn)算，造成其內(nèi)部運(yùn)算過多，使CPU過熱，從而導(dǎo)致系統(tǒng)運(yùn)算錯(cuò)誤。 有些CPU的超頻性能比較好，如INTEL的賽揚(yáng)處理器和AMD-K6-2處理器還算較好的，但有時(shí)也會出現(xiàn)一些莫名其妙的錯(cuò)誤。(例如：我曾試過將INTEL賽揚(yáng)300A，在超頻到450時(shí)，軟驅(qū)在沒有接受命令時(shí)，進(jìn)行讀盤操作)。INTEL的低于200的CPU以及AMD-K5的超頻能力就不是那么好。建議高檔的CPU要超頻時(shí)，那么散熱工作一定要做好，最好裝一個(gè)大的風(fēng)扇，再加上一些硅膠之類的散熱材料。至于一些低檔的CPU我建議你就最好不要超頻了，免得超頻達(dá)不到預(yù)想的效果反而經(jīng)常出現(xiàn)藍(lán)屏影響計(jì)算機(jī)的正常速度。
二、 存條的互不兼容或損壞引起運(yùn)算錯(cuò)誤。
這時(shí)個(gè)最直觀的現(xiàn)象，因?yàn)檫@個(gè)現(xiàn)象往往在一開機(jī)的時(shí)候就可以見到，根本啟動不了計(jì)算機(jī)，畫面提示出內(nèi)存有問題，問你是否要繼續(xù)。造成這種錯(cuò)誤是物理上的損壞內(nèi)存或者內(nèi)存與其它硬件不兼容所致。這時(shí)候只有換過另外的內(nèi)存了。
三、 遭到不明的程序或病毒攻擊所至
這個(gè)現(xiàn)象只要是平時(shí)我們在上網(wǎng)的時(shí)候遇到的，當(dāng)我們在沖浪的時(shí)候，特別是進(jìn)到一些BBS站時(shí)，可能暴露了自己的IP，被"黑客"用一些軟件攻擊所至。對互這種情況最好就是在自己的計(jì)算機(jī)上安裝一些防御軟件。再有就是登錄BBS要進(jìn)行安全設(shè)置，隱藏自己IP。
四、 光驅(qū)在讀盤時(shí)被非正常打開所至
這個(gè)現(xiàn)象是在光驅(qū)正在讀取數(shù)據(jù)時(shí)，由于被誤操作打開而導(dǎo)致出現(xiàn)藍(lán)屏。這個(gè)問題不影響系統(tǒng)正常動作，只要再彈入光盤或按ESC鍵就可以。
關(guān)了顯示器再打開就沒問題的話，那就是你的顯示器出了問題了
Win7藍(lán)屏代碼1000008E解決方法是什么相關(guān)文章：
2.Win7出現(xiàn)藍(lán)屏代碼0x00000050怎么樣處理