F5F Stay Refreshed Hardware Desktop EXPO isn't compatible with Asus TUF x670e plus

EXPO isn't compatible with Asus TUF x670e plus

EXPO isn't compatible with Asus TUF x670e plus

Pages (2): Previous 1 2
L
LumbarX
Junior Member
37
10-22-2017, 09:30 PM
#11
So far everything appears satisfactory. The 1410 model seems suitable. EXPO-II Memory Context Restore functions well; minor CPU speed increase from 6000MHz to 6200MHz didn’t affect timing or performance. No noticeable slowdown observed. Sleep issues are absent, and the CPU downclocks consistently as before during idle periods. The system feels stable thus far.

However, there’s no improvement in boot time. It took roughly 11-12 seconds under 0821, and remains similar now. With Memory Context Restore activated, Fast Boot enabled, and POST delay at zero, the process still takes a bit longer than expected. ASUS doesn’t account for this delay, but it’s still within acceptable limits.

I didn’t see any reduction in boot duration. The system took 11-12 seconds before reaching under 0821, and continues to do so even after enabling Memory Context Restore. BIOS was updated following ASUS guidelines, and I set everything up gradually.

After installation, the BIOS was restored using the provided tools. I followed the instructions carefully—rename files, use USB flash drive, enable Safe-Eject, and completed the setup step by step. The system loaded normally, went through Windows, and booted correctly after a few restarts.

In UEFI settings, I disabled Memory Context Restore and saved without making changes to boot order or RAID (unless needed). After exiting, everything worked as expected.

When prompted, I checked for memory-related changes—like "Power Down" being set to Enable—and accepted it. This is fine; ASUS allows flexibility here.

Regarding saved profiles, I didn’t reload them because the BIOS version included all necessary settings. No issues arose from mismatched profiles.

I remember manually entering configurations earlier, and taking photos before starting was a good idea.

System memory training completed successfully, and Windows loaded without problems. If everything checks out, simply restart, adjust UEFI as desired, and enjoy your setup!

Please note: When enabling Memory Context Restore, some memory options may shift—such as changing "Power Down" to Enable. That’s acceptable if it matches ASUS recommendations.

This BIOS version introduced new features, so I stayed within the guidelines provided by ASUS to avoid conflicts.
L
LumbarX
10-22-2017, 09:30 PM #11

So far everything appears satisfactory. The 1410 model seems suitable. EXPO-II Memory Context Restore functions well; minor CPU speed increase from 6000MHz to 6200MHz didn’t affect timing or performance. No noticeable slowdown observed. Sleep issues are absent, and the CPU downclocks consistently as before during idle periods. The system feels stable thus far.

However, there’s no improvement in boot time. It took roughly 11-12 seconds under 0821, and remains similar now. With Memory Context Restore activated, Fast Boot enabled, and POST delay at zero, the process still takes a bit longer than expected. ASUS doesn’t account for this delay, but it’s still within acceptable limits.

I didn’t see any reduction in boot duration. The system took 11-12 seconds before reaching under 0821, and continues to do so even after enabling Memory Context Restore. BIOS was updated following ASUS guidelines, and I set everything up gradually.

After installation, the BIOS was restored using the provided tools. I followed the instructions carefully—rename files, use USB flash drive, enable Safe-Eject, and completed the setup step by step. The system loaded normally, went through Windows, and booted correctly after a few restarts.

In UEFI settings, I disabled Memory Context Restore and saved without making changes to boot order or RAID (unless needed). After exiting, everything worked as expected.

When prompted, I checked for memory-related changes—like "Power Down" being set to Enable—and accepted it. This is fine; ASUS allows flexibility here.

Regarding saved profiles, I didn’t reload them because the BIOS version included all necessary settings. No issues arose from mismatched profiles.

I remember manually entering configurations earlier, and taking photos before starting was a good idea.

System memory training completed successfully, and Windows loaded without problems. If everything checks out, simply restart, adjust UEFI as desired, and enjoy your setup!

