Tweet
Originally posted by obogobo
View Post
-
Since the agesa is released without even a generic changelog there's no way to know but around there are experimental bios for boards from others manufacturers with option to set the vddg voltage per ccd. -
Agreed, it's super annoying. That was the main reason why I switched back to W10 since fTPM is mandatory for W11. Turning it on causes the system to freeze/stutter for 1-2 seconds multiple times a day.Originally posted by MykelNeiD View PostComment
-
after cold boot issue today i switch back from f15a to f14c (agesa 1.2.03.c).
cold boot is no problem. i will try f15b.
and the cbr20 performance is also like before updated to agesa 1.2.0.5.
so i can contradict deskmodder, that the performance after a downgrade will be lower than before.Last edited by mgfirewater; 02-24-2022, 04:53 AM.Comment
-
Is it possible to downgrade from F15 to F13 on the b550i pro ax? I feel like F13 was the best agesa so far (1.2.0.3b)Comment
-
With QFLASH+ it might be possible. There is also a beta F16 that you should have spotted. For me F15 is satisfactory enough to wait for a future release that offers a genuine reason to update.Originally posted by baldersz View PostComment
-
If you are overclocking you'll want to set all of your clocks to stock as the first thing you do. It may well be something you are overclocking (like the fsb, for instance) is causing the problem.Originally posted by Zeko39 View Post
Been running fTPM with zero problems, ran it under Win10 for ~two years before I went to Win11, and I've run it under Win11 for the past six months. I run with both bios entries under fTPM enabled. Nary a single stutter, glad to say. Sounds very much like a hardware resources conflict with fTPM, as stutter stops when fTPM is disabled in the bios. The conflict isn't apparent until it's turned on, from what people say. If you are running any older expansion cards in your system, RAID cards, or something like a Creative Xfi sound card, you could try turning fTPM on in the bios, removing those cards, and booting into Windows to see if the stuttering stops. If it does, then you can put the cards back in, one at a time, until the stuttering starts again, and you will have found the problem. You may need to update the bios on the card, or replace it with a newer version.
Of course, it could be a software conflict with a device driver or a third-party application of some kind you are running--have to troubleshoot there, too. You could try booting into safe mode to see if the stuttering stops--if it does, then you've nailed down the issue to one of your device drivers. Good luck!Comment
-
tried F15a for B550 vison D-P, VDDG IOD bug here too. system not stable... and go back again to F12 and Agesa 1.0.2.3b from august 2021. seriously....Comment
-
Unsure if this is F36b issue on Aorus Master v1.2 board or not, but suddenly I had a weird SSD error in Windows 10, game stared completely stalling out.
The IO operation at logical block address 0x7c6c380 for Disk 1 (PDO name: \Device\0000004f) was retried.
The IO operation at logical block address 0x606618 for Disk 1 (PDO name: \Device\0000004f) was retried.
...
Different hex addresses, shutdown Windows 10, then it took a long time to boot into Windows 10, then powered it off, Windows failed to boot altogether, went into F8 recovery, hung, powered off, powered on. Went into Linux, was fine. Rebooted, Windows back into F8 Recovery for WIndows, recovered boot.
When I logged in I had a ton of disk notices.
Went into UEFI BIOS.
Things went back to normal on their own.. I'm not sure if the SSD (SATA connected on the hot swappable support on this case).
Really weird...the only more recent thing was Samsung Firmware, but those were NVMe not the SATA SSD devices....
Just reporting this incase any other others noticed this.
Comment
-
I tried reporting the VDDG bug to gigabyte multiple times and they keep saying they can't find the problem
and the ftpm bug is a known issueComment
-
Gigabyte Adds BIOS Support For Upcoming AMD Ryzen 7 5800X3D CPU on 500 & 400 AM4 Series Motherboards
Comment
-
Unsure if this is F36b issue on Aorus Master v1.2 board or not, but suddenly I had a weird SSD error in Windows 10, game stared completely stalling out.
The IO operation at logical block address 0x7c6c380 for Disk 1 (PDO name: \Device\0000004f) was retried.
The IO operation at logical block address 0x606618 for Disk 1 (PDO name: \Device\0000004f) was retried.
...
Different hex addresses, shutdown Windows 10, then it took a long time to boot into Windows 10, then powered it off, Windows failed to boot altogether, went into F8 recovery, hung, powered off, powered on. Went into Linux, was fine. Rebooted, Windows back into F8 Recovery for WIndows, recovered boot.
When I logged in I had a ton of disk notices.
Went into UEFI BIOS.
Things went back to normal on their own.. I'm not sure if the SSD (SATA connected on the hot swappable support on this case).
Really weird...the only more recent thing was Samsung Firmware, but those were NVMe not the SATA SSD devices....
Just reporting this incase any other others noticed this.Comment
-
esupport of gigabyte doesn't intresst in my feedback to f15a (agesa 1.2.0.6b). since i'm back to f14c every thing runs perfect.
did anybody known the vulnerabilities of agesa 1.2.03 which will fix in agesa 1.2.05 and higher?Comment
-
Same here the official answer I've got is "we cannot reproduce the bug"Originally posted by legitsu View PostComment
-
about ready to just order an asus tuf board and be done with itComment
-
Wow. Maybe they should help us find which option can control this voltage.Originally posted by lafonte View Post
Or maybe they show us real screenshot with vddg voltage above 1.0V (on AGESA 1.2.0.4 to 1.2.0.6b). zentimings?Comment
Comment