P55A-UD3 internal speaker single beeps

[Cantoris]

That's interesting - thanks for that.
I'd just sent a support ticket too so it will be interesting to hear if they say anything specific.

[crazybones]

Please let us know how you get on. My reply from tech support (in full!) was:

"Please check you have change any setting in bios, for example, cpu warning temperature or cpu/system fan fail warning….etc?

Or install ET6 and set the CPU temp. or fan speed alarm"

[Dark Mantis]

So basically GGTS was thinking it was an alarm that was sounding. Sounds about right

[frustrated]

According to post #18 in this thread http://forums.anandtech.com/showthread.php?t=2093181 BIOS flash F13 apparently finally fixes the 8+ month old problem.

[crazybones]

Good spot - I'd missed the new bios. F13 only lists improved USB 3 compatibility and F14 improved memory compatibility. Time to experiment!

[Dark Mantis]

This is an age old problem with the description of BIOS update features being very unhelpfull.

[TheWarder]

All,

Just built my new PC this weekend based on the Gigabyte GA-P55A-UD3 MB (Rev 2.0) and am experiencing the beep issue... I flashed to F11, which is the latest version available from the Gigabyte website, and still have the problem.

F13 that's mentioned in this thread doesn't seem to be available (anymore?) for the MB. Anyone have any pointers?

Thanks in advance!

Johan

[Dark Mantis]

Hi and welcome to the forum. I would suggest looking on the TweakTown Forum as they have an archive of BIOS updates both beta and final versions.

[Lsdmeasap]

F11 is the latest for the P55A-UD3.

When you flashed did you use Qflash and Disable Keep DMI Data, then load optimized and save/apply/reboot to BIOS after the flash?

If not you may want to try flashing again doing the above mentioned things to see if it helps.   If not try disabling C1E and EIST, and then the other C3/C6 ect settings as mentioned in this thread.

[TheWarder]

Thanks for your replies (and the warm welcome). On Tweaktown the latest version is F11 as well.

For now I disabled CPU temp alarms in the BIOS, which indeed stops the random beeps. When I have a chance I'll follow lsdmeasap's suggestion and apply a more 'thorough' flash process.

In the meanwhile I'm glad I now at least know what the problem is (nothing serious).

Rgrds,

johan

[Dark Mantis]

Just be carefull now you have disabled the alarms and keep an eye on the temperatures.

[crazybones]

Sorry for the confusion. UD4's are up to BIOS version F14 whereas the UD3's latest version is F11.

[Cantoris]

I linked them this (http://www.wpcoe.com/images/intel_c6_state.gif) in my techsupport query.  The reply came back today as follows:

"Hi,

Intel errata number: 3409775, the PECI get temp command occasionally returns incorrect temperature data.
Implication: The PECI GetTemp command occasionally returns incorrect temperature data when the Lynnfield\Clarksfield processors is are in the package C6 state.
Status: No fix, so far Intel has no plan to fix this issue."

[Dark Mantis]

That seems like about "par for the course" for Gigabyte Technical Support. You send them the information and they copy it and send it back as an answer! Great!
What you must do is complain in the question box and they will get someone who speaks english to answer you. It falls far short of good customer relations though doesn't it?

[PC Freak]

Hi All (First Ever Post)

I have hadthe same issue (GA-P55A-UD3) and after many dealings with GGTS and web searching I have found the following.

Intel I5 and I7 (I believe) send out random overheat warnings, now Intel are aware of this and have produced a document to that effect with a workaround.

If the CPU overheat warning is set in the BIOS to any Temperature you will get the random PC Speaker single beeps.

GGTS did say if you change the C state it can stop it.

Obviously turning off the overheat warning in the BIOS stops it.

I was not too happy with that, pressing GGTS further they have basically ended by saying they will be doing nothing about it.

Apparently many other manufacturers have sorted the issue, Gigabyte are dragging behind Here