Printable View
I think I was confusing before. It didn't die immediately after flashing. It died a couple of days after I flashed to F9 and started stability testing with various speeds and voltages. One of the MOSFETs doesn't look good so I think that's what happened. I've never pushed any crazy voltages through this thing either.Quote:
Originally Posted by dekruyter
Oh man this really sucks my dq6 board is somehow locked to 445 fsb nomatter what volts i run even with multi at x6 wont go higher then 445 this sucks ..................... i was hoping to hit 3.6 or more from my e6400 week 28a cpu what should i do buy another board if so what one?
ziddey : Please show us full picture of DS3 Rev2.0 means DS3-E also I like your test result ;)
dekruyter : find Core voltage with your motherboard software I have GB and I use ET5
LordShadow : Nice! :p: if you find more please share it with us
eXceededgoku : please tell me water cooling how much decreased your idle and load temp
Richard Dower : Tanx for News about Rev2.0 I'm waiting for your test result I hope your problems become sovle
mackintire : QX6700 is too hot CPU if want OC try Water Cooling
0oDeuzo0 : you sure that you have memory headroom
You want full picture of board? It's really the same. I'm recharging batteries now will snap pictures when they're done. I'm guessing ds3-e like p5b-e, only not...
I'll tell you once I have the whole thing set up, since I already screwed it up once. I have another 15 feet of cable to go through to screw it up even furtherQuote:
Originally Posted by HamidFULL
ziddey and eXceededgoku : tanx and waiting ...
I went back to f8i DS3 from f7 S3 and these are my results. Overall, I can say I'm happy....:banana: http://img230.imageshack.us/img230/1...3700mhzzx0.jpg
I cannot find an FSB strap on this damn board. Pretty impressive though, running stable 8x400 with all default voltages except memory (+.2v) Booted at 366 and setfsb to 400... Just flashed to F7 instead of F9 (DS3 f9 -> S3 F7.) This is a WR capable E6400 with the right hardware! 3.2ghz under full load with default vcore cpu voltage dips below 1.25v and it stays stable...
**Update**
I think my problem was too much voltage. Just booted at 425mhz fsb with mem +.2, vsb normal, gmch +.1 and cpu vcore 1.375v... Haven't ever gotten this board to boot into windows over 405mhz fsb... Super pi 2m ran flawlessly...
you're lucky it's "B" 6400 and not an "A". i just received a 6400 "A" chip, threw it in my ds3 c2 that's been doing 450x8, and it wouldn't even boot at 400! the B chip had a pack date of 9/20/06, and this A chip was packed 10/31/06. guess A chips are still coming down the pipe so be careful!Quote:
Originally Posted by Hutch
Not all A chips are bad, guess you just weren't lucky enough. My L625A427 E6400 can do 450x8 just fine, haven't tested above that because of crappy memory that is holding me back.Quote:
Originally Posted by burn what?
Hot News for DS4 F8 BIOS
Changes :
1.Micron D9 Issue Finally Completely Resolved
Description : I have Micron D9 with F4-F5-F6-F7b-F7e-F7 I could reach 940MHz 4-4-4-8 2.0v and 1000MHz 5-5-5-12 2.0v I couldnt go over 1000 at all but now with F8 I reached 1000MHz 4-4-4-12 2.2v and 1100MHz 5-5-5-15 2.3v and 1200MHz 5-8-8-20 2.35v also I could reach 1250MHz but its not stable and need better cooling
2.Better Cold Boot
3.Added New Future for Memory Overclocking in BIOS "High Speed DRAM DLL Setting"
Description : "Better Memory Overclocking over 1000MHz" and you could choose "option1" and "option2" no more details
4.Much Better FSB overclocking I can hit 520MHz FSB (before I could do 500+1MHz)
5.Decreased Turn on-off While Overclocking
6."Advanced Chipset Future" Removed from BIOS
7.Better Vdroop and C1E Function
But is Vdroop a pure bios issue or hardware/mobo issue?
As i said my rev 1.0 was 1.360V under 100% Orthos load, with rev 2.0 is 1.344V....and things are not stable.
Has anyone noticed any USB problems with these new bios updates?
I am not happy with things right now, not sure if it's my PSU or the new 2.0 motheboard.
Nah i gskill 6400hz there is heaps of room for oc but i think there is a locked on my e6400 at 450fsbQuote:
Originally Posted by HamidFULL
I ll let you know what the temps end up to be after I install my new heatsink.
I know that I am uncomfortable with the load temp being over 74C on air.
My goal is to shoot for 3.0Ghz on air.
Later,
Mackintire
I just had another one of those magic no info reboots. Windows doesn t know that it happened, the event log is clean...under testing the machine runs orthos untill the cows come home.....errr.
I m going to keep quiet untill I get these parts swapped out...then I ll report back.
Hamid, as requested, pictures:
http://img20.imageshack.us/img20/756...e020gp8.th.jpg
http://img405.imageshack.us/img405/4...e021rz5.th.jpg
two pictures since i couldn't get a good quality close shot without strong lighting
Why does the DS3 have 4 fan pin headers...while the higher end DQ6 only has 3? :confused:Quote:
Originally Posted by ziddey
I can't seem to get this rev 2.0 to work right, 425x8...the OC holds but it's like the cold boot issue is still present with either rev 2.0 or the F8 bios.
On restart the PC will turn off and then power up, it'll hold the overclock ok...but it's bloody annoying :mad:
The Vdroop is definately worse, with 1.4V set in bios with rev 1.0 and running Orthos i get a CPU-Z shot of the Vcore as 1.360V under 100% load, idel it's 1.376V.
Rev 2.0 it's displaying 1.360V on idel while under 100% load it's 1.344V.... huh?
This cold boot thing is annoying, it's not as bad as it was with F7 whereby you'd do the whole shutdown/restart cycle thingy and your hard drives getting switched off and switched on.
With F8 it'll either shutdown once and power up and hold the overclock or it will stall for a few seconds. There also seems to be some USB problems with the 2.0 as well, not sure if it's hardware or software, but devices connected to some ports won't start.
Or maybe it's some resources problem or perhaps not enough USB power...but whatever it is i never had these issues with the rev 1.0 PCB, :nono:
Maybe because dq6 has heatpipe and ds3 has header for nb fan :p: haha then again I have no idea what fan headers the dq6 has and hell knowing how how my foot's always in my mouth, I can see there being a nb header on the dq6Quote:
Originally Posted by Richard Dower
Richard Dower : both of them but I dont understand on rev1.0 and vdroop 1.36v you was stable but now with rev2.0 and vdroop 1.344v you are not stable? check voltages with ET5 its more accurate than others
Richard I think Rev2.0 motherboards need Special better BIOS but you can Flash to DS4 F8 and try again
0oDeuzo0 : ok whats your mobo? GB oe Asus? if you have GB which BIOS you have tested? and one time set voltage and memory timings to auto and try again
ziddey : Tanx a lot guy it helped me a lot Tanx again
I download DS3 Rev2.0 pics very better build quality it have 6-phase power design? put heatsink on MOSFETs it can help to reach higher FSB
DS3 REV 2.0
Optimised for Quad cores.
whats the difference to the REV 1.0?
better voltage feed etc...?
THis 680i I have is stuck at 312 fsb!
I'm still trying to figure out what the issue is, it could be a pure bios problem or it might be that damn OCZ 850W PSU...i'm still consulting OCZ staff about that.
The rev 2.0 PCB for the DQ6 has alot of changes, technically...transistors, resistors, inductors, coils, MOSFETs etc.
The heatsinks are afixed better to the PCB using spring loaded screws, the SB has it's own crazycool backplate, the thermal pad used for the crazycool is better then rev 1.0...i want to be happy with this mobo, but right now i can't say that.
Perhaps a new bios will help things.
I believe I also had trouble holding 425 x 8 with the e6600 and DS3. I'm staying at 400 x 8 = 3.2 till I figure things out. With the 965 chipset getting the additional 9/8 x FSB factor, the chipset is overclocked, I believe, and this may be the cause of additional instability. I don't understand why this is documented so poorly, if its true. Overvolting the MCH and/or RAM may help, but I'm not sure of this.
For example, when you're trying for 425, it's actually 478 per the chipset; go figure; so I think ram and voltage settings have to be made accordingly;
Anyone want to comment on this? it would be most helpful.
M
I'm usually ok except for the rare cold boot issue with f9 with 400 x 9 = 3.6ghz in orthos blend. Superpi 1 mil = 14.43 sec. Ram/MCH/etc are overvolted a little, and pci-e is locked at 102. :cool:Quote:
Originally Posted by dekruyter
Yeh, but the cold boot issue is the whole point.
When we get a cold boot problem, I think this means either (1) our settings disagree with the pre-determined built-bios settings for that FSB, multiplier, etc., or (2) the settings are basically ok, but they need to be tweeked more to be stable (voltage, CAS, etc.)g.
M
Just spotted a F9 bios for the DQ6 here http://www.jzelectronic.de/jz2/index.php
I'll test it out now :)
Isn't it weird to get cold boot when everything is at default? GB had done a bad job on the 965 chipset. Afterall we're the 1st batch user... :slapass:Quote:
Originally Posted by dekruyter
Anyone try the F10 bios for DS3?
GA-965P-DS3
http://www.station-drivers.com/page/...a-965p-ds3.htm
F10
1. . Enhance FSB frequency flexibility
2. 2. Fix OC für Allendale CPUen
3. 3. Micron D9 1000 MHz 4-4-4-12 2.2V
4. 3. Micron D9 1100 MHz 5-5-5-15 2.3V
5. 3. Micron D9 1200 MHz 5-8-8-20 2.35V
6. 4. Fix Kaltstart
7. 5. Fix Vdrop in C1E Funktion
8. 6. Neues Features ´High Speed DRAM DLL Setting´
9. 7. Intel® HPET Support
10. 8. FSB 1333 MHz support (Auto ab Rev.3.3)
11. 9. JMicron ROM update
12. 10. BIOS Profilspeicherung möglich
13. 11. Q-Flash jetzt mit USB-Stick möglich
Holy crikey. Looks like somebody finally got off their ass. Sweet.Quote:
Originally Posted by markopoleo
7. 5. Fix Vdrop in C1E Funktion
This looks promising......
This looks too good to be true! Someone test! Go go go!
It's not on their web site; have at it if you want. I can wait a day to verify this release.
DQ6 F9 observation:
Settings selected in BIOS (8x438 9x389 etc) will always post and run to windows now, no cycle restarting after saving them ever. If I turn off PC, and press power on its getting cycle restart, so nothing new here.
But whats different from previous bioses: When I turn off manualy PSU then turn PSU on again and turn on PC by pressing power on button -> system posts and goes to windows with saved BIOS settings for first time every try! Previously I got cycle restarts or reset to defaults.
So can someone explain me why is system booting with BIOS setting everytime fine when i turn off PSU first, but not when I just press power up button. What does happen to BIOS when you turn your PSU off. Whats the difference between this and normal power on. Now I see something is wrong with board/BIOS or something when I can boot with my settings fine, but not without turning PSU first. :confused:
wow f8 9 10 i think gigabyte started taking speed
ok this is what i got after switching back to my DS3 (from a 680i) i updated to F9 533FSB, i tryed to go higher on the fsb but memory's dont let me go , i need ddr1000, whats the highest u guys go on the fsb?
Guys They steal my test result for New BIOS!! :mad: :mad: look at my post Yestreen!!
my later post :
I want to know which one of us is Station-Drivers AdminQuote:
Originally Posted by HamidFULL
jondl : yes I test it Last night and reported here!!
Ajfina : I can reach FSB 500+1 on F4-F7 and FSB 520 with new BIOS release means DS4 F8
Here piggy piggy.....
Thats a good gunipig.
Here's a carrot------> F9
:slapass:
F9 for DQ6 is well good, running my GeIL DDR800 4-4-4-12 at DDR1000 4-4-4-12
Will clock the CPU after wcing is fully installed. Ran the pump and setup over night and the pump leaked so I have sent it back since I can't stand it anymore...
I think i can do 540+ but memory is holding me
I m still debugging this thing, then I ll see how far I can take it on air cooling.
Using the Ninja with a 1600RPM Scythe fan I am seeing 74-76C full load running Orthos on all four cores.
Normally under real life useage I never see higher then 72C
Idle is 38C
I also know I have way too much Artic Silver applied.
If I get the chance between work and the wife I m going to switch over to my Noctura.
What do you guy suggest as a severe bench stress test?
I was thinking 2 instances Orthos running with 3Dmark 2006 running for 12 hours. I got the idea from [H]ocp
F9 sounds good so far. Also what settings would you suggest if I said I wanted to run EIST with the highest Clock being 3.0Ghz what divider should I be trying to use. Should I be trying to use the 300Mhz bus speed with a 1:1 or should I try some other combination?:hm:
BTW im using the DRAM DLL Setting at option 2
wow you're right hamid, I just compared ds3 rev1 vs rev2 and big differences all over the entire board in terms of electrical components. Also, to one who said ds3 has more fan headers than dq6, only rev2 ds3 :). rev1 ds3 only has 2 headers. Maybe this explains why only 2 rpm signals are consistently accurate with ds3 rev2.
F10 for our DS3 please!!!!! T_T
Same here. F9 = 485mhz // F10 = 495mhz for me. I'm still hitting a wall at 500mhz even with option 2 for DLL.Quote:
Originally Posted by rattsabre
Quote:
Originally Posted by ScythedBlade
Scroll up, its released.
F9 DS3/F7 S3 Didn't fix the fsb straps for the earlier boards I dont believe...
Is there an english version?
I just got a used ds3 rev1. Last owner had F8a on it. There's a noticable squeal from the motherboard way louder than on my rev2, and it makes it at all times and not just load. But here's the problem. With F8a, it was doing the cold boot thing on every reboot, even at stock 266fsb! Then, I flashed to F10 and it posted. I did the load optimized defaults and now all it does is loop cold boot up down up down. Haven't seen a post in a while now. What the...
edit: Should note I've tried cmos clear pins, pulling battery and shorting those, all to no avail.
Also, when the board was working, I noticed that this board sets vdimm 0.1v less than what's set in bios. In my rev2, when I do +0.4v, vcore2 reading in smartfan reads 2.30 (0.1v over). With this one, it reads 2.10 (0.1v under). Also, with the electrical components on the rev1, I know how to measure the vdimm, so I'll do that. But the thing is, my ram can boot at 667 or whatever stock is (if it's 266 with 4:5) at 1.8v absolutely no problem whatsoever. It can even post 800 with 1.8v although I've never tested stability there. So now I'm kind of in a stuck position again...
update: removing a stick of ram worked. weird since I've never had to do that before
Little drivers roundup, same file as i posted before but official from Intel direct, Intel Matrix Storage Manager 6.2.1.1002:
http://downloadmirror.intel.com/df-s...ata621_enu.exe
Oh yes, one more thing I found striking in F10 for DS3. There is an option in bios for ahci for ich8 sata. I didn't attempt to turn it on but I have a feeling it won't work since I don't think gigabyte would have a way around the limitations inherent to the ich8 non-r. Would be pretty interesting if it did work though..
Can anyone offer insight as to the Vdroop and if it's better on the DQ6 with the new bios?
Rich, Everest is reporting my CPU as having avoltage of 1.49v now as opposed to what it says in my signature (1.47v). So vdroop has dropped by around 0.02v which may not be accurate as that is one reading and I haven't played around with anything yet.
Exceed...you need 1.47V for 3.2GHz?...why is the voltage soo high?
I've left my PC on and am testing 400x8 with 1.375V set in bios...i'm away from my house and just let orthos run overnight.
I'm not having a good time over here. I have a pretty good feeling it's the board and not necessarily the bios. I've been demoted to a ds3 rev1 with c1 p965 for the time being. For what it's worth, I jotted down sspec and dates for the p965 chips:
C2 p965 from rev2:
L633A760 / SL90X
C1 p965 from rev1:
L623A518 / SL9NU
10 weeks difference between the two that I'm comparing.
As for how the c1 is fairing, I can do 400 1:1 stably it looks. 450 1:1 is proving to be a difficult one already. I've been fiddling with vmch, dimm dll, dropping multi to rule out cpu. The thing about it (and I'm not sure if it's the board or f10), recovery from a failed setting is really difficult. More often than not, it'll keep cycling or come on and stay on but not post. On more than one occasion so far, I've had to reset cmos and then yank a stick of ram.
Interesting. I haven't ever used ahci on ich8r before but can say that I tried turning it on in ich8 ds3 and it went to some sort of ahci screen where it noted intel and detected my drive. It's a shame I can't boot off it with my current setup though (window load sends it into a reboot)
Update: It could definitely be the board. I'll conclude when I put F7 later tonight. With my rev2 and f7, I could do 800 3-3-3-9, 1000 4-4-4-12 with reasonable voltages (<2.3v). However, with the rev1 c1 board I have right now, I haven't been able to prove stability yet, and quickly saw 3-3-3-9 at 800 was unstable even with 2.2v (previously tested stable at 2.0v)
Quote:
Originally Posted by ziddey
For some reason, the F9 bios fixed the having the clear cmos issue for me with a C1 S3 board... I flashed to F7 for S3 and half the time I'll have to clear the cmos...
Going to try F10 later tonight when my gf goes to sleep... It's well below freezing tonight and going to put the bench setup right next to the open window and turn off the heat... My idle temps are 50*c right now because my setup is right above the heater lol. Even the WCing radiator/tank combo is frying.
F10 bios for ds3 seems ok so far, no lock ups or cold boot issues yet. Bootup seems a little more snappy too. So far so good!
ziddey, your best bet on the older rev1, c1 board is the f5 bios. trust me, i've been through hell and (well, not sure if) back. f5 will give you stablity to test upper limits of cpu, but memory still has d9 issue on the bios so no go as you approach 1000. just go 1:1 and see what your cpu will do. i have an "A" chip in there and my max is 420x8. anything over boots but not stable. you won't have endless reboots as it recovers nicely. if it does start the loop and poop then as it first comes up and you hear the fan kick in press the reset button for 1 sec. and let go. should end the cycle and boot at fail safes. after you know your cpu limit, play with the f8i (not f8 final) which is pretty good, or maybe the new f10 with more reviews come outQuote:
Originally Posted by ziddey
is it in english?Quote:
Originally Posted by LagunaX
Hmm I've never tried F5 since my first ds3 (rev2 c2) came with f7. My used ds3 rev1 c1 came with f8a from last owner. I tried F10 and it was terrible. Then I went back to F7 and have had decent luck so far. I'd like to push ram further like I used to, but haven't gotten aroudn to seeing if it's possible. As for right now, I'm at 8x450=3600 1:1 so 900ddr2 4-4-4-12. So far it seems like it's just a characteristic of this board to loop and die until I fiddle with ram and try one stick and just mess around. I guess this is one of the d9 issues? I didn't run into that with my rev2 c2 for sure.Quote:
Originally Posted by burn what?
I managed to goof one time after I reset cmos and didn't set time in bios. Then once I got to windows, it timebombed on me and I'm reformatting now. Good grief.
Yes, it is.Quote:
Originally Posted by burn what?
nobody's really pinned down the cause of the loop and poop, but it happens alot on the rev1 c1's with many bios. you'll see almost none of that with f5, and like i say, just hit reset button as it comes up and stops the cycle should you get into it. i've seen it cycle usually when mem gets either 2 high in speed, i.e. over 1000, or timings to tight for the speed. a high fsb that cpu won't handle will just load fail safes. not the best bios in the world, but comparatively speaking it's way better than f6, 8, 9 for sure. can't speak to 7, but when i went back to it briefly before 5 i had more issues which is why i ended up on 5.Quote:
Originally Posted by ziddey
Hmm maybe I'll try f5 sometime, but for the most part, I'm way more satisfied with f7 than anything else. What are you running burn_what for timings? I assume you're at 8x450 1:1 also according to your sig?
I'm curious since I should be able to do 4-3-3-10 at 950ddr2 I think, but so far have only been able to achieve that with F7. At the rate gigabyte's been pumping stuff out, one could only hope for f11,12,13 rather soon :)
i'm stuck at 55515 with f5, tomorrow going to f8i to see if can push the mem some more. pretty much know the cpu limit is 450 stable. f8i and beyond have gotten better at the mem speed and timings, but also to date have gotten less and less stable. once again we hope for good tight timings AND stability all in 1 crazy package, can g-byte deliver? we shall see :cool:Quote:
Originally Posted by ziddey
Hmm weird. I ran orthos for an hour a-ok with 8x450 and 1.55v. Then I used the system for an hour, reinstalled windows, and everything was still a-ok. Then I ran into a brick wall all of a sudden, where it just kept crashing nonstop. Now I have the vcore raised to whatever the last 1.5xxx is since my experience with my last ds3 had a 1.6v that was extremely unstable. So far so good, going to let it orthos overnight again. Load coretemp can hit around 64-65 under apogee, but that's more than livable. I was cooking the cpu at >100'c the other night in a fried ds3 board. I tested by splashing water on the stock hsf and it boiled right off. That's burn-in for you ;)
I gotta say though, voltage control varies so sharply between boards. I guess it's not really fair of me to assess since I'm trying to compare rev1 vs rev2 (and electrical components look extremely varied for sure). But with my rev2, I'd set 1.375v for example, and see 1.32 idle, and 1.29-1.31 load. Now with this, I'm getting roughly what I set at idle, and droop is almost nonexistant at stock speed/vcore. Now I have it at 1.58 or 1.59 and it's around 1.57 idle and 1.52-1.54 load. Still well acceptable since the same setting with my rev2 would have landed me at 1.5-1.52v idle and 1.49v load. I was really hoping for a stable 7x500+ but I guess I'll "settle" for 8x450 ;)
Update: Looks like this ds3 was returned to newegg for a reason. Seems like the board will go unstable after running for some time. I can run at say 3.6 or even 3.2 for a good long time with zero sign of instability. Then after a few hours, it'll lock up hard. Then it won't even post until it's had time to chill. NB cooling provided by a thermalright so it's not that. Haven't seen a prime failure though. Just lockup. Anyone recognize this board :p I figure I'd ask since it came to me with f8a so I figure it might be one of you guys
Richard, I don't need this many voltages to remain stable I just can't be bothered to run orthos to ensure stability at lower voltages. AFAIK I need 1.52v to get 3.6Ghz to boot... And haven't changed it since lol :)
Yikes, has anyone run into a ds3 where the fsb drops on you?? I have c1e and eist disabled. Set to 8x400 in bios. Am noticing that system is really choppy right now and see that fsb got dropped to 369fsb
Is this a beta release? I don't see it anywhere on the gigabyte site.Quote:
Originally Posted by markopoleo
not a beta. It was on some website from them though, french i think. regardless i installed it and works perfectly.
I did too, wondering whats the diferents on the option 1 and option 2 for the memory ?Quote:
Originally Posted by markopoleo
I dunno but Option 2 for the memory allowed me to get to 1000mhz successfully
option 1 : optimization memory for running above 1000MHz below 1000 not difference between 1 and 2Quote:
Originally Posted by Ajfina
soo if is not diferent why is there? why they put it on, i thought opt 2 was to go over 1000mhz
Wow, this ds3 really seems to be on last legs. I orthos from last night at 2am until just now at 8x450=3600 no problem. I take setfsb and try to bump to 460. Locks up. Reboot, try to drop ram timings to 4-4-4-12. Windows locked up at logon screen. Fails to post, and needs to sit for 10 minutes off. Drop back to 5-5-5-15. Still running into issues with it being stable. Any sort of load in windows sends it into a crash. Voltages don't dip below working values. Wonder how long gigabyte's rma is
Haha, and you are going to rma the board because of that :clap:Quote:
Originally Posted by ziddey
Nono, well yes, but there's more. Even at stock speeds, I can use it for hours on end and be flawless, but then all of a sudden, it'd go berserk on me and lock up and fail to post for a while. Nothing has been changed except for motherboard (ds3 rev2 c2 changed into a ds3 rev1 c1). It was perfectly stable with the first board. I'm thinking if it's not consistently stable at stock, then something's up eh? And it also does the silly turnoff-on on startup and reboot even at 266fsb. Kind of weird
edit: I might need to retest the psu, even though I already did a month ago and it checked out fine. Really strange since the board works miraculously at 8x450 albeit 5-5-5 for hours on end but then eventually goes into the :banana::banana::banana::banana:ter and won't come back to life for a while. For testing purposes, I've focused a lot of airflow on the board itself, but it didn't help. So I'm not sure what the time is doing to help it, but it doesn't seem to be temperature
Update: aaagh. I've been letting it sit for a while and it came back at stock speeds. It froze at logon screen at stock. Then it went in and hung at prime. Third time it's priming now at stock. Really weird.
Well I guess a lot of the C1 boards don't clock very well. No matter what I can't get anything stable over 425mhz fsb. Although my memory limitations should limit me to below 500mhz fsb, I've reached 455mhz FSB 910mhz ram (running 4 sticks too) on my P5W DH. The board is VERY picky about ram voltages and timings. Would be nice if I could RMA it for a C2 board, but oh well, it's not worth it. Better off waiting til Q3 when bearlake comes out and I have the money!
Hutch, what have you tried running for timings? I've found with my c1 board that a lot of times it refuses to post until I remove a stick (though I'm only using 2 sticks). Also, even though I know my ram is good for 500 4-4-4, I'm only able to run 5-5-5 at say 450 even. So I dropped down voltage since there's no sense feeding the 2.3v for higher speed. My board is being very tempermental with higher fsb, but after manipulating some more, I've got it temporarily stable at 450fsb 1:1 5-5-5 again. Don't want to bother pushing anymore since I don't think it could possibly end well. Also, I'm back to two sticks. Hope this helps.
Edit: One more thing that might help. Not sure if you have access to a dmm (looks like you would since vmch mod in progress), but you could try measuring vdimm and see what it actually is. On my c1 board, it's actually undervolted by about 0.1v. Or, based on the two boards I've used, vcore2 in speedfan is pretty accurate vdimm (might be 0.02v too low though compared to actual).
Yea it won't boot into windows if I use more than 2.0v on the ram, Have tried 4 sticks, 3 sticks, 2 sticks and even 1 stick. The ram isn't high clocking ram (Elipda chips, 4-4-4-12 @ 667 is spd settings.) I've gotten it to run 4-4-3-4 880mhz @ 2.25v on the P5W DH but over 900mhz required 5-5-4-15 @ 2.25v. I'll check out vr-zone as they probably have the vdimm measuring point..
Ahh, elpida. I hear some of that doesn't like higher volts? Then again 2.2v isn't really considered high though. I think it was more referring to 2.5+.
As for measuring point, it's really simple on the rev1 boards. If you look to the left of the dimms (assuming you tilt your head 90' ccw such that you're properly reading the silkscreen on the motherboard), you'll see an inductor (round and upright with wireloop around). Stick negative to chassis or whatever ground you prefer, and red to the end of the inductor (I used the side facing the dimm). I got readings about 0.02v higher than what vcore2 reports, and 0.1v less than what I set.
When I had my rev2, I didn't look to figure out how to do vdimm checkpoint (really different components and no conventional looking inductor). But the vcore2 value was consistently about 0.1v higher than what I set, so I just assumed it to be more or less true. Much better board than my rev1, but I recall the higher vdimms being instable for whatever reason. Not sure if I hadn't done enough fiddling at the time or if it's the case, but in the end, I've found that I never needed to go higher than 2.3v (+0.4v for that board) to achieve results I was looking for.
sorry u r having all those problems , i do have the same board u have C1 and god i love this DS3 is running at 500fsb 24/7 no problem VERY stable, had a 680I b4 and sold it to go back to my DS3, i was doing a bit better on the memory department with the 580i but only 50 mhz faster than my ds3, im runnng 1000mhz now, any way , im getting tomorrow a bad axe 2 cause i always wanted to have one of those , lets see if i can beat my ds3 , so far ive done 533fsb maybe i can do more with the bad axe 2Quote:
Originally Posted by Hutch
f10 bios was terrible for me. after about 8 different trys with various settings it showed no higher memory speeds and no better timings. the option 1 or 2 for the memory dll thing did nothing. neither option booted at 1000 speed no matter how loose the timings were. anyone else with micron d9 having any luck? wait till official release i guess, don't waste your time AGAIN with this bios!!!!!!!!!! this was on my rev. 1, C2, B2 rig that's been doing 450x8 rock solid.
Ajfina, that's very impressive. Is that with "normal" vmch or what? how about vfsb?
is your corsair micron d9? i can't even sniff those fsb speeds cause of my mem.Quote:
Originally Posted by Ajfina
all voltage to max here ,except for cpu vcore and memory is +4Quote:
Originally Posted by ziddey
mines are 64ooc4 , i think they are micron or is it only the 6400c4d the ones d9?Quote:
Originally Posted by burn what?
Measuring vdimm when set to +.2 = 2.02v actual voltage... gmch set to +.1 actual voltage reading is 1.337v (WOW 1337 MAN!) Lol
Is there a problem with running an SATAII drive on the external sata ports (purple ones) and having SATA ports running in IDE mode in bios? It's weird that the overclocks dont fail until it starts to load windows and it gives me a c:/windows/system/ cannot find a certain dll message...
Wow Hutch, I got that cannot find error yesterday too with the rev1 c1 (never saw it with rev2). Scared the :banana::banana::banana::banana: out of me since I'm used to high pci corrupting hdd's in ide day. Never narrowed that down to something, although I was thinking possibly vfsb or vpcie.
As for running off the purple jmicron connectors, I don't really see anything wrong with that. However, I'm not sure if it'd be slower when accessing optical media, since I'm not sure how the jmicron operates with respect to the ide controller and those two raid ports.
Yea the first few times it happened to me it scared the **** outta me... But it just about always happens when I try to boot over 430mhz FSB and more than +.2 on the vdimm...
Something interesting was just posted in the biostar thread that might possibly hold true for us too. One guy was setting cpu temp warning of 65'c and even though readings didn't show him coming close to it, it was causing bad behavior when overclocking. Once he removed it, it was good to go. That's kind of interesting because I never enabled that option (albeit 70'c) on the ds3 until I got my rev1 board. That's the one and only thing I did different. Perhaps it's worth a shot. Not sure if it'd apply to you though.Quote:
Originally Posted by Hutch
Things here are weird, it's freaky man! :eek:
So i did that orthos run, 400x8=3.2GHz with 1.375V in bios..this was the result (attahced image), F8 bios used for that.
So i then flashed to F9, this time i tried flashing using a USB flash drive...and it worked! :banana:
The flashing process was even faster, y'all know how slow it is to read from a Floppy drive, using USB flash was super fast!...and the flash was sucessful, this is a really good addition to the bios and QFlash.
My USB problems i think are related to my RangeMax USB dongle, i think it's fooked...it's like touch and go with it, sometimes it works other time it won't get detected by Windows or lockup or won't make an internet connection.
F9 is dated January 11th 2007, but the Award bios date still reads "2006" when you enter bios. It seems like my hardware is going kaput...i've now asked OCZ for a second RMA for the 850W Gamextreme...the rails are very bad.
Under 100 Orthos load i get 12.61V on the 12V rails and 4.89V on the 5V, on idle it's 12.65V and 4.88V...thats surely is out of ATX spec :confused:
It's a bloody noisy PSU, sensitive ears be advised, strange frequencies, inductor/coil/electrical noise from within the PSU...none of which was present on the 700W model :mad:
I'm still in diagnostic mode right now.... :fact:
Coretemp showing 3600 eh? haha
CoreTemp also shows my 425x8 as being 478.13x8...Orthos is also wrong and assumes a 9x multi, thus 3600MHz.
Another screenie for y'all. My bog standard setting (for now) 425x8 with 1.4Vcore set in bios. As you can see Vdroop is no better with F9, it still reads 1.344V whereas revion 1.0 PCB was 1.360V.
(G)MCH and FSB set to normal, DDR2 voltage set to 2.0V, PCI-E and others set to normal. My Orthos run is still going...but i'm upto this stable. I am gonna try for 487x7 once i fell things are stable, then try some multi options and memory at 1000MHz.
Can i just say that the new Arctic Silver method of AS5 application works perfect, done the routine four times now and each time the IHS is 100% covered, a thin line down the center of the IHS.
Got my new case/artic cooler freezer pro 7 today, running stable 1.86ghz @3.2ghz stock voltage on everything, only thing i had to change was FSB and memory at 1:1 :D
Temps are only ..50c under load! vs 60c at 2.8ghz before in old case, stock HSF. :D
Orthos locked up after 5 hours, so it appears i need more Vcore. My USB problems continue...it's also effecting my Logitech USB keyboard/mouse...could it be a USB problem related to the Intel INF Software?
You know how there is a box to turn USB devices off to save power etc.
I'm starting to think it's either hardware related to the mobo or some driver issue.
http://www.ijib.com/~ziddey/rig.html :) finished 24hr.
Next time I'll try to see how far I can tune down voltage. I'm currently running at what my other e6400 needs. Maybe this ES can do it with less
What's your mouse/ usb issue? I used to have to goto device manager and disable power save for the mouse. Otherwise, every minute of inactivity will cause it to lag for a sec while it starts up again. Haven't seen that happen lately though, and never with the gigabyte board.
I *think* it's bios related, i don't remember any issues with F7..basically my attached USB devices stop working, no data being moved and many times my Neagear Rangemax USB 2.0 dongle has a yellow warning symbol in Device Manager saying "error code 10 - this device cannot start", the only way to get it working is to unplug the device from the USB post and it starts working again.
It's effecting my wirless USB dongle more then my Logitech MX3100 USB keyboard/mouse.
They are all USB 2.0, has anyone else experienced USB issues with these recent bios releases?