New bios (5.6) issues Fatal1ty AB350 ITX w/2200g

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I recently updated to the new bios (5.6) on my Fatal1ty AB350 mini-ITX motherboard. I have a 2200g in it, and now when I go to change the frame buffer size from the default 2GB to any other value, it does not get saved.

I have tried changing it down to 64MB and up to 4GB, 

UMA_forces > UMA_specified > frame buffer

I go to save changes and exit, and when I come back into bios, it is set back too Auto.

Any ideas? I left the Legacy/non-legacy/hybrid setting on Auto since I am not too familiar with that. All other changes get saved (XMP settings, CPU OC, GPU OC, fan control, etc.).

Anyone else seeing this issue with their 2200g/2400g with the new bios?

Backstory:
I was trying to upgrade my ram from 8 to 16GB, but one of the sticks was bad and cause game crashes and has a bad address in memtest86, so I have to exchange them. Now with the 8GB back in the PC, I don't want it to be stuck at 2GB allotted to vram. This happened with both sets of ram, so it is a bios issue and not a ram issue. And even when I put 16GB back in when I get the replacement ram, I want to set it to 4GB for vram to avoid the annoying low vram messages in game.

I was not having this issue on 5.3 or whatever was the last bios release.

Thanks!

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
FireMrshlBill Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 29 Apr 2019 Status: Offline Points: 6	Post Options Post Reply Quote FireMrshlBill Report Post Thanks(0) Quote Reply Topic: New bios (5.6) issues Fatal1ty AB350 ITX w/2200g Posted: 01 May 2019 at 10:43am
	I recently updated to the new bios (5.6) on my Fatal1ty AB350 mini-ITX motherboard. I have a 2200g in it, and now when I go to change the frame buffer size from the default 2GB to any other value, it does not get saved. I have tried changing it down to 64MB and up to 4GB, UMA_forces > UMA_specified > frame buffer I go to save changes and exit, and when I come back into bios, it is set back too Auto. Any ideas? I left the Legacy/non-legacy/hybrid setting on Auto since I am not too familiar with that. All other changes get saved (XMP settings, CPU OC, GPU OC, fan control, etc.). Anyone else seeing this issue with their 2200g/2400g with the new bios? Backstory: I was trying to upgrade my ram from 8 to 16GB, but one of the sticks was bad and cause game crashes and has a bad address in memtest86, so I have to exchange them. Now with the 8GB back in the PC, I don't want it to be stuck at 2GB allotted to vram. This happened with both sets of ram, so it is a bios issue and not a ram issue. And even when I put 16GB back in when I get the replacement ram, I want to set it to 4GB for vram to avoid the annoying low vram messages in game. I was not having this issue on 5.3 or whatever was the last bios release. Thanks!

FireMrshlBill Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 29 Apr 2019 Status: Offline Points: 6	Post Options Post Reply Quote FireMrshlBill Report Post Thanks(0) Quote Reply Posted: 02 May 2019 at 11:31pm
	Reflashed 5.60 again in case there was an issue during the previous flash. Still the same issue. It is really annoying. I emailed tech support and they just sent some nonsense about how the frame buffer doesn't actually change the 2GB of memory dedicated to the gpu in windows (which counters my previous experience in 5.30 and earlier, and that of everyone on various forums, youtube, etc. that build little 2200g gaming rigs). And completely ignored whether this was a bug in the 5.60 bios or an issue with my board that magically started only after updating to 5.60. Swapped 16gb of ram back in, so losing that 2gb isn't a big deal, however, not being able to save a setting is a pretty large bug. Will just keep an eye out on the next bios and hopefully they fix it in that release. Since I am not getting a response on here or to my reply email with tech support.