วีดีโอ

So as an update, I've been able to install a new vbios and I have the drivers from amd adrenaline. I'm still having terrible artifacting, it's like a 2 inch strip going from the top to bottom of my screen, then a 2 inch gap of clear viewing space where everything displays normal, then another 2 inches of artifacting and so on. I'm going to start "brute forcing" all of the available vbio's I can out of the 10 or so that came up for my gpu, hopefully it will work, I'm also going to try a different output and monitor aswell!

❤️

The GUI was deprecated and subsequently removed in version 5.x, so people on newer GPUs need to use the CLI. Plus, I've seen reports of some people having a lot of trouble with the GUI in older versions.

Which version of amdvbflash are you using?

Yeah I'd try to flash the stock VBIOS if you can find it, that would most likely resolve your issues. But I'd only do so if it's annoying you too much, since flashing the VBIOS does carry a little risk :)

You may need to specify local domain using .\<username> if you're connecting from windows, or from a Linux machine it'd be -o domain=. And it's possible you may need to restart the samba service if you haven't tried that already (systemctl restart smbd nmbd).

Depending on the version you're using, you can use the -f or -fp flags to try and force the flash. I think -f is force version 2.x and -fp for 3.x, but I could remember it wrong.

also i have on gpu-z the BIOS Version is Unknown

You're welcome! :D

It looks like you download the flatpaks for offline installation using the "create-usb" command: 1. configure the remote with a collection id: flatpak remote-modify --collection-id=org.flathub.Stable flathub 2. update the flatpak references: flatpak update 3. package up Firefox: flatpak create-usb /path/to/usb-drive/ org.mozilla.firefox 4. install with flatpak: flatpak install --sideload-repo=/path/to/usb-drive org.mozilla.firefox For other machines, you'd just need to move the USB drive to them and: 1. add flatpak remote: flatpak remote-add --if-not-exists flathub flathub.org/repo/flathub.flatpakrepo 2. add the collection id to flathub repo: flatpak remote-modify --collection-id=org.flathub.Stable flathub 3. install with sideloaded repo: flatpak install --sideload-repo=/path/to/usb-drive org.mozilla.firefox Let me know if this works! And the source I used for this: docs.flatpak.org/en/latest/usb-drives.html

It's possible that flashing the VBIOS could fix this, but it's hard to say exactly for sure. I'd say it's worth a shot though.

did you manage to fix it? I'm going through this exact same problem

@ i havent tried flashing the vbios ive tried some other things but nothing has totally stopped it ....its weird sometimes it does it multiple times in a row on multiple consecutive days and then it wont do it for weeks and i sorta forget about it....but it always comes back eventually

@@zacinnc78 Same here. I'd like to know what makes it exactly behave normally every now and then, but I couldn't narrow it down. Flashing the bios is the only thing I haven't tried yet

I'm glad it was helpful! :D

It's likely just the same command, but with " -fv" added at the end of the command, without the quotes of course. Let me know if that helps!

@BitGoblin I've tried it and it didn't work It just gives me a blank space that I can write in but it doesn't do anything, I waited for half an hour and nothing's changed

Does this vbios work? www.techpowerup.com/vgabios/261621/261621

@@BitGoblin That's exactly the bios I found on the card. I would like the original one. Let me explain, the card has frequencies by default that make it work stably. Primary Clock Speeds: Base clock Up to: 1875 MHz Game Clock Up To: 2250 MHz Boost clock Up to: 2655 MHz Someone or XFX itself has put out modified bios focusing on the build quality of the video card. My bios has these frequencies: Base clock Up to: 1720 MHz Game Clock Up To: 2250 MHz Boost clock Up to: 3000 MHz. When I use it with some applications that make intensive use of the boost clock, the card exceeds the temperature limit and the PC turns off. I would like to bring it back to the original and I need an AMDVBFlash / ATI ATIFlash compatible with my card and an original bios.

I found a couple other VBIOSes for your card. They look fairly similar, but I wonder if either of them is fixed or if your current one is corrupted somehow? Might be worth a shot www.techpowerup.com/vgabios/258606/258606 www.techpowerup.com/vgabios/270262/270262

That's normal, sudo usually hides all input to prevent someone looking over your shoulder to see how long your password is. If you type your password and hit enter it should still work

@ thank you

Is this using the copy of windows shipped with your laptop or have you reinstalled it at some point? I wonder if it's missing a driver for the chipset or something.

I'm glad you got it working! :D and I'll take a look at revisiting it. IIRC I brushed over the docker installation steps since the docker docs are pretty good, but I could've made that clearer :)

