Forward: official GIGA 965P-S3/DS3/DS4/DQ6 beta BIOS

Just do what my friend did.He called Tech Support and asked them that same question.Since they are separate from the sales department and mostly deal with your type of board.They understand the problems.They can tell you where to short out the board so it doesn't look like you did anything to it.Then will send an email to the sales department to activate a RMA for you.Just tell them your Name,address,phone number and email address.I just about fell off my stool when my friend got a new board.But don't do anything on your own and call for RMA.When you send it back they test the boards.They might find out what you did.

Don't turn it off during a flash and send it back.They'll just reflash it and send back the same board.

Quote:

---

Originally Posted by Warpcore

Just do what my friend did.He called Tech Support and asked them that same question.Since they are separate from the sales department and mostly deal with your type of board.They understand the problems.They can tell you where to short out the board so it doesn't look like you did anything to it.Then will send an email to the sales department to activate a RMA for you.Just tell them your Name,address,phone number and email address.I just about fell off my stool when my friend got a new board.But don't do anything on your own and call for RMA.When you send it back they test the boards.They might find out what you did.

Don't turn it off during a flash and send it back.They'll just reflash it and send back the same board.

---

No they won't. I had two boards that I sent back to newegg that worked fine until the BIOS corrupted for some reason. Both full refunds. And they sent me e-mails detailing their tests.

EDIT: I missed that your sending it back to gigabyte. I doubt they will tell you how to fool them into giving you a new revision.

i tried to give f10 1 more honest try. after all combos of option 1 or 2 for the high speed ram thing with only 55515 timings at 400fsb, i couldn't even get a 1M superpi run to finish. i began to worry my ram was bad! flashed back to f8i and all is well. how anyone is solid on f10 is mystery to me!!!!!

F10 w/ the DS3 rev. 1 has been fine for me; but I've never really gone past 400 24/7.

my sweet spot on several boards has been 500x7, but i couldn't even get stable at 400. no cold boot probs yet at 500x7 f8i, 24 hours w/ many cold boots. tomorrow will test upper limits to see if any better/higher than rev1.

does increased vdimm = tighter timings, higher fsb speed, or both?? i've never pushed past 2.2V, which is what the patriot sticks are rated at. wondering if i should go 2.4V, but i'm afraid to fry the mem. what is the gain?

Quote:

---

Originally Posted by PanteraGSTK

EDIT: I missed that your sending it back to gigabyte. I doubt they will tell you how to fool them into giving you a new revision.

---

I just got my DS3 back from Gigabyte RMA and they "fixed" my old board and sent it back to me. It actually POSTs now, but now it's also terribly unstable. I'm so happy I waited a month for them to replace a part and not test to see if the whole board was fubared from the fried part. There's more to computing than just POSTing. :( I haven't given up yet on getting to work, but this is going to be my last Gigabyte board. I have NEVER had the same exact part returned to me after an RMA, especially not a part as complex as a motherboard.

My LAN on my DS3 rev2 is not working, everything in bios that is lan related is working and enabled, what's going on?

my OS is ubntu

Quote:

---

Originally Posted by SaII

My LAN on my DS3 rev2 is not working, everything in bios that is lan related is working and enabled, what's going on?

my OS is ubntu

---

Rev2 uses a newer LAN chip that may not be supported yet. IIRC Marvel offers linux drivers on their homepage (I never tried them).
I had a lot of trouble with the Marvel LAN chips of my ASUS P5B-D and P5W-DH boards and Suse10.2 (using only the shipped/and updated) 2.6.18 kernel.

all these rev 2's seem to have a wall of 500fsb. the cpu's i have to go with aren't stellar, but set multi at 6 so don't believe it's cpu limit problem. i put active cooling on stock nb sink, cool to touch while running, just can't break 500. combo of f8i and f10, nothing get past 500. no cold boot issues which is nice. anyone on air getting over 500 with rev 2? undervolts from what is set in bios, but while running an app like prime95, seems to be no droop at all. either board is better about droop or it's the new cpuz that doesn't show droop when starting an app.

I was able to run my rev2 ds3 up at 520, but after that it wasn't too stable. Think max post I got was around 525.

