i am sure.Quote:
Originally Posted by Ruhnie
Printable View
i am sure.Quote:
Originally Posted by Ruhnie
I noticed it when I was doing OC. Does it boot @ 2.1 after CMOS reset now too?! That's great news then as I don't think much RAM would fry at the increase. I do know it would open doors for some of the higher VDIMM-liking RAM.
Hmm... We have the exact same RAM, CPU, and motherboard. Are the mch and Ram voltages the only thing you changed?Quote:
Originally Posted by The_Hardstylez
What timings are you using?
Going to try it.
Only change mch + 0,1V and set the timings to 5-5-5-10. My corsair sticks have elpida on them. Whitch 5-5-5- is the sweetspot.Quote:
Originally Posted by norain
Just checked the website; the F5 official BIOS is now available.
http://www.gigabyte.com.tw/Support/M...me=GA-965P-DS3
40mm fan + 2 screws:Quote:
Originally Posted by Stalk3r
http://www.crowdcontrolusa.com/overc...nside_core.jpg
Im having the same exact problems here too, I use two of these in raid-0 and after the first format they showed fine, then after a few windowes exits and speed increases it seems that now my raid dont show up..Quote:
Originally Posted by thunderstruck!
Im running WD diagnostic on them now (tech told me to try this) I really hope the drive isnt bad, and its just a bios error..
Plz keep me posted if you find a fix, ill do the same for you.
does that little fan spin fast enough to add a noticeable amount of noise?Quote:
Originally Posted by chrisf6969
Quote:
Originally Posted by Philosophy
I'm using a single Seagate SATA2 drive, running ACHI on Gigabyte SATA port and I get weird errors on bootup at times (very rare, like once a week) -- the bios detects the drive, but it would give me "Disk boot failure". A soft-reset (Ctrl+Alt+Del) will always get it working again. :confused:
It's really weird, since there's no problem at all once it runs. Looking at the HDD LED, it doesn't seem that the BIOS even bothered to try loading the MBR on my HDD when it fails. It only looks for my floppy (doesn't matter if I set floppy as 3rd boot)! Even my DVD-Rom drive didn't even light up (2nd boot device)... this has got to be a BIOS bug.
Anyone having anymore success than me with team 667 and the ds3?
Currently ive primed my way into 464X7 4-4-3-8
Any more than that and i have random freezes.
Im on the f3 bios BTW..
Before I had a 40mm fan on my NB, the heatsink was @ 55C under load (probed with a digital multimeter with thermal probe). Your finger would burn in 3 seconds. That's on a non-oc'ed system (everything stock @ 266FSB). But of course, ambient temp over here is nearly 30C.Quote:
Originally Posted by jaberocs
With the fan, it's at 47C under load. The heatsink still feels quite hot, even though I can now stick my finger on it forever (still hurts a little). I really wonder what sort of temperatures those guys at over 400FSB are getting.
The heatsink temp being so bad already, I just can't imagine how much hotter the core is running. The pdf file of the 965 (G)MCH says there's no readable thermal sensor on it. There's a thermal trip sensor which we could program, but there's no way we could read the actual temperature value.
The heatsink feels hotter than my Gigabyte G-Power's base... And I've got a P-XE-955 running at 66C under load... :confused:
Flash to the F5 Final, that will fix all the problems with 667Mhz memories. I had a lot of errors on prime and memtest and also I got BSODS on Windows, but when I flashed to the F5 Final Bios all the problems disapeared.Quote:
Originally Posted by Philosophy
So how does one disable the onboard sound on the DS3? Is there some Bios option I am missing or something?
based on how easy i got to my sig specs, 400 x 8 1:1, i'm thinking about 4ghz. but has anyone ever got to 4 ghz on air? i don't want to get into water as i'm a noob, but i'm still on all stock volts and haven't pushed this thing at all. i know i'd need a better nb cooler than the stock. want a jing ting but don't know where to buy. just wondering if i should even consider 4ghz on air. any thoughts???
Disable AzaleaQuote:
Originally Posted by raleigh29
Good to hear. My Orthos crashed after an hour the other day. I have no idea what did it as it's ran 14+ hours and I've played BF2142 and FEAR on it. It ran again today for 5+ hours...we'll see.Quote:
Originally Posted by ClockCatcher
A lot of people including me are having the same problem connecting an IDE drive to the DS3. It only works when windows is installed on the drive, but try adding it as a secondary drive, and it becomes "unreadable" under windows. Guess you'll have to wait until you switch to a different mobo.Quote:
Originally Posted by crspyjohn
Thanks, if I find a solution, I'll post here and PM you. :up:Quote:
Originally Posted by Philosophy
Here's something that many have not pointed out:
Some configurations have an FSB hole from 3xx to 400. So everyone ... jump straight to 401 FSB!!! You should so sticky this statement.
I'm having trouble using DVD or CD burners (tried NU DDW-082 & Teac CD-W58E). Nero tanks with, "DMA error" every time after lead-in. Reads from the drives fine. Haven't tried forcing PIO mode and would rather not.
Using F5 BIOS, Giga's RAID0 with 2 Raptor's and the latest GSATA drivers available from their site (dated 01-Aug-06). BIOS set to "RAID/IDE".
oooohh...an official F5 BIOS was posted yesterday. I wonder if that'll cure my OC wall. Anyone try the above theory of that if you skip over 400FSB to 401 FSB it may be stable? I never tried 401 (just 400) so I wonder if that statement as merit to it. Or has anyone tried the F5 and gotten past their wall?
Ah yes...soon I'm just gonna go for a Corsair Cool Water system and water cool everything...maybe even the NB and then continue my OC'ing experiments. This thing is noisey enough without another fan (NB) in there.
I'm up to 450 FSB (7x multi) with my DS3. But I'm kind of worried about the effect this will have on my graphics card. I left the PCI setting to Normal and the Robust graphics setting to normal. Should I change these?
Im on he F5 and im still @ my wall which is 464X7 4-4-3-9
Try for 465 and itll crash on prime after about 5-10 mins :(
Ima keep trying different things though, I dont think im beaten at all..
This is def a mobo limitation for sure..
Cpu @ 1.375 ram @ 2.2
Something is broken here but I don`t know what :p: