MS-7670 (Big Bang Marshal) - RAM WILL NOT run at default speed.

doubleohseven

New member
SECOND LIEUTENANT
Joined
May 20, 2011
Messages
138
Hi everybody, I am having a strange problem I hope you all can help me with.  I am getting a double boot issue, when I start up the computer, it gets stuck at code 69 (late north bridge initialization), then reboots.  This is where it gets strange - upon reboot, the computer passes the point where the BIOS loads, then boots to a black screen - it will not load the OS (or boot from a CD or a USB drive for that matter) no matter what I try.

The problem seems to be correlated with RAM. The first RAM I had on this system was http://www.newegg.com/Product/Product.aspx?Item=N82E16820220535, I ran with X.M.P. enabled (at 1866, since this RAM was 2000), and had the issue described above.  Went ahead and tried it at 2133, disabled X.M.P., loosened the timings, and bumped the voltage up to 1.7v - still a no go. So I re-enabled X.M.P., lowed the voltage back to 1.65v, and tried 1600. It worked, and that is how I was using the computer for almost 2 months with no problems.  This weekend, RAM went on sale at newegg, so I sprung for some 1.5v RAM, thinking that might be the issue. I bought http://www.newegg.com/Product/Product.aspx?Item=N82E16820233142, which says it is optimized for Sandy Bridge systems. Well I tried all the steps I did with the other RAM, and its still a no go.  I am running currently at 1.5v, with X.M.P. enabled, at 1600 (default it 1866).

P.s. This was happening with BIOS 1.0, so I upgraded to 1.1 with no problems, but the problem is still there.

I hope you guys can help me troubleshoot this problem, because I am at a loss here. Thanks in advance for all your help.

-Frank

 
Default is 1333. RAM that has SPD Profiles that set the correct RAM Speed for the Sandy Bridge platfform should be purchased. There is no significant performance increase with the Sandy Bridge platform when running faster 'rated' RAM. Tests have shown this to be true; https://forum-en.msi.com/index.php?topic=147704.0 
 
HU16E said:
Default is 1333. RAM that has SPD Profiles that set the correct RAM Speed for the Sandy Bridge platfform should be purchased. There is no significant performance increase with the Sandy Bridge platform when running faster 'rated' RAM. Tests have shown this to be true; https://forum-en.msi.com/index.php?topic=147704.0  

Thanks for your reply HU16E.  Well, this RAM said "optimized for the Sandy Bridge platform," so I am pretty sure it meets all the requirements for this system (it is also name brand RAM, so this should not be a problem).  As for the link you provided, I read that long before I built this computer... regardless, that is not the question at hand here.  I purchased 1866 RAM, therefore, it SHOULD run at 1866. The fact that I have also tried TWO different brands of RAM also is strange, I do not know if i have a setting set incorrectly, or have forgotten something.  Secondly, why when my system double boots, it will not load into the OS, as well as boot from a CD or USB drive?

Anyone else have any ideas? Thanks again...
-Frank
 
Well, this RAM said "optimized for Sandy Bridge systems," so I am pretty sure it has all the requirements for the system.
For the double boot, have you disabled EuP 2013? That in many cases cures that unless there is underlying other reasons, RAM for one. To be 'Optimized' for Sandy Bridge platform, the modules should have DDR3 SPD profiles for 1333. It will run at 1866 if certain parameters are met. #1, the CPU IMC will cooperate, & the RAM will most likely need to be set up manually in the BIOS. Sometimes just setting X.M.P. will work, but in the event it doesn't, manual setting in BIOS can be tried. Unfortunately, RAM manufacturers mislead the public with their claims. If you have CPU-Z utility, look at the SPD Tab & note the bandwidth. Your RAM may be 'rated' 1866, but most likely 1333 chipped, possibly 1600. Suggest purchase of RAM that has an SPD profile that will default to the Intel native CPU IMC supported specifications of 1333. If the system won't run correctly with the RAM at 1333, then there is a problem. This is not to say 1600, 1866, 2000, 2133 modules won't run at those OC'd speeds, compatibility can be a problem as to their SPD profiles. BIOS revisions are always under development to improve these compatibility problems.
 
