Windows 11 : does not want RAM to be overclocked

Alphonse777 said:

I have to change 45 parameters manually ?

Click to expand...

No - it's only really the top six under GDM Disabled that have to be right. With earlier BIOSes I needed to tweak the VDDG and VDDP settings too (i.e. increase them a bit), but the final F36 and the later F37a and F37b BIOSes didn't need any tweaking for those settings.

By the way, you may already know this, but F36 is later than F36f. The lower case letter signifies a Beta BIOS, and the one without the lower case letter is the final, hopefully stable version. In practice, nearly all Beta BIOSes are quite stable, but some people like to stick to the ones without the lower case letters just in case.

Given the GSkill reference in @Ghot 's post above, you might want to manually change the top 4 settings to 19, 21, 21, 41.
Also, I'm not sure why you're showing 2t rather than 1t. If I recall correctly (and it's quite a big if) that is only necessary if pushing the Cas setting hard, and maybe using even values rather than odd values for Cas.

@Alphonse777
This is what mine looked like (in BLUE box). These are the important timings.

For your RAM, I would try the frequency, timings and voltage (in the RED boxes).
You should have similar settings in your BIOS, sort of like the ones I have in MY BIOS...





@Senecio

Download and run Aida64 and go to the Motherboard section to see which RAM modules you have and which timings each frequency supports. Using these timings should give you a stable system. If unsure increase the timings one or two steps.

spapakons said:

Download and run Aida64 and go to the Motherboard section to see which RAM modules you have and which timings each frequency supports. Using these timings should give you a stable system. If unsure increase the timings one or two steps.

Click to expand...

This is the OP's RAM...


The OP should try the numbers in the RED boxes, in post #23
The OP's CPU-Z screen shots are in post #9

Unfortunately, his motherboard manual doesn't "show" his actual timing's settings, or I would have posted a pic of them.
His manual just shows the timing section titles....
Which is weird, because he has a huge manual... 39 MB



Link to OP's motherboard (pdf), manual...

I know the OP's specs say ASUS AORUS... but ASUS doesn't make any AORUS motherboards.
AORUS is all Gigabyte.




Anyway... OP should start out with these settings (in the RED boxes)...
The OP's RAM is on his motherboard's Memory Support list. Screen shot of that, is in post #16.

This is NOT a pic from the OP's manual. This is just a guide.

The timing with the question mark, isn't shown in either CPU-Z or the manufacturer's specs.
When I had to do the same thing for my RAM, I couldn't get the comp to boot, if I left that number on Auto.

In my case I had to... guess at that timing (see post #23). I picked 14, and it... worked.
So for the OP's timings, I guessed at 21 for his RAM.

Hello,
Today I just changed to 3200 Mhz
I just put 32 x 100 Mhz in the BIOS I did not play with other parameters ... I was in a hurry, to be honest. I do not know if the Bios did something automatic with the 50 other parameters. Let's see how it goes...

Exactly what I suggested. Set the desired frequency and let others to auto.

A per today, and after two sleep sequences, everything goes well !
I'll put a solved status in few days, it disserves it.

I was not aware that Ryzen 9 3900x12 could not cope with 4000 Mhz Ram sticks ...
Simple question so what for those are sold ?

It depends what nominal frequency the CPU is and how it reaches that frequency, that is what is the FSB and what is the multiplier. The RAM typically operates at a multiple of the FSB, so if your FSB doesn't divide 4000 exactly to an integer number, the RAM will work at a lower frequency which is an exact multiple of the FSB, such as 3984, 3818, 3652 etc

Alphonse777 said:

A per today, and after two sleep sequences, everything goes well !
I'll put a solved status in few days, it disserves it.

I was not aware that Ryzen 9 3900x12 could not cope with 4000 Mhz Ram sticks ...
Simple question so what for those are sold ?

Click to expand...

The maximum specified frequency for the 3900X is 3200MHz. 4000MHz is considered to be overclocking. That doesn't mean that a motherboard/CPU combination can't run it.

I don't know about AMD, but for Intel, using "overclocked" RAM voids the processor's warranty. (I have personal sad experience.)

If possible switch to normal speed (cancel overclocking) before giving your computer for repair, so it will be done under Warranty.

For repair ? This is a computer that I have assembled myself. I never buy computer from big companies, they make a lot of money with poor components.

If you want the motherboard checked inside Warranty, just cancel overclocking before returning to the shop. My main computer is also custom built. Here in Greece we mostly build our computers from parts because it is cheaper and we can choose what we put inside. Usually a company will order OEM computers from HP or Dell or whatever. An individual has more chances to build a custom computer than buy an OEM model.

[SOLVED]
I did many cycles of sleep / hibernate and restart and it works fine now with 3200 Mhz
I would like to thank this community. I did not know that Ryzen 9x can "only" cope with 3200 Mhz RAM stick...

Well, of course it can "cope" with more than that, typical enthusiasts overclocks being 3800 Mhz. You are right that the official (recommended) RAM speed is 3200 Mhz. When I bought my current RAM in 2020 I was able to reach 3600 Mhz quite easily (that is what the RAM is rated for). I have had no problems in the three years since installing the RAM, running at that overclock.
I'm glad you have achieved a stable result for your system.

Sorry but this is [NOT SOLVED]
I have two crashes on PC wake up after sleep.When I'm looking to the crash dump, here what I have ->

FAULTING_IP:
nt!KeSetEvent+1db
fffff806`0e6c5a3b 488b00 mov rax,qword ptr [rax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0xA

PROCESS_NAME: System

BAD_PAGES_DETECTED: 284a7

LAST_CONTROL_TRANSFER: from fffff8060e83e2a9 to fffff8060e828c50

STACK_TEXT:
ffffb308`2093a5f8 fffff806`0e83e2a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffb308`2093a600 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff8060e6c5209-fffff8060e6c520a 2 bytes - nt!MiAllocateSlabEntry+2e9
[ 00 de:80 d2 ]
fffff8060e6c5519-fffff8060e6c551e 6 bytes - nt!MiCheckProcessShadow+79 (+0x310)
[ 68 df be 7d fb f6:10 2d 5a b4 68 d1 ]
fffff8060e6c5569-fffff8060e6c556d 5 bytes - nt!MiCheckProcessShadow+c9 (+0x50)
[ d0 be 7d fb f6:20 5a b4 68 d1 ]
fffff8060e6c557c-fffff8060e6c5580 5 bytes - nt!MiCheckProcessShadow+dc (+0x13)
[ d7 be 7d fb f6:27 5a b4 68 d1 ]
fffff8060e6c5689-fffff8060e6c568e 6 bytes - nt!MiCheckProcessShadow+1e9 (+0x10d)
[ 68 df be 7d fb f6:10 2d 5a b4 68 d1 ]
24 errors : !nt (fffff8060e6c5209-fffff8060e6c568e)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
================================================================================

It does not like that ... still at 3200 MHZ
What a pain in the n...
What should I do ?

Ok... I'm looking at GSkill RAM configurator.
For 32GB RAM (4x8GB), the fastest they show is 3600Mhz.

For pretty much all size combinations... the fastest they show is 3600Mhz.
I would aim for 3600Mhz, and try these timings...

You may have to adjust the timings a bit. The higher the numbers used for the timings, the easier they are to get stability. BUT... the higher the timings, the slower the RAM runs, even though it's still set to 3600Mhz.
The overall object of the game when OCing RAM is to get the highest frequency, with the "tightest" timings (lowest numbers).






Your only other real option is to go on overclock.net, spend about a month learning how to overclock, and then stress testing over and over, till you get a stable overclock.

Ghot,
Ok I can try those and see.

Your only other real option is to go on overclock.net, spend about a month learning how to overclock, and then stress testing over and over."

Click to expand...

That was my feeling at some point. But if this turns out to be the case, the Bios is really totally useless to help out. This would be a real pity.

Alphonse777 said:

Ghot,
Ok I can try those and see.



That was my feeling at some point. But if this turns out to be the case, the Bios is really totally useless to help out. This would be a real pity.

Click to expand...

No. The BIOS is where you should overclock. It just takes some practice and a lot of stress testing.

@Dude

BIOS does not have a stress testing embedded to it ? This is simply read and write memory like does MEMTEST.