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: Newest
  1. Anonymous
    2022-11-08T05:14:40+00:00

    Well, I put the "data" partition images (E:, F:, G:, and H:) from the failed HD to the D630 clone I made that has Windows 7 PRO on C: and I also put the last good image file of eCS back on the D: partition. Then I put that D630 clone in the Lenovo. I booted eCS and although certain drivers (like Wifi) didn't work, it got to the desktop and since I already booted to the Win 7 login screen, now I have an HD that if I put it in another "good" laptop, I should be able to upgrade Win 7 to Win 10 and be somewhat back to normal.

    I don't really worry about Microsoft abandoning OSes. I still have several old computers running Win 98, Win 2000, and the D630 with Win 7. I just need to resurrect my Win 10 and eCS somehow from this failed system.

    Jordan

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-11-08T01:49:09+00:00

    You tried hard. You went above & beyond the call of troubleshooting. Sorry I couldn't help you to a cure. What is your reason for wanting eComStation? Even Win 10 will go out of service soon enough, & I'll be scrambling for a new computer. I think any new computer we get needs to run Win 11 & to run in UEFI mode. But, if it has a 2nd HDD, you can format it as MBR & possibly install eComStation onto it. Good luck & keep us informed.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-11-07T15:29:56+00:00

    DFSee can clone and make image backups but I had no luck with it for the D630. The Lazesoft worked great even though taking 15+ hours. I am now backing up the D630 clone with Lazesoft image backup. It looks like it is going to be very fast (which is kind of scary). After removing the battery and CMOS battery overnight form the E6530, I tried booting the Hiren's XP CD with F12 boot options. It booted. No surprise. Like I said there are other (non-UEFI) ones that boot. But, when I tried to boot the D630 HD clone as an internal HD in the E6530 it still gives the "No physical.." message . It is setup to boot IBM Boot Manager which shows Win 7 and eCS. As soon as I select Win7, "No Physical..." message.

    I just have no clue what could be broken. How in the world is BIOS "broken"? It doesn't make any sense to me at all. So, I just don't think I can "fix" this computer. I think even reinstalling Win 10 or upgrading this "good" D630 clone to Win 10 will not fix this problem especially considering it boots fine in the Lenovo. I think it is time to cut loses and get a "new" computer and by that I mean either a used E6530 or a brand new one.

    Jordan

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-11-07T03:46:48+00:00

    (1) If necessary, you can always backup files at a Command Prompt with Xcopy or even with Notepad.

    (2) Yep, great news that a clone of the D630 worked on the Lenovo, (even taking 15+ hours yow). If you can get that to work on the E6530, you'd only have to restore file backups & reinstall apps. And when all is working well, make a system image backup or new clone.

    (3) "this experiment also points to the original E6530 HD having some sort of problem WRT Windows Boot Manager since the cloned D630 with Windows 7 works on the Lenovo and the original problem HD that was in the E6530 moved to internal to the Lenovo boots with a Windows Boot Manager failed screen 0xC00000001 error code."

    That sounds right to me. I wonder, can DFsee be used to "backup, backup, backup" items from the D630, then restore them to the E6530...?...

    http://www.scoug.com/os24u/2001/scoug012.dfseetutorial.html#:~:text=To%20do%20this%3A%201%20We%20start%20the%20program,anything%20you%20want.%20...%203%20Press%20enter.%20 DFSee -- A Tutorial For OS/2 Users

    But it does sound like a perilous task to do. I guess I would want to try the VBRs of the IBM BM partition & possibly the Windows partition. Then I guess the MBR. And maybe the "spareblocks" whatever those are.

    (4) But you still get that "No physical..." error when trying to boot the clone of D630 in the E6530. Did you make it the internal drive & try it through the normal BIOS boot menu (you report only trying F12)?

    You used to get it when trying to boot a Win 10 Installation DVD in Legacy mode. Devices did boot in UEFI mode. And there is that "DOS based one" that does boot.

    (I have a "DOS based" Seagate DiscWizard rescue CD that too would boot at a time when other DVD/CD's would not, including UEFI. But I only vaguely recall the cure. And I never got that dread "No physical..." error. I think what I did was to delete Dell's preinstalled boot menu option for DVD/CD in BIOS Setup (F2 for me). That one used to show up with F12 even when no CD/DVD was inserted. After deleting it in BIOS Setup, a new one shows up only when a DVD/CD is inserted pre-boot, & it does work.).

    On original E6530 HDD, when using F12 (BIOS boot options menu), you said...

    "Right now no DVD/CDs will boot (except a DOS based one) under the Legacy Boot Options hitting F12 on BIOS screen and in fact booting anything HD, DVD/CD or external USB all get the 'No physical...' message when trying to boot (except the DOS based one). The Macrium, Hiren's, Win ISO and Win recovery all boot under UEFI boot on the F12 option menu."

    And when booting normally (BIOS boot screen)...

    "IBM Boot Manager did work until this problem. Now, if I enable it the behavior for both Win 10 and eCS is the same. Selecting either the screen goes black for a second and then reboots to the BIOS screen. But making Win 10 startable and active and trying to boot gives the "No physical.." message."

    You got various other errors on the Lenovo but never a "No physical..." error. You got the "No physical..." whether booting to the HDD (though maybe only when Win 10 is Startable) or to other media. That is why I tend to think it is a BIOS problem. Do you see anything different in the BIOS settings of the Lenovo compared to the E6530? But you did get boots of eCS & Windows that went to the brink when booting through IBM BM, so it may be the VBR or its ilk that is at fault.

    But now, the new clone (OMG, 15+ hours), gives the "No physical..." message when trying to boot it under F12 Legacy Boot Options. I think you said you made it internal. Have you tried booting it through the normal BIOS boot menu?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-11-06T22:09:08+00:00

    So. Good news. Cloning the D630 1 TB HD using Lazesoft software took 15+ hours, but appears to have worked. I say that because when I put the drive in the Lenovo laptop it booted to the Windows 7 login screen via IBM Boot Manager. I shut it down. eCS did not boot but that is not unexpected. Now for the bad news. When I put this D630 clone in the E6530, it once again gave the "No physical..." message trying to boot it under F12 Legacy Boot Options. So my conclusion from this experiment is that the E6530 has some kind of problem. It is completely unclear to me exactly what has died since BIOS is in ROM and should be read-only and RAM is volatile so can't have any memory footprint. I did not change or alter any HW except for the pulling of a USB stick out of the laptop when the BIOS screen was showing. It still could be the memory is buggered somehow, but that would be bizarre since I tested it and retested it and no problems were found. Unfortunately, this experiment also points to the original E6530 HD having some sort of problem WRT Windows Boot Manager since the cloned D630 with Windows 7 works on the Lenovo and the original problem HD that was in the E6530 moved to internal to the Lenovo boots with a Windows Boot Manager failed screen 0xC00000001 error code. I am contemplating what to do now. Either, buy a used E6530 or a brand new laptop. Either way I am not willing to give up everything that was on the E6530 since all my data is there and appears to be intact.

    Jordan

    Was this answer helpful?

    0 comments No comments