Win7藍(lán)屏代碼0x0000007F解決方法
Win7藍(lán)屏代碼0x0000007F解決方法
經(jīng)過(guò)小編之前的介紹之后，想必大家覺(jué)得w764位旗艦版下載出現(xiàn)藍(lán)屏的現(xiàn)象已經(jīng)是不足為奇了吧?是的，雖然在之前的文章中小編也介紹了不少關(guān)于win7旗艦版出現(xiàn)藍(lán)屏故障的解決方法，但是總的來(lái)說(shuō)，咱們介紹的并不算完整，因?yàn)槊看蝫in7旗艦版出現(xiàn)藍(lán)屏，都可能有不同的故障代碼出現(xiàn)，而咱們的解決辦法，也是需要以這個(gè)故障代碼為依據(jù)的。今天，又一位朋友遇到了win7旗艦版藍(lán)屏的故障，故障代碼0x0000007F，那么這樣的代碼，是什么原因引起的呢?
1.第一種情況，是因?yàn)殡娔X主板的問(wèn)題，很多時(shí)候，主板的不兼容就會(huì)導(dǎo)致這樣的情況出現(xiàn)，而主板不兼容的情況是比較常見(jiàn)的，大家不妨檢查一下自己的電腦主板。
2.除了硬件之外，還有一個(gè)就是win7旗艦版中的軟件的問(wèn)題了，大家可以試著將最近下載的服務(wù)或者是程序全部卸載掉，軟件的不兼容也會(huì)造成win7旗艦版出現(xiàn)藍(lán)屏的現(xiàn)象。
3.如果上述操作方式都無(wú)法解決問(wèn)題的話，小編就建議各位將win7旗艦版中計(jì)算機(jī)提供的所有系統(tǒng)診斷軟件都用上，特別需要做一個(gè)內(nèi)存檢查，非常的重要。
Windows7使用過(guò)程中，經(jīng)常會(huì)遇到藍(lán)屏的現(xiàn)象。對(duì)于初學(xué)者來(lái)講，好象就是一場(chǎng)電腦災(zāi)難一樣，不知所措。其實(shí)只要了解其原因之后，對(duì)癥下藥即可。針對(duì)0x0000003B藍(lán)屏故障，微軟在最近發(fā)布了解決此問(wèn)題的補(bǔ)丁
微軟近日表示，在Windows 7或Windows Server 2008 R2中運(yùn)行部分應(yīng)用程序可能會(huì)導(dǎo)致藍(lán)屏死機(jī)(BSOD)，在這種崩潰情況下，系統(tǒng)會(huì)給出0x0000003B停止錯(cuò)誤提示。當(dāng)前，微軟已經(jīng)發(fā)布了一個(gè)熱修復(fù)補(bǔ)丁，遭遇此類問(wèn)題的用戶可以手動(dòng)獲取該補(bǔ)丁。
微軟在知識(shí)庫(kù)文章KB2584454中詳細(xì)描述了這個(gè)問(wèn)題，當(dāng)你在Windows 7、Windows 7 SP1或是Windows Server 2008 R2、Windows Server 2008 R2 SP1上運(yùn)行特定的應(yīng)用程序時(shí)，例如Cyberlink YouCam，可能會(huì)收到下面的停止錯(cuò)誤信息：
Stop 0x0000003B (c0000094 fffff8800ff22e54 fffff880098897f0 0)
YSTEM_SERVICE_EXCEPTION
導(dǎo)致這一問(wèn)題的原因是，D3D9運(yùn)行時(shí)(runtime)沒(méi)有對(duì)應(yīng)用程序(如YouCam)傳送的矩形值執(zhí)行參數(shù)驗(yàn)證，因此，Dxgkrnl.sys模塊收到的是無(wú)效的矩形坐標(biāo)。然而，Dxgkrnl.sys模塊也不會(huì)對(duì)矩形坐標(biāo)進(jìn)行驗(yàn)證，從而導(dǎo)致了"被零除"異常。
修復(fù)補(bǔ)丁下載http://support.microsoft.com/hotfix/KBHotfix.aspxkbnum=2584454&kbln=zh-cn
問(wèn)題反映：win7電腦在瀏覽網(wǎng)頁(yè)時(shí)候出現(xiàn)藍(lán)屏，使用的瀏覽器是IE 11，win7藍(lán)屏代碼008e，附上藍(lán)屏日志信息,請(qǐng)幫助解決。
藍(lán)屏日志如下：
復(fù)制代碼代碼如下:
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\桌面1614-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
---------
【編輯分析及建議】經(jīng)過(guò)查看文件，了解到qutmdrv.sys引起的。qutmdrv.sys似乎是360的驅(qū)動(dòng)，建議您卸載掉再查看問(wèn)題是否存在。