@@BitGoblin Thanks man. There were two issues i ran into with this tutorial. And the "sudu iftop" showed no stats of incomming or outgoing traffic. I don't know how to fix this. So i used "docker stats" did which generally showed me if it was working or not. I am also new in terms of dns/ip's etc so i had a bit of reading prior. But as soon as i understood that the LanCache had an ip, and that you had to insert this into the router settings things started rolling. Then changing the network settings on the client was a breeze. Last thing was i couldnt figure out how to save the .env file. You just said "save and exit" and i was stuck on this so long lol. There is also an issue that i don't fully understand yet. The speeds are really fast to begin with but over time they drop alot. From 800mbs to around 70mbs half way through a "re download" of a game. I dont have a second client pc to this on at the same time to see if the speeds also settle around there. But any data that is not grabbed from the internet a win in my book. :) Also what is the difference between Lancache monolithic and Lancache_dns Those are the two shown in the docker stats. :) I used your tutorial as a general method of pointing me in the right direction. Thanks for this!

My guess is possibly something to do with your SSD cache running out of space and it has to wait for writing to the slower part of the drive. Or it could be CPU-related, if it's only in some games that are compressed more. The lancache_monolithic has everything (I think including DNS?) built into the same image so it's an easier deployment, but makes it hard to scale up if you have lots of clients and need to scale or segment one of the components for whatever reason. lancache_dns is just the DNS service. If what you have is working I wouldn't sweat it too much lol. And it's no problem! :D

I think you are right. Thanks mate :)

What issue are you having? Is it failing during the flash, or is amdvbflash not seeing the card, or something else?

Wait I'm dumb, I missed the second bit 😂 I think there's a way to force it even with the mismatched ssid but I'll see what I can find

Thank you so much for the prompt response! I'm considering using an older version of amdvbflash like version 3.15 but I'm not so sure how well that'll work for 6000 series cards and almost afraid to force a flash 😅.

To further elaborate on the process of what happened, I used the latest 5.x version to do these: 1) I used the -i command to check my GPU number. 2) I saved my current BIOS in a backup like instructed. 3) I prompted the flash for the new, stock, BIOS aaaaand "ERROR: IFWi's SSID is not same. Failed to flash the VBIOS."

@johnymcmememan2151 you could try the older version, worst case that would probably just fail with an error (if it even detects the card) And yeah, forcing a flash is risky so I wouldn't recommend it unless you're desperate lol

Have you checked if HWiNFO can show your memory timings?

That's odd that GPU-Z isn't showing the memory timings, that certainly makes things a bit more difficult 😅 but let me see what I can find, I wonder if that card has something weird with their bioses or something

@@BitGoblin The bios shows an SSID of C812, the same bios from TechPowerup shows C810. Would it be safe to try and force the stock bios?

@billvarner6548 it's possible. I can't guarantee anything but it might be fine. Worst case you can probably flash it back. You might also be able to try an older version of amdvbflash. Some people have had luck using like 3.31 to get around the ssid mismatch on tlnewer cards

@@BitGoblin I found an unverified bios on techpowerup that actually worked. about to run some tests

@@BitGoblin I found an unverified vbios on techpowerup for the MX and it flashed without problems and the card seems more stable now in gaming and benching, just ran a 15 min. 3d adaptive test with OCCT. before I was getting 1.5 million errors, now I'm getting no errors.

It was a Corsair Vegeance LPX kit. Hopefully you are/were able to get your ram RMA'd!

Has anything changed? Like are you using a different USB port/controller, or were there any updates to Windows or OBS since the last time it worked? Usually for me when I get a black screen I either restart OBS or unplug and re-plug it back in and it works.

It’s the same USB port (granted it’s a laptop) I did have to buy a longer usb cable since before my tv was closer to my desk, both sides are USB 3.0 and I have tried other ports like one on my Port extender that is a USB 3.0 and still no dice..

It might be worth moving your laptop and/or Mirabox closer to the TV to use a shorter cable, to see if that's maybe the issue. Granted for 1080p60 it shouldn't be an issue, but my Logitech Brio was getting funky when I used a longer cable (15ft IIRC?) but was perfectly fine when it was on a 6ft cable.

@@BitGoblin I’ll have to try that!

Huh, that is frustrating! If you haven't yet tried another GPU in the slot, it's possible that maybe your x16 slot is borked.

@@BitGoblin tried 4 other GPUs in the rig, all worked just fine.. the 580 simply wont work in the X16... works in the X4 slot tho.. and it works in a threadripper x399-e mobo's x16 slot.. just no other rigs... its weird AF ... so im goign to leave it in the X399 and call it good. lol .. BUT this video DID show me how i can flash the easy way for gpu bios, so thank you much for that Sir ..

