在下列情况下，系统经常挂起和 BSOD 的原因可能是什么？
1) BSOD 经常不会显示，也没有保存任何转储，计算机只是挂起。
2) 保存时，它会报告 NTOSKRNL 和随机错误检查代码。
3）经过数小时的长时间内存测试（使用标准内存诊断工具）显示一切正常。
4) 重新安装 Windows 以清理新硬盘没有帮助。
还有什么不好的？我不知道……CPU？系统总线？随便什么？怎么知道？
更新
今天我在全新安装时遇到了新的 BSOD：https://1drv.ms/u/s!AkjSY7WYaKo6ljq-wBFKjcGsJ-m2
更新2
将一些崩溃转储加载到 WinDbg 中得到以下结果：
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {5012, fffff18010804310, c73, c70}
*** ERROR: Symbol file could not be found. Defaulted to export symbols for win32k.sys -
Probably caused by : memory_corruption
Followup: memory_corruption
---------
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005012, The subtype of the bugcheck.
Arg2: fffff18010804310
Arg3: 0000000000000c73
Arg4: 0000000000000c70
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.14393.447 (rs1_release_inmarket.161102-0100)
SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.
SYSTEM_PRODUCT_NAME: B85M-D3H
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: F13
BIOS_DATE: 06/19/2014
BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.
BASEBOARD_PRODUCT: B85M-D3H
BASEBOARD_VERSION: x.x
DUMP_TYPE: 2
BUGCHECK_P1: 5012
BUGCHECK_P2: fffff18010804310
BUGCHECK_P3: c73
BUGCHECK_P4: c70
BUGCHECK_STR: 0x1a_5012
CPU_COUNT: 8
CPU_MHZ: da4
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: CODE_CORRUPTION
PROCESS_NAME: msiexec.exe
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: LAGRANGIAN
ANALYSIS_SESSION_TIME: 11-30-2016 19:21:21.0450
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
LAST_CONTROL_TRANSFER: from fffff80215394944 to fffff80215357510
STACK_TEXT:
ffffc681`ad47c768 fffff802`15394944 : 00000000`0000001a 00000000`00005012 fffff180`10804310 00000000`00000c73 : nt!KeBugCheckEx
ffffc681`ad47c770 fffff802`1525ff11 : ffff8003`c3ab1d00 ffff8003`c3ab1d00 00000000`00000000 fffff180`10804310 : nt! ?? ::FNODOBFM::`string'+0x2dfa4
ffffc681`ad47c830 fffff802`156723b1 : 00000000`00000000 ffff8003`c3ab1d00 ffff8003`c3ab1d00 ffff8003`c3ab1800 : nt!MiCleanWorkingSet+0x45
ffffc681`ad47c860 fffff802`15672107 : 00000000`00040000 ffff8003`cedc8680 00000000`00000001 ffff8003`c3ab1800 : nt!MmCleanProcessAddressSpace+0x185
ffffc681`ad47c8d0 fffff802`156c9590 : ffff8003`c3ab1800 ffffb002`c303f060 ffffc681`ad47c9c0 00000000`00000000 : nt!PspRundownSingleProcess+0x117
ffffc681`ad47c950 fffff802`15620fa2 : ffff8003`00000000 ffff8003`c3ab1800 ffff8003`c3ab1800 ffff8003`cedc8680 : nt!PspExitThread+0x508
ffffc681`ad47ca90 fffff802`15362193 : ffff8003`c3ab1800 ffff8003`cedc8680 ffffc681`ad47cb80 ffffffff`ffffffff : nt!NtTerminateProcess+0xde
ffffc681`ad47cb00 00007ff9`049b53e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000b9`acc7f758 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`049b53e4
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff8021531ae6d-fffff8021531ae6e 2 bytes - nt!MiPurgeZeroList+6d
[ 80 fa:00 aa ]
2 errors : !nt (fffff8021531ae6d-fffff8021531ae6e)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE
PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_LARGE
TARGET_TIME: 2016-11-30T15:39:26.000Z
OSBUILD: 14393
OSSERVICEPACK: 447
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-11-02 13:17:03
BUILDDATESTAMP_STR: 161102-0100
BUILDLAB_STR: rs1_release_inmarket
BUILDOSVER_STR: 10.0.14393.447
ANALYSIS_SESSION_ELAPSED_TIME: 1139
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:memory_corruption_large
FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}
Followup: memory_corruption
---------
更新 3
CPU-Z 报告:(已删除）
更新 4
DSIM 报告：
C:\WINDOWS\system32>dism /Online /Cleanup-Image /CheckHealth
Deployment Image Servicing and Management tool
Version: 10.0.14393.0
Image Version: 10.0.14393.0
No component store corruption detected.
The operation completed successfully.
C:\WINDOWS\system32>dism /Online /Cleanup-Image /ScanHealth
Deployment Image Servicing and Management tool
Version: 10.0.14393.0
Image Version: 10.0.14393.0
[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.
答案1
您的内核（nt）内存损坏。奇金格将转储中的 exe 文件与从符号服务器下载的干净 exe 文件进行比较。
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff8021531ae6d-fffff8021531ae6e 2 bytes - nt!MiPurgeZeroList+6d
[ 80 fa:00 aa ]
2 errors : !nt (fffff8021531ae6d-fffff8021531ae6e)
在您的情况下，您有 2 次匹配失败，这会导致崩溃。
如果您有磁盘问题（坏扇区、NTFS 文件系统问题）或 RAM 损坏，就会发生这种情况。
调试步骤：