阅读96 返回首页    go 微软 go windows

win10游戏时蓝屏

玩游戏时频繁蓝屏，不知道什么原因 dmp文档如下

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


Loading Dump File [C:\Windows\Minidump\092117-4453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*D:\mysymbol*https://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.1715.amd64fre.rs1_release_inmarket.170906-1810
Machine Name:
Kernel base = 0xfffff800`d3e05000 PsLoadedModuleList = 0xfffff800`d4103040
Debug session time: Thu Sep 21 21:15:47.058 2017 (UTC + 8:00)
System Uptime: 0 days 0:59:51.803
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffffffffffff, 0, fffffddc6b88aef5, 0}


Could not read faulting driver name
Probably caused by : memory_corruption

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

 *** Memory manager detected 81357 instance(s) of page corruption, target is likely to have memory corruption.

5: 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: ffffffffffffffff, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffffddc6b88aef5, 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: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 ffffffffffffffff

FAULTING_IP:
win32kfull!xxxInterSendMsgEx+1765
fffffddc`6b88aef5 488b7bff        mov     rdi,qword ptr [rbx-1]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

PROCESS_NAME:  memtest.exe

CURRENT_IRQL:  2

BAD_PAGES_DETECTED: 13dcd

LAST_CONTROL_TRANSFER:  from fffff800d3f7eaae to fffff800d3f548b0

STACK_TEXT:  
ffffd901`18666188 fffff800`d3f7eaae : 00000000`00000050 ffffffff`ffffffff 00000000`00000000 ffffd901`18666480 : nt!KeBugCheckEx
ffffd901`18666190 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiSystemFault+0x10004e


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32kfull
8 errors : !win32kfull (fffffddc6b88aec7-fffffddc6b88aeff)
fffffddc6b88aec0  db  74  32  48  8b  cb  ff *89  ec  b6  2c  00  85  c0  74 *6c .t2H......,...tl
fffffddc6b88aed0  48  89  5c  24  28  4c  89 *26  24  20  4c  8d  8c  24  78 *f5 H.\$(L.&$ L..$x.
fffffddc6b88aee0  00  00  4c  8d  84  24  70 *f0  00  00  8d  56  01  41  8b *62 ..L..$p....V.A.b
fffffddc6b88aef0  e8  6b  c7  ff  ff  48  8b *7b  ff  15  5a  9b  2c  00  48 *74 .k...H.{..Z.,.Ht

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

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

 *** Memory manager detected 81357 instance(s) of page corruption, target is likely to have memory corruption.

5: kd> .reload
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
......................

最后更新：2017-09-22 00:02:39

  上一篇：go .net framework崩溃了
  下一篇：go 激活疑难解答无法使用