No physical memory is available at the location required for the Windows Boot Manager. The system can not continue.

Anonymous
2022-10-18T21:44:49+00:00

I have a Dell Latitude E6530 laptop that somehow went south after a pulled a USB stick out of the computer while the BIOS screen was showing. All the data in all the partitions including Windows 10 PRO are intact. I can view all the files in the directories. The problem is the system just won't boot. This system originally had Windows 7 PRO that I updated to Windows 10 PRO. The system is UEFI capable and I have enabled the legacy roms in the BIOS and I have the Boot Sequence set to Legacy. the hard disk layout is NOT UEFI. It is MBR. When I try to boot all devices that are on the boot options menu (F12 when the BIOS screen appears), I have 2 Legacy Boot Devices: the Internal Hard Drive and the DVD/CD drive, but when I attempt to boot form either of them (LEGACY), I get the "No physical memory..." message. I can only boot devices that are UEFI such as the DVD/CD or an external USB bootable stick. I have run the memory test diagnostic on the computer 4 times. No problems. I have run chkdsk the computer a couple times. No problems. I have tried to rebuild the BCD, but with the latest ISO, I get access error for bootrec /fixboot. If I drop back to ISO 1703, bootrec /fixboot works, but I get "The requested system device cannot be found" when trying to execute bootrec /RebuildBcd. I feel like the whole problem is because I cannot boot legacy devices. To make matters worse I tried to reninstall Windows from the ISO DVD, but it won't let me do it. I just really want to be able to boot Windows hopefully without reinstalling or losing *anything* since all my data is there still, but until I can successfully "restore" Legacy Boot options working, I don't think I can. Any help appreciated.

Jordan Krim

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

65 answers

Sort by: Oldest
  1. Anonymous
    2022-10-18T23:40:03+00:00

    Hi Jordan. I'm Greg, 10 years awarded Windows MVP, here to help you.

    UEFI has been the standard for BIOS for 12 years. Installing in Legacy or CSM mode on a UEFI BIOS is like buying a new car and disabling all of the safety and performance features.

    The error refers to Windows Boot Manager which is only used by UEFI. I understand you have it set to Legacy, what if you disable UEFI. After getting it fixed I can help you convert it to UEFI using Windows own tool, or better yet you can rescue your files which aren't backed up, wipe the drive and do a gold standard UEFI CLean Install which will never have these kind of problems.

    Go to another PC to create bootable media to try the repairs, do a Reset or do the gold standard Clean install. The bootable media is the only repair method that doesn't require a password, has it's own drivers, repair and installation files which often work when Windows or the WinRE Repair Mode doesn't.

    To create Windows 10 Installation Media on another PC install Media Creation Tool follow the directions in the middle of the download page here: http://windows.microsoft.com/en-us/windows-10/m.... Uncheck the box for Recommended Settings to choose the exact version and bit rate for the target PC only.

    Insert media, boot it by powering up PC while pressing the BIOS Boot Menu Key given here: https://www.sysnative.com/forums/hardware-tutor...

    If the media won't boot you may need to enter BIOS/UEFI Setup (pressing key given in chart in link above) to turn off Fast Boot or Fast Startup first.

    Choose the boot device as a UEFI device if offered, on second screen choose Repair Your Computer, then Advanced Troubleshoot Options, then:

    1. Try a System Restore to a point before the problem began, or keep working backward,
    2. If that fails try Uninstall Updates, working backward until the problem goes away,
    3. Open the Command Prompt to:

    a) run System File Checker: https://www.wintips.org/how-to-run-sfc-offline-...

    and DISM Offline from https://www.ubackup.com/windows-10/dism-offline...

    b) run a full Disk Check: https://www.groovypost.com/howto/check-hard-dri...

    c) trigger Safe Mode with Networking (for internet) or Safe Mode following Option 3 here: https://www.digitalcitizen.life/4-ways-boot-saf... to roll back Updates & Drivers in Windows Update History, update your drivers from the PC/Motherboard manufacturer's website and diagnose further:

    https://www.pcmag.com/news/354269/how-to-use-sa...

    You can also create a new Local Admin account to replace yours: https://www.isumsoft.com/windows-10/3-ways-to-c...

    d) To replace the User account try to enable the built-in elevated Admin account from Option Five here:

    https://www.tenforums.com/tutorials/2969-enable...

    Boot into this emergency Admin account (leaving password box blank) to create a new Local Admin account:

    https://www.isumsoft.com/windows-10/3-ways-to-c...

    Sign into the new Account, make sure it works correctly, if so move your files over via C:\Users, when ready delete the old account and change the new one to your MS Account if desired in Settings > Accounts > Your Info > Sign in with a MS Account instead.

    1. If those fail then go back to Troubleshoot Options to do a Reset. Make it a deep clean reset to set up a new account, with Cloud option to download fresh installation files so it doesn't use old onboard files that may be corrupted.
    2. If that fails choose Install Now, then Custom Install, then at the drive selection screen delete all partitions down to Unallocated Space to get it cleanest, click Next to let it create needed partitions and start install - this makes it foolproof.

    Everything needed to get the best possible Clean Install is here: http://answers.microsoft.com/en-us/windows/wiki.... It is a better install than any amount of money can buy and a great learning experience that will make you the master of your PC because you will learn what works best and how to apply it with your own hands.

    1. If you have files that aren't backed up you can use the same bootable media to try to rescue your files using these methods: http://answers.microsoft.com/en-us/windows/wiki...

    I hope this helps. Feel free to ask back any questions and keep me posted. If you will wait to choose if I solved your problem, I will keep working with you until it's resolved.

    ________________________________________________________

    Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2022-10-19T01:53:24+00:00

    Here is a thread in which that error was cured with a UEFI/BIOS upgrade...

    https://www.techsupportforum.com/threads/solved-quot-no-physical-memory-available-at-location-required-quot.736153/ [SOLVED] "No Physical Memory Available at location required"

    JoshJ5Hawk (the OP) said, "I got it guys! (Don't know why this didn't occur to me earlier, and I feel pretty stupid for it) but I had to update the gosh darn Bios!"

    Here is that computer's site...

    https://www.dell.com/support/home/en-us/product-support/product/latitude-e6530/drivers Latitude E6530

    The latest UEFI/BIOS there is version A22 of 09 Jan 2019. Click the "View full driver details" button under it to see the various options to install it. But I hope you have BitLocker turned off, if it is installed.

    After that, I think I would do a UEFI clean install as Greg suggests. https://www.techsupportforum.com/threads/solved-quot-no-physical-memory-available-at-location-required-quot.736153/post-4405657

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-10-19T12:54:31+00:00

    My BIOS is set to Legacy Boot with Legacy ROMs enabled, so why do I get the error message for Windows Boot Manager when you say it only applies to UEFI? I have another bootable file system on this hard disk, so I am not sure converting to UEFI is an option as it probably won't boot then.

    Jordan Krim

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-10-19T12:55:09+00:00

    I already have A22 installed. Even tried to down rev it to A21. Didn't help. Went back to A22 at that point.

    Jordan Krim

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-10-19T16:35:38+00:00

    Are you able to disable UEFI to test that?

    What is "another bootable file system?" If you don't think you can convert using the Windows tool I showed you, then at some point I would wipe the drive and reinstall to UEFI to have the modern UEFI protection and performance.

    Was this answer helpful?

    0 comments No comments