faulty board maybe Rich...? I know it sucks to RMA it when it was brought abroad, but it looks like you might have to :O
Printable View
faulty board maybe Rich...? I know it sucks to RMA it when it was brought abroad, but it looks like you might have to :O
my DS4 with F8:
+ 400mhz fbs limit (about 430mhz can boot, 470mhz can be set in windows)
+ setfbs causing speedhack in games fixed
- lot more sensitive to cold boot than F6.
Can any of you tell us what the memory dividers actually do in real life at 266, 333, 400, 433, 466 Mhz FSB
As I understand it some programs do not report the correct results, and in earlier BIOS versions the divider did not function completely normally.
I m asking for this to be placed in one post so that maybe everyone with a Gigabyte board can find it.
Please post your results and the BIOS version, motherboard, PCB version, Rev version C1, C2, and the memory that you are using to get those results.
Thank you in advance.
i have ds4 it work very well with f2 bios and specteck ram 533 bus but after i am apdate bios to f8 or f7 when turn on my pc for first time it turn off for 2 sec and it turn on automatic you tell me to clear CMOS i did and flash f8 bios on backup bios but i still have problem what can i do or is it normal ? thanks
Depending on what your settings are.... Im assuming you are trying to run your memory at 533. What is your FSB running at? And with what memory divider.
The 2 second off and back on thing has been normal since F3 I think.
If your CMOS says that you need to clear. I would say that your BIOS settings are probably off.
533 memory should probably run 133 FSB with the memory running X 4
133 X 4 = 533
You may also need to use Cntr-F1 to get into he advanced memory settings to manually set your voltage and memory CAS Tcas and Rct settings.
I don't think it's normal but I have the same issue with my DS4. I didn't manage to work it out since August 2006. I didn't send my board to RMA because system is rock stable and I have no time to wait two or three weeks to get it back. But it's really annoying. I'm not overlocker and don't OC my system but because of this I'm frequent reader of this thread ;-).Quote:
Originally Posted by amr
Mack,
Gigabyte S3, Bios F8 (Same bios as DS3 F10) C1 Chipset, Rev 1. Using 2:3 Divider max ram speed 920mhz, using 4:5 divider max ram speed 930mhz, using 1:1 divider max ram speed: 890mhz. Only program that reports the wrong ram speed is setfsb, it will only show the 1:1 ram speed.
Ram used: PQI turbo PC5400 4-4-4-12 (value elipda chips)
Max Cas 3: 733mhz
Max Cas 4: 870mhz
Max Cas 5: 930mhz
All results using 2.1v, anymore voltage causes bsod's.
Those results also using single channel with my best stick (have 3 sticks that max around 840mhz, one stick that maxed at 930mhz.
Mine seems to be working better witht he F8 than the F7.Quote:
Originally Posted by t800
Currently at 450FSB C1 rev mobo and an e6300.
Havent had the time to play with it more, seems good so far to me...
NVIDIA nTune v5.05.22.00 Released :
http://www.xtremesystems.org/forums/...d.php?t=130686
we can't use that...??
Seems theres quite a few fixes in BIOS revision F9 for the DQ6:
1. Enhance FSB frequency flexibility
2. Fix OC für Allendale CPUen
3. Micron D9 1000 MHz 4-4-4-12 2.2V
4. Micron D9 1100 MHz 5-5-5-15 2.3V
5. Micron D9 1200 MHz 5-8-8-20 2.35V
6. Fix Kaltstart
7. Fix Vdrop in C1E Funktion
8. Neues Features ´High Speed DRAM DLL Setting´
9. Intel® HPET Support
10. FSB 1333 MHz support (Auto ab Rev.3.3)
11. JMicron ROM update
12. BIOS Profilspeicherung möglich
13. Q-Flash jetzt mit USB-Stick möglich
http://www.station-drivers.com/page/...a-965p-dq6.htm
Only #1 is official
anyone has downloaded F8 for DS4? what u think of the new feature
Anyone know's why the CD Player line does'nt work on DQ6 F8&F9??
I have to use the CD Player line for my TV card.... :(
Because one of your optical drives has been selected to use "digital audio extraction" and the analogue audio input for that channel then perhaps get disabled? :confused:Quote:
Originally Posted by Tush
This list created by me!!Quote:
1. Enhance FSB frequency flexibility
2. Fix OC für Allendale CPUen
3. Micron D9 1000 MHz 4-4-4-12 2.2V
4. Micron D9 1100 MHz 5-5-5-15 2.3V
5. Micron D9 1200 MHz 5-8-8-20 2.35V
6. Fix Kaltstart
7. Fix Vdrop in C1E Funktion
8. Neues Features ´High Speed DRAM DLL Setting´
9. Intel® HPET Support
10. FSB 1333 MHz support (Auto ab Rev.3.3)
11. JMicron ROM update
12. BIOS Profilspeicherung möglich
13. Q-Flash jetzt mit USB-Stick möglich
look page 160-167Quote:
kingcarlos
anyone has downloaded F8 for DS4? what u think of the new feature
I don't think that this is the problem....Quote:
Originally Posted by LvR
I just found out that with the new bios I have 2nd Output, WTF is this? :stick:
http://grm.m.walla.co.il/briefcase/0...15043674/J.JPG
Did you uninstall the old drivers?
YAY! it works again!Quote:
Originally Posted by Richard Dower
Thank you! :D
I've never fiddled with robust graphics before so I gave that a shot. I've always had pcie set to 110.
However, when robust is to turbo, when I boot windows, stock gpu speeds are changed from 450/500 to 496/551 (110%). Is that done simply via pcie manipulation?? If so, how come when I normally have pcie set to 110 it doesn't raise it? Or is ds3 bios somehow able to manipulate core and mem clock of graphics card?
I'm not sure how it's doing it, but I wish OFF was an option. AUTO makes me nervous.Quote:
Originally Posted by ziddey
^lol, exactly the same way i feel
I think I have found the main reason for our cold boot problem. I hooked up a dmm to the read point for vmch.
I started out with plans this afternoon of being vdroop, vmch, and vdimm. Vdroop so I could get a more reasonable vcore at idle. Vdimm since mine was 0.1v lower than what was set. Plus, I figured if I made starting vdimm at 2.1v, it may eliminate some boot issues. Results show vdimm boost didn't help boot issues though, but it's nice to have +0.2v have it at 2.3v.
Vmch. Here's the interesting guy. It's been brought up many times before, and people have done actual reads based on different fsbs and all settings normal, +0.1, +0.2, and +0.3. I should have done this as a baseline for comparison but I didn't think to at the time. I ran out of qtips for the time being, but I need to erase the pencil for vmch anyway.
But here's what I found. I recall setting it so that base vmch was 1.35v. Then I proceeded to try and do 450fsb. I tried +0.2v setting as my preference, since I read I think a vrzone article saying they stopped seeing cold boot issues after keeping vmch at 1.55+. However, this +0.2v resulted in a setting somewhere around 1.7v. What the... Maybe the graphite heated up and become less resistive. I'll check that in a bit. I try normal and +0.3v and both send me to 1.8v vmch. Yikes. +0.1 sets me very close to my original target of 1.55 though so I figured I'd just try to keep it there.
One thing I noticed was that each time the system went for a reboot, I saw a first vmch setting of 1.45-1.49v regardless of what vmch is set to. Then it pulls it up to what the setting was. However, I haven't been able to boot 450fsb ever since I did the mod. Got it to post maybe once or twice, with insane vmch iirc. But even then it didn't boot successfully into windows.
I'll try to get rid of the graphite, and see if I can determine any characteristics of it at stock.
Perhaps if there was a way to clamp vmch at 1.55 - 1.6v, everything would be peachy? The problem is that I'm not sure how to approach this. Since with however much graphite I put on, it looks like the effective baseline vmch is being set to 1.45-1.49, which rarely do I see applied. The problem is that "normal" goes to the +0.3v equiv at the fsb's we want to be focusing on. And the problem with that comes in that there is no +0.0. The best compromise would be +0.1v. If things do work out properly, this would mean it'd always turn on at 1.55v, and once it gets ready to post it pulls it up to 1.65v. With adequate cooling, 1.65 should be ok. However, this still has the problems of normal/+0.3 sending vmch to nearly 1.9v (seems the +0.3v setting is slightly more than a 0.3v jump). On recovery posts, I believe it always forces max vmch, so there should be frequent shocks for us tweakers.
I'd imagine that clamping vmch would require soldering, beyond the pencilmods I did.
edit: Oh yeah, I nuked my windows again. Agh. I shorted out the read point for vmch with one of the legs, powering off the system. On boot up again, bios settings are retained, except time gets reset. I didn't realize this, and proceeded to try and boot windows. I was greeted with "trial period over" again. Grrr, back to safemode to backup and format once I get it up I guess
update: bleh didn't help with instability. guess the board was returned for a reason. but woohoo, got my rev2 working again :)
All i know is....1.4000V in bios is not gonna cut the mustard with rev 2.0 DQ6, i now need 1.41250V
richard u need to stop buying newer versions of teh same product lol, you have such bad luck!