Ryzen 7000 / Zen 4 Owner's Club

[J7SC_Orion]

On 09/10/2023 at 15:33, richardmeppelin said:

 

 

Ye i saw that indeed. 

 

I think expo is better for if there are any issues i can always revert back to expo settings that work but maybe that is the lazy/faulty way lol. 

I want stability for mostly gaming. 

 

I was tweaking on my previous system which was an AMD 5600x with FlareX 3200MHz RAM tweaked to 3600 MHz lol. 

So i am not an total noob but definetaly A LOT to learn about DDR5 xD. 

 

Thnx for the help, much obliged! 

 

As @The Pook mentioned, the DDR5 scene has been much murkier to unkey as of late and 'id' than DDR4 was (I only used GSkill Samsung-B - GTZR on AM4, Intel CPUs). Re. DDR5, I have a new 2x24 GB GSkill M-die kit and couldn't be happier, whether running at > CL 36 8000 or CL 30 6400. Some earlier results I posted > here, > here and > here  (1:1, 1:2).

 

All that said, technically, my one and only DDR5 kit is Intel-spec RAM but XMP does show in the bios of my 670E Master / 7950X3D combo as an option and works fine. Same story before with my 5950X DDR4 CL14 4000 - Intel-spec RAM . If both the die designation and 'EXPO' are important to you, I would make a short list and contact for example GSkill and see if they will confirm (they should know, given serial numbers and production date)...

 

 

Edited October 10, 2023 by J7SC_Orion

[Hurricane28]

7 hours ago, J7SC_Orion said:

 

As @The Pook mentioned, the DDR5 scene has been much murkier to unkey as of late and 'id' than DDR4 was (I only used GSkill Samsung-B - GTZR on AM4, Intel CPUs). Re. DDR5, I have a new 2x24 GB GSkill M-die kit and couldn't be happier, whether running at > CL 36 8000 or CL 30 6400. Some earlier results I posted > here, > here and > here  (1:1, 1:2).

 

All that said, technically, my one and only DDR5 kit is Intel-spec RAM but XMP does show in the bios of my 670E Master / 7950X3D combo as an option and works fine. Same story before with my 5950X DDR4 CL14 4000 - Intel-spec RAM . If both the die designation and 'EXPO' are important to you, I would make a short list and contact for example GSkill and see if they will confirm (they should know, given serial numbers and production date)...

 

 

 

 

Yes indeed, that was what i am afraid of. O well, its time to roll the dice i guess lol. 

 

I noticed that i am missing lot of RAM setting in my bios, my 670x Aorus Elite AX is not that sophisticated as your master board. 

Perhaps its good idea to upgrade to the X670 master, it has better features too than my board. 

[Hurricane28]

My first score of today: 

 

Nice latency. 

[J7SC_Orion]

8 hours ago, richardmeppelin said:

 

 

Yes indeed, that was what i am afraid of. O well, its time to roll the dice i guess lol. 

 

I noticed that i am missing lot of RAM setting in my bios, my 670x Aorus Elite AX is not that sophisticated as your master board. 

Perhaps its good idea to upgrade to the X670 master, it has better features too than my board. 

 

...the 670E Master has quickly become one of my fav boards, especially from a price-performance POV. It does come with 'eclk' options rather than just 'bclk' and has a great memory topography and the full PCIe 5 treatment. It does have it quirks, for example, the CMOS reset is via a jumper / bottom right of the board, instead of a button on the IO panel. All in all, a great X670E option.

[neurotix]

6 hours ago, richardmeppelin said:

My first score of today: 

 

Nice latency. 

Isn't this significantly better than what you were doing before? Is it using the timings I gave you? More importantly, is it stable?

 

I suggest testing it with membench in the old Ryzen DRAM Calculator, do custom and then do 20000MB and 1600 for task scope. This will run memtestCL on 16 threads to 105% coverage per thread.

 

You can also use GSAT but let's not get into that again

[Hurricane28]

1 hour ago, J7SC_Orion said:

 

...the 670E Master has quickly become one of my fav boards, especially from a price-performance POV. It does come with 'eclk' options rather than just 'bclk' and has a great memory topography and the full PCIe 5 treatment. It does have it quirks, for example, the CMOS reset is via a jumper / bottom right of the board, instead of a button on the IO panel. All in all, a great X670E option.

 

 

I hear ya, 

 

