

In Windows, there is a mechanism that analyzes ECC errors in memory and protects the operating system from using erroneous memory blocks in RAM. Predictive Failure Analysis (PFA) in Windows But why is that, anyway? For your understanding, I'll dig a bit deeper. There are no longer enough contiguous memory blocks to set up the RAM disk of the appropriate size. I found a ' shredded' explanation here (German). The problem here is that there should be enough RAM available. The error 0xc0000017 probably occurs when trying to create a RAM disk for the Windows PE environment during the boot process.

However, Windows PE is loaded into a ramdisk and depends on the fact that a certain number of (RAM) memory pages can be used in a contiguous way.

Once this transaction is completed, the machine reboots and the actual Windows is restarted. Then the required file operations are carried out within Windows PE. For this purpose, a so-called Windows PE (PE stands for Preinstall Environment) boots. Update installations require a restart to replace files that are blocked during a running Windows. This may help some users to understand what has happened. An attempt to explain the background Instead of typing a few commands, I would like to take the time and dig into some of the background of this error. Error code 0xc0000017 stands for STATUS_NO_MEMORY – There are not enough virtual memory or swap file quotas for the specified operation. My attempt to find out more about the error text with the help of an error-lockup tool didn't really go any further. I was trapped a while ago with this error within a virtual machine, when I installed an Insider Preview and ended with the screen shown below. There isn't enough memory available to create a ramdis device. A blue screen appears with the following message: This error occurs if Windows 10 (or Windows 8.1) is rebooting after installing an update.
