积极答复者
Windows Server 2008 R2 服务器蓝屏 代码0x00000124 请高手帮忙看看 附上蓝屏dmp

问题
-
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [E:\系统更新\开机通道\Win7\052414-29374-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`01865000 PsLoadedModuleList = 0xfffff800`01aa9670
Debug session time: Sat May 24 15:24:26.845 2014 (UTC + 8:00)
System Uptime: 4 days 19:56:07.828
Loading Kernel Symbols
...............................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {5, fffffa80321e1028, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000005, Generic Error
Arg2: fffffa80321e1028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x124_5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
PROCESS_NAME: System
CURRENT_IRQL: f
STACK_TEXT:
fffff800`05f5bbf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_5_PCIEXPRESS
BUCKET_ID: X64_0x124_5_PCIEXPRESS
Followup: MachineOwner
---------
0: kd> !process
GetPointerFromAddress: unable to read from fffff80001b13000
PROCESS fffffa8031040040
SessionId: none Cid: 0004 Peb: 00000000 ParentCid: 0000
DirBase: 00187000 ObjectTable: fffff8a000001840 HandleCount: <Data Not Accessible>
Image: System
VadRoot fffffa803204bc70 Vads 5 Clone 0 Private 8. Modified 34058800. Locked 0.
DeviceMap fffff8a000008a70
Token fffff8a000004bf0
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
fffff78000000000: Unable to get shared data
ElapsedTime 00:00:00.000
UserTime 00:00:00.000
KernelTime 00:00:00.000
QuotaPoolUsage[PagedPool] 0
QuotaPoolUsage[NonPagedPool] 0
Working Set Sizes (now,min,max) (91, 0, 0) (364KB, 0KB, 0KB)
PeakWorkingSetSize 6911
VirtualSize 3 Mb
PeakVirtualSize 29 Mb
PageFaultCount 35905
MemoryPriority BACKGROUND
BasePriority 8
CommitCharge 28
*** Error in reading nt!_ETHREAD @ fffffa8031040b50- 已编辑 greedyo 2014年5月26日 12:26
答案
-
你好!
请参考以下步骤来检查:
1. 首先请检查PC是否有过热现象, 因为很多时候过热会导致BSOD.
2. 从错误上看可能是硬件的问题,请用一些检测硬件的工具检查硬件是否存在问题,特别对于在问题出现前有变动的硬件, 尝试替换有可能出现问题的硬件。
3. 是否安装了与Windows不兼容的硬件,你可以通过官方网站来检测:
http://www.microsoft.com/en-us/windows/compatibility/CompatCenter/Home
另外,我建议你可以联系微软的CSS来帮助你更专业地分析Dump文件:
http://support.microsoft.com/gp/profsup/en-au
希望能有所帮助。
- 已标记为答案 AnnaWYModerator 2014年6月3日 9:11