閱讀572 返回首頁    go windows

可以幫忙看一下藍屏原因嗎


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


Loading Dump File [C:\Users\mx\Desktop\092217-6093-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.1715.amd64fre.rs1_release_inmarket.170906-1810
Machine Name:
Kernel base = 0xfffff803`52e91000 PsLoadedModuleList = 0xfffff803`5318f040
Debug session time: Fri Sep 22 21:54:32.961 2017 (UTC + 8:00)
System Uptime: 0 days 10:26:53.799
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 139, {2, ffffa801fa7edc90, ffffa801fa7edbe8, 0}

*** ERROR: Module load completed but symbols could not be loaded for NTFS.sys
Probably caused by : memory_corruption

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

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

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000002, Stack cookie instrumentation code detected a stack-based
buffer overrun.
Arg2: ffffa801fa7edc90, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffa801fa7edbe8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.14393.1715 (rs1_release_inmarket.170906-1810)

SYSTEM_MANUFACTURER:  Hasee Computer

SYSTEM_PRODUCT_NAME:  CP75S

SYSTEM_SKU:  Not Applicable                  

SYSTEM_VERSION:  Not Applicable                  

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1.05.01

BIOS_DATE:  07/13/2016

BASEBOARD_MANUFACTURER:  Notebook                        

BASEBOARD_PRODUCT:  P7xxDM2(-G)                     

BASEBOARD_VERSION:  Not Applicable                  

DUMP_TYPE:  2

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_P1: 2

BUGCHECK_P2: ffffa801fa7edc90

BUGCHECK_P3: ffffa801fa7edbe8

BUGCHECK_P4: 0

TRAP_FRAME:  ffffd1834af00b4f -- (.trap 0xffffd1834af00b4f)
Unable to read trap frame at ffffd183`4af00b4f

EXCEPTION_RECORD:  ffffa801f0aed100 -- (.exr 0xffffa801f0aed100)
Cannot read Exception record @ ffffa801f0aed100

CPU_COUNT: 4

CPU_MHZ: a98

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

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

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x139

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

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

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

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000002

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

WATSON_BKT_EVENT:  BEX

ANALYSIS_SESSION_HOST:  MX

ANALYSIS_SESSION_TIME:  09-23-2017 18:27:11.0957

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

LAST_CONTROL_TRANSFER:  from fffff80352feba29 to fffff80352fe08b0

FAULTING_THREAD:  0000000000000000

STACK_TEXT:  
ffffa801`fa7ed968 fffff803`52feba29 : 00000000`00000139 00000000`00000002 ffffa801`fa7edc90 ffffa801`fa7edbe8 : nt!KeBugCheckEx
ffffa801`fa7ed970 fffff803`52febd90 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff803`52eca4a1 : nt!KiBugCheckDispatch+0x69
ffffa801`fa7edab0 fffff803`52fead73 : ffffa801`fa7edf70 fffff803`52e1e277 ffffffff`ffd01a58 00000000`0000002f : nt!KiFastFailDispatch+0xd0
ffffa801`fa7edc90 fffff80c`3ec700c5 : fffff80c`3ec47616 fffff803`532305f0 fffff803`52f3b6d4 fffff80c`3ecdb71c : nt!KiRaiseSecurityCheckFailure+0xf3
ffffa801`fa7ede28 fffff80c`3ec47616 : fffff803`532305f0 fffff803`52f3b6d4 fffff80c`3ecdb71c fffff803`52e91000 : NTFS+0x500c5
ffffa801`fa7ede30 fffff803`52fe6cad : ffffa801`fa7f0000 ffffa801`fa7edf90 00000000`00000000 ffffa801`fa7e9000 : NTFS+0x27616
ffffa801`fa7ede60 fffff803`52f3a301 : ffffa801`fa7f0000 00000000`00000000 ffffa801`fa7e9000 fffff803`52fe56c6 : nt!RtlpExecuteHandlerForException+0xd
ffffa801`fa7ede90 fffff803`52f39077 : ffffa801`fa7eed88 ffffa801`fa7eeac0 ffffa801`fa7eed88 00000000`0010001f : nt!RtlDispatchException+0x421
ffffa801`fa7ee590 fffff803`52febb0e : ffffa801`f0aed100 00000000`00000000 ffffd183`4af00b4f ffffd183`4af5e9f8 : nt!KiDispatchException+0x1d7
ffffa801`fa7eec50 fffff803`52fe9fe1 : 00000000`00000006 00000000`00000011 9b93a053`907d5b7c 00000000`00000034 : nt!KiExceptionDispatch+0xce
ffffa801`fa7eee30 ffffd183`4af0458a : ffffd183`4a747400 fffff803`53189260 ffffd183`4af0056b ffffffff`b8797400 : nt!KiPageFault+0x221
ffffa801`fa7eefc0 ffffd183`4a747400 : fffff803`53189260 ffffd183`4af0056b ffffffff`b8797400 00000000`00000000 : 0xffffd183`4af0458a
ffffa801`fa7eefc8 fffff803`53189260 : ffffd183`4af0056b ffffffff`b8797400 00000000`00000000 fffff80c`3ed29a4a : 0xffffd183`4a747400
ffffa801`fa7eefd0 ffffd183`4af0056b : ffffffff`b8797400 00000000`00000000 fffff80c`3ed29a4a ffffa801`fa7ef840 : nt!PsWin32CallBack
ffffa801`fa7eefd8 ffffffff`b8797400 : 00000000`00000000 fffff80c`3ed29a4a ffffa801`fa7ef840 ffffd183`402443a0 : 0xffffd183`4af0056b
ffffa801`fa7eefe0 00000000`00000000 : fffff80c`3ed29a4a ffffa801`fa7ef840 ffffd183`402443a0 ffffd183`41c87f40 : 0xffffffff`b8797400


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80352fe0b63-fffff80352fe0b70  14 bytes - nt!KiRestoreProcessorControlState+33
[ 0f 01 59 66 0f b7 41 70:68 00 50 77 d6 c7 44 24 ]
    fffff80352fe0c40-fffff80352fe0c4d  14 bytes - nt!KiSaveProcessorControlState+50 (+0xdd)
[ 0f 01 49 66 0f 00 49 70:68 00 e0 77 d6 c7 44 24 ]
28 errors : !nt (fffff80352fe0b63-fffff80352fe0c4d)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

STACK_COMMAND:  ~0s ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_LARGE

TARGET_TIME:  2017-09-22T13:54:32.000Z

OSBUILD:  14393

OSSERVICEPACK:  1715

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-09-07 12:54:57

BUILDDATESTAMP_STR:  170906-1810

BUILDLAB_STR:  rs1_release_inmarket

BUILDOSVER_STR:  10.0.14393.1715

ANALYSIS_SESSION_ELAPSED_TIME:  12e7

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

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

最後更新：2017-09-23 19:03:17

  上一篇：go win10高級顯示設置不見了，無法調整字體大小
  下一篇：go Synatics WBDI 驅動無法加載