&gt; Not some ~20GB of Microsoft crap driving the system to crash every couple days.<p>I agree the system should be running as few services and as little other third-party software as possible, but let&#x27;s be fair. Since at least Windows 7 &#x2F; 2008R2, <i>particularly</i> for an offline system, the OS is not going to crash unless there is a hardware problem. It&#x27;s not clear the OS crashed even in the article - &quot;the screen went black&quot; (the application went black?) and they &quot;had to reboot&quot; doesn&#x27;t give us enough information.<p>A modern Windows system, like a modern Linux or a modern FreeBSD, is stable and will stay up for as long as you need it to, unless as I said before, there is a hardware problem. (Or in the case of consumer Windows, you do an update.)<p>EDIT: According to the actual report, the OS was not rebooted, the application was. There was no Windows crash.<p>&gt; On (b)(6) 2016, a customer reported to merge healthcare that, in the middle of a heart catheterization procedure, the hemo monitor pc lost communication with the hemo client and the hemo monitor went black. Information obtained from the customer indicated that there was a delay of about 5 minutes while the patient was sedated so that the application could be rebooted. It was found that anti-malware software was performing hourly scans. With merge hemo not presenting physiological data during treatment, there is a potential for a delay in care that results in harm to the patient. However, it was reported that the procedure was completed successfully once the application was rebooted.