Trying to set up a sys with 32GB RAM.
DZ77GA-70K works with only 2 (out of 4) 8 GB Corsair CMX32GX3M4A1600C11 modules of this set in DIMM 3 and 1.
With 3 or 4 modules POST stops at 21 or 41.
!! Bought these "pricy" modules because Intel references it as tested memory http://www.intel.com/support/motherboards/desktop/dz77ga-70K/sb/CS-033219.htm here. !!!
When setting the BIOS to "Automatic" it sets 1333 9-9-9 - works fine with 2 modules.
Setting BIOS to 1600 11-11-11-30 (Corsair specification) works fine only with 2 modules, too.
CPU: I7-3770K, PS is a brand new Corsair AX750 Gold Plus.
Does anyone experienced the same problem? Any solutions?
Thx for help.
here it comes.... (Dimm # 2 is the same)DIMM # 1 1 SMBus address 0x50 Memory type DDR3 Module format UDIMM
Manufacturer (ID) Corsair (7F7F9E0000000000)Size 8192 MBytes Max bandwidth PC3-10700 (667 MHz) Part number CMX8GX3M1A1600C11 Number of banks 8 Nominal Voltage 1.50 Volts EPP no XMP yes XMP revision 1.3JEDEC timings table CL-tRCD-tRP-tRAS-tRC @ frequency JEDEC # 1 6.0-6-6-17-22 @ 457 MHz JEDEC # 2 7.0-7-7-20-26 @ 533 MHz JEDEC # 3 9.0-9-9-25-33 @ 685 MHzXMP profile XMP-1600 Specification PC3-12800 Voltage level 1.500 Volts Min Cycle time 1.250 ns (800 MHz) Min tRP 13.75 ns Min tRCD 13.75 ns Min tWR 15.00 ns Min tRAS 37.50 ns Min tRC 50.63 ns Min tRFC 260.00 ns Min tRTP 7.50 ns Min tRRD 7.50 ns Command Rate 2TXMP timings table CL-tRCD-tRP-tRAS-tRC-CR @ frequency (voltage) XMP # 1 6.0-7-7-18-24-2T @ 457 MHz (1.500 Volts) XMP # 2 11.0-12-12-32-43-2T @ 838 MHz (1.500 Volts)
EFI is disabled from the beginning - I couldn't install win7pro 64bit with EFI because it did not work with the initial bios.
Meanwhile I switched the bios to the "traditional" view. There, all HDs are visible and it is possible to arrange the boot order. So - am more than happy to start the system without the F10 work around. Obviously the programmers of the new bios GUI can't keep track.... - but who cares
I'm having a very similar problem. I just bought the DZ77GA-70K mainboard with a i5-3570k processor and 32GB RAM Corsair Vengeance CMZ8GX3M1A1600C10.
With all RAM slots occupied it does not work. The most I'm able to run is 16GB - two modules in DIMM3 and DIMM1.
I've checked every module separately, and everyone is running so I don' think the RAM modules are faulty.
What I've noticed while trying every combination of occupying the slots was, that the same combination might work one time and might stop working for no apparent reason later.
Upgrading BIOS to version 45 didn't change anything.
Sad such a noble reputation has turned into another sell and fix later manufacturer.
Perhaps Foxconn is getting more money from Apple to do QA on their Xeon based systems, that actually load Max RAM and work 100%.
I'll check back later in hopes Intels consumer parts will funtion 100%.
If not, Supermicro actually checks their boards out still and has some Z77's due out in 2 weeks.
I still love Intel, but this sad bit of information, especially on the suggested Memory/Tested modules not working is very sad, and untypical, but we need working boards, not bells and whistles that can't handle the very RAM that was " used " during testing.........
I have 32GB memory in this board - 4 x 8 GB G.Skill Ripjaws X 32GB Kit, Model F3-1600C9Q-32GXM. Works at 1600 speed with XMP1 or XMP2 profile (Both the same timings)
One other thing you mentioned is
"Marvell SATA controller does not work at all (latest STOR_Win7_XP_22.214.171.1246 installed). Connecting WD2002FAEX 2 TB to the gray ports results in nice bluescreens and disconnects of the hard drives!!'.
That driver is for the SATA INTEL ports. You need to load the Marvell SATA driver to utilize those ports, and you should only use hard drives on those ports. I have 2 3TB SATA III Seagate drives on that controller and they are FAST!
I'm having a similar problem but with different hardware.
Started with 8 gigs Corsair memory [don't have number but it was 1600 2x4] . The new build would not boot with the memory in any configuration in the slots. Bad board? Returned it and got a new one. Same deal. Returned memory and got some Kingston HyperX KHX1600c9d3k2/8gx [2x4 gigs]. Fiddling around with it I get the computer to post with the sticks in the first two slots - it will not work in the 2nd and 4th slots [blue] which Intel says should be used. Update the bios from 0057 to 0070. The memory is running at 1333 1.5 volts. I enable the XMP profile and it changes to 1600 at 1.65 volts. I go buy a second set of the same memory and install it for a total of 16 gigs.
With this configuration the computer will boot and run most of the time. Sometimes I get the 3 beeps and have found that I must remove the stick in the 4th slot then the computer will boot. I can put the 4th stick back in and the same thing - boots most of the time but not always. When I set the bios to default the computer will not boot with 4 sticks in it at all period. This would be at the 1333 1.5 volts settings.
Right now I have the 4th stick of memory sitting in the box. Everthing seems to work fine with 12 gigs in the first three slots in XMP mode.
A guy on Intel chat told me the processor only supports 1333 1.5 volt memory but everything I have read says different...that it will support 1600 @ 1.65 volts.
What you all think? I think the bios is goofy. Looks good but has glitches. I've tried the all the memory in different slots so there's no problem with it. This returned board was acting the same way so I don't think it's a bad slot.
does any of you have some earlier experience with intel support and how much time it takes them to fix things like the above?
because right now i'm wondering if i should wait for intel to finally make a BIOS that works with 32GB RAM without problems, or should i try to get my money back for the mainboard and buy another one (absolutely no intel board this time). the latter would be a bit complicated, as i bought the mainboard in a bundle with the processor.
well i'm not sure it is a BIOS issue, but since all the memory modules do work separately it leaves me with the options that it's either BIOS, or the mainboard is malfunctioning. or maybe i'm just totally missing something
i even asked at the store where i bought it if these modules are compatible with the board and how many GB of RAM can i have, and they answered that i can have up to 32 GB RAM with these modules. but i think they based that just on the board's specification and haven't physically tested it.
and here are the parts:
Thank you for your reply.
I used additional SATA_allOS_126.96.36.1999_PV_Marvell (INTEL download for this MB) having these problems. Will say: the recommended configuration.
Nice to hear you can work with 32 GB.
Which BIOS version do you have installed?
I have 4 * 8GB Corsair (CMZ16GX3M2A1600C10) and I managed to get three of them work, so I currently have a total of 24 GB memory.
I am unable to boot up when all four modules is inserted.
Intel - please go fix! :-/
Currently I cannot remember which slots is being used. But as I recall, it didn't matter how they were inserted.
The board is being used as a server, so I rather not reboot unless it is really necessary. But I will report back when that happens!
I haven't restarted the server, but I just remembered which slots is being used:
DIMM 3, 1 (channel A) and 4 (channel B). (see item 5 for explanation: http://downloadmirror.intel.com/20956/eng/dz77ga-70k_IntegrationGuide02.pdf http://downloadmirror.intel.com/20956/eng/dz77ga-70k_IntegrationGuide02.pdf)
All memory modules are of type CMZ16GX3M2A1600C10. (Corsair 8 GB modules)
Grrr, hate that such a hightech board does not support this! Again - Intel - go fix!
I RMA-ed my entire kit to corsair and got a new one. Without changing a think except enabling the xmp profile in the classic bios config it now works @1600MHz. No beeps or anything, not even once.
There was either something wrong with the modules after all or there is an incompatibility between the DZ77BH-55K and earlier versions of these dimms. Maybe this is even an accident. Maybe I got dimms using ic's from a different manufacturer. Less bus capacitance or so.
Whatever the reason, I'm glad it works now.