Associate
- Joined
- 13 Jun 2012
- Posts
- 340
seems like the answer is wait!
1.2.0.3 Patch B being released.
USB issues should now be totally fixed.
That sounds awful and extremely frustrating. I'm glad you sorted it out in the end. Gigabyte have started providing checksums with the BIOS file so you can determine whether the file is corrupt, I think this would have prevented your problem. I can't understand why other manufacturers don't do this or provide a simple MD5 or SHA1/256 hash, the latter would also be a great idea from a security point of view.Thanks for that .... but it bricked my bios the version I downloaded from the MSI Global site and the file was actually funny, it stated the bios version and date correctly but when it got to the 50% area on the MSI flash tool in the bios it stated Unknown Unknown as some file name also I noticed funny enough the file when looking to pick it from the list it stated Nul Nul too as the date, where all other files before stated the details right, I have one usb stick with all the bios versions and this one from the global site screwed my bios to the point I had to switch to second working one and then try again to flash it, it seemed to flash ok but all the time CPU error and stuck at 00 on DR BIOS LED, anyways I got it working again, I went to the uk msi site and downloaded again and this file states everything correctly and worked when I accidentally flashed the working bios with it and had a massive panic attack that it was going to brick the working bios now, but it all worked ok and no unknow file name at the 50% area of the flash.
Now the fun began 1st bios was screwed and wouldn't even flash correctly when I used the second working bios to get to the flash tool and then flipped to the 1st bricked bios with CPU error, I let the tool flash it and noticed it took ages to flashing this time compared to the working bios, anyways it completed rebooted and I knew it wasnt going to work as the DR BIOS LED was still saying 00 and then I got cpu error on the OLED screen again and of course failed to post...
Now I got mad , got a jumper and stuck it on Jbat1 to clear the cmos as the button on the back with clear cmos wasn't doing it, walked away with it in for 5 mins , came back took a deep breath as I had this problem before when I got this board and the 5950x was not supported so took ages to get it to flash correctly for some weird reason and I just kept doing it before and worked with the same stick I knew that was formatted correctly and the file name MSI.ROM on it, I also did the clear cmos with the jumper and in the end it worked and when it did all I did before was go to the flash tool in the bios and flash the second not working bios and worked too, now this time it wouldn't work, in the end this is what worked in this order.
1. clear cmos with jumper, unplugged from mains. Remember to remove jumper before starting up again.
2. went to working bios and started the flash tool
3. in flash tool flipped the switch to none working bios
4. in flash tool used the new bios file with the name that came in the zip file and ran flash, it took a lot longer and said all ok in the end.
5. of course CPU error.
6. clear cmos with jumper again , 5 mins walked away with all unplugged from mains,
7. removed the jumper, started system up again .. cpu error
8. stuck the flash drive back in the flash port and clicked the flash update button on the back.
9. it updated the bios and restarted without error.
10.. it worked again...
Insane really. originally when I got the board I thought it was faulty but we ordered some at work and of course they all did the same thing all MSI boards from godlike to the cheap ones. I hope this helps some one , just keep trying and make sure the drive is formated in fat 32 and the file names MSI.ROM if using the button to flash it, when in bios flash tool use the original file name of the file.
grrr, nice day. DON'T USE THE FILE FROM THE MSI GLOBAL SITE, USE THE UK SITE.
Don't give up if you have the problem the BIOS will unbrick in the end, just sometimes have to try many times and the two ways they allow us the button and the tool in the bios if you can get to it with a working second bios.
I hope this update was worth it and lets see what it fixes and updates now, once I put the damn sli setup back together and sound card on the riser.
<mood
SO HEADS UP....BEFORE YOU FLASH THIS ... MAKE SURE TO CHECK THE FILE AND IF IT STATES UNKNOWN AT ANY POINT IN THE BIOS FLASH TOOL IN THE BIOS, WHEN YOU SELECT IT AND CHECK ITS DETAILS BELOW. IF ANYTHING SAYS UNKNOWN OR NUL ... DON'T RUN IT AND GET THE ONE FROM UK SITE .. THEN MAKE SURE SAME AGAIN NO ISSUES BEFORE YOU CLICK FLASH..
That sounds awful and extremely frustrating. I'm glad you sorted it out in the end. Gigabyte have started providing checksums with the BIOS file so you can determine whether the file is corrupt, I think this would have prevented your problem. I can't understand why other manufacturers don't do this or provide a simple MD5 or SHA1/256 hash, the latter would also be a great idea from a security point of view.
7C84v17 is working great for me.I wouldn't touch 7C84v17 or 7C84v16 for the X570 Tomahawk with someone elses 10,000ft barge pole. With my trusty kit of Klevv BoltX 3600MHz (part # KD4AGU880-36A180U) manually setting a 1T or 2T Command Rate with A-XMP enabled results in the system failing to POST. Only the [Auto] (GDM, basically) works. Not good, not good at all particularly as this kit is on the MSI memory QVL list.
I've one of these incoming for a build, x570 Tomahawk, 5800x, 2x8Gb sticks of Ballistix 3600 CL16. What's the recommended bios then?
7C84v17 is working great for me.
If anyone can test the below steps with firmware 7C84v17 it would be very useful and I can get MSI to look at the affected memory kits.
Load setup defaults > save and exit
Enter UEFI > load A-XMP profile > Manually change Command Rate to 1T or 2T (the bug should happen with both but if you want to test both that would be helpful info too)
If your system fails to POST, thats the Command Rate bug. Post here what memory you have along with a Thaiphoon Burner screenshot and I can pass the info on.
It's now been confirmed, the issue is an AGESA bug. Hopefully it'll be fixed in the next release.
What version of AGESA is the bios you get the bug on ?
Sorry for not getting back sooner.
Tested both 1T and 2T and posted/booted to windows fine.
RAM is 2 x
My basket at Overclockers UK:
Thaiphoon screenshot
Good kit that, I reviewed the 32GB kit a while back that did 3333MHz with some decent timings, bit below what I expected for Micron E-Die but pretty good all the same. You tried tightening timings up and seeing what your kit will clock to?