F5F Stay Refreshed Hardware Desktop Updated PC Construction – Fixes for my issues (PC freezing, Windows glitches) and Expo (Halp) problems

Updated PC Construction – Fixes for my issues (PC freezing, Windows glitches) and Expo (Halp) problems

Updated PC Construction – Fixes for my issues (PC freezing, Windows glitches) and Expo (Halp) problems

C
233
05-26-2022, 07:05 AM
#1
Hey everyone, I just assembled a fresh setup using some vintage components. Here’s what I used: AMD Ryzen 7 7700X, MSI x670-P Pro, Wi-Fi 6E Corsair 5600MHz DDR, Expo support enabled, 2x16GB Peak Assassin ARGB cooler, thermal paste from Grizzly. I reused my old 6600XT (about a year), EVGA 750W PSU (five months), and a 1TB NVMe PCIe 3.0 drive (one year). After the first boot, everything worked smoothly—Windows loaded without trouble, drivers installed, and no glitches. Games ran well with solid FPS and stable temperatures. It felt like I was in good hands for a short time.

Later, I upgraded my BIOS. This caused problems: Windows wouldn’t recognize my license. Even when I tried the “Changed hardware” option, it said I already had a valid license on another machine. The issue seemed tied to the same PC model but an older BIOS version. After switching from Windows 7 to Windows 10, I tried using the Windows 11 activation key, but it didn’t work. I learned that entering a Windows 7 key can sometimes fix activation issues.

I also discovered that disabling memory training helped speed up the boot process. Sometimes the CPU or MEM lights would stay on, causing delays. Resetting CMOS and resetting BIOS settings helped, though it was frustrating to deal with. I re-seated everything and checked for hardware faults, but found no problems.

Looking at other users online, a few reported similar struggles. Some suggested resetting the CMOS or disabling Expo support in BIOS. Others mentioned checking power management settings, like disabling S3 sleep mode. One person noted that their monitors would wake up when they slept, which confused me since I heard sounds during sleep.

I also found out that my Samsung chips were the ones affected most. After some troubleshooting—like clearing regs with Regedit and adjusting power plans—I managed to get the system running again. The AMD Expo feature seemed to be the root cause, but once I disabled it, everything worked fine.

If anyone has more details or tips on fixing this, especially for someone with a similar build, I’d really appreciate it. Thanks for your help!
C
Configurations
05-26-2022, 07:05 AM #1

Hey everyone, I just assembled a fresh setup using some vintage components. Here’s what I used: AMD Ryzen 7 7700X, MSI x670-P Pro, Wi-Fi 6E Corsair 5600MHz DDR, Expo support enabled, 2x16GB Peak Assassin ARGB cooler, thermal paste from Grizzly. I reused my old 6600XT (about a year), EVGA 750W PSU (five months), and a 1TB NVMe PCIe 3.0 drive (one year). After the first boot, everything worked smoothly—Windows loaded without trouble, drivers installed, and no glitches. Games ran well with solid FPS and stable temperatures. It felt like I was in good hands for a short time.

Later, I upgraded my BIOS. This caused problems: Windows wouldn’t recognize my license. Even when I tried the “Changed hardware” option, it said I already had a valid license on another machine. The issue seemed tied to the same PC model but an older BIOS version. After switching from Windows 7 to Windows 10, I tried using the Windows 11 activation key, but it didn’t work. I learned that entering a Windows 7 key can sometimes fix activation issues.

I also discovered that disabling memory training helped speed up the boot process. Sometimes the CPU or MEM lights would stay on, causing delays. Resetting CMOS and resetting BIOS settings helped, though it was frustrating to deal with. I re-seated everything and checked for hardware faults, but found no problems.

Looking at other users online, a few reported similar struggles. Some suggested resetting the CMOS or disabling Expo support in BIOS. Others mentioned checking power management settings, like disabling S3 sleep mode. One person noted that their monitors would wake up when they slept, which confused me since I heard sounds during sleep.

I also found out that my Samsung chips were the ones affected most. After some troubleshooting—like clearing regs with Regedit and adjusting power plans—I managed to get the system running again. The AMD Expo feature seemed to be the root cause, but once I disabled it, everything worked fine.

If anyone has more details or tips on fixing this, especially for someone with a similar build, I’d really appreciate it. Thanks for your help!

S
Sacha101
Junior Member
15
06-12-2022, 09:37 PM
#2
Navigate to Settings > AMD CBS > UMC Common options > DDR Options > DDR Memory Features > Memory context restore > Disable features
S
Sacha101
06-12-2022, 09:37 PM #2

Navigate to Settings > AMD CBS > UMC Common options > DDR Options > DDR Memory Features > Memory context restore > Disable features

C
ChloeET
Senior Member
736
06-14-2022, 12:58 AM
#3
This adjustment would just lower the retraining cost. On the MSI forum, users also set Power Down Enable. After a fresh start with Power Down Enabled, I activated Expo and waited for the PC to boot after a delay. It hung initially but eventually started running smoothly at 5600 with good timing and stability. Now I prefer not to restart again.
C
ChloeET
06-14-2022, 12:58 AM #3

This adjustment would just lower the retraining cost. On the MSI forum, users also set Power Down Enable. After a fresh start with Power Down Enabled, I activated Expo and waited for the PC to boot after a delay. It hung initially but eventually started running smoothly at 5600 with good timing and stability. Now I prefer not to restart again.

A
AER0D
Member
55
06-14-2022, 05:08 AM
#4
However, this comes with a loss of stability.
A
AER0D
06-14-2022, 05:08 AM #4

However, this comes with a loss of stability.

D
dniznemac
Senior Member
555
06-24-2022, 11:35 AM
#5
When I turned it on, I experienced more crashes. I’ve been through day 2 without any problems. I haven’t restarted or shut it down yet. It seems like this is the optimal setting.
D
dniznemac
06-24-2022, 11:35 AM #5

When I turned it on, I experienced more crashes. I’ve been through day 2 without any problems. I haven’t restarted or shut it down yet. It seems like this is the optimal setting.