Please note: When enabling Memory Context Restore, some memory options may shift—such as changing "Power Down" to Enable. That’s acceptable if it matches ASUS recommendations.

This BIOS version introduced new features, so I stayed within the guidelines provided by ASUS to avoid conflicts.

L
Llyodsk
Member
164
10-22-2017, 09:30 PM
#12
Achieved strong results last night using TUF x670e-plus with Wi-Fi BIOS 1223. I avoided the 1410 beta because of persistent problems with BIOS 1222. With BIOS 1222: frequent crashes in games and Cinebench with EXPO turned on, no PBO or curve optimizer applied. Overall a non-functional machine when EXPO is active. Running smoothly without EXPO. Switching to BIOS 1223 fixed everything – stable performance. RAM at 6000MHz, benchmarks between 36-36-80, VPP 1.35 and 1.8. No crashes after 60 minutes of prime95 memory tests; memtest passed without issues. Negative curve -10 enabled on 7600x without problems. Cinebench score hovered around 14300. Memory restore works, and the shutdown option takes roughly 20 seconds from cold start to Windows. Task manager shows about 13 seconds for boot time (similar to my old Intel 2016 machine, which booted in ~10 seconds). All this ensures a solid machine ready for Diablo 4 beta on Friday. BIOS: 7600x, Kingston Fury KF560C36BBEAK2-32. ASUS TUF x670e-plus Wi-Fi.
L
Llyodsk
10-22-2017, 09:30 PM #12

Achieved strong results last night using TUF x670e-plus with Wi-Fi BIOS 1223. I avoided the 1410 beta because of persistent problems with BIOS 1222. With BIOS 1222: frequent crashes in games and Cinebench with EXPO turned on, no PBO or curve optimizer applied. Overall a non-functional machine when EXPO is active. Running smoothly without EXPO. Switching to BIOS 1223 fixed everything – stable performance. RAM at 6000MHz, benchmarks between 36-36-80, VPP 1.35 and 1.8. No crashes after 60 minutes of prime95 memory tests; memtest passed without issues. Negative curve -10 enabled on 7600x without problems. Cinebench score hovered around 14300. Memory restore works, and the shutdown option takes roughly 20 seconds from cold start to Windows. Task manager shows about 13 seconds for boot time (similar to my old Intel 2016 machine, which booted in ~10 seconds). All this ensures a solid machine ready for Diablo 4 beta on Friday. BIOS: 7600x, Kingston Fury KF560C36BBEAK2-32. ASUS TUF x670e-plus Wi-Fi.

E
everready155
Member
62
10-22-2017, 09:30 PM
#13
I am so happy things work for you, I really am, but I kinda feel disappointed either in my hardware or my skill to get it to work properly. I installed 1223 and still no EXPO for me only yellow light. Tried the exact steps @GoodBytes suggested. At this point I'll wait for 1410 to get out of the beta phase, and try my luck than. If nothing works I'll RMA the MB, and when they tell me that everything works fine I'll put it in a wood chipper. Thanks for your support, if either Asus or AMD cared as much as randos on tech forums I wouldn't have to write this. P.S. how does your MB behave after turning on the EXPO? Mine doesn't even turn off and just switches green light to yellow after I hit enter. Shouldn't it realize the memory won't train and restore defaults, I HAVE TO RESET F(ASUS) CMOS AFTER EACH ATTEMPT. P.S.2. why does it think 6000>>>5600 after fresh reset?
E
everready155
10-22-2017, 09:30 PM #13

