Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: drb01 on March 25, 2014, 12:53:18 pm
-
What does 6 long beeps mean immediately after power up?
I have only CPU (i3-2100), CPU fan, and 1 or 2 DIMMs installed.
I have tried all combinations of 1 and 2 DIMMs in different channels and still get 6 long beeps.
With no DIMM then I get rapid continuous beeps. Have looked online to find nothing conclusive as to what all this means.
Help MUCH appreciated!!
-
1.AWARD BIOS
1short beep :System normal
2 short beep :CMOS Error
1 long beep and 1 short beep:Memory error
1 long beep and 2 short beep:Graphic card error
1 long beep and 3 short beep :AGP error
1 long beep and 9 short beep :Memory Error
Continuous long beep :Memory not correctly installed
Continuous short beep :Power supply unit failed
2.AMI BIOS
1 short beep :Memory Error
2 short beep:Memory parity check error.
3 short beep :basic memory 64K address check error
4 short beep :Real Time Clock malfunction .
5 short beep :CPU error
6 short beep:Keyboard error
7 short beep :CPU interruption error
8 short beep:Graphic card error
9 short beep :Memory error
10 short beep :CMOS error
11 short beep :CPU cache memory malfunction
-
Its from POST
-
Thanks very much. Gigabyte says it uses "AMI EFI BIOS", but the list doesn't have "6 long beeps" or "continuous short beeps". I have also been to AMI's website which doesn't help a lot ... Have looked around the forums and can't fina anything. Gigabyte tech support doesn't get back to me...
-
I don't know if this will help: http://apurbthegeek.wordpress.com/tag/amibios-beep-codes/
-
Thanks very much. That would suggest it is the motherboard as I don't have anything in the expansion slots. But it doesn't list "continuous short beeps" when there is no RAM installed, which makes me think that maybe Gigabyte have customised the BIOS..
-
Hi
Check the memory thoroughly. Use Memtest86 and run it on each module in turn for about 10 loops. Takes a while but I think that is most likely.
-
Well it did turn out to be the mobo. Replaced that and everything is working nicely now! Thanks very much for your help ...