Are Bristol Ridge processors connected to A320M motherboards at your end?
Are Bristol Ridge processors connected to A320M motherboards at your end?
Hello AMD enthusiasts, are there any users experiencing problems with your build? You're using an AMD A10 9700 paired with a320-mh motherboards, specifically the Bristol Ridge line (A12-9800, A12-9800E, etc.), and wondering if it can work with an AM4 socket board. I own three new A10-9700 units with Biostar A320M-H and A32ES715 BIOS. The motherboard listings claim compatibility, but I've encountered booting difficulties with Windows 7/10 and PrimeOS across all three boards. After trying the processor on another A320M motherboard, the issue persists. Interestingly, when swapping to a different A320M board and using an Athlon 200GE processor, everything functions correctly. This suggests a possible compatibility problem rather than a hardware defect, especially since all three processors behave similarly even on different platforms. It seems unlikely that three identical units would share the same defect unless it's a recent issue with the distributor. If you have a working processor and motherboard combination that works, please share the model details. Your insights would be greatly appreciated. Thank you!
These are five-year-old APU models. If the A320 boards got a new BIOS update, it probably removed support for Bristol Ridge but that was mentioned in the BIOS description. For example, with the Biostar board you referenced, this has been a recognized issue for some time. It seems the board ended up getting Ryzen 5000 support, which caused them to stop supporting older chips.
Yes, thanks for your feedback. Hell, i think asking for feedback for other users might not be helpful in my case. I do suspect it is as you guys said, to support newer processors it means a limit to the bios chip can support on old processors due to the 32mb limit or somewhat like that. Why am I still in circles is because why BioStar put in their website its supported under the default stock bios patch A32ES715.BSS but this made it proof that it is not compatible anymore. The distributor does not give right-away my right to return for warranty or atleast swap-upgrade the processor if they themselves sold me these as board-procie bundle. I gave that proof and explanation and they are not yet willing to take action. Thanks for the suggestions,buddy.
If it's due to a BIOS chip capacity limitation there isn't anything any of us can do about it. I do know that chip should be supported but at the same time, occasionally they will drop support for an older one to include support for a newer chip, that too is out of our hands and you'd have to run an older BIOS version to regain support for older chips. That's what I had to do with a certain 775 board I had, to run older chips I had to use an older BIOS, to run newer 775 chips I had to use a newer version. Drove me crazy trying different chips until I finally figured that out.
Unfortunately, I used the outdated BIOS version and the workaround didn't help. The BIOS version shown on the support page doesn't appear to work with the processor anymore. I only noticed this because the same 3 identical processors have the same problem even on different motherboards. This is frustrating, and I haven't received any response from the distributor. I requested a return, but they seem unwilling to share more details.
I would reach out to Biostar's support team directly to inquire about the issue, describing the problem and seeking their guidance. I expect they will provide at least some information, even if it's not favorable. By this stage, I don't think further action is advisable.
Yes, you're correct. I'm using the A32ES715.BSS, the earliest model available for the unit. It shows up in the BIOS, but I'm having trouble booting any operating system. After isolating all components, the problem seems to be with the processor itself. I switched to an Athlon 200ge board and it worked. It looks like the support for Bristol bridge processors has been completely removed. I suspect the distributor didn't realize that, and it's frustrating because they don't seem to care. I need to explain this to them, but they just shrug it off.