积极答复者
windows 7 关机和开机时经常蓝屏

问题
-
每天開機都要重起5 - 6次 才可以正常使用 安全模式 修復都不行
我用Debugging Tools for Windows 后發現是rdyboost.sys 引起的問題
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\042510-19843-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\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16539.x86fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0x8403e000 PsLoadedModuleList = 0x84186810 Debug session time: Sun Apr 25 07:12:28.257 2010 (GMT+8) System Uptime: 0 days 0:00:16.225 ********************************************************************* * 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\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Loading Kernel Symbols ............................................................... .......................................................... Loading User Symbols Loading unloaded module list .... Unable to load image \SystemRoot\System32\drivers\rdyboost.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for rdyboost.sys *** ERROR: Module load completed but symbols could not be loaded for rdyboost.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {3, 2, 1, 8dbd5910} *** WARNING: Unable to verify timestamp for CLASSPNP.SYS *** ERROR: Module load completed but symbols could not be loaded for CLASSPNP.SYS *** WARNING: Unable to verify timestamp for ataport.SYS *** ERROR: Module load completed but symbols could not be loaded for ataport.SYS ***** 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 : rdyboost.sys ( rdyboost+3910 ) Followup: MachineOwner ---------
請問這個問題怎麽搞定~~google 搜索到 好像只有關閉 某個服務
答案
-
安全模式都蓝屏的话,这个问题就有点棘手了。
我建议你备份好重要的数据,然后重装系统。如果新的系统也会蓝屏,基本可以断定是硬件和系统有冲突。如果是这样的话,请你联系你的硬件供应商来检测硬件问题。
Arthur Li - MSFT- 已标记为答案 Arthur_LiMicrosoft contingent staff, Moderator 2010年5月3日 1:59
-
请您检查一下硬件的设置是否正确,开机进入BIOS恢复默认设置试试,在硬件引导菜单中,请确保已经正确设置从硬盘启动,曾经遇到一个问题是,用U盘引导BT3系统,设置开机先从U盘引导,使用完之后,就直接拔掉了U盘,并未设置从硬盘启动,出现的情况是,每次开机时不到3秒,不论进入安全模式还是正常启动,都会出现蓝屏现象。最后恢复BIOS设置,再次把U盘插上,按F12把引导设置从硬盘启动,最后问题解决了。
王万利 http://hackerjx.blog.51cto.com/- 已标记为答案 Arthur_LiMicrosoft contingent staff, Moderator 2010年5月3日 1:59
全部回复
-
出现需要TrustedInstaller提供的权限是因为Windows 7的系统根目录下的很多文件都是被保护的,要想替换、删除或修改这些文件必须先获得该文件的权限。要获得文件权限可以参考以下:
单击“开始”按钮,并在搜索条中输入“cmd”敲击回车键;
在“命令提示符”窗口中输入:
takeown /f C:\Windows\system32\drivers\rdyboost.sys
在获取权限之后还需打开该文件的属性 - 安全选项卡,单击“编辑”按钮为当前用户账户添加修改或完全控制权限。
楼主的问题应该是设备或程序错误的调用了Readyboost的驱动程序,由于异常从而蓝屏。
修改rdyboost.sys文件可以让系统跳过对该文件的加载。
请将已解决的问题标记为“答案”,以便更多的朋友能够方便的找到问题解决方案。 - Windows User Experience | Virtualization Sino -
錯誤的回復
建議以管理員身份運行命令提示符并執行命令:
sc config rdyboost start= disabled
REM 注意: 选项名称包括等号。
REM 等号和值之间需要一个空格。以禁用 ReadyBoost 服務
如要恢復, 同樣請以管理員身份運行命令提示符并執行命令
sc config rdyboost start= boot
錯誤的回復
通過之前在虛擬機的測試, 表明禁用 ReadyBoost 服務將會在系統啟動過程中, 因錯誤配置(服務被禁用)而發生藍屏錯誤.
Folding@Home- 已编辑 repl 2010年4月29日 12:09 對錯峰的方法進行說明
-
安全模式都蓝屏的话,这个问题就有点棘手了。
我建议你备份好重要的数据,然后重装系统。如果新的系统也会蓝屏,基本可以断定是硬件和系统有冲突。如果是这样的话,请你联系你的硬件供应商来检测硬件问题。
Arthur Li - MSFT- 已标记为答案 Arthur_LiMicrosoft contingent staff, Moderator 2010年5月3日 1:59
-
其實本不該犯這個錯誤, 因為 ReadyBoost 服務的 ERROR_CONTROL 被配置為 3 CRITICAL, 只有重要服務才會被如此設置.
該設置表明如果服務或驅動程序發生錯誤, 并且尚未通過 "最後一次正確配置" 引導, 那么系統將重新啟動, 并使用 "最後一次正確配置" 嘗試解決該問題; 如果 "最後一次正確配置" 修復無效, 那么系統將終止引導, 并產生一個藍屏錯誤.
如果發生了藍屏錯誤, 那么 Windows 7 將在下一次重新啟動時, 嘗試通過 "啟動啟動修復" 來解決該問題, 之前在虛擬機中的測試, 系統是通過 "系統還原" 來解決此問題的.
相關截圖01:
相關截圖02:
Folding@Home -
请您检查一下硬件的设置是否正确,开机进入BIOS恢复默认设置试试,在硬件引导菜单中,请确保已经正确设置从硬盘启动,曾经遇到一个问题是,用U盘引导BT3系统,设置开机先从U盘引导,使用完之后,就直接拔掉了U盘,并未设置从硬盘启动,出现的情况是,每次开机时不到3秒,不论进入安全模式还是正常启动,都会出现蓝屏现象。最后恢复BIOS设置,再次把U盘插上,按F12把引导设置从硬盘启动,最后问题解决了。
王万利 http://hackerjx.blog.51cto.com/- 已标记为答案 Arthur_LiMicrosoft contingent staff, Moderator 2010年5月3日 1:59