Having issues with Gigabyte P965-ds3 rev 3.3 mobo.

Grimlock

n00b
Joined
Aug 8, 2008
Messages
16
I'm hoping someone can help me out...I just finished a system build using the P965-ds3 rev 3.3 board and I'm having issues. 1st, the hardware, besides the board:

E6300 BX stepping used with my old board (AsRock 775 Dual-VSTA)
Crucial Ballistix 2x1GB matched pair DDR2-800 4-4-4-12 2.2v
Zalman 9700 cooler
Maxtor 320GB SataII with 16mb cache-using the JMicron Sata ports for NCQ.
520watt OCZ Modstream PSU with 26A on the +12v rail
NEC 3500A IDE burner used for Windows install, later replaced with Lite-On 20X Sata burner plugged into the JMicron Sata port #12.
PNY 7900GS plain-vanilla card
Creative X-Fi XtremeGamer PCI card
Antec Super Lanboy case
Win XP Pro with SP3
Antec Spot-Cool directed at the northbridge
Silverstone 4-port USB 2.0 3.5 bay header

Now, before I even installed the board I replaced the thermal paste for the north- & southbridges using Arctic Silver 5, and before I installed XP SP3 I flashed to bios F13 & set up the Bios using the "baseline" settings Billparish outlined in his overclocking guide on this forum. The XP install went fine, and I rebooted after installing the chipset drivers & the Marvell driver, and that's when things went flaky. I went into Bios to check & make sure my settings were still there and I noted some of them went back into "auto", specifically the CPU Host Clock Control, PCI Express Frequency, and DRAM Timing Selectable. I reset them to the "baseline" settings, saved them & re-booted. The rig booted very briefly, then bliped & then booted again. I went back into bios and those settings I changed were back at "auto" again. The board did keep my memory timings-it just kept setting the DRAM Timing to "auto" with them. My CPU was set to the right speeds, but still at "auto" as far as control was concerned. I haven't been able to get the board to keep the "baseline" settings manually, but they still appear to be there otherwise.

I decided to continue on with the Windows install, only to run into a later issue where Device Manager advised of an unknown PCI device, even though I didn't have any PCI cards besides my X-Fi, and it's drivers were already installed. XP keeps prompting me to install drivers for this "unknown PCI device", but I can't figure out what it's even talking about. I only noticed this after I changed out my IDE burner for the Sata burner and deactivated my IDE channels & the Floppy drive in Bios, so I'm not sure if that's related. And, I noted that the rig was taking longer than normal in unzipping/raring files, so I checked Task Manager and found that it was showing only one core, even though I'm using an E6300. I go back into Bios and switched CPU Hyper-Threading back to "enabled" and Task Manager showed 2 cores. Also, after I got the PC back from my buddy's place, I couldn't connect it to the internet anymore, even though I had no issues previously. I couldn't even pull up the command screen for my router, although it was working fine (my Xbox360 was still able to connect, and another PC on the router had no issues), and that was after I uninstalled Comodo firewall & reverted back to the Windows Firewall.

