Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

[hughythomas]

Hello everyone, I require assistance with a somewhat painful troubleshooting process.

We are experiencing what can be described as word-clock type noise issues.

Switching to 192kHz sample rate with-in a DAW (playback stopped) produces word-clock instability, represented by clock noises.

44.1kHz and 48kHz sample-rates seem perfectly fine.
96kHz sample-rate appears intermittent.

Equipment in use: UA Apollo X8P on Z490 platform. TB3 stock. (un-flashed)
In our case, This phenomenon exists with ProTools, Logic Pro X and Luna.

Are you having similar problems?
Information from community members with thunderbolt audio interfaces, posting their particular results when selecting various sample-rates, would be greatly appreciated.

@CaseySJ, this may be one to mandate Thunderbolt flashing.

Thank you,
Tony.

Hey Tony,

Sorry to hear you're having issues mate.

I too was having problems with my interface (RME FF802) similar to what you're describing. I work in Logic Pro X exclusively and was experiencing random glitches/dropouts (typical to the type of clocking issues you stated). I only work at 96kHz so can't speak for other sample rates at least on my system.

I fixed my issue by re-arranging the PCI-E cards internally and switching 'Bifurcation' in BIOS to 'Auto'. I also disabled all of the intel speedstep/thermal states nonsense as I want 5Ghz overclock all the time (system is watercooled).

My interface isn't thunderbolt but it might be worth a shot your end as you never know? I'm pretty certain it was the BIOS option that sorted mine out and it now runs flawlessly on large projects with loads of native & UAD-2 plugins on the go.

Good luck!

Best,

Tom

 

[one07]

@sambear, @Jno, @CaseySJ

I finally received an answer. I was sent a new (?) version of the MCU firmware (v1.0.15).

@CaseySJ @Ayvan (or others that successfully installed the other MCU update): Could you please describe me as detailed as possible how you proceeded with the firmware update? e.g. from which environment started, which processes/applications have you terminated before installing, did you use an external usb stick or the internal hard drive...

I will test it later. So there is hope that the boards don't have to be exchanged.