Yeah that really is weird! It could maybe be due to the motherboard's BIOS version acting weird for certain GPUs, but I've only seen that when installing like HBAs or NICs. Certainly weird either way. Sorry for the late response, but I'm glad the video helped and you're welcome :D

Have you tried with the CLI? The GUI can be flaky at times, though it has usually worked pretty well for me.

@@BitGoblin nah, my problem was that I had multiple drivers stacked and it didn't worked well. Just uninstalled them all and installed a fresh one. Still thank you for your help!

Oh yikes, that's definitely not good! But I'm glad you figured it out, and you're welcome! :D

Also, for those of you watching that can't find amdvbflashwin in the most recent version, delete that and download the same one in this video, version 3.31. It works just fine.

I'm surprised the older 3.x version worked. My understanding was that the RX 5000-series and newer cards needed the 5.x versions, which sadly only has the CLI Either way, I'm glad my video helped :D I hope your 6900 XT serves you well for many games to come!

Thanks for posting this warning! I wouldn't have expected ASUS (or any other brand) in particular to have trouble with flashing its VBIOS, but the results don't lie. I hope find a way to recover your Q BIOS if you ever need it!

i have the same card and i can't boot to the Performance bios, even though I haven't flashed it, that's why I was considering flashing it maybe I'll stop and stick to the Q bios but even then when I boot the PC when It's been off for hours I have to hold the power to turn it off then on again for it to boot normally

Don't worry, I'm good for that 😋

Yep! Using the integrated graphics on your CPU is perfectly fine :)

@ the bios was at its latest build. I just did some tuning and undervolting… stress testing didnt make it black screen yet. Maybe it was just badly tuned by radeon

@HarenunHoppus that definitely could be it! And good job getting your GPU to work :D

That sounds like the flash didn't work, unfortunately. You should try putting in another GPU (if you have one) to use for a display and either flash the old VBIOS or a different one to see if that helps.

I would lean towards maybe the motherboard's BIOS needs flashed. Or potentially the PCIe slot you're putting the card in is dead, if you have another card to try in it would be where I'd start.

I updated the BIOS to the latest version and tried the GTX 970 it worked . This problem still for rx 470 power cooler occurred. I noticed it on any device that has a UEFI system BIOS happen this problem .​@@BitGoblin

Hmm, that's a new one for me, and anything I'm finding online suggests problems the other way (it works in a UEFI board but not a legacy BIOS). Maybe try resetting the CMOS on your motherboard? It's possible there's a setting or something that's preventing it from working with the RX 470. This sounds like a fun problem to troubleshoot! :D

I did a bit more investigation, but the errors popped up even with stock settings (i.e. no DOCP profile for overclocking, nothing fancy on my CPU) and didn't occur with other sticks of RAM. IMO, that should be enough to submit for an RMA. Easiest way to check is to save your settings to a profile (if your motherboard supports it) and run everything stock to see if that helps. At least then you'll know if it's your config or the RAM itself

In theory the amdvbflash 5.0.567 version should support rx 7000 GPUs, though I don't have any on hand to test it. If that's the case then it's going to be the same commands as before.

@BitGoblin I've spend hours trying to make it work on different version and used your video, my knowledge, and chatGPT. Nothing as worked. To make things worse. Some command are slightly different/doesn't work on 5.0.567 (or maybe it's specific to 7000 cards) anyway, on a Qick 319 7800XT. And I wanted the Merc 319 BIOS for obvious reasons.

Huh, well I'm sorry to hear that. I was basing my response off of the release notes on the TechPowerUp site which says "Added support for flashing Navi 3x GPUs (Radeon RX 7900 XTX and RX 7900 XT)", which I'm now guessing means strictly those two GPUs :/ so sorry I couldn't be much more of a help. It really kinda sucks that amdvbflash feels like an afterthought by AMD... If you figure how to get your card flashed I'd be glad to know!

Is this happening when you're running the flash command, or somewhere else? And what version of amdvbflash did you use?

That's a good question... do you potentially have another system to test putting the card in to see if it shows up there? Or another PCIe slot on your motherboard?

Just to confirm: did you run the AMDVBFlashDriverInstaller.exe file?

Awesome! I'm glad I could help! :D

It's worth a shot if you're up for it, but if you don't need to flash it then I'd see if you can figure out why it's failing the test

​@@BitGoblin initially the flash failed and i try to flash it after 2 days it suddenly work.

In that case, you can install it like so: "sudo ubuntu-drivers install nvidia:550". You may need to change the version number depending on what's available in your ubuntu version.