W
williamgault
Windows Server 2016 running natively on an Intel based dual Xeon server is rendered inoperable by update:
2018-10 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4462928)
The server had previously installed the 2018-09 (KB4091664) without issue as well as 2018-10 Cumulative Update (KB4462917), and of course all updates prior to that. However once the above update goes into the system it will provide a DPC WATCHDOG VIOLATION blue screen and you can no longer boot up the server.
The resolution is to boot into safe mode after which the update will be backed out and the server will continue to function without it.
Server specs:
Is anyone familiar with what can trigger this blue screen in this update?
Evaluating https://support.microsoft.com/en-us/help/4462928/windows-10-update-kb4462928 I see nothing in that list related to hardware or would cause such a blue screen. I was able to install one of the updates above around this update that wouldn't install, so it is specifically this update causing an issue.
Continue reading...
2018-10 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4462928)
The server had previously installed the 2018-09 (KB4091664) without issue as well as 2018-10 Cumulative Update (KB4462917), and of course all updates prior to that. However once the above update goes into the system it will provide a DPC WATCHDOG VIOLATION blue screen and you can no longer boot up the server.
The resolution is to boot into safe mode after which the update will be backed out and the server will continue to function without it.
Server specs:
- Intel S5520HC server motherboard
- Dual Xeon X5550
- 18GB RAM
- Avago RAID controller
- 10 SAS drives via HSBP expanders (Intel) to controller (Avago)
Is anyone familiar with what can trigger this blue screen in this update?
Evaluating https://support.microsoft.com/en-us/help/4462928/windows-10-update-kb4462928 I see nothing in that list related to hardware or would cause such a blue screen. I was able to install one of the updates above around this update that wouldn't install, so it is specifically this update causing an issue.
Continue reading...