閱讀702 返回首頁    go 微軟 go windows

ntkrnlmp.exe 導致win10 64位係統頻繁藍屏重啟

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


Loading Dump File [C:\Windows\Minidump\010518-8750-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Windows 10 Kernel Version 16299 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff802`e9a12000 PsLoadedModuleList = 0xfffff802`e9d78fd0
Debug session time: Fri Jan  5 14:55:26.191 2018 (UTC + 8:00)
System Uptime: 0 days 16:53:03.922
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, fffffb8000099f58, c, b}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+1567 )

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

9: 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: fffffb8000099f58
Arg3: 000000000000000c
Arg4: 000000000000000b

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  16299.15.amd64fre.rs3_release.170928-1534

SYSTEM_PRODUCT_NAME:  To Be Filled By O.E.M.

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:  P3.40

BIOS_DATE:  11/07/2017

BASEBOARD_MANUFACTURER:  ASRock

BASEBOARD_PRODUCT:  X370 Killer SLI

BASEBOARD_VERSION:                        

DUMP_TYPE:  2

BUGCHECK_P1: 41793

BUGCHECK_P2: fffffb8000099f58

BUGCHECK_P3: c

BUGCHECK_P4: b

BUGCHECK_STR:  0x1a_41793

CPU_COUNT: 10

CPU_MHZ: bb2

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-UHTPPFE

ANALYSIS_SESSION_TIME:  01-05-2018 15:51:55.0110

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

LAST_CONTROL_TRANSFER:  from fffff802e9a78f97 to fffff802e9b876e0

STACK_TEXT:  
ffffd88c`dcaa74d8 fffff802`e9a78f97 : 00000000`0000001a 00000000`00041793 fffffb80`00099f58 00000000`0000000c : nt!KeBugCheckEx
ffffd88c`dcaa74e0 fffff802`e9a742b6 : 00000000`00000000 ffffa384`48230080 00000000`00000000 ffffa384`4aef5580 : nt!MiDeleteVirtualAddresses+0x1567
ffffd88c`dcaa77e0 fffff802`e9aeda09 : ffffa384`47a82300 ffffa384`47a82300 00000000`000133ec 00000000`133ecfff : nt!MiDeleteVad+0x3b6
ffffd88c`dcaa7930 fffff802`e9ebaa94 : 00000000`00000000 00000000`00000000 ffffd88c`dcaa7b80 00000000`133ecfff : nt!MiFreeVadRange+0x79
ffffd88c`dcaa7980 fffff802`e9eba787 : 00000000`00818000 00000000`133eafa0 00000000`15100040 00000000`0a3ff210 : nt!MmFreeVirtualMemory+0x2f4
ffffd88c`dcaa7ac0 fffff802`e9b9a203 : 00000000`15100040 00000000`0a4fa4e0 ffffa384`48230080 00000000`00818000 : nt!NtFreeVirtualMemory+0x27
ffffd88c`dcaa7b00 00007ffc`792a0234 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0a3fe8a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`792a0234


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  ca0cf8b0fe48e544801625842d88eef48f1b48ee

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  5edb3d930070deb91e393c66d44aa0382aed0da9

THREAD_SHA1_HASH_MOD:  30a3e915496deaace47137d5b90c3ecc03746bf6

FOLLOWUP_IP: 
nt!MiDeleteVirtualAddresses+1567
fffff802`e9a78f97 cc              int     3

FAULT_INSTR_CODE:  c38b4ccc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiDeleteVirtualAddresses+1567

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  5a4a1659

IMAGE_VERSION:  10.0.16299.192

IMAGE_NAME:  memory_corruption

BUCKET_ID_FUNC_OFFSET:  1567

FAILURE_BUCKET_ID:  0x1a_41793_nt!MiDeleteVirtualAddresses

BUCKET_ID:  0x1a_41793_nt!MiDeleteVirtualAddresses

PRIMARY_PROBLEM_CLASS:  0x1a_41793_nt!MiDeleteVirtualAddresses

TARGET_TIME:  2018-01-05T06:55:26.000Z

OSBUILD:  16299

OSSERVICEPACK:  192

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:  2018-01-01 19:07:05

BUILDDATESTAMP_STR:  170928-1534

BUILDLAB_STR:  rs3_release

BUILDOSVER_STR:  10.0.16299.15.amd64fre.rs3_release.170928-1534

ANALYSIS_SESSION_ELAPSED_TIME:  2aa1

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x1a_41793_nt!mideletevirtualaddresses

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

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

您好！

 

感謝您聯係微軟技術支持。

 

我了解到您遇到係統藍屏的問題 。

 

請您在電腦重啟之後，上傳藍屏minidump文件到百度網盤，然後提供鏈接，文件默認路徑在C:\Windows\Minidump（不需要進行壓縮操作）。

 

您可以通過以下方案收集您的dump日誌文件：

 

1）打開控製麵板>>係統>>高級係統設置>>高級>>啟動和故障恢複>>設置；

 

2）寫入調試信息>>選擇“小內存轉儲（256KB）”，路徑選擇默認，確定並重啟您的計算機；

 

3）再次藍屏後，前往C:\Windows\Minidump提取即可。

 

希望以上的信息可以幫助到您。

最後更新：2018-01-05 18:04:16

  上一篇：go windows7補丁係統補丁安裝失敗
  下一篇：go 郵箱子文件夾問題