depl服务器做系统开机蓝屏,系统蓝屏请分析dump文件出现蓝屏的具体原因是什么...

尊敬的工程师们，你们好：

我的电脑好几天都会出现蓝屏，用Windows Debugging Tool分析后，出现以下信息，请帮忙分析一下导致蓝屏主要的原因：

Windows Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506

Kernel base = 0xfffff800`04e16000 PsLoadedModuleList = 0xfffff800`05059890

Debug session time: Sat Nov  1 22:36:28.869 2014 (GMT+8)

System Uptime: 0 days 0:22:10.947

Loading Kernel Symbols

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

Loading User Symbols

Loading unloaded module list

.....

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

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {8, 2, 0, fffff80004f4776b}

Probably caused by : memory_corruption ( nt!MiStoreSetEvictPageFile+b )

Followup: MachineOwner

---------

0: kd> !analyze -v

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

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

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

IRQL_NOT_LESS_OR_EQUAL (a)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high.  This is usually

caused by drivers using improper addresses.

If a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: 0000000000000008, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, bitfield :

bit 0 : value 0 = read operation, 1 = write operation

bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)

Arg4: fffff80004f4776b, address which referenced memory

Debugging Details:

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

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800050c3100

0000000000000008

CURRENT_IRQL:  2

FAULTING_IP:

nt!MiStoreSetEvictPageFile+b

fffff800`04f4776b 488b5008        mov     rdx,qword ptr [rax+8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880047ff8d0 -- (.trap 0xfffff880047ff8d0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80050c48c0

rdx=0000000001600160 rsi=0000000000000000 rdi=0000000000000000

rip=fffff80004f4776b rsp=fffff880047ffa68 rbp=0000000001600160

r8=0000000001600160  r9=0000000000000002 r10=0000000000000000

r11=0000058000000000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up ei pl zr na po nc

nt!MiStoreSetEvictPageFile+0xb:

fffff800`04f4776b 488b5008        mov     rdx,qword ptr [rax+8] ds:00000000`00000008=????????????????

Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80004e8b169 to fffff80004e8bbc0

STACK_TEXT:

fffff880`047ff788 fffff800`04e8b169 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

fffff880`047ff790 fffff800`04e89de0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69

fffff880`047ff8d0 fffff800`04f4776b : fffff800`04f48cac fffff8a0`0456f920 00000000`00000001 fffffa80`050c48c0 : nt!KiPageFault+0x260

fffff880`047ffa68 fffff800`04f48cac : fffff8a0`0456f920 00000000`00000001 fffffa80`050c48c0 fa8005a3`c09004c0 : nt!MiStoreSetEvictPageFile+0xb

fffff880`047ffa70 fffff800`04ef5861 : 01600160`01600160 00000000`00000000 01600160`01600160 fffff800`05183036 : nt!MiReleaseConfirmedPageFileSpace+0x7c

fffff880`047ffaf0 fffff800`0512b9db : fffffa80`05a3c010 00000000`00000000 00000000`00088081 fffffa80`05adcaa0 : nt! ?? ::FNODOBFM::`string'+0x2ad5d

fffff880`047ffbc0 fffff800`04ed8311 : fffffa80`05a3c018 00000000`00000001 00000000`00000000 00000000`00000631 : nt!MiSegmentDelete+0x7b

fffff880`047ffc00 fffff800`04ed81d5 : 00000000`00000000 00000000`00000080 fffffa80`02adb400 fffffa80`00000012 : nt!MiProcessDereferenceList+0x131

fffff880`047ffcc0 fffff800`0512773a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDereferenceSegmentThread+0x10d

fffff880`047ffd40 fffff800`04e7c8e6 : fffff800`05006e80 fffffa80`02b08260 fffff800`05014cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a

fffff880`047ffd80 00000000`00000000 : fffff880`04800000 fffff880`047fa000 fffff880`047ff7f0 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND:  kb

FOLLOWUP_IP:

nt!MiStoreSetEvictPageFile+b

fffff800`04f4776b 488b5008        mov     rdx,qword ptr [rax+8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiStoreSetEvictPageFile+b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  53b9f073

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiStoreSetEvictPageFile+b

BUCKET_ID:  X64_0xA_nt!MiStoreSetEvictPageFile+b

Followup: MachineOwner

---------