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

Anonymous

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

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

65 answers

Anonymous

2022-12-03T19:30:55+00:00

Check whether those keys work in the recovery environment...

(a) Click any Power icon, then hold Shift as you click Restart.

(b) Click "Troubleshoot > Advanced Options > Command Prompt".

Try the keys, then exit the Command Prompt & click Continue to get back to Windows. If the keys worked there, then it's a software issue in Windows. So, try "START, Settings, Update & Security, Troubleshoot, Additional troubleshooters, Keyboard". If that fails, try uninstalling the keyboard driver in Device Manager, then reboot for it to automatically reinstall.

I've seen other threads in which that kind of thing will mysteriously happen.
Was this answer helpful?

0 comments No comments
Anonymous

2022-12-03T18:28:43+00:00

You missed my edit. The "new" one suddenly broke (after swapping the memory?). Bizarre. Keys w,s,z,x,c,v don't work on the keyboard. Blew it off with compressed air, then took it out. Re-seated the cable. No luck. I don't believe that swapping the memory back will fix the keyboard. Back to square one.

Jordan
Was this answer helpful?

0 comments No comments
Anonymous

2022-12-03T18:07:56+00:00

Wow, that's a lot of progress, if tough to explain. It's mysterious why RAM tests are passed on the new but not the old E6530 using the old RAM. And don't forget RAM tests were done earlier that did pass on the old E6530 with old RAM. Maybe you ran them more thoroughly now or it was the newer Memtest86+ that found them. Anyway, yeah, try the old chips back in the old E6530. I think they will have to pass because the "new" chips pass in both computers & the "old" ones do work in the "new" computer.

That's tremendous progress getting past the "No physical memory..." error. Sounds like you've got two working E6530's now with the latest BIOS. They both can boot to Legacy media now. I think the clean install will get past the 0xC0000001 error. Great work!
Was this answer helpful?

0 comments No comments
Anonymous

2022-12-03T14:40:26+00:00

For those of you still following my saga/quest, here is some additional info:

After reinstalling Win 10 PRO on the "new" E6530, and reinstalling almost all the programs I had icons for on the desktop, everything I am aware of is working.

I decided to check the memory on both laptops. I ran Memtest86+ with the original memory in each computer, then I swapped all the memory (both DDR3 DIMMs totalling 16 GB) from the old to the new and from the new to the old laptop.

Laptop Memtest86+ version Result with original memory Result with memory swapped

E6530 ("old" bad) v4.2 (orig), v4.3.7 (swap) Over 800 errors at pass #1 No errors
E6530 ("new" good) v4.3.7 No errors No errors

Interesting that swapping the memory appeared to get rid of all the errors. Not sure why.

Now for the really strange part. I pulled the CMOS battery out of the "bad" E6530, held the power button on for about 30-40 seconds. Rebooted the machine (without the CMOS battery in). Of course the BIOS said the time/date wasn't set, so went in the set them. Tried to change the BIOS to A22 but wouldn't let me, so put the CMOS battery back in. Tried to install BIOS A22 again. Didn't work. Tried again and it worked. Rebooted and now the "No physical memory..." message is gone! It will now boot legacy CD/DVD and the Internal Hard Disk. I do of course still get the 0xC0000001 error booting the HD immediately after the Windows 10 blue logo. Might swap the memory back. Stay tuned...

And just now 5 keys on the "new" one stopped working. :(

Jordan
Was this answer helpful?

0 comments No comments
Anonymous

2022-11-28T00:28:41+00:00

All right; sounds reasonable. Yeah, that ubackup article says how to install it in Win 10. I'm not well versed in using WBAdmin (the command prompt version of Window's Backup & Restore) anyway. So...

OK, keep us informed. Good luck.
Was this answer helpful?

0 comments No comments