蓝屏代码0x0000007F解决方法
又一位朋友遇到了win7旗舰版蓝屏的故障，故障代码0x0000007f，那么这样的代码，是什么原因引起的呢?下面读文网小编就为大家介绍一下吧，欢迎大家参考和学习。
具体的故障现象及解决方法如下：
1.第一种情况，是因为电脑主板的问题，很多时候，主板的不兼容就会导致这样的情况出现，而主板不兼容的情况是比较常见的，大家不妨检查一下自己的电脑主板。
2.除了硬件之外，还有一个就是win7旗舰版中的软件的问题了，大家可以试着将最近下载的服务或者是程序全部卸载掉，软件的不兼容也会造成win7旗舰版出现蓝屏的现象。
3.如果上述操作方式都无法解决问题的话，小编就建议各位将win7旗舰版中计算机提供的所有系统诊断软件都用上，特别需要做一个内存检查，非常的重要。
Windows7使用过程中，经常会遇到蓝屏的现象。对于初学者来讲，好象就是一场电脑灾难一样，不知所措。其实只要了解其原因之后，对症下药即可。针对0x0000003B蓝屏故障，微软在最近发布了解决此问题的补丁
微软近日表示，在Windows 7或Windows Server 2008 R2中运行部分应用程序可能会导致蓝屏死机(BSOD)，在这种崩溃情况下，系统会给出0x0000003B停止错误提示。当前，微软已经发布了一个热修复补丁，遭遇此类问题的用户可以手动获取该补丁。
微软在知识库文章KB2584454中详细描述了这个问题，当你在Windows 7、Windows 7 SP1或是Windows Server 2008 R2、Windows Server 2008 R2 SP1上运行特定的应用程序时，例如Cyberlink YouCam，可能会收到下面的停止错误信息：
Stop 0x0000003B (c0000094 fffff8800ff22e54 fffff880098897f0 0)
YSTEM_SERVICE_EXCEPTION
导致这一问题的原因是，D3D9运行时(runtime)没有对应用程序(如YouCam)传送的矩形值执行参数验证，因此，Dxgkrnl.sys模块收到的是无效的矩形坐标。然而，Dxgkrnl.sys模块也不会对矩形坐标进行验证，从而导致了"被零除"异常。
修复补丁下载http://support.microsoft.com/hotfix/KBHotfix.aspxkbnum=2584454&kbln=zh-cn
问题反映：win7电脑在浏览网页时候出现蓝屏，使用的浏览器是IE 11，win7蓝屏代码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
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引起的。qutmdrv.sys似乎是360的驱动，建议您卸载掉再查看问题是否存在。