Everything posted by Demac
- The official Challenger 2015 Div III Round 3 thread.
- Splave.ROM - Core i7 6700K @ 6100MHz - 2001 marks XTU
- Bullshooter - Radeon R5 230 @ 875/950MHz - 2513 marks 3DMark Vantage - Performance
- Demac - Radeon R5 230 @ 625/825MHz - 1942 marks 3DMark Vantage - Performance
- Demac - Radeon R5 230 @ 625/825MHz - 1942 marks 3DMark Vantage - Performance
-
sebro - Intel HD Graphics @ 1800/1221MHz - 8961 marks 3DMark06
Nice score.
-
Vishera/Richland SuperPI 32M 5G Challenge
http://hwbot.org/submission/2930385_demac_superpi___32m_a6_6420k_14min_10sec_375ms/
- Demac - A6-6420K @ 7520.8MHz - 7520.8 mhz CPU Frequency
- pasatoiutd - HD Graphics (Haswell) @ 1850/1400MHz - 1954 marks Catzilla - 720p
- Rbuass - GeForce GTX Titan X @ 2000/2040MHz - 7398.91 DX11 Marks Unigine Heaven - Xtreme Preset
- The official GIGABYTE X99 Champion Challenge thread.
- Demac - Core i7 5820K @ 5000MHz - 2077 marks XTU
-
FireKillerGR - GeForce GT 730 GDDR5 @ 2210/1600MHz - 3620 marks 3DMark - Fire Strike
Oh lets take for expample then Doc`s score 2890 graphics score with 1700 core then and please redo your whole thinking again man... you know because you tested that a normal 2100 mhz run should be around 3030 points overall test.If you do not want to admit it then it is your problem man. I will not stay here and try to become even more petty trying to prove the obvious.It's a real bummer though seeing you react like that really... Good luck to you and all the other guys for the rest of the comp...I'm gone do my best in the remaining stages.
-
FireKillerGR - GeForce GT 730 GDDR5 @ 2210/1600MHz - 3620 marks 3DMark - Fire Strike
No Phil i think you are wrong here.I have uploaded 4 results in FS two not bugged and two bugged all at the same clocks.It seems to me that the bug happens due to high voltage and relatively low temp.For me when i run at -160 no bug occurs but when i start the GT1 at -150 the thing at my video happens.Also i have plenty of verification links and screenshots that i have not uploaded (they are at staff's disposal at any time) that have only one subtest bugged and it was due to artifacting and not rendering the correct amount of pixels at the specific subtest.And yes these runs are of course frequency related because there are same pixels left for rendering so the higher the gpu clocks the higher the score.I had no intention of uploading any bugged run untli i saw FK uploading his and i clearly stated that in my opinion it is bugged (thus and the video).My 2c and i have nothing personal with you guys at all,on the contrary you helped me HUGELLY for the bios to run Catzilla efficiently!!!
- Demac - GeForce GT 730 GDDR5 @ 2169/1603MHz - 3513 marks 3DMark - Fire Strike
- Demac - GeForce GT 730 GDDR5 @ 2169/1603MHz - 3513 marks 3DMark - Fire Strike
-
The official GIGABYTE X99 Champion Challenge thread.
ok i think i have to take position since i have been running "buggy" xtu here is a 1864 run with cpu-z mem tab and gtl open (at that moment i thought that only the 3000c10 mem would be considered suspicious of me...)if you see anything buggy please let me know to change it in my next runs... attached also a 1869 (<1870 not bugged right?) that the olny difference with the video one is that i have closed cpu-z and gtl (duh) and that i have run xtu at 640x480 (xtu folder\binnaries\right click properties at p95.exe\compatibility (also compatibility for xp sp2 is nice) also please take notice that you can get a nice boost if you have your prefetch-superfetch parameters right and know how to use them and also take some time to test wich ramdisk gives you better score.Core parking settings and power options can give you a couple of points too. Please no offence and nothing personal here but i just wanted to make my case clear since some people think the comp is unjust or anything
- bits - Core i7 5820K @ 4500MHz - 1875 marks XTU
-
Asus Rampage V extreme "error" 79
Oh boy i had a gigabyte z77 that could not post past code 79 (internal device initialization) and it never booted again. Bios flashing or hard flashing did not do absolutely nothing. Out of nowhere without too much oc or something just doing some low clock runs. I hope that is not your issue man.
- sofos1990 - Core i7 5960X @ 5931MHz - 25.74 points Cinebench R11.5
- Schmuckley - Core i3 4360 @ 3944.3MHz - 41332 marks PCMark 2005
- Schmuckley - Core i3 4360 @ 3944.3MHz - 41332 marks PCMark 2005
- Schmuckley - Core i3 4360 @ 3944.3MHz - 41332 marks PCMark 2005
- Schmuckley - Core i5 4670K @ 5521.3MHz - 56311 marks PCMark 2005
- Schmuckley - Core i5 4670K @ 5521.3MHz - 56311 marks PCMark 2005