閱讀243 返回首頁    go windows

係統重啟藍屏

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


Loading Dump File [C:\Users\Chen\Desktop\dmp\092217-5968-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 14393.1715.amd64fre.rs1_release_inmarket.170906-1810
Machine Name:
Kernel base = 0xfffff800`51616000 PsLoadedModuleList = 0xfffff800`51914040
Debug session time: Fri Sep 22 11:39:08.620 2017 (UTC + 8:00)
System Uptime: 0 days 0:00:12.526
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

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

Use !analyze -v to get detailed debugging information.

BugCheck EF, {ffffc08adaff4780, 0, 0, 0}

ETW minidump data unavailable
Probably caused by : ntkrnlmp.exe ( nt!PspCatchCriticalBreak+d6 )

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

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

CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffffc08adaff4780, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

ETW minidump data unavailable

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  14393.1715.amd64fre.rs1_release_inmarket.170906-1810

SYSTEM_MANUFACTURER:  MECHREVO

SYSTEM_PRODUCT_NAME:  X6Ti Series

SYSTEM_SKU:  To be filled by O.E.M.

SYSTEM_VERSION:  To be filled by O.E.M.

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  N.1.00

BIOS_DATE:  07/29/2016

BASEBOARD_MANUFACTURER:  MECHREVO

BASEBOARD_PRODUCT:  X6Ti Series

BASEBOARD_VERSION:  0.1

DUMP_TYPE:  2

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_P1: ffffc08adaff4780

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME:  svchost.exe

CRITICAL_PROCESS:  svchost.exe

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

ERROR_CODE: (NTSTATUS) 0xdb094080 - <Unable to get error code text>

CPU_COUNT: 8

CPU_MHZ: a20

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: 7C'00000000 (cache) 7C'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0xEF

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-TK1NB3G

ANALYSIS_SESSION_TIME:  09-22-2017 21:53:17.0373

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

LAST_CONTROL_TRANSFER:  from fffff80051c8e99a to fffff800517658b0

STACK_TEXT:  
ffffaa80`9c3098f8 fffff800`51c8e99a : 00000000`000000ef ffffc08a`daff4780 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffaa80`9c309900 fffff800`51bb05b3 : ffffc08a`daff4780 ffffc08a`db094460 00000000`00000000 ffffc08a`db094080 : nt!PspCatchCriticalBreak+0xd6
ffffaa80`9c309960 fffff800`51ab2509 : ffffc08a`00000002 ffffc08a`daff4780 ffffc08a`db094460 00000000`00000000 : nt!PspTerminateAllThreads+0x1460b3
ffffaa80`9c3099d0 fffff800`51ab22c0 : ffffc08a`daff4780 00000000`c0000005 ffffc08a`daff4780 ffffc08a`db094080 : nt!PspTerminateProcess+0x101
ffffaa80`9c309a10 fffff800`51770593 : ffffc08a`daff4780 ffffc08a`db094080 ffffaa80`9c309b00 00000000`00000003 : nt!NtTerminateProcess+0x9c
ffffaa80`9c309a80 00007ffa`a50b6624 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000087`0e57fca8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`a50b6624


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  042a2b51772309c39e12d732cc93cacf0af3064e

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  2ff63c5e69f4ee7227a08670ea945f65a8b0a24a

THREAD_SHA1_HASH_MOD:  ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

FOLLOWUP_IP: 
nt!PspCatchCriticalBreak+d6
fffff800`51c8e99a cc              int     3

FAULT_INSTR_CODE:  ff8440cc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PspCatchCriticalBreak+d6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  59b0d121

IMAGE_VERSION:  10.0.14393.1715

BUCKET_ID_FUNC_OFFSET:  d6

FAILURE_BUCKET_ID:  0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_db094080_nt!PspCatchCriticalBreak

BUCKET_ID:  0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_db094080_nt!PspCatchCriticalBreak

PRIMARY_PROBLEM_CLASS:  0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_db094080_nt!PspCatchCriticalBreak

TARGET_TIME:  2017-09-22T03:39:08.000Z

OSBUILD:  14393

OSSERVICEPACK:  1715

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2017-09-07 12:54:57

BUILDDATESTAMP_STR:  170906-1810

BUILDLAB_STR:  rs1_release_inmarket

BUILDOSVER_STR:  10.0.14393.1715.amd64fre.rs1_release_inmarket.170906-1810

ANALYSIS_SESSION_ELAPSED_TIME:  7a2

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xef_svchost.exe_bugcheck_critical_process_db094080_nt!pspcatchcriticalbreak

FAILURE_ID_HASH:  {540d4921-5761-d9e5-9136-49b8c9076d59}

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

最後更新：2017-09-23 03:03:39

  上一篇：go 藍屏日誌可以看一下嗎
  下一篇：go windows defender中的應用和瀏覽器控製出現問題