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

65 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2022-10-27T14:45:35+00:00

    (1) eCS was working perfectly until the both eCS and Win 10 couldn't boot (9/16). It was a sector by sector clone from a Dell Latitude D630 running eCS and Win 7 Pro. After that the Win 7 PRO on the computer with the problems (Dell Latitude E6530) was updated to Win 10 PRO. Before the clone was put on the E6530 it already had Win 10 Pro on it, but not the same partition layout that the clone from the D630 had.

    (2)

    (a) No. I didn't install anything new. Like I said before it appears that pulling a USB stick from the computer when the BIOS screen was active somehow killed the boot of Win and eCS. I don't know how this action can produce a HW issue and I am unable to find the cause of Fimware-wise of the "No Physical Memory..." message.

    (b) No. But Win and eCS were updated to run on the E6530.

    (c) If you mean before the system crashed, then no.

    (d) No.

    (e) No. The partition layout was taken form the clone and never changed after that.

    (3) I believe my Windows partition (C:) has always been the system partition in this MBR/BIOS Legacy Boot configuration. There should be no trace of UEFI boot here, so again no idea where this "No Physical Memory.." message is coming from unless I suddenly for some reason have a hardware failure, but it's not memory AFAICT (tested many times), so no idea where the failed hardware if that is what is, is located.

    (4) I tried to run the command from a command prompt booted from a Windows recovery disk. I changed the x:\sources to c:\windows\system32 (because my windows drive c: is there and all the data is there -- just can't boot). Unfortunately I got this:

    c:\windows\system32>bcdedit

    The boot configuration data store could not be opened.

    The requested system device cannot be found.

    Jordan

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-10-28T03:34:08+00:00

    (1) What about DiskPart? I would leave it at the X: prompt, then try...

    DiskPart <<<Enter DiskPart

    List Vol <<<List volumes & letters

    List Disk <<<List the disks

    Select Disk 0 <<<Focus on Disk 0

    List Part <<<List its partitions

    Select Part 1 <<<Focus on partition 1

    Detail Part <<<Show its details

    === Select each other partition & show its details ===

    Exit <<<Leave DiskPart

    BCDEdit /Enum All <<<Show the BCD

    I want to see what partitions are there, what are their type codes, & which is marked Active. Only one should be Active. I'm thinking the BCDEdit command may fail, if the wrong one is Active. Normally, a System Reserved partition will exist. Then, it should have the boot files (including the BCD) & be marked Active. But I'm wondering whether your eCS partition is supposed to take its place. And, of course, you say it is C: that has the files. Are you aware that drive letters may be different when in the Recovery Environment? Go by sizes & labels instead of letters.

    I'll answer the rest later.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-10-28T08:47:05+00:00

    (1) How were eCS & Win 7 installed on the D630? Which was first? How do you know it is the IBM Boot Manager being used & not the Windows Boot Manager? I want to see it mentioned in the BCD. Also, can you put a letter on System Reserved (if one isn't already on it) & show a DIR of it, Windows, & eCS. Then, if it has a Boot directory, DIR it...

    DiskPart <<<Enter DiskPart

    List Vol <<<Show volumes & letters

    === Identify the volumes by size &/or label. System Reserved likely is 100 MB ===

    === Put a letter on it, if it doesn't already have one ===

    Select Vol=x <<<Use the volume number of System Reserved, not x

    Assign Letter=S <<<Give it letter S

    Exit <<<Leave DiskPart

    === For each of System Reserved, Windows & eCS, do the following ===

    *DIR /a L:* <<<Use the letter they have, not L.

    DIR /a L:\Boot <<<If it has a Boot folder, DIR it

    === Finally, remove the letter from System Reserved ===

    DiskPart <<<Enter DiskPart

    Select Vol=S <<<Select the volume of letter S

    Remove Letter=S <<<Remove the letter

    Exit <<<Leave DiskPart

    (2) After the clone was put onto the E6530, I'm sure the first boot to Win 7 caused all the drivers to update with multiple reboots. Did the first boot to eCS do anything similar?

    (3) When the upgrade to Win 10 occurred, likely the Windows partition was resized & a new Recovery partition was created. I want to see those DiskPart commands (in my prior post).

    (4) I too find it hard to believe removing a USB drive while in BIOS could be the cause of this.

    (5) Flashing the BIOS back & forth to different versions could affect BIOS settings.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-10-28T14:52:56+00:00

    (1) This partition layout has been around for many years moving from old computer to new computer.  There was Win Vista 32 bit on the D630 and it was updated to Win 7 PRO 64 bit.   As for eCS, I don’t exactly remember, but I think the eCS install CDs work on the D630 (as they were probably created for that computer), and I installed it from them.  At  this point, enabling the IBM Boot Manager causes it to appear and I can select between Win 10 & eCS.  To make the Windows recovery happy, I turned off IBM Boot Manager and set Windows 10 as bootable (using DFsee).  The BCD has timeout 0.

    The only one I can see at the moment is Windows (c: and c:\boot) because the system reserved is hidden so doesn’t have a volume in diskpart so won’t let me assign a letter to it unless I unhide it.   The eCS partition is HPFS filesystem so unreadable by Windows 10, so cannot do a dir.

    dir /a c:\

    Volume in drive C has no label.
    Volume Serial Number is A6ED-6DA2

    Directory of c:\

    11/26/2020 08:20 PM <DIR> $Recycle.Bin
    11/27/2020 05:03 PM <DIR> $SysReset
    11/24/2020 07:39 AM <DIR> $Windows.~WS
    09/16/2022 01:38 PM <DIR> $WinREAgent
    02/14/2021 09:43 PM 0 $WINRE_BACKUP_PARTITION.MARKER
    11/17/2018 12:31 PM <DIR> 3d9fea1c0d9a83801d382401b465
    01/21/2018 08:19 AM <DIR> 638bf2f5425d977b7ebd11c4
    07/17/2019 07:34 PM <DIR> 6b4afaa2840b095147488fcf
    07/17/2019 07:44 PM <DIR> b6012b9072df1d25975d35f36684fb
    09/16/2022 08:43 PM 24,576 BCD_Backup
    09/16/2022 08:09 PM 24,576 BCD_Backup.LOG
    09/16/2022 08:09 PM 0 BCD_Backup.LOG1
    09/16/2022 08:09 PM 0 BCD_Backup.LOG2
    10/20/2022 02:02 PM <DIR> Boot
    09/01/2022 08:35 AM 415,530 bootmgr
    12/07/2019 01:08 AM 1 BOOTNXT
    02/15/2021 08:03 AM 8,192 BOOTSECT.BAK
    02/28/2021 10:18 AM 112 bootTel.dat
    09/16/2022 01:57 PM <DIR> Config.Msi
    12/24/2019 09:22 PM <DIR> dell
    07/13/2009 09:08 PM <JUNCTION> Documents and Settings [C:\Users]
    05/30/2020 11:46 AM <DIR> Downloads
    09/16/2022 01:23 PM 8,192 DumpStack.log.tmp
    09/16/2022 04:59 PM <DIR> EFI
    11/24/2020 07:52 AM <DIR> ESD
    12/23/2021 03:23 PM <DIR> Fix
    09/16/2022 01:23 PM 12,838,592,512 hiberfil.sys
    02/15/2021 09:43 AM <DIR> inetpub
    02/11/2017 02:18 PM <DIR> Intel
    02/11/2017 04:33 PM <DIR> it
    12/26/2019 01:54 PM 178,978,816 MacriumRescue_win7.iso
    02/17/2022 08:39 AM <DIR> MDT
    09/16/2022 01:23 PM 4,294,967,296 pagefile.sys
    12/07/2019 01:14 AM <DIR> PerfLogs
    09/01/2022 04:49 AM <DIR> Program Files
    01/26/2022 01:33 PM <DIR> Program Files (x86)
    02/08/2022 07:57 AM <DIR> ProgramData
    07/19/2022 06:40 PM <DIR> Recovery
    10/28/2022 08:35 AM 0 Recovery.txt
    02/03/2022 01:21 AM <DIR> RECYCLER
    12/26/2019 01:46 PM 559,578 Reflect_Install.log
    09/17/2022 01:43 PM 352 rescuepe.log
    11/27/2020 03:48 PM <DIR> sources
    09/16/2022 01:58 PM 268,435,456 swapfile.sys
    09/16/2022 04:28 PM <DIR> System Volume Information
    02/15/2021 10:20 AM <DIR> temp
    10/26/2020 09:40 AM <DIR> temp2
    02/15/2021 10:22 AM <DIR> Users
    09/01/2022 02:51 PM <DIR> Windows
    03/11/2017 03:51 PM <DIR> winnt
    01/27/2022 10:33 AM 1,602 xwlan312.txt
    01/27/2022 10:33 AM 2,071,548 xwlan312.zip
    19 File(s) 17,584,088,339 bytes
    33 Dir(s) 225,211,199,488 bytes free

    dir /a c:\boot

    Volume in drive C has no label.
    Volume Serial Number is A6ED-6DA2

    Directory of c:\boot

    10/20/2022 02:02 PM <DIR> .
    10/20/2022 02:02 PM <DIR> ..
    10/27/2022 10:15 PM 28,672 BCD
    10/25/2020 04:18 PM 28,672 BCD.Backup.0001
    11/10/2020 06:47 PM 36,864 BCD.Backup.0002
    09/16/2022 08:01 PM 16,384 BCD.Backup.0003
    09/16/2022 08:42 PM 16,384 BCD.Backup.0004
    09/16/2022 06:37 PM 61,440 BCD.bak
    01/29/2022 11:28 AM 83,968 BCD.LOG
    02/10/2017 07:55 PM 0 BCD.LOG1
    02/10/2017 07:55 PM 0 BCD.LOG2
    09/16/2022 08:09 PM 24,576 bcd.old
    09/16/2022 08:38 PM 16,384 bcd.old1
    09/16/2022 08:43 PM 16,384 bcd.old2
    10/20/2022 02:02 PM <DIR> bg-BG
    09/16/2022 08:04 PM 65,536 BOOTSTAT.DAT
    09/01/2022 08:35 AM 28,520 bootuwf.dll
    09/01/2022 08:35 AM 101,232 bootvhd.dll
    10/20/2022 02:02 PM <DIR> cs-CZ
    10/20/2022 02:02 PM <DIR> da-DK
    10/20/2022 02:02 PM <DIR> de-DE
    10/20/2022 02:02 PM <DIR> el-GR
    10/20/2022 02:02 PM <DIR> en-GB
    10/20/2022 02:02 PM <DIR> en-US
    10/20/2022 02:02 PM <DIR> es-ES
    10/20/2022 02:02 PM <DIR> es-MX
    10/20/2022 02:02 PM <DIR> et-EE
    10/20/2022 02:02 PM <DIR> fi-FI
    10/20/2022 02:02 PM <DIR> Fonts
    10/20/2022 02:02 PM <DIR> fr-CA
    10/20/2022 02:02 PM <DIR> fr-FR
    10/20/2022 02:02 PM <DIR> hr-HR
    10/20/2022 02:02 PM <DIR> hu-HU
    10/20/2022 02:02 PM <DIR> it-IT
    10/20/2022 02:02 PM <DIR> ja-JP
    10/20/2022 02:02 PM <DIR> ko-KR
    10/20/2022 02:02 PM <DIR> lt-LT
    10/20/2022 02:02 PM <DIR> lv-LV
    12/26/2019 01:50 PM <DIR> macrium
    09/01/2022 08:39 AM 1,002,856 memtest.exe
    10/20/2022 02:02 PM <DIR> nb-NO
    10/20/2022 02:02 PM <DIR> nl-NL
    10/20/2022 02:02 PM <DIR> pl-PL
    10/20/2022 02:02 PM <DIR> pt-BR
    10/20/2022 02:02 PM <DIR> pt-PT
    10/20/2022 02:02 PM <DIR> qps-ploc
    10/20/2022 02:02 PM <DIR> qps-plocm
    10/20/2022 02:02 PM <DIR> Resources
    10/20/2022 02:02 PM <DIR> ro-RO
    10/20/2022 02:02 PM <DIR> ru-RU
    10/20/2022 02:02 PM <DIR> sk-SK
    10/20/2022 02:02 PM <DIR> sl-SI
    10/20/2022 02:02 PM <DIR> sr-Latn-RS
    10/20/2022 02:02 PM <DIR> sv-SE
    10/20/2022 02:02 PM <DIR> tr-TR
    10/20/2022 02:02 PM <DIR> uk-UA
    10/20/2022 02:02 PM <DIR> zh-CN
    07/20/2019 11:09 AM <DIR> zh-HK
    10/20/2022 02:02 PM <DIR> zh-TW
    16 File(s) 1,527,872 bytes
    43 Dir(s) 225,211,199,488 bytes free

    (2) Yes.  The Win 7 drivers updated and it was working fine before upgrading to Win 7. The first boot to eCS crashed.  If you know anything about eCS, it is not like Windows and cannot update drivers on the fly.  After many iterations of creating an image backup and restoring it to the E6530, I got a working eCS system.  Like I said before, I don’t think I’ve ever been able to boot diskettes/CDs because they didn’t have the right drivers to allow me to get to the maintenance desktop or a command prompt.

    (3) The Windows partition wasn’t resized.  I have a verified the size of the partitions on the D630 and the D6530 and nothing has changed.

    (4) Me too, but I’ve literally checked many things several times.  I still have a couple things to try: Find another computer (laptop) that has a HD bay and BIOS supporting Legacy Boot and put the “misbehaving” HD from the E6530 into it and try to boot it.  This could determine whether the E6530 MB has gone bad or the HD has something bad on it.  The other attempt would be to “start from scratch” and clone the D630 to the E6530 (again).  This would also help to prove whether it’s the E6530 MB vs. the HD.

    (5) I have also checked and rechecked the BIOS settings when going back and forth.  AFAICT (and I have many screen shots of the BIOS), the settings make sense and should be as they were before the inability to boot.

    Jordan

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-10-28T15:42:58+00:00

    I unhid the system reserved partition to do a dir:

    dir i: /a

    Volume in drive I is System Reserved

    Volume Serial Number is 7880-03E0

    Directory of I:\

    02/13/2017 02:52 AM <DIR> $RECYCLE.BIN

    02/13/2017 02:51 AM <DIR> Boot

    11/21/2010 03:23 AM 383,786 bootmgr

    02/13/2017 02:49 AM <DIR> EFI

    03/04/2017 04:59 PM <DIR> System Volume Information 

               1 File(s)        383,786 bytes 

           4 Dir(s)     450,596,864 bytes free

    dir i:\boot /a

    Volume in drive I is System Reserved

    Volume Serial Number is 7880-03E0

    Directory of I:\Boot

    02/13/2017 02:51 AM <DIR> .

    02/13/2017 02:51 AM <DIR> ..

    02/13/2017 02:58 AM 28,672 BCD

    02/13/2017 02:58 AM 21,504 BCD.LOG

    02/13/2017 02:49 AM 17,408 BCD.LOG1

    02/13/2017 02:49 AM 0 BCD.LOG2

    02/13/2017 02:49 AM 65,536 BCD{a0f4b701-f188-11e6-a39c-001e37003fb1}.TM.blf

    02/13/2017 02:49 AM 524,288 BCD{a0f4b701-f188-11e6-a39c-001e37003fb1}.TMContainer00000000000000000001.regtrans-ms

    02/13/2017 02:49 AM 524,288 BCD{a0f4b701-f188-11e6-a39c-001e37003fb1}.TMContainer00000000000000000002.regtrans-ms

    02/13/2017 02:49 AM 65,536 BOOTSTAT.DAT

    02/13/2017 02:49 AM <DIR> cs-CZ

    02/13/2017 02:49 AM <DIR> da-DK

    02/13/2017 02:49 AM <DIR> de-DE

    02/13/2017 02:49 AM <DIR> el-GR

    02/13/2017 02:49 AM <DIR> en-US

    02/13/2017 02:49 AM <DIR> es-ES

    02/13/2017 02:49 AM <DIR> fi-FI

    02/13/2017 02:49 AM <DIR> Fonts

    02/13/2017 02:49 AM <DIR> fr-FR

    02/13/2017 02:49 AM <DIR> hu-HU

    02/13/2017 02:49 AM <DIR> it-IT

    02/13/2017 02:49 AM <DIR> ja-JP

    02/13/2017 02:49 AM <DIR> ko-KR

    06/14/2016 03:25 PM 509,672 memtest.exe

    02/13/2017 02:49 AM <DIR> nb-NO

    02/13/2017 02:49 AM <DIR> nl-NL

    02/13/2017 02:49 AM <DIR> pl-PL

    02/13/2017 02:49 AM <DIR> pt-BR

    02/13/2017 02:49 AM <DIR> pt-PT

    02/13/2017 02:49 AM <DIR> ru-RU

    02/13/2017 02:49 AM <DIR> sv-SE

    02/13/2017 02:49 AM <DIR> tr-TR

    02/13/2017 02:49 AM <DIR> zh-CN

    02/13/2017 02:49 AM <DIR> zh-HK

    02/13/2017 02:49 AM <DIR> zh-TW 

               9 File(s)      1,756,904 bytes 

          26 Dir(s)     450,596,864 bytes free

    Also, looking at the BCD in the i:\boot it says timeout 30 and boot Windows 7, so obviously left over from the clone from the D630, but like I said, this partition shouldn't even matter because this is Legacy Boot not UEFI so it should not be used at all and the BCD should live in the c:\boot.

    I looked at the BCD in c:\boot and other than the timeout set to 30 it looked good. I changed it to skipped but still booting the HD gives the dreaded message ("No physical...).

    Jordan

    Was this answer helpful?

    0 comments