Bobnova Posted August 19, 2013 Posted August 19, 2013 I often wondered if there shouldn't be point separation between cooling methods, but in the end it would be difficult to properly police it. So rules wide open, run what ya brung! Do the best you can. No way to police it other than videoing the runs, and that's a major PITA. Quote
zeropluszero Posted August 19, 2013 Posted August 19, 2013 it takes a lot of work to write your name, date and the score on a piece of paper and take a photo of your rig showing that piece of paper?'murica eh? You bet. -Australia out. Quote
Xtreme Addict Posted August 27, 2013 Posted August 27, 2013 I will also try to get some prizes I don't have golden AMD cpus though, but 3rd place looks tempting! Quote
Crew Trouffman Posted August 27, 2013 Crew Posted August 27, 2013 ehehe jsut for the fun and because it's good to have some NON UBER Exepensive contest sometimes Quote
I.nfraR.ed Posted August 29, 2013 Author Posted August 29, 2013 (edited) Not sure where I need to post this. I had problems with Gigabyte FA85X-UP4 - updated the main bios, restarted and tried to change some settings. Saved and restarted, then it was stuck at 84 code. Apparently, the main bios got corrupted (I guess during the flash process and trying to change some settings and save them triggered the bad block). Board was trying to load from backup bios, but what I got was just a blueish gradient screen with a gigabyte text. It seems the board didn't detect main bios is corrupted and that's why it didn't rewrite it with the backup bios. I tried different ram and cpu and what not, but didn't go further than that. Shortcut keys didn't work. So then I searched for the datasheet of the bios chips - MX25L6406E. According to the datasheet pin #7 is HOLD and pin #4 is GND, so I took one paperclip, shorted the pins and turned on the board. It booted and I released the short. Luckily it detected the main bios is corrupted and reflashed it with the backup. It might be useful for other people. This method should work for most of dual-bios Gigabyte boards. Edited August 29, 2013 by I.nfraR.ed 1 Quote
dinos22 Posted August 29, 2013 Posted August 29, 2013 You can short pin 6&7 also with a screwdriver, it's easier Quote
Strat Posted August 30, 2013 Posted August 30, 2013 Wow very usefull, thanks a lot for sharing this Infrared! Quote
rsnubje Posted August 30, 2013 Posted August 30, 2013 Just asking in case, can an A88X motherboard be used? Quote
Calathea Posted September 1, 2013 Posted September 1, 2013 Every gigabyte fm2 or fm1 regardless of chipset. The rules are pretty clear about that. Quote
Calathea Posted September 2, 2013 Posted September 2, 2013 Oh, A88X is FM2+. Really legit question by RSNUBJE then. Quote
Massman Posted September 2, 2013 Posted September 2, 2013 Will check this today. A88X is pretty much like A85 chipset, FM2+ is just FM2 with Kaveri support. Quote
rsnubje Posted September 9, 2013 Posted September 9, 2013 Except for that it's not really available yet, but I just happen to have a hand on an A88X board. Will probably just use good old A85, or 990FX with FX-8350. Quote
Hiwa Posted September 11, 2013 Posted September 11, 2013 (edited) Nice score hazzan Edited September 11, 2013 by Hiwa Quote
Massman Posted September 11, 2013 Posted September 11, 2013 Will check this today. A88X is pretty much like A85 chipset, FM2+ is just FM2 with Kaveri support. Oh right, A88X is allowed since the only difference is official support for USB3, PCI-e Gen3, and Kaveri. Kaveri CPU is of course not allowed. Quote
BeepBeep2 Posted September 12, 2013 Posted September 12, 2013 Hi. Daveburt714's gem FX-8120 will be up on teh bench hopefully before comp is over. I have an A6-5400K and ASRock FM2 M-ITX but it's not gonna win anything. Can't even get DDR3-1866 divider to work Quote
HobieCat Posted September 13, 2013 Posted September 13, 2013 Just got everything set up (8350 and UD7), went and filled up my dewar, I get home and the set-up doesnt want to boot (post code 00) Looks like I'm out. Quote
I.nfraR.ed Posted September 14, 2013 Author Posted September 14, 2013 Can I ask somebody with UP4 check what post code is displayed on the debug led when no cpu installed? Something failed last week and I thought it's the board, because then I tried with 5800K and it was switching off immediately (I think the PSU protection kicks off). So I bought another UP4, but when I start the board only 2 segments on the debug display flash for a blink of an eye and it turns off (the led). Board stays on, but does not post. It's the same with both cpus and without a cpu installed. I though if both cpus are dead it should display 00, no? It would be pity if the faulty board killed the other cpu too when I tried it I'm scared to try the dead board again, so I will just throw it, don't want to risk the PSU too. Quote
Oggy_Dz2 Posted September 14, 2013 Posted September 14, 2013 When our CPU died the motherboard didn't show anything, just turned itself off immediately, but an A10-5800K worked with the same motherboard. Quote
Massman Posted September 14, 2013 Posted September 14, 2013 00 on the UD7 here meant CPU dead. But, I also had the situation where after testing a working CPU, that afterwards the 00 would be gone with the "dead" CPU. I think 00 might also mean CPU not recognised (microcode issue) or so. Quote
The Stilt Posted September 14, 2013 Posted September 14, 2013 Can I ask somebody with UP4 check what post code is displayed on the debug led when no cpu installed?Something failed last week and I thought it's the board, because then I tried with 5800K and it was switching off immediately (I think the PSU protection kicks off). So I bought another UP4, but when I start the board only 2 segments on the debug display flash for a blink of an eye and it turns off (the led). Board stays on, but does not post. It's the same with both cpus and without a cpu installed. I though if both cpus are dead it should display 00, no? It would be pity if the faulty board killed the other cpu too when I tried it I'm scared to try the dead board again, so I will just throw it, don't want to risk the PSU too. When the CPU dies it usually shorts (either VDDCR or VDDNB). Unless the VRM CC protections acts fast enough usually the VRM burns too. In case of a UP4, the VRM CC protection is fast and usually saves the board. If you put a broken APU in the socket and try to start it, the Port 80 segment display flashes briefly and then turns black. Depending on how the APU is damaged, the board turns off immediately or continues running (segment still blank). The most common reasons for a APU to burn is a voltage spike (e.g a large voltage swing from low to high voltage) or simply too high voltage. This is the reason you want to have a smallest possible delta between the cool down (Slowmode) an the running voltage. It will hurt you temperatures, but it will save your APU. In case the VRM fails it usually kills the CPU in about 90% of cases too. And a broken APU can definitely kill a working board too. To check if the CPU core part of the APU (FM2 or FM2r2) is fine: Measure the resistance between the two pins (VDDCR & VSS). Anything under 25 ohms means the APU is burned. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.