Jump to content

Updated BIOS for the ASUS ROG Crosshair X670E GENE, what am I missing?

So the ASUS website mentions they put a limit in place to protect the motherboard and CPU (My R9 7950X). However, after the bios update it states it's using 1.350v.

 

Did I misunderstand something?

image.thumb.png.794bbe75100bde7b972c38c3a762745c.png23-04-2816-07-276674.thumb.jpg.871821a8e032c5289ae19a90a04b15fe.jpg

{"anno":"2023Q2","cpu":"AMD Ryzen 9 7950X","board":"Asus ROG Crosshair X670E GENE","ram":{"brand":"Kingston","type":"Fury Beast","size":"64GB","specs":{"version":"DDR5","mts":"6,000MT/s","kit":"2x32GB","cas":36,"trcd":38,"trp":38,"serial":"KF560C36BBEK2-64"}},"gpu":"PowerColor Red Devil AMD Radeon 7900XTX 24GB","storage":[{"qty":1, "drive":"Kingston Fury Renegade","size":"1TB","interface":"NVMe PCI-e 4.0 x4","specs":{"mtbf":"1,800,000hr","seq-read":"7,300MB/s","seq-write":"6,000MB/s"},"raid":null},{"qty":2,"drive":"Kingston NV2","size":"2TB","interface":"NVMe PCI-e 4.0 x4","specs":{"mtbf":"1,500,000hr","seq-read":"3,500MB/s","seq-write":"2,800MB/s"},"raid":0}],"psu":"Seasonic Prime PX-1300","cooling":["Noctua NH-D15S chromax.black","Thermal Grizzly Kryonaut"],"case":{"brand": "Fractal Design","type":"Torrent Compact","color":"black","rgb":false},"link":"https://pcpartpicker.com/list/p9JVGP","images":"https://photos.app.goo.gl/tZsgjkqaaT4HS1i67"}

Link to comment
Share on other sites

Link to post
Share on other sites

@RONOTHAN## I got the same reply on another forum. I was looking in the wrong section, however it's still going above it. See attachments.

 

23-04-2818-22-046679.thumb.jpg.b2bd03e2d1570c70f7a80d73288098a3.jpg23-04-2818-24-526680.thumb.jpg.a7b50c450df9cb38746ead491760f717.jpg

(memory settings left: "auto", right: "EXPO 1")

{"anno":"2023Q2","cpu":"AMD Ryzen 9 7950X","board":"Asus ROG Crosshair X670E GENE","ram":{"brand":"Kingston","type":"Fury Beast","size":"64GB","specs":{"version":"DDR5","mts":"6,000MT/s","kit":"2x32GB","cas":36,"trcd":38,"trp":38,"serial":"KF560C36BBEK2-64"}},"gpu":"PowerColor Red Devil AMD Radeon 7900XTX 24GB","storage":[{"qty":1, "drive":"Kingston Fury Renegade","size":"1TB","interface":"NVMe PCI-e 4.0 x4","specs":{"mtbf":"1,800,000hr","seq-read":"7,300MB/s","seq-write":"6,000MB/s"},"raid":null},{"qty":2,"drive":"Kingston NV2","size":"2TB","interface":"NVMe PCI-e 4.0 x4","specs":{"mtbf":"1,500,000hr","seq-read":"3,500MB/s","seq-write":"2,800MB/s"},"raid":0}],"psu":"Seasonic Prime PX-1300","cooling":["Noctua NH-D15S chromax.black","Thermal Grizzly Kryonaut"],"case":{"brand": "Fractal Design","type":"Torrent Compact","color":"black","rgb":false},"link":"https://pcpartpicker.com/list/p9JVGP","images":"https://photos.app.goo.gl/tZsgjkqaaT4HS1i67"}

Link to comment
Share on other sites

Link to post
Share on other sites

5 hours ago, McBrown83 said:

@RONOTHAN## I got the same reply on another forum. I was looking in the wrong section, however it's still going above it. See attachments.

 

23-04-2818-22-046679.thumb.jpg.b2bd03e2d1570c70f7a80d73288098a3.jpg23-04-2818-24-526680.thumb.jpg.a7b50c450df9cb38746ead491760f717.jpg

(memory settings left: "auto", right: "EXPO 1")

It could be the placement of the voltage sensor, it could be closer to the VRM output than at the CPU with a 50mV drop across. The other option if you're concerned is to just manually set the SOC voltage if you want to have it lower, setting it to say 1.2V set, and it should have that sensor running st around 1.25V. 

Link to comment
Share on other sites

Link to post
Share on other sites

Okay.... I don't trust the motherboards internal reporting anymore...
 

 

