我刚刚完成了一个新的 I7 构建，我得到的 BSOD 比我想要的要多。我认为第一次安装可能在某个时候出了什么问题，所以我把它扔掉，重新开始。你可以看到，从昨天开始我已经遇到了 3 个 BSOD。
我运行了 MEMTEST86，运行一天后没有出现任何问题。
这个 BSOD 可能是由不可靠的驱动程序引起的吗？
我已经在 WINDBG 中加载了崩溃转储，最近的一个显示 vmwp.exe 是正在运行的进程，前一个显示 ngentask.exe。
我下一步该采取什么步骤来诊断该问题？
!analyze如果有人想要windbg的结果，请参见：
0: 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: fffff6809d59cff8
Arg3: 0000000000000200
Arg4: 00000000000001ff
Debugging Details:
------------------
Page 159ca not present in the dump file. Type ".hh dbgerr004" for details
Page 1080 not present in the dump file. Type ".hh dbgerr004" for details
Page 1080 not present in the dump file. Type ".hh dbgerr004" for details
Page 1080 not present in the dump file. Type ".hh dbgerr004" for details
Page 1080 not present in the dump file. Type ".hh dbgerr004" for details
Page 1080 not present in the dump file. Type ".hh dbgerr004" for details
Page 1080 not present in the dump file. Type ".hh dbgerr004" for details
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 10586.103.amd64fre.th2_release.160126-1819
SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.
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: F2
BIOS_DATE: 07/27/2015
BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.
BASEBOARD_PRODUCT: H170M-D3H-CF
BASEBOARD_VERSION: x.x
DUMP_TYPE: 1
BUGCHECK_P1: 41793
BUGCHECK_P2: fffff6809d59cff8
BUGCHECK_P3: 200
BUGCHECK_P4: 1ff
BUGCHECK_STR: 0x1a_41793
CPU_COUNT: 8
CPU_MHZ: d50
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 5e
CPU_STEPPING: 3
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 23'00000000 (cache) 23'00000000 (init)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: vmwp.exe
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: FAMILY
ANALYSIS_SESSION_TIME: 02-21-2016 22:24:27.0933
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
LAST_CONTROL_TRANSFER: from fffff802727eabab to fffff802727c6480
STACK_TEXT:
ffffd000`24efb538 fffff802`727eabab : 00000000`0000001a 00000000`00041793 fffff680`9d59cff8 00000000`00000200 : nt!KeBugCheckEx
ffffd000`24efb540 fffff802`726b6543 : 00000000`00000000 ffffd000`24efb809 00000000`00000000 00007ff5`ff61ffff : nt! ?? ::FNODOBFM::`string'+0x15dab
ffffd000`24efb740 fffff802`72ab6950 : 00000000`00000000 ffffe001`47d530a0 ffffe001`4223f680 ffffe001`422797c0 : nt!MiDeleteVad+0x3a3
ffffd000`24efb870 fffff802`72ab6777 : 00000000`00040000 ffffe001`4223f680 00000000`00000001 ffffe001`422797c0 : nt!MmCleanProcessAddressSpace+0x94
ffffd000`24efb8d0 fffff802`72a4e19b : ffffe001`422797c0 ffffc001`81fee060 ffffd000`24efb9c0 ffffe001`4223f680 : nt!PspRundownSingleProcess+0x117
ffffd000`24efb950 fffff802`72afeef6 : ffffe001`00000000 ffffe001`422797c0 ffffe001`422797c0 ffffe001`4223f680 : nt!PspExitThread+0x4f7
ffffd000`24efba90 fffff802`727d0ca3 : ffffe001`422797c0 ffffe001`4223f680 ffffd000`24efbb80 ffffd000`24efbb80 : nt!NtTerminateProcess+0xde
ffffd000`24efbb00 00007fff`78d35604 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000034`dca7fb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`78d35604
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 53b8912a4e8bc66404dcb8384b6660e10443ee81
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 205b2aa944e7090e1f96fc2bbfe11822ff56b666
THREAD_SHA1_HASH_MOD: cb5f414824c2521bcc505eaa03e92fa10922dad8
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+15dab
fffff802`727eabab cc int 3
FAULT_INSTR_CODE: 4f8b44cc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+15dab
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 56a849a9
BUCKET_ID_FUNC_OFFSET: 15dab
FAILURE_BUCKET_ID: 0x1a_41793_nt!_??_::FNODOBFM::_string_
BUCKET_ID: 0x1a_41793_nt!_??_::FNODOBFM::_string_
PRIMARY_PROBLEM_CLASS: 0x1a_41793_nt!_??_::FNODOBFM::_string_
TARGET_TIME: 2016-02-21T11:00:15.000Z
OSBUILD: 10586
OSSERVICEPACK: 0
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: 2016-01-27 15:38:01
BUILDDATESTAMP_STR: 160126-1819
BUILDLAB_STR: th2_release
BUILDOSVER_STR: 10.0.10586.103.amd64fre.th2_release.160126-1819
ANALYSIS_SESSION_ELAPSED_TIME: 877
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x1a_41793_nt!_??_::fnodobfm::_string_
FAILURE_ID_HASH: {2bb49b32-09fa-a96d-8b93-292cf7a50b3f}
答案1
ntoskrnl.exe 错误可能是由多种问题引起的，因此很难检测。它们很可能是由有问题的硬件/驱动程序引起的。由于您有内存错误，请考虑以下事项：
运行至少 6 次内存测试（扩展测试），如果不是两位数的话。这将需要很长时间。请参阅此帖子。
请移除所有 RAM 棒，然后尝试一次使用一根或一对（如果需要）来排除故障。非分页区域中的故障也可能是硬件问题。请尝试调整分页文件的大小。
http://www.online-tech-tips.com/computer-tips/page-fault-in-non-paged-area-error/
祝你好运！