have a response from a person, where the sound works again. I'm not home until the weekend, to test if it works. he wrote: Hello Tauro,
even the gigabyte support was overwhelmed with my request and must first in Taiwan request. Even those had no answer and then the support staff member and I took some time to fiddle around. End of the song was an update of the chipsets. Try out the following:
If the problem persists then run the other exe. Thereafter, the calculator restarts by itself, do not be scared. After the restart check again if the sound goes.
If the problem persists, contact me again. Have a last option but I have to upload somewhere first.
Right now I'm Offline I have made 44 posts
I joined April 2017
I've received 1 like
My gender is Male
I currently have no messenger contact information filled out.
I currently have no social network information filled out.
Well.. that german guy I contacted write me back almost the same thing:
"Hi there,
Well the german support seems to be a little better then. Well i spend some time with them on the phone and they even had to ask the engeniers in Taiwan becuse of the problem. At the end and after a very long telephonecall we had my solution.
Try this:
Download this file download.gigabyte.eu/FileList...B19.0517.1.zip ans start the ECFwUpdate.exe. Restart the system directly. After the resatrt the EXE will automaticly start. Check the sound after that.
If this does not help:
Restart again, start the IFU_XE32_v1310.exe in the Zip you downloaded and flash. The System starts automaticly new, dont be suprised. After restart check the sound.
If even this doenst help (like in my case):
Write me back, i'll have to upload a zip with an other ROM for the mainboard that worked for me
Cheers Stephan"
But, this file is the same as the one on gigabyte motherboard web site, the same file that made my sound stop working. Since I have already fixed it by using the firmware that I wrote some posts back, I'll ask for his other file just for comparing.
Right now I'm Offline I have made 1,611 posts
I joined January 2017
I've received 217 likes
My gender is Other / Decline to State
I currently have no messenger contact information filled out.
I currently have no social network information filled out.
You can also try our discord if you need help. Link at the bottom of my signature.
Sorry about my lack of involvement in this thread, I was on vacation for the last week. I have been playing around with some different things with the firmware tonight trying to make some sense of what is going on with the sound. So far I can confirm flashing back with the version that thiih posted will get the sound working again. The old version that gets the sound working only has 1 .bin file in it, but the new version has 6, and none of them are the working version and I have no clue what the difference is between them. What I am describing below is basically blindly flashing bin files without knowing what they are meant for in hopes of figuring something out. All of this is done with the bios forced into single bios mode on my x470 gaming 7 because it would occasionally kick into the backup bios after flashing with the firmware tool. In single bios mode this is obviously not an issue. To start with I will give my directions on how to flash the old version. Here are the directions that I did to get it working again.
Obviously download the file, and then extract it. After its extracted open the folder it was extracted to and launch the IFU_XE32_v1090.exe. Click on the Load*.bin button. select the V678.bin file. After that click the flash button. I dialog box will open with a poorly translated version of save your work and close running programs before you click ok. Save anything you might be doing before clicking the OK button. This will start the flash which should only take a few seconds. after you run the .exe just leave the system alone for a few minutes and it should restart on its own, but it doesnt always seem to restart itself. I have flashed this probably 12 times and sometimes it restarts within a few seconds sometimes it takes 2 minutes. Sometimes it just doesnt seem to want to restart. if it does not restart on its own after about 1-2 minutes click on the setting tab, then click the checkbox for check ec f/w version which brings up some extra options and then continue to wait. For some reason doing this and and then just waiting maybe 10-30 seconds it triggered a reset for me. I was playing with some other things in the menus like reading the .bin and .rom versions so this could have also been what triggered it. Once if figure out which one it was I will update this post.
After that I edited the the .ini file for the ecfw tool to be able to flash each .bin file individually rather than have it do so automatically when you launch the ifu_xe32_v1310.exe. I started by flashing a random .bin just to see if I lost sound after. I chose v623 and after a restart there was no sound. At this point I copied v678 from the version thiih posted to the folder with the ecfw update and manually flashed it from there to make sure whether or not the issue might be with either the firmware tool or possibly a setting in the .ini but after flashing it again my sound was back which rules out the tool itself.
Now that I was back on the version with working sound I went back to flashing other .bin files to see if any of them would cause me to lose sound. So far the only version that I have found that doesn't cause a loss of sound is the old v678, and the v810. The v810 would only work after having already flashed back to v678. If I flashed it after a version that caused a loss of sound then the sound still didn't work. V810 is slightly quieter than v678, but only just a bit quieter. I confirmed this by swapping between the optical output from the motherboard and the analog (green) with both hooked to my receiver at the same time. Optical is always a bit louder on my setup, but the v810 was maybe the equivalent of having windows volume on 85 or 90 when it was at 100. The other issue with v810 is that it causes the bios led code to always display AA so at this point I would not advise flashing it. I may play around with this some more tonight and see if I can continually reproduce any of this or find some combination that works properly.
Edit, after testing again v684 also has working sound if flashed after v678. However it also has the always stuck on AA led issue. I am going to try and clear the cmos and see if that makes a difference.
Edit 2. After clearing the cmos with either v810 or v684 the led code is stuck on 00. the system will still boot and operate normally but as stated earlier I don't suggest anyone run either of these versions. Also after 2 reboots v684 lost all sound from the green port and I was unable to get it back with the normal power down method. currently back on v678 and plan to stay there for the time being.
My Signature... I do not work for gigabyte. My advice and opinions are my own.
Right now I'm Offline I have made 40 posts
I joined December 2016
I've received 2 likes
My gender is Male
I currently have no messenger contact information filled out.
I currently have no social network information filled out.
Okay so what about in my case, I ran the tool after already updating to F40 bios. It just rebooted my system and produced a read file in the folder that I unzipped the tool too, which said "pass". The EC version in msinfo32 is 255.255. I also do not have any problems with my onboard sound which I tested, I actually use Sound Blaster.
My Signature... Gigabyte X570 Master- AMD 3900X MSI GTX 1080 Gaming X 8G -32GB GSkill Ripjaws Sound Blaster AE-5 Crucial MX500 1TB SSD EVGA Supernova G3 Gold 1000 Watt Corsair 780T Graphite series case
Right now I'm Offline I have made 1,611 posts
I joined January 2017
I've received 217 likes
My gender is Other / Decline to State
I currently have no messenger contact information filled out.
I currently have no social network information filled out.
You can also try our discord if you need help. Link at the bottom of my signature.
was your onboard disabled at the time that you flashed since you use a sound blaster? any chance you are on a rev 1.1 board? The rev 1.1 had some changes to the onboard sound.
I was also already on f40 when I ran the firmware tool and instantly lost sound.
My Signature... I do not work for gigabyte. My advice and opinions are my own.
was your onboard disabled at the time that you flashed since you use a sound blaster? any chance you are on a rev 1.1 board? The rev 1.1 had some changes to the onboard sound.
I was also already on f40 when I ran the firmware tool and instantly lost sound.
" was your onboard disabled at the time that you flashed since you use a sound blaster?"
Yes
I got a eVGA Nu Audio two day before saw this update at website.
...produced a read file in the folder that I unzipped the tool too, which said "pass"...
I get a file said "pass" too, but my sound stopped working, as well as many other users here (and that german guy I said previously).
The EC version in msinfo32 is 255.255.
This means nothing to me. On my board, msinfo gives me 255.255, but my Samsung laptop, and 2 of my working computers at office (i5-2xxx with a generic MB, each one different from another), these 3 different computers gives me 255.255 on msinfo32 too, so..
Sorry about my lack of involvement in this thread, I was on vacation for the last week. I have been playing around with some different things with the firmware tonight trying to make some sense of what is going on with the sound. So far I can confirm flashing back with the version that thiih posted will get the sound working again. The old version that gets the sound working only has 1 .bin file in it, but the new version has 6, and none of them are the working version and I have no clue what the difference is between them. What I am describing below is basically blindly flashing bin files without knowing what they are meant for in hopes of figuring something out. All of this is done with the bios forced into single bios mode on my x470 gaming 7 because it would occasionally kick into the backup bios after flashing with the firmware tool. In single bios mode this is obviously not an issue. To start with I will give my directions on how to flash the old version. Here are the directions that I did to get it working again.
Obviously download the file, and then extract it. After its extracted open the folder it was extracted to and launch the IFU_XE32_v1090.exe. Click on the Load*.bin button. select the V678.bin file. After that click the flash button. I dialog box will open with a poorly translated version of save your work and close running programs before you click ok. Save anything you might be doing before clicking the OK button. This will start the flash which should only take a few seconds. after you run the .exe just leave the system alone for a few minutes and it should restart on its own, but it doesnt always seem to restart itself. I have flashed this probably 12 times and sometimes it restarts within a few seconds sometimes it takes 2 minutes. Sometimes it just doesnt seem to want to restart. if it does not restart on its own after about 1-2 minutes click on the setting tab, then click the checkbox for check ec f/w version which brings up some extra options and then continue to wait. For some reason doing this and and then just waiting maybe 10-30 seconds it triggered a reset for me. I was playing with some other things in the menus like reading the .bin and .rom versions so this could have also been what triggered it. Once if figure out which one it was I will update this post.
After that I edited the the .ini file for the ecfw tool to be able to flash each .bin file individually rather than have it do so automatically when you launch the ifu_xe32_v1310.exe. I started by flashing a random .bin just to see if I lost sound after. I chose v623 and after a restart there was no sound. At this point I copied v678 from the version thiih posted to the folder with the ecfw update and manually flashed it from there to make sure whether or not the issue might be with either the firmware tool or possibly a setting in the .ini but after flashing it again my sound was back which rules out the tool itself.
Now that I was back on the version with working sound I went back to flashing other .bin files to see if any of them would cause me to lose sound. So far the only version that I have found that doesn't cause a loss of sound is the old v678, and the v810. The v810 would only work after having already flashed back to v678. If I flashed it after a version that caused a loss of sound then the sound still didn't work. V810 is slightly quieter than v678, but only just a bit quieter. I confirmed this by swapping between the optical output from the motherboard and the analog (green) with both hooked to my receiver at the same time. Optical is always a bit louder on my setup, but the v810 was maybe the equivalent of having windows volume on 85 or 90 when it was at 100. The other issue with v810 is that it causes the bios led code to always display AA so at this point I would not advise flashing it. I may play around with this some more tonight and see if I can continually reproduce any of this or find some combination that works properly.
Edit, after testing again v684 also has working sound if flashed after v678. However it also has the always stuck on AA led issue. I am going to try and clear the cmos and see if that makes a difference.
Edit 2. After clearing the cmos with either v810 or v684 the led code is stuck on 00. the system will still boot and operate normally but as stated earlier I don't suggest anyone run either of these versions. Also after 2 reboots v684 lost all sound from the green port and I was unable to get it back with the normal power down method. currently back on v678 and plan to stay there for the time being.
well, I did some similar tests like you did, but not as thorough as yours and the only way to get my sound back again was with that IFU_XE32_v1090.exe file and V678.bin and after that I stopped messing up with these firmware. I'm on 41a BIOS, sometimes my led stuck at AA and sometimes at 00 after a boot, but nothing seems to change.
After using IFU_XE32_v1090.exe with V678.bin and get my sound working again, I tried to update Firmware with the one on their website and I get the message that I dont need to update the firmware.
Right now I'm Offline I have made 1,611 posts
I joined January 2017
I've received 217 likes
My gender is Other / Decline to State
I currently have no messenger contact information filled out.
I currently have no social network information filled out.
You can also try our discord if you need help. Link at the bottom of my signature.
You can get the ifu_xe32 to read which version of the .bin is on your system currently by disabling autoflash in the ini (change 1 to 0) then click on settings and get rom. but when you read the rom number the system will restart in after about 5 seconds so you have to be fast with a picture or a screenshot.
My Signature... I do not work for gigabyte. My advice and opinions are my own.
You can get the ifu_xe32 to read which version of the .bin is on your system currently by disabling autoflash in the ini (change 1 to 0) then click on settings and get rom. but when you read the rom number the system will restart in after about 5 seconds so you have to be fast with a picture or a screenshot.
Okay so which version is it supposed to be, or which bin file do you use to avoid this 4 dimm compatibility error with 3rd gen cpu's?
My Signature... Gigabyte X570 Master- AMD 3900X MSI GTX 1080 Gaming X 8G -32GB GSkill Ripjaws Sound Blaster AE-5 Crucial MX500 1TB SSD EVGA Supernova G3 Gold 1000 Watt Corsair 780T Graphite series case
Right now I'm Offline I have made 1,611 posts
I joined January 2017
I've received 217 likes
My gender is Other / Decline to State
I currently have no messenger contact information filled out.
I currently have no social network information filled out.
You can also try our discord if you need help. Link at the bottom of my signature.
The v678 which is the old one that has functional sound is the one from my screenshot. I don't have any screenshots from the other versions, but I can get a screenshot of the one from the broken version from the ecfw patch if anybody wants it. It will be several hours before I have time to mess around with it any more today.
My Signature... I do not work for gigabyte. My advice and opinions are my own.
rgarrison wrote: Sept 14, 2021 22:20:10 GMT -8 When you go to BIOS, does it show any media connected at all? Try and plug USB drives in, SD cards, whatever you can, and see if the BIOS can recognize any device. If it can, then try and get a bootable image on that device.
kshipper wrote: Sept 14, 2021 17:38:33 GMT -8 You could make a bootable USB key with Windows on it..just Google Windows Media Creator
scooterdooder wrote: Sept 13, 2021 15:33:37 GMT -8 Be tried to start the pc up with another hdd and it won’t boot either goes straight to bios but I am able to see it, tells me no bootable device
kshipper wrote: Sept 13, 2021 8:18:19 GMT -8 Sounds like a failed HDD....
scooterdooder wrote: Sept 12, 2021 17:51:46 GMT -8 hwving trouble getting into Windows I have a z97-hd3, I’m getting no bootable device detected. Reset the cmos battery on mobo, checked all SATA ports and tested another hdd still no boot
scooterdooder wrote: Sept 12, 2021 17:50:25 GMT -8 Hey having issues booting into windows I have z97-hd3 mobo. I’m getting no bootable device tetected
bamainark wrote: Sept 11, 2021 8:18:04 GMT -8 @starfighter......what motherboard/cpu are you using? If it's a later model TPM support will probably be built in. A TPM module itself is a separate option you must purchase yourself. Most motherboards also has a TPM header for this TPM module.
starfighterj wrote: Sept 10, 2021 7:28:36 GMT -8 What is Gigabyte going to do about windows 11 TPM 2.0 Support where is this Module and does it even work? GC-TPM2.0
kshipper wrote: Sept 9, 2021 21:13:34 GMT -8 gearjamer: Does holding down the shift button and clicking restart still bring you to the Troubleshoot menu like it did in Win10? When I used UEFI I could dig through the options there and boot directly into BIOS from there*
gearjamer wrote: Sept 9, 2021 12:30:14 GMT -8 hello can someone help me i just updated to windows 11 i have the z390 motherboard and after i turned off csm and turn on secure boot and turned on ptt i was able to install windows 11 but i cant get back in the biso anymore no matter what buttons
bamainark wrote: Sept 8, 2021 7:24:46 GMT -8 ehs83....best place to look is at TechPowerUP. They have quite the collection of VGA Bioses.
ehs83 wrote: Sept 7, 2021 9:12:50 GMT -8 Hello guys I need a default bios for 2080 super gaming OC Rev 2.0 . Can someone help me please ?
shakilurahmed wrote: Sept 5, 2021 8:19:18 GMT -8 Hi everyone! I have a Gigabyte GA-H110M-S2PH with 2 DDR4 sticks. first one is 2133 MHz and another one is 2400 MHz. when I insert 2 RAM together. My PC doesn't run when I insert. I tried so many ways but there is no solution I found. As I got to know, I
s2h wrote: Sept 5, 2021 8:01:29 GMT -8 MBIST crashes the notherboard on Picasso APU !
kshipper wrote: Sept 4, 2021 23:15:05 GMT -8 phoenix ...the underscore type slash is the detection phase of the board.
phoenix wrote: Sept 4, 2021 14:38:54 GMT -8 Anyone know why brand new Gigabyte boot comes up with a _ before the BIOS screen please. It is B560 Aurous Pro Ax. Thank you.
greggg wrote: Sept 3, 2021 8:29:56 GMT -8 About X470s 5 pin wrgb header. I can just snip off the 'w' pin or use 5 Pin Splitter Cable 1 To 2/3/4 Female Connector Extend For 5050 LED RGBW RGBWW combined with 4 pin male adapter.
kshipper wrote: Aug 29, 2021 22:43:00 GMT -8 Glad you got it sorted out danb62 =)
danb62 wrote: Aug 29, 2021 13:35:16 GMT -8 Case solved, thanks kshipper. So bad this issue is so poorly documented. That Q-flash button works like a charm.
