我有一个相当严重的问题Windows 10 Enterprise 2016 LTSB 32-bit：
这台机器上有一个应用程序全天候运行，并且有大量网络连接。总共有 14 个网络端口。
很少（也许一周一次……但偶尔，但如果时间足够长，就会持续观察到）我们观察到某种系统范围的暂停，这会导致网络和应用程序中正在发生的其他内部事件出现意外问题。也许是应用程序问题，问题是我们总是在事件查看器中观察到一些事件完全相同的时间发生这种情况。
事件查看器中的日志如下所示。发生了什么？我们如何避免这种情况？
首先，来自System。抱歉格式不对，但希望大家能看懂。
Information 2018-03-11 15:02:59 Kernel-General 16 None
The access history in hive \??\c:\users\defaultuser0\AppData\Local\Microsoft\Windows\usrclass.dat was cleared updating 1 keys and creating 1 modified pages.
Information 2018-03-11 15:02:59 Kernel-General 16 None
The access history in hive \??\c:\users\defaultuser0\ntuser.dat was cleared updating 9 keys and creating 4 modified pages.
Information 2018-03-11 15:02:03 Kernel-General 16 None
The access history in hive \??\C:\Windows\System32\config\components was cleared updating 1 keys and creating 1 modified pages.
Warning 2018-03-11 15:01:52 Time-Service 134 None
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Information 2018-03-11 15:01:52 Kernel-General 16 None
The access history in hive \SystemRoot\System32\Config\RegBack\SAM was cleared updating 65 keys and creating 7 modified pages.
Information 2018-03-11 15:01:52 Kernel-General 16 None
The access history in hive \SystemRoot\System32\Config\RegBack\DEFAULT was cleared updating 229 keys and creating 38 modified pages.
Information 2018-03-11 15:01:52 Kernel-General 16 None
The access history in hive \SystemRoot\System32\Config\RegBack\SYSTEM was cleared updating 15748 keys and creating 1077 modified pages.
Information 2018-03-11 15:01:51 Kernel-General 16 None
The access history in hive \SystemRoot\System32\Config\RegBack\SOFTWARE was cleared updating 78112 keys and creating 5756 modified pages.
Warning 2018-03-11 15:01:51 Time-Service 134 None
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Information 2018-03-11 15:01:51 Time-Service 158 None
The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well.
Information 2018-03-11 15:01:50 Kernel-General 16 None
The access history in hive \SystemRoot\System32\Config\RegBack\SECURITY was cleared updating 72 keys and creating 4 modified pages.
Warning 2018-03-11 14:59:31 DNS Client Events 1014 (1014)
Name resolution for the name settings-win.data.microsoft.com timed out after none of the configured DNS servers responded.
然后，同样来自Application：
Information 2018-03-11 15:08:22 VSS 8224 None
The VSS service is shutting down due to idle timeout.
Information 2018-03-11 15:04:51 VSS 8224 None
The VSS service is shutting down due to idle timeout.
Information 2018-03-11 15:03:40 SecurityCenter 15 None
Updated Windows Defender status successfully to SECURITY_PRODUCT_STATE_ON.
Information 2018-03-11 15:03:40 SecurityCenter 15 None
Updated Windows Defender status successfully to SECURITY_PRODUCT_STATE_ON.
Information 2018-03-11 15:01:54 Defrag 258 None
The storage optimizer successfully completed defragmentation on System Reserved
Information 2018-03-11 15:01:53 SecurityCenter 15 None
Updated Windows Defender status successfully to SECURITY_PRODUCT_STATE_ON.
Information 2018-03-11 15:01:53 SecurityCenter 15 None
Updated Windows Defender status successfully to SECURITY_PRODUCT_STATE_ON.
更新：过去 30 天内未运行任何任务：
答案1
事件日志显示 0x80072AF9 表示“没有已知这样的主机”，因此表明系统无法在主机上执行 DNS 查找（time.windows.com在本例中）。
我不知道导致此错误代码的具体原因，但它可能表明系统无法与其指定的 DNS 服务器通信。这可能表明存在 Internet 问题或（如果您的 DNS 服务器位于 LAN 上）本地网络问题。
我遇到过类似的问题，导致服务器将自己置于“未识别网络”而不是域网络。我没有找到原因，但我怀疑它在启动时找不到网络路由器。禁用/重新启用网络适配器会将其恢复到正确的网络配置文件。