Well my board is a nice beginner but i am not an beginner and i do need/want the extra features the Master has. 

Audio is really bad on my board also.

 

I guess i wait for another month until its black friday and go from there to save some cache lol. 

[Hurricane28]

10 minutes ago, neurotix said:

Isn't this significantly better than what you were doing before? Is it using the timings I gave you? More importantly, is it stable?

 

I suggest testing it with membench in the old Ryzen DRAM Calculator, do custom and then do 20000MB and 1600 for task scope. This will run memtestCL on 16 threads to 105% coverage per thread.

 

You can also use GSAT but let's not get into that again

 

 

Not really, look: 

 

I mean, the latency is lower but not that much. Its more stable too as i haven't run in any issues yet. 

 

I adjusted more voltages too, perhaps that did the trick. It is M die but the later M die cos its made in late 2023, so i guess this is the better M die? 

 

The timings i used was from Buildzoid as i wanted to know why it crashed an all weird but i think its power down mode being buggy. Anything but auto gives freezes and BSOD for some reason, kinda weird. I remember it has to do with CR1 or CR2? If running CR2 you can disable it. 

 

What is GSAT? never heard of that tbh. 

[J7SC_Orion]

17 minutes ago, richardmeppelin said:

 

 

I hear ya, 

 

Well my board is a nice beginner but i am not an beginner and i do need/want the extra features the Master has. 

Audio is really bad on my board also.

 

I guess i wait for another month until its black friday and go from there to save some cache lol. 

 

...I got my 670E Aorus Master on sale as well, ditto for the RAM. BTW,  in addition to Neurotix' suggestion, Techpowerup's memtest64 is very good and, well, stressfull judging by the CPU and DDR5 temps it can generate. 10 error-free loops is what I use as the 'pre-screen' for shortlisted, potential RAM settings.  This test will start to fail after 4 - 5 loops if your DDR5 gets too hot / has not enough airflow. Then there's the old stand-by: y-cruncher, it will reboot your system if you are too frisky with your settings, and of course OCCT's RAM tests, including Linpack. Finally, with a single CCD CPU, going to 1:2 does not make sense according to Buildzoid as the latency 'cost' cannot be outweighed by the potential benefits. So focusing on tight but safe (voltages, temps) primaries and secondaries is the way forward, IMO.

 

[neurotix]

4 minutes ago, J7SC_Orion said:

 

...I got my 670E Aorus Master on sale as well, ditto for the RAM. BTW,  in addition to Neurotix' suggestion, Techpowerup's memtest64 is very good and, well, stressfull judging by the CPU and DDR5 temps it can generate. 10 error-free loops is what I use as the 'pre-screen' for shortlisted, potential RAM settings.  This test will start to fail after 4 - 5 loops if your DDR5 gets too hot / has not enough airflow. Then there's the old stand-by: y-cruncher, it will reboot your system if you are too frisky with your settings, and of course OCCT's RAM tests, including Linpack. Finally, with a single CCD CPU, going to 1:2 does not make sense according to Buildzoid as the latency 'cost' cannot be outweighed by the potential benefits. So focusing on tight but safe (voltages, temps) primaries and secondaries is the way forward, IMO.

 

 

I'll have to check out memtest64 myself. I just used memtestCL in Ryzen DRAM Calc, and 3 hours of GSAT in Linux.

 

kaliz was nice enough to give me some suggested timings for 8000Mhz, marked with suggestions in red for what to raise, on Orion's loose 8000MHz timings set. I also used 1.1 VDDP, 1.05v VDDG_CCD, and 0.950v VDDG_IOD, as well as 1.45v MEM_VDD. Unfortunately it failed instantly with errors constantly being generated in memtestCL.

 

So, this is the best I can do for now. Tbh I don't know if it's the sticks, the motherboard, the IMC or what but I cannot do 8000 stably (I can bench on it however)

 

 

[ENTERPRISE]

23 hours ago, J7SC_Orion said:

 

 Apart from the particular RAM sticks you have, a lot also has to do with the specific CPU's memory performance, and of course board topography and even bios version. I usually shortlist 2 - 3 potential settings via initial RAM tests, ie. 10 loops of TPU/Memtest64 error-free.  Then I run each of the settings through some memory-sensitive benchies and games, and the 'winner' gets the long stress test treatment. If that doesn't make it through long tests w/o errors, the runner up gets a try... Without short-listing first, you might be doing this for weeks. 

 

