724      魔獸

藍屏代碼求解答，安全模式正常，開機數分鍾內藍屏

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


Loading Dump File [C:\Windows\Minidump\111717-18843-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 17035 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff803`fc016000 PsLoadedModuleList = 0xfffff803`fc38c890
Debug session time: Fri Nov 17 10:29:26.215 2017 (UTC + 8:00)
System Uptime: 0 days 0:03:34.134
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 C2, {4, 0, 6c, ffffa209a2ca9008}

Probably caused by : memory_corruption ( nt!MiBuildImageControlArea+15565b )

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

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

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000004, Pool header has been corrupted
Arg2: 0000000000000000, Pointer to pool header
Arg3: 000000000000006c, First part of pool header contents
Arg4: ffffa209a2ca9008, 0

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

SYSTEM_MANUFACTURER:  LENOVO

SYSTEM_PRODUCT_NAME:  20DSA02SCD

SYSTEM_SKU:  LENOVO_MT_20DS_BU_Think_FM_ThinkPad L450

SYSTEM_VERSION:  ThinkPad L450

BIOS_VENDOR:  LENOVO

BIOS_VERSION:  JDET53WW (1.15 )

BIOS_DATE:  07/27/2015

BASEBOARD_MANUFACTURER:  LENOVO

BASEBOARD_PRODUCT:  Intel powered classmate PC

BASEBOARD_VERSION:  Not Defined

DUMP_TYPE:  2

DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump

BUGCHECK_P1: 4

BUGCHECK_P2: 0

BUGCHECK_P3: 6c

BUGCHECK_P4: ffffa209a2ca9008

FAULTING_IP: 
nt!MiBuildImageControlArea+15565b
fffff803`fc66e213 4d85e4          test    r12,r12

BUGCHECK_STR:  0xc2_4

CPU_COUNT: 4

CPU_MHZ: 95a

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3d

CPU_STEPPING: 4

CPU_MICROCODE: 6,3d,4,0 (F,M,S,R)  SIG: 21'00000000 (cache) 21'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  SearchProtocol

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  MARKBRUCE

ANALYSIS_SESSION_TIME:  11-17-2017 10:34:08.0041

ANALYSIS_VERSION: 10.0.16299.15 amd64fre

LAST_CONTROL_TRANSFER:  from fffff803fc2ced7e to fffff803fc19ca50

STACK_TEXT:  
fffff186`2a4f4278 fffff803`fc2ced7e : 00000000`000000c2 00000000`00000004 00000000`00000000 00000000`0000006c : nt!KeBugCheckEx
fffff186`2a4f4280 fffff803`fc66e213 : ffffa209`a4601d10 00000000`00000000 00000000`00000000 fffff803`00000000 : nt!ExFreePoolWithTag+0x1d4e
fffff186`2a4f4360 fffff803`fc5188cd : 00000000`00000002 ffff8600`3711f210 fffff186`00001f8c fffff186`00001000 : nt!MiBuildImageControlArea+0x15565b
fffff186`2a4f43f0 fffff803`fc516d78 : fffff186`2a4f4890 00000004`00000002 00000000`00000000 00000000`00000000 : nt!MiCreateImageFileMap+0x3d5
fffff186`2a4f45c0 fffff803`fc54382e : fffff186`2a4f4890 fffff186`2a4f4760 fffff186`2a4f4890 ffffa209`87016640 : nt!MiCreateNewSection+0x228
fffff186`2a4f4730 fffff803`fc542eed : fffff186`2a4f4760 00000000`00000000 ffffcd0a`2080e300 00000000`00000000 : nt!MiCreateImageOrDataSection+0x2ce
fffff186`2a4f4820 fffff803`fc542dc4 : ffffa209`9fdc29d0 00000000`00000000 fffff186`2a4f4a50 fffff186`2a4f49b8 : nt!MiCreateSection+0xdd
fffff186`2a4f4980 fffff803`fc542be5 : 00000000`00000000 fffff186`2a4f4b80 00000000`00000002 00000000`11000000 : nt!MmCreateSection+0xe4
fffff186`2a4f4a00 fffff803`fc1a8253 : ffffcd0a`1ed2d080 00000026`1bbf8998 00000000`00000000 00000000`00000000 : nt!NtCreateSection+0x155
fffff186`2a4f4a90 00007ffa`72e8c704 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000026`1bbf8978 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`72e8c704


THREAD_SHA1_HASH_MOD_FUNC:  864c9d806dc19b406e6784edc65992eda813e8d4

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  009287d2cf7a849af82c822028624e8d8f363fa8

THREAD_SHA1_HASH_MOD:  bc100a5647b828107ac4e18055e00abcbe1ec406

FOLLOWUP_IP: 
nt!MiBuildImageControlArea+15565b
fffff803`fc66e213 4d85e4          test    r12,r12

FAULT_INSTR_CODE:  74e4854d

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!MiBuildImageControlArea+15565b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  59fd1ebe

IMAGE_VERSION:  10.0.17035.1000

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  memory_corruption

BUCKET_ID_FUNC_OFFSET:  15565b

FAILURE_BUCKET_ID:  0xc2_4_nt!MiBuildImageControlArea

BUCKET_ID:  0xc2_4_nt!MiBuildImageControlArea

PRIMARY_PROBLEM_CLASS:  0xc2_4_nt!MiBuildImageControlArea

TARGET_TIME:  2017-11-17T02:29:26.000Z

OSBUILD:  17035

OSSERVICEPACK:  1000

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-11-04 09:58:22

ANALYSIS_SESSION_ELAPSED_TIME:  88e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xc2_4_nt!mibuildimagecontrolarea

FAILURE_ID_HASH:  {82ab6b21-ce14-759e-ffbb-30e614bdbe30}

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

最後更新：2017-11-17 11:05:04

  上一篇： win10 如何刪除不存在的打開方式

  下一篇： 關於11月16日和11月17日更新補丁導致愛普生(Epson)針式打印機無法使用的問題