HU16E said:
For the double boot, have you disabled EuP 2013? That in many cases cures that unless there is underlying other reasons, RAM for one. To be 'Optimized' for Sandy Bridge platform, the modules should have DDR3 SPD profiles for 1333. It will run at 1866 if certain parameters are met. #1, the CPU IMC will cooperate, & the RAM will most likely need to be set up manually in the BIOS. Sometimes just setting X.M.P. will work, but in the event it doesn't, manual setting in BIOS can be tried. Unfortunately, RAM manufacturers mislead the public with their claims. If you have CPU-Z utility, look at the SPD Tab & note the bandwidth. Your RAM may be 'rated' 1866, but most likely 1333 chipped, possibly 1600. Suggest purchase of RAM that has an SPD profile that will default to the Intel native CPU IMC supported specifications of 1333. If the system won't run correctly with the RAM at 1333, then there is a problem. This is not to say 1600, 1866, 2000, 2133 modules won't run at those OC'd speeds, compatibility can be a problem as to their SPD profiles. BIOS revisions are always under development to improve these compatibility problems.

Thanks for your help again HU16E.  Yes, I have already disabled EuP 2013 (as well as all the other phase control options in the green power section).  The fact that it double boots at 1866, but boots normally at 1600, leads me to believe it is the RAM, but I could be wrong. Also, is there a reason why it does NOT load the OS or boot into anything once it double boots (because it seems other people have double booting issues but are able to get into their OS just fine)?

As for the RAM goes, this makes ALOT more sense now... so basically these RAM companies put 1333 or 1600 chips on the RAM we buy, and "OC" it themselves and advertise it at 1600, 1833, or 2133?  If this is the case, that is QUITE misleading! I am assuming I have a 1600 chip on mine since it works at 1600, but I will certainly check that.

Thanks again,
-Frank
 
The double boot did that with the B2, B3, & the Z68 at certain overclock settings. It is a frequency anomoly I believe. I wish I had an answer about the OS loading issue though. Never did experience that. Hopefully someone with a lot more knowledge of what can cause that will happen by soon.

As for the RAM goes, this makes ALOT more sense now... so basically these RAM companies put 1333 or 1600 chips on the RAM we buy, and "OC" it themselves and advertise it at 1600, 1833, or 2133?  If this is the case, that is QUITE misleading! I am assuming I have a 1600 chip on mine since it works at 1600, but I will certainly check that.
Yup! Marketing trickery at it's finest! Sometimes even 1066 chips. :lol_anim:  CPUID's CPU-Z Memory Tab & SPD Tab will have lots of information shown.

Added: What may be of help, could you provide a full list of your systems components? It will really help in the suggestions & recommendations. Sometimes even PSU's can cause odd behaviors.
 
HU16E said:
The double boot did that with the B2, B3, & the Z68 at certain overclock settings. It is a frequency anomoly I believe. I wish I had an answer about the OS loading issue though. Never did experience that. Hopefully someone with a lot more knowledge of what can cause that will happen by soon.
Yup! Marketing trickery at it's finest! Sometimes even 1066 chips. :lol_anim:  CPUID's CPU-Z Memory Tab & SPD Tab will have lots of information shown.

Added: What may be of help, could you provide a full list of your systems components? It will really help in the suggestions & recommendations. Sometimes even PSU's can cause odd behaviors.

Ahh interesting... yeah hopefully someone will have an answer to the OS not loading after the double boot.

As for the RAM, I checked CPU-Z, it is a 1333 chip. What an epic fail on my part there. If I would have posted this earlier, I would have saved myself $110. Live and learn I guess! Off topic: Can I run mismatched RAM together (the 2000 and 1866 together if I clock them both at 1600)?

Anyways, here are the system specs:
Mobo: Big Bang Marshal
CPU: 2600k
RAM: Corsair Vengence 8gb 1866 (running at 1600)
PSU: Corsair Performance Gold AX 1200 watt
GPU: Gigabyte Super Overclock 560ti SLI x2
HDD: x2 Corsair Performance 3 128gb's in RAID 0
SPU: Creative Titanium HD
NPU: Visiontek Killer 2100


-Frank
 