Update: The other version was 1.0.15, too. The new file from gigabyte has a suffix "20200620" though and some files were edited recently (that's at least what it looks like at first glance)

 

[tonben]

Hey Tony,

Sorry to hear you're having issues mate.

I too was having problems with my interface (RME FF802) similar to what you're describing. I work in Logic Pro X exclusively and was experiencing random glitches/dropouts (typical to the type of clocking issues you stated). I only work at 96kHz so can't speak for other sample rates at least on my system.

I fixed my issue by re-arranging the PCI-E cards internally and switching 'Bifurcation' in BIOS to 'Auto'. I also disabled all of the intel speedstep/thermal states nonsense as I want 5Ghz overclock all the time (system is watercooled).

My interface isn't thunderbolt but it might be worth a shot your end as you never know? I'm pretty certain it was the BIOS option that sorted mine out and it now runs flawlessly on large projects with loads of native & UAD-2 plugins on the go.

Good luck!

Best,

Tom

Thank you @hughythomas I have noted your response.
We are gathering all possible information.

 

[CaseySJ]

Hello everyone, I require assistance with a somewhat painful troubleshooting process.

We are experiencing what can be described as word-clock type noise issues.

Switching to 192kHz sample rate with-in a DAW (playback stopped) produces word-clock instability, represented by clock noises.

44.1kHz and 48kHz sample-rates seem perfectly fine.
96kHz sample-rate appears intermittent.

Equipment in use: UA Apollo X8P on Z490 platform. TB3 stock. (un-flashed)
In our case, This phenomenon exists with ProTools, Logic Pro X and Luna.

Are you having similar problems?
Information from community members with thunderbolt audio interfaces, posting their particular results when selecting various sample-rates, would be greatly appreciated.

@CaseySJ, this may be one to mandate Thunderbolt flashing.

Thank you,
Tony.

Please have a look at this post from @smashdownbabylon after firmware was flashed. It discusses sample rates.

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

@CaseySJ My mother board is gigabyte z390m gaming. Where would I found instruction to unlock MSR 0xE2? Or would it be same as yours? UPDATE: I found the below guide so will give it a try. https://www.tonymacx86.com/threads/gigabyte-z390-m-gaming-build-with-working-nvram.291193/ UPDATE2: I have...

www.tonymacx86.com

 

[CaseySJ]

@sambear, @Jno, @CaseySJ

I finally received an answer. I was sent a new (?) version of the MCU firmware (v1.0.15).

@CaseySJ @Ayvan (or others that successfully installed the other MCU update): Could you please describe me as detailed as possible how you proceeded with the firmware update? e.g. from which environment started, which processes/applications have you terminated before installing, did you use an external usb stick or the internal hard drive...

I will test it later. So there is hope that the boards don't have to be exchanged.

Update: The other version was 1.0.15, too. The new file from gigabyte has a suffix "20200620" though and some files were edited recently (that's at least what it looks like at first glance)

Thank you for following up on this important issue. I did not install the MCU firmware update because I saw the warnings.

I believe one should just quit all running applications in Windows. If RGB Fusion is running, we have to use Task Manager to manually kill the service. Just quitting the application is not enough. We can also uninstall RGB Fusion, reboot, then attempt to update MCU firmware.

 

[Ayvan]

@CaseySJ @Ayvan (or others that successfully installed the other MCU update): Could you please describe me as detailed as possible how you proceeded with the firmware update? e.g. from which environment started, which processes/applications have you terminated before installing, did you use an external usb stick or the internal hard drive...

I will test it later. So there is hope that the boards don't have to be exchanged.

Update: The other version was 1.0.15, too. The new file from gigabyte has a suffix "20200620" though and some files were edited recently (that's at least what it looks like at first glance)

I think, you receive new version of firmware update tool.

My setup when updates firmware:

• Windows 10 (last updates)
• Start update from SSD ("Downloads" folder)
• All software from tray turned off (incl. AMD Adrenalin, NZXT CAM etc.), all RGB software and services turned off, including services (some software has services in memory, in tray you can see only GUI application what you can use to configure service).
• No active antivirus (Windows Antivirus turned off too) and other "security" services.

One more thing! I had some issues with RGB DDR (soft, including Crucial MOD and RGB Fusion, can't see modules) when Thermaltake DPS G App was installed and iPSU Thermaltake Toughpower iRGB PLUS 1050W Platinum was connected to USB!
In my system USB from PSU disconnected, and all software for Thermaltake PSU was removed.

 

[sambear]

Hi All, I'm new to the forum and while I'm not specifically interested in the CustoMac aspect, I am very interested in the the failed MCU Firmware update with BIOS version F5a on the Z490 VISION D (rev. 1.x) motherboard and it seems @CaseySJ @sambear @one07 are the only one's talking about it. I too had the same issue and also raised a ticket with gigabyte. I was hoping you may have had a different response. I got a response from gigabyte today saying I need to RMA the motherboard which is the last thing I want to do. Any help would be appreciated. It seems the update seriously wrecked RGB... while I also can't run Fusion 2.0 I also have a bunch of stuff missing in Corsair iCUE, one of my DIMM's has disappeared and I no longer have any control over it nor any readings from it in iCUE. Your welcome to stop reading here, but if you want the full run down on what i did and or the issues I have, please read on which is a copy of what I send to gigabyte which got the response RMA (and many thanks to anyone who can provide any info) :
Updated to BIOS to F5a and as per instructions then updated MCU firmware with the mb_utility_mcu-firmware_1.0.15.zip provided on the support page for the Z490 VISION D (rev. 1.x). The first attempt failed with a unable to delete error message (it only appeared for a second and I don't know the full details of the error message). Subsequent attempts to install the MCU Firmware result in a Locked! Chipid mismatch! Error message and does not allow update. Following the failed update, RGB Fusion 2.0 no longer works (any change in the software has no effect) and Corsair iCUE can no longer see all four DIMMs. 3 DIMMs appear okay but the fourth has no RGB control and does not register in the iCUE software and cannot be controlled. DDR4_B2 is the affected slot. Fixes attempted :
Re-Installing RGB Fusion 2.0 - Did not Fix the Issues
Re-Installing Coarsair iCUE - Did not Fix the Issues
Re-Installing Windows - Did not Fix the Issues
Re-installing all drivers on a fresh Windows install - Did not Fix the Issues
Reverting to BIOS version F2 - Did not Fix the Issues
Reverting to BIOS version F3 - Did not Fix the Issues
Reinstalling BIOS version F5a - Did not Fix the Issues
Repeated re-install attempts after each of the above with MCU Firmware results in a Locked! Chipid mismatch!
Re-Installing the Corsair Dominator RGB 32GB (4x8GB) 3200MHz CL16 DDR4 DIMMs in a different order proved that it is not an issue with the DIMMs themselves, any memory chip installed in DDR4_B2 loses RGB control, putting that same chip an any of the other 3 slots and RGB control is restored. BIOS and Windows still registers all 32 GB (all four slots) so it appears only RGB control and temperature readings are affected. Following all testing I can only conclude that mb_utility_mcu-firmware_1.0.15 is broken. Is there any way to roll this back to the previous version? The previous version was working flawlessly. Given the issues with Locked! Chipid mismatch we would need a way to forcibly install the previous version to correct the issues.

@sambear, @Jno, @CaseySJ

I finally received an answer. I was sent a new (?) version of the MCU firmware (v1.0.15).

@CaseySJ @Ayvan (or others that successfully installed the other MCU update): Could you please describe me as detailed as possible how you proceeded with the firmware update? e.g. from which environment started, which processes/applications have you terminated before installing, did you use an external usb stick or the internal hard drive...

I will test it later. So there is hope that the boards don't have to be exchanged.

Update: The other version was 1.0.15, too. The new file from gigabyte has a suffix "20200620" though and some files were edited recently (that's at least what it looks like at first glance)

@Jno @CaseySJ @one07
I got email replied with gigabyte esupport last weekend,so I brought visiond to gigabyte repairing service center in my city today，they try to reverting to f4 ,f3 bios / install fresh window in empty ssd/uninstall rgb fusion / all failed, and I was waiting for 4hours with no help...so I retured the mother board for exchange the new board.
finally I have to wait 2 weeks for new mother board.

 

[ssijak]

OK, I got it installed and running, everything seems to be running fine except the lan connections. I am still waiting for my fenvi t919 from China and do not have alternative here in my country except maybe tplink archer t9e (but it says atheros chip on the spec). So I am stuck with lan.

Both lan ports kind of work, but the latency is between dropping packets randomly and 2seconds, sometimes working ok for 1-2mins in between. Speed is also much slower than what I have on the wan side. All other devices on the network work fine. Somebody else encountered this problem?

 

[mickelsn]

Hello @mickelsn, let's get you some answers inline:

M2P_SB shares bandwidth with the bottom long slot. Normally that slot operates at x4 (4 PCIe lanes) and M2M_SB also operates at x4. But when both M2P_SB and the bottom long slot are occupied, then each operates at x2 (half the bandwidth).

Copy that and thanks...I don't believe I have any use for that slot, certainly right now, since the WiFi card will use the x1 slot and I still have the x8 slot open after using the x16 for video. Really appreciate your quick-turn response -- here's hoping my power supply shows up on time tomorrow!

 

[CaseySJ]

@Jno @CaseySJ @one07
I got email replied with gigabyte esupport last weekend,so I brought visiond to gigabyte repairing service center in my city today，they try to reverting to f4 ,f3 bios / install fresh window in empty ssd/uninstall rgb fusion / all failed, and I was waiting for 4hours with no help...so I retured the mother board for exchange the new board.
finally I have to wait 2 weeks for new mother board.

Sorry to hear that, but glad you're getting a replacement board. I don't think I will update MCU for a very long time...