Welcome to ExtremeHW
Welcome to ExtremeHW, register to take part in our community, don't worry this is a simple FREE process that requires minimal information for you to signup.
Registered users can:
- Start new topics and reply to others.
- Show off your PC using our Rig Creator feature.
- Subscribe to topics and forums to get updates.
- Get your own profile page to customize.
- Send personal messages to other members.
- Take advantage of site exclusive features.
- Upgrade to Premium to unlock additional sites features.
ENTERPRISE
-
Posts
6,058 -
Joined
-
Last visited
-
Days Won
384 -
Feedback
0%
Everything posted by ENTERPRISE
-
What Die is your new kit ?
-
They were removed as the quality I did not find acceptable. So I will be trialling something new soonish.
-
Corsair Dominator Titanium DDR5 RAM Review Discussion
ENTERPRISE replied to ENTERPRISE's topic in Review Discussions
Released -
Source
-
The big sticker should now be back and showing in the store
-
No problems bud, thanks for confirming
-
@kaliz is this from an Intel BIOS ?
-
Well played sir! Likely the product needs renewing, I will look at that. Please send me a pm to remind me
-
Possible its only an Intel thing then.
-
The one Kaliz sent they rejected saying it was from an Intel BIOS which I need to look into again. So I thought I would ask again. I cannot see it in your screenshot either as something you would "Enable"
-
That would be great. Source
-
Hey guys, Can someone give me a screenshot of the ability to enable "Round Trip Latency" on an AMD X670 BIOS ? This is just for continuing discussions with MSI. Cheers.
-
Well I think for now I am happy with my OC. After tweaking timings, I was able to get my 6600 OC running SuperPi where it ought to be. After some further BIOS and AGESA updates I will see if I can achieve anything better but for now I am pleased with this. Thanks everyone for your help!
-
Just do not paint the blades, this can have an effect on performance due to differential weight on each blade depending on the paint thickness applied. It would be virtually impossible to get an even coat on each blade. Plus depending on the uneven rotation of blades that have been painted it could shorten the life of the motor. Not trying to be the naysayer but lot's of people forget there is a science that goes into these products. Painting the frame however, less of an issue.
- 19 replies
-
- 1
-
-
- apex
- stealth metal (power) fan
- (and 2 more)
-
I will run that and see what it comes back with. So I adjusted tRDRDSD/tRDRDDD to 11 for my 6600 OC and that certainly helped, I was getting 5m 32s vs 6m 12s. 6400 is still better at 5m 9s, so I will have to investigate what else I need to adjust to get 6600 on par or better. If anyone has any suggestions, it would be appreciated, though I am trying to see if I can keep CL28.
-
Those timing values are currently set to Auto, that is likely why the variance between the two ZenTimings for 6600 & 6400. But fair point, I may set that to 11 for the 6600 profile as 10 may be too tight. I have looked in event viewer, I have not noted and errors relating to memory correction or WHEA errors.
-
Well this is my 6400MT/s & 6600MT/s OC Curiously the 6600 OC has a worse Pi Score. So Even though it passed 4 Hours of GSAT and 15000% of Karhu I can only assume an instability or other factor causing it to be worse
-
Yeah disabled TSME a while ago on your advice I think Once I have locked in my RAM OC I will come back here to optimise my CPU with Curve Optimizer for sure
-
Yeah I do Yep already set to that thanks bud.
-
Awesome thanks What motherboard was that on again ? I will try and see if those areas shed any light, though I think I have been through them but it is possible I missed it. On another note while I did get 6400MT/s stable, I thought just for a laugh, I would try my hand at 6600 MT/s again using the same timings as on my 6400 OC. With a little bit of additional voltage I was able to get 6600 through 4 Hours of GSAT and 11000% of Karhu before it gave me an error. So I am upping the VDDQ to 1.42 and DRAM Voltage to 1.57 with a SOC of 1.255 to see if it gets me stable. My 6400 OC - VDDQ 1.35, VDD 1.55, SOC 1.25 My attempt at 6600 OC -VDDQ 1.42, VDD 1.57, SOC 1.255 Not a stellar difference in throughput on the speeds mind you.
-
Well played....well played!
-
techspot Asus is prepping a GeForce RTX 4060 Ti with a built-in SSD slot
ENTERPRISE replied to bonami2's topic in Rumour Mill
I would sort of understand one of those brands from the left field doing this...but seems like an odd move for Asus. If you are buying a GPU at the price bracket of the 4060 Ti, I would expect generally that you would also have a motherboard with at least one M.2 slot. Not sure I see the audience for this tech combo. Plus...I generally think putting an SSD near a heat generating source like a GPU is not massively wise. -
Sometimes no harm in waiting for BIOS/AGESA to mature before going at it again On another note chaps, looks like MSI are going to implement GDM after my discussions with them. However they are asking about a screenshot of where in the BIOS you would enable "Round Trip Latency", could someone do me a favour and screenshot their BIOS page with this and pop it in here ? I can then go back to them on this as well and see what they say. Still beyond me that consumers are having to tackle a vendor about basic settings.
-
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!
-
Will do.
