閱讀163 返回首頁    go 阿裏雲 go 技術社區[雲棲]


Windows 2008 R2 頻繁DUMP藍屏

請教各位,最近有一台HP 380G5的老機器頻繁藍屏,DUMP文件如下,請各位大神 分析一下,非常感謝:


Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\kongweiwei\Desktop\11.37MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*C:\Symbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`01661000 PsLoadedModuleList = 0xfffff800`0189ee50
Debug session time: Thu May  4 22:29:28.525 2017 (UTC + 8:00)
System Uptime: 1 days 5:34:01.341
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols

Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa800c611000, 1, fffff880065417f5, 0}

Probably caused by : srv.sys ( srv!SrvOs2FeaToNt+45 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa800c611000, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff880065417f5, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------


WRITE_ADDRESS:  fffffa800c611000 

FAULTING_IP: 
srv!SrvOs2FeaToNt+45
fffff880`065417f5 c60300          mov     byte ptr [rbx],0

MM_INTERNAL_CODE:  0

IMAGE_NAME:  srv.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc257

MODULE_NAME: srv

FAULTING_MODULE: fffff880064d5000 srv

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880062518a0 -- (.trap 0xfffff880062518a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800c611000 rbx=0000000000000000 rcx=fffffa800c611000
rdx=fffffe1ff9c42099 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880065417f5 rsp=fffff88006251a30 rbp=fffff88006251b60
 r8=0000000000000000  r9=0000000000000000 r10=5a2f423231393436
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
srv!SrvOs2FeaToNt+0x45:
fffff880`065417f5 c60300          mov     byte ptr [rbx],0 ds:0001:00000000`00000000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800017521e4 to fffff800016d2f00

STACK_TEXT:  
fffff880`06251738 fffff800`017521e4 : 00000000`00000050 fffffa80`0c611000 00000000`00000001 fffff880`062518a0 : nt!KeBugCheckEx
fffff880`06251740 fffff800`016d0fee : 00000000`00000001 fffffa80`0c611000 000001df`ff106b00 00000000`00001000 : nt! ?? ::FNODOBFM::`string'+0x42907
fffff880`062518a0 fffff880`065417f5 : fffff880`06251b78 fffff8a0`06243114 fffff8a0`06243138 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`06251a30 fffff880`06543c36 : fffff8a0`06253095 fffff8a0`06253095 fffff880`06251b60 00000000`00000000 : srv!SrvOs2FeaToNt+0x45
fffff880`06251a60 fffff880`0655c1d8 : fffffa80`05369680 fffff8a0`06243114 fffff8a0`06243010 00000000`00000000 : srv!SrvOs2FeaListToNt+0xc6
fffff880`06251ab0 fffff880`06521235 : 00000000`00000000 fffff880`00000000 00000000`00010fe8 fffffa80`0c600010 : srv!SrvSmbOpen2+0xc8
fffff880`06251b60 fffff880`065645f7 : fffff8a0`06243010 fffffa80`04f3b240 00000000`0000ff00 fffff880`064f2110 : srv!ExecuteTransaction+0xc5
fffff880`06251ba0 fffff880`064d7698 : 00000000`00000000 fffff880`00000000 fffffa80`00000035 fffff880`0000f3d0 : srv!SrvSmbTransactionSecondary+0x3f7
fffff880`06251c30 fffff880`064d75b3 : fffffa80`05369680 00000000`00000006 00000000`00000002 fffffa80`05369680 : srv!SrvProcessSmb+0xb8
fffff880`06251cb0 fffff880`0651c6a3 : fffffa80`052ac020 00000000`00000003 fffffa80`0a4e4010 fffffa80`05369690 : srv!SrvRestartReceive+0xa3
fffff880`06251cf0 fffff800`01976166 : fffffa80`05369680 fffffa80`04f9b040 00000000`00000080 fffffa80`039a2890 : srv!WorkerThread+0xed
fffff880`06251d40 fffff800`016b1486 : fffff800`0184be80 fffffa80`04f9b040 fffffa80`04f6e060 fffff880`01466534 : nt!PspSystemThreadStartup+0x5a
fffff880`06251d80 00000000`00000000 : fffff880`06252000 fffff880`0624c000 fffff880`062519f0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
srv!SrvOs2FeaToNt+45
fffff880`065417f5 c60300          mov     byte ptr [rbx],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  srv!SrvOs2FeaToNt+45

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x50_srv!SrvOs2FeaToNt+45

BUCKET_ID:  X64_0x50_srv!SrvOs2FeaToNt+45

Followup: MachineOwner
---------



最後更新:2017-05-12 10:46:24

  上一篇:go 升級到1703後nvdia experience自動更新出現權限問題。
  下一篇:go 電腦更新後黑屏無信號