Can I run mismatched RAM together (the 2000 and 1866 together if I clock them both at 1600)?
It can certainly be tried, usually with modern systems, it will fail. Sometimes even RAM of the exact same type & brand in every detail will fail if from different production batches. I had some identical RAM kits that one set had Elpida chips, & the other batch were Samsung. Now that will make for an interesting situation. Give it a try, no system damage can become of it as far as I know. :-))

SSD or platter drives? I'm always suspicious of SSD's. :lol_anim:
 
HU16E said:
It can certainly be tried, usually with modern systems, it will fail. Sometimes even RAM of the exact same type & brand in every detail will fail if from different production batches. I had some identical RAM kits that one set had Elpida chips, & the other batch were Samsung. Now that will make for an interesting situation. Give it a try, no system damage can become of it as far as I know. :-))

SSD or platter drives? I'm always suspicious of SSD's. :lol_anim:

Good to know, I will try it out tomorrow.

Just noticed we are running the same power supply, see it in your sig. :D

Err, I am running SSD's... x2 Corsair Performance 3 128gb's in RAID. lol. Please tell me this is not the cause for the OS not loading after the double boot? Honestly, I would not mind the double boot AT ALL if it would just go into the OS for goodness sakes!!! lol!

^Updated system specs.


-Frank
 
Your CPU has a 1333 memory controller, above that speed anything can happen.
That your memory can operate faster doesn't matter.
It's the same as with a car, when you put 300KM/H tires on it, that doesn't mean the engine can reach it.

Ergo, set your memory to 1333 and work your way up until you get problems then go 1 notch down to make it stable.
 
Bas said:
Your CPU has a 1333 memory controller, above that speed anything can happen.
That your memory can operate faster doesn't matter.
It's the same as with a car, when you put 300KM/H tires on it, that doesn't mean the engine can reach it.

Ergo, set your memory to 1333 and work your way up until you get problems then go 1 notch down to make it stable.

Thanks for your reply Bas. This may be true, in which case, I am disappointed... but at any rate, I am seeing other people overclocking their RAM on Sandy Bridge systems to 1866 and even 2133. It can not be my RAM, cause I have tried two brands already (and the one stick trick with each of them as well).  So in this case, I find it suspect that I can not go over 1600 (why 1600 and not 1333, and why with both brands) on this system?

Also, why am I not able to load my OS or boot from any devices after the double reboot? Like I said previously, I would not mind the double reboot at all if I could just boot up correctly at 1866 or even 2133. Two strange problems that seem to correlate together... more than coincidence I think.
 
Well a little update, I was able to put my old RAM in with my new RAM, booted up just fine at 1600. Now I have 16gb :D Will I see any performance decrease from using mismatched RAM though?

On a lower note, problems above still exist...
 
Did you try raising voltage to the MC and to the CPU (vCore) proper in addition to the DRAM voltage?  Not sure where your set, but both those will need a boost for 2133
 
Will I see any performance decrease from using mismatched RAM though?
Run MaxxMEM2 v1.95 in all the configurations & combinations, compare results, that will then provide an answer. Run the tests several times each to get an average.

:think: He's lucky it runs at 1600 with mixed RAM as it is. 2133? :rofl2: Anyway, 1600 & above is OC section of the forum stuff. Vengeance seems to be maxed out as 'rated', OC'ing above already OC'd 'rated' speed is often a dead end endeavor. The double boot issue in relation with getting into the OS is the one to concentrate on. :-))
 
Tradesman said:
Did you try raising voltage to the MC and to the CPU (vCore) proper in addition to the DRAM voltage?  Not sure where your set, but both those will need a boost for 2133

Excuse my ignorance, what is the "MC" voltage? Also, I did not know vCore had to be raised when overclocking RAM! I will go ahead and try that once I figure out what "MC" is! :D I am currently running at 1.65v on the RAM, and 1.380v on the CPU @4.7GHz (2600k, specs above). What would you suggest?

As for the mixed RAM running at 1600, it seems I am very lucky!  I have kinda given up on OC'ing the RAM... :P

But I completely agree, the double booting with no loading into the OS or booting from ANY devices is what I should concentrate on.  After the double boot (1866 or 2133 on the memory), it gets passed the BIOS screen, then sits at a cursor blinking, will not load into the OS or boot from any CD or USB devices...
 
