Error 0xc0000017 often appears while Windows starts, upgrades, resets, or creates a recovery RAM disk. The message may say there is not enough memory to create a ramdisk device even when the PC has plenty of installed RAM. Do not assume the solution is more memory or an immediate reinstall. Preserve important files, record the full screen, test the RAM, and inspect the Windows bad-memory list before changing boot configuration.
The stage of failure changes the diagnosis
Photograph the error, including any file path and status line. Note whether it appeared during a normal boot, Windows Setup, a feature update, Reset this PC, or recovery-media startup. A failure before the Windows logo points toward boot configuration, firmware, RAM, or the recovery environment. A crash after sign-in belongs to a different path.
Next, reconstruct what changed. New RAM, a BIOS update, memory overclocking, a failed update, disk cloning, BCD editing, or removal of a recovery partition can narrow the cause. Disconnect nonessential USB storage and return firmware memory settings to stable defaults, but do not clear TPM, delete partitions, or reset the PC while the only copy of important files remains inside.
| Evidence | More likely explanation | Useful next test |
|---|---|---|
| Started after installing RAM | Module seating, compatibility, timing, or hardware defect | Use firmware defaults and test modules with the vendor’s supported arrangement |
| BCD lists excluded memory pages | Windows recorded pages as unreliable | Test memory before deciding whether the list is stale |
| Only recovery or Setup fails | RAM-disk creation, media, boot data, or recovery image issue | Test official media and confirm storage remains accessible |
| Random crashes occur outside Setup | Physical RAM, driver, power, or board instability | Run memory diagnostics and remove overclocking |
| Files are inaccessible after repeated failed boots | Separate storage or file-system risk | Recover data before reset, reinstall, or BCD experiments |
Test physical memory before deleting the bad-memory list
Power down, disconnect power, and follow the computer manufacturer’s service instructions before reseating memory. On a laptop with soldered RAM, do not open the device unless the procedure is supported. Confirm that modules match the board requirements and occupy the recommended slots. Remove XMP, EXPO, manual timings, and CPU or memory overclocking for diagnosis.
Run the built-in Windows Memory Diagnostic when Windows or recovery options can launch it. For intermittent faults, a longer bootable memory test and repeated cold starts may provide better evidence. One clean pass does not prove that every thermal, power, or timing condition is stable. Conversely, a reproducible error is enough reason to stop treating the BCD entry as harmless clutter.
On systems with error-correcting memory, Windows Hardware Error Architecture can persist page frame numbers predicted to fail. Microsoft documents how the PFA bad-memory list is stored and viewed. The documentation also warns that incorrect BCD changes can prevent Windows from starting. This is why the list should not be erased merely because an online command looks convenient.
Inspect boot records without changing them
From an elevated Command Prompt in a working Windows installation or an appropriate recovery environment, bcdedit /enum {badmemory} can display the current bad-memory object. Recording the output is safer than immediately using a delete command. If badmemorylist contains entries, compare that finding with actual memory-test results and hardware history.
A list may be stale after defective RAM was replaced, but it may also be the evidence that Windows is protecting itself from pages that still fail. Clear it only after the hardware has been tested, unstable modules have been replaced, and the system has returned to supported settings. Create a BCD backup and recovery plan first. If BitLocker protects the system drive, make sure the recovery key is available before boot changes.
Do not use commands copied for a different identifier. Braces, store location, and boot context matter. If the BCD store is damaged or the error followed partition work, use official Windows recovery media and a technician who can identify the correct Windows installation. Rebuilding boot files is not data recovery and can write to the disk.
Protect files when Windows cannot reach the desktop
If the PC contains irreplaceable data, postpone Reset this PC, clean installation, formatting, and partition changes. Check whether a current external or cloud backup already contains the needed files. When the storage device is stable, a read-only recovery scan is an option. A drive that clicks, disconnects, vanishes from firmware, or generates severe read errors needs imaging or professional recovery instead.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
Drecov is Windows recovery software for PCs, hard drives, SSDs, external drives, USB devices, SD cards, and memory cards. It supports documents, photos, videos, audio, email data, and archives through read-only recovery, Quick Scan, Deep Scan, filters, preview, and recovery to another healthy location. Lost Partition Recovery is available when a partition is missing. Drecov does not repair RAM, change BCD records, bypass encryption, or repair physical hardware.
Prepare a healthy external destination. Do not install recovery software on the partition that holds the missing files, and never recover results back to that source. If BitLocker is enabled, obtain the recovery key; a recovery application cannot decrypt a locked volume without valid access.
Step 1: Open Drecov and select the inaccessible Windows location
On a stable Windows PC or supported recovery setup, choose the original system partition or drive by capacity and layout. Use Lost Partition Recovery only if the partition itself is absent.
Step 2: Run Quick Scan for priority folders
Start Quick Scan. Look first for user Documents, Desktop, Pictures, project folders, and other irreplaceable data. Filter by path, file type, name, date, and size.
Step 3: Use Deep Scan only if the source stays stable
Continue with Deep Scan when Quick Scan misses required files and the disk remains consistently detected. Stop at new read errors, disconnections, unusual sounds, or overheating.
Step 4: Preview and recover to the healthy destination
Preview representative supported candidates and compare paths, dates, and sizes. Recover to the external destination. If files are not where expected, check Drecov Folder or Recovery Folder. Open a sample and verify content before clearing memory lists, rebuilding boot files, resetting Windows, or reinstalling.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
Apply the repair that matches the evidence
If memory tests fail, replace or service the RAM before changing Windows. Test the repaired hardware at default settings. If the bad-memory list remains after verified replacement, a qualified administrator can back up the BCD store and clear the stale value according to Microsoft documentation. Restart and rerun memory checks rather than assuming a successful boot proves stability.
If memory passes but only installation media fails, recreate official Windows media on a known-good USB drive and test a direct USB port. Check the download and architecture. If the internal disk also reports errors, protect its data and inspect storage health before another upgrade.
If the problem followed boot-partition changes, compare the actual firmware mode, GPT or MBR layout, EFI System Partition, and selected Windows installation. Do not convert the disk, mark random partitions active, or delete recovery partitions as a first response. Those actions change the boot structure and can turn one error into an unbootable layout.
Verify stability instead of stopping at one successful boot
After the chosen fix, perform several cold starts and a normal workload. Check Event Viewer and Reliability Monitor for recurring hardware or bugcheck entries. Run the memory test again. If an update or reset was the original trigger, repeat that operation only after backups are current.
For adjacent recovery cases, consult the Drecov homepage, the Windows data recovery overview, guidance for a desktop that will not boot, and the explanation of system images and file safety. Keep memory diagnosis and file recovery as connected but distinct tasks.
Error 0xc0000017 FAQs
Does 0xc0000017 always mean bad RAM?
No. It can involve excluded memory pages, boot configuration, recovery media, or setup context. Test the hardware and inspect the full error.
Can I delete the badmemorylist immediately?
Do not delete it before testing RAM. It may record genuine failures, and incorrect BCD changes can prevent startup.
Will adding more RAM solve the error?
Not if Windows is excluding pages or if a module, timing, boot record, or recovery image is faulty. Diagnose first.
Does Drecov fix the 0xc0000017 boot code?
No. It recovers accessible data from supported stable storage so you can protect files before boot repair or reinstall.
When should I seek hardware service?
Seek service when memory errors repeat at default settings, the board cannot detect modules reliably, or the storage device is physically unstable.
Conclusion
Error 0xc0000017 is a reason to gather evidence, not to erase the PC. Match the failing stage with memory tests, hardware history, and the recorded bad-memory list. Protect inaccessible files first; Drecov can recover them from a stable source to another drive. Repair or replace faulty memory before editing BCD data, and verify several cold boots and memory tests before returning the machine to normal use.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
