x570 Taichi BIOS v3.80 Code 92 with 3600Mhz RAM

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

   Hi,

finally got 5950x and dropped it into x570 Taichi motherboard. Updated BIOS to latest (at that time) beta v3.80. Now this BIOS is posted as stable.
The system produces Code 92 when I set RAM speeds anything above 3533Mhz. 3533Mhz is stable.

Previous CPU (3900x) on BIOS 2.80 ran 3600Mhz c14 no problem since the CPU was released. I believe 5000 series has much better memory compatibility, so I am surprised that it fails to boot with 3600Mhz and above speeds.
RAM is Corsair vengeance 4000Mhz Samsung b-die. 2x8GB. RAM has not been removed when CPU swap took place. I expected at least be able to match the same RAM speeds I got from 3900x.
Code 92 according to google's wisdom has nothing to do with RAM, and has something to do with pci-e on Asrock motherboards, which makes no sense, so I suspect some sort of a bug in the BIOS.

RAM voltage is set to 1.36v and can even take 1.4V if needed.
I suspect maybe RAM somehow fails memory training, and if I could find where to set pre-POST VDIMM, that would answer that question.
By the way AM4 motherboard BIOS layout (it is similar with all motherboards) is a complete illogical mess

Thanks in advance :)

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
muziqaz Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 04 Jan 2021 Location: London Status: Offline Points: 590	Post Options Post Reply Quote muziqaz Report Post Thanks(0) Quote Reply Topic: x570 Taichi BIOS v3.80 Code 92 with 3600Mhz RAM Posted: 04 Jan 2021 at 10:39pm
	Hi, finally got 5950x and dropped it into x570 Taichi motherboard. Updated BIOS to latest (at that time) beta v3.80. Now this BIOS is posted as stable. The system produces Code 92 when I set RAM speeds anything above 3533Mhz. 3533Mhz is stable. Previous CPU (3900x) on BIOS 2.80 ran 3600Mhz c14 no problem since the CPU was released. I believe 5000 series has much better memory compatibility, so I am surprised that it fails to boot with 3600Mhz and above speeds. RAM is Corsair vengeance 4000Mhz Samsung b-die. 2x8GB. RAM has not been removed when CPU swap took place. I expected at least be able to match the same RAM speeds I got from 3900x. Code 92 according to google's wisdom has nothing to do with RAM, and has something to do with pci-e on Asrock motherboards, which makes no sense, so I suspect some sort of a bug in the BIOS. RAM voltage is set to 1.36v and can even take 1.4V if needed. I suspect maybe RAM somehow fails memory training, and if I could find where to set pre-POST VDIMM, that would answer that question. By the way AM4 motherboard BIOS layout (it is similar with all motherboards) is a complete illogical mess Thanks in advance :)
	folding@home

muziqaz Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 04 Jan 2021 Location: London Status: Offline Points: 590	Post Options Post Reply Quote muziqaz Report Post Thanks(0) Quote Reply Posted: 16 Feb 2021 at 4:54pm
	So v4.00 fixed the code 92 error, however at 3600Mhz I get WHEA errors every 5 seconds logged in Event viewer. So yeah, so much for better memory compatibility with 5000 series :D
	folding@home

ThreeDee Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 24 Jul 2019 Location: Billings,MT Status: Offline Points: 2396	Post Options Post Reply Quote ThreeDee Report Post Thanks(0) Quote Reply Posted: 16 Feb 2021 at 6:32pm
	maybe you got a dud memory controller on that new 5950x proc .. I'd say RMA it if it wasn't for the fact that you probably wouldn't get a replacement one for a verrrry long time
	\|Ryzen 5 5900\|ASRock X570 Taichi-BIOS 4.60\|2x16GB HyperX Predator RGB 3200@3600 1:1 IF\|ASRock RX 6700XT\|2 x PCIe 4.0 M.2 Drives for OS & Games\|850 WTT Seasonic 80+ Titanium PSU\|Noctua NH-D15\|

muziqaz Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 04 Jan 2021 Location: London Status: Offline Points: 590	Post Options Post Reply Quote muziqaz Report Post Thanks(0) Quote Reply Posted: 16 Feb 2021 at 11:19pm
	I'm not really fussed about it. 3533Mhz is as fast as 3600mhz anyways. I'll just play around with PBO this weekend and be done with it ;)
	folding@home

datonyb Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 11 Apr 2017 Location: London U.K. Status: Offline Points: 3139	Post Options Post Reply Quote datonyb Report Post Thanks(0) Quote Reply Posted: 17 Feb 2021 at 1:17am
	tried setting a more basic xmp type setting for booting up? e.g. 3200 cl16 @1.375 volts (avoiding this cold boot issue) and then using ryzen master to activate 3600 in windows once its past the cold boot timeframe? i suggest 1.375 volts as apperently you cant alter dram voltage once in windows with RM im still getting very very random cold boot issue with my system (can be months apart) and mine involves a wierd procedure to get back to working (involving full cmos clear ,boot 2133mhz with only one stick in a2, set 3600 cl16 .reboot to windows ,shut down then insert the second stick simply will not do an initial boot with more than one stick and 2133mhz after a cmos clear as you say we could do with the pre post voltage options
	[url=https://valid.x86.fr/jpg250][/url] 3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold

muziqaz Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 04 Jan 2021 Location: London Status: Offline Points: 590	Post Options Post Reply Quote muziqaz Report Post Thanks(0) Quote Reply Posted: 17 Feb 2021 at 2:33am
	I can boot with 3600Mhz clock fine now with BIOS v4.00. I can even play games on that memory, and it passes mem stability tests. However, in the background system is spamming WHEA errors (1 every 5 seconds). As it is right now, I am still trying to completely get rid of WHEA reboot with 3533Mhz speed, which happens once a week or so. Funnily enough, WHEA related system restart happens in the mornings when I am at work :D
	folding@home