Reply to thread

[URL unfurl="true"]https://event.asrock.com/tsd.asp[/URL]


For those of you who have crashing/stutters/etc its best to be fully transparent with your issues, try to record the issue and submit video.


For the rest, the fact that AMD says its for the FULL 300 series of boards and has several improvements/fix's including USB3.0Connectivity/+Audio issues, PROPER Windows 11 support, fTPM stuttering issues and so many more that they (AMD) refuse to disclose, who knows what bugfix's/improvements/securityfix's are included


You can also include the same thing my customers have stated to me, EX: They HATE running a BETA or ALPHA BIOS to get proper function out of the system, Considering the official BIOS is only at 1.0.0.1, I myself had no end of buggy crash's for games, for myself and customers weird crashing with office programs, considering I had them purchase these, and the solution we have is being on the "Alpha" 3.60S BIOS with AGESA ComboAM4v2 1.0.0.2 that wasn't even released on the main site... Needless to say 2 of the business's I had buy them have already replaced them with non ASRock products.


There is plenty more, but those are some brief points, I said very early on in this thread, as long as they kept updating the BIOS to fix bugs and update AGESA I would buy into X300, needless to say, statement is still valid, I have no updates for my A300, so I have no X300.


I have also stopped recommending ASRock products (completely) to anyone, business or not.



Its super dumb that I cannot drop in a 4xxxG or 5xxxG processor because ASRock is being stupid, Product stack is already segmented, X300 = Overclocking, we get it, doesn't mean you have to totally ABANDON the A300 folks...


EDIT: Does it mean ASRock will take it seriously, probably not, but it will be on record and companys hate having a large flood of requests for something. As a simple example, the "Official" v3.70 release with this bugfix: "2. Follow AMD guide to support shared memory adjustment when Hyper-V is enabled" Myself and many others reported this and I also had to complain to AMD as well, and neither AMD nor ASRock wanted to do anything, I didn't even get a reply to my ticket that it was confirmed and then resolved