Windows 8蓝屏出现bad-pool-header的提示
这个问题已经出现三次了，每次都自动重启后一切正常。
我已经把相关文件共享了，先谢谢大家帮忙解答
https://skydrive.live.com/redir?resid=BE889A910A1BDA79!696
您好，下面是您蓝屏的原因：
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:UsersYonglongDownloads 32513-30109-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 SystemRootsystem32 toskrnl.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 9200 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
Machine Name:
Kernel base = 0xfffff801`2e005000 PsLoadedModuleList = 0xfffff801`2e2cea80
Debug session time: Mon Mar 25 22:24:27.022 2013 (GMT+8)
System Uptime: 9 days 9:58:42.939
*********************************************************************
* 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 SystemRootsystem32 toskrnl.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 19, {e, fffffa800cda4b20, 9d2c300200000078, 9d2c30028964bb97}
*** 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 : ntoskrnl.exe ( nt+7a040 )
Followup: MachineOwner
---------
解决方案:
1.卸掉所有的新近安装的硬件.
2.运行由计算机制造商提供的所有系统诊断软件.尤其是内存检查.
3.检查是否正确安装了所有新硬件或软件,如果这是一次全新安装,请与硬件或软件制造商联系,获得可能需要的任何Windows更新或驱动程序.
4.禁用或卸载所有的反病毒程序.
5.禁用BIOS内存选项,例如cache或shadow
微星主板BIOS设置－高级BIOS特性设置
来源：http://www.tudoupe.com时间：2015-06-12
微星主板BIOS设置－高级BIOS特性设置
上篇文章中我们分享了微星主板BIOS设置－标准CMOS设置，接下来我们继续来看下微星主板BIOS设置－高级BIOS特性设置
Quick Boot （快速引导）
此项设置为[Enabled]将允许系统在5秒内启动，而跳过一些检测项目。设定值有：
[Enabled], [Disabled]。
Boot Device Select （引导设备次序） 按回车<Enter>进入子菜单并出现以下屏幕：
如果要从U盘启动，在1ST中设置为U盘就可以了。
1st/2nd/3rd Boot Device （第一/ 第二/ 第三 启动设备） 此项允许您设定AMIBIOS载入操作系统的引导设备启动顺序。
Try Other Boot Device （其它设备引导） 将此项设定为[Yes]时，允许系统在从第一/第二/第三设备引导失败后，尝试从其 它设备引导。
Full Screen LOGO Show （全屏LOGO 显示） 此选项能在启动画面上显示公司的logo标志。设置值有：
[Enabled] 启动时全屏显示静态的LOGO画面。
[Disabled] 启动时显示自检信息
S.M.A.R.T. for Hard Disks （硬盘的智能检测技术）
此项允许您激活硬盘的S.M.A.R.T.（自我监控、分析、报告技术）能力。S.MA.R.T应 用程序是来监控硬盘的状态预测硬盘失败。可以提前将数据从硬盘上移动到安全的地
方。设置为：[Enabled], [Disabled]。
BootUp Num-Lock （启动时Num-Lock 状态） 此项可以让您用来设定系统启动后，NumLock的状态。当设定为[On]时，系统启动 后将打开Num Lock，小键盘数字键有效。当设定为[Off] 时，系统启动后Num Lock 关闭，小键盘方向键有效。设定值为：[On], [Off]。
Floppy Drive Seek （寻找软驱）
此项设置引起启动时候BIOS搜寻驱动器。当设定为[Enabled]时，则在系统引导中，BIOS会激活软驱，驱动器的激活指示灯将闪烁并且磁头来回移动一次。首先是A ，然 后是B。设定值为：[Enabled], [Disabled]。
Password Check （检查密码）
此项规定了AMI BIOS的密码保护的种类。设置如下：
| 选项 | 描述 |
| [Setup] | 密码框仅在用户试图进入BIOS设置时出现。 |
| [Always] | 密码框在每次加电开机或用户试图进入BIOS设置时出现。 |
Boot To OS/2 （引导至OS/2 ）
当允许您在OS/2®操作系统下使用大于64MB的DRAM。当您选择[No]时，您不能在内存大于64M时运行OS/2®操作系统。但如果您选择[Yes]时则可以。
Hyper Threading Function （超线程功能） 此部分用于启用或禁用超线程功能。设置为[Enabled]可以提高系统的性能。设定置： [Enabled], [Disabled]。如果您的操作系统不支持超线程功能，请禁用此选项，否则会 导致系统不稳定。
MPS Revision （MPS 版本）
此项允许您选择操作系统所使用的MPS（多处理器规范）版本。您需要选择您的操作
系统所支持的MPS 版本。要了解所使用的版本，请咨询操作系统的经销商。设定值 为：[1.4], [1.1]。
APIC ACPI SCI IRQ
此项用来控制APIC （高级可编程中断控制器）。兼容于PC2001 设计标准，系统可以
在APIC模式运行。启用APIC模式可扩展可选的IRQ系统资源。设定值有：[Enabled],
[Disabled]。
CPU L1 & L2 Cache （CPU 一级二级缓存） 缓存是比常规的系统内存要快很多的附加内存。当CPU需要数据时，系统将所需的数 据从系统内存传到缓存中，供CPU更快的存取。内部缓存（也称做L1或第一级缓 存）和外部缓存（也称做L2或第二级缓存）。设定值有：[Enabled], [Disabled]。
System BIOS Cacheable （系统BIOS 缓存）
选择[Enabled]允许建立系统BIOS ROM缓存，位置在F0000h-FFFFFh范围，能得到更 好的系统性能表现。但是，如果任何一个程序在此内存区内进行写入操作，系统将会
报错。设定值为：[Enabled], [Disabled]。
C000, 32k Shadow
此项规定了如何控制指定适配器ROM 的内容。设定值描述如下：
| 选项 | 描述 |
| [Disabled] | 指定的ROM不复制到RAM中。 |
| [Enabled] | 指定的ROM复制到RAM中以加快系统效能。 |
| [Cached] | 指定的ROM不仅复制到RAM中，还可以从缓存中读和写。 |
以上微星主板BIOS设置－高级BIOS特性设置内容出自土豆PE，感谢浏览~！ 下一篇文章中我们将继续分享微星主板BIOS设置－高级芯片组设置
[] 1071 add unique `translations_table_name_column_name_foreign_key_locale_unique
[] 已知热气球 体积 热空气密度 自重 怎么求 最大载量?
[] 红薯可代替主食？能减肥吗？
[] 如何正确选择激光护目镜？