After all that, I decided to at least run Memtest for a day, and it didn't detect any errors after 24 straight hours, and it showed the board kept the timings for my Ballistix, so I don't think they're the cause of anything at this rate. I'm going to go ahead and reinstall XP SP3 using the Sata burner this time, and hopefully that'll take care of the no internet & WTF PCI thing in Device Manager. What I'm concerned with at this point is why I can't keep even maunally-set "baseline" settings in the MIT section. The CPU is almost 2 years old, but it's never had more than a minor overclock (the AsRock wouldn't even handle letting me put the thing up to E6400 speeds-sad), but the thing with Task Manager showing only one core with CPU Hyper-Threading disabled has me thinking there might be something wrong with it. The CPU temps seemed normal-I don't think either core got above 35c in CoreTemp. The CPU temps in bios were reported wrong, though-it kept saying the temp was like 15-17c at most, which would've been below room temperature! System temp in Bios was 44c on average, IIRC. The P965 was brand new in the box, but it was clearanced to $55. I looked it over, and there's no scorch marks or bad solder on it. I tested my PSU, and it checked fine, and it's been a reliable unit. The only other culprit I can think of besides the CPU would be my 7900GS-I noted in my repeated attempts to get the Bios to keep the manual settings that sometimes only the PCI Express Frequency would revert to "auto", but the CPU & DRAM Timing would revert to "auto" after I went out of Bios. Also, I think there might be something with the PCI-E slot being 2.0, but IIRC the 7900GS is a 1.1 card (I know 2.0 is supposed to be backwards-compatible, but "supposed" covers a lot of ground). I don't have any spare parts to swap out with, so I'd have to RMA anything, and the video card is out-of-warranty. Anyone have any suggestions?
 
Forgot one thing-the core voltage for the CPU is at 1.35v & the memory is at 2.2v.
 
The 7900GS is a PCI-E 1.1 card so PCI-E 2.0 doesn't apply here.

For the LAN problem, did you reinstall the LAN drivess?

Have the exact same unknown PC device with my DS3 motherboard as well. But I made it so it never asks me to install the device.
 
'PCI Device' does not necessarily mean it's installed in one of the board's PCI slots.

Have you installed all drivers on the motherboard disk?

edit: I'd leave PCIe frequency at auto. I've had setting it to 100 cause instability before.
 
Danny Bui-Yeah, first thing I tried. Didn't work. Tried the driver on the CD, didn't work either.

AVT-Tried that, too. No dice. I started out with the newest drivers on Gigabyte's site. About to try re-installing XP now.
 
First leave "hyperthreading" disabled. Your e6300 does not have hyperthreading, its a true dual core cpu.

For now set your memory timings to something like 5-5-5-15 just for now till you can get a overclock of around 2.8GHz. Set your memory divider to "2" so your memory will be at a 1:1 ratio with your FSB.

Once you there stable then you can tighten your timings and or go for a high overclock.
 
Well, reinstalled XP and I still have that WTF PCI thing in Device Manager. Guess I'll just live with it for now. And I couldn't get the on-board LAN port to work for crap-installed & reinstalled drivers, plugged it directly to my DSL modem-nothing worked. It just flat-out refused to cooperate. I put in a spare NIC that I had lying around & disabled the Marvell LAN (and uninstalled its driver) and Windows Update popped right up-annoying, but frankly not the first time I've seen something like this. At least my bios changes are holding-I'm keeping the PCI-Express Frequency to "auto" and so far nothing else has flipped out-my CPU and DRAM are still on "manual" even after a dozen reboots. I've been pondering putting a 4850 in whenever I can scrape up the cash & see what that'll do. But right now I'm not gonna change another thing until I get XP all patched up and backed up.
 
Well, the board just blipped and I went into Bios to check, and sure enough the CPU & DRAM are back on "auto". I tried putting just the DRAM on "manual", but it just blipped and put it back into "auto" again. I dunno what to think at this point.
 
Was this a "used" board or bought "new" ?

Did you install the onboard audio driver ? I could see where with the sound card you considered it not needed (and it is not technically) but I am wondering if windows is finding the device even though you disabled it in the bios, (you did disable on-board audio in the bios right ? )

First thing I would uninstall the sound card drivers drivers and then take out the sound card. Reboot, activate the onboard sound and load the drivers for it, take special note that there is a microsoft UUA driver that MUST be installed first then the sound driver package. They might have finally combined them in one driver package, read the driver description carefully from the web site. Do that and see if the "strange" device goes away. If so then you can disable it in the bios and go back to your sound card but not yet, see below) .

For the other stuff I am guessing (and thats all it is, a guess) its the hibh voltage memory it does not like. Clear the bios with the jumper on for at least 1 full minute with the power off or unplugged. Load "failsafe defaults" from the bios, reboot and go right back into the bios and load "optimized defaults" and save and reboot. Go back into the bios and leave everthing alone except the memory. When I say leave everything alone I am mainly talking about in the MIT overclocking menu, in the other menus set the stuff that is normally set based on your hardware. In the MIT menu set the timings to manual 5 5 5 15 and set the voltage to +.4 (you might have to boot with just one stick until you get the memory voltage set). Make sure everytime you go in the memory multiplier is set to 2.0. On automatic reboots/resets it like to change that, lock it down/check it every time to 2.0.

Do that and let us know. The idea here is to:
Get rid of the unknown device.
Reset all the boards timings and voltages (there are a bunch automaticlly set you cannot see) back to factory except the main memory timing which we set loose and the needed memory voltage.

Once the board is stable at stock you can start increasing the fsb slowly and let the board adjust itself as you move up in OCing the cpu. Leave the sound card out for now. The onbaord is not all that bad and we need to eliminate things that might be causing you grief until we get things under control. Uinstall its drivers from windows. If you have any other USB drives/devices other than a mouse and or keyboard, dump them too for now.

It appears you got a "twitchy" one and will have to "sneak up" on overclocking it. The worst thing you can do is make big jumps as the board will reset and you might have to start all over. The bad place we dont want to go is that there are reports of some boards that will just not OC no matter what and need to be sent back. But its way to early to say that yet. So lets get it stable at stock and the flaky device driver taken care of and then go from there. Use the F11 key to save the stock profile.

Go slow will be the key to OCing this one I think.

I will try to watch thread.
 