Quote:

---

Originally Posted by mibo

Rev2 uses a newer LAN chip that may not be supported yet. IIRC Marvel offers linux drivers on their homepage (I never tried them).
I had a lot of trouble with the Marvel LAN chips of my ASUS P5B-D and P5W-DH boards and Suse10.2 (using only the shipped/and updated) 2.6.18 kernel.

---

thank you!

Quote:

---

Originally Posted by HamidFULL

today I go to Gigabyte RMA Center in my land and I saw that all newer boards in store are Rev3.3

I know here gigabyte have poor technical office and easily change board if it cant boot

I have Gigabyte 965P-DS4 Rev1.0 and I want Destroy it (not physical) to replace it with Rev3.3 :D

How I can to Destroy My Gigabyte 965P-DS4 Rev1.0 as that
it become turn-on but cant show boot screen (monitor stay off after turn-on)
:toast:

---

Why go to all that trouble, just buy the new one and sell yours on Ebay.

Just imagine this if everyone destroyed theirs and had new replacements next year when the price has doubled you would know why :stick:

damn. I thought my old rev2 ds3 died. It got real finicky with ram that's known to work at spd settings and 1.8v at 667 and even post at 800. It always still gave ram beeps when it wasn't installed, but never posted with sticks in. I figured ram shouldn't be that shot, and just didn't want to put any more effort into the ds3. Then I got my p5b in today, and same deal. Looks like ram died. God damn it buffalo firestix d9gmh. :( But probably, more of a god damn it ds3. I remember someone else (Hutch?) mentioned ds3 eating ram.

Quote:

---

Originally Posted by ziddey

damn. I thought my old rev2 ds3 died. It got real finicky with ram that's known to work at spd settings and 1.8v at 667 and even post at 800. It always still gave ram beeps when it wasn't installed, but never posted with sticks in. I figured ram shouldn't be that shot, and just didn't want to put any more effort into the ds3. Then I got my p5b in today, and same deal. Looks like ram died. God damn it buffalo firestix d9gmh. :( But probably, more of a god damn it ds3. I remember someone else (Hutch?) mentioned ds3 eating ram.

---

Yea I actually found a solution to the issue. If you take out any sticks, you must do the following for the board to post when you put them back in:

1. Power down, remove power cord from psu, switch psu off, wait 10 seconds before you do anything (watch the network card light, it stays on for around 10 seconds.)

2. Remove all of the ram.

3. Pull the battery.

4. put the thing on the clear cmos pins, keep it there.

5. Put ram + ram your adding back in.

6. Put battery back in.

7. Remove the clear cmos blue thingy from the pins.

8. Plug power cord back in, switch psu on and fire it up.

Just about every time you add ram (even if it had previously been in the board) you have to do this in order for the board to post.

I had a similar approach to that and had to do it over 10 times for no apparent reason. Then finally it just wasn't responding to it at all. Also, I tried the same ram in a p5b and no dice. Just got some kvr667 to try and it started right up. Going to rma the firestix since they would have posted 667 1.8v no problem.

Finally after 2 weeks of fighting with my retarded computer, I've replaced my p5b-dlx wifi *dead* for a DS4 Rev 1.1, it came with the BIOS F8 (latest ?), i would like to know if possible, is the rev 1.1 bad compared with the 2.0 and 3.3, i dont care about onboard sound, got a x-fi fatl1ty, i just want to oc my little e6300 Stepping 6 - Rev B2.

The very first test i did was to try achieve 400FSB (2.80Ghz), no problems, stock 1.30V, i did not touch anything other voltage, seems stable after 4;30hrs of ORTHOS, should i keep trying to get a higher FSB ? I am on Air Cooling (9500LED with AS5), but i am worried about the north / southbridge temps, as the picture shows, on full the cpu - > 40degress || System - > 33

http://img296.imageshack.us/img296/8...2800fc2.th.jpg

I believe i can keep trying to achieve 3000Mhz but duunno if i will end burning the north.

Quote:

---

Originally Posted by leopr

Finally after 2 weeks of fighting with my retarded computer, I've replaced my p5b-dlx wifi *dead* for a DS4 Rev 1.1, it came with the BIOS F8 (latest ?), i would like to know if possible, is the rev 1.1 bad compared with the 2.0 and 3.3, i dont care about onboard sound, got a x-fi fatl1ty, i just want to oc my little e6300 Stepping 6 - Rev B2.

The very first test i did was to try achieve 400FSB (2.80Ghz), no problems, stock 1.30V, i did not touch anything other voltage, seems stable after 4;30hrs of ORTHOS, should i keep trying to get a higher FSB ? I am on Air Cooling (9500LED with AS5), but i am worried about the north / southbridge temps, as the picture shows, on full the cpu - > 40degress || System - > 33

http://img296.imageshack.us/img296/8...2800fc2.th.jpg

I believe i can keep trying to achieve 3000Mhz but duunno if i will end burning the north.

---

I have a case fan blowing room temp air onto the NB and it isn't even warm to the touch at 516mhz fsb. as long as you put some kind of fan on it you won't have to worry, unless your ambient temps are like 35*c or something.

Has Bingo13 any updates re: bios?
I've been quiet while some new hardware is en route, i have to do a slight rebuild...running Vista right now.

After replacing the TT Extreme Spirit II for the stock NB heatsink with a 60mm 26CFM fan blowing on it I finally got my DS3 rev.1 stable enough to start doing some serious overcklocking attempts.
Using F9 bios I got a max stable FSB of 444MHz (8 hours Orthos blend stable). Anything above that craps out within 30mins.
This is with +0.2V on FSB and GMCH.
HIghest memspeed I could get was 975MHz (6x390 4:5) (Have Corsair Dominators rated at 1066) so D9 bug was still present.
Highest stable CPU speed so far 3442MHz (9x382) at 1.475V. Was hoping for 3.6GHz with this E6600 but I've got a Vapo LS just waiting for a proper socket kit and then I'll hopefully get it a bit higher than 3.4! ;)

After testing and finding the limits with F9 I flashed to F10 and now I can't get the FSB higher than 420... Top CPU is still 3442MHz. Haven't tried top mem speed yet...

Which bios would you recommend for high FSB speeds? F8i or F7?

Also which is the highest CPU voltage you'd recommend with good air cooling (Scythe Infinity)?

Personally, I had the best luck with F7 although most people swear by F8. Have you tried keeping vmch on auto? or on +0.3v? A lot of people report the p965 requiring 1.55v to get general stability and reduced cold boot bug.

Just doing some final tests for mem speed with F10 now before I flash to F8i and see what happens with that...
No change in top mem speed... 975 with both Option 1 and 2... :/

F7 for my DS3 is stable but doesn't let me boost vdimm voltages even 0.1v. I can boot in OS at normal vdimm, but with added voltage to the RAM it barely posts with F7. Now using F8i: e6600 @ 426x7 = 2982MHz 1.3375v, DDR2-1065 +.4v, 5-5-5-15 timings, MCH +.1v, other options at auto or "normal". I'm astonished with the NB stability i'm getting, regarding the low cpu multiplier i'm using. Any known straps for the DS3 NB? Cuz I tested mine from 300FSB to 410FSB and the memoryspeed gain was pretty linear, without any noticable NB latency drops. F8i lets me reboot at least without having to cut the power...

Man, my RMAd board is screwed I think. Have you guys ever overclocked your DS3, had it lock up in dual-Prime, and then not POST afterwards? It's driving me nuts. I've tried every X-Fi compatible BIOS available in my collection and I can't get my board to behave when overclocked. It always locks up. The system always refuses to POST afterwards. I've never seen anything like this crap.

I had that problem a lot. Seemed to be when the board was eating my ram. Usually, removing a stick of ram and trying again helps. If not, try moving them around. Maybe reset cmos too. That was the test pattern for me, and it usually worked. However, after a while, it stopped working, and my d9's were shot, and won't even post in any other motherboard

Looks like my Tunique Tower was causing a short somewhere. I just went back to my Scythe Mine and I'm up and running again. Here's another thread about the problem:

http://forums.pcper.com/showthread.php?t=435128