johnksss
I had this long drawn out post, but not really worth it to explain.
https://www.3dmark.com/compare/pr/820304/pr/681933/pr/819320#
Bottom line I see a few things that are not the same as you seem to think they are.
1: steam version
2: 1412 on memory while your at 1375
3: older driver while your on newer one.
4: his average is higher than yours at 2181 mhz while you are 2177
5: you don't know what bios he is using.
6: you don't know if he is using classified or not.
7: you don't know if he is benching with open window or ac cooling.
8: he has an asus you have a gigabyte.
9: you dont know what his nvidia settings are.
10: you are running the same os and cpu speed as him. that seems to be about the only thing you have in common.
1: you need to reset your nv settings back to factory.
2: you need to drop the curve business for now.
3: you need to start by seeing how high your core can go.
4: you need to use the 520W version and quit slow dragging through the versions.
5: you need to use the classified tool to set voltage to 1.1V nvvdd and leave everything else alone.
6: you need to start at about 135+ on core and leave memory alone for now. work on one then the other. you pass, add +15 and run it again. don't worry about waiting. open gpuz and drop it to task manager. i use px1 for locking the clocks with boost lock
7: you will have crappy scores at first because you are just trying to see what the core will do vs the memory.
8: when you crash add .050mv to core and run the same clocks again. you are trying to see how high you can go before you max out at 540W as that's about where it stops for 520W vbios.
9: as was stated before. the count goes by 15's. so 105/120/135/150/165/180/195/210/225/240/255
10: as also stated before, you might crash because depending on which bin you are in your clocks will change. this is why on some days the same clocks will crash because they are running higher mhz at that setting. example +240 can go as high as 2295 if the temps are pretty low while on hot days some thing like 2265 or a bin lower.
11: can you break 15k with just core? yes you can.
once you get as high as you feel comfortable with, then start with memory. 1000 is a nice place to start as you don't need to move memory voltage. and go up in +100 increments till you crash. core is also at stock at this point. to get a 1400 mhz memory you need to be like +1500 to +1600 and if your room is a furnace, it's not gonna happen.
12: if your room and back of your card is like a furnace you can forget about getting any decent scores. just not going to happen. scores will be super crappy as you are looking for how high your memory overclocks for this time of day.
13: best to bench during the night with a window open and fan pointed towards your case or card.
14: learn the time, frames and fps points in the bench. if it isn't at a certain point no sense in letting it run till the end. you'll just be mad is all and wasted 2 minutes for nothing. stop bench and make a minor adjustment and run again.
14: never assume anyone with really good numbers is just hitting the go button and just miraculously has super great numbers. it's just not possible.
15: when you get your clocks set for a real good go at your best, then switch settings to performance mode in nv control panel and close out. and run bench.
16: best drivers are usually older drivers. 457.xx seems to do really well, although a few have been able to do with some newer drivers. not sure about the newest driver.
You can use that as a guide.
Edit:
And last but not least.....You card is not a dud if you are 1 fps off the leaders. people get so invested in the score that they do not realize that it is like 1 to 2 fps in the grand scheme of things. if you were like 20 fps behind, then you can start with the rma campaign.
1: not using steam, pretty sure I stated that already
2. can't go any higher on vRAM, I tried, would likely have to increase voltage in Classified Tool, will probably try that later
3. I ran on 460.89 previously and my scores went up with the newer drivers, planning on using 457.51 as a lot of people seem to get good scores with those, for the next time I'm pushing for personal bests
4. 4MHz... seriously...
5 6 7 8 don't actually matter that much, if he's not using the 520W BIOS I'd be shocked, obviously it's not an open window because our average temps are the same, motherboard I probably have an advantage because of the memory layout being superior on the Gigabyte
9 - Unless I missed some recent discovery, my NVidia Control Panel settings are pretty "optimized" for benchmarking, with High Performance being set in filter etc.
10 that's literally why I chose THAT person to point out how their score is 400pts higher than mine for seemingly no reason... Glad you noticed.
2 (dunno why numbers started over, but swa) - As someone that's actually being helpful pointed out in PMs, the curve can actually gain you clock stability instead of it varying so much, but I am trying both with & without a curve set, obviously
3 Such help much wow
4: ??? You missed the screenshot with power draw a few posts before the score that is in the compare, that's fine - I am on the 520W BIOS.
5: Been there, done that
6: I started at where I started, 150 seems to be about the limit I could hit before increasing voltages in Classified Tool - and so far bumping the ones up that effect core voltage have no resulted in an increase in set-able clock, but have resulted in higher average clock & of course, higher power draw
7: I've done core first, then memory without core OCed, to see where each tops out, vRAM will not run much higher than 1250 without failing, score went up with 500, 1000 and 1250, then crashed at 1500 & 1350, so 1250 is where it is.
8: This is the part where I stopped once I got to 1.1V NVVDD because I was unsure how high people were going so I started looking over the thread, saw Sajin running 1.2V (assumably with higher than normal cooling) & figured I'd ask what others are running
9: Super aware, 15MHz increments has been the norm for a few generations now, much easier to calculate in the brain-parts than the increments on my old 1080 Ti was.
10: Aware I am
11: Can other people? Yes, can this system? Not yet, not even close, haven't gotten higher than 14.6k with just core tuning, yet
12: Temps are definitely not a problem:
Right side is max load temps in PR and that's with nothing special being done case-wise (no side off or whatnot)
13: I'll be letting the room get cool tomorrow when I resume pushing, but that's the most I'm doing, people can go crazy all they like with running in super-cool environmentals, I sleep in the same room, I'm not doin' that lol
14x2 Yes
15: This is exactly a problem I was having yesterday that made me get irritated & stop, I had clocks that would pass with Afterburner & GPUz open to monitor things, but once I closed them, for whatever reason, the benchmark would not pass again. No idea what was going on there, but that happening repeatedly is what made me throw in the towel for the day... and that's with letting it cool down between runs
16: Yes as I said in an earlier number, plan on using 457.51s in the next runs, just to see how they do, but I'm also going to test with the 461.40s because like I said in an earlier post, they resulted in a stock-speed score increase of ~133pts from previous drivers I was using, which is well outside run-to-run variance for my system.
And I know the card is definitely not a dud, I do think my vRAM is a bit weak though, nothing a lil' voltage bump might not fix, but it seems like +1250MHz on the memory is definitely sub-par.
bumfoto
https://www.3dmark.com/pr/823587
new score 16054
not ln2
I was about to say "Wow that's insane" then I saw your average temp & it made more sense, sick score either way though!