诊断内核符号生成的Windows 8 Pro崩溃

我的Windows 8 Pro 64位每天至少随机崩溃一次。

该崩溃的内存转储说：

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is 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+                                    *
*********************************************************************
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
Machine Name:
Kernel base = 0xfffff802`92417000 PsLoadedModuleList = 0xfffff802`926e3a20
Debug session time: Sat May 25 14:36:35.216 2013 (UTC + 3:00)
System Uptime: 0 days 1:01:49.888
*********************************************************************
* 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+                                    *
*********************************************************************
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`fe238018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff802924bb182, 0, ffffffffffffffff}

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : ntkrnlmp.exe ( nt!PsReturnProcessNonPagedPoolQuota+42a )

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

内存转储可以从这里下载： http://sdrv.ms/11iYaqT

事件查看器中的系统错误日志共享以下与重新启动相关的条目：

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000133 (0x0000000000000000, 0x0000000000000504, 0x0000000000000503, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052613-19359-01.

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

The previous system shutdown at 12:49:39 on ‎26/‎05/‎2013 was unexpected.

我研究了最近发生的崩溃，当系统没有真正使用时，它们总是出现。例如，我离开了Winamp，我在房子周围做了别的事。就好像计算机在切换到更低功率状态时遇到了麻烦。同样，事件日志中提供的细节很少。

我真的不明白这个转储，我该怎么做才能解决问题。

感谢您的任何输入，让我开始。

感谢您的建议和想法。最后，我做了一个实验，看看哪个设备是真正的罪魁祸首。我很清楚，某些组件或驱动程序会导致这些随机但频繁的问题。

我查看了我的硬件配置，三个组件似乎是合理的嫌疑人：SSD，我的Creative X-Fi XtremeGamer Fatal1ty Pro声卡或AverMedia Live Game视频采集卡。

首先，我查看了SDD并发现固件更新可用。它说它解决了驱动器无法正确进入更低功耗状态的问题。固件承诺解决与我经历的非常相似的问题。不幸的是，固件更新后几分钟，崩溃仍在继续。

然后，我禁用了视频捕获卡。没有得到改善。

最后，我禁用了声卡并使用了板载音频。这样做48小时后，没有崩溃。我的系统运作完美。

不幸的是，Creative再次讨厌，并没有给客户留下废话。虽然我的声卡真的很棒，但他们决定停止对它的驱动程序支持。他们有一个糟糕的驱动程序，它不会很快更新。我唯一的解决方案是购买另一张卡。 Windows 7推出时，他们采取了同样的噱头。 :(

我希望这次讨论能够帮助其他有类似问题的人。如果你有一张去年一年半未购买的Creative声卡，他们糟糕的驾驶员支持可能会引起类似的挫败感。

Windows文件 win32k.sys 您的硬盘已损坏。跑 sfc /scannow 要么 DISM /Online /Cleanup-Image /RestoreHealth 修复损坏的文件。

现在看看你是否遇到新的崩溃。