Some people don't turn off their computers. LOL. That's all I can think of.Quote:
Originally Posted by frostman
Printable View
Some people don't turn off their computers. LOL. That's all I can think of.Quote:
Originally Posted by frostman
No!Quote:
Originally Posted by frostman
Tired of this crap. Going back to F4 AGAIN!
This BIOS is total scrap, when I first flashed it I was unable to boot at all, first thing I thought that mobo is dead or something like that, there were strange beeps and after that nothing :mad: Reseted BIOS, no luck, after leaving it unpluged from power for some time it booted again, sometimes it can boot @ 480FSB, somtimes not, now I set all at stock, i think I will go back to F8i till there will bo new BIOS.Quote:
Originally Posted by frostman
With F8i there was problem - cold boot - my CPU can do with this board 500 x 7 @ 1.56 - 1.58v, but I hate it when its not posible to boot with such high FSB :nono: :slapass:
When Giga Byte will release BIOS without cold boot? :(
Not to say others aren't having issue, obviously they are, Mine has been fine with F8j and F8i at 490 as long as I don't use auto for voltage control. If I use auto then it's random whether it will boot without resetting my bios settings on me. I am manual now and it's fine with the cpu voltage I set, all the rest are auto except vdimm which is +0.3v so that it meets it's own 2.1v spec.
Readings I mentioned (1.325/1.163V) were taken from 'Computer/Overclock'. You are right, the 'Sensor' reading is in line with the CPU-z, also with Speedfan Vcore reading. These with value of 1.25V would correspond with the BIOS setting of 1.275V. The only question that remains now is whether with a BIOS setting 'Core Voltage Control' to manual the CPU/mobo does adjust Vcore according to the actual core clock. From the 'Sensor' reading it doesn't seem so. Also it seems that Vcore values from the 'Computer/Overclock' reading are just defaults from BIOS set for the clock multiplier, 8 - 1.325V, 6 - 1.163V. Do you have some suggestion on how to control the core voltage according to the CPU clock? It doesn't seem to be possible from the BIOS...Quote:
Originally Posted by GAM
Same here :( Cold boot still an issue.Quote:
Originally Posted by aldamon
My 24h/24h OC is still stable though.
I didnt even realize there was a 'cold boot' issue till last night when the PC was off for a bit and it reset to default after 12 hours of prime. Same thing happened today. ARGH - flashed to F8J today but I guess I may have to move back to the P5B-E if this doesnt get fixed.
wow...I'm staying with the f8i for now...
bock bock BAWWWKK :chicken:
yea still wont hold OC on a cold (few hours off) boot. Reverts.
Hey Bingo, wassup with the cold boot issue?
So the problem i noted with F8b/c beta for the DQ6 is called "cold boot"?...Gigabyte called it a watch clock timeout problem, it was only introduced in the new betas.
F7 works fine, so it's effecting all boards then...there's alot of work to be done on these bios.
Has F8j updated the JMicron bios ROM to 1.06.59?
Hate to be repeating myself but DS4 F7e has introduced problems with connected with usb devices when overclocking, which seemed to be fixed at F7b, which was not as stable though. Can't Gigabyte get it right ? They seem to fix one thing and another goes wrong. Plz don't tell me next BIOS will introduce again the X-Fi problem!!!! (which was fixed for me btw in both F7b and F7e. I had problems with X-Fi reinstalling with all previous BIOSes)
X-Fi problem is/was introduced again with F7 final for the DQ6, same goes for the F8 betas i have tried.
You also only have a gig of RAM and I doubt it's D9. That could also be contributing to your limited success.Quote:
Originally Posted by MadMikeSS
With F8j, my system does not POST until I hit reset. Then it beeps 4 times, reboots itself, and then POSTs with my overclock disabled. F8i always beeped and reset the overclock on its own. I can recreate this after the system is turned off for 5 minute or 12 hours. Any kind of "cold" boot (if you can call it that after 5 minutes) does it. Seems like the issue is getting worse to me. I'm back on F4. It doesn't find my Raptor on a cold boot, but at least my overclock is not reset every time. I just have to hit reset and I'm on my way. Annoying, but no big deal.Quote:
Originally Posted by blurp
DQ6 2.0 page updated, i'll assume same for the other 2.0 boards...gonna read the 2.0 manual:
http://www.giga-byte.com.tw/Products...me=GA-965P-DQ6
p.s. - let's hit 200,000 views on this thread!!
the f8i for the ds 3 i cant see it coming out for a while i may just get a new mobo instead.
Well my DS3 was dead. I am sending it back on RMA this afternoon. I've never done an RMA before. I wonder if they will just replace the bios chip or the whole board.
Anyway....in the mean time I have dusted off my C19-A SLI board and configured the nvidia raid 0. Funny, it could run circles around that jmicron controller, but the board doesn't OC worth a darn.
How long do GB RMA's take anyway?
Anyone here have there PC run at +350 FSB and have there memory At 3.0x??
On a DQ6..
Ok, well I've had enough of this board. I enjoyed the lack of Asus vdroop but the cold boot issue is enough to drive a sane man insane.
Overclocks great but seems like this board and the p5b isnt even of the same generation, like rev 1 vs a rev 2. The issues it has seem to be something GB just will never get a proper handle on, detachment from the community hurts. I dont understand why we dont have people from Asus and GB on these forums to get immediate feedback. We have folks from the memory companies here. I think the detachment from their own customers is what is really hurting some of these companies. Nvidia as well with the 8800 has a drive mess on their hands right now. The latest drivers cause a ton of issues but since there is no public way of filing feedback to them it's nearly impossible to get the issue recognized - ati has a nice submission program and issues that users find are resolved. I guess if I was ever brought in to consult my best suggestion would be to penetrate the user base and find out what the problems are from the users, not the in house beta testers that cannot seem to find / fix or identify a problem.
Thanks, but...Quote:
Originally Posted by markopoleo
1. This was the first thing I tried and I had no luck even with PCI Latecny Tool. I've tested it with PCI Latency set to 32,64,128,248. No difference at all.
2. All options are on default.
3. I don't think this could help :)
I've tried all driver releases from Creative...
Codecs were the some for all systems but only my DS4 with XFi installed had this issue.
btw. I tried full system reinstall(including disk format) same time ago and everything was running fine until i added XFi drivers into the system. :mad:
Well, I'm going to wait until the official F7 BIOS arrives and then I'm going to buy either ASUS P5B Deluxe or ASUS with nVidia 680i, but definitely NOT Gigabyte.
I used to have it. Corsair Dominator 9136 and DQ6 F7 bios. FSB 360 MHz / DDR2 1080 stable. As I got rid of the Dominators, I run my system at 8x400 DDR1000.Quote:
Originally Posted by Lee_Kay
I've been reading this thread from the start but this is my first time posting.
I just got my DS3 up and running with an E6600 L628A, 2GB Corsair 8500 C5 Dominator mem, X1950XTX, 2 x 74GB Raptors (not RAID yet) on the Jmicron and using a Scythe Infinity on the CPU and a Thermaltake Extreme Spirit II on the NB along with a Hiper Type-R 580W PSU.
I'm still on the F4 bios as I wanted to find out what it could do there until I move up to F8i or F8j.
Right now I'm trying to find my highest stable FSB bt I'm not having much luck with it... Around 340MHz it keeps crashing or rebooting...
I've set CPU multi to x7 so it's not running much more than default.
Mem ratio is 1:1 with 5, 5, 5, 18 and 2.1V. Other voltages are set to +0.1V.
Questions:
1. Which PLL to choose in Clockgen?
Right now I'm only using Easytune for FSB clocking and it's a bit of a pain compared to clockgen.
2. Could someone who's hitting 400MHz FSB or more post their M.I.B. bios settings because I feel a bit like I'm fumbling in the dark with some of them...
Why don't you just use a non-beta bios and wait till a final, stable bios is out to upgrade?Quote:
Originally Posted by dnottis
Also, I'd like to take this oppurtunity to request people to stay on topic. It seems a lot of random questions that have nothing to do with BIOS are asked in this thread, and it's annoying. I check this thread a couple times a day and it's just kind of annoying. They'd be better fit in the DS3 FAQ or in their own thread.
Sorry, I'm not sure I follow you exactly... however, typically, there is always some difference between the vCore reported in Windows (by Easy Tune, CPU-z, Everest, etc) and what has been set manually in BIOS. Whether the vCore reported in Windows is accurate or not is debatable (typically believed to be inaccurate), however it does serve as a fairly consistent guide if you always consult the same program (Everest for instance). The difference between Windows and BIOS essentially comes down to vDroop under different loads, i.e., I have 1.475v set in BIOS and 1.42v reported by Everest under load. This value fluctuates a little. When you change the BIOS setting, you should expect the same change reflected in your Windows monitoring tool.Quote:
Originally Posted by cassper1
Why in hell are you bashing Dnotis for using a beta BIOS ???? This thread is about beta BIOS and he is sharing his results :nono: :stick: :slapass:Quote:
Originally Posted by feek