有关BlueScreen的那些事儿

Question

小本本最近遇到局域网内客户机频繁蓝屏问题。阴差阳错的问题抛到了我这边(what?)男人不能怂就是干。
然后，本本在网上查了大部分的蓝屏原因解决方法，并找到了客户机本地的蓝屏日志文件内容。日志贴到后面好了，目前问题还没有解决，，先来记录一下过程。希望有大腿给点意见：
本本先是按着这个说明搞得：
https://jingyan.baidu.com/article/b87fe19ea527c25218356801.html
然后未见异常，找了一些其他方法未果，就去找了下面的日志：

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [F:\zooqun\error\Minidump2\062718-12453-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 \SystemRoot\system32\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 x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850 Machine Name: Kernel base = 0xfffff80003e0d000 PsLoadedModuleList = 0xfffff80004052e90 Debug session time: Wed Jun 27 08:33:22.599 2018 (UTC + 8:00) System Uptime: 0 days 0:00:45.021 *********************************************************************
• 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 \SystemRoot\system32\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 .... *******************************************************************************
• *
• Bugcheck Analysis *
• * *******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, fffff88001591401}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Answer 1

---

Unable to load image \SystemRoot\system32\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 x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff80003e0d000 PsLoadedModuleList = 0xfffff80004052e90
Debug session time: Wed Jun 27 08:33:22.599 2018 (UTC + 8:00)
System Uptime: 0 days 0:00:45.021

---

• 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 \SystemRoot\system32\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 ............................................................... ................................................................ 其中这部分应该是最关键的了：加载SystemRoot\system32\ntoskrnl.exe失败，有提到环境变量，本本找到了客户机的ntoskrnl文件首先确认文件是有的，不知道这是干嘛使得，系统安装用的吧。那估计是环境变量的问题了？去试试