Ugh...Intel recalling P67 chipsets over SATA bug...need to find PCI-E x1 SATA card I guess
That sucks!!
Ugh...Intel recalling P67 chipsets over SATA bug...need to find PCI-E x1 SATA card I guess
Running GPU benchmark 1
Results will depend on current system settings
Press any key to continue . . .
Running...
==============================================================
TimeDemo Play Started , (Total Frames: 2000, Recorded Time: 111.86s)
!TimeDemo Run 0 Finished.
Play Time: 38.07s, Average FPS: 52.53
Min FPS: 38.87 at frame 1968, Max FPS: 68.21 at frame 974
Average Tri/Sec: -28297308, Tri/Frame: -538688
Recorded/Played Tris ratio: -1.70
!TimeDemo Run 1 Finished.
Play Time: 36.06s, Average FPS: 55.46
Min FPS: 38.87 at frame 1968, Max FPS: 70.29 at frame 96
Average Tri/Sec: -29707944, Tri/Frame: -535682
Recorded/Played Tris ratio: -1.71
Press any key to continue . . .
==============================================================
TimeDemo Play Started , (Total Frames: 2000, Recorded Time: 111.86s)
!TimeDemo Run 0 Finished.
Play Time: 31.56s, Average FPS: 63.37
Min FPS: 46.27 at frame 1974, Max FPS: 81.97 at frame 930
Average Tri/Sec: -3307903, Tri/Frame: -52198
Recorded/Played Tris ratio: -17.56
!TimeDemo Run 1 Finished.
Play Time: 29.84s, Average FPS: 67.03
Min FPS: 46.27 at frame 1974, Max FPS: 82.79 at frame 875
Average Tri/Sec: -2493720, Tri/Frame: -37200
Recorded/Played Tris ratio: -24.64
!TimeDemo Run 2 Finished.
Play Time: 29.81s, Average FPS: 67.10
Min FPS: 46.27 at frame 1974, Max FPS: 83.06 at frame 983
Average Tri/Sec: -2393463, Tri/Frame: -35669
Recorded/Played Tris ratio: -25.70
!TimeDemo Run 3 Finished.
Play Time: 29.70s, Average FPS: 67.33
Min FPS: 46.27 at frame 1974, Max FPS: 83.06 at frame 983
Average Tri/Sec: -2396632, Tri/Frame: -35594
Recorded/Played Tris ratio: -25.75
TimeDemo Play Ended, (4 Runs Performed)
==============================================================
Press any key to continue . . .
TimeDemo Play Started , (Total Frames: 2000, Recorded Time: 111.86s)
!TimeDemo Run 0 Finished.
Play Time: 37.29s, Average FPS: 53.63
Min FPS: 36.74 at frame 168, Max FPS: 101.19 at frame 909
Average Tri/Sec: -33110690, Tri/Frame: -617412
Recorded/Played Tris ratio: -1.48
!TimeDemo Run 1 Finished.
Play Time: 31.48s, Average FPS: 63.53
Min FPS: 36.74 at frame 168, Max FPS: 103.62 at frame 899
Average Tri/Sec: -39226428, Tri/Frame: -617462
Recorded/Played Tris ratio: -1.48
!TimeDemo Run 2 Finished.
Play Time: 31.32s, Average FPS: 63.86
Min FPS: 36.74 at frame 168, Max FPS: 103.62 at frame 985
Average Tri/Sec: -39403256, Tri/Frame: -617005
Recorded/Played Tris ratio: -1.49
!TimeDemo Run 3 Finished.
Play Time: 31.25s, Average FPS: 64.01
Min FPS: 36.74 at frame 168, Max FPS: 103.62 at frame 985
Average Tri/Sec: -39459048, Tri/Frame: -616498
Recorded/Played Tris ratio: -1.49
TimeDemo Play Ended, (4 Runs Performed)
==============================================================
Press any key to continue . . .
what's a "suicide run"?
what's a "suicide run"?
also, If TRSSAA doesn't work is it still applying MSAA?
Very nice looking system BTW Almighty!
So my lower 19x10 vs. 19x12 would be a result of scaling to my monitor's native resolution?
To me it appears you have a CPU bottleneck, What speed do you have your Sandy Bridge clocked at? 5Ghz is easy acheived for 24/7 safe useage on these chips.
And going from 19x10 to 19x12 increases the load on the GPU's as it's a higher resolution, thus increases Crossfire scaling and efficiency giving you better results :smile:
Interesting how you guys went with CF since AFAIK you can't use tripple-buffering with dual/quad setups, which is a must IMO.
Triple buffering: "Why we love it"
The benefits of Crossfire out weigh the benefits of tripple buffering, And I force it with RadeonPro and I get no tearing