Infatti Furmark li provoca.
Unigine valley 1.0 / heaven 4.0 fanno solo renderizzare alla scheda scene diverse assai pesanti, mettendola sotto stress.
In ogni caso puoi googlare eh!
Ecco i risultati
[h=1]
Unigine Valley Benchmark 1.0[/h] [TABLE="class: result"]
[TR]
[TD="class: right"]FPS:[/TD]
[TD]
33.0
[/TD]
[/TR]
[TR]
[TD="class: right"]Score:[/TD]
[TD]
1379
[/TD]
[/TR]
[TR]
[TD="class: right"]Min FPS:[/TD]
[TD]
17.1
[/TD]
[/TR]
[TR]
[TD="class: right"]Max FPS:[/TD]
[TD]
63.2
[/TD]
[/TR]
[/TABLE]
[h=2]
System[/h] [TABLE="class: detail"]
[TR]
[TD="class: right"]Platform:[/TD]
[TD]Windows 8 (build 9200) 64bit
[/TD]
[/TR]
[TR]
[TD="class: right"]CPU model:[/TD]
[TD]AMD FX(tm)-8320 Eight-Core Processor (3492MHz) x4
[/TD]
[/TR]
[TR]
[TD="class: right"]GPU model:[/TD]
[TD]NVIDIA GeForce GTX 660 9.18.13.3165 (2048MB) x1
[/TD]
[/TR]
[/TABLE]
[h=2]
Settings[/h] [TABLE="class: detail"]
[TR]
[TD="class: right"]Render:[/TD]
[TD]Direct3D11
[/TD]
[/TR]
[TR]
[TD="class: right"]Mode:[/TD]
[TD]1842x1036 8xAA fullscreen
[/TD]
[/TR]
[TR]
[TD="class: right"]Preset[/TD]
[TD]Custom
[/TD]
[/TR]
[TR]
[TD="class: right"]Quality[/TD]
[TD]Ultra
[/TD]
[/TR]
[/TABLE]
Quà una screen fatta a: cpu-z, gpu-z e HWmonitor subito dopo aver chiuso Unigine Valley. Prima del benchmark l'ho fatto girare 5 minuti a "vuoto" (senza fare il bench, solo facendo girare la camera intorno alle scene).
Grazie.