那位大神分析一下,蓝屏原因在哪?最新的WIN10红石

显示全部楼层 · 发表于 2016-8-3 21:31:29

本帖最后由 cs221314 于 2016-8-3 21:33 编辑

就蓝屏一次,以前用WIN10从未蓝屏过,那位大神帮忙分析下,我自己用软件解析出来的内容如下:并附上原文件

080316-13828-01.rar (55.21 KB, 下载次数: 65)

2016-8-3 21:31 上传

点击文件名下载附件

Microsoft (R) Windows Debugger Version 6.10.0003.233 X86Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [D:\Document And Settings\zhou\Desktop\080316-13828-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 14393 MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSMachine Name:Kernel base = 0xfffff801`0b08a000 PsLoadedModuleList = 0xfffff801`0b38f060Debug session time: Wed Aug 3 20:47:43.596 2016 (GMT+8)System Uptime: 0 days 10:15:15.398********************************************************************** 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 3B, {c0000005, fffff805d7a651c6, ffffbe0055652c70, 0}Unable to load image WiseFs64.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for WiseFs64.sys*** ERROR: Module load completed but symbols could not be loaded for WiseFs64.sysUnable 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*** 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 ****** 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 ****** ******************************************************************************************************************************************************** ****** ****** 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 ****** ******************************************************************************************************************************************************** ****** ****** 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 <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_ram ( PAGE_NOT_ZERO_VISTA )Followup: MachineOwner--------- *** Memory manager detected 58466 instance(s) of page corruption, target is likely to have memory corruption.

显示全部楼层 · 发表于 2016-8-3 22:58:50

你还没有挂载符号文件

显示全部楼层 · 发表于 2016-8-3 23:27:58

扬帆起航发表于 2016-8-3 22:58
你还没有挂载符号文件

蓝屏分析的不就是这个文件么?搞不清楚,要是以后不蓝屏就这么用了,我把显卡驱动重新更新了一次,

显示全部楼层 · 发表于 2016-8-4 07:37:50

10586曾经蓝屏过一次，并且还把主板折腾挂了。

显示全部楼层 · 发表于 2016-8-4 08:50:30

cs221314 发表于 2016-8-3 23:27
蓝屏分析的不就是这个文件么?搞不清楚,要是以后不蓝屏就这么用了,我把显卡驱动重新更新了一次,

我帮你看了下,找出了这个驱动程序:WiseFs64.sys
你是不是正在使用Wise Folder Hider这个软件

显示全部楼层 · 发表于 2016-8-4 20:51:10

我是安装了驱动人生就蓝屏重启，后拉卸载了就没什么事了

显示全部楼层 · 发表于 2016-8-5 10:00:29

扬帆起航发表于 2016-8-4 08:50
我帮你看了下,找出了这个驱动程序:WiseFs64.sys
你是不是正在使用Wise Folder Hider这个软件

嗯啊,以前用的老软件了,现在基本不怎么用了,可能是老软件的驱动问题吧,我更新最新版了,目前两天了没蓝屏,也许是偶然现象,要是在遇到的话我就卸载了它

[分享] 那位大神分析一下,蓝屏原因在哪?最新的WIN10红石