I ordered my new build from Cyberpower on 2/28 and finally just yesterday they got all the parts and are now building it. Can hardly wait!
Would have liked to get 64GB 32x2 memory but they didn’t have it available when I ordered, may upgrade it later.
CAS: CORSAIR 5000D SERIES AIRFLOW Edition ATX Mid-Tower Gaming Chassis
CPU: AMD Ryzen™ 9 Processor 7950X3D 16-core/32-thread 4.2GHz [Turbo 5.7GHz] 144MB Cache AM5
CS_FAN: 6X 120mm Phanteks SK120 Digital RGB PWM FAN - high airflow nine-blade 500-1500 RPM Radiator Fans
FAN: CORSAIR iCUE H150i ELITE LCD XT Liquid CPU Cooler - IPS LCD Screen 360mm Radiator - AF120 RGB ELITE Fans
HDD: 2TB SAMSUNG 990 PRO (PCIe Gen4) NVMe 2.0 M.2 SSD - Seq R/W: Up to 7450/6900 MB/s, Rnd R/W up to 1200/1550k (Dual Drive (2TB x 2 (4TB Capacity)))
MEMORY: 32GB (16GBx2) DDR5/6000MHz Dual Channel Memory [+225] (GSKILL TRIDENT Z5 RGB)
MOTHERBOARD: ASUS ROG STRIX X670E-E GAMING WIFI AM5 ATX w/ Wi-Fi 6E, 2.5GbT LAN, (2)PCIe x16, (1)PCIe x1, (4)M.2, (4)SATA
POWERSUPPLY: 1200 Watts - Corsair RM1200x SHIFT 80 PLUS Gold ATX 3.0 Fully Modular w/ PCIE 12+4Pins Connector for PCIe 5.0 graphics cards
VIDEO: MSI GeForce RTX™ 4090 GAMING X TRIO 24GB GDDR6X Video Card (Ada Lovelace) [VR Ready] (Single Card)
Don’t look for them. There’re no Ryzen plans installed with the chipset driver for the 7xx0X3D CPUs versions.
AMD’s recommend is the Windows’ Balanced power plan in other to allow the thread parking feature functionality to work properly.
Someone commented about High Performance power plan giving 5fps more for higher TLOD… Well you have to test it yourself. But that’s a very minimal and rounded change that could be related to any other parameter like, for example, ram in use at that moment, etc. The High Performance plan won’t allow the cpu to reduce its minimum frequency and neither to park any thread.
But again, the 7950x3D and 7900x3D parked cores are NOT disabled cores.
When running the simulator the system will prefer to run the sim processes in the vcache cores and other windows and background software in the non vcache cores (unparking those threads).
[quote=“DensestSnail693, post:485, topic:578422”]
Personally I expect a CMOS reset to fix it this…[/quote]
I thought clearing the CMOS was already tried at some point, but guess it wouldn’t hurt to try again.
This makes no sense. I could see possibly needing to re-activate Windows, but the process of replacing the board as far as that goes is pulling the drives from the old and installing in the new. There shouldn’t be any data loss, but always a good idea to make backups where possible prior to sending back.
This link provides step by step instructions. According to it, the BIOSrenamer program should be included in the zip file you download for the update.
https://www.asus.com/support/FAQ/1038568/
According to a Reddit post where I found that link, the file you download is named to identify the version of the BIOS to be installed, but the board requires a specific file name regardless of the version used, and the renaming tool sets that for you automatically. It sounds like you could simply do it with Windows Explorer if you know the correct name.
One thing mentioned in the instructions is to use a FAT32 formatted USB drive. By default, Windows limits that to 32 GB drives and smaller. If you have a drive larger than that, you can still format in FAT32, but it would require a workaround. You can find various ways to do that, but I used a specific program designed to format larger capacity drives like that when I had to BIOS update (unfortunately I don’t remember the name of it to recommend).
So, you’ve NEVER reset the CMOS manually after all those issues? Usually the mb will do it itself when sensitive hardware is changed (cpu) but you should always do it if any issue is encountered. It’s the “mandatory” first step.
That “rename the bios name” it’s just something done automatically. You will see one bios file and one .exe file that will rename the bios file.
But don’t go into the rabbit hole. Don’t install the “beta” version of any bios if you don’t know what are you doing. Apart from the term high density ram modules… it is just allowing the compatibility to new ddr5 24GB and 48GB modules. They are high capacity by definition, but also it is 32GB. It is just a definition.
1 Like
Hello, I just assembled my new pc:
ASUS X670-E Plus motherboard, 2x 32 Gb Ram Corsair 6000 mhz, ASUS 4090, AMD 7950X3D.
Each boot is a bit slow and all the LEDs on the motherboard light up 1 by 1. It takes ± 40 seconds for the pc to boot into Windows and my main screen to light up.
I updated to the latest motherboard driver (not the beta!), CPU chipsets, etc.
Everything is running fine.
MSFS is now beautiful. Everything in ULTRA with TLOD 200, DX 12, DLSS quality and Frames Generation On, in the heart of Paris everything is smooth with Fenix A320.
I can go up TLOD a bit more but I prefer 200 and still smooth even in the middle of Paris.
Only 1 PROBLEM, but it’s the same as with my old configuration (5800X3D). I have this problem since I upgraded to 4090 with FRAMES GENERATION enabled.
Stuttering of MSFS with 2 screens - Community Support / Tech Support - Microsoft Flight Simulator Forums
No, I didn’t since putting the G.skill in. I did as advised by the seller when the 4 sticks of Fury didn’t want to boot but not since swapping to the new ram.
I didn’t know I had to - this is all pretty over my head. I haven’t built a PC for like 20 years and that’s why I bought a pre-built system tbh.
So I’ll give that a go. Hold the back button for 10 seconds (with mains power off?).
And I will NOT install the beta bios (yet, at least even though @kido007dz said to lol).
Fingers crossed the CMOS was the reason?!
I understand where you’re coming from, and I would not recommend that you do something you’re not comfortable with. However, the following reddit post may be of interest in your situation:
More here.
Have you tried DX11? The visuals are better and you do not need frame generation (common denominator for stutters?). I am locked at 60FPS and also running FSLTL (at high settings). I also recommend you adjust your timings per this video that was shared by @xxYUNIORxx . It makes a huge difference.
1 Like
Reddit… and the permanent confidence not knowing what are they talking about. I really dislike them sometimes.
This guy probably has some other ram issues. To just state that the feature was “broken” without even understanding what it is.
“You can enable memory restore context finally which will reduce the boot time because it won’t train memory”. Memory restore context trains the memory for several boots at a cost of a few more seconds of boot time. When ENABLED. If you disable it, it’s when you get back those seconds to reduce your boot time.
CMOS reset, 2 sticks in, same 3 beeps after a minute.
Shouldn’t it go STRAIGHT to bios after a CMOS reset?
Power off, take one stick out again (leaving A2 which was working ok last night), power on, no beeps, just stuck again. Left it a few minutes but nothing so powered down.
Powered on again, no changes (just to try), boots ok. Now I’m in bios screen. I set optimised defaults, saved and booted to windows.
What Next? Try the bios flash or just give up?!
Noticed in bios it now says if I try to enable the AI Overclocking that my CPU does not support overflowing. Pretty sure I got into that screen before. That’s where the ram timing and voltage are? Do I need to reboot after optimised defaults for it to catch up (since cmos reset)?
All I can do is Advanced Mode > AI Tweaker and the Advanced menu (everything is “auto” now).
Honestly the only thing you should do in the bios is enable EXPO II. That’s all. Also if you need something else (fans, pbo, leds, bios behavior, etc). But nothing more.
PBO (Precision Boost Overdrive) depends of your preference but if you are not willing to go into curve optimizer just leave PBO → AUTO
Don’t change anything in AI Tweaker\Precision Boost Overdrive, that’s not the directory. Also, the 7XX0x3D CPUs cannot be overclocked.
If you want to manage your PBO go to Advance\AMD Overclocking\Precision Boost Overdrive there you can set it to AUTO or use curve optimizer.
In AI Tweaker tab you can set your EXPO and in AI Tweaker\xxxxx you can change several ram parameters as you already know, including timings. But I wouldn’t bother at all with that.
Enabling the EXPO profile would give you the best of your ram, unless you know exactly what to do there and squeeze a little bit more of your ram to get 5% more performance. If you don’t get it right you will be pron to instability with all the headache that comes with it.
You don’t need 64 gb of ram, 32gb is more then enough.
1 Like
This is where you need to be to set EXPO.
1 Like
OK will try that (thanks @BoboSkypark for the image) - but it still only boots with 1 stick. Shouldn’t I (try to) get the other stick working BEFORE enabling EXPO II?
Or would expo HELP it train the other stick?
Someone mentioned increasing the Voltage VSOC but I didn’t see that and searching in the manual brings nothing up for “vsoc” so not sure where that is hidden.
Nothing I can change here to make the other stick more likely to pass training?
Definitely I don’t. You can see that!
I don’t care about 5%. 25% yes but not 5!
Sure Reddit is not the bible.
I counted at least 4 people indicating their boot/memory issues were resolved with this bios update, though.
In my experience bios release notes/changelogs are not always exhaustive.
However, updating to a beta firmware is always a risk.
A few questions. You mentioned it only runs with one module inserted. So, in this context:
1- Are we talking about one particular module of the pair?
2- Did you try to use only the “module 1” or “module 2” to verify if there is one not working or defective?
3- Is this working module inserted in the A2 or B2?
4- Does it work if you place it in B2?
Out of this: What is your BIOS actual version? v925, v922 or inferior?
Don’t enable the EXPO profile until you manage to make your both RAM modules work and post.
Answers 
- Either works individually, but they seem to take varying amounts of time to train
- As above, either in A2 works and I can fly and it’s nice and stable
- A2
- When I tried in B2, it didn’t last time, but I could try again but it all seems hit and miss (as I said it didn’t boot a moment ago with 1 stick, no beeps. But just doing another boot and it worked)
Bios is 0922 I believe. Didn’t know there was a 0925. You said earlier 0922 was the correct one for me but this is newer. So should put that on (not Beta)?
Okey that discard a faulty unit at least in the ram modules themselves.
Another questions:
-Do you still have the old x4 64GB modules?
-Did you try to take 2 of them and place them in A2 and B2 to check if there could be any issue with B2? You can also try A1 and B1.
You will have to clear the cmos before and after doing all of that (if you save a default profile to your bios user profiles with not overclocking or special extreme settings you can always have your personal settings back to test the modules or go back to your actual state).
Bios v. 0922 was the most recent at that moment but v. 0925 (2023/03/15) was recently released.
Yes, you can try to flash to the new release version. Don’t go for the “beta v.1003”.
You can do it in the order you want.
If you can post and get into Windows with one module, then it could be easier to download the v0925 Bios and flash it.
Since you asked about what is that “rename thing” before, I presume you’ve never flashed the asus bios before. Do as follows:
Bios update
-Format a pendrive to FAT32
-Extract the downloaded BIOS file and run “BIOSRenamer.exe”
-That will open a Prompt window asking you to press any key to continue.
-ROG-STRIX-X670E-E-GAMING-WIFI-ASUS-0925.CAP file will be renamed to SX670EE.CAP
-Paste the SX670EE.CAP file into your pendrive
-Once in bios you have to go to Tools/ASUS EZ Flash 3
-Select your pendrive, chose SX670EE.CAP file and follow the instructions.
-System may reboot several times with a message on top of the screen “updating your bios…”
As a last resource, if nothing of mentioned before works and have nothing else to lose… yes, you may try that beta version.
EDIT:
Ah, about the mentioned VSOC, it is the SOC Voltage. That’s the voltage applied into the CPU, which controls the memory controller. A faulty CPU or CPU socket (bended pin) may prevent B1 and B2 to be detected. An incorrect lower voltage may prevent the same?
Someone mentioned the voltage requirements of your modules compared to the x2 16GB… I’m not an expert in that matter, and others may help you better. But it is very risky to change numbers there without a previous knowledge.
AI Tweaker\CPU SOC Voltage Set to manual
VDDSOC Voltage Override and type in the voltage. 1.05 (2xdimms) or 1.1 (4xdimms) or 1.15 (4xdimms, not quite stable 1.1v)
Please ask for others help to assist you. And confirm if those numbers are correct before proceed. As I said I’m not sure about that particular topic.
1 Like
Yes still got them. I was running with 2 of the sticks until the G.Skill arrived in A2 B2 so I assume the B2 slot is OK? I did not try A1 B1 but I did with the G.Skill and that did not work. (But also I didn’t know about CMOS reset then!)
Hang on you mean even if I add another stick into a 2nd slot of the SAME brand, I need to CMOS reset again? I have not been doing that. Just did once today before booting, and I put both G.Skill sticks in before powering on. Then removed 1 and it works but I didn’t CMOS reset again.
Yeah cool I will try - I prepared the thumb drive and did the rename. So reboot, hold DEL then go to the menu you mentioned - roger!
Bios 0925 never came out of beta before 1003 beta was released.
I am on 0922 on an x670E-E with no issues.