For sure, possibly in future BIOS releases this will be possible, but for now it is not something I will chase, and even then depending on the lottery, it may never be possible. 

 

I have now finished my RAM OC journey for now after getting 6400 stable with 2100 FCLK, I get 62.7ns on the latency which is not too bad. Depending on future BIOS releases with access to other settings (If MSI decide to include them) and more mature AGESA, I may be able to push further. 

 

I will get a ZenTimings Screenie soon. 

[neurotix]

33 minutes ago, ENTERPRISE said:

 

For sure, possibly in future BIOS releases this will be possible, but for now it is not something I will chase, and even then depending on the lottery, it may never be possible. 

 

I have now finished my RAM OC journey for now after getting 6400 stable with 2100 FCLK, I get 62.7ns on the latency which is not too bad. Depending on future BIOS releases with access to other settings (If MSI decide to include them) and more mature AGESA, I may be able to push further. 

 

I will get a ZenTimings Screenie soon. 

Can you also post AIDA64 please?

[ENTERPRISE]

9 minutes ago, neurotix said:

Can you also post AIDA64 please?

Will do.

[Hurricane28]

BIOS locked for me again.. 

 

Idk what happens but just dialed the Builzoid things in and all is fine untill its not lol. Just freezes and Mouse feels laggy in BIOS too.. 

 

Had to reboot several times and completely reset the BIOS in order to make it work again. Even in EXPO settings the BIOS tripped out.. 

 

I know its an beta BIOS but c'mon this is terrible. So back to square one l guess lol.

[neurotix]

14 minutes ago, richardmeppelin said:

BIOS locked for me again.. 

 

Idk what happens but just dialed the Builzoid things in and all is fine untill its not lol. Just freezes and Mouse feels laggy in BIOS too.. 

 

Had to reboot several times and completely reset the BIOS in order to make it work again. Even in EXPO settings the BIOS tripped out.. 

 

I know its an beta BIOS but c'mon this is terrible. So back to square one l guess lol.

Sorry to hear that. Perhaps you should give my timings a try?

 

Maybe there's something wrong with your RAM, have you tried switching channels (if you have 2 sticks) or reseating the memory? Maybe you need to roll back your BIOS to a non beta? Also, could it be the motherboard?

 