doubleohseven said:
Excuse my ignorance, what is the "MC" voltage? Also, I did not know vCore had to be raised when overclocking RAM! I will go ahead and try that once I figure out what "MC" is! :D I am currently running at 1.65v on the RAM, and 1.380v on the CPU @4.7GHz (2600k, specs above). What would you suggest?

As for the mixed RAM running at 1600, it seems I am very lucky!  I have kinda given up on OC'ing the RAM... :P

But I completely agree, the double booting with no loading into the OS or booting from ANY devices is what I should concentrate on.  After the double boot (1866 or 2133 on the memory), it gets passed the BIOS screen, then sits at a cursor blinking, will not load into the OS or boot from any CD or USB devices...
MC (or IMC) is the Memory Controller (or Integrated Memory Controller), sometimes it will be listed both ways. Not really sure about the CPU V. increase as being needed, but if it is, then the recommended upper voltage limit needs to be watched. Does the double boot & OS entering problem not exist when running the RAM & CPU at it's current level? Yes, 1.65v's DRAM V. is the maximum limit. You have a 'really' decent OC, so trying to push it farther for an everyday use rig, is up to you of course. The blinking cursor in the upper left screen corner can mean not enough DRAM V. (which you are already maxed at), or CPU V., which is recommended by some in the industry to keep at 1.400v's or below.
 
HU16E said:
MC (or IMC) is the Memory Controller (or Integrated Memory Controller), sometimes it will be listed both ways. Not really sure about the CPU V. increase as being needed, but if it is, then the recommended upper voltage limit needs to be watched. Does the double boot & OS entering problem not exist when running the RAM & CPU at it's current level? Yes, 1.65v's DRAM V. is the maximum limit. You have a 'really' decent OC, so trying to push it farther for an everyday use rig, is up to you of course. The blinking cursor in the upper left screen corner can mean not enough DRAM V. (which you are already maxed at), or CPU V., which is recommended by some in the industry to keep at 1.400v's or below.

Yeah, I know about the 1.4v recommended limit, which is why I stopped at 4.7. I am VERY happy with this OC, and will not be OC'ing any farther as far as the CPU is concerned.  

The double boot/ not loading into the OS is non-existent at 4.7 and 1600, it only happens when I try to OC the RAM past 1600 (seems to be the magic number for some reason with both brands of RAM, which is the only reason I suspect I have a voltage/ other setting set incorrectly...)

As far as MC/IMC, I do not remember a voltage setting for that in the BIOS... would it be possibly listed as CPU IO voltage? That is currently set to "Auto," and I thought I remember that having to do with the RAM somehow, not sure though...
 
As far as MC/IMC, I do not remember a voltage setting for that in the BIOS... would it be possibly listed as CPU IO voltage? That is currently set to "Auto," and I thought I remember that having to do with the RAM somehow, not sure though...
CPU I/O works in relation with the Memory, however, if all is stable & no further issues are noted, it may be best to leave that one on auto. If you have a digital multi meter, you can check the actual voltage at the V-Check point.

The double boot/ not loading into the OS is non-existent at 4.7 and 1600, it only happens when I try to OC the RAM past 1600 (seems to be the magic number for some reason with both brands of RAM...)
Sounds like you have it well under control then. :biggthumbsup:
 
 
HU16E said:
CPU I/O works in relation with the Memory, however, if all is stable & no further issues are noted, it may be best to leave that one on auto. If you have a digital multi meter, you can check the actual voltage at the V-Check point.
Sounds like you have it well under control then. :biggthumbsup:
 

Right, I was just wondering if the CPU IO would cause the "blinking cursor" when the system double boots at 1866 and 2133.  Also, no MC/IMC voltage settings for Sandy Bridge or what?

And yes, I do have it under control, and it is very stable! I love my new system/setup! :) Looks like I might have to settle for the 1600, and forget about the double boot issues...
 
Exactly what settings are you inputting for DDR-1866?

Juice DRAM voltage to 1.67V.  Change timings to 9-9-9-27 CR2.  Set tRFC to 88-92.
 
Back
Top