|
本帖最后由 blueelf 于 2011-2-7 18:15 编辑
[tr][td] [/td][td] 旧电脑[/td][td]新电脑 [/td][td]新配件价格 [/td][/tr]
[tr][td]键鼠[/td][td]多彩套装[/td][td]---- [/td][td] [/td][/tr]
[tr][td]显示器 [/td][td]BenQ21.5[/td][td]----[/td][td] [/td][/tr]
[tr][td]机箱[/td][td]百盛[/td][td]----[/td][td] [/td][/tr]
[tr][td]电源[/td][td]世纪之星自由战士2[/td][td]酷冷至尊eXtremePowerPlus 战斧400W电源 2.3版[/td][td]259(**)[/td][/tr]
[tr][td]主板[/td][td]升技 NF7[/td][td]DFI LP DK790FXB-M2RSH[/td][td]599(GZ团购)[/td][/tr]
[tr][td]CPU[/td][td]闪龙1800+[/td][td]包开四核 AMD5000 包开4核 默电超3G 4钻真情回馈 一年质保[/td][td]274(淘宝)[/td][/tr]
[tr][td]CPU风扇 [/td][td]原装[/td][td]超频三(pccooler)红海标准版[/td][td]59(**)[/td][/tr]
[tr][td]内存[/td][td]金士顿2x512M[/td][td]镁光Ballistix PC2 DDR2 800 2G红板带灯条,默电2.2V 1000MHZ X 2[/td][td]258x2+12(淘宝)[/td][/tr]
[tr][td]显卡 [/td][td]MSI9550小强版[/td][td]蓝宝石 HD3850 512M/256BIT 320处理器DX10.1游戏高清[/td][td]310+12(淘宝)[/td][/tr]
[tr][td]硬盘[/td][td]迈拓80G[/td][td]希捷(Seagate)500G ST3500418AS 7200转16M SATAII 台式机硬盘 三年免费质保[/td][td]309(**)[/td][/tr]
[tr][td]光驱[/td][td]三星DVD-RW[/td][td]----[/td][td] [/td][/tr]
电脑是升级过来的,用开核版BIOS,也从未超频,系统是XP
现在双核版本BIOS也是这个现象
2个硬盘是一块挂着,用的是NATIVE IDE模式
现在已经无法开机,要么停在第一屏,要么还未键入密码进XP就蓝屏
1、开机的时候会经常停在自检完毕,第一屏全部显示完毕,然后卡住,不显示第二屏
自检信息完整,“按DEL进入BIOS” 消失后卡住
即使断电也如此
刷BIOS亦无法解决此问题
2、一直被DFI的蓝屏折磨着
刷了无数次的BIOS均无法解决
主要刷的是 开核版本的R7SD820A.rar和官方网的R7SDA08.rar
icrosoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini020710-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 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 XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055d700
Debug session time: Sun Feb 7 11:25:39.953 2010 (GMT+8)
System Uptime: 0 days 0:00:19.656
*********************************************************************
* 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 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
..
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {8047bd18, 0, 805cb0c0, 0}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+f30c0 )
Followup: MachineOwner
---------
|
|