My physical HPE server running Windows Server 2019 starts normally, but applications begin failing one after another. RDP first reports "An internal error has occurred," and the iLO console eventually goes black. Other errors include a side-by-side configuration failure for SystemPropertiesRemote.exe, SideBySide Event 59 reporting invalid XML in the ndfapi.dll manifest, repeated DCOM Event 10000 errors from DllHost.exe, and "Only part of a ReadProcessMemory request was completed" messages. The graphical interface crashes so quickly that DISM and SFC cannot complete. iLO 5 is running firmware version 2.44 and does not show obvious hardware faults apart from network-related entries. What should I check first to determine whether this is failing hardware, storage corruption, or a damaged Windows installation?
5 Answers
If a recovery environment remains stable, use DiskPart to confirm the Windows volume's drive letter, then run an offline CHKDSK. From WinRE you may also need to load the RAID driver manually before the volume is accessible. After checking the disk, try offline SFC and DISM rather than relying on the unstable desktop.
Check the storage path carefully: RAID health, controller logs, drive status, cache or battery condition, and recent power events. A failing array, controller, or write-cache problem can corrupt manifests and produce very different-looking application errors. iLO may not report every storage issue, so check the RAID controller's own management utility and event logs.
If diagnostics show healthy hardware but the manifests and system components remain badly damaged, a clean rebuild may be faster and safer than continuing to repair the installation. Before doing that, verify backups, document the server's roles and configuration, and confirm that the RAID and memory tests pass so the replacement installation does not suffer the same corruption.
Safe Mode or a command-only recovery boot is another useful test. If the machine is stable there, collect the System and Application event logs and run the repair tools offline. If it fails even in Safe Mode or from external media, stop focusing on Windows corruption and concentrate on memory, storage, controller, power, and thermal checks.
Start by separating hardware problems from Windows problems. Boot the server from a known-good WinPE or Linux USB and leave it running for a while. If the live environment also crashes or shows read errors, investigate RAM, overheating, the RAID controller, firmware, and the disks. A memory test is especially worthwhile because bad RAM can make many unrelated system files appear corrupted.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures