[BUG REPORT] A320m NB frequency bug on newest BIOS

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

   Hi,

There is a bug in newest BIOS (v3.7) for A320m HDV R4.0,
which the NB frequency only becomes 1/2 of Memory frequency.

For example,
If I set my RAM to 3200Mhz (1600Mhz DDR), the NB frequency becomes 800Mhz instead of 1600Mhz.

I was able to solve this by rolling back the BIOS to v 3.3.

This is reported by numerous users on Korean hardware forums, which cause very high memory latency. (Because the NB freq is half of what it should be)
Below are the posts of those reports.

https://quasarzone.co.kr/bbs/board.php?bo_table=qf_overclocking&wr_id=36046
https://quasarzone.co.kr/bbs/board.php?bo_table=qf_hwjoin&wr_id=308827

This problem also happens for A320m HDV R3.0 too,
and also can be solved by rolling back the BIOS.

Can you please update the BIOS with this bug fixed with the newest AGESA?

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
myblues Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 27 Feb 2020 Location: Seoul, Korea Status: Offline Points: 3	Post Options Post Reply Quote myblues Report Post Thanks(0) Quote Reply Topic: [BUG REPORT] A320m NB frequency bug on newest BIOS Posted: 28 Feb 2020 at 12:52am
	Hi, There is a bug in newest BIOS (v3.7) for A320m HDV R4.0, which the NB frequency only becomes 1/2 of Memory frequency. For example, If I set my RAM to 3200Mhz (1600Mhz DDR), the NB frequency becomes 800Mhz instead of 1600Mhz. I was able to solve this by rolling back the BIOS to v 3.3. This is reported by numerous users on Korean hardware forums, which cause very high memory latency. (Because the NB freq is half of what it should be) Below are the posts of those reports. https://quasarzone.co.kr/bbs/board.php?bo_table=qf_overclocking&wr_id=36046 https://quasarzone.co.kr/bbs/board.php?bo_table=qf_hwjoin&wr_id=308827 This problem also happens for A320m HDV R3.0 too, and also can be solved by rolling back the BIOS. Can you please update the BIOS with this bug fixed with the newest AGESA?

mst.duu Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 02 Mar 2020 Status: Offline Points: 1	Post Options Post Reply Quote mst.duu Report Post Thanks(0) Quote Reply Posted: 02 Mar 2020 at 2:22am
	I'm having the same problem with my am320m-hd. I'm afraid to touch the bios, my bios is the p5.40