I am so happy things work for you, I really am, but I kinda feel disappointed either in my hardware or my skill to get it to work properly. I installed 1223 and still no EXPO for me only yellow light. Tried the exact steps @GoodBytes suggested. At this point I'll wait for 1410 to get out of the beta phase, and try my luck than. If nothing works I'll RMA the MB, and when they tell me that everything works fine I'll put it in a wood chipper. Thanks for your support, if either Asus or AMD cared as much as randos on tech forums I wouldn't have to write this. P.S. how does your MB behave after turning on the EXPO? Mine doesn't even turn off and just switches green light to yellow after I hit enter. Shouldn't it realize the memory won't train and restore defaults, I HAVE TO RESET F(ASUS) CMOS AFTER EACH ATTEMPT. P.S.2. why does it think 6000>>>5600 after fresh reset?

H
HudsonNZ
Member
63
10-22-2017, 09:30 PM
#14
I'm running smoothly with version 1410 beta. It's performed well with my current setup. I started using it on day one and now it handles both work and personal tasks. The only minor hiccup is a 11-12 second boot time—still acceptable compared to the usual 5-7 seconds. The memory training sometimes adds a 1-second delay at startup, which I can tolerate. It's not ideal, but manageable.
H
HudsonNZ
10-22-2017, 09:30 PM #14

I'm running smoothly with version 1410 beta. It's performed well with my current setup. I started using it on day one and now it handles both work and personal tasks. The only minor hiccup is a 11-12 second boot time—still acceptable compared to the usual 5-7 seconds. The memory training sometimes adds a 1-second delay at startup, which I can tolerate. It's not ideal, but manageable.

T
ThatOneGuy14
Member
157
10-22-2017, 09:30 PM
#15
I adjusted to version 1410 without an EXPO update, modified the settings, and noticed my PC began acting strangely. It started training, but the behavior was unusual.
T
ThatOneGuy14
10-22-2017, 09:30 PM #15

I adjusted to version 1410 without an EXPO update, modified the settings, and noticed my PC began acting strangely. It started training, but the behavior was unusual.

I
imr_ali_craft
Junior Member
29
10-22-2017, 09:30 PM
#16
I've faced problems with this exact motherboard before. Even after trying BIOS upgrades, it didn't show any reliability. Sometimes it needs a fresh CMOS to work, other times just requires about 20 minutes to boot. They labeled it as the right name for gaming on systems that don’t cooperate. After spending $300 on another RAM module, it still isn’t working, so I’m now considering an RMA for the board. It seems this issue is common, though I hope Asus would acknowledge the problems they’re experiencing here.
I
imr_ali_craft
10-22-2017, 09:30 PM #16

I've faced problems with this exact motherboard before. Even after trying BIOS upgrades, it didn't show any reliability. Sometimes it needs a fresh CMOS to work, other times just requires about 20 minutes to boot. They labeled it as the right name for gaming on systems that don’t cooperate. After spending $300 on another RAM module, it still isn’t working, so I’m now considering an RMA for the board. It seems this issue is common, though I hope Asus would acknowledge the problems they’re experiencing here.

T
TheSnowBooy
Junior Member
8
10-22-2017, 09:30 PM
#17
Well, aSUS is facing serious trouble now. Witnessing tech Jesus and Jayz completely crush them gave me a huge smile. All the effort I put into fixing my build—literally hours of my time wasted—will finally pay off. Feeling proud. I’m tempted to switch to a different x670 board and discard this one, but that idea fades when I think about protecting the public from this terrible product. My second thought is to hide it in a metal box and sink it in the ocean so it never comes back. Clearly, I deeply dislike this board with intense passion. It was meant to be my dream machine, but what I got is just a nightmare.
T
TheSnowBooy
10-22-2017, 09:30 PM #17

Well, aSUS is facing serious trouble now. Witnessing tech Jesus and Jayz completely crush them gave me a huge smile. All the effort I put into fixing my build—literally hours of my time wasted—will finally pay off. Feeling proud. I’m tempted to switch to a different x670 board and discard this one, but that idea fades when I think about protecting the public from this terrible product. My second thought is to hide it in a metal box and sink it in the ocean so it never comes back. Clearly, I deeply dislike this board with intense passion. It was meant to be my dream machine, but what I got is just a nightmare.

Pages (2): Previous 1 2