cancel
Showing results for 
Search instead for 
Did you mean: 

X670 resource

Shamino
Moderator

ill use this thread to collect some new test bioses for the boards, maybe also to explain some less understood options

to disable cores ccd go here and choose ccd xx bit map down core.
each ones stand for an enabled core
best to disable from the back, ie:
110000
instead of 0011000
after selection press downcore apply changes or discard if made mistake

ocpak/octools

FAQ:
7950x not boosting pass 5.5G -> check that CStates is not disabled
Detailed Explanation on CState Boot Limiter


Test BIOSes:

new:
X3D OC Preset for those MB with asynch BCLK Support: (for simple slight perf boost for X3D)
97792

DOCP/EXPO Tweaked: (for simple timings tightening)
97793

strixe-e 1515 

strixe-f 1515 

strix e a 1515 

crosshair hero 1515 

crosshair gene 1515 

crosshair extreme 1515 

creator 670 1515

creator b650 1515

strix 650E I

strix 670 itx

 

 

for crosshair and strix e-e:

explanation of segment2 Loadline:

dualseg.jpg

customize a heterogenous loadline for a dual segment workload range.

example above shows loadline=L6 when current is in range of 0~40A, and Level4 when current is above 40A.

 

 

 


Adds for x3d

dynamic ccd priority switch with core flex, os / driver agnostic so win10 win11 ok

97403

97404

Algo as follows:
If condition reached and ccd0 specified, then check current mem/cache activity > threshold and hysteresis reached, if fulfilled then switch
If condition reached and ccd1 specified, then check current mem/cache activity <=threshold and hysteresis reached,, if fulfilled then switch
Default hysteresis =4

Can combine multiple algos for ccd priority so combinations are wide

works on non x3d too but of course senseless on it. detailed explanation here.

498 Views
2,054 REPLIES 2,054

kamyk155 wrote:
I confirm too - strix e-e POWER DOWN enabled and MCR enabled - nice and fast boot without BSOD - still testing in windows 11.

I found another problem:
- BIOS freeze when I was inside checking settings. Maybe it is connected with USB power lost ? Mouse didn't move, keyboard didn't work. It stay freeezed for about 20-30sec and then CTRL+ALT+DEL worked or it restarted itself. Computer starts again without any info about error. It was my 2nd time in bios 1001.


StrixE-E @ 1001

I confirm the same problem as freezing inside the bios,
where the board seems to be running fine (temperatures are moving) but the keyboard and mouse are dead.

prace.matlas wrote:
StrixE-E @ 1001

I confirm the same problem as freezing inside the bios,
where the board seems to be running fine (temperatures are moving) but the keyboard and mouse are dead.


Same problem. StrixE-F@1001. It happens when mcr is enabled. Bios doesn't freeze when I disable mcr.

kamyk155 wrote:
I confirm too - strix e-e POWER DOWN enabled and MCR enabled - nice and fast boot without BSOD - still testing in windows 11.

I found another problem:
- BIOS freeze when I was inside checking settings. Maybe it is connected with USB power lost ? Mouse didn't move, keyboard didn't work. It stay freeezed for about 20-30sec and then CTRL+ALT+DEL worked or it restarted itself. Computer starts again without any info about error. It was my 2nd time in bios 1001.


I have tested just about every BIOS version from the launch of these boards and i have had this happen several times. Whilst i can't give a definitive answer, what i can say is it always happens when the BIOS version is one that causes BSOD on windows load and always happens when i have DOCP or EXPO enabled, depending on the RAM kit installed.

BIOS version 0805 is currently the only one i can use and get support for my 4090 and enabled EXPO without a BSOD or BIOS locking up, the only way i have got round this is by clearing CMOS and flashing back to a know version that is stable

johnnync21
Level 7
bios for strix-i with 1.0.0.6 ???

RobrPatty
Level 10
From Shamino. Tested and confirmed by myself:

Bios 1001: MCR enabled will be stable and usable (no more BSODs...), if in the bios setting of DRAM TIMING CONTROL > DRAM POWER DOWN is set to enabled, too.

Conclusion: For now, MCR and DRAM POWER DOWN have to be enabled at the same time for maintaining a stable system.


Stabilizes X670E-E

kamyk155
Level 10
Today I had again USB ports disconnect - one time for few seconds.
I set in all windows power plans USB selective suspends to OFF but it didn't help.

kamyk155 wrote:
Today I had again USB ports disconnect - one time for few seconds.
I set in all windows power plans USB selective suspends to OFF but it didn't help.


In Windows Device Manager, turn off Power Management for all USB Hubs you can find in there. Should fix the problem.
R9 7950X - ASUS X670E Crosshair Extreme (bios 0803) - 32GB HyperX Fury Beast @6200c32 - Corsair H150i Pro - ASUS RTX3080 TUF OC V2 - Phanteks P400A - Corsair RM850 - WD SN850

xeizo wrote:
In Windows Device Manager, turn off Power Management for all USB Hubs you can find in there. Should fix the problem.


Turned off permission to turn off for power saving on all 13 hubs - now I need to check.

I've managed to get my ROG CROSSHAIR X670E EXTREME with R9 7950X and 2x32 G.SKILL 6000MHz CL30 Trident Z5 mostly stable.
I had to use DOCP 2 (DOCP 1 doesn't work) and enabling MCR causes massive amount of memory errors (or no POST).
System posts with following timming, but it takes around 70s (just over a minute) to get to ASUS logo/bios.
97770

On top of that I experience weird issue, where I get a couple of memory errors in memtestx86+ when I jump into it quickly before CPU reaches something like 50*C. It doesn't seems to be just "cold boot" (total power off of the machine) issue as it doesn't happen if I just switch powesupply off for a short time. It also doesn't happen if I wait in bios (for few minutes) before booting memtestx86+. These memory errors happen almost immediately, but after that there are no more errors even after few memtest passes.
This behavior did not change with 805 or 922.

I honestly never seen something like this, any ideas are wellcomed.

For reference, here are my timings from 0805, same RAM as the prior post, using EXPO 1 (I assume EXPO = DOCP):