Maximus V Gene

[Janus67]

tried installing the ROG+ server/addin in the benching OS and it didn't make a difference. Only thing we didn't install was the full AISuite but I don't believe it works properly in my stripped OSes.

[Nico]

Originally Posted by Softex

Thanks but if I could do Rma I never ask here, unfortunate I bought it in another country because here costs higher.

Thanks anyway everyone.

Alex

I had exactly the same problem, but if I booted without a videocard installed it seemed to work. Hooked the iGPU up to HDMI today and it did indeed work fine, and after some trial and error I got it working on PCI-E now. Seems the likely answer was just to apply optimised settings, reboot, shutdown and add videocard.

Time will tell though

[Kaladryn]

Asus Maximus V Gene
Seasonic 650w gold
Gskill ripjaws 2133
Intel Ivy Bridge 3550
Seagate Barracuda
Asus AMD 7950

Hi guys, great forum here! I'm thinking this is the place where I might find some info on this issue I'm having, this has also been posted on the Asus forums, but I'm reposting here, I hope that is OK!

This is my 4th Asus build, I have always updated my bios, and never had a problem. I know that, technically, I should not update my bios without a good reason, however I was lead to believe (accurately I think) that a) the new bios improved stability, and b) the new bios might be needed for my Ivy Bridge support, and c) there are several other tweaks (some voltage related) that would be desirable to me. I was told at some lengh by Asus tech support that I should not have updated the bios, actually that is pretty much all he said to me, however I have to disagree, I SHOULD be able to update my bios on a modern motherboard without problems, I have probably done 100 bios updates in my life (almost exclusively on Asus boards) and have never had a single problem I could not recover from (same goes for several graphics card bios flashes).

So, disclaimer aside, here is what happened, first my motherboard passed the breadboard test perfectly. Assembled computer in case with all components. Booted to bios, perfect. Turned off computer, then:

1. Downloaded 0813 bios from Asus site.
2. Renamed file to M5G.CAP (manual that comes with motherboard said to use .ROM, but UPDATED manual from Asus website to use .CAP-the updated manual is correct)
3. Copied bios to USB 3.0 stick (formatted NTFS, which DOES work on the Maximus V, per the updated manual)
4. Followed the USB Bios Flashback proceedure (It seemed to work perfectly based on flashing lights both on the flashback button and on the USB stick matching perfectly video demonstrations of the flash.)
5. Tried to power on computer, power supply just clicks repeatedly, MB doesn't power up enough to get an error code. Error LED for CPU comes on momentarily.

I think the board is stuck in some kind of protection mode, overvolt protection maybe, or some kind of short protection. In every way it seems like a short, but it is not.

1. Power supply tested (multimeter) everything is perfect. (Seasonic Gold 650w)
2. CPU checks out, tested in another board. (Intel Ivy Bridge 3550)
3. Memory tested, working. (G.SKILL Ripjaws Z Series 2133)
4. MB passed breadboard test before bios updated, will not pass any sort of breadboarding after. MB breadboarded with only CPU, 12pin, and 8pin connnected.
5. MB doesn't POST, instantly shuts down after it gets power, cycles repeats every 5-7 seconds. No error code, only CPU_PWR light comes on momentarily at the start of each cycle.
6. Also, CPU reseated, pins examined very closely, everything looks perfect, plus it WAS working before bios update.

OK, here is the kicker, I RMAed the first board, got a second one, and repeated everything exactly the same, with the same result (I know about the Einstein quote...).

I tried using USB Bios Flashback to load the 602 bios, I seems to load perfectly from the flashing lights on both devices, however it does not fix my problem. I tried clearing the CMOS, both before and after loading the old bios. I went back and tried FAT32 format (bios still loads exactly the same it seems, per flashing indicator lights).

I understand now (slow learner) that I SHOULD NOT be using USB Bios Flashback, and instead I should have used Asus EZ Flash 2, however the mistake has been made. I am hoping all this info will be enough to find a solution without having to RMA another board. Also, I have a feeling other people will share my experience under similar conditions.

Finally (thanks for reading all this!!!), my theories: I think the USB 3.0 stick I used might cause a voltage issue and put the board into some kind of protection mode.

PS I tried flashing everything back with a USB 2.0 stick, no dice.

Thank you!

[Janus67]

Have you tried using ROGConnect to flash it?


And yes, use the EZFlash, it is excellent and easy, next time.

[Splave]

This board is such a dream to bench, I dont think I could go back to a board without the memory profiles.

[hokiealumnus]

Hear hear! ...and so MANY of them.

[Mikecdm]

Originally Posted by Splave

This board is such a dream to bench, I dont think I could go back to a board without the memory profiles.

Don't forget, you still have a date with MSI

[Splave]

I noticed while running superpi with turbo evo up (just stability testing) on ln2 and in the 5 seconds that it takes to run the bench if I set 6527mhz it will drop down to 6515mhz then 6475mhz then back up to 6527mhz in turbo evo window. Is anyone else experiencing this? Some sort of cpu throttle? CPU-z polling time is to slow to catch it but it shows in turbo evo. I will take a vid next time I bench

[Shammy]

Originally Posted by Splave

I noticed while running superpi with turbo evo up (just stability testing) on ln2 and in the 5 seconds that it takes to run the bench if I set 6527mhz it will drop down to 6515mhz then 6475mhz then back up to 6527mhz in turbo evo window. Is anyone else experiencing this? Some sort of cpu throttle? CPU-z polling time is to slow to catch it but it shows in turbo evo. I will take a vid next time I bench

nah it just uses a diff way to determine cpu freq such that when cpu is 'busy' it will think it to be slowerrf

[Splave]

Thanks! Was just thinking that that was probably it.