昨天我遇到了启动非常慢的情况。今天我遇到了 BSOD。我在一台东芝 Satellite A660-11M最近没有对硬件进行过任何改动(几个月前更换过硬盘)。以下是倾倒和系统数据来自 BSOD 的文件。
事情的经过是这样的:
昨天:我打开机器,加载,启动到登录屏幕。我输入密码,然后就是缓慢的部分。Windows 桌面淡入,但我无法做太多事情(屏幕部分冻结)。然后,1-2 分钟后,一切恢复正常,我收到 AVG 弹出的提示,提示它出现错误(抱歉,忘记具体说了什么)。
拍马屁:我打开机器,Windows 启动到登录屏幕,我输入密码然后去煮咖啡;当我回来时(假设我花了几分钟),带有小加载符号的“欢迎”加载屏幕仍然存在。等了一会儿后,我意识到机器没有响应,于是强行关闭它(不断按下开/关按钮)。然后我再次启动机器,加载到登录屏幕,我输入密码 - 屏幕冻结,几秒钟后,BSOD。
在我下一次尝试时(BSOD 之后),Windows 确实成功完全启动了。但是,进入桌面后,我仍然遇到了非常缓慢的性能问题。我收到了常见的“Windows 未正确关闭”消息,我从中保存了 .DMP 和 .SYSDATA 文件(见上文)。
正如标题所暗示的,我觉得这与 AVG 2012 免费版有关。因为我昨天收到了奇怪的错误消息,而且今天,在 BSOD 之后,Windows 7 操作中心标志出现在系统托盘中。它显示“AVG Anti-Virus 免费版 2012 报告它已关闭”。但是,我确实在系统托盘上看到了 AVG 图标。
所以这一切对我来说似乎有点模糊。我希望转储和系统数据文件能帮到你。我会非常非常感激。如果我遗漏了任何相关信息,请告诉我,我会尽快添加。谢谢!
更新 1:我以带网络连接的安全模式启动 Windows,问题似乎解决了。Windows 启动正常,桌面加载正常。没有冻结,Windows 资源管理器也没有无响应。因此,我想知道问题是否可能是由硬件以外的其他因素引起的。我之所以问这个问题,是因为我不完全确定安全模式是如何工作的,但据我所知,它仍然使用相同的硬件(只是没有使用某些驱动程序)。那么,再次问一下,这有可能与 HDD(或其他硬件)无关吗?
更新2:根据用户 Moab 的建议,我运行了制造商提供的硬盘诊断工具。此工具允许我先运行 SMART 测试,这是一种更快、更智能的“预览”测试。结果是“发现的问题太多,因此诊断工具已结束”。然后我连夜运行了完整测试,结果这。
我仍在寻找解决方案,非常非常感谢您提供的帮助!
谢谢!
答案1
转储分析显示 BSOD 是硬盘的 I/O 错误,请在驱动器上运行硬盘制造商诊断程序,以确保驱动器没有故障。也可能是一次性错误。
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000006, The exception code that was not handled
Arg2: fffff88000c110e9, The address that the exception occurred at
Arg3: fffff88007a60778, Exception Record Address
Arg4: fffff88007a5ffd0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
FAULTING_IP:
CI!MinCrypK_GetCertAlgId+45
fffff880`00c110e9 66394104 cmp word ptr [rcx+4],ax
EXCEPTION_RECORD: fffff88007a60778 -- (.exr 0xfffff88007a60778)
.exr 0xfffff88007a60778
ExceptionAddress: fffff88000c110e9 (CI!MinCrypK_GetCertAlgId+0x0000000000000045)
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 0000000000000000
Parameter[1]: 00000000021c3804
Parameter[2]: 00000000c0000185
Inpage operation failed at 00000000021c3804, due to I/O error 00000000c0000185
CONTEXT: fffff88007a5ffd0 -- (.cxr 0xfffff88007a5ffd0)
.cxr 0xfffff88007a5ffd0
rax=0000000000000200 rbx=0000000000000000 rcx=00000000021c3800
rdx=0000000000001b80 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000c110e9 rsp=fffff88007a609b0 rbp=0000000000000000
r8=000007fffffeffff r9=fffff88007a60aa8 r10=0000000000000000
r11=0000000000000000 r12=fffff8a00000bec0 r13=0000000000000000
r14=0000000000000000 r15=fffff80000b96080
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
CI!MinCrypK_GetCertAlgId+0x45:
fffff880`00c110e9 66394104 cmp word ptr [rcx+4],ax ds:002b:00000000`021c3804=????
.cxr
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 00000000021c3804
EXCEPTION_PARAMETER3: 00000000c0000185
IO_ERROR: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
BUGCHECK_STR: 0x7E
EXCEPTION_STR: 0xc0000006_c0000185
FOLLOWUP_IP:
+45
00000000`021c3804 ?? ???
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware_disk
IMAGE_NAME: hardware_disk
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: kb
FAILURE_BUCKET_ID: X64_0x7E_IMAGE_hardware_disk
BUCKET_ID: X64_0x7E_IMAGE_hardware_disk