Board was bought new-in-box; the cables, i/o shield & discs were untouched when I opened it, and the 775 socket cover was on it. If it was used before & then returned to the store, they did an awesome job of repackaging it. I had already disabled the onboard sound prior to installing Windows in bios, but I haven't installed my sound card drivers this time yet. The only drivers I have installed currently are the chipset drivers from Gigabyte's site and the one for the NIC-I went ahead and uninstalled the Marvell driver & disabled the on-board Lan, since it kept refusing to work with my network setup. I'll go ahead and clear the bios & yank out the sound card, but I just came up with something else I'd like as well-flash the bios to an earlier version to see if some of the flakiness could be tied to the F13 version. I'm going to download the F12 bios & flash the board to it, since that version came out over a year prior to F13.
 
Well, the re-flash to F12 went well enough when I was finally able to do it-QBios wouldn't find the file on my thumbstick so I hooked up a USB Floppy drive & it took forever to read the file, but it flashed it once it verified. Did all the Bios stuff ya suggested, BillParrish, and I installed the Azelia drivers & the Nvdia drivers for my video card, but that WTF PCI is still there. I don't have anything else plugged into the rig besides my mouse, keyboard & monitor, and the monitor has no do-dads on it. Device Manager is showing the IDE Channels & the Floppy Drive, as well as my Sata drives and all the USB ports, as well as my NIC, so I'm dumb-founded as to what this mystery PCI thing is. I'm starting to wonder if it would be worth the effort to try to RMA the board-I can't exchange it, as the store I bought it from only had a 1-week policy, and that was up more than a month ago, and it was the last one they had anyway. I think for the momemt I'll just set up some basic apps in Windows like EasyTune and CoreTemp and see how well I can get the board to overclock before I go the RMA route. That'll have to wait until tommorrow, though. Anyone have any other thoughts?
 
Im wondering about that 2.2 on the ram seems high to me. The board defaults at 1.8 but i set mine at 2.1 on all my boards. Got Four. I know when I set something too extreme on mine they default back to base settings. Running 1.4 on cpu, 2.1 on ram. 5-5-5-15, 3.2 ghz on a e6400, same volts and timings on the other three all run great.
 
Yea I agree with mx500torid that setting the ram voltage at 2.2v is pushing the envelope on what ddr2 can handle. The max I would go is 2.1v

BillParrish has one of the Best overclocking guides available on the net for overlcocking Gigabyte boards with an Intel chipset. Make sure you have not over looked something on the first couple of posts in Bills DS3 thread.

Double checking the ram divider can't be emphasized enough. Make sure its at "2" as Bill and mx500torid have already pointed out. If the ram divider is not set right while overclocking it can mess up your ram speeds and they will be way above your ram specs if your not careful. Using CPU-Z while in windows will tell you if you have your ram speeds set with in spec.

With your e6300, 2.8GHz, should be very doable (7X400) with little or no voltage increase, any higher than that and you will probably have to start upping the voltage to your cpu. Also above 7X400 you will have to overlcock your ram since you posted you have ddr2 800.

I can't imagine what the mystery device is in "device manger"? I have never seen that problem in my DS3. So that could be a indication of a motherboard problem if BillParrish's suggestions don't work.

The Gigabyte DS3 is a solid board, but as with any model motherboard it is possible to get a bad one. If you can't get rid of the mystery pci device and you can rma the board that might be the best way to go if all else fails.
 
Well, things seem to be steady for the moment. I'm posting this from the rig now. I went ahead & disabled the floppy & IDE connectors, and nothing has blipped on the board in over a dozen re-boots. I've gone ahead and installed CrapCleaner, AVG, EasyTune, Diskeeper9Lite, and a couple of other apps, but nothing serious. I noticed that the CPU temp in Bios is more or less correct now-between 28 & 30c. Maybe F13 bios has a few issues in it. The Ram divider's still at "2", and the timings are still 5-5-5-18 for now in Bios, and CPU-Z is showing the same thing in XP. Haven't done any XP tweaks yet, not even TweakUI or TuneXP. Defragged & installed 3dMark06 & PCmark05. Got PCmark05 to run, which it wouldn't do right when I first installed XP on this thing last week, and got a score of 5499. It wouldn't run properly the 2nd time tonight, though-it just hangs on the hard drive test. Maybe it doesn't like the way my Sata's set up. I then rebooted and ran 3dMark twice and got scores of 4066 & 4036 respectively, which was lower than the 1st XP install on this board, but I had a bunch of tweaks on that install before I flushed it, so I'm taking the results with some salt. The WTF PCI still in Device Manager, but I don't think it's affecting anything, and XP hasn't prompted me to install a driver for it, so I'm going to stop worrying about it for now. I'm going to go ahead and knock the Ram voltage down to 2.1v and run MemTest for a day to see what happens, and if it passes then I'll start tweaking and trying to do a mild to moderate overclock-I wasn't going to try for anything greater than 2.8ghz on this processor in the 1st place. I'll update as I go along.
 
