閱讀1030 返回首頁    go 微軟 go windows

WIN8.1 每天玩DNF的時候 都有會突然藍屏死機 DUMP分析了 有沒有大神看一下分析問題 十分感謝~~

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


Loading Dump File [C:\Users\raystalie\Desktop\102217-11343-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.18685.amd64fre.winblue_ltsb.170427-1704
Machine Name:
Kernel base = 0xfffff801`96403000 PsLoadedModuleList = 0xfffff801`966d6670
Debug session time: Sun Oct 22 13:54:51.062 2017 (UTC + 8:00)
System Uptime: 1 days 2:42:49.490
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
..............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffe000849ae000, 0, fffff8019687a66e, 0}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------

6: 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: ffffe000849ae000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8019687a66e, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: fffff801966c4060: Unable to get special pool info
fffff801966c4060: Unable to get special pool info
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 ffffe000849ae000 

FAULTING_IP: 
nt!PspWow64ReadOrWriteThreadCpuArea+13e
fffff801`9687a66e 0f284360        movaps  xmm0,xmmword ptr [rbx+60h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

PROCESS_NAME:  dnf.exe

CURRENT_IRQL:  0

TRAP_FRAME:  ffffd0002aaa5bb0 -- (.trap 0xffffd0002aaa5bb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000004 rbx=0000000000000000 rcx=00007fffffff0000
rdx=ffffd00065139180 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8019687a66e rsp=ffffd0002aaa5d40 rbp=ffffd0002aaa6620
 r8=0000000000000006  r9=ffffd0002aaa6670 r10=0000000000000000
r11=fffff8019655de8f r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!PspWow64ReadOrWriteThreadCpuArea+0x13e:
fffff801`9687a66e 0f284360        movaps  xmm0,xmmword ptr [rbx+60h] ds:de8f:00000000`00000060=????????????????????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8019658dc9c to fffff801965512a0

STACK_TEXT:  
ffffd000`2aaa5948 fffff801`9658dc9c : 00000000`00000050 ffffe000`849ae000 00000000`00000000 ffffd000`2aaa5bb0 : nt!KeBugCheckEx
ffffd000`2aaa5950 fffff801`964467a9 : 00000000`00000000 ffffe000`7b0ff8c0 ffffd000`2aaa5bb0 ffffc001`cf226770 : nt! ?? ::FNODOBFM::`string'+0x2c4cc
ffffd000`2aaa59f0 fffff801`9655b52f : 00000000`00000000 ffffe000`849adfa0 ffffd000`2aaa5c00 ffffd000`2aaa5d10 : nt!MmAccessFault+0x769
ffffd000`2aaa5bb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x12f


STACK_COMMAND:  .bugcheck ; kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80196551543-fffff80196551550  14 bytes - nt!KiRestoreProcessorControlState+23
[ 0f 01 59 66 0f b7 41 70:68 00 20 8f c7 c7 44 24 ]
    fffff801965515fa-fffff80196551607  14 bytes - nt!KiSaveProcessorControlState+2a (+0xb7)
[ 0f 01 49 66 0f 00 49 70:68 00 10 90 c7 c7 44 24 ]
28 errors : !nt (fffff80196551543-fffff80196551607)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

Followup: memory_corruption
---------

6: kd> g
       ^ No runnable debuggees error in 'g'

最後更新：2017-10-22 15:03:32

  上一篇：go 升級win10後，1、打開文件夾緩慢，要麼顯示“正在處理它”，
  下一篇：go 關於Windows10 設置