I don't use the profiles but I have in the past and they didn't help.
I 1st thought it was vccsa or vtt.
Then I thought it was dram rtl's and iol's, because well, long story kinda...
Those sets of timings are baised off an offset, which is a royal pain in butt.
You set say -2, restart and end up getting results you don't expect.
They just don't work right to put it simply.
Auto works but they can change on there own, and they can change baised on the order you put your sticks in (using the same slots).
Because of that I thought these timings were the main prob, and because when I asked for help on this on the overclock.net and got screens of people's good bandwith at around 2600mhz these timings differed greatly from mine.
I manage to get it to behave a little by switching one of my sticks around, but setting it manually is still like the lottery :\.
It does some really goofy stuff when you try to manually offset them, very tricky stuff.
I spent a few days working on them, I can kinda get them todo what I tell them todo lol.
Anyways.. I had managed to get it to match another dudes timings and it didn't fix the bandwith prob.
Another was the latency boundry setting and rampage tweak mode, didn't help.
Dram clk period didn't help.
Other settings I tried were mch recheck, mch fast reboot, training options..., clock gen full reset.
Even tried disabling the epu power savings and spread spectrums (which I normally use).
Tried every single voltage, couple diff ram profiles, swapping my sticks around...
For a while there I was worried that I would need to rma my ram
.
In the end it's just some goofy bug with the way the cpu and ram div initializes.
(Oh and it affected both my cpu's, 1st got fried by accident)
One of the 1st things I started doing was complain about the 2400mhz ram div being slower then 2133...
And then at one time, I managed to get my bandwith back, and then I changed my cpu multi and I lost my bandwith (my board usually but not always powers off during a multi change).
There were times were I wanted to take screens of the 2 diff ram divs and saw that both had the bandwith issue.
Somehow I figured out if I change both at the same time in the right combo I get the bandwith back :\.
It's a really annoying bug.
Once you fix it, sometime you're gonna power your machine off and it's gonna be right back.
Listen to this, I saved the good bandwith runs in my cmos profiles, several times before I figured it out.
Say you have bad bandwith, load a cmos profile that had the good bandwith and you will not fix the bug ^^, that in it's self is really crazy.
Then again the bios profile doesn't save the boot logo setting for example...
But it's gotta be something todo with the bios'es cold boot code.
Heck it could even effect all x79 bios'es I don't know, what I'm saying is maybe it's even an ami bug.
But it's probably asus.
I've got a list of a dozen (at least) bios bugs for this board of mine, I was gonna try to show them to RGone but I got busy with android 4.4.2 and linux instead.
The one we're talking about though is the one I'm most concerned about, other then the darned boot order and boot menu bugs.
Bookmarks