The WTF PCI still in Device Manager, but I don't think it's affecting anything

I wonder, havent used that model of Nvidia card, if there is another driver for HDMI or a secondary card function not in the basic driver. I got a little bell going off in my head but I am damned if I can remember exactly what it is for .... might be confused with ATI but might be worth a check, I cant stand a ? in device manager. /shrug.
 
I had one of these boards before my current Abit IP-35...I loved that board too, but if memory serves me correctly you had the option of running two SATA drives off a separate controller on the board itself. There is an independant driver that has to be loaded for it. That's probably the driver you're missing in the Device Manager. I cannot remember who made the chip for it. I had the same thing happen with my board initially.
 
AFAIK, the 7900gs doesn't have any special functionalities or such. There is an s-video out on it, but TV output is run by the Nvdia driver. I bounced my situation by my brother, who's a bit more experienced at this stuff than I am, and he suggested my WTF PCI is a PCI bridge chip. I just did a google search & there's a Marvell PCI bridge chip that's made to work with one of their gigabit ethernet chips, but I can't check if this chip is on the board, as I'm currently at work, but here's the link I found about it. I'm not sure what impact this has, as the WTF PCI was already in Device Manager when I was trying to get the Marvell Gigabit Lan to work. Also, I turned off Memtest just before going to work, and it said no errors, but the memory is running at DDR2-533 speeds at 5-5-5-15; the 15 bothers me, as I remember the Bios having set it at 18, but I didn't have time to check it before running out the door. I'll eyeball it when I get back. I'm also going to try and raise the FSB up a bit & see what happens.
 
Overclocked the FSB to 276Mhz in Bios. Set FSB & (G) MCH OverVolt Control to +.1 each. Bios says the memory is at 5-5-5-15-I obviously forgot this earlier this morning. Just ran PCMark05 & got a score of 5548. CPU-z shows the expected settings: 1932Mhz for the CPU, and DRam/FSB frequency match. CPU voltage is 1.28v-I'm barely tickling this thing. Temp never went above 35c on either core. I think I'll try taking it up to 300fsb and see what happens.
 
Well, took it up to 300fsb and so far no hiccups. Cpu-z is showing 1.28v core voltage, but EasyTune is showing 1.31v. PCMark05 gave a score of 5789, and 3DMark06 gave me a 4152 score. Ran 2 instances of Orthos for 5 minutes and neither core got above 42c. Think I'll take the FSB up another 20 at a time until I hit 400fsb or a snafu.
 
Currently at 370fsb (2.59ghz). Cpu-z still showing 1.28v core, & EasyTune showing 1.31v. PCMark score is now 6664 & 3DMark is up to 4272. Core temps are still okay, but that's because I have my case's back fan cranked up and the 9700 cooler at 2250rpm, and I have a box fan pointed at the case. It's getting late, so I'm going to try for 400fsb tomorrow after work. I'll let a couple instances of Orthos run for a while to check stability in the meantime.
 
Went to 400fsb earlier. Still the same core voltages in CPU-Z & EasyTune. PCMark score is now 7031 & 3DMark is at 4304. Ran 2 instances of Orthos using blend mode for 5 minutes-no errors reported. Coretemp is showing the chips are idling between 37-39c. Think I'll run Orthos just stressing the CPU's for an hour or so before I consider this a successful outcome. I'd run Memtest overnight, but there's bad weather forecast for my locale for the next day or so-no point risking things right now if this mobo is "flaky".
 
Ran Memtest for 4+ hours tonight-no errors. Ran 2 instances of Orthos just stressing the cores for 45 minutes-no errors. I think it'll be alright to proceed with tweaking XP and installing the rest of my stuff and my sound card. Think the best way to work the machine from here out is to run it at normal FSB for when I just wanna web-surf & such, and bring it up to 400 when I'm doing intensive work, like with Photoshop & the like. That way the power bill won't end up being murderous. :D Well, thanks for the help, folks. Think I'll be okay from here on out.
 
I get vdroop on all mine set em at 1.4 and cpuz shows1.35. i set the north bridge at .2. looks like you are on the right track. Did you set the volts down to 2.1 on ram? I had better luck overclocking thru bios instead of Easytune.
 
Yeah, I set my Dram voltage to 2.1v. I'm debating whether or not to try and set the memory timings back to 4-4-4-12 & 2.2v, or just stick with tweaking XP for performance boosts. Currently leaning towards just sticking with the XP tweaks.
 
Now that you got it figured out you can play with timings. Those timings were just a good baseline.
 
No, my Dram voltage is still at 2.1v. I'm debating if I should try putting the voltage back to 2.2v along with timings of 4-4-4-12. I'll probably make up my mind this weekend.
 
Back
Top