LOL老是突然蓝屏怎么办 LOL玩游戏蓝屏解决办法
lol很多玩家应该都遇到过玩游戏突然蓝屏的轻卡U那个吧，那么LOL老是突然蓝屏怎么办呢？到底是什么原因呢？我们就来看看LOL玩游戏蓝屏解决办法吧。
LOL蓝屏原因
使用插件或者辅助工具、TGP的加速驱动或者是游戏内的检测驱动，目前为止官方也没有给出准确的原因。
LOL蓝屏解决方法
1、官方论坛方法
2、论坛玩家给出的解决方法
3、可能是你家里的网速什么有问题哦
以上就是手机56带来的游戏详细内容介绍了，更多精彩内容，请关注手机56下载网。
相关游戏推荐
主播真会玩
下载地址：
下载地址：
下载地址：
cdec大师赛积分排名查询
cdec联赛排名查询
不要不要的是什么意思
16882人推荐
2.4分游戏辅助
25854人推荐
2.5分游戏辅助
33154人推荐
0.0分游戏辅助
42159人推荐
6.4分游戏辅助
51289人推荐
1.7分游戏辅助
6905人推荐
8.0分游戏辅助
7628人推荐
0.0分游戏辅助
8521人推荐
5.0分游戏辅助
9930676人推荐
9.3分视频播放
10650175人推荐
8.8分生活应用
1209人推荐
8.0分游戏辅助
2238人推荐
8.0分游戏辅助
3332人推荐
8.0分生活应用
4353人推荐
8.0分游戏辅助
5103人推荐
8.0分主题壁纸
6905人推荐
8.0分游戏辅助
8.0分拍照摄像
8297人推荐
8.0分游戏辅助
9116人推荐
10.0分视频播放
101550人推荐
10.0分学习帮助后使用快捷导航没有帐号？
查看: 1106|回复: 7
新人欢迎积分1 阅读权限70积分5880精华0UID帖子金钱350 威望0
Lv.7, 积分 5880, 距离下一级还需 4120 积分
UID帖子威望0 多玩草0 草
& && && && &朋友给我机箱里插了一个莫名其妙的卡以后就跑路了，导致我的电脑一玩游戏就蓝屏。
& && && && &不玩游戏就好好的。玩魔兽世界也不蓝屏，就是玩LOL就总闪退。
& && && && &打开机箱的话，怎么才能看出哪一个卡是他放进去的？
& && && && &这个问题是不是不好回答？我研究了半天没研究明白。
& && && && &可是此人已经跑路我找不到了啊。
& && && && &不仅是我习惯掉线重连了，跟我一起玩的小朋友们大概也习惯了！
服务器：扭曲丛林
游戏ID：丨恋嗳仲De钕孩灬
她还没有牵手的人
新人欢迎积分1 阅读权限100积分88514精华0UID帖子金钱2831 威望10
Lv.11, 积分 88514, 距离下一级还需 1486 积分
UID帖子威望10 多玩草171 草
电脑该换了
新人欢迎积分1 阅读权限70积分5880精华0UID帖子金钱350 威望0
Lv.7, 积分 5880, 距离下一级还需 4120 积分
UID帖子威望0 多玩草0 草
吖哈|_笨笨范r丶 发表于
电脑该换了
不该电脑的事，都是那个卡，我电脑才换的还不到一年
服务器：扭曲丛林
游戏ID：丨恋嗳仲De钕孩灬
她还没有牵手的人
新人欢迎积分1 阅读权限100积分88514精华0UID帖子金钱2831 威望10
Lv.11, 积分 88514, 距离下一级还需 1486 积分
UID帖子威望10 多玩草171 草
内内go 发表于
不该电脑的事，都是那个卡，我电脑才换的还不到一年
好吧网速吗
新人欢迎积分1 阅读权限70积分5880精华0UID帖子金钱350 威望0
Lv.7, 积分 5880, 距离下一级还需 4120 积分
UID帖子威望0 多玩草0 草
吖哈|_笨笨范r丶 发表于
好吧网速吗
不该网速的事。我家10兆的网。就是那个卡，内存卡好像是。不道从哪偷摸来的就插我机箱里了。害惨我
服务器：扭曲丛林
游戏ID：丨恋嗳仲De钕孩灬
她还没有牵手的人
新人欢迎积分1 阅读权限100积分88514精华0UID帖子金钱2831 威望10
Lv.11, 积分 88514, 距离下一级还需 1486 积分
UID帖子威望10 多玩草171 草
内内go 发表于
不该网速的事。我家10兆的网。就是那个卡，内存卡好像是。不道从哪偷摸来的就插我机箱里了。害惨我 ...
游戏没问题吧
新人欢迎积分1 阅读权限70积分5880精华0UID帖子金钱350 威望0
Lv.7, 积分 5880, 距离下一级还需 4120 积分
UID帖子威望0 多玩草0 草
吖哈|_笨笨范r丶 发表于
游戏没问题吧
游戏没问题啊、！
服务器：扭曲丛林
游戏ID：丨恋嗳仲De钕孩灬
她还没有牵手的人
新人欢迎积分1 阅读权限100积分88514精华0UID帖子金钱2831 威望10
Lv.11, 积分 88514, 距离下一级还需 1486 积分
UID帖子威望10 多玩草171 草
内内go 发表于
游戏没问题啊、！
好吧我不猜了
向日葵勋章
永远的阳光
我是一只羊咩咩
话题王小红花
话题王小红花
阳光热情勋章
阳光热情勋章
诛仙小碧瑶
诛仙MM专属勋章
春天纪念勋章
初级人缘勋章
初级人缘勋章
爱情守望者
爱情守望者
狮子座勋章
狮子座勋章
需要金钱：1100
手机盒子客户端点击或扫描下载
Powered by编辑推荐最新发布的文章本站作品版权所有，未经许可不得转载 CopyRight &【故障求助】玩游戏时不定时出现蓝屏【电脑故障吧】_百度贴吧
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&签到排名：今日本吧第个签到，本吧因你更精彩，明天继续来努力！
本吧签到人数：0成为超级会员，使用一键签到本月漏签0次！成为超级会员，赠送8张补签卡连续签到：天&&累计签到：天超级会员单次开通12个月以上，赠送连续签到卡3张
关注：365,856贴子：
【故障求助】玩游戏时不定时出现蓝屏收藏
Microsoft (R) Windows Debugger Version 6.10.Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\85-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol 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 &symbol_path& argument when starting the debugger. **
using .sympath and .sympath+
**********************************************************************Unable to load image ntoskrnl.exe, Win32 error 0n2*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeWindows 7 Kernel Version 7600 MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSMachine Name:Kernel base = 0xfffff800` PsLoadedModuleList = 0xfffff800`0449de70Debug session time: Sat Dec
6 14:46:27.812 2014 (GMT+8)System Uptime: 0 days 0:16:27.605********************************************************************** 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 &symbol_path& argument when starting the debugger. **
using .sympath and .sympath+
**********************************************************************Unable to load image ntoskrnl.exe, Win32 error 0n2*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeLoading Kernel Symbols.............................................................................................................................................Loading User SymbolsLoading unloaded module list.....********************************************************************************
Bugcheck Analysis
********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 3B, {c0000005, fffffe0, fffff, 0}Unable to load image afd.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for afd.sys*** ERROR: Module load completed but symbols could not be loaded for afd.sys*** WARNING: Unable to verify timestamp for hal.dll*** ERROR: Module load completed but symbols could not be loaded for hal.dll***** 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
Type referenced: nt!_KPRCB
****************************************************************************Unable to load image 360AntiHacker64.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for 360AntiHacker64.sys*** ERROR: Module load completed but symbols could not be loaded for 360AntiHacker64.sysUnable to load image 360netmon.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for 360netmon.sys*** ERROR: Module load completed but symbols could not be loaded for 360netmon.sys****************************************************************************
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
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
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 &symbol_path& 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 &symbol_path& argument when starting the debugger. **
using .sympath and .sympath+
**********************************************************************Probably caused by : hardware ( 360AntiHacker64+2f18 )Followup: MachineOwner---------上面1下面2Microsoft (R) Windows Debugger Version 6.10.Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\81-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol 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 &symbol_path& 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.exeWindows 7 Kernel Version 7600 MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSMachine Name:Kernel base = 0xfffff800` PsLoadedModuleList = 0xfffff800`0448ee70Debug session time: Sat Dec
6 16:39:09.173 2014 (GMT+8)System Uptime: 0 days 0:31:50.062********************************************************************** 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 &symbol_path& 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.exeLoading Kernel Symbols.............................................................................................................................................Loading User SymbolsLoading unloaded module list......********************************************************************************
Bugcheck Analysis
********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 4E, {99, 8a132}***** 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
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
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
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 &symbol_path& 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 &symbol_path& argument when starting the debugger. **
using .sympath and .sympath+
**********************************************************************Probably caused by : ntoskrnl.exe ( nt+70040 )Followup: MachineOwner
登录百度帐号推荐应用}