Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with AMD processors => Topic started by: Darby on August 07, 2010, 08:20:41 pm
-
Basic information:
MB: Gigabyte GA-890FXA-UD5 Rev. 2.0
CPU: AMD Phenom II X4 965 3.4GHz C3
RAM: 4GB (2X2GB) Corsair DDR3 1600MHz C8 PC-PC12800
GPU: Sapphire Radeon 5870 1GB Vapor-X
PSU: Corsair HX850 850W
SSD: Intel X25-M 80GB
HDD: WD GreenPower 1TB, WD GreenPower 1,5TB & Samsung SpinPoint F1 750GB
Problem:
I just upgraded my system with a GA-890FXA-UD5 and 4GB of Corsair DDR3 RAM, the installation went smooth and without a single problem. When I first assembled the computer I used a Be-Quiet! Dark Power 650W
The system starts and everything runs, you can see the GPU-fan and the CPU-fan spinning (and all other fans connected to the motherboard aswell, you can hear the HDDs spinning up and the DVD-writer checking for a CD. But there is no post or boot indication on the monitor. I got the speaker for the case and plugged it in and listen to the beep-code. The beep-code contains of 11 short signals followed by a pause and then continues beeping. It does this in an infinite loop until the system is powered down.
I took a look in the manual and interpreters that as a Power Error, I tried another cable and also disconnecting everything except CPU, RAM and GPU, the problem still remains. I rebuilt the system just in case I forgot something, still no luck.
I now decided to buy a new PSU (just in case the 650W didn't deliver as it should, as 650 would be enough to run the system) and got myself a Corsair HX850 850W. I plugged it and to my despair, still the same beep-code. I now stripped the system to just the CPU and power cable just to check if I would get another beep-code this time, no luck still the same 11 short signal-loop.
I've also tried to reset the bios by removing the battery for a while and removing the motherboard and the PSU from the case to escape any potential short-circuit
As this is my first Gigabyte-board I'm unsure if I have missed something or if I just had the bad luck to get a defect board and need to request a new from the store.
And yes, I have connected the 8-pin 12V (even tried with a 4-pin).
Any help would be greatly appreciated as I already spent way above my initial budget.
-
Well you have already made a good start at faultfinding. You seem to have covered most of the obvious things. It would be worth removing the CPU and checking it for any damage.
-
Nope, the CPU is fine and I know it's working as the last time ran it was 48 hours ago. I also took out the motherboard from the case for a very close inspection and there is no indication of burned or damage circuits.
-
Well I think we can discount the PSU as faulty (mainly because I aslo use that one ;D) so it is either the connections or the board. Try removing the RAM and graphics card and see what beeps you get.
-
Already tested that, still the same beep-code. It could be the power connections on the board is itself tho... never thought of that.
-
Yes look closely at the sockets on the board.
-
All the connections looks fine, even the power connections looks good. It seems to be the board then...
-
Yes I would have to agree. Take it back and get it changed if it was locally purchased if not RMA it. Better luck next time. ;)
-
Aye, next stop RMA! Thanks for the help! :)
-
I actually have the exact same thing going on. PC worked fine for about a week after i upgraded it, my current setup is:
Gigabyte 890FXA-UD5 (Rev 2.0)
4gb PC 10600 Corsair Ram (CT2KIT51264BA1339)
650 watt Corsair PSU
EVGA GTS 250
AMD Phenom II x6 1090T BE (@ 3.2ghz, stock speed)
When I power on the PC all the fans spin up, HDD's spin up, DVD drive checks for a disc, etc - Then I get 11 beeps from my system speaker. Much like the problems OP had.
I have, like OP, disconnected every peripheral from my PC. I have disconnected everything that is not necessary from the board, leaving only the CPU (and heatsink), RAM, and Video card connected to the mobo. Hell I cleared the CMOS with the button on the mobo (after the PC was powered down and the power cable disconnected). I even pulled the CMOS battery before I went to bed, woke up this morning and popped it back in. I have tried cycling both of my ram sticks through all 4 slots one at a time, all of which gives me the 11 beeps. The only time I get a different beep code is if I try to boot with no ram, then I get 12 beeps. I still get the 11 beeps, a pause, and then 11 more beeps, and a pause...so on and so forth.
Much searching through forums and various websites has not turned up any useful description of this beep code - only that it may or may not be a component of my computer that may or may not be working correctly. I have not had the chance to talk to Gigabyte customer service, as they are closed on sundays...
If OP is still watching this thread, did RMAing your board fix the issue? Or did you replace your ram?
Edit 1: Added a bit more description to troubleshooting and the cause of the problem.
Edit 2: This started as a system freeze as I was closing programs to turn my PC off for the night. I shutdown my media player (SongBird) and the system hung right there. I waited a couple seconds to see if maybe it was just some odd hardcore lag or something, but this wasn't the case. After about half a minute of waiting my system responded, but with horribly distorted audio that appeared to be stuck in a 5 second loop. I performed a hard shutdown and when I tried to reboot, I started having this problem.
-
The OP only posted this thread yesterday so there will be no feeback yet. We tried the motherboard without the memory and still had the same beep code. Actually your last remark sounds like a bad latency effect. Not that it helps much now.
-
Oops, didn't even look at the post date. I hope this isn't an inherent problem with an otherwise outstanding motherboard -.-
-
It's only the second one I have seen on the forum so hopefully not.
-
Any suggestions, anyone? I'm desperate to get this system back up and running asap. Seems odd that it can be running perfectly fine, without a flaw, one moment and then be completely dead the next. Albeit, I've yet to have a part break on me up untill this point...
-
Well basically if you have done as you say and the same as the OP then the fault we must presume is the same. I'm afraid it is an RMA. As a matter of interest were you running the memory in ganged or unganged mode? The only other possibility is the CPU but I feel there is more chance of the motherboard being the culprit.
-
Was running in unganged mode - I won't lie, I really dunno the difference between ganged and unganged xD It was a system default so I let it be. I guess I was hoping there was some little gem of a trick I hadn't tried yet to get this bastard back up and running.
-
Not that I can think of, sorry :'(
Unganged or ganged is just the same as single or dual channel modes. AMD recommend unganged or single channel. I don't think there is anything to do but RMA the board but if my colleague absic is watching he is the AMD magician and may have some idea.
-
Seems strange that 2 similar systems can fall over like this and the obvious thing is to look for common elements to try and pinpoint the cause of the problem.
The problem could be caused by the CPU and I have noticed a couple of things, whilst trawling the net, where the Memory Controller on some of the Phenom ii CPU's has been the problem so don't ignore this as a possible cause. If possible try a different CPU just to confirm that the problem lies elsewhere.
Without having your hardware in front of me I can't really say what is wrong so sorry, but all I have are some questions:
What HDD(s) are you using?
Are you running your HDD's in IDE, RAID or AHCI?
Have you any other hardware installed in the PCIe or PCI slots?
Have you checked your keyboard and mouse are OK? (If they are wireless try swapping for PS2 or USB model)
-
@ absic
I'm currently using 2 SATA HDD's, specs are below:
My OS drive is a Seagate 500gb drive, Momentus 7200.4,
My secondary drive (storage/media) is a 320gb Seagate Barracude 7200.10
Both drives had been running in IDE mode. There is no other hardware installed in the PCIe/PCI slots. I'm currently using the same keyboard to type this message, and have also been using the same mouse (working on a backup laptop). I do have another phenom in the house but it's of the original Phenom x4 line, and I haven't looked around to see if I could pop it into an AM3 board without problems. I'm leaning towards it maybe being a RAM issue, but only because most of the googling I've done on the 11-beep-code seems to suggest it's a RAM issue. I also tried a little bit more troubleshooting, completely disconnected the Mobo from any source of power, hit clear CMOS button, threw the clear CMOS jumper on for about 5 seconds, pulled out the ram and CPU and video card (basically tore this mofo apart). I'm still getting the 11 beeps!
I don't expect anyone here to have a magic fix at this point - However, if this starts to become an issue for other people with similar setups (or mobo's, specifically), it'd be nice to have as much info available as possible.
So, should I RMA the board or the ram? Or both, since I just got this stuff earlier this week from NewEgg?
-
The problem is that it could be the CPU as the memory controller is part of that rather than on the motherboard.
If your old CPU is AM2 or AM2+ you can't fit that to an AM3 board but, if you have an old AM2 or AM2+ board you could, if the BIOS has been updated to accept it, put an AM3 CPU into that. (It maybe a way of checking if the CPU is OK if you have an old AM2(+) board & DDR2 RAM)
If you got all the parts from Newegg it would be better to return the RAM, CPU & Motherboard and ask if they can check all of them.
Just as a thought I haven't seen through this thread which BIOS version you were using and I can't see it mentioned by the OP.
Before the problem occurred had you updated it at all?
What version were/are you using?
I notice that the F2 & F3 version both address CPU compatibility and memory OC ability.
By the way the reason I wondered about your HDD's is that sometimes the so called "green" models can cause problems.
-
When I first put the mobo in, it was using the F2 bios. That same day (last tuesday), I flashed to F4 just to be sure it was as up to date as possible (i'm somewhat OCD about that, even though it probably wasn't necessary). RMAing the whole set seems like a safe bet, so good suggestion there, i'll prolly do that.
I'm gonna pop this processor into my AM2/AM2+ board and see what happens...With any luck, AMD hasn't failed me as a CPU manufacturer! I only say that because I have never had any trouble whatsoever with AMD CPU's before, the things are tanks.
-
I have built over 100 rigs using AMD processors and I have yet to have one cause a problem. But that doesn't mean there can't be a problem there.
If everything was working fine before the BIOS update, I would be looking at that as the probable cause, but again, it is very hard to prove.
RMA'ing the kit, although annoying, should give an indication of what's gone wrong and it has the advantage of saving you from pulling out too much of your hair.
Let us know how you get on.
-
Just to comment on the memory controller thought, I tested to run the system with only the CPU connected and got the same beep-code. I also reassembled my old system and the Phenom II X4 ran perfectly on my old mobo. I however couldn't the system to boot at all on the Gigabyte. I sent the retailer an email about an RMA but will get an answer earliest monday.
-
In that case it seems to prove the bad board theory and the RMA was the right way to go.
-
Amazingly I found this thread. It seems with me included, there are three of us with the same issue within a couple days. Same troubleshooting and same effect.
System stats are:
AMD Phenom II 1090T Giga 890FXA-UD5
Corsair TX750W Patriot 1333 Gseries DDR3
Kingston 64 Gig SSD WD 1TB Black
(Although it never made it to the drives nor have I hooked them up to T/S this. Worst part is, this is my second UD5 as I had just RMA'd one due to another issue. The new board fixed that issue but created this one.)
I'm gathering most are attempting to RMA the board and CPU. I do hear CPU's are harder to turn back in though. Just figured I'd post for reference sake and let me know if anyone's get's fixed by whatever method. Appreciate the time.
V/R
-
Thanks for the post the more inforamtion on these things the better, but let us not lose sight of the fact that millions of these boards are made and only a handfull with problems are ever posted about on these forums. When you are on here all the time it can seem like it is a massive problem building up but this is not the reality. ;)
-
Bad new from the clinic, I just got the result of the error diagnosis done by the store. They couldn't find any faults and the mobo worked fine with two different setups and they've sent it back to me (they were even nice not to charge me with the "if-theres-not-a-problem"-cost. That seems to comfirm (in my case at least) that the CPU is the problem, which is weird because it's on the CPU Support list for the rev. 2.0.
I'm now considering buying a new CPU (X6) to have some use of the parts, however I'm not sure if that is the right way to go, spending even more money...
-
Yes your CPU is on the support list.
Can you RMA the CPU?
It should be covered by AMD's Warranty which, I think is 3 years. Annoying, I know, but probably a cheaper option.
-
Same store but yes, I could probably RMA it. However it has been in a small cooling paste accident earlier where cooling paste got stuck under the CPU between the pins.That could probably cause the problem in the first place but as I said earlier the CPU runs fine on my old mobo. And I don't think they will find any faults with it which means that this time I need to pay them for sending in a fully working part for RMA.
-
Did you send them the CPU when you returned the motherboard?
It might be worthwhile getting in touch with the supplier again, explaining the problem you are having and sending them the board, RAM and CPU to see if they can get it working for you. Still cheaper than a new CPU and, if they can't get it working they should be able to pinpoint the problem and correct it or advise you where you have gone wrong if everything is OK.
With regard to the thermal paste that may have accidentally got onto the CPU pins. You could try cleaning the pins with a small piece of kitchen towel and a little alcohol. I usually use Isopropanol (IPA) alcohol, the trick is just be careful not to use too much alcohol and not to be too rough when wiping the pins.
-
Well something is faulty and you said they checked everything else out and was ok. Therefore the CPU must be faulty or at least incompatible.
-
Nope, I didn't send the CPU when I returned the board.
I think the solution will be to buy me a new CPU and try to sell my old rig to a friend to get the money back.
-
That's a definite way to lose friends quickly ;D
-
Hehe, the old rig works perfectly actually (yeah, you might be wondering why I updated in the first place :D)
-
It's the price we pay for having this hobby! ;)
-
*sigh*... Well I got the mobo back from the store and I even bought a new CPU, this time a Phenom II X6 1055T 125W, and guess what? Same 11 beep-code from the mobo. I must be missing something somewhere. The funny thing was I chose the GA-890FXA-UD5 over the Crosshair IV Formula because I was afraid it would have the heat problem. It seems that I can't handle a mobo from Gigabyte.
Any ideas on what I might be missing?
-
I am a bit busy right at the moment but I will go through the entire thread again and see if I can come up with the answer. I will post again later.
-
OK,
I have gone back through the thread and I am at a loss to explain what is going on.
The only thing that gave me cause to ponder was your Graphics Card. Have you tried swapping that for something a little lower spec?
Ooo! Whilst typing this I just had another thought, what keyboard and mouse are you using? Are they OK? I have seen so called DOA Systems spring to life with a different keyboard and or mouse.
-
I will try my older 9800GT as we write (:D). I'm using a SteelSeries Xai Laser with Logitech Illuminated, both working prefectly with this netbook and my old system.
-
Nope, same error with the old card aswell. Been thinking a bit and after reading the interesting information absic posted about memory speeds and the amd memory controller, could it be that the RAM won't underclock itself to 1333Mhz but rather keeps running at 1600Mhz creating this beep code? It won't explain how the other got the same beep code but if this error signals a memory problem that could be the problem. Just a thought...
Edit: scratch that, got a post with the old card however with using the lower pci-e x16... hmm
-
It's a puzzle and that's no doubt.
It is always much harder to diagnose a problem at distance but I am forced to admit to a lot of head scratching here. ???
I would suggest trying a basic mouse & keyboard just to totally eliminate the Logitech ones as the cause of the problem as there have been occasional issues with Logitech before.
If that doesn't work then try the different Graphics Card.
If that doesn't work try a different monitor. (Sounds stupid but we have had a couple of problems on the forum recently that were due to incompatible monitors)
I'll keep thinking and I'm sure Dark Mantis will offer further advice and/or moral support. :D
-
Hurray, I got a POST, however with my old GFX card in the other pci-e x16 slot, I'm now going to try to get my new GFX card working using the same slot...
UPDATE1: Got a POST with my "new" GFX card, however only with one RAM connected and using another set of pci-e power cables...
-
UPDATE2: Found the problem, a faulty RAM-stick (and it was of course the one I used when I first tested running the system on one stick) as I got the system working using the default PCI-E power cables and got the system to post using the other RAM. A second RMA seems to be the solution to my problem noew located problem (deja vu...)
-
Oh well, all's well that ends well....... I hope! :P
Good luck with your new RMA and let us know how things go.
-
A very good reason to have checked it with Memtest86 at the beginning. Ah, hindsight is a very wonderfull thing ;)
-
A very good reason to have checked it with Memtest86 at the beginning. Ah, hindsight is a very wonderfull thing ;)
The system wont even boot with it connected.
-
You know, I thought it was only apple's that spoiled everything. Now it seems like one male sheep can ruin things too! :P
-
I have the exact same peoblem
but I've found out that is the psu, as I test it on another computer and it will freeze up under the OS and then didn't even post like doing the same with the GA-890FXA-UD5
you can call me as you like
but I have notice that all the treads I've read from the users with the same problem are using Corsair PSU
is there any possibility that the board draws too much power from tha psu, or either the psu just won't keep up with a Motherboard this "High end"?
-
Hi Christoph,
You are quite right about the possibility of there being to much of an energy draw being asked for when the PC first BOOTS up and it is something both Dark Mantis and I have been considering, especially with some of the newer GPU's.
I will make a few enquiries regarding this and will post back when I can get some proper information.
Thanks for your input, it is much appreciated.
-
So, I've been getting the exact same thing. Well, I am now. I got all the parts for my new machine about two weeks ago. I went with:
GA-890FXA-UD5 R (v2.0)
Phenom II 1090 (OEM)
This memory: OCZ3RPR1333C9LV8GK http://www.newegg.com/Product/Product.aspx?Item=N82E16820227541
Sapphire HD5830 RT
and a crucial 128gig RealSSD.
and... drum roll please: CORSAIR HX Series CMPSU-750HX 750W http://www.newegg.com/Product/Product.aspx?Item=N82E16817139010
So it was up and running for a few days, though it would BSOD a few times a day and I was trying to figure out what was causing that. I upgraded to f4 bios just fine. Rebooted and everything.
I had played around a little with overclocking using AMD Overdrive and I decided to just restore it to the default config (which I had been running mainly anyway). So I went into overdrive and clicked reset default settings. And my screens went blank. Computer turned off.
Tried to reboot, no beeps, lights fans went on for a second then off. I took everything out of the case, unhooked everything but the proc, could not get it to beep let alone post. Fans would come on, lights, but no beep.
So, it has to be either the proc or the MB right? I bought the proc at superbiz (which was stupid, should have just got a retail one) and the board at newegg. Anyway today I took it into fry's to see if they could tell me which was busted so I could replace the part. The service guy was actually pretty awesome and nice to help me out, but he did. He ran my board with his proc and it worked. Got video and everything. He ran my proc on his board and it was dead.
Ok, fine. This shouldn't have happened but I'm a big boy, I read the giant screaming warnings on the screen and clicked ok. I can accept that I fried a proc. So I'm at fry's, might as well buy another 1090.
Take it home, set it up, it beeps. I get the same 11 beeps, pause, 11 beeps. but no video. I tried this with my 5830, and an old 4650 from multiple slots. I tried it with memory, without memory, one dimm, two dimms, all the memory slots, etc. 11 beeps.
The manual for the mb says "continuous short beeping" is a power problem. This isn't quite continuous, but it doesn't mention 11 anywhere. Anyway, my old machine is a dell core2 machine and I can't use the powersupply from that because it's only 300w and only has a fourpin for the cpu power. So I do it the other way and run it off of my corsair which works fine.
So, now I'm really not sure what to rma? Is it the psu? The super duper nuclear bomb proof, comes in a freaking VELVET BAG psu that cost me a $300 proc? Should I RMA the memory? My old box is DDR2 so I can't test it. And fry's is a bit far, and they already really went above and beyond helping me once with suff I didn't buy there.
It really does seem like this motherboard, proc and PSU simply do not play well together.
What do you guys think I should do?
Oh, I was also wondering about that whole short beep long beep being subjective, because long beeps are a bios issue right? So I've posted video for anyone to see.
http://www.youtube.com/view_play_list?p=32772F4144013545
Ok, this has now eaten my entire weekend. I'm going to bed.
-
Well firstly it is definitely 11 short beeps ;) I think the memory controller has gone which is on the CPU but I must admit that doesn't sound reasonable considering that you have just changed it.
Can you swap the slave PSU over to just power the board and use the Corsair to power the GPU etc?
-
Just another thing to try out if you haven't already done so, is clearing CMOS as this can sometimes help.
After you have cleared CMOS go through the same steps that you did before but don't use the 5830 Graphics Card but try with the 4650 in the 2nd PCIE slot instead. I know the manual says to use the first one but....... :-\
There have been several cases recently where the higher end GPU's want a lot of power at start-up and this might be the problem you are now facing. If we can eliminate or prove that is the case we will have a better understanding of the next steps to take.
-
I have tried resetting the cmos on numerous ocassions using the button, jumpers and removing battery. Sometimes all three.
I think did try the 4650 on the second 16x slot, but I'll try again after work.
As to using the psu from the dell, I'm a little leary of that. Mainly because I work from home and I need a working machine to actually do my job. The dell's power cables are all too short and clipped in, so I'd have to remove it and apparently dell doesn't think a psu should be user servicable. Also, it doesn't have a hard power switch which scares me a bit.
-
That's fair enough. Well can you borrow one just to try?
-
I don't really have anyone to borrow one from. Re the video card, do you think it would matter since the same beepcodes happen with no vid at all?
-
To be fair probably not. Just trying to cover all the bases. I would just RMA the motherboard and have done with it. From everything that you have tested it looks to be faulty.
-
Yeap
11 beeps just like mine.
the thing here is that I have tested the Psu on another computer and it does the same, I think (don't know much about this) the 3+/5+ line got broke
Another thing in common is that we all flash to F4, and the thing is that the board sets the vcore for boot at 1.47v with the cpu running at 2.8 GHz, either the F4 bios revision is misreading and is giving more Vcore than that, causing either hardware to blow
one thing I'm almost sure, is that the pause between the 11 beeps, is a reboot, I know this cuz I have the HD4890 that lights up and starts with the fan at full speed at the boot, if is a bad board it would not try to reboot (correct me on this one)
people with the same symptoms (the board of course) have RMAed the board getting it back with instructions that 'No trouble found"
-
Thanks for sharing that information with us. Sometime ago I was helping a member with that exact same fault and the tech support told him to RMA it because anything other than standard beep codes means a faulty board. :-\
Do you know what other hardware has been blowing?
-
Cristoph, do you mean that your PSU worked in the other machine? Or that it made the motherboard there fail too?
I bought this on Jul 31 so if I want to RMA to newegg I have to do it quick. I'm just not sure *what* to rma.
-
No basically he's saying the same symptoms happened on the second computer when he swapped over the power supply. In other words faulty PSU. This is why I was advising trying another PSU earlier.
-
Doesn't it seem somewhat coincidental that the powersupply would flip out just at the exact time I pushed a button in amd overdrive? And then fry the cpu? I mean, I'm leaning towards the PSU as well, I'm just not sure what it didn't mess up the mobo too...
-
This is often the problem when more than one device might be blown. Without being able to test things "hands on" it can be difficult. Dont worry about the board though, you have three years warranty on that and I suspect the same for the CPU. I don't know about the PSU but most are at least three years. Can you not just take all the bits to them and tell them that it is faulty and the symptoms?
-
Well I ordered them at newegg so my choice is either return for refund (-15% restocking) or return for replacement. But if the psu sucks, I'd rather just get another one.
-
Just to add another headache what made you choose those memory modules? They are designed for the Intel platform not AMD and neither Gigabyte or OCZ lists them as compatible with your board.
http://www.ocztechnology.com/products/desktop-memory/ddr3/enthusiasts/reaper-hpc-series/reaper-hpc--small----optimized-for-the-intel-lynnfield-platform/ocz-ddr3-pc3-10666-reaper-cl9-edition-low-voltage-dual-channel.html
-
Basically I didn't know enough when I bought them a I wanted 4gig dimms. But they seemed to work fine, passed memtest,etc. Maybe I'll just rma the memory and PSU and go get better for both.
What memory would you recommend for that board?
-
You are probably better off asking absic that one, but I would say that the speed is fineand jsut find some that are on the QVL(Qualified Vendor List) from either Gigabyte or the memory manufacturer. Personally I like Corsair but you would need a different set to mine because I run an Intel i7 platform. I am not so keen on OCZ but that is a personal choice which I am sure that others here would disagree with. Crucial are another company that I have used many times in the past and have a good track record for replacements.
Personally I would be surprised iof your PSU is faulty being a Corsair one(if memory serves me rightly it is the HX750) and they are warrantied for 7 years. That shows the manufacturer has faith in their quality! ;)
-
I thought the same about the corsair psu, there do seem to be quite a lot of people on newegg who had one die though. I would really like for gb to answer what those beeps actually mean. It would help. As it is I think I might just rma everything then go buy local so I can have someone to test it if anything doesnt work.
-
Well that is probably the most sensible thing to do but you must have learnt quite a lot on this build anyway. You know where to find us if you need any more help or information(before or after your build) ;)
-
I'm having trouble finding the list of approved vendors on their site, do you know where it is?
Thanks!
-
well
mmm, no, the psu didn't work with the other computer, as is doing the same, turns on, but won't go into bios
and, actually I have RAM'ed this psu once that it has 5 year warranty besides that Corsair did sent me another Psu with 6 pci-ex onnector having the original just 4
I won't be surrise myself that the psu did blow, as I said I already have one bad, but don't get me wrong, I still think that Corsair is one of the best brands there on the market, may be just some bad design or some
anyway, some other guy, I think was in this tread that had a faulty ram stick having the same symptoms
-
I'm having trouble finding the list of approved vendors on their site, do you know where it is?
Thanks!
Do you mean the QVL for Gigabyte? If so try here: http://www.giga-byte.co.uk/products/product-page.aspx?pid=3519&dl=1#dl
If you want Corsair here: http://www.corsair.com/
Crucial here: http://www.crucial.com/uk
-
I'm going to go drive all the way out to fry's tonight and buy some new memory and a new PSU then rma these. If it still doesn't work, then I think I'm going to get a different make of board.
Thanks for all your help. I'll let you know what happens!
-
Yes please do, I would be very interested.
-
another board.....
hmmmm, I did switch sides from Asus buying this board that have a problem, and just cuz the support the provided to my old board simple sucks
actually I even was about to buy the crosshair IV
-
Hi Christoph,
You lost me there, have you replaced your board? Actually the Crosshair IV is a nice board but people even get problems with that.
-
I have not replace it, I really like this board cuz it has some good features
besides that I wanted so badly to change sides from Asus to Gigabyte.
Asus support sucks, please Gigabyte, hear me and don't let me down
we still need to know what those beeps means, cuz I'm buying ahother psu tomorrow and I not gonna put it to work on the UD5
-
Yes i would have to agre with you about the ASUS technical support being hopeless. Gigabyte is better but still slow and if it wasn't for this forum there would be a lot more dissatisfied customers. The problem being that the only link between us and Gigabyte is their official moderator, runn3R, and he is overworked and can't devote his entire time to the forum.
-
yeah
this community is kinda good, I like the communication that rules over here.
But as you have said, we still need more people from Gigabyte checking the forum cuz this is taking forever and I need my computer running not sitting just there
-
I have to tell you guys that I bought a new PSU that didn't work either so I ended up returning the psu
we need to know what is the problem with the board.
any news about it? I thought by now we would get an answer
-
Hi again Christoph, I am afraid that you picked a bad time for you system to go faulty, runn3R has just come back off holiday and is now trying to catch up, on top of that he is getting ready for this show so I don't think we will be seeing a lot of him for the rest of the week. Did you put a question into GGTS?
-
Not really
but this other guy have sent the video that he took about his MB, and I was kinda hoping that would've be enough to get their attention
-
It may be but I would have to advise you to take your own approach too. Not only that the more people that make a complaint/fault question the more notice it will receive. ;) It is always logged for any future problem you might have.
-
Done
but I know that it would take 4-5 days to get an answer, that actually will be converted to a question
this is my first time that I emailed Gigabyte, we'll see how they handle it
-
Well let us know the answer too please. ;)
-
well there's another guy with his MB being halt by Gigabyte for more than a week
and there's another guy that got his MB back from Gigabyte and guess what? No trouble found
-
To be honest not all RMAs are valid and as we have found out later here on the forum sometimes there is a different reason for the problem. We try and reach the right decision give the facts but that doesn't make us infallible.
The one you are referring to regarding his board being in RMA for some time was just due to bad timing, not his fault obviously, but these things happen. :-\
-
so
any news about this?
any other suggestion?
-
No, not that I have seen so far. Everthing is very quiet :-\
-
How come nobody else is getting issues with this board?
only a bunch of motherboards turn to be bad?
and then, why Gigabyte is not doing anything as one guy got his board back from Gigabyte with the same problem claiming that the board has nothing wrong
-
How come nobody else is getting issues with this board?
only a bunch of motherboards turn to be bad?
and then, why Gigabyte is not doing anything as one guy got his board back from Gigabyte with the same problem claiming that the board has nothing wrong
I am sure that others are having problems as well Christoph. It may be that they went direct to GGTS and didn't come to the forum or it might be that they are buried deep amongst the other queries.
As far as the chap who had his board returned as NFF(No Fault Found before somebody puts their own description to the acronym) it could well be true. Maybe there is some other explanation for the problem. I am not trying to stick up for Gigabyte but you have to be fair in your assessments. We have made wrong diagnoses before.
-
2 days for RMA approval
I cannot believe that companies that are worth billions cannot have at least a regular costumer service and they even dare to call it "costumer care"
but well mmm is all right actually it is my fault for change from bad known to even worst unknown
yeah this is what I get
-
I just had issues with my MB also. It ran for 2 months then will not boot up. It would power up but no beep to show it is booting, just a no signal sign on my monitor. The MB gave no beebs at all. Removing the RAM gave the the RAM beeping (moving them around, trying 1 slot at a time caused the same no booting up). With everything removed, the RAM, CPU, graphics card the MB made no sounds at all (according to AMD the MB should beep). The CPU (AMD 955 BE) was sent for RMA and was found to have no problems. I sent my MB for RMA and have no new information. I am disapointed though. I always went with ASUS but they have bad driver update support. I went with Gigabyte and my first MB from Newegg was DOA. Now I am having issues.
CPU Arch : 1 CPU - 4 Cores - 4 Threads
CPU PSN : AMD Phenom II X4 955 Processor
CPU EXT : MMX(+), 3DNow!(+), SSE (1, 2, 3, 4A), x86-64, AMD-V
CPUID : F.4.3 / Extended : 10.4
CPU Cache : L1 : 4 x 64 / 4 x 64 KB - L2 : 4 x 512 KB
CPU Cache : L3 : 6144 KB
Core : Deneb (45 nm) / Stepping : RB-C3
Freq : 3214.72 MHz (200.92 * 16)
MB Brand : Gigabyte
MB Model : GA-890FXA-UD5
NB : ATI ID5A11 rev 02
SB : AMD SB850 rev 40
GPU Type : Radeon HD 5870
GPU Clocks : Core 157 MHz / RAM 300 MHz
DirectX Version : 11.0
RAM : 4096 MB DDR3 Dual Channel
RAM Speed : 803.7 MHz (1:4) @ 9-9-9-24
Slot 1 : 2048MB (10700)
Slot 1 Manufacturer : G.Skill
Slot 2 : 2048MB (10700)
HD: SSD
PSU: Thermaltake Toughpower 850
-
I was always under the impression that the CPU needed to be installed(obviously including heatsink and fan) to have any POST beeps.
It does sound like a fault on the board though and hopefully when you get it returned/replaced all will be well but please keep us informed of your progress, albiet slow ::)
-
Welcome to the club
The same exact crap happend to me, I always bought Asus MB but forthe same reason about the driver support, I've bought a Gigabyte MB forthe first time that was up and running for only 2 days
I've send my MB for RMA yesterday, hopefully I will get it back next wednesday
-
2 days for RMA approval
(...)
Hi Christoph
Are you from the USA or UK?
-
hi, i live in usa but i'm from mexico
-
hi guys, how/where can i check rma status
-
RMA from USA has been discussed here:
http://forum.giga-byte.co.uk/index.php/topic,447.msg2042.html#msg2042
-
Hi all,
very nice forum!!!
The absolute same problem happend to me and now I have no further ideas. Now we are 4 people with that issue.
- ~14 days ago I flashed my board to bios F4
- 10 days ago my PC switched off in the middle of my work ( somehow like a power cut )
- next power on the system doesn't start (only 11 beeps)
- I tried nearly everythink without success
- I used the Gigabyte Support Webside with detailed information
- They asked me If I have installed the correct operating system drivers???
- Ok :-) I called the Gigabyte telephone support
- 10 or also 11 beeps means that there is an memory issue
- Together we tried every combination of putting my memory to the board ( right ... left side, and so on)
- Gigabyte suggested me to send back the CPU (because the memory controller is inside the CPU) and also the mainboard
- I send back the CPU and also the GA-890FXA-UD5 (Rev. 2.0) to Mindfactory (also with detailed information)
- today I got both back - CPU and motherboard should be OK ( Next RMA without reason I have to pay)
- I put again all together, starts the system and ... 11 beeps
- I checked again every connector
- I also checked the +5V and the +12V line
- I removed every not needed device like hard disk and so on
- I changed all cables I was able to exchange
- I tried again a CMOS reset
Result -> ... 11 beeps
My last idea I have is that all 4 memory modules I use are broken. I think it's not possible but ...
Unfortunately I have no DDR3 memory to exchange and test.
Does anyone checked new DDR3 memory?
I'm happy about any new idea's. Sorry for my german english.
-
I would have to agree with Gigabyte support here. It definitely does sound like a memory controller fault which as you say is on the CPU. What speed were you running your memory at? Can you also list your hardware please including PSU?
-
Hi Dark,
thanks for your answer.
The components are
-PowerColor GoGreen 5750
-Gigabyte GA-890FXA-UD5 (Rev. 2.0)
-G.Scill DDR3 1600 PC-3-12800 (4x2GB) F3-12800CL7Q-8GBECO
-Enermax Pro87+ 600 W
-Caviar Black 1TB
I agree with you but I send back motherboard and CPU to Mindfactory and they state that they have tested both with success.
I just read the entry "VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's and RAM SPEEDS".
I'm not interested in overclocking. Some minutes before the crash I started EasyTune. I wrote some multicore source code and was locking for the system temperature. More playing than it was needed. The EasyTune application crashes and sends error report.
I have respect for overclocking so I think I have not changed any values.
But there was another person while playing with AMD Overdrive the system crashes. So may be that is the hint for all the problems.
Unfortunately I don't know the next step. CPU and motherboard are checked and should be ok. PSU on another PC will run.
May be back to bios F3 will help
Is there a possibility to send the whole system to e.g. AMD or Gigabyte?
-
Hi there,
My best advice would be to return the CPU to AMD as there have been a few cases of the Memory Controller failing under the circumstances you describe. In fact, I know this has happened to one of AMD's own Technical Support Gurus in the UK so they are aware of the problem.
AMD's normal response is to return a new CPU, enough said! :o
-
A have try with A brand new set of CPU and RAM with no luck at all
still 11 beeps, so what is gonna be, everything? or nothing?
-
and there's another guy that had this same problem but from the very begining he push the ON button for the first time after finishing hooking up every hardware just out of the box
-
Hi Christoph,
I see you also try everything to get your system running again.
Today I will try to contact AMD and may be again Gigabyte.
I will inform you about all further information I will get.
-
I really don't know if it will help at all but all knowledge is useful. I did a bit more digging around and found that the 11 beeps is recognised as a memory problem. Of course we already thought that was the basic fault but just to confirm out theories.
-
Hi tzky
In such situation it's definitely worth trying to check with other RAM.
And check your G.SKILL RAM with other MB, as it maybe faulty.
-
As runn3R suggests you could try checking your memory but I can't really see all four modules being faulty :-\ Download and run Memtest86+ on each module, one at a time for several loops each. Time consuming but thorough! You can get the free utility here: http://www.memtest.org/
-
If system will run with 1 stick then check the RAM voltage in BIOS before installing 2 or 4 sticks, as ECO series work at 1.35V, not the default one (1.5V).
-
Yes I was able to test my memory in another PC. One module seems to be broken.
Unfortunately the good tested memory and also DDR3 memory from another PC will not work on my GA-890FXA-UD5.
So same situation as Christoph. He has changed CPU and Memory without success.
In my case CPU and mainboard are successfully tested by Mindfactory. I think there are a combination of more than one problem.
At the moment I'm in contact with Gigabyte Germany.
-
Yes I was able to test my memory in another PC. One module seems to be broken.
Unfortunately the good tested memory and also DDR3 memory from another PC will not work on my GA-890FXA-UD5.
So same situation as Christoph. He has changed CPU and Memory without success.
In my case CPU and mainboard are successfully tested by Mindfactory. I think there are a combination of more than one problem.
At the moment I'm in contact with Gigabyte Germany.
I think the point that youi may be missing is that whether the memory is good or not it might be not compatible and changing it to another pC won't prove that one way or another.
-
ok
so, my cpu is dead along with one memory stick
take note, the good ram stick was not working with the new cpu I tested the MB with, why? don't know
but after a few tries in all the slots that ram stick worked, how? don't know
So, 11 sort of short beeps means Ram problem, but according with Gigabyte, does not matter how many (sort of, kind of, maybe) short beeps there are, that means is a Ram error, you could have 4-5-7 short beeps that means ram error
so what we have here is that the MB itself can decide how many short beeps to through for the Ram error
that is clever :thumps up: for Gigabyte
-
Ok, so after just 2 days AMD shipped the replacement for my cpu
anyway, just wanted to ask you one last question
what do you guys use to monitor temperatures and Voltages? other than Everest and AMD overdrive (amd overdrive could be the one blame for my dead cpu)
-
As a matter of interest whay speed were you running your memory at?
On the Intel side of things we use Core Temp but I think that Real Temp is preferred on the AMD platform. Everest is ok.
-
RAM was at 1600 with the stock timings 9-9-9
ok, you have the UD7, so what actually shows the CPU-NB voltage for you?
I can tell that you have overvolt the CPU-NB at least a little bit, but actually shows the voltage you set for it?
everest shows me the stock voltage (1.75) does not matter what voltage I set
right now I got 1.2v cpu-nb, at least I think cuz everest says 1.75
-
RAM was at 1600 with the stock timings 9-9-9
That could well have been your trouble as the CPU memory controller can burn out if used at over 1333Mhz. Absic spent a lot of time and trouble doing a series of tests that he has kindly shared with the forum and are there for anyone to read and hopefully learn from.
http://forum.giga-byte.co.uk/index.php/topic,2515.0.html
*I will answer the rest of your question tomorrow as it is quite late now.*
-
I know that
people, are running their ram even at 1900-2000 MHz without any issue
and yeah, i know, I know, it does not mean that my cpu can do the same
-
You are quite correct even AMD's technical engineer was running his memory at 1600 until it killed his CPU one day. That's when they started checking into it. They say it is quite possible to run it at higher speeds but sooner or later it will burn out your CPU. :'(
-
so, about the software?
what I really need to check is the CPU-NB, that's all...
-
Sure you can have my readings but I don't really see what good they will do you because I am running an Intel platform I have the GA-X58A-UD7 board with an i7 920 processor. Under Everest the CPU is 1.23V with the memory running at 1.65V on XMP. Northbridge core voltage is 1.1V Hope this helps you.
-
I've posted similar problems on "GA-890FXA-UD5 (rev 2.0) & X6 1090T: no POST, 10 short beeps"
Darby and Christoph found that RAM was culprit.
Svindle, genyx_04, Lazlo, nashelton and tzky: please, how did you resolved?
-
See the topic I posted today, I hope it helps. I needed to update the BIOS to F5 to fix my issue (10 beeps and later no POST beeps at all). Note that the 890FXA-UD5 in my case was a very new H/W revision 2.1