Gigabyte P35-DS3P Weird Beep Issues

[patsun123]

When i turn the computer on, before the post beep, it will emit a low, longer beep, more like a duck call than anything else. Than the computer will post, and run just fine. Does anyone know why this is? It also does this during reboot and wake from sleep.



specs in case you need to know

GA-P35-DS3P
XFX 7900GS
4x1gb g.skill ram
Intel Core2Quad6600
320gb SATAhd, 250gb SATAhd
liteon dvdrw

 

[SerpentRoyal]

Could be a fan sensor or temperature out of range. Go into BIOS and disable rpm and temperature monitoring.

 

[Billbo]

Originally posted by: patsun123
When i turn the computer on, before the post beep, it will emit a low, longer beep, more like a duck call than anything else. Than the computer will post, and run just fine. Does anyone know why this is? It also does this during reboot and wake from sleep.

Now that's a good way to describe it - there's a duck in my box.

I had this happen last week with a P35-DS3L running an E2160. Only had it 3 days and it was running fine with a mild overclock for that time. Then I turned it on one morning and was greeted by a quacking duck. In my case the board did a few reboots and reset the FSB etc. It seemed to be running stable but just as you, even waking from standby would give the same noise. And I had fan control etc disabled.

After a day of this I ended up clearing the cmos and it hasn't happened again for nearly a week. Anyone know more about this?

 

[SerpentRoyal]

BIOS corruption can cause a lot of crazy symptoms with P35 boards.

 

[Billbo]

Yes but I'm also getting the cold boot problem occasionally and was wondering if these two things are related?

 

[SerpentRoyal]

Cold boot as in no boot below certain temperature, or you need to hit the reset button to boot?

 

[patsun123]

i fixed my problem. disabled fan warnings and set smart fan to legacy. (if i disabled smart fan it would just run at 100% all the time)

 

[Billbo]

SerpentRoyal, I mean the problem with these P35 boards of deciding every now and then to not like the OC settings and reverting to default FSB and ram timings. I thought it may have been due to low temps at first. But it happened yesterday afternoon when the system was warm and I did a cold boot. And I was running 300x9 (2700MHz) for a couple of days to see if my cpu just can't handle the 3gig that others are getting. BTW been running the Apacer 800MHz ram (true 1.8V) below 800.

In my case the system ran fine at 300x9 for a couple of days, with several cold boots and no problem. Then one day it just did the "can't handle it" and reset the settings. And this has happend 3 times in the 10 days I've owned the board. When OC'ing with everything on normal it seems more stable. So I'd like to hypothesize the problems are due to bad settings. Though the board seems to increase Vcore too much when everything is on auto (mine goes over spec if cpu-z is correct, taking into account 0.045V vdroop).

patsun, don't be too sure about it. I thought I'd fixed it too by disabling smartfan etc but it happened again a few days later. If you google, there are heaps of people with this problem. Apparently it was worse with the version 1 boards but it can still happen with the v2's.

I'm interested in knowing whether most people with this problem are running default voltages on all the buses etc. I have kicked the MCH volts up 0.1V and it has seemed more stable the last 24 hours.

 

[SerpentRoyal]

I'm only aware of a cold boot issue (ambient temp below 60F) with some Abit IP35/IP35-E boads due to a bad transistor. Some vendors will try to circumvent the double post inherent with all P35 chips by tweaking the BIOS. One of the by-product is BIOS corruption during POST. I was able to duplicate this with the Abit IP35-E 14 BIOS. The older 12 BIOS does not have the double post patch. It works fine with no BIOS reset.

I only have a very short exposure to the DS3L, but I would expect it to behave similar to the IP35-E. Perhaps you have an unstable overclock. An easy test is to oveclock by only 5MHz FSB with all other parameters at default settings. If the BIOS resets, then you know that the problem is not related to an unstable oveclock.

I wold also try another BIOS. Look for one that does not address the double post.

 

[Billbo]

SerpentRoyal, I'm still having troubles with this.

It had been running fine but failed to boot again this morning with FSB set at 300.
After playing with settings for a while it would finally boot at that FSB but Vcore had to be increased close to the 1.35V max and with +0.1V on the other voltages.

During these several reboots and power cycling it started producing a very short beep just before the proper post tone.
I loaded bios defaults just to be on the safe side and the short beep is still occurring. What's more I get the long "buzz" the OP mentioned when coming out of S3 standby even though the system seems to work ok.

Like I mentioned this was fixed last time by clearing cmos and starting from scratch.
So it seems maybe bios corruption does occur like you said. Do you have some more info on this "vendor tweaking" that you say may cause this?

I also wonder whether it's worth flashing the bios. But after scanning many forums over the last few days, it seems these Gigabyte P35's have many issues which don't seem to be helped through bios upgrades (a couple of people were told by GB to send the board in for repair, so maybe they know what the problem is).

Is anyone using the new F7 bios on the P35-DS3L and have any feedback on stability etc compared to previous versions? I'm currently at F5.

 

[SerpentRoyal]

They try to stop the double post by tweaking the BIOS. Look for a BIOS that does not address the double post to see if you will get a more reliable POST.

I would definitely try the BIOS before returning the board.

 

[Billbo]

Ok but I don't know how to find info on which bios. The only thing I've found is several people saying they got better overclocks on the F3 compared to the F5. But there doesn't seem to be much feedback about the newest F7 as yet. Though it's been out for almost a month.

Anyway, after clearing cmos once more the weird beeping has gone and it posts much quicker. But I'm pretty sure the problem will return. I won't overclock for a few days to confirm this problem is nothing to do with overclocking.

 

[SerpentRoyal]

Try all of them.