Get error: «No physical memory is available at the location required for the windows boot manager. The system cannot continue»

I have a stable working system with an E6300 processor, evga 680i motherboard, 8800gts video card, and 8gbs of RAM running on windows ulitmate 7 (32bit-I’m planning on re-installing with 64 bit to utilize the extra 4GB of RAM after I deal with the issue below).

I recented tried to add an Intel RS2WC080 SAS/SATA controller adapter into one of the PCI express slots on the 680i motherboard. I know the card works (as it operates fine in another motherboard) but for some reason when I put it in the 680i mobo I get the following message when I try to boot windows. (i.e. the raid controller does not have windows on the drives. I’m still using the original hdd drive still plugged into the same Sata port on the mobo)

«No physical memory is available at the location required for the windows boot manager. The system cannot continue»

I tried disabling virtually everything I could in the mobo bios as an experiment (including things I needed) . I also disabled the bios in the Intel RS2WC080 card.

I’m stumped. So what I’d like to know is this simply a hardware incompatibility issue or is there some sort of workaround I can perform in windows 7. For instance, is there perhaps some sort of way for it to boot using a different memory location than its currently using? (Or is this error message something related to bios memory that can’t be overcome with software?)

No physical memory is available at the location required for the windows boot manager.The system can not continue

Replies (7) 

3 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

3 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Well, remove one of the hard drives then try reinstalling Windows 10 using the following instructions:

Go to a working computer, download, create a bootable copy, then perform a clean install.

Step 1: How to download official Windows 10 ISO files
http://answers.microsoft.com/en-us/windows/wiki.

If there are files on the drive you want to recover, see — How to: Perform a Custom install of Windows 10
http://answers.microsoft.com/en-us/insider/wiki.

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

virtualbox.org

End user forums for VirtualBox

• Board index‹General‹VirtualBox on Mac OS X Hosts
• Change font size
• Print view

• FAQ
• Login

No physical memory available — Windows Boot Manager

No physical memory available — Windows Boot Manager

by Jim on Mac Host » 19. Mar 2017, 15:26

Running Mac Sierra and VB 5.1.18; Windows 7 64 bit guest.

I was having some problems with Windows 7 freezing and made the apparent mistake of experimenting.

I tried changing the Base Memory setting from 4 MB to 8 MB and got an error message when I tried to start Windows 7. I didn’t pay a great deal of attention to the detail and just went back to change the setting back to 4 MB.

Now I get the error message: «No physical memory is available at the location required for the Windows Boot Manager»

I did find one other old topic in the Index that’s related, but that didn’t seem to apply in this situation.

Re: No physical memory available — Windows Boot Manager

by socratis » 19. Mar 2017, 23:10

Are you sure this is MB and not GB?

Since the VM doesn’t start. delete it. Create a new VM. Accept the defaults. Try again.

Re: No physical memory available — Windows Boot Manager

by Jim on Mac Host » 26. Mar 2017, 18:42

Do I feel stupid? Yes, I feel stupid.

It was 4G, and I wasn’t paying attention and thoughtlessly moved it to 4M instead of 4096M.

Changing it to 4096M works much better.

Now, I’ll take a break and beat my head against the wall.

virtualbox.org

End user forums for VirtualBox

• Board index‹General‹VirtualBox on Mac OS X Hosts
• Change font size
• Print view

• FAQ
• Login

No physical memory available — Windows Boot Manager

No physical memory available — Windows Boot Manager

by Jim on Mac Host » 19. Mar 2017, 15:26

Running Mac Sierra and VB 5.1.18; Windows 7 64 bit guest.

I was having some problems with Windows 7 freezing and made the apparent mistake of experimenting.

I tried changing the Base Memory setting from 4 MB to 8 MB and got an error message when I tried to start Windows 7. I didn’t pay a great deal of attention to the detail and just went back to change the setting back to 4 MB.

Now I get the error message: «No physical memory is available at the location required for the Windows Boot Manager»

I did find one other old topic in the Index that’s related, but that didn’t seem to apply in this situation.

Re: No physical memory available — Windows Boot Manager

by socratis » 19. Mar 2017, 23:10

Are you sure this is MB and not GB?

Since the VM doesn’t start. delete it. Create a new VM. Accept the defaults. Try again.

Re: No physical memory available — Windows Boot Manager

by Jim on Mac Host » 26. Mar 2017, 18:42

Do I feel stupid? Yes, I feel stupid.

It was 4G, and I wasn’t paying attention and thoughtlessly moved it to 4M instead of 4096M.

Changing it to 4096M works much better.

Now, I’ll take a break and beat my head against the wall.

All Physical memory being used but nothing showing in task manager

Hi I have windows 7 64 bit fresh install as of yesterday (fully updated) and experiencing a performance issue. When I look under task manager 95% of my physical memory (3.5 gb out of 4gb) is being used but there are no tasks that are using the memory. I have selected show task for all users and again nothing is using the 3.5 gb of memory. It is a pretty clean install (just have virus checker and Skype, steam installed) so no chance of a virus. I have check my page file and it is configured for windows to automatically mange page file.

Things I have tried:- Stopped all of the service that I can (no change)
manually configure the page file (no change)
Reinstalled windows 7 (problem eventually comes back once all of the updates have been applied)

Any help is greatly appreciated.

This problem plagued me for much longer, and required much more effort to resolve, than it should have. I have been running an 8 core, 12 GB Dell that would go from 4ish GB to 11.5GB in the matter of 10 minutes, without any warning. Google searches led to a plethora of failed attempts including shutting down the Windows Media Player service, uninstalling VMWare, and removing AVG anti-virus software. The problem didn’t budge. One aspect of the problem that I noticed was that I was using much more RAM on start-up, and overall hard-drive space, than I anticipated.

I believe your culprit is Window 7 itself: the Windows Search service. From what I can glean, if you do a lot of computationally heavy work which creates a lot of temporary files, or have a large number of files (not large files per se, but a large number of files) on your hard drive(s), when this service kicks in, it attempts to index them, and store the resulting index in memory for quick searching. This leads to two problems:

(i) a huge Windows.edb (basically, the physical file representing the index)
(ii) a massive amount of used memory (which doesn’t show on task manager), when this file (or aspects of it) is loaded into memory

A nice tool, which in fact on a MS hosted site and should be much more accessible, to see your ACTUAL RAM usage is RAMMap http://technet.microsoft.com/en-us/sysinternals/ff700229. This will show you the offending culprit.

Blowing away the service and the Windows.edb file not only solved the problem of interest, but added 70GB to my hard drive, and lowered my startup RAM usage to 2.5GB (from 4.5GB)! Here is a good starting point:
http://www.howtogeek.com/howto/10246/how-to-disable-search-in-windows-7/

For the record, I find it to be bad OS development to allow a system file to get in the realm of hundred of MBs, and really awful development to get into GBs. A 70GB (almost 12% of the total hard drive size) OS file speaks volumes for Windows 7 development.