The servers dont repond that I have reached some limit (e.g. the 100 tasks limit), just that no work is avaiable for setiathome v8.

The servers dont know the internal debit of my boinc client. It simply responds to the request from my client. If my client asks for 50.000 seconds of work, the server tries to answer that request based upon previous numbers for crunch time and of course given the 100WU restriction and availability of work.

For some reason that doesn't work. I would like to know the reason why.

I made settings for 3533, 3400, and 3200, all with the safe calculations.

3533 didn't boot. And I honestly didn't expect it to.

3400 did boot, but windows crashed loading the desktop.

Tried 3333 with the 3400 settings, and it booted and started correctly. Running RAM tester gave me an error within 1 minute.

3200 with safe settings, booted fine, but RAM tester threw an error after about 30 seconds.

3200 with bios defaults, but with 48 ohm ProcODT, runs fine. Default settings are a lot more relaxed, as far as I can see.

So, I guess I'll stick to 3200 at (almost) default for now, which was really also what I was hoping for.

My only problem with this is that the system should be able to run at the safe settings (at least at 3200), as they make sure that the specs of the actual ram is maintained. So the bios / agesa is not doing what it should.

Finding that memtest64, wouldnt find errors, even with settings that eventually crashed, I tried to read up on it.

I found a guy promoting "RAM test" (by Karhu software). A program that it seems is basically made for testing RAM on Ryzen CPU's (will work on others too)
The downside was, it costs 10$ (9.99). After some time thinking about it, I decided to try it, and bought a license. Its not that much money anyway.

And it has proven to be a good decision. I can run the program at 3200 for an hour (and more) without errors, but at 3266 I get an error from the program within 20 seconds (at a setting where the system could run 12+ hours yesterday).
You can set the program to stop on errors or keep running. And you can set it to beep on eroors.

It has helped me very much in finding reliable settings. I found that setting back GDM to auto did nothing, the system is still stable (perhaps its on pr. default at 3200), but the ProcODT has to be set at 48 ohm on my system, higher than that I get memory errors.

I like the simplicity of it, and I like how fast it detects errors, at least on my system, when I push things too much.

There have been varying reports of succes, but on my system, with my G-Skill FlareX, that are rated to 3200Mhz, I seem to have gained complete stability at 3200Mhz. At least it ran for nearly 24h without crashing.

Now I have even been able to boot and run at 3400Mhz, which I decided to try due to reports from another user with the same RAM. I have never been able to even boot at that speed before.

Even at 3400, the system seems stable.

I'll have to run it for some days before I can say for sure if its reliable, but it does seem the 4011 bios is an improvement over 4009.