求助，这个蓝屏是什么原因？_电脑吧_百度贴吧
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&签到排名：今日本吧第个签到，本吧因你更精彩，明天继续来努力！
本吧签到人数：0成为超级会员，使用一键签到本月漏签0次！成为超级会员，赠送8张补签卡连续签到：天&&累计签到：天超级会员单次开通12个月以上，赠送连续签到卡3张
关注：1,925,567贴子：
求助，这个蓝屏是什么原因？收藏
登录百度帐号推荐应用
为兴趣而生，贴吧更懂你。或【蓝屏求助】蓝屏求解救_蓝屏吧_百度贴吧
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&签到排名：今日本吧第个签到，本吧因你更精彩，明天继续来努力！
本吧签到人数：0成为超级会员，使用一键签到本月漏签0次！成为超级会员，赠送8张补签卡连续签到：天&&累计签到：天超级会员单次开通12个月以上，赠送连续签到卡3张
关注：8,720贴子：
【蓝屏求助】蓝屏求解救收藏
Microsoft (R) Windows Debugger Version 6.12. AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\0-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 7601 (Service Pack 1) MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSMachine Name:Kernel base = 0xfffff800` PsLoadedModuleList = 0xfffff800`Debug session time: Sun May
8 00:26:16.927 2016 (UTC + 8:00)System Uptime: 0 days 5:28:36.708********************************************************************** 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 109, {a3a039d8aac4ca994d4ba2629c, 101}***** 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
********************************************************************************************************************************************************
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
********************************************************************************************************************************************************
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
****************************************************************************Probably caused by : ntoskrnl.exe ( nt+73c40 )Followup: MachineOwner---------
登录百度帐号推荐应用
为兴趣而生，贴吧更懂你。或}