莫名其妙就频繁重启了,打了SP1也不起作用,仍然频繁重启,大神帮忙分析下dump。
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\y16249.H3C\Desktop\临时文件夹\20180620\fljflfg-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*DownstreamStore****.***/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.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`01457000 PsLoadedModuleList = 0xfffff800`0169ce90
Debug session time: Wed Jun 20 17:02:01.937 2018 (UTC + 8:00)
System Uptime: 0 days 10:22:11.015
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffffae0039de010, 1, 3e5b2b92}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4987d )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffffae0039de010, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 000000003e5b2b92, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
FAULTING_IP:
+6465323236383137
fffffae0`039de010 ?? ???
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 000000003e5b2b92
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800017080e8
000000003e5b2b92
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx
BUGCHECK_STR: 0x1E_c0000005
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff88004b58800 -- (.trap 0xfffff88004b58800)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffae0039c2000 rbx=0000000000000000 rcx=0000000000000000
rdx=000000004131c372 rsi=0000000000000000 rdi=0000000000000000
rip=fffffae0039de010 rsp=fffff88004b58998 rbp=fffffae002e55000
r8=fffffae003444450 r9=fffff8a006198010 r10=00000000fffffffc
r11=fffff8a00619811c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
fffffae0`039de010 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80001523028 to fffff800014d7640
STACK_TEXT:
fffff880`04b57f78 fffff800`01523028 : 00000000`0000001e ffffffff`c0000005 fffffae0`039de010 00000000`00000001 : nt!KeBugCheckEx
fffff880`04b57f80 fffff800`014d6cc2 : fffff880`04b58758 00000000`0050f000 fffff880`04b58800 fffffae0`039c2000 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`04b58620 fffff800`014d583a : 00000000`00000001 00000000`3e5b2b92 fffffae0`039c2000 00000000`0050f000 : nt!KiExceptionDispatch+0xc2
fffff880`04b58800 fffffae0`039de010 : fffffae0`02e5517a 00000000`00000000 fffffae0`0240ec50 fffff880`030edcf0 : nt!KiPageFault+0x23a
fffff880`04b58998 fffffae0`02e5517a : 00000000`00000000 fffffae0`0240ec50 fffff880`030edcf0 fffffae0`0240ec50 : 0xfffffae0`039de010
fffff880`04b589a0 00000000`00000000 : fffffae0`0240ec50 fffff880`030edcf0 fffffae0`0240ec50 fffff8a0`00000002 : 0xfffffae0`02e5517a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4987d
fffff800`01523028 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4987d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a
FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+4987d
BUCKET_ID: X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+4987d
Followup: MachineOwner
---------
3: kd> !process
GetPointerFromAddress: unable to read from fffff80001708000
PROCESS fffffae000ec79e0
SessionId: none Cid: 0004 Peb: 00000000 ParentCid: 0000
DirBase: 00187000 ObjectTable: fffff8a000001940 HandleCount: <Data Not Accessible>
Image: System
VadRoot fffffae0012aa850 Vads 5 Clone 0 Private 8. Modified 41181. Locked 0.
DeviceMap fffff8a000008b30
Token fffff8a000004040
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 1423
VirtualSize 3 Mb
PeakVirtualSize 8 Mb
PageFaultCount 12028
MemoryPriority BACKGROUND
BasePriority 8
CommitCharge 28
*** Error in reading nt!_ETHREAD @ fffffae000ec7460
(0)
暂无评论
亲~登录后才可以操作哦!
确定你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作
举报
×
侵犯我的权益
×
侵犯了我企业的权益
×
抄袭了我的内容
×
原文链接或出处
诽谤我
×
对根叔社区有害的内容
×
不规范转载
×
举报说明
暂无评论