»
首页
|
手机壁纸
|
海淘值得买
|
度假
|
求职招聘
|
广告联系
» 您尚未登录:请
登录
|
注册
|
标签
|
帮助
|
小黑屋
|
TGFC Lifestyle
»
完全数码讨论区
» 电脑间隙性蓝屏,有啥办法吗
发新话题
发布投票
发布商品
发布悬赏
发布活动
发布辩论
发布视频
打印
[数码手机]
电脑间隙性蓝屏,有啥办法吗
尖锐湿疣
小黑屋
帖子
747
精华
0
积分
15288
激骚
152 度
爱车
主机
相机
手机
注册时间
2009-4-3
发短消息
加为好友
当前离线
1
#
大
中
小
发表于 2011-9-5 23:30
只看该作者
不知道是那里的问题,最近换了SSD硬盘,换了主板,换了内存,换了CPU。系统重装了好几次了,经常蓝屏。都是先蓝屏,再读秒,最后重启。有什么办法吗?
UID
125638
帖子
747
精华
0
积分
15288
交易积分
0
阅读权限
1
在线时间
2496 小时
注册时间
2009-4-3
最后登录
2019-11-19
查看详细资料
TOP
beterhans
hans
银河飞将
帖子
38651
精华
2
积分
54831
激骚
2377 度
爱车
11路
主机
Xbox 360
相机
Nikon D5000
手机
注册时间
2003-10-20
发短消息
加为好友
当前离线
2
#
大
中
小
发表于 2011-9-5 23:33
只看该作者
总之硬件问题了 :D :D
UID
15723
帖子
38651
精华
2
积分
54831
交易积分
0
阅读权限
50
在线时间
19887 小时
注册时间
2003-10-20
最后登录
2024-5-8
查看个人网站
查看详细资料
TOP
尖锐湿疣
小黑屋
帖子
747
精华
0
积分
15288
激骚
152 度
爱车
主机
相机
手机
注册时间
2009-4-3
发短消息
加为好友
当前离线
3
#
大
中
小
发表于 2011-9-5 23:41
只看该作者
分析了下蓝屏后生成的DMP文件得到以下信息
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\sy\Desktop\090511-8174-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`04017000 PsLoadedModuleList = 0xfffff800`0425c670
Debug session time: Mon Sep 5 23:21:09.529 2011 (GMT+8)
System Uptime: 0 days 4:34:56.762
*********************************************************************
* 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
....
Unable to load image \SystemRoot\System32\drivers\dxgmms1.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8801098cb06, fffff880048e9198, fffff880048e89f0}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.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 : dxgmms1.sys ( dxgmms1+2ab06 )
Followup: MachineOwner
---------
UID
125638
帖子
747
精华
0
积分
15288
交易积分
0
阅读权限
1
在线时间
2496 小时
注册时间
2009-4-3
最后登录
2019-11-19
查看详细资料
TOP
dizhang
版主
Live Free or Die
帖子
42792
精华
0
积分
99022
激骚
17555 度
爱车
捷安特
主机
相机
手机
来自
QUASAR
注册时间
2001-8-18
发短消息
加为好友
当前离线
4
#
大
中
小
发表于 2011-9-6 00:04
只看该作者
有可能是内存问题,内存重新拔出来擦干净金手指重插。
另外系统要装MSDN原版的,不要装ghost的那种。
UID
3396
帖子
42792
精华
0
积分
99022
交易积分
1
阅读权限
100
来自
QUASAR
在线时间
28585 小时
注册时间
2001-8-18
最后登录
2024-5-8
查看详细资料
TOP
尖锐湿疣
小黑屋
帖子
747
精华
0
积分
15288
激骚
152 度
爱车
主机
相机
手机
注册时间
2009-4-3
发短消息
加为好友
当前离线
5
#
大
中
小
发表于 2011-9-6 00:05
只看该作者
是原版的。明天拔内存试试
UID
125638
帖子
747
精华
0
积分
15288
交易积分
0
阅读权限
1
在线时间
2496 小时
注册时间
2009-4-3
最后登录
2019-11-19
查看详细资料
TOP
控制面板首页
密码修改
积分交易
积分记录
公众用户组
基本概况
版块排行
主题排行
发帖排行
积分排行
交易排行
在线时间
管理团队
管理统计