Windows 10 1709 藍屏錯誤 Memory_Management 問題

以下ˋ是錯誤訊

Microsoft (R) Windows Debugger Version 10.0.16299.15 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [D:\112517-28906-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************

Response                         Time (ms)     Location

Deferred                                       SRV* C:\Symbols *http://msdl.microsoft.com/download/symbols

Symbol search path is: SRV* C:\Symbols *http://msdl.microsoft.com/download/symbols

Executable search path is: 

Windows 10 Kernel Version 16299 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Machine Name:

Kernel base = 0xfffff80170019000 PsLoadedModuleList = 0xfffff8017037afb0

Debug session time: Sat Nov 25 22:45:09.408 2017 (UTC + 8:00)

System Uptime: 2 days 1:55:27.495

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 1A, {41793, ffff9700f9434808, 2, 1}

Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+1223bf )

Followup:     MachineOwner

---

2: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

MEMORY_MANAGEMENT (1a)

    # Any other values for parameter 1 must be individually examined.

Arguments:

Arg1: 0000000000041793, The subtype of the bugcheck.

Arg2: ffff9700f9434808

Arg3: 0000000000000002

Arg4: 0000000000000001

Debugging Details:

---

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.16299.64 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER:  Acer

SYSTEM_PRODUCT_NAME:  Aspire TC-605

SYSTEM_SKU:                        

SYSTEM_VERSION:          

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  P11-B4

BIOS_DATE:  06/11/2015

BASEBOARD_MANUFACTURER:  Acer

BASEBOARD_PRODUCT:  Aspire XC-605

BASEBOARD_VERSION:          

DUMP_TYPE:  2

DUMP_FILE_ATTRIBUTES: 0x8

  Kernel Generated Triage Dump

BUGCHECK_P1: 41793

BUGCHECK_P2: ffff9700f9434808

BUGCHECK_P3: 2

BUGCHECK_P4: 1

BUGCHECK_STR:  0x1a_41793

CPU_COUNT: 4

CPU_MHZ: c79

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 1E'00000000 (cache) 1E'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-02BPN9A

ANALYSIS_SESSION_TIME:  11-26-2017 18:42:26.0348

ANALYSIS_VERSION: 10.0.16299.15 amd64fre

LAST_CONTROL_TRANSFER:  from fffff801701b5e3f to fffff8017017d0e0

STACK_TEXT:  

fffffd0cba4f41d8 fffff801701b5e3f : 000000000000001a 0000000000041793 ffff9700f9434808 0000000000000002 : nt!KeBugCheckEx

fffffd0cba4f41e0 fffff801700905e6 : 0000000000000000 ffff858f91cc4700 0000000000000000 ffff858f8c424080 : nt!MiDeleteVirtualAddresses+0x1223bf

fffffd0cba4f44d0 fffff80170504842 : ffff858f91cc4700 ffff858f901fc490 0000000000000000 ffff858f91cc4700 : nt!MiDeleteVad+0x3b6

fffffd0cba4f4620 fffff80170504497 : ffff858f91cc4700 ffff858f00000000 ffff858f901fc490 ffff858f901fc490 : nt!MiUnmapVad+0x32

fffffd0cba4f4650 fffff801705042de : ffffffff00000000 ffff858f91ba5270 ffff858f901fc490 ffff858f91cc4700 : nt!MiCleanVad+0x27

fffffd0cba4f4680 fffff801704c3a99 : ffffffffffffffff ffff858f8c424080 ffff858f8c424378 ffff858f00000000 : nt!MmCleanProcessAddressSpace+0x12e

fffffd0cba4f4700 fffff80170555c17 : ffff858f8c424080 ffff9d08c9bfe8c0 fffffd0cba4f4918 0000000000000000 : nt!PspRundownSingleProcess+0x129

fffffd0cba4f4780 fffff801705562e3 : 00000000c0000005 0000000000000001 0000001e7cf7d000 0000000000000000 : nt!PspExitThread+0x583

fffffd0cba4f4880 fffff8017007e1c7 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSchedulerApcTerminate+0x33

fffffd0cba4f48c0 fffff80170180830 : 000001f2dfafd130 fffffd0cba4f4950 0000000000000000 fffff801700f3cd0 : nt!KiDeliverApc+0x337

fffffd0cba4f4950 fffff801701885fa : 000001f2dfa6cd58 0000000000000000 ffffeec4ffffffff 0000001e00001cff : nt!KiInitiateUserApc+0x70

fffffd0cba4f4a90 00007ffa43539164 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceExit+0x9f

0000001e005ff7f8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffa`43539164

THREAD_SHA1_HASH_MOD_FUNC:  5807e9fbede505f57a296dced4c7b96bb76ed997

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  ba6395c0b034b3aa778a79d632e2bed47e53af89

THREAD_SHA1_HASH_MOD:  dc844b1b94baa204d070855e43bbbd27eee98b94

FOLLOWUP_IP: 

nt!MiDeleteVirtualAddresses+1223bf

fffff801`701b5e3f cc              int     3

FAULT_INSTR_CODE:  c48b4dcc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiDeleteVirtualAddresses+1223bf

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  59efff9b

IMAGE_VERSION:  10.0.16299.64

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  memory_corruption

BUCKET_ID_FUNC_OFFSET:  1223bf

FAILURE_BUCKET_ID:  0x1a_41793_nt!MiDeleteVirtualAddresses

BUCKET_ID:  0x1a_41793_nt!MiDeleteVirtualAddresses

PRIMARY_PROBLEM_CLASS:  0x1a_41793_nt!MiDeleteVirtualAddresses

TARGET_TIME:  2017-11-25T14:45:09.000Z

OSBUILD:  16299

OSSERVICEPACK:  64

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-10-25 11:06:03

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.16299.64

ANALYSIS_SESSION_ELAPSED_TIME:  506

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x1a_41793_nt!mideletevirtualaddresses

FAILURE_ID_HASH:  {0730eb34-d667-1bcc-76fe-94b17390a3ef}

Followup:     MachineOwner

---

網路上搜尋似乎是出現在虛擬記憶體的方面!

win10 memory management蓝屏解决方案

Debugging Tools for Windows 10

【藍屏分析】Debugging Tools for Windows 10 - 讓你從此看到藍屏不再害怕

CBS.LOG我本來也是錯誤,我是參考了這篇的回復後把zh-TW和zh-HK移動裡面的檔案才把錯誤弄掉的

https://answers.microsoft.com/zh-hant/windows/forum/windows\_10-windows\_install/windows-10-%E6%9B%B4%E6%96%B01709-%E5%BE%8Ccbslog/889cced4-9f97-4f48-82d8-29fe0b74b07e

重灌後更新都跑過了,依舊如此

隨機藍屏

Win10蓝屏重启提示Memory Management的解决方法

win10系统蓝屏提示 memory management错误信息的原因和解决方法

我是Intel的