I agree, mine is can do 367 on air.
Printable View
I agree, mine is can do 367 on air.
My Crosshair IV and 1055T combo are acting up...
I have the following settings applied:
In the first boot and ONLY in the first boot, after Windows pops up, it works for a while and then, inevitably after a few seconds or minutes i get a BSOD. I then shut down the power supply in the power button, let the motherboard "discharge" and power on the PSU once again. I press the power button and it boots happily to never crash again until i leave it off for a good 6-7 hours time.Code:CPU Ratio Setting 13.5x
Turbo Boost Disabled
CPU Bus Speed 300
PCIE Clock 100
DRAM Clock 1600
CPU/NB Auto
HT Link Auto
(DRAM SETTINGS) 8-8-8-24-1T (all the rest is Auto)
CPU Voltage 1.4750000
CPU/NB Voltage 1.2000000
CPU VDDA Auto
DRAM Voltage 1.6500000
HT Voltage 1.3250000
NB Voltage 1.3250000
NB 1.8v Voltage 1.8285000
SB Voltage Auto
VDDR Auto
VDDPCIE Auto
DRAM Ctrl Ref Voltage Auto
DRAM Data Ref Voltage Auto
Load Line Calibration Enabled
CPU/NB Load Line Cal Enabled
CPU Spread Spectrum Disabled
PCIE Spread Spectrum Disabled
Also, RAM is in "UNGANGED" mode and INTERLEAVE in Auto
If i turn the PC off and back on 3-4 hours later, this doesn't happen. It does happen if i turn it off now, go to bed and turn it back on - BSOD after windows loads as i described above.
The RAM i'm using is GSKILL Trident 2x2GB PC3-12800 8-8-8-24 at 1.60v.
Any ideas why this is happening? :shrug:
make a bootable USB key via the HP tool, copy the dos files to it and you can flash firmwares biosses etc... eg linkie here : http://www.lowfps.com/creating-a-boo...sb-thumb-drive
Brian:)
Quite right on the ability to run 350Mhz FSB. Up to that point it is very easy utilizing the right ram divider.
On the FSB/ram ratio's, wouldn't 1-1 be almost impossible? You would need an 800Mhz HT and 1600Mhz ram(800Mhz CPUz) to be at 1-1. 400HT and 1600Mhz ram would be 1-2 ratio, which would be about the best you could attain on this architecture.
If AMD could have only refined the NB even further would have been a major performance advance on this architecture. Having the cache running at 1-1 at CPU speed in itself would take us several steps up, with the memory at 1-2.
I too am perplexed at the Asus boards inability to scale HT/FSB above 350-360Mhz. I figured it had to be the board and/or bios. When I tested for DFI back in the NF4 era alot of the NF4 boards had trouble pushing high HT. Abit, MSI, ECS...I had a bunch of them and none would do much better than mid 350's. The early DFI NF4 would not boot up at 400Mhz HT or higher, but we could push it up booting at a lessor HT and then using SetFSB to take it where we wanted it.
Subsequent boards had registers in the bios adjusted based on our feedback data and could boot at 500Mhz HT and higher.
Are you working on the Asus or Gigabyte Brian, or both? Can you boot at 400+ or are you setting it after boot into Windows?? Thanks in advance my friend:)
Best regards,
Randi:D
Randi, I work on everything and anything, just stating thuban itself is capable.
420 HT i'm referring to is a boot stable/benchable. I hate that software crap.......it's misleading.
400 HT will give users 1600 ram IIRC with the 800 ram divider. More importantly that equals to a nice 4000 usable NB for the cold guys.
Here's a shot for you that I was booting at.
Everything was eliminated from equasion partly due to using a stock x4 cooler.
http://chew.ln2cooling.com/AMD%20build1/420ht2.jpg
Excellent my man:up:
Thats what I wanted to hear re: that you are booting into Windows at 400+HT. 400HT+ and 1600Mhz Memory+ and 4000Mhz NB will give you guys running LN2 a decided boost at 6000Mhz + CPU speed. With the improved NB where alot of the guys here are at 3200Mhz or a little better, the 400HT and 1600 Mem will also give them a nice boost in bandwidth at moderate overclocks.
I was working with mine this morning at low CPU mhz, but on the Asus CF IV w/ 801 bios anything over 365ish is a no go. I've got the bios here on my laptop to look at right now and tinker with. 400HTT and the 800 divider are important. I tried maintaining 1-2 ratio with 333HT/1333 Mem with tight timings but even with a 3500Mhz NB the system bandwidth was not as high as I last posted in my own thread.
Great work Brian, looking forward to great things:)
Randi:D
Do me a favour and next time it crashes , reboot and go into the bios and read out the CPU NB voltage plz... if it's lower then the voltage you applied report back... though I must say 1.2CPU/NB voltage is already low... Try upping to 1.25-1.3ish
I made a small homevideo of my NB voltage issue I've been experiencing since 0707 bios... passed it on to the big shots at Asus...
Thank you Leeghoofd, i'll do that in the morning as it is the next time it will exhibit that behaviour :up:
I'll try upping the CPU/NB as you mentioned.
Seeing this is turning in to a general CH4 topic, isnt it smart to change the thread name and such?
Well I've been busy trying to persuade Jack C for weeks about it, he still says it's safe mode all the time Brian... some people never listen... so I won't rest till it gets solved or it pops up in the review next week...
I need people to back me up... to get them moving !
Not sure if you remember but m4a79_T deluxe ddr III had the same exact issue but with vcore. Work around was to not set vcore to ignore so it would peg the overvolt warning every boot.
When it stopped warning you that you were over volted you knew your vcore had dropped. I think that issue and this issue may be a form of OCP kicking in which i also found to be the case on the m4a89TD Pro.
Sure they will get it nailed down but i've already moved on and am working on other things to better end users experience with locked chips now :D
Another nice one. I was just pushing HT ref clock to see how high it would go. At 330 (stock ht and NB volts) it refused to boot and i had to press reset twice. After that it booted at default settings but all settings including OC profiles were gone!
The only thing that remained were clock and date settings. :( Has anyone else had this before?
I had a slimilar thing once .
all settings went back to auto , and lost my first 4 saved oc profiles in the bios . the last ones were still there .
this was with 0801 bios .
Also i need to powercycle my psu every time an overclock locks up . :down:
Yah thats not uncommon. I have run into that issue on asus and gigabyte.
When pushing the limits things like that are to be expected. Luckily im a bios setting crack fiend. I know all my settings by heart for every board i have :ROTF:
It's certainly an issue; quite funny how some people refuse to acknowledge there's a problem :D.
This whole problem makes me feel like there's a VID setting issue. Have you tried to replicate this behavior using the offset voltage mode (remember: I assigned you this as homework!)? If there's no problem with the offsets, it's definitly a VID table screw-up ... something which has been on some AMD mainboards in the past.
Well, I just got my first message on the subject, but I assure you it will be addressed tomorrow night with engineering. ;) In the meantime, I must have a perfect setup on four boards here as I started testing it and have not been able to replicate it yet. Albrecht is going to send me his OC profile so I will start from that point. Of course that means I have to roll back to a crappy CPU stepping to match his system. :rofl:
What is HT link speed set at? If it is auto, go in and back it off to 2000MHz as you clock HT ref up. Also, cooling and CPU quality makes a difference in this area but with decent water cooling or really good air, I can clock my good 1055T up to around 410 HT ref clock. I have to really fine tune the voltages (HT, CPU VID, CPU-NB VID, and NB/SB VIDs) around 370~380 to get that last bit out of the board with the Thubans.
Any chance for us with 1055T to be able to use a multiplier of 16.5 if we disable turbo? Would love that feature!
Just read this.
I'm not sure it's even possible to do it using the existing DDR2 memory dividers. Waaaaaay back when the first DDR3 boards were launched, I already asked some manufacturers to look into this, but most of them reported it's not as easy as just opening up the 'locked' dividers.
Check out page 185 of the BKDG of AMD's 10h. In short, the type of DDR memory detected determines what memory dividers are available. When DDR3 is used, the Ddr3Mode register is set to 1 thus enabling 400/533/667/800 dividers.
Do note that there are unused (reserved) divider registry keys available, but as far as I understand they are locked and not useable.
I'm not following you.
Real 1:1 divider (DDR3-400) could actually be useful. It's proven many times before that the high memory frequency is holding back the HTT clock.
I think if you choose 400 on ddr III it shows as 2/1?
Not good with ratios. But at 350 HT and lowest ram divider 1400 ram is not what I would call high memory frequency.
The problem is related to memory IMO but not high mem frequency unless you consider 1400 ish "high"
Try the lowest ram divider you will see what i'm talking about.
Internal latencies are changing is my guess with the lowest ram divider on ddr 3 as well as some other things.
Work in progress not saying it can be done but it can't be done unless we try :)
Brian, you are absolutely correct. When using the 400 divider, 1600 Mem and 400HTT, CPUz would show memory at 1/2. Massmans mention of 1/1 would mean that you'd have to run 800Mhz HTT on the 400 divider to be at 1/1 with the memory at 1600Mhz. That won't be happening anytime soon without a miracle:D
Edit: Confusion may be that 400HT is DDR, effectively 800Mhz ..... HT 800 Mem 1600 - Memory is twice HT speed
-------------------------------------------------------------------- 1-----/----2
You are definitely pressing in the right direction my friend and you have many diligantly watching your progress.
best regards,
Randi:D
Lowest divider for the DDR3 is indeed 1:2, or "400". Set 400HTT and you get DDR3-1600 speeds.
The problem is the combination of high HTT and high memory. DDR3-1400 isn't high, no, but then again the limitation isn't at 350HTT either. Think about trying to reach HTT frequencies of 450+ ... with DDR2 you can just run 450MHz memory, but with DDR3 it's 900MHz.
We've seen this on the previous generation of hardware ... the board (memory type) limits the HTT overclockability of the CPU.
Hi guys,
Yesterday I flashed 0801 bios. Since I have 1,5Mhz swing HT speed. Somebody, know how can we solve this? or I need back 0707 bios..
await a new bios mate... downflashing is not an option...
any one try downgrade bios with afudos 236ES
afudos (bios.rom) /p /b /n /c
Well, that's exactly what's happening...
http://www.tech-caffe.com/gfx/cpu_nb.jpg
I had it set to 1.200000 and it set itself to 1.052 on the first boot. Meanwhile i did what *chew described (save profile/load defaults/reload profile), hope somehow it fixes it.
Have you got Auto Load Lane calibration Enabled or Disabled in that tab NaMcO?
I haven't had this issue on my system, but I'm running it Enabled since day 1.
Interesting stuff ...
Ok, now I know what you're talking about.
I'm not sure if the inability to boot at 350HTT and the lower max HTT on DDR3-based motherboards are different problems or have a shared underlying cause. What I do notice is that changes in the memory setup (single or dual, different memory slots) change the maximum HTT frequency I can post at.
What do you have in mind as cause of the problem?
I was having HT ref swings, not able to raise mulit, well it would raise then in windows, regaurdless of which one I loaded into, it would read as if I didn't change it and some other issues. While in the bios, I hit that refresh button on the back near the PS2 ports. I have been running 13.5x305 HT Ref for over 24hrs now with no swing on HT Ref. I can raise multi now and everything seems to be normal again.
Regarding the HTT swing. I only experience this in idle (365MHz to 368MHz) and only see this with CPU-Z. Leeghoofd send me the THG_clock application and that shows no swing at all.
Question is if it's a hardware issue or a CPU-Z issue.
Sorry to be off topic,but what ram slots are you guys using,ie blue or black,reason i'm asking is with my old GD70,it preffered the blue slots,furthest away from the cpu socket.Just curious.:)
MRL tables at very low ram dividers and or internal latencies changing running things very tight.
Very similar to why we see better results on some boards with 1333 divider at 270htt versus 1600 at 225htt. aka 1800 ram but diff methods to get there.
No reason since I doubt most are running 2/1 ram divider default for 24/7 with that type of ram why some things can't be slacked a tad. It has to be memory issues imo becasue I peg D5 and the easiest way for me to peg D5 is tick off my ram.I can raise HT to some retarded speed and it will never peg d5 on port 80. I can also crank it higher that 350 with 1066 divider but once again i hit a wall there to depending on quality of ram and or "IC's".....but ram has to be uber. I want to make high HT clocking for the "AVG" guys without uber 2000 ram easy, so 2/1 divider is the one to tune.
This is also going to cause a validation issue to say the least.
With the swings i've seen 7 gig on ln2 with a chip that "really" does 6936 on lhe is possible now ;) No diff than intel floating BCLK atm.
I've seen larger swings than 2mhz HT the higher i'm clocked and the less stable i am. So based on this are we to accept "bugged" cpu-z valids?
Certain people have been able to valid lets say exactly 3ht over what there prior max was right on the buitton ( exactly what you saw )...I did not attempt to as I figured it was a bug seeing as I have been using the THG tool all along.
Not only with CPUz Brian, but I've had 2 of my best 3DMark scores not successfully upload because of the FSB/HT fluctuation. When it checks your system between tests, if there is any change of parameters whatsoever it will invalidate your score and it won't submit, I'm sure you've probably had that happen over the years with other boards and setups.
Best regards,
Randi:D
I will use my invisable powers to fight crime.....
Hmm, I just assemble my rig, after ln2 session what was yesterday. Board start with full reset bios, and new cpu installed (955BE what was inside yesterday,lol:D). I set everything, and check swing. Swing is gone.
I set 200 ht speed, cpu-z show 200.7-200.8 -whatever I doing - what was "normal" with 0707 bios. Now, works well with 0801 too. Dunno what happened..:)
High swing might be under high frequencies only... I set eg only 208 in bios, Turbo V or ROG connect reads out 210... on air I have almost no swing either...
Think we better get data together what swing at what ht clock, total cpu speed, HT link,...cooling used.
Think I'm gonna give the CH IV one last spin on wednesday to see what happens with the Thuban... will prolly have to return the board to Asus on friday...
Yesterday, HT swing was me on air too for both cpu. (955BE, 1090T BE).
It seems, 0801 bios gave more stability for my 955BE.
4Ghz Prime, real ~ 1,421v (before ~1,435)
http://img265.imageshack.us/img265/3...21vcopy.th.png
I did the Bios clear using the button on the back of the board after swapping chips. I also had to do this after major OCing changes. If I clear bois and then make my changes, I have no HT Ref Swing. I am using currently 305HT Ref 4.1ghz 1.53v
Same thing, this BIOS is poop :down:
I was just messing with the offset voltage a while back, saving, booting again to check the values and came up with 1.23v for the NB/CPU.
Happy, booted into Windows to do some testing when i got a BSOD and went "WTF?". I booted into the BIOS again, checked voltages and NB/CPU was at a dangerous 1.38v :eek:
I give up, i'll just wait for another BIOS, this was happening with my Maximus 3 GENE and i returned her to get this... useless pile of electronics... Meh @ ASUS, you're starting to disappoint me MAJOR.
So your board overvolts ? I'm getting lost now ....
I adjusted the OFFSET of the CPU/NB and kept booting with the new settings into the BIOS to check when the voltage was set to 1.23v (the one i wanted). When i was finally reading 1.23v on the CPU/NB, booted again into windows until that BSOD. When i went into the BIOS again and checked voltages, it was reading 1.38v...
What matters here is that the motherboard changes CPU/NB voltage to its content and it appears to be completely random WHEN it does it :shrug:
well one thing I can say, is for the first time I have been able to get more out of my OCZ 1600BE Cas8 modules then on any other board. Though the timings are not the best, but this ram has never been able to do this on other boards. I'll try a 32M run to see how it is..
http://3800z24.info/Phenom/CrossHairIV/2006RAM-Pi1M.jpg
GPU's can go much higher but I was focused on CPU passage.
http://www.overclock.net/gallery/dat...0crosshair.PNG
Just noticed the 0801 bios has been removed from the Asus website,i wonder why.????:confused:
I hope they're working on some sort of fix, the motherboard is simply awesome WHEN it works. It's so annoying not knowing when it's stable or not :(
I guess that's the final option until ASUS does something about it. Connect a DMM to the measurement point and keep resetting until the voltage readout is ok :lol:
I also use 0801 and i don't seem to have any problems regarding cpu-nb voltage drops .
The only thing i see is the swaying core (bus) speed, and the fact that it overvolts a lot .
Is this only with certain hardware combinations maybe ?
It does hang often on a failed overclock , requiring me to shut off my PSU before trying to boot .
Also CORE implementation is poor as of now .
The only overvolting i see under load with LLC enabled. I haven't had any issues regarding CPU-NB voltage, i'm using the manual settings, not the offset.
Still waiting for a new bios though, this one seem to have some quirks.
I have to physically power down the PSU before the CPU-NB volts are similar to the settings in the bios. A restart just makes it go way lower and stay lower.
to time remain at 0707...some bugs, but great OC for me.
hmm, if you check out the asus FTP, last 'change' is yesterday, the 18th. for bios 0801, perhaps they changed something?
ftp://ftp.asus.com/pub/ASUS/mb/socke...-ASUS-0801.zip
Exact bios at first glance...
http://users.telenet.be/OAP/bios0801.jpg
I would call that a workaround Brian, not a problem fix...
weird that it got 'reuploaded' then yesterday.
Well, that sure are good news. Would be a shame to leave such a wonderful motherboard unattended :up:
0801 is back on site with a new description as well... There might be something different, i'll give it a whirl ASAP.
Good Day,
We have replicated the floating CPU-NB voltage problem finally and will have a BIOS fix shortly. Thanks to the members who assisted us. :clap:
Great!
the new 0801 (non beta) is the one which contains the fix ?
Bios description is very vague ..
No, it will take a couple of days to get the fix in the bios :)
I use LinX in most all of my testing.
http://www.xtremesystems.org/forums/...d.php?t=252114
0801 has been removed again,perhaps ready for the updated one,here's hoping.:)
Give them some time lads, I'm already glad they have replicated the bug... don't think the new bios will be named 0801 again
Thats great news,thankyou.:)
guess it didn't happen ;) Then again when have I ever publicly stated something that I had not managed to do. Things that make you go hmmm :p:
I can tell you that if it happened it did not require ln2 or DI on ram or retarded volts like some would have you think is necessary.
Need to provoke you a little to break out the screens. :)
Curious what it took if it didn't take crazy volts. Tell us more man!
What the, i've had issues with 'bios boot block ( or something' earlier, but now i cant seem to get out of it? :S perhaps something is frozen that shouldnt be frozen?
Was benching for a bit, rebooted, and saw the - 0.2V NB voltage. i made a safe of the bios earlier, so i selected that to see if i could fix it, and rebooted.
And then it said bios boot block crap, checking cdrom / flash drive for C4F.rom. so i put my usb stick in there, changed my 0801 bios to C4F.rom , it says succesfull, but with rebooting i get the same crap again?
it wont do any other bios. now im stuck @ -190 with a faulty bios :( , seriously, never had such a :down: motherboard before. im sure it's not dead or anything, but this is utter crap.