F5F Stay Refreshed Hardware Desktop The B650-PLUS model from TUF Gaming often faces stability concerns when connected to Wi-Fi.

The B650-PLUS model from TUF Gaming often faces stability concerns when connected to Wi-Fi.

The B650-PLUS model from TUF Gaming often faces stability concerns when connected to Wi-Fi.

E
EtAkS_PvP
Junior Member
3
08-20-2022, 02:50 AM
#1
I just installed new upgrades for my PC. My configuration looks like this: Ryzen 7700X TUF Gaming, B650-Plus Wi-Fi, Corsair Vengance 2x16GB CMK32GX5M2A4800C40, powered straight on at 11 kW. RTX 3070 Phoenix is connected. After setup I’m facing stability problems. The system boots but crashes repeatedly within seconds to minutes. These occur during boot and when using Memtest. My BIOS settings are: Firmware 1616, SoC Voltage manual 1.2V (HWInfo says ~1.23V), MCR off, Fast Boot disabled, RAM/EXPO off, PBO enabled. When I press power, the LEDs show a specific pattern. I’ve tried reassembly, running without GPU, using one RAM stick, but nothing seems to help. I’m considering downgrading the BIOS firmware to versions like 0829 or 1001, as some users reported stable results with those updates. Any advice from others with similar configurations would be appreciated.
E
EtAkS_PvP
08-20-2022, 02:50 AM #1

I just installed new upgrades for my PC. My configuration looks like this: Ryzen 7700X TUF Gaming, B650-Plus Wi-Fi, Corsair Vengance 2x16GB CMK32GX5M2A4800C40, powered straight on at 11 kW. RTX 3070 Phoenix is connected. After setup I’m facing stability problems. The system boots but crashes repeatedly within seconds to minutes. These occur during boot and when using Memtest. My BIOS settings are: Firmware 1616, SoC Voltage manual 1.2V (HWInfo says ~1.23V), MCR off, Fast Boot disabled, RAM/EXPO off, PBO enabled. When I press power, the LEDs show a specific pattern. I’ve tried reassembly, running without GPU, using one RAM stick, but nothing seems to help. I’m considering downgrading the BIOS firmware to versions like 0829 or 1001, as some users reported stable results with those updates. Any advice from others with similar configurations would be appreciated.

A
aussieboy28
Member
55
08-20-2022, 12:51 PM
#2
This situation seems both typical and improbable. On the board each hue represents a specific stage in the boot process (as I recall Orange for CPU, Red for RAM, White for GPU, Green for boot device), yet using three colors makes it hard to interpret the RAM indicator clearly. It’s normal for all four LEDs to light up during startup, so that behavior is expected. Regarding the crash, since it fails testing in Memtest, faulty RAM is a strong suspect. I’d consider returning the unit and getting a replacement if possible. If you’ve gone through many BIOS updates without improvement, hardware likely needs attention first—DDR5 components are sensitive to improper installation and can cause instability.
A
aussieboy28
08-20-2022, 12:51 PM #2

This situation seems both typical and improbable. On the board each hue represents a specific stage in the boot process (as I recall Orange for CPU, Red for RAM, White for GPU, Green for boot device), yet using three colors makes it hard to interpret the RAM indicator clearly. It’s normal for all four LEDs to light up during startup, so that behavior is expected. Regarding the crash, since it fails testing in Memtest, faulty RAM is a strong suspect. I’d consider returning the unit and getting a replacement if possible. If you’ve gone through many BIOS updates without improvement, hardware likely needs attention first—DDR5 components are sensitive to improper installation and can cause instability.

R
rayshealy
Junior Member
27
08-20-2022, 04:35 PM
#3
Thanks a lot. I might be mistaken about that. The LEDs are incredibly small, making them hard to see clearly. It could be worth experimenting with a fresh set of RAM. I’m curious if it’s really essential, since the mainboard officially supports it. I’ll let you know once I’ve tried a new pair.
R
rayshealy
08-20-2022, 04:35 PM #3

Thanks a lot. I might be mistaken about that. The LEDs are incredibly small, making them hard to see clearly. It could be worth experimenting with a fresh set of RAM. I’m curious if it’s really essential, since the mainboard officially supports it. I’ll let you know once I’ve tried a new pair.

K
Krohlus
Junior Member
18
08-21-2022, 01:26 AM
#4
K
Krohlus
08-21-2022, 01:26 AM #4

M
Mario10Gamer
Member
188
08-21-2022, 03:24 AM
#5
Also consider upgrading to a quicker RAM type since 4800c40 slows things down and harms CPU speed. Go with 5600c30 or 6000c32; 6000c36+ works too well.
M
Mario10Gamer
08-21-2022, 03:24 AM #5

Also consider upgrading to a quicker RAM type since 4800c40 slows things down and harms CPU speed. Go with 5600c30 or 6000c32; 6000c36+ works too well.

M
MaskeddPig
Member
179
08-21-2022, 11:08 AM
#6
You don't need to replace RAM just to check its performance—test it one stick at a time. Crashing during Memtest usually points to CPU problems rather than faulty RAM. The Q-LEDs aren’t error indicators; they indicate which stage of POST the system is executing. They’re helpful only if you notice a single LED turning on, signaling a problem in that specific part of the POST process. If the green light stays on, it suggests a storage drive issue.
M
MaskeddPig
08-21-2022, 11:08 AM #6

