Rankings and Points
World Record Rank
Not Chilli-Man's Best 3DMark03 Submission
Global 1 Cores GPU Rank
NVIDIA
GeForce GT 1030 (GDDR5)
Rank
20.0 Points
Global 1 Cores GPU Team Power Rank
0.0 Points
NVIDIA
GeForce GT 1030 (GDDR5)
Team Power Rank
6.6 Points
Hardware Details
Memory
n/a
Videocard
Model NVIDIA GeForce GT 1030 (GDDR5) (GP108) Cooling Liquid Nitrogen Speed 2,556 MHz (+108.31%) / 2,242 MHz (+49.27%)
Comments
Crazy Nature!
It looks like a crash out at very end of nature, i had this happen to me once and resulted in a slightly inflated nature fps and couple thousand point boost. GT1 score is boosted due to very good cpu/mem efficiency sense that sub test is the only one CPU limited on these GPU's, really solid run otherwise!
GT1 gains a lot from gpu too. Can see the boost vs my previous score (got others in between too) which had same cpu/mem clocks iirc
yeah it does but its the only one that can also benefit from more cpu / memory system performance a good amount sense gpu use goes up and down constantly with the high FPS
maybe he has another with slightly less clocks that is inline that he can show
seems like bugged then the driver reset and maybe he didn't even realize since the screenshot is default gpu clocks
Yeah sadly the ratio looks to be pretty far off compared to others, maybe a new secret tweak or bugged I think?
Edit:
"Rule Update #2 - All verification screenshots must show the settings at which the benchmark was completed. This means it is not allowed to decrease the operating frequency for screenshot purposes. In effect, the staff reserves the right to reject a submission that is deemed out of line for the stated system parameters. For XTU specifically, the data file must contain monitoring information (frequency and temperature)."
i think the context of that rule change is for clock limited comps but it indeed does help with benches like this one that will bug out scores if you crash during a run and the only way to tell for sure that someone didn't crash out is if the gpu freqency monitoring is visible thru end of the run at full clocks at least on nvidia cards because if you do crash you ether loose the driver altogether and have to reboot or in many cases the driver recovers and your card is back at stock clocks but power state will stick if you forcing a higher power state (k boost etc)
No need to reboot to raise again the frequencies after a bug run
Only if the driver doesn't recover yeah
Log in or register to comment