Strange behaviour from X670e Tomahawk

Joined
Jul 31, 2023
Messages
149
Greetings good people,

I have been rocking an X670e Tomahawk for almost 2 years now, Recently, about 10 days or so, I upgraded the BIOS to ver. 7E12v1H, which is the latest at the time of typing this. I also reinstalled a copy of Windows 11. All is well execpt that sometimes when I boot my PC from a cold boot, the PC takes longer than normal to boot into Windows and windows feels very sluggish like even the mouse pointer jumps around and clicking or trying to open any app feels impossible—turning the PC off then on again from a cold boot fixes this.
PC specs :

7800X3d
2x32GB DDR5 6000T Gskill RAM
4080 SuprimX
512 GB Samsung 960 pro SSD for booting
2TB Kingston Fury SSD
1TB Samsung EVO 840 SATA
1TB Seagate HD
Antec 1350w PSU
 
Greetings good people,

I have been rocking an X670e Tomahawk for almost 2 years now, Recently, about 10 days or so, I upgraded the BIOS to ver. 7E12v1H, which is the latest at the time of typing this. I also reinstalled a copy of Windows 11. All is well execpt that sometimes when I boot my PC from a cold boot, the PC takes longer than normal to boot into Windows and windows feels very sluggish like even the mouse pointer jumps around and clicking or trying to open any app feels impossible—turning the PC off then on again from a cold boot fixes this.
PC specs :

7800X3d
2x32GB DDR5 6000T Gskill RAM
4080 SuprimX
512 GB Samsung 960 pro SSD for booting
2TB Kingston Fury SSD
1TB Samsung EVO 840 SATA
1TB Seagate HD
Antec 1350w PSU


what voltages are you typing in the bios?
 
so is there still issue with the newset bios? VOC for me is 1.300 auto 7800x3d 4090RTX , PCIe seems always stay on PCIE 4x 16x , no matter which bootup i make cold or warm

I am not sure if the new bios caused is though, my Team Z540 2TB Nvme and Samsung 9100 Pro with heatsink 2TB but both died one after the other at the windows update Nvme stupid issue, so I am sure Samsung 9100 didn't have bad firmware, because there was no update to their firmware and reverting back to 1.J0 it works fine over months
1780362806270.png
 
Last edited:
With older AGESA pre 1.2.0.3 I always set the SOC voltage to 1.3 or lower. I for some reason assumed that with AGESA 1.2.0.3 and after this issue of the SOC voltage was fixed, but obviously it progressed even more! Setting the value manually so far has resulted in a stable boot, though it is too early for me to say so; the issue is so random that it could happen multiple times a day or once a month.
 
you have to stress test the ram for stability, voltages like MEM VDD, MEM VDDQ and CPU VDDIO cannot be left in auto nor just by setting EXPO, if you set EXPO then you stress test and adjust voltages ad needed, if you are setting the RAM at 6000 MT/s then you don't need Vsoc more than 1.2v even 1.18v should be more than enough, BUT every setup is different there could be an scenario where you need 1.22 or 1.24 for RAM at 6000 MT/s
 
you have to stress test the ram for stability, voltages like MEM VDD, MEM VDDQ and CPU VDDIO cannot be left in auto nor just by setting EXPO, if you set EXPO then you stress test and adjust voltages ad needed, if you are setting the RAM at 6000 MT/s then you don't need Vsoc more than 1.2v even 1.18v should be more than enough, BUT every setup is different there could be an scenario where you need 1.22 or 1.24 for RAM at 6000 MT/s
The first thing I do when I assemble a new PC is to test the RAM for a full day. No issues there.
 
Back
Top