{"anno":"2023Q2","cpu":"AMD Ryzen 9 7950X","board":"Asus ROG Crosshair X670E GENE","ram":{"brand":"Kingston","type":"Fury Beast","size":"64GB","specs":{"version":"DDR5","mts":"6,000MT/s","kit":"2x32GB","cas":36,"trcd":38,"trp":38,"serial":"KF560C36BBEK2-64"}},"gpu":"PowerColor Red Devil AMD Radeon 7900XTX 24GB","storage":[{"qty":1, "drive":"Kingston Fury Renegade","size":"1TB","interface":"NVMe PCI-e 4.0 x4","specs":{"mtbf":"1,800,000hr","seq-read":"7,300MB/s","seq-write":"6,000MB/s"},"raid":null},{"qty":2,"drive":"Kingston NV2","size":"2TB","interface":"NVMe PCI-e 4.0 x4","specs":{"mtbf":"1,500,000hr","seq-read":"3,500MB/s","seq-write":"2,800MB/s"},"raid":0}],"psu":"Seasonic Prime PX-1300","cooling":["Noctua NH-D15S chromax.black","Thermal Grizzly Kryonaut"],"case":{"brand": "Fractal Design","type":"Torrent Compact","color":"black","rgb":false},"link":"https://pcpartpicker.com/list/p9JVGP","images":"https://photos.app.goo.gl/tZsgjkqaaT4HS1i67"}

Link to comment
Share on other sites

Link to post
Share on other sites

Okay, had to see it with my own eyes... Now I believe it!

 

VSOC seems to work properly now with bios v1401 (beta)

 

 

{"anno":"2023Q2","cpu":"AMD Ryzen 9 7950X","board":"Asus ROG Crosshair X670E GENE","ram":{"brand":"Kingston","type":"Fury Beast","size":"64GB","specs":{"version":"DDR5","mts":"6,000MT/s","kit":"2x32GB","cas":36,"trcd":38,"trp":38,"serial":"KF560C36BBEK2-64"}},"gpu":"PowerColor Red Devil AMD Radeon 7900XTX 24GB","storage":[{"qty":1, "drive":"Kingston Fury Renegade","size":"1TB","interface":"NVMe PCI-e 4.0 x4","specs":{"mtbf":"1,800,000hr","seq-read":"7,300MB/s","seq-write":"6,000MB/s"},"raid":null},{"qty":2,"drive":"Kingston NV2","size":"2TB","interface":"NVMe PCI-e 4.0 x4","specs":{"mtbf":"1,500,000hr","seq-read":"3,500MB/s","seq-write":"2,800MB/s"},"raid":0}],"psu":"Seasonic Prime PX-1300","cooling":["Noctua NH-D15S chromax.black","Thermal Grizzly Kryonaut"],"case":{"brand": "Fractal Design","type":"Torrent Compact","color":"black","rgb":false},"link":"https://pcpartpicker.com/list/p9JVGP","images":"https://photos.app.goo.gl/tZsgjkqaaT4HS1i67"}

Link to comment
Share on other sites

Link to post
Share on other sites

Hopefully someone can clear this up...from what I've gathered this is only a 'X3D'-related issue. 
Afaik the only product failures involved a 3D chipset, but there are some reporting headlines encompassing all of the 7000 series, and a bunch of people like us wondering/worrying if this might effect us in a slightly different situation (the Asus mobo angle).  From my searching/reading the following quote segment stood out....

"Ryzen 7000X3D processors do not allow for CPU ratio or CPU core voltage tuning (CPU overclocking) but do allow for performance tuning and DRAM overclocking via PBO2 and EXPO memory. To support EXPO and/or memory overclocking at DDR5-6000 and beyond, SoC voltage has to be sufficiently increased to ensure compatibility and stability..."   https://wccftech.com/amd-root-cause-ryzen-7000-burnout-issues-related-to-higher-cpu-voltages-official/
 

Now, I'm only half literate with this level of stuff...but to me that suggests the non-3D chipsets aren't seeing the (same level of) increased SOC voltage, because they can attain a boost via ratio or Core Voltage [seems like core voltage is listed as 'VDDCR_VDD'].
Out of curiousity, and a little anxiousness, I monitored my voltages idle and under load...'VDDCR_SOC Voltage' sits at 1.235 every time I look at it [but does show a 1.234-1.237 variance in min/max logs].  Meanwhile 'VDDCR_VDD Voltage' does vary quite drastically, from 1.237 up to 1.399, but from what I can tell that is normal.
Add in that I've never seen CPU temps above 81C, and browsing such as now sits at 50C leaves me with zero indications that my 7950x is in any danger...that said, I am kind of relying on that quote to represent the effectual difference wrt each chipset.  I'm still sitting on UEFI 0809 since everything has been seemingly perfect....certainly prepared to update if the above is wrong, but I've yet to see any solid reason to be concerned. 

[Edit:  It seems the ASUS mobo angle to this is more about manual voltage settings/manual overclocking...older bios do bring the potential for damage to any 7000series chip if you're manually playing with voltages and go too far.  And the fact that AGESA 1.0.0.7 is going to be coming soon with other (non-Vsoc-related) measures suggests that there's likely still some vulnerability even with the most recent bios, making 1.0.0.6 seem like only half of 'the fix'.  My assessment above was definitely lacking the full picture, and it looks like these boards should be flashed (though waiting for 1.0.0.7 might fly...supposed to only be a few more days).]

Edited by JLssg4
update/add
Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×