You don't need to replace RAM just to check its performance—test it one stick at a time. Crashing during Memtest usually points to CPU problems rather than faulty RAM. The Q-LEDs aren’t error indicators; they indicate which stage of POST the system is executing. They’re helpful only if you notice a single LED turning on, signaling a problem in that specific part of the POST process. If the green light stays on, it suggests a storage drive issue.

K
koalaholic2004
Junior Member
12
08-22-2022, 08:02 PM
#7
I disassembled and reassembled the entire system to verify potential problems with connectors, high CPU mounting pressure, etc. I also reset the BIOS using the jumper and left everything unchanged. After that, I ran Memtest and it completed without errors—about 2.5 hours. BUT: Once I powered on, the machine froze immediately on the log-in screen, just like in BIOS settings. It reached the ~2-minute mark before freezing. In another attempt, it stayed operational for a while, allowing me to check HWMonitor/Armoury and perform some tests. The CPU core voltage idled around 1.15–1.2V, and the SoC voltage stayed at 1.04–1.048V. Even though this was lower than previous configurations, I’m unsure if it stops the SoC from exceeding 1.3V. The CPU VDDIO/MC voltage was between 1.12–1.136V, with a temperature around 35°C. I then ran FurMark CPU Burner; the core voltage was 1.3–1.32V, which is within range. The SoC voltage stayed at 1.048–1.056V, and temperature remained near 84°C. When I tried FurMark with a GPU load for a 1440p preset, everything worked fine—voltages were stable and scores were in the 7600s. My takeaway is that you can apply stress to the system, but the issue might lie elsewhere. I attempted to play games; the PC crashed midway through LoL after installation. Restarting helped, but it crashed again within two minutes on YouTube. It seems to occur unpredictably, despite normal temperatures and voltages. I’m considering logging the system (for error tracing) to help diagnose further. Unfortunately, I haven’t encountered a BSOD that would provide clear clues. From other forums, many suggest CPU-related problems, even though I’m not fully understanding the details. Adjusting settings like RAM overclocking, Expo, PBO, MCR, or Fast Boot might resolve the issue. I’m just offering some suggestions here.
K
koalaholic2004
08-22-2022, 08:02 PM #7

I disassembled and reassembled the entire system to verify potential problems with connectors, high CPU mounting pressure, etc. I also reset the BIOS using the jumper and left everything unchanged. After that, I ran Memtest and it completed without errors—about 2.5 hours. BUT: Once I powered on, the machine froze immediately on the log-in screen, just like in BIOS settings. It reached the ~2-minute mark before freezing. In another attempt, it stayed operational for a while, allowing me to check HWMonitor/Armoury and perform some tests. The CPU core voltage idled around 1.15–1.2V, and the SoC voltage stayed at 1.04–1.048V. Even though this was lower than previous configurations, I’m unsure if it stops the SoC from exceeding 1.3V. The CPU VDDIO/MC voltage was between 1.12–1.136V, with a temperature around 35°C. I then ran FurMark CPU Burner; the core voltage was 1.3–1.32V, which is within range. The SoC voltage stayed at 1.048–1.056V, and temperature remained near 84°C. When I tried FurMark with a GPU load for a 1440p preset, everything worked fine—voltages were stable and scores were in the 7600s. My takeaway is that you can apply stress to the system, but the issue might lie elsewhere. I attempted to play games; the PC crashed midway through LoL after installation. Restarting helped, but it crashed again within two minutes on YouTube. It seems to occur unpredictably, despite normal temperatures and voltages. I’m considering logging the system (for error tracing) to help diagnose further. Unfortunately, I haven’t encountered a BSOD that would provide clear clues. From other forums, many suggest CPU-related problems, even though I’m not fully understanding the details. Adjusting settings like RAM overclocking, Expo, PBO, MCR, or Fast Boot might resolve the issue. I’m just offering some suggestions here.

M
mishy07
Senior Member
371
08-23-2022, 03:39 AM
#8
Be cautious about the operating system. Unstable RAM often causes problems with OS stability, so I’d consider reinstalling Windows to check if it resolves the issue.
M
mishy07
08-23-2022, 03:39 AM #8

Be cautious about the operating system. Unstable RAM often causes problems with OS stability, so I’d consider reinstalling Windows to check if it resolves the issue.

R
Redacting
Member
207
08-23-2022, 05:07 AM
#9
Consider trying manual BSOD mode, see if you can trigger one after it freezes. Think about adding it to the registry, rebooting, and then holding Ctrl plus Scroll Lock twice to start a crash. Keep in mind these steps need more expertise to troubleshoot, so feel free to share the dump files for assistance. If the system is sufficiently frozen, nothing may occur.
R
Redacting
08-23-2022, 05:07 AM #9

Consider trying manual BSOD mode, see if you can trigger one after it freezes. Think about adding it to the registry, rebooting, and then holding Ctrl plus Scroll Lock twice to start a crash. Keep in mind these steps need more expertise to troubleshoot, so feel free to share the dump files for assistance. If the system is sufficiently frozen, nothing may occur.