光影精灵2经常蓝屏

LIyI123 — Wed, 27 Sep 2017 06:23:16 GMT

经常蓝屏，重装系统以后还是这样。用文件检测之后发现原因是什么ntoskrnl.exe(nt +14f8b0)这是什么原因，求大神解答

回复：光影精灵2经常蓝屏

y2kim — Wed, 27 Sep 2017 06:38:47 GMT

@LIyI123 已写：
经常蓝屏，重装系统以后还是这样。用文件检测之后发现原因是什么ntoskrnl.exe(nt +14f8b0)这是什么原因，求大神解答

这个文件检测其实根本没分析出真正原因，没有太大参考意义。蓝屏问题，具体情况都不太一样，找人工客服开case跟进。

回复：光影精灵2经常蓝屏

LIyI123 — Wed, 27 Sep 2017 06:40:43 GMT

怎么弄？求指点

回复：光影精灵2经常蓝屏

LIyI123 — Wed, 27 Sep 2017 06:48:53 GMT

Loading Dump File [C:\Windows\Minidump\092717-9687-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 <symbol_path> 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 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 14393.1715.amd64fre.rs1_release_inmarket.170906-1810
Machine Name:
Kernel base = 0xfffff801`e8e13000 PsLoadedModuleList = 0xfffff801`e9111040
Debug session time: Wed Sep 27 13:47:09.998 2017 (GMT+8)
System Uptime: 4 days 15:05:18.123
*********************************************************************
* 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 \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 9F, {3, ffffc90a5a5c1060, ffffdc8189cbb8e0, ffffc90a5feda480}

***** 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!_IRP ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_IRP ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_IRP ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : ntoskrnl.exe ( nt+14f8b0 )

Followup: MachineOwner
---------

回复：光影精灵2经常蓝屏

y2kim — Wed, 27 Sep 2017 06:52:11 GMT

看到这句没

Symbol search path is: *** Invalid ***

没有配置好symbol，没法准确分析。得出来的都是很笼统的信息。

不要浪费时间了，找专人开case。

回复：光影精灵2经常蓝屏

y2kim — Wed, 27 Sep 2017 06:56:24 GMT

0x0000009F

The DRIVER_POWER_STATE_FAILURE

先将机器BIOS版本更新到最新版本

回复：光影精灵2经常蓝屏

LIyI123 — Wed, 27 Sep 2017 06:57:35 GMT

怎么弄？我不会弄啊

回复：光影精灵2经常蓝屏

y2kim — Wed, 27 Sep 2017 06:59:31 GMT

HP 笔记本电脑 - 更新 BIOS

http://support.hp.com/cn-zh/document/c00444074

回复：光影精灵2经常蓝屏

LIyI123 — Wed, 27 Sep 2017 07:08:51 GMT

之后呢

回复：光影精灵2经常蓝屏

LIyI123 — Wed, 27 Sep 2017 07:28:47 GMT

安装好了再怎么弄啊哥

回复：光影精灵2经常蓝屏

y2kim — Wed, 27 Sep 2017 07:36:09 GMT

在系统下，按Fn+Esc，现在的BIOS版本是多少？

回复：光影精灵2经常蓝屏

LIyI123 — Wed, 27 Sep 2017 08:01:58 GMT

BIOS 版本/日期 Insyde F.38, 2017/5/24

回复：光影精灵2经常蓝屏

y2kim — Wed, 27 Sep 2017 08:03:52 GMT

@LIyI123 已写：
BIOS 版本/日期 Insyde F.38, 2017/5/24

可以了，先观察几天看看。

回复：光影精灵2经常蓝屏

LIyI123 — Wed, 27 Sep 2017 08:09:34 GMT

好的谢谢哥

该主题

光影精灵2经常蓝屏

回复： 光影精灵2经常蓝屏

回复： 光影精灵2经常蓝屏

回复： 光影精灵2经常蓝屏

回复： 光影精灵2经常蓝屏

回复： 光影精灵2经常蓝屏

回复： 光影精灵2经常蓝屏

回复： 光影精灵2经常蓝屏

回复： 光影精灵2经常蓝屏

回复： 光影精灵2经常蓝屏

回复： 光影精灵2经常蓝屏

回复： 光影精灵2经常蓝屏

回复： 光影精灵2经常蓝屏

回复： 光影精灵2经常蓝屏

回复：光影精灵2经常蓝屏

回复：光影精灵2经常蓝屏

回复：光影精灵2经常蓝屏

回复：光影精灵2经常蓝屏

回复：光影精灵2经常蓝屏

回复：光影精灵2经常蓝屏

回复：光影精灵2经常蓝屏

回复：光影精灵2经常蓝屏

回复：光影精灵2经常蓝屏

回复：光影精灵2经常蓝屏

回复：光影精灵2经常蓝屏

回复：光影精灵2经常蓝屏

回复：光影精灵2经常蓝屏