Are you using PBO? If you are, try lowering your max boost clock (if it's at +200). Perhaps it's a CPU stability issue and not the RAM at all?

 

Hope this helps.

[J7SC_Orion]

22 minutes ago, richardmeppelin said:

BIOS locked for me again.. 

 

Idk what happens but just dialed the Builzoid things in and all is fine untill its not lol. Just freezes and Mouse feels laggy in BIOS too.. 

 

Had to reboot several times and completely reset the BIOS in order to make it work again. Even in EXPO settings the BIOS tripped out.. 

 

I know its an beta BIOS but c'mon this is terrible. So back to square one l guess lol.

 

Which bios ? I am still on 13c instead of 13d, because bugs usually accompany a new bios release... 

 

[Hurricane28]

7 minutes ago, neurotix said:

Sorry to hear that. Perhaps you should give my timings a try?

 

Maybe there's something wrong with your RAM, have you tried switching channels (if you have 2 sticks) or reseating the memory? Maybe you need to roll back your BIOS to a non beta? Also, could it be the motherboard?

 

Are you using PBO? If you are, try lowering your max boost clock (if it's at +200). Perhaps it's a CPU stability issue and not the RAM at all?

 

Hope this helps.

 

Ye im gonna try your timings tomorrow, getting late again lol. 

 

Its just weird that the entire time it was stable and all of a sudden it went south real quick lol. 

 

I personally think its the BIOS man, im gonna try your timings tomorrow and some ram testings, if that doesnty work i go flash other "stable" BIOS and stick with it until new "stable" BIOS.  

[Hurricane28]

7 minutes ago, J7SC_Orion said:

 

Which bios ? I am still on 13c instead of 13d, because bugs usually accompany a new bios release... 

 

 

Latest one with AGESA 1.0.0.7. 1.0.8.0 is on its way but not here yet.. Its an D BIOS so it should be close of "stable" but sadly its not. What AGESA are you on and what is your max ram speed etc?

[ENTERPRISE]

19 minutes ago, richardmeppelin said:

BIOS locked for me again.. 

 

Idk what happens but just dialed the Builzoid things in and all is fine untill its not lol. Just freezes and Mouse feels laggy in BIOS too.. 

 

Had to reboot several times and completely reset the BIOS in order to make it work again. Even in EXPO settings the BIOS tripped out.. 

 

I know its an beta BIOS but c'mon this is terrible. So back to square one l guess lol.

 

It takes a fair while to get the timings right, plumbing in timings from someone else does not always work as there are so many factors involved, but that does not mean you cannot use it as a sensible frame of reference, you just have to tailor it a little to your specific setup.

 

I would suggest that you put your system at stock for everything while you work on the RAM, this removes any other factors that could cause you issues. Nothing worse that testing something, thinking there is an issue when it turns out it is something else completely. It can have you going in circles. 

 

After you make any changes to the timings, while it is a pain, it is worth running a full battery of stability tests to ensure your most incremental change is 100% stable before you move further. 

 

I (like others) run the following tests:

 

-GSAT (4 Hours)

-Karhu (10000%)

-YCruncher VST (I just let this run for approximately 4-6 hours)

 

It is massively time consuming, but all your changes  within reason need to be incremental, otherwise if you find an instability, you will have less idea what is causing it and you will find yourself questioning all the timings. I tend to change 1-3 timings per time to keep any instabilities pinned to a small subset of timings for "easy" rectification.

 

I would also suggest playing with your voltages (you can reference voltages from others but mileage may vary), even if you are not pushing raw speed, tighter timings sometimes require additional voltage to get stable, if you are pushing for the tightest of timings it is likely you will need to increase your DRAM voltage.

 

While it is unlikely your RAM has a fault, to check your RAM is 100% OK, it may be worth restoring your RAM to standard EXPO profile and running Memtest86. At least then once you start your OC journey you know your RAM is all well and any issues you experience is coming from the OC only, whether it be bad timings or voltage factors.

 

I seldom mess around with RAM, once I get stable with a kit I like, I leave it alone. It is a time consuming beast and sometimes massively frustrating. I have personally found DDR5 a massive pain in the ass to OC compared to DDR4. That being said DDR5 is still a baby compared to DDR4 and within reason a different beast. Hang in there!

[J7SC_Orion]

8 minutes ago, richardmeppelin said:

 

Latest one with AGESA 1.0.0.7. 1.0.8.0 is on its way but not here yet.. Its an D BIOS so it should be close of "stable" but sadly its not. What AGESA are you on and what is your max ram speed etc?

 

...top right > here (DDR5 8000; Agesa in Zen header, click on pic to enlarge)

[neurotix]

13 minutes ago, ENTERPRISE said:

 

I would also suggest playing with your voltages (you can reference voltages from others but mileage may vary), even if you are not pushing raw speed, tighter timings sometimes require additional voltage to get stable, if you are pushing for the tightest of timings it is likely you will need to increase your DRAM voltage.

 

While it is unlikely your RAM has a fault, to check your RAM is 100% OK, it may be worth restoring your RAM to standard EXPO profile and running Memtest86. At least then once you start your OC journey you know your RAM is all well and any issues you experience is coming from the OC only, whether it be bad timings or voltage factors.

 

I seldom mess around with RAM, once I get stable with a kit I like, I leave it alone. It is a time consuming beast and sometimes massively frustrating. I have personally found DDR5 a massive pain in the ass to OC compared to DDR4. That being said DDR5 is still a baby compared to DDR4 and within reason a different beast. Hang in there!

 

I'm lucky, for my Flare X B-Die kit I found some ZenTimings from OCN that worked great for me (6200MHz cas 30) and for my new M-Die kit, @J7SC_Oriongave me tightish timings for 7600MHz. Because I'm a n00b. Lol.

 

As you stated, increasing memory voltage to 1.435v might help. VDD_SOC should be 1.25 and he might need more VDDP and VDDG voltage.

 

I agree, setting everything to stock and running memtest86 would *definitely* help cuz then he can figure out if his memory is defective. Hopefully @richardmeppelinknows how to make a flash stick with memtest86.

 

I mess around with RAM a lot and still have a 5900x running 3733/1866 memory with tight timings. I haven't found DDR5 to be any worse than DDR4 personally but as stated, I lucked out and other people's sets of timings worked great for me.

 

I have given up on trying to get 8000mhz RAM as even with very loose timings I got errors in my tests right away. It just won't do it. However, I'm only losing like less than 1.5GB/sec bandwidth and my latency is lower at 7600MHz, which is confirmed stable.

 

Good advice E.

[Hurricane28]

33 minutes ago, ENTERPRISE said:

 

It takes a fair while to get the timings right, plumbing in timings from someone else does not always work as there are so many factors involved, but that does not mean you cannot use it as a sensible frame of reference, you just have to tailor it a little to your specific setup.

 

I would suggest that you put your system at stock for everything while you work on the RAM, this removes any other factors that could cause you issues. Nothing worse that testing something, thinking there is an issue when it turns out it is something else completely. It can have you going in circles. 

 

After you make any changes to the timings, while it is a pain, it is worth running a full battery of stability tests to ensure your most incremental change is 100% stable before you move further. 

 

I (like others) run the following tests:

 

-GSAT (4 Hours)

-Karhu (10000%)

-YCruncher VST (I just let this run for approximately 4-6 hours)

 

It is massively time consuming, but all your changes  within reason need to be incremental, otherwise if you find an instability, you will have less idea what is causing it and you will find yourself questioning all the timings. I tend to change 1-3 timings per time to keep any instabilities pinned to a small subset of timings for "easy" rectification.

 

I would also suggest playing with your voltages (you can reference voltages from others but mileage may vary), even if you are not pushing raw speed, tighter timings sometimes require additional voltage to get stable, if you are pushing for the tightest of timings it is likely you will need to increase your DRAM voltage.

 

While it is unlikely your RAM has a fault, to check your RAM is 100% OK, it may be worth restoring your RAM to standard EXPO profile and running Memtest86. At least then once you start your OC journey you know your RAM is all well and any issues you experience is coming from the OC only, whether it be bad timings or voltage factors.

 

I seldom mess around with RAM, once I get stable with a kit I like, I leave it alone. It is a time consuming beast and sometimes massively frustrating. I have personally found DDR5 a massive pain in the ass to OC compared to DDR4. That being said DDR5 is still a baby compared to DDR4 and within reason a different beast. Hang in there!

 

Appreciate the time man! 

 

I agree with everything and that is how i did it with DDR4 too which i still have some PTSD from lmao. That, and defective ROG boards so i had my fair share of issues and testings. 

 

I even went as far as consulting to Elmor (jon sandstrom) because of all of this but that's another matter. 

 

Tomorrow i will do the things you mentioned if i have enough time and go from there. 

 

Thnx for the support and input tho, much obliged. 

[Hurricane28]

21 minutes ago, neurotix said:

 

I'm lucky, for my Flare X B-Die kit I found some ZenTimings from OCN that worked great for me (6200MHz cas 30) and for my new M-Die kit, @J7SC_Oriongave me tightish timings for 7600MHz. Because I'm a n00b. Lol.

 

As you stated, increasing memory voltage to 1.435v might help. VDD_SOC should be 1.25 and he might need more VDDP and VDDG voltage.

 

I agree, setting everything to stock and running memtest86 would *definitely* help cuz then he can figure out if his memory is defective. Hopefully @richardmeppelinknows how to make a flash stick with memtest86.

 

I mess around with RAM a lot and still have a 5900x running 3733/1866 memory with tight timings. I haven't found DDR5 to be any worse than DDR4 personally but as stated, I lucked out and other people's sets of timings worked great for me.

 

I have given up on trying to get 8000mhz RAM as even with very loose timings I got errors in my tests right away. It just won't do it. However, I'm only losing like less than 1.5GB/sec bandwidth and my latency is lower at 7600MHz, which is confirmed stable.

 

Good advice E.

 

I guess you are man.

 

most of these voltages were correct set tho which is why its weird to me what happened. Normally it doesn't just lock up, so imo the BIOS OR the RAM is at fault here but idk, hard to say at this point. 

 

To be fair tho, weeks of tweaking and even with 8000MHz its not much faster than my stock 6000 expo set. 

I mean, the benchmarks numbers are higher and there will be an slight performance increase but at the end i ask myself, is it all the time worth i played with it? 

You have to be an enthousiast in order to handle the amount of stress that is causing this lol. 

 

That being said, i like tweaking but i would like to understand what i am doing and after 2 years of DDR4 tweaking on OCN and asking people that should know simply say that they also do not know what most settings do xD. 

 

Anyway, i never give up so tomorrow i gonna try again and bend this PC to my will lmao. 

[J7SC_Orion]

6 hours ago, richardmeppelin said:

 

I guess you are man.

 

most of these voltages were correct set tho which is why its weird to me what happened. Normally it doesn't just lock up, so imo the BIOS OR the RAM is at fault here but idk, hard to say at this point. 

 

To be fair tho, weeks of tweaking and even with 8000MHz its not much faster than my stock 6000 expo set. 

I mean, the benchmarks numbers are higher and there will be an slight performance increase but at the end i ask myself, is it all the time worth i played with it? 

You have to be an enthousiast in order to handle the amount of stress that is causing this lol. 

 

That being said, i like tweaking but i would like to understand what i am doing and after 2 years of DDR4 tweaking on OCN and asking people that should know simply say that they also do not know what most settings do xD. 

 

Anyway, i never give up so tomorrow i gonna try again and bend this PC to my will lmao. 

 

FYI. I have linked > Buildzoid's DDR 8000 / Ryzen 7900X a few times in this thread...very much worth watching, including his comments re. single chiplet Ryzen 7K and bandwidth, as well as voltages and such.

 

In any case, it takes a certain masochistic streak to tune-test-tune-test RAM  -  I remember finally getting to a solid  DDR4 4000 w/my 5950X...did it make a difference in most games compared to DDR 3800 ? Nope, but it was (mostly) fun getting there with limited voltages. 

 

Spoiler

       

...now, with DDR5 8000 locked in on the 7950X3D, I like to go higher   - I briefly hit an even 8200 CL 36 at the same voltages as 8000, but 8200 only lasted for a few seconds. 8110 can run 'ok', though it will eventually throw errors in long stress tests since I use the same voltages as 8000. I could go a bit higher on voltages, but then again, the new bios for this board supposedly has even better RAM oc but as posted before. I just rather wait a bit for them to iron out the new-bios-bugs.

 

Spoiler

 

I am pretty sure that by this time next year, we will be chasing at least 8400; probably more...

  

[Hurricane28]

2 hours ago, J7SC_Orion said:

 

FYI. I have linked > Buildzoid's DDR 8000 / Ryzen 7900X a few times in this thread...very much worth watching, including his comments re. single chiplet Ryzen 7K and bandwidth, as well as voltages and such.

 

In any case, it takes a certain masochistic streak to tune-test-tune-test RAM  -  I remember finally getting to a solid  DDR4 4000 w/my 5950X...did it make a difference in most games compared to DDR 3800 ? Nope, but it was (mostly) fun getting there with limited voltages. 

 

  Reveal hidden contents

       

...now, with DDR5 8000 locked in on the 7950X3D, I like to go higher   - I briefly hit an even 8200 CL 36 at the same voltages as 8000, but 8200 only lasted for a few seconds. 8110 can run 'ok', though it will eventually throw errors in long stress tests since I use the same voltages as 8000. I could go a bit higher on voltages, but then again, the new bios for this board supposedly has even better RAM oc but as posted before. I just rather wait a bit for them to iron out the new-bios-bugs.

 

  Reveal hidden contents

 

I am pretty sure that by this time next year, we will be chasing at least 8400; probably more...

  

 

Ye i follow him for quite some time now and he is very knowledgeable only he rambles too much for me to stay focuses for long lol. 

Same as for Steve Burke, Gamersnexxus, (Tech Jezus) lol. 

 

Yes it does man! I mean, its the pursuit of performance which is not there or only in the numbers but we all know, numbers can lie. Like, you see an higher number in benchmarks but never ever notice the difference. But is it fun? Heck yeah!   

 

that is unbelievable man, so high speeds and i am stuggling with stock 6000 MHz lmao. I feel such a noob xD. 

 

Anyway, back to testing some RAM AGAIN xD

[Hurricane28]

After a while of testing i discovered that at this time its pointless. 

 

no matter what i change or set higher for the ram its simply not working. Crashes, lockups etc. etc. Windows corruption, i am done for now. 

 

I wait until there is new BIOS cos this one is really bad, send feedback to Gigabyte already so hopefully they fix it cos this is not doable at this stage. 

 

Its expo settings for me from now on and if the new BIOS arrives i might try again but i don't think so as it cost me too much time which i can use better on productive things than pissing in the wind on this platform lmao. 

 

Thnx anyway for the help guys, much obliged!