This post is more than 5 years old
6 Posts
1
115677
Area 51-R2, 64GB Memory Support?
I see that the manual says the limitation is 32gb but everything I'm reading regarding the chipset and processor is that it should support 64gb. Has anyone successfully upgraded to 64gb?
ark.intel.com/.../Intel-Core-i7-5960X-Processor-Extreme-Edition-20M-Cache-up-to-3_50-GHz
RaysXPS730h2c
23 Posts
0
August 15th, 2016 13:00
I have upgraded my R2 from 8gbs stock to 32 gbs of Corsair dominator 2666 MHz ram. I left the auto settings at 2133mhz and have not attempted in anyway to over clock anything. The PC runs fine with no problems. I also upgraded my video card from the base r370 to dual r390x, which I bought from dell online. I can run all game's at ultra settings. I am happy with the upgrade's.
PUC_Snakeman
33 Posts
0
September 24th, 2016 16:00
I just bought:
Crucial 64GB Kit (4 x 16GB) DDR4-2400 UDIMM
DDR4 PC4-19200 • CL=17 • Dual Ranked • x8 based • Unbuffered • NON-ECC • DDR4-2400 • 1.2V •
part # : CT4K16G4DFD824A
... and in about 6-10 days
... then I'll reply back on whether it works in this Area 51-R2 with A08 BIOS. :)
PS: I'm upgrading from 32GB to 64GB, because I do distributed computing, running RNA World VirtualBox VM tasks that each take 3GB. And, instead of being limited to 10 simultaneously, I'd like to be able to do 15.
I'd encourage everyone to consider helping a worthy cause with your spare CPU/GPU cycles. Visit BOINC, and get crunching :)
marctronixx
2 Intern
2 Intern
•
141 Posts
0
September 27th, 2016 09:00
To follow up. I have installed with no issues the crucial ram. 64gb found on amazon. Works very well and windows 10 pro recognizes it. I have an Area 51 r2 .
DELL-Chris M
Community Manager
Community Manager
•
54.9K Posts
0
September 27th, 2016 12:00
marctronixx,
Memory running at what speed? Check the bios and then in windows run CPU-Z.
RaysXPS730h2c
23 Posts
0
September 27th, 2016 14:00
Probably running at the base 2133mhz. Did you run a memory stress test to see if it will handle a load?
PUC_Snakeman
33 Posts
2
October 1st, 2016 10:00
I have successfully upgraded my Alienware Area-R2, to 64 GB RAM (4 x 16 GB), from 32 GB RAM (4 x 8 GB). But there is a problem that Alienware will need to address. Read on.
After about 8 hours of troubleshooting and testing, here are the results:
- Alienware Command Center 4.0.59.0, has an incompatibility in Windows 10 x64, causing Windows to entirely freeze when booted.
- The Alienware Command Center windows services, "MSICPU_CC", must be disabled using "msconfig" in Safe Mode, in order to load Windows without freezing.
- Otherwise, all stress tests (Windows Memory Diagnostic, Prime95, LINPack, LinX), are successful!
- So, I get to keep my upgrade, so long as I have that "MSICPU_CC" service disabled, until Alienware can fix it!
Chris M:
What can we do about the Alienware Command Center 4.0.59.0 "64 GB RAM" incompatibility?
More details about my upgrade experience, below. Thanks for reading! :)
===========================================================
BIOS reported that:
- the original 32 GB, was running at 2133 MHz.
- the new 64 GB, runs at 2400 MHz.
My purchase was:
Crucial 64GB Kit (4 x 16GB) DDR4-2400 UDIMM
DDR4 PC4-19200 • CL=17 • Dual Ranked • x8 based • Unbuffered • NON-ECC • DDR4-2400 • 1.2V •
part # : CT4K16G4DFD824A
===========================================================
Original 8 GB RAM stick details (from CPU-Z):
"Chipset":
Memory Type DDR4
Memory Size 32 GBytes
Channels Quad
Memory Frequency 1064.2 MHz (1:16)
CAS# latency (CL) 15.0
RAS# to CAS# delay (tRCD) 15
RAS# Precharge (tRP) 15
Cycle Time (tRAS) 36
Row Refresh Cycle Time (tRFC) 278
Command Rate (CR) 2T
tCCD 4
tCCD_L 6
tCCD_WR 4
tCCD_WR_L 6
"Memory SPD":
Memory type DDR4
Module format UDIMM
Manufacturer (ID) Samsung (CE000000000000000000)
Size 8192 MBytes
Max bandwidth DDR4-2132 (1066 MHz)
Part number M378A1G43EB1-CPB
Serial number 9926E65A
Manufacturing date Week 03/Year 16
Nominal Voltage 1.20 Volts
EPP no
XMP no
AMP no
JEDEC timings table CL-tRCD-tRP-tRAS-tRC @ frequency
JEDEC #1 10.0-10-10-24-34 @ 727 MHz
JEDEC #2 11.0-11-11-27-38 @ 800 MHz
JEDEC #3 12.0-12-12-29-41 @ 872 MHz
JEDEC #4 13.0-14-14-32-45 @ 945 MHz
JEDEC #5 14.0-14-14-34-48 @ 1018 MHz
JEDEC #6 15.0-15-15-36-50 @ 1066 MHz
JEDEC #7 16.0-15-15-36-50 @ 1066 MHz
===========================================================
New 16 GB RAM stick details: (from CPU-Z):
"Chipset":
Memory Type DDR4
Memory Size 64 GBytes
Channels Quad
Memory Frequency 1197.2 MHz (1:18)
CAS# latency (CL) 17.0
RAS# to CAS# delay (tRCD) 17
RAS# Precharge (tRP) 17
Cycle Time (tRAS) 39
Row Refresh Cycle Time (tRFC) 421
Command Rate (CR) 2T
tCCD 4
tCCD_L 6
tCCD_WR 4
tCCD_WR_L 6
"Memory SPD":
Memory type DDR4
Module format UDIMM
Manufacturer (ID) Crucial Technology (7F7F7F7F7F9B00000000)
Size 16384 MBytes
Max bandwidth DDR4-2400 (1200 MHz)
Part number CT16G4DFD824A.M16F
Serial number E0247A2C
Manufacturing date Week 38/Year 16
Nominal Voltage 1.20 Volts
EPP no
XMP no
AMP no
JEDEC timings table CL-tRCD-tRP-tRAS-tRC @ frequency
JEDEC #1 10.0-10-10-24-34 @ 727 MHz
JEDEC #2 11.0-11-11-26-37 @ 800 MHz
JEDEC #3 12.0-12-12-28-40 @ 872 MHz
JEDEC #4 13.0-14-14-31-44 @ 945 MHz
JEDEC #5 14.0-14-14-33-47 @ 1018 MHz
JEDEC #6 15.0-15-15-35-50 @ 1090 MHz
JEDEC #7 16.0-16-16-38-54 @ 1163 MHz
JEDEC #8 17.0-17-17-39-55 @ 1200 MHz
JEDEC #9 18.0-17-17-39-55 @ 1200 MHz
JEDEC #10 19.0-17-17-39-55 @ 1200 MHz
JEDEC #11 20.0-17-17-39-55 @ 1200 MHz
JEDEC #12 21.0-17-17-39-55 @ 1200 MHz
===========================================================
Steps that I took, while trying to narrow down what was causing Windows to freeze on load:
Note, for each of the uninstallations/disablings, I performed the action in Safe Mode, then booted to Normal Mode, to verify it would freeze, until I found the culprit.
Enabled Legacy Boot Policy for Windows 10 (using bcdedit), so I could gain access to Safe Mode easily
Removed BIOS overclocks
In Safe Mode, uninstalled each of these one by one, then rebooted into Normal mode, to verify still freezes:
- Uninstalled TeamViewer
- Uninstalled Logitech Gaming Software
- Uninstalled NVIDIA Graphics Driver
- Uninstalled left-over NVIDIA pieces, using Display Driver Uninstaller (DDU)
- Uninstalled Oculus software
- Uninstalled SoundBlaster Recon3Di Extras
- Uninstalled MSI Afterburner (note: Later, when I found the culprit service, because it was named "MSI", I thought it was a part of MSI Afterburner, but really it was a part of Alienware Command Center)
- Uninstalled Adobe Flash Player NPAPI
- Uninstalled Core Temp
- Uninstalled CPU-Z
- Uninstalled EPSON Scan
- Uninstalled Teamspeak
Disabled Startup for the following (via the "Startup" tab in Task Manager)
- EPSON Status Monitor
- iRacingAmbience
- Logitech Wingman Event Monitor
- Microsoft OneDrive
- RequiredApplicationsLauncher x9 (Alienware Command Center)
- Skype x2
- Sound Blaster Control Panel x2
- TradingPaints
- Windows Defender Notification Icon
- Windows Desktop Gadgets x3 (8GadgetPack)
Disabled non-Microsoft Services (via "msconfig" Services tab)
- Creative/SB x2
- Intel x3
- Misc: iRacing, Mozilla, Skype
- Misc: MSIODD (Eject button), Overwolf, Steam
- Misc: Origin x2, Cyberlink
- Misc: Alienware Fusion Service, ThermalsWindowService
- Misc: ioloEnergyBooster, PAExec (DDU piece)
- 10x "MSI*_CC" services, for Alienware Command Center
Found that Windows would now boot! Meaning, culprit was one of the "MSI*_CC" services
- Tested enabling each one at a time, then actually starting it in Windows Normal mode
- Worked: MSIBIOSData_CC, MSIClock_CC, MSICOMM_CC, MSICTL_CC, MSIDDR_CC, MSISaveLoad_CC, MSISMB_CC, MSISuperIO_CC, MSIWMI_CC
- Failed: MSICPU_CC (made windows freeze at login screen, since it was set to "Automatic" once I enabled it via msconfig)
Workaround tried:
- Uninstalling Alienware Command Center 4.0.59.0
- Could boot and login without problems.
- Reinstalling Alienware Command Center 4.0.59.0
- Problem reappeared - freezes at login screen.
- So, only workaround is to keep that "MSICPU_CC" service disabled
Now with culrpit found, I spent about 2 hours:
- Disabled the "MSICPU_CC" service
- Re-enabled all other services that I had disabled
- Re-enabled all Startup items that I had disabled
- Reinstalled all programs that I had uninstalled
And so far, testing is looking great :) I'm continuing my testing with LinX v0.6.9.
===========================================================
Chris M:
What can we do about the Alienware Command Center 4.0.59.0 "64 GB RAM" incompatibility?
RaysXPS730h2c
23 Posts
0
October 1st, 2016 10:00
They probably won't do anything because the ram and the 64gb used is not compatable at this time.
PUC_Snakeman
33 Posts
0
October 1st, 2016 12:00
I believe they are shipping new Area-51 R2 units, right now, that have 64 GB ram in them. Try it out, you can choose that as a customization option, on 3 of their models.
So, I'm not sure where the problem lies, but it is within their power to fix this 64 GB issue. Maybe they have a new Alienware Command Center up their sleeves!
I'd at least like to know what the real problem is, if possible.
PUC_Snakeman
33 Posts
1
October 1st, 2016 13:00
Here's the fallout of disabling that "MSICPU_CC" service:
With that "MSICPU_CC" service disabled:
- When you open Alienware Command Center 4.0.59.0, it will hang if you click "OC Controls".
- If you manage to close that hung window, then try to relaunch "Alienware Command Center", nothing happens
- You can open Task Manager and kill "CommandCenter.exe", in order to be able to relaunch it
- All other aspects appear to work find, but "OC Controls" is non-functional.
Actually, I've been using "Intel® Extreme Tuning Utility (Intel® XTU)", for my CPU overclocking needs anyway, so not a big loss to me. I highly recommend using Intel XTU.
I'd still like Chris M, and Dell, to respond. I put a lot of effort into tracking this one down, and making info available to the community, and would appreciate followup on it.
Thanks,
Jacob Klein
marctronixx
2 Intern
2 Intern
•
141 Posts
0
October 3rd, 2016 09:00
I have 64gb and its likely the same ram you have.
What are you doing to get windows to freeze? Does it do this on boot each time? I know you posted a lot of info there but im ignorant to all of that mish mash. Im not a tinkerer or gamer and designed this pc for 4k video editing, but would like to know how this freezing occurs...
PUC_Snakeman
33 Posts
0
October 3rd, 2016 20:00
Here is a summary of the 64 GB RAM freezing issue, caused by the Alienware Command Center 4.0.59 "MSICPU_CC" service.... including cause and a workaround.
For me, the freeze happens when:
- I have 64 GB RAM installed
- I go to the Dell Downloads page for my XPS 730x, then download Alienware Command Center 4.0.59
- I install it
- I reboot
- Windows freezes on the login screen.
It happens because Alienware Command Center installs a bunch of Windows services (which you can view using Start -> Computer Management -> Services and Applications -> Services) .. 10 services called MSIxxxxx_CC, but one is not compatible.
- The problem is that the "MSICPU_CC" service is not compatible with 64 GB RAM, and it is set for automatic start, which freezes the PC on the login screen.
- The workaround is to get into Safe Mode, then disable that "MSICPU_CC" service, either by opening Windows services then right-clicking it and editing it, or by using "msconfig" -> Services, to disable it there.
- The solution is on Dell to fix, if they're interested. Still waiting on a response.
- The fallout is that, in Alienware Command Center, the "OC Controls" page won't work with that service disabled, and if you try it, you'll have to use Task Manager to kill it.
RaysXPS730h2c
23 Posts
0
October 4th, 2016 18:00
Does it freeze with Alien command center uninstalled? If not, uninstall alien command center, you can still over clock or set ram speed in bios. Just adjust lights to what you want with the stock memory and then uninstall alien command. They should remain at that color, I believe the fans will also. Then uninstall and put your 64gb in. Then if it doesn't freeze you are good to go.
DELL-Chris M
Community Manager
Community Manager
•
54.9K Posts
0
October 4th, 2016 21:00
4.0.59.0 was for Windows 7/8/10. Uninstall it and test version 4.0.51.0 which was only for Windows 10.
The 64GB configuration is not compatible with the i7-6950X. The sales site makes you choose either the i7-6850K or the i7-6900K. What CPU do you have installed? A user with 64GB of our memory (V51K2) will need to test AWCC 4.0.59.0.
PUC_Snakeman
33 Posts
1
October 5th, 2016 09:00
Hi Chris,
Thanks for responding!
I tried Alienware Command Center 4.0.51.0 as you suggested, and restarted, but it exhibits the exact same behavior as 4.0.59.0. When 64 GB RAM is installed, it makes Windows freeze on the login screen, if the "MSICPU_CC" service isn't disabled.
This is on Windows 10 x64 v1607, with CPU i7-5960X (not i7-6950X), with 64 GB RAM.
My workaround continues to be to disable that "MSICPU_CC" service, avoid "OC Controls" in Alienware Command Center since it won't work with that service disabled, and modify overclock settings using a different tool - "Intel® Extreme Tuning Utility (Intel® XTU)".
Let me know if there's anything I can do to help test a fix.
Thanks,
Jacob
Carbon Based Lifeform
872 Posts
0
October 14th, 2016 10:00
So I Neet Help.
I Installed 64 GB Crucial Balistics RAM. It Runs Fine. XMP Enabled, 2400 MHz.
Problem:
After Upgrading Shutdown or Reboot takes Forever. More than 1 Minute.
Do You Guys Have any Idea?
Thanks.