Printable View
As far as intermittent booting with OC failed error on a Deluxe, but after booting it passes all stressing sw, there is a CPU Vcore Bootup Voltage .800-1.700 which on auto seems to be .800, but when raised to somethin like 1.000, cures probs. That sure would explain booting issues, but no booted issues.
Could you Raja please give us an explain (ask home office) of why that option is present - what is it supposed to do?
Thnx in advance.
This setting is best left at Auto for OC.Quote:
Originally Posted by wazoo99
Hey Raja,
Any beta bios's for the Sabertooth x79? :)
Ron
Mdzcpa I have your problem exactly on 0083b. Same memory sticks too 32gb. Mine work totally stable including Linx, 3D, Prime, Pi, Cinebench, gaming, encoding the lot once booted but cold boot they dont always boot at stock clocks and voltages. Obce they do boot they are absolutely fine with CPU at 5.0+ ghz. Have you tried anything else to improve the situation I have tried the VTT etc but after adjustment it still wont always boot. Strange as I had teh self same sticks and CPU in a Sabretooth and it booted flawlessly at this frequency and was also completely stable.
Unfortunately I had to leave town for work this week and was unable to fully test if increasing vccsa and vtt to 1.3 permanently fixed the issue. Based on all I've read this week (without being home to test) I am skeptical this will be the long term fix. More importantly I'm not really comfortable running 1.3 vccsa and vtt for everyday use.Quote:
Originally Posted by pazza316
My next step when I get home tomorrow is to try the boot voltages. There are CPU and VCCSA boot voltage options. Have you tried these?
I have also read that using manual versus XMP can help. I will try this next along with boot voltages.
Another guess is that eliminating speed step and c state functions along with running a static voltage will help...versus using the offset and other power and heat reducing functions I prefer. So I will try this second to last.
Lastly...the ultimate fix I know that works is to drop the ram speed. Setting to 1600 is a solid fix, and 1833 ran well too with limited testing time. But it bothers me that I know the system can run at 5ghz and 2133 ddr3 once booted in.
RAJA: I saw you post above about using Auto, but given this boot issue a few of us seem to be facing, can these settings help?
Ok, some wierd behavior to report, i have 32GB of corsair vengence 1600 ram, cas 9 1.5v. I boot into the OS, run prime stable, then randomly on the 3rd boot or something, windows gets a bsod or wont boot in, i reset to default settings and it starts working.
mdzcpa I am gonna do some testing on this issue myself this afternoon. Its clearly something in the bios the Sabretooth is setting and the R4E is not. I am not too bothered about the VCCSA at 1.3 etc so long as it boots everytime I am on very good water temps under linx on the warmest core never touch 60c at 5.0ghz and board temps are good too. I just want to sort this cold boot issue.
I will also try all settings at AUTO and report back. I notice your using 16gb of the G.Skill I only have this issue with 32gb never with 16gb. I tried clocking both and with 16gb all is fine. I am also wondering if both of us have a stick that needs more Voltage initially??? I am gonna try this theory too.
If on 00xxb BIOS, can set Rampage Tweak to Mode 1 manually for less aggressive timings.
Ok shamino. I will try this out. Does mode 2 have a similar effect then?? evan less aggressive than mode 1???
I recenlty upgraded to a 2600k and swore I was gonna wait for Ivy to come out to upgrade again but then I found this thread and found a 3930k with an H80 on ebay for $500. I clicked the buy it now without hesitation. I couldn't find a rampage and ended up getting a P9X79 Deluxe. I got the 2011 mounting kit directly from Swiftech and put my system together last night.
http://www.dadepc.com/3930k_2.jpg
How can I adjust the vcore manually? I don't see any settings in the bios that allow me to do that.
The problem was the memory, went from 32GB to 16GB, and overclocking is fine again, sitting at 4.8GHZ with 1.4v, 40c idle. This is with bios 0802. 32GB is a bad for overclocking at this moment, i hope a new bios will fix this.
I'm on my way home now and will do more testing this evening. I'm also going to try the Warm Boot Fast enabled to disable the memory learning that occurs on boot up. Once stable settings are confirmed with stress testing then these values will be fixed with Warm Boot Fast enabled. However...I'm thinking this only applies to warm boot as the option indicates and may not help with cold boot.Quote:
Originally Posted by pazza316
Also...I do think this might be a RIVE issue for my configuration. I did not experience the issue on the P9X79 Deluxe I had running for a day or so before i swapped to the RIVE. I did not have that system running long enough to confirm it for sure, but I cannot remember this issue the first few days.
Im still having the same problem as some others with cold boot. If I go back into bios, reload the " tight hynix profile" then reset timings to 9 10 9, or whatever was stable it boots fine again without having to adjust any voltages, until the next morning or later that day on a cold boot. I think it is related to the memory profiles. Just my guess, but what the hell do I know lol.
The easy fix for now is, on cold boot, go to bios and reload the mem profile, set timings and boot with no problem.
Thats exactly how I fixed it OC Nub!!! LOL!! Not great but without fail it works. Second boot all is fine and rock stable.
On some guides i have read relating to a overclock with a strap multiplier on it i have seem people reducing their PPL by quite an ammount. Can anyone explain the theory of this to me so i can understand. Im new to SB overclocking.
Im trying to get my setup to run with 125 strap so i can get my 2000 memory to run at speed but im having some troubles getting it to post. I have upped VTT and VCSSA to 1.2 but i cant get it to post.
at strap 100 it can handle 4.7 fine with max 1.378 vcore. I could probably tune that down a little but its on a H100 so temps are fine. Dont go much over 70.
There is something im missing.
Im sure they will get it figured out, the support has been awesome so far for this board IMO. But for now, a double boot isnt too much trouble once or twice a day.Quote:
Originally Posted by pazza316
Another thing I noticed, if I am trying to tweak the timings, and it doesnt work/boot. Then I go back and change the timings and or voltages back to what did work, it will still refuse to boot into windows, usually hangs right at load screen before making it to windows (I see "Windows" but no four dots). As soon as I reload the hynix, or hyper profile, depending on what ram im using, set the timings it boots up just fine. It seems once you make any changes to the profile's timings that are unstable/not bootable, something happens and they do not change back when you try and adjust them back. ( hope that made sense).
Also I wanted to say, Im not complaining. I really like this board and the memory profiles. It sure makes it A LOT easier on everyone to have these profiles in the bios instead of having to start from scratch trying to figure out what works with what kit of memory. Now if I can just get a CPU with a strong IMC I can enjoy it even more.
OC Nub...yep the first post into the UEFI works every time for me as well. Unfortunately my wife uses the system for email and small stuff every day and she wouldn't have a clue as to what to do. Jacking up VCCSA/VTT to 1.3v slowed the issue down, but I have now had another "no boot" occurence under those settings as well. It's much less frequent though. Also, altering vcore and vccsa boot up voltage also seems to slow down the occurence rate but not cure it.
Right now it seems my best option for solving the random no boot is to drop the memory to 1600 (although its stable at 1833, 2133, and 2400 once its booted).
That said, I'm actually happy with the board as well. The support has been great, and I'm actually learning a ton about the platform. It runs great at 1600mhz ram speeds at 5Ghz. I'm sure this issue will be sorted in time.
Did you guys manually change the ClkGen Filter Settings?
20UF will trigger a reset at cold boot as well, though leaving at auto will also do that. Or you guys disable that?
I have it set to auto at the moment, but also tried enabled but not with this kit of memory. I will try enabled again, and then disabled if that doesnt work. I wasnt sure if 10UF or 20UF would help anything because other then the cold boot hang up, it clocks the memory very nice and is otherwise stable.
Thanks.
im just saying 20UF may have similar effect as you going into BIOS and not changing anything and saving and resetting.
I have the AI Overclock Tuner set to Manual which defaults the ClkGen Filter to Enabled. That's how mine is set now. The only ClkGen Filter choices when AI Tuner is set to Manual are Enabled/Disabled. Are you suggesting trying Disabled?
no, you're talking about clockgen full reset NOT clockgen filter
im talking about filter which has en/dis/10/20uf
Yep....I see it now. My bad. I've had mine set to Auto (default) in all scenarios so far.
For you guys with cold boot problems when overclocked:
Please list the following:
Motherboard:
CPU Model:
Memory model, include part number and number of modules:
PSU model:
BIOS Version:
CPU Frequency:
Memory frequency:
Clockgen Filter:
Vcore:
VCCSA:
VTT:
VDIMM:
CPU PLL Voltage:
Memory Timings
Rampage Tweak Mode
Any memory profile
Additionally, please list ALL settings you have changed from Auto.
Lastly, please also state the naure of the cold boot problem, ie freeze when loading Windows or failure to POST etc...
-Raja
no promises but you can try this biosQuote:
Originally Posted by HelixPC
http://www.mediafire.com/?s5mbqsba3qjoa6p
And set the Third timings as shown:
http://www.freeimagehosting.net/t/82d2f.jpg
http://www.freeimagehosting.net/82d2f