Why can I only use 2.48 GB RAM in Boot Camp (Win 8.1 Pro, 64-bit)?

Hello, I am fairly new to the iMac and I have to use some programs in Windows that are not available for Mac so I set up Boot Camp and installed Windows 8.1.


My iMac is a I7-2600 CPU @ 3.4GHz with 16 GB RAM, system type-bit. Under system in Windows it shows Installed memory (RAM) 16 GB (2.48 GB usable).


I read about this problem and most answers are related to people using 32-bit. So what is wrong in my case, where is the problem?


Thank you in advance for help and suggestions.

iMac, OS X Yosemite (10.10.3)

Posted on May 3, 2015 11:52 AM

Reply
Question marked as Top-ranking reply

Posted on May 4, 2015 8:04 PM

Your 2011 iMac is a preUEFI Mac (all Macs prior to Late 2013 models are). The preUEFI Macs support varying degrees of EFI boot capability, but do not fully comply with UEFI specifications. This causes various BC drivers to work, not work, or partially work, depending the year of the Mac and the OS used.


There are two methods that have been "successful" in working around broken Optical drives (apart from replacing it).


1. http://forums.macrumors.com/showthread.php?p=20584499#post20584499

2. Bootcamp without Optical disc drive


My recommendation is to remove Windows using BC Assistant (only, nothing else), and then try either of these two methods. You want a legacy BIOS installation (aka Hybrid MBR method). The CSM-BIOS layer correctly exposes hardware for preUEFI machines. It will also address your memory visibility issue.

195 replies
Question marked as Top-ranking reply

May 4, 2015 8:04 PM in response to Mortandos

Your 2011 iMac is a preUEFI Mac (all Macs prior to Late 2013 models are). The preUEFI Macs support varying degrees of EFI boot capability, but do not fully comply with UEFI specifications. This causes various BC drivers to work, not work, or partially work, depending the year of the Mac and the OS used.


There are two methods that have been "successful" in working around broken Optical drives (apart from replacing it).


1. http://forums.macrumors.com/showthread.php?p=20584499#post20584499

2. Bootcamp without Optical disc drive


My recommendation is to remove Windows using BC Assistant (only, nothing else), and then try either of these two methods. You want a legacy BIOS installation (aka Hybrid MBR method). The CSM-BIOS layer correctly exposes hardware for preUEFI machines. It will also address your memory visibility issue.

May 3, 2015 5:14 PM in response to Mortandos

Can you check msconfig in Windows as shown in the linked discussion?


You may also want to look at https://msdn.microsoft.com/en-us/library/windows/desktop/aa366796%28v=vs.85%29.a spx?f=255&MSPPError=-2147217396.


What is the year/model of your iMac (my guess is a 2011 iMac)? Can you post the output of the highlighted command from OS X Terminal?

sysctl hw.cpu64bit_capable

hw.cpu64bit_capable: 1

Jun 6, 2015 9:42 PM in response to Mortandos

Your Windows setup has two separate modes. EFI and BIOS. You may see the EFI mode which would be the default and it will complain about the disk being MBR. Creating an exFAT partition will create a Hybrid MBR. Try the bless command which will try to bring up the BIOS version as it has been blessed with --legacy qualifier. You have had issues with EFI and repeating will lead to the same set of issues again.


If you get no bootable device or a hanging underscore cursor in top left, you may need an SMC reset/NVRAM reset to get OS X back up.

Jul 14, 2015 4:30 AM in response to Loner T

This was my suspicion , and yes, that was it.


Reporting success, guys !


I was not trying to fix the exact issue that the original reporter had, but is pretty close. The main differences are : a) I use Win7 (not sure if this is important), and b) I don't care about OSX, and ended up wth a single 2Tb Win7 partition. I suspect the process would work with Win8, but I haven't tried. The process I used would NOT work for dual boot on the internal drive.


As pointed, the major problem in a "normal" install is that the Mac EFI BIOS does not pass correct information to windows, with the net result of not having access to the full 16Gb, and having no sound.


An addtional problem arises when windows is booting and is trying to get back to its own partition: there seems to be some misunderstanding about where to boot from, and it seems that part of the Boot Camp Assistant.app is to manage this magic, which seems to be somewhat relying on the EFI boot process (and very badly implemented, as most things around the boot process on this mac). I tried to use refind at some point, but it didn't really helped (I looks like it may work and may be the safest bet for someone that needs a dual boot.)


At the end, this is what worked for me (there have been many additional steps, but were dead ends. Here is a step-by-step guide)


* Created a external OSX boot disk, and rebooted on it

* Downloaded the "Boot Camp 5" drivers on an USB Key

* Installed Virtual Box

* Installed Windows 7 on the virtual box, using a fixed size 10Gb disk and Sysprep'ed the Win 7 installation.

I followed this http://huguesval.com/blog/2012/02/installing-windows-7-on-a-mac-without-superdri ve-with-virtualbox/ guide, part 1 (for the XML file, you may want to use explorer from with the virtual machine to go to the article and get the file). Note that all this is quite slow and painful due to the emulation. (Note that I did the whole proces twice [I didn't realize the 10Gb size was important], and the second time the sysprep failed, and I had to run the same command twice. SO YMMV.)

* Umounted all the /dev/disk0 partitions

* Copy the full windows 10Gb raw drive (not partition) onto your internal drive:


dd if=windows_copy.raw of=/dev/disk0 bs=1048576


Note the lack of disk0s1, which means we override the partition table of the drive, and we end up with NO GPT partition. This will trickle the boot process to boot windows in BIOS mode. Also, windows will easily find its partition, as it is going to be active and the first and only partition on the MBR.


Shutdown. Remove external drive. Boot. Windows installation appear. Wait for install to complete, check you have access to 16Gb. Use diskmgmt.mcs to extend the partition to the full drive. Reboot. Insert USB key with boot camp drivers. Run setup.exe. Reboot.


Many many thanks to ALL the posters in this thread, and let me know if anyone needs additional info.

May 5, 2015 1:50 PM in response to Mortandos

Can you post the output of the following Terminal commands?


diskutil list

diskutil cs list

sudo gpt -vv -r show /dev/disk0

sudo fdisk /dev/disk0


The "sudo" commands will prompt for your password, and it will not be echoed back. You may also see a warning about improper use of "sudo" and potential data loss due to "abuse" of the command.

Jun 6, 2015 9:15 PM in response to Mortandos

Check the output of sudo fdisk /dev/disk0 . Post the output and i can give you more specific steps.


If there is an entry for disk0s2 (using the start/size from the gpt command), then mark it as bootable using flag command.


Here is an example on my MBP which has a GPT/Hybrid MBR.


sudo gpt -vv -r show /dev/disk0

Password:

gpt show: /dev/disk0: mediasize=256060514304; sectorsize=512; blocks=500118192

gpt show: /dev/disk0: Suspicious MBR at sector 0

gpt show: /dev/disk0: Pri GPT at sector 1

gpt show: /dev/disk0: Sec GPT at sector 500118191

start size index contents

0 1 MBR

1 1 Pri GPT header

2 32 Pri GPT table

34 6

40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

409640 250392096 2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC

250801736 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

252071272 664

252071936 248045568 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

500117504 655

500118159 32 Sec GPT table

500118191 1 Sec GPT header


$ sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 31130/255/63 [500118192 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec [ start - size]

------------------------------------------------------------------------

1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>

2: AC 1023 254 63 - 1023 254 63 [ 409640 - 250392096] <Unknown ID>

3: AB 1023 254 63 - 1023 254 63 [ 250801736 - 1269536] Darwin Boot

*4: 07 1023 254 63 - 1023 254 63 [ 252071936 - 248045568] HPFS/QNX/AUX

Jun 24, 2015 9:30 AM in response to Mortandos

This is from my WININSTALL USB2.0 stick. Notice that I have a 3.6G file (the entire Windows 64-bit ISO file) on the USB.


diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_HFS Macintosh HD 741.7 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data rMBPBCMP 258.0 GB disk0s4

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *16.0 GB disk1

1: DOS_FAT_32 WININSTALL 16.0 GB disk1s1


diskutil info disk1

Device Identifier: disk1

Device Node: /dev/disk1

Part of Whole: disk1

Device / Media Name: SanDisk Cruzer Glide Media


Volume Name: Not applicable (no file system)


Mounted: Not applicable (no file system)


File System: None


Content (IOContent): FDisk_partition_scheme

OS Can Be Installed: No

Media Type: Generic

Protocol: USB

SMART Status: Not Supported


Total Size: 16.0 GB (16008609792 Bytes) (exactly 31266816 512-Byte-Units)

Volume Free Space: Not applicable (no file system)

Device Block Size: 512 Bytes


Read-Only Media: No

Read-Only Volume: Not applicable (no file system)

Ejectable: Yes


Whole: Yes

Internal: No

OS 9 Drivers: No

Low Level Format: Not supported


ls -lh

total 7622128

drwxrwxrwx 1 MyName staff 8.0K Nov 18 2014 $RECYCLE.BIN

drwxrwxrwx 1 MyName staff 8.0K Sep 23 2014 $WinPEDriver$

-rwxrwxrwx 1 MyName staff 102K Nov 18 2014 AMDr290x-14.2.PNG

-rwxrwxrwx 1 MyName staff 101K Nov 18 2014 AMDr290x-14.3.PNG

-rwxrwxrwx 1 MyName staff 2.8K Sep 23 2014 AutoUnattend.xml

drwxrwxrwx 1 MyName staff 8.0K Nov 17 2014 BootCamp

-rwxrwxrwx@ 1 MyName staff 370K Nov 18 2014 DeviceManager-1.PNG

-rwxrwxrwx 1 MyName staff 387K Nov 18 2014 DeviceManager-2.PNG

drwxrwxrwx 1 MyName staff 8.0K Nov 18 2014 System Volume Information

-rwxrwxrwx 1 MyName staff 3.6G Jul 26 2014 Windows8.1-64bit.cdr

-rwxrwxrwx 1 MyName staff 128B Aug 22 2013 autorun.inf

drwxrwxrwx 1 MyName staff 8.0K Aug 22 2013 boot

-rwxrwxrwx 1 MyName staff 418K Aug 22 2013 bootmgr

-rwxrwxrwx 1 MyName staff 1.5M Aug 22 2013 bootmgr.efi

drwxrwxrwx 1 MyName staff 8.0K Aug 22 2013 efi

-rwxrwxrwx@ 1 MyName staff 6.9K Nov 18 2014 imac5k-diskutil.rtf

-rwxrwxrwx 1 MyName staff 76K Aug 22 2013 setup.exe

drwxrwxrwx 1 MyName staff 16K Aug 22 2013 sources

drwxrwxrwx 1 MyName staff 8.0K Aug 22 2013 support


Can you do the same with your USB2.0 stick with what you currently have on it?

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Why can I only use 2.48 GB RAM in Boot Camp (Win 8.1 Pro, 64-bit)?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.