2003服务器开机无限重启,Windows2003 系统自动重启

各位好，

我有台服务器这两天老是自动重启，分析DMP文件如下，请问各位有什么好的意见或者办法解决。谢谢。之前是不停的蓝屏后来修复系统变成不停的重启。

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86

Copyright (c) Microsoft Corporation. All rights reserved.

Unable to load image \WINDOWS\system32\ntoskrnl.exe, Win32 error 0n2

*** WARNING: symbols timestamp is wrong 0x4b7abd06 0x427b58bb for ntoskrnl.exe

Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (8 procs) Free x64

Product: Server, suite: Enterprise TerminalServer SingleUserTS StorageServer

Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140

Debug session time: Thu Feb 23 21:47:34.420 2012 (GMT+8)

System Uptime: 3 days 11:10:44.264

Unable to load image \WINDOWS\system32\ntoskrnl.exe, Win32 error 0n2

*** WARNING: symbols timestamp is wrong 0x4b7abd06 0x427b58bb for ntoskrnl.exe

Loading Kernel Symbols

.................................................................................................................................

Loading User Symbols

Loading unloaded module list

....

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa800be4e670, fffffa800be4e6e0, 6070167}

GetUlongFromAddress: unable to read from fffff80001074b88

Probably caused by :ntoskrnl.exe( nt!KeContextToKframes+1a4 )

Followup: MachineOwner

---------

4: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

BAD_POOL_HEADER (19)

The pool is already corrupt at the time of the current request.

This may or may not be due to the caller.

The internal pool links must be walked to figure out a possible cause of

the problem, and then special pool applied to the suspect tags or the driver

verifier to a suspect driver.

Arguments:

Arg1: 0000000000000020, a pool block header size is corrupt.

Arg2: fffffa800be4e670, The pool entry we were looking for within the page.

Arg3: fffffa800be4e6e0, The next pool entry.

Arg4: 0000000006070167, (reserved)

Debugging Details:

------------------

GetUlongFromAddress: unable to read from fffff80001074b88

BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  fffffa800be4e670

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:

DRIVER_FAULT_SERVER_MINIDUMP

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8000102e890

STACK_TEXT:

fffffadf`891c3f78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeContextToKframes+0x1a4

STACK_COMMAND:  kb

FOLLOWUP_IP:

nt!KeContextToKframes+1a4

fffff800`0102e890 48894c2408      mov     qword ptr [rsp+8],rcx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KeContextToKframes+1a4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b7abd06

FAILURE_BUCKET_ID:  X64_0x19_20_nt!KeContextToKframes+1a4

BUCKET_ID:  X64_0x19_20_nt!KeContextToKframes+1a4

Followup: MachineOwner

---------

4: kd> q

quit: