F5F Stay Refreshed Hardware Desktop Join the Biostar X570GT8 Owners Club for exclusive support and updates.

Join the Biostar X570GT8 Owners Club for exclusive support and updates.

Join the Biostar X570GT8 Owners Club for exclusive support and updates.

Pages (2): 1 2 Next
P
Pooky2
Member
56
03-22-2019, 06:32 PM
#1
Hello, I'm seeking fellow enthusiasts who own this motherboard. It seems to be a niche product, so online searches yield limited details. I'd appreciate hearing from others about this platform, especially regarding the BIOS settings and memory configurations.

I experienced a RAM failure on this board recently—possibly linked to a CMOS issue mentioned in an earlier post. The faulty RAM was replaced with a different module, and everything functioned normally afterward. My test showed 68.1 ns for GSKILL F4-3600C15-16GTZ CL15-15-x and 71.4 ns for the TG UD4 3600 model. I'm hoping these times are reasonable, though I'd be grateful for confirmation if they fall within typical ranges.

Ideally, I'd like to connect with users who have similar experiences, such as BIOS tweaks or power-down settings, and get their insights on any quirks they've encountered. If anyone has used the same RAM type or followed specific configurations, sharing those details would be invaluable.
P
Pooky2
03-22-2019, 06:32 PM #1

Hello, I'm seeking fellow enthusiasts who own this motherboard. It seems to be a niche product, so online searches yield limited details. I'd appreciate hearing from others about this platform, especially regarding the BIOS settings and memory configurations.

I experienced a RAM failure on this board recently—possibly linked to a CMOS issue mentioned in an earlier post. The faulty RAM was replaced with a different module, and everything functioned normally afterward. My test showed 68.1 ns for GSKILL F4-3600C15-16GTZ CL15-15-x and 71.4 ns for the TG UD4 3600 model. I'm hoping these times are reasonable, though I'd be grateful for confirmation if they fall within typical ranges.

Ideally, I'd like to connect with users who have similar experiences, such as BIOS tweaks or power-down settings, and get their insights on any quirks they've encountered. If anyone has used the same RAM type or followed specific configurations, sharing those details would be invaluable.

C
crazyone23
Member
147
03-29-2019, 03:00 PM
#2
I'm struggling here. This could be a long post, so I'll try to keep it brief. I used the board fine for 4 months and a morning boot. Everything looked good until last minute when CMOS failed. I pressed the setup button, saw old BIOS error, then it booted again. Restarted, set up, changed RAM, and it worked this time. Booted back into Windows, but still got blue screen crashes. After updates, it ran at 2400 but crashed at 3600. Now it's stuck between 8-Ball TG UD4 3600. I'm unsure why it keeps looping or failing. Maybe someone can help explain what's going on.
C
crazyone23
03-29-2019, 03:00 PM #2

I'm struggling here. This could be a long post, so I'll try to keep it brief. I used the board fine for 4 months and a morning boot. Everything looked good until last minute when CMOS failed. I pressed the setup button, saw old BIOS error, then it booted again. Restarted, set up, changed RAM, and it worked this time. Booted back into Windows, but still got blue screen crashes. After updates, it ran at 2400 but crashed at 3600. Now it's stuck between 8-Ball TG UD4 3600. I'm unsure why it keeps looping or failing. Maybe someone can help explain what's going on.

H
HiImAnnabel
Member
238
03-29-2019, 04:34 PM
#3
Same here. After a few months my Ryzen 3600X began showing random blue screens with various codes, especially 000000a. Other issues appeared too, like problems writing data in an already used space or threading errors. I had another machine available. A regular 3600 and an Asus Prime B450. I placed the standard 3600 in the BIOSTAR X570 and the 3600X in the Asus unit—it functioned flawlessly... days of intense testing in Heaven, 3DMark, CineBench, Memtest, etc., without any blue screen. I swapped the processors back: the 3600X on the X570 and the regular 3600 on the B450... the X570 setup returned to random blue screens. I can't figure it out because it had worked perfectly for months. The B450 card is simpler overall, including its VRM; if a defect existed, it would likely be more obvious on the B450. Yet on the 3600X it performed just fine. Both cards run AGESA 1.0.0.4B. After seven days of testing and trying to figure it out, I gave up and decided to leave these processors in place. Even returning for an RMA is tricky because if you test the 3600X there, it might work as it did on the B450... and ordering an RMA from the X570 could also resolve the issue with another processor. At least I have a second unit that I can replace, which worked, though it was strange. Since the performance difference was only about 5% across all tests, it doesn’t bother me to stick with the simpler 3600 on the X570, but I remained curious about why this happened.
H
HiImAnnabel
03-29-2019, 04:34 PM #3

Same here. After a few months my Ryzen 3600X began showing random blue screens with various codes, especially 000000a. Other issues appeared too, like problems writing data in an already used space or threading errors. I had another machine available. A regular 3600 and an Asus Prime B450. I placed the standard 3600 in the BIOSTAR X570 and the 3600X in the Asus unit—it functioned flawlessly... days of intense testing in Heaven, 3DMark, CineBench, Memtest, etc., without any blue screen. I swapped the processors back: the 3600X on the X570 and the regular 3600 on the B450... the X570 setup returned to random blue screens. I can't figure it out because it had worked perfectly for months. The B450 card is simpler overall, including its VRM; if a defect existed, it would likely be more obvious on the B450. Yet on the 3600X it performed just fine. Both cards run AGESA 1.0.0.4B. After seven days of testing and trying to figure it out, I gave up and decided to leave these processors in place. Even returning for an RMA is tricky because if you test the 3600X there, it might work as it did on the B450... and ordering an RMA from the X570 could also resolve the issue with another processor. At least I have a second unit that I can replace, which worked, though it was strange. Since the performance difference was only about 5% across all tests, it doesn’t bother me to stick with the simpler 3600 on the X570, but I remained curious about why this happened.

C
C_M
Junior Member
31
03-30-2019, 02:05 AM
#4
Same here. After a few months my Ryzen 3600X began showing random blue screens with various codes, especially 000000a. Other issues appeared too, like problems writing data in an already used space or threading errors. I had another machine available. A regular 3600 and an Asus Prime B450. I placed the standard 3600 in the BIOSTAR X570 and the 3600X in the Asus unit—it functioned flawlessly... days of intense testing in Heaven, 3DMark, CineBench, Memtest, etc., without any blue screen. I swapped the processors back: the 3600X on the X570 and the regular 3600 on the B450... the X570 model returned to showing random blue screens. I can't figure it out because it had worked perfectly for months. The B450 card seemed simpler overall, including its VRM; if a defect existed, it would likely be more obvious on the B450. Yet on the 3600X it performed just fine. Both cards run AGESA 1.0.0.4B. After seven days of testing and trying to figure it out, I gave up and decided to leave these processors in place. Even returning for an RMA is tricky because if you test the 3600X there, it might work as it did on the B450... and ordering an RMA from the X570 could also resolve the issue with another processor. At least I have a second unit that I can replace, which worked, though it was strange. Since the performance difference was only about 5% across all tests, it doesn’t bother me to stick with the simpler 3600 on the X570, but I remained curious about why this happened.
C
C_M
03-30-2019, 02:05 AM #4

Same here. After a few months my Ryzen 3600X began showing random blue screens with various codes, especially 000000a. Other issues appeared too, like problems writing data in an already used space or threading errors. I had another machine available. A regular 3600 and an Asus Prime B450. I placed the standard 3600 in the BIOSTAR X570 and the 3600X in the Asus unit—it functioned flawlessly... days of intense testing in Heaven, 3DMark, CineBench, Memtest, etc., without any blue screen. I swapped the processors back: the 3600X on the X570 and the regular 3600 on the B450... the X570 model returned to showing random blue screens. I can't figure it out because it had worked perfectly for months. The B450 card seemed simpler overall, including its VRM; if a defect existed, it would likely be more obvious on the B450. Yet on the 3600X it performed just fine. Both cards run AGESA 1.0.0.4B. After seven days of testing and trying to figure it out, I gave up and decided to leave these processors in place. Even returning for an RMA is tricky because if you test the 3600X there, it might work as it did on the B450... and ordering an RMA from the X570 could also resolve the issue with another processor. At least I have a second unit that I can replace, which worked, though it was strange. Since the performance difference was only about 5% across all tests, it doesn’t bother me to stick with the simpler 3600 on the X570, but I remained curious about why this happened.

S
StreetHobo
Senior Member
568
04-18-2019, 02:32 PM
#5
Another batch of 3600 RAM seems faulty while running on this Biostar. I've now swapped in 3200 and 1600 FCLK if the CMOS keeps failing at 3200. When it hits that point, I'm considering discarding the motherboard entirely (seriously). If their support had been better, it would have been fixed sooner. Their support team kept saying 3600 is standard and not guaranteed, and mentioning blue light isn't really helpful in their explanations.
S
StreetHobo
04-18-2019, 02:32 PM #5

Another batch of 3600 RAM seems faulty while running on this Biostar. I've now swapped in 3200 and 1600 FCLK if the CMOS keeps failing at 3200. When it hits that point, I'm considering discarding the motherboard entirely (seriously). If their support had been better, it would have been fixed sooner. Their support team kept saying 3600 is standard and not guaranteed, and mentioning blue light isn't really helpful in their explanations.

X
xGeezuz_G0D
Junior Member
6
04-25-2019, 11:42 PM
#6
X
xGeezuz_G0D
04-25-2019, 11:42 PM #6

C
Cokkie77
Senior Member
556
04-26-2019, 05:31 AM
#7
I believe I attempted but can't recall the exact steps. Now I'm planning to disassemble everything and test the spare motherboard to check if the existing components function properly at 1800/3600 on the X570 AORUS MASTER I purchased in January this year. I've been feeling unwell, and honestly, for the first time in over 30 years, I'm tired of dealing with computers and troubleshooting them. My mind won't switch off after a few years, but my body is worn out and my energy is fading. When trying to sleep, two hours later my brain suggests it's the issue, and you wake up at 4 AM feeling exhausted and stressed. I struggle to fit into tight spaces anymore—my hands don’t feel as they used to, even though they’re not overly large. My vision is also affected. I keep getting stuck on errors in this build and can't shake them off, knowing it didn’t defeat me but I’ve managed to fix it before. As I mentioned earlier, it’s time to accept defeat (no!), not because I’m naturally that way, but rather to stop trying to fix things that might be beyond my control, like a faulty motherboard or other hardware issues. Once I finish building and wait for the RMA RAM to arrive, I’ll update. I’ve seen some 3700x recommend replacing them due to reliability concerns, and the chipset fan seems to skip on itself sometimes. I’ll have to manually check if it spins when I restart and gently push or blow until it starts. Dust levels are low, and my PC is well-maintained—cleaned regularly, dust intake minimal. All my PCs are in good shape.
C
Cokkie77
04-26-2019, 05:31 AM #7

I believe I attempted but can't recall the exact steps. Now I'm planning to disassemble everything and test the spare motherboard to check if the existing components function properly at 1800/3600 on the X570 AORUS MASTER I purchased in January this year. I've been feeling unwell, and honestly, for the first time in over 30 years, I'm tired of dealing with computers and troubleshooting them. My mind won't switch off after a few years, but my body is worn out and my energy is fading. When trying to sleep, two hours later my brain suggests it's the issue, and you wake up at 4 AM feeling exhausted and stressed. I struggle to fit into tight spaces anymore—my hands don’t feel as they used to, even though they’re not overly large. My vision is also affected. I keep getting stuck on errors in this build and can't shake them off, knowing it didn’t defeat me but I’ve managed to fix it before. As I mentioned earlier, it’s time to accept defeat (no!), not because I’m naturally that way, but rather to stop trying to fix things that might be beyond my control, like a faulty motherboard or other hardware issues. Once I finish building and wait for the RMA RAM to arrive, I’ll update. I’ve seen some 3700x recommend replacing them due to reliability concerns, and the chipset fan seems to skip on itself sometimes. I’ll have to manually check if it spins when I restart and gently push or blow until it starts. Dust levels are low, and my PC is well-maintained—cleaned regularly, dust intake minimal. All my PCs are in good shape.

K
kbolt
Member
238
05-04-2019, 09:14 PM
#8
K
kbolt
05-04-2019, 09:14 PM #8

B
BenTGreat
Senior Member
437
05-05-2019, 01:20 AM
#9
I possess a large amount of RAM purchased for this system/processor. I initially believed a 3700 was safe, but I set it at 1800 as an upgrade over the previous models. I considered the lower range of 3600/3733 and thought 1:1. I also assumed the Samsung B-Die team group DDR4 board should operate at 1T from the XMP profile, though the BIOS didn't recognize it correctly, showing 34xx instead of 3600. The manual suggested using 1T, but stability seemed more likely at 2T. This was prepared by Thaiphoon Burner Super Blaster.
B
BenTGreat
05-05-2019, 01:20 AM #9

I possess a large amount of RAM purchased for this system/processor. I initially believed a 3700 was safe, but I set it at 1800 as an upgrade over the previous models. I considered the lower range of 3600/3733 and thought 1:1. I also assumed the Samsung B-Die team group DDR4 board should operate at 1T from the XMP profile, though the BIOS didn't recognize it correctly, showing 34xx instead of 3600. The manual suggested using 1T, but stability seemed more likely at 2T. This was prepared by Thaiphoon Burner Super Blaster.

G
Gryzzly13
Junior Member
29
05-06-2019, 12:41 AM
#10
CMOS failure occurred on this board recently, even though it was running at 1600 MHz and using the 3200 16-18-18-36 XMP profile. Biostar might still think I’m overclocking, while 2933 is only supported. I have a new 3700X in development and a testbench ready. I plan to replace the old Biostar with a Gigabyte model, but I don’t want to mix hardware from that system into my Mobo. I attempted an RMA through Ebuyer using online returns, entered all details, and waited—after some time, they called me. About 60 minutes later, they told me to call back. After that, no response. I hung up. Scan confirmed they would RMA the CPU and arranged a pickup, asking when I should come. I’m not confident enough to say if the CPU is broken right now. There’s conflicting info, and my mind is confused. The RAM seems faulty, but I can’t be sure if it’s the only problem or something else on the board causing all this RAM instability. I’m not ready to return a CPU that might hide these issues, especially since I’m unsure whether an RMA would actually fix it. If they say nothing’s wrong, I’ll have to pay for a replacement, which could lead to more trouble and stress. It feels like a long shot—maybe I’ll keep it and test it on another board, or give it away. The problem with the Biostar is unpredictable; there are no clear signs it will fail again next time. If this happens, I’m worried about wasting time and money, especially since I can’t travel easily and need to protect the unit. It’s like watching something strange happen without knowing why, and I’m not sure if it’s a warning or just bad luck.
G
Gryzzly13
05-06-2019, 12:41 AM #10

CMOS failure occurred on this board recently, even though it was running at 1600 MHz and using the 3200 16-18-18-36 XMP profile. Biostar might still think I’m overclocking, while 2933 is only supported. I have a new 3700X in development and a testbench ready. I plan to replace the old Biostar with a Gigabyte model, but I don’t want to mix hardware from that system into my Mobo. I attempted an RMA through Ebuyer using online returns, entered all details, and waited—after some time, they called me. About 60 minutes later, they told me to call back. After that, no response. I hung up. Scan confirmed they would RMA the CPU and arranged a pickup, asking when I should come. I’m not confident enough to say if the CPU is broken right now. There’s conflicting info, and my mind is confused. The RAM seems faulty, but I can’t be sure if it’s the only problem or something else on the board causing all this RAM instability. I’m not ready to return a CPU that might hide these issues, especially since I’m unsure whether an RMA would actually fix it. If they say nothing’s wrong, I’ll have to pay for a replacement, which could lead to more trouble and stress. It feels like a long shot—maybe I’ll keep it and test it on another board, or give it away. The problem with the Biostar is unpredictable; there are no clear signs it will fail again next time. If this happens, I’m worried about wasting time and money, especially since I can’t travel easily and need to protect the unit. It’s like watching something strange happen without knowing why, and I’m not sure if it’s a warning or just bad luck.

Pages (2): 1 2 Next