閱讀753 返回首頁    go iPhone_iPad_Mac_apple

WIN10玩遊戲時突然藍屏，然後藍屏重啟後進桌麵接著又藍屏了兩次，隻生成了一個DMP文件，求分析&

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff803`12a93000 PsLoadedModuleList = 0xfffff803`12ddf5c0
Debug session time: Mon Sep 11 20:56:45.958 2017 (UTC + 8:00)
System Uptime: 0 days 0:05:06.639
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000066`8c45d018).  Type ".hh dbgerr001" for details
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80312c04834, 0, ffffffffffffffff}

Probably caused by : Unknown_Image ( nt!SwapContext+1e4 )

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

nt!KeBugCheckEx:
fffff803`12bff560 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffb300`d81a8910=000000000000001e
0: 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: fffff80312c04834, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  15063.0.amd64fre.rs2_release.170317-1834

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME:  B250M-D3H

SYSTEM_SKU:  Default string

SYSTEM_VERSION:  Default string

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  F6

BIOS_DATE:  04/24/2017

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  B250M-D3H-CF

BASEBOARD_VERSION:  x.x

DUMP_TYPE:  1

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80312c04834

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS:  ffffffffffffffff 

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

FAULTING_IP: 
nt!SwapContext+1e4
fffff803`12c04834 0fc719          xrstors [rcx]

EXCEPTION_PARAMETER2:  ffffffffffffffff

BUGCHECK_STR:  0x1E_c0000005_R

CPU_COUNT: 4

CPU_MHZ: d50

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R)  SIG: 42'00000000 (cache) 42'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-NMUKADG

ANALYSIS_SESSION_TIME:  09-11-2017 22:32:01.0859

ANALYSIS_VERSION: 10.0.16270.1000 amd64fre

EXCEPTION_RECORD:  0000000000f8004c -- (.exr 0xf8004c)
Cannot read Exception record @ 0000000000f8004c

TRAP_FRAME:  ffffd80af8054988 -- (.trap 0xffffd80af8054988)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffd80af80549b8 rbx=0000000000000000 rcx=ffffd80af80549b8
rdx=ffffd80af7df61e0 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=0000000000000000 rbp=ffffd80af81741a0
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=01d32afcb9b2100d r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na pe nc
00000000`00000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80312abdb7c to fffff80312bff560

STACK_TEXT:  
ffffb300`d81a8908 fffff803`12abdb7c : 00000000`0000001e ffffffff`c0000005 fffff803`12c04834 00000000`00000000 : nt!KeBugCheckEx
ffffb300`d81a8910 fffff803`12c0a98e : 00000000`00f8004c ffffd80a`f7d9aad0 ffffd80a`f8054988 ffffb300`d81a0000 : nt!KiDispatchException+0x23c
ffffb300`d81a8fc0 fffff803`12c08c34 : 00000010`00000000 ffffffff`00000010 00000003`00000006 ffffd80a`00000000 : nt!KiExceptionDispatch+0xce
ffffb300`d81a91a0 fffff803`12c04834 : ffffb300`d81a9608 fffff803`12f3731b ffffc58c`80f29040 00000000`01000002 : nt!KiGeneralProtectionFault+0xf4
ffffb300`d81a9330 fffff803`32c04396 : ffffb300`d81a9490 ffffb300`f81a9608 00000000`00000010 00000000`00000000 : nt!SwapContext+0x1e4
ffffb300`d81a9370 ffffb300`d81a9490 : ffffb300`f81a9608 00000000`00000010 00000000`00000000 ffffb300`00000010 : 0xfffff803`32c04396
ffffb300`d81a9378 ffffb300`f81a9608 : 00000000`00000010 00000000`00000000 ffffb300`00000010 00000000`00000000 : 0xffffb300`d81a9490
ffffb300`d81a9380 00000000`00000010 : 00000000`00000000 ffffb300`00000010 00000000`00000000 00000000`00000000 : 0xffffb300`f81a9608
ffffb300`d81a9388 00000000`00000000 : ffffb300`00000010 00000000`00000000 00000000`00000000 00000000`00000000 : 0x10


THREAD_SHA1_HASH_MOD_FUNC:  4bafef5224e4e4de236896b191e27930d24dfadd

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  3ceb0378cf2888b5e101d88d31be5cf5b58792c7

THREAD_SHA1_HASH_MOD:  f08ac56120cad14894587db086f77ce277bfae84

FOLLOWUP_IP: 
nt!SwapContext+1e4
fffff803`12c04834 0fc719          xrstors [rcx]

FAULT_INSTR_CODE:  eb19c70f

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!SwapContext+1e4

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

MODULE_NAME: Unknown_Module

BUCKET_ID:  RAISED_IRQL_USER_FAULT_0x1E_c0000005_R

DEFAULT_BUCKET_ID:  RAISED_IRQL_USER_FAULT_0x1E_c0000005_R

PRIMARY_PROBLEM_CLASS:  RAISED_IRQL_USER_FAULT_0x1E_c0000005_R

FAILURE_BUCKET_ID:  RAISED_IRQL_USER_FAULT_0x1E_c0000005_R

TARGET_TIME:  2017-09-11T12:56:45.000Z

OSBUILD:  15063

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2017-08-01 09:23:25

BUILDDATESTAMP_STR:  170317-1834

BUILDLAB_STR:  rs2_release

BUILDOSVER_STR:  10.0.15063.0.amd64fre.rs2_release.170317-1834

ANALYSIS_SESSION_ELAPSED_TIME:  3e3

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:raised_irql_user_fault_0x1e_c0000005_r

FAILURE_ID_HASH:  {d1e1826c-605d-7a79-a04d-b8220695ad88}

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

最後更新：2017-09-11 23:02:50

  上一篇：go 最近使用的項目
  下一篇：go 美版Windows 10 Home能否激活簡體中文版Windows 10？