Well, my SSC GX2 is installed.
One odd thing is as soon as I plugged it in, my favorite stable 3.8GHz BIOS settings would not boot withought getting a CPU Check on my Maximus LCD Poster. It booted fine using the BIOS default settings.
I had to then load in my saved OC profile in, and back er down to 3.3GHz.
I need to go back to OCing my system to get my 3.8GHz back. I am guessing that it probably need more CPU voltage, but not sure what to think.
Any advice what setting in the BIOS might help a GX2 out?
At 3.8GHz and my OCed 8600GT in 3DMark06 (default settings):
I was getting a score of about 4,982 3DMarks.
At only 3.3GHz, and my stock SSC GX2, This was my very first run, Vista Ultimate and 174.74 driver:
3DMark Score 16,976 3DMarks.
SM 2.0 Score 6601
SM 3.0 Score 8182
CPU Score 4649
Graphics Tests
1 - Return to Proxycon 53.49 FPS
2 - Firefly Forest 56.53 FPS
CPU Tests
CPU1 - Red Valley 1.52 FPS
CPU2 - Red Valley 2.28 FPS
HDR Tests
1 - Canyon Flight (SM 3.0) 96.26 FPS
2 - Deep Freeze (SM 3.0) 67.38 FPS
Things are looking up...
I am happy with the card. It installed fine...
The power plugs went right in...
The removal of the old drivers, and install of the new also went well.
I did spend more time OC'ing my system, and faught my way back to 3.4GHz.
After an unsuccessful 3.5GHz attempt, I ran into that Maximus CMOS error message, that only time heals. (The clear CMOS button did not help me out.)
I must have tried 10 times booting unsuccessfully to get around the CMOS ERROR on the LCD Poster. The display would go from 'INIT ROM' to 'CMOS ERR' to System lockes up...
I was real close to removing the battery, but that was under the GX2 and I didn't want to take it back out. I chilled for 20 minutes with the power off to the PC. After some Captain Black, I was ready to try again...
Came back in, hit the system with power, and it acted like it was fine again!! Booted right up.
Loaded the last successful OC profile back in that worked with some light OCCT testing, then backed that down a tad for saftey. 3.4GHz is where she currently sits.
My gut feeling is that I am so new at OCing CPU's, that it just needs a BIOS adjustment that I havent tried yet...
The CMOS error gave me pause though...
Ran two more tests trying to match my CPU speed best I could, to re-produce my last 8600 runs using 3DMark06...
At 640 x 480 No AA OCed 8600 GT, [email protected]:
8,842 3DMarks
SM2.0 Score: 2,988
HDR/SM3.0 Score: 3,673
CPU Score: 5,445
Return to Proxycon - 27.65fps
Firefly Forest - 22.16fps
CPU1 Red Valley - 1.83fps
CPU2 Red Valley - 2.59fps
Canyon Flight - 27.18fps
Deep Freeze - 46.28fps
At 640 x 480 No AA GX2 SSC Stock, [email protected]:
18,530 3DMarks
SM2.0 Score: 6,803
HDR/SM3.0 Score: 9,653
CPU Score: 4,746
Return to Proxycon - 54.93fps
Firefly Forest - 58.45fps
CPU1 Red Valley - 1.53fps
CPU2 Red Valley - 2.35fps
Canyon Flight - 122.81fps
Deep Freeze - 70.25fps
At 1920 x 1200 No AA OCed 8600 GT, [email protected]:
3,466 3DMarks
SM2.0 Score: 1,256
HDR/SM3.0 Score: 1,199
CPU Score: 5,196
Return to Proxycon - 10.79fps
Firefly Forest - 10.14fps
CPU1 Red Valley - 1.68fps
CPU2 Red Valley - 2.58fps
Canyon Flight - 10.29fps
Deep Freeze - 13.69fps
At 1920 x 1200 No AA GX2 SSC Stock, [email protected]:
16,402 3DMarks
SM2.0 Score: 6,632
HDR/SM3.0 Score: 7,458
CPU Score: 4,723
Return to Proxycon - 54.92fps
Firefly Forest - 55.61fps
CPU1 Red Valley - 1.55fps
CPU2 Red Valley - 2.3fps
Canyon Flight - 78.57fps
Deep Freeze - 70.58fps
She is a runner, and I have never seen my games look so good, or move so fast.
I installed FRAPS 2.9.4 right before I removed my 8600 GT.
In real life games this is what I was getting.
Q6600 @ 3.8GHz, OC'ed 8600GT:
In COD4 1920 x 1200 AAx2
Sync every frame - NO
Shadows - NO
Specular Map - NO
Everything else to YES or Normal
34 to 39 fps in game play.
Q6600 @ 3.4GHz, and stock SSC:
In COD4 1920 x 1200 AAx2
Sync every frame - NO
Shadows - NO
Specular Map - NO
Everything else to YES or Normal
57fps in most game play, all the way up to 700 or more at times.
Q6600 @ 3.8GHz, OC'ed 8600GT:
Crysis 1920 x 1200 AA off
Fullscreen X'ed
VSYNC not X'ed
Plane flying in - 4 to 7 fps
'OK gentlemen listen up' scene - 10 fps
'Parachute in' scene - 11 fps
Swimming in the water to the beach - 8 to 9 fps
Q6600 @ 3.4GHz, and stock SSC:
Crysis 1920 x 1200 AA off
Fullscreen X'ed
VSYNC not X'ed
Everything set to High...
Plane flying in - 29fps
'OK gentlemen listen up' scene - 47fps
'Parachute in' scene - 52 to 55fps (more right before landing)
Swimming in the water to the beach - 45fps
After doing some OC'ing on the GX2, I now believe a Q6600 at 3.4GHz is a bottleneck to a GX2 SSC.
Q6600 @ 3.419 GHz for all testing... (Best I can currently do)
Core clock - 675MHz (Stock GX2 SSC speed)
Shader clock - 1,674MHz
Memory clock - 1,050MHz
3DMark06 - 17,284
Kept the Core and Shaders linked, and upped the core and memory.
Core clock - 730MHz
Shader clock - 1,810MHz
Memory clock - 1,100MHz
3DMark06 - 17,234 (Score was lower than stock SSC by 50 points.)
Kept the Core and Shaders in the same spot, and lowered the memory only.
Core clock - 730MHz
Shader clock - 1,810MHz
Memory clock - 1,090MHz
3DMark06 - 17,159 (Score was lower than stock SSC by 125 points.)
Raised the memory, and lowered the core still keeping it linked to Shaders.
Core clock - 720MHz
Shader clock - 1,785MHz
Memory clock - 1,100MHz
3DMark06 - 17,079 (Score was lower than stock SSC by 205 points.)
Unlinked the core and shaders, for largest OC yet...
Core clock - 740MHz
Shader clock - 1,846MHz
Memory clock - 1,100MHz
3DMark06 - 16,818 (Score was lower than stock SSC by 466 points.)
De-installed Riva Tuner, and returned to stock SSC Clock speeds:
Core clock - 675MHz (Stock GX2 SSC speed)
Shader clock - 1,674MHz
Memory clock - 1,050MHz
3DMark06 - 17,350 (Score went up 66 points over the origional stock SSC numbers.)
Conclusion...
There is currently no advantage for me to OC my GX2 SSC right now...
In my mind, one of two reasons is why.
1) The GX2 runs fast enouigh already, to fill it's data path between it and the PC, so OC'ing the card won't do too much for you...
2) A Q6600 @ 3.4GHz is too slow to take advantage of OC'ing a GX2 SSC. I now believe this is the real issue if I want my score to climb any higher.
A quad core processor running at 3.4GHz, is indeed a bottleneck to a GX2...
I can't fix no-1 even if it was the issue, but intend to work more on number 2.
For right now, until I get my Q6600 running faster than 3.4GHz, I am going to run my GX2, just the way EVGA made it.
I don't want the extra heat on the card by OC'ing it, nor do I think there is any performance for me to be had by doing so.
Not as long as I am limping along at 3.4!!
This strikes me a rather demanding... Imagine the poor SOB running his processor at stock speed, with GX2 installed.
Ouch!! That's gunna hurt...
The card does do a number on my games even at 1920 x 1200. It is a beast, and I am having a blast with it.
One odd thing is as soon as I plugged it in, my favorite stable 3.8GHz BIOS settings would not boot withought getting a CPU Check on my Maximus LCD Poster. It booted fine using the BIOS default settings.
I had to then load in my saved OC profile in, and back er down to 3.3GHz.
I need to go back to OCing my system to get my 3.8GHz back. I am guessing that it probably need more CPU voltage, but not sure what to think.
Any advice what setting in the BIOS might help a GX2 out?
At 3.8GHz and my OCed 8600GT in 3DMark06 (default settings):
I was getting a score of about 4,982 3DMarks.
At only 3.3GHz, and my stock SSC GX2, This was my very first run, Vista Ultimate and 174.74 driver:
3DMark Score 16,976 3DMarks.
SM 2.0 Score 6601
SM 3.0 Score 8182
CPU Score 4649
Graphics Tests
1 - Return to Proxycon 53.49 FPS
2 - Firefly Forest 56.53 FPS
CPU Tests
CPU1 - Red Valley 1.52 FPS
CPU2 - Red Valley 2.28 FPS
HDR Tests
1 - Canyon Flight (SM 3.0) 96.26 FPS
2 - Deep Freeze (SM 3.0) 67.38 FPS
Things are looking up...
I am happy with the card. It installed fine...
The power plugs went right in...
The removal of the old drivers, and install of the new also went well.
I did spend more time OC'ing my system, and faught my way back to 3.4GHz.
After an unsuccessful 3.5GHz attempt, I ran into that Maximus CMOS error message, that only time heals. (The clear CMOS button did not help me out.)
I must have tried 10 times booting unsuccessfully to get around the CMOS ERROR on the LCD Poster. The display would go from 'INIT ROM' to 'CMOS ERR' to System lockes up...
I was real close to removing the battery, but that was under the GX2 and I didn't want to take it back out. I chilled for 20 minutes with the power off to the PC. After some Captain Black, I was ready to try again...
Came back in, hit the system with power, and it acted like it was fine again!! Booted right up.
Loaded the last successful OC profile back in that worked with some light OCCT testing, then backed that down a tad for saftey. 3.4GHz is where she currently sits.
My gut feeling is that I am so new at OCing CPU's, that it just needs a BIOS adjustment that I havent tried yet...
The CMOS error gave me pause though...
Ran two more tests trying to match my CPU speed best I could, to re-produce my last 8600 runs using 3DMark06...
At 640 x 480 No AA OCed 8600 GT, [email protected]:
8,842 3DMarks
SM2.0 Score: 2,988
HDR/SM3.0 Score: 3,673
CPU Score: 5,445
Return to Proxycon - 27.65fps
Firefly Forest - 22.16fps
CPU1 Red Valley - 1.83fps
CPU2 Red Valley - 2.59fps
Canyon Flight - 27.18fps
Deep Freeze - 46.28fps
At 640 x 480 No AA GX2 SSC Stock, [email protected]:
18,530 3DMarks
SM2.0 Score: 6,803
HDR/SM3.0 Score: 9,653
CPU Score: 4,746
Return to Proxycon - 54.93fps
Firefly Forest - 58.45fps
CPU1 Red Valley - 1.53fps
CPU2 Red Valley - 2.35fps
Canyon Flight - 122.81fps
Deep Freeze - 70.25fps
At 1920 x 1200 No AA OCed 8600 GT, [email protected]:
3,466 3DMarks
SM2.0 Score: 1,256
HDR/SM3.0 Score: 1,199
CPU Score: 5,196
Return to Proxycon - 10.79fps
Firefly Forest - 10.14fps
CPU1 Red Valley - 1.68fps
CPU2 Red Valley - 2.58fps
Canyon Flight - 10.29fps
Deep Freeze - 13.69fps
At 1920 x 1200 No AA GX2 SSC Stock, [email protected]:
16,402 3DMarks
SM2.0 Score: 6,632
HDR/SM3.0 Score: 7,458
CPU Score: 4,723
Return to Proxycon - 54.92fps
Firefly Forest - 55.61fps
CPU1 Red Valley - 1.55fps
CPU2 Red Valley - 2.3fps
Canyon Flight - 78.57fps
Deep Freeze - 70.58fps
She is a runner, and I have never seen my games look so good, or move so fast.
I installed FRAPS 2.9.4 right before I removed my 8600 GT.
In real life games this is what I was getting.
Q6600 @ 3.8GHz, OC'ed 8600GT:
In COD4 1920 x 1200 AAx2
Sync every frame - NO
Shadows - NO
Specular Map - NO
Everything else to YES or Normal
34 to 39 fps in game play.
Q6600 @ 3.4GHz, and stock SSC:
In COD4 1920 x 1200 AAx2
Sync every frame - NO
Shadows - NO
Specular Map - NO
Everything else to YES or Normal
57fps in most game play, all the way up to 700 or more at times.
Q6600 @ 3.8GHz, OC'ed 8600GT:
Crysis 1920 x 1200 AA off
Fullscreen X'ed
VSYNC not X'ed
Plane flying in - 4 to 7 fps
'OK gentlemen listen up' scene - 10 fps
'Parachute in' scene - 11 fps
Swimming in the water to the beach - 8 to 9 fps
Q6600 @ 3.4GHz, and stock SSC:
Crysis 1920 x 1200 AA off
Fullscreen X'ed
VSYNC not X'ed
Everything set to High...
Plane flying in - 29fps
'OK gentlemen listen up' scene - 47fps
'Parachute in' scene - 52 to 55fps (more right before landing)
Swimming in the water to the beach - 45fps
After doing some OC'ing on the GX2, I now believe a Q6600 at 3.4GHz is a bottleneck to a GX2 SSC.
Q6600 @ 3.419 GHz for all testing... (Best I can currently do)
Core clock - 675MHz (Stock GX2 SSC speed)
Shader clock - 1,674MHz
Memory clock - 1,050MHz
3DMark06 - 17,284
Kept the Core and Shaders linked, and upped the core and memory.
Core clock - 730MHz
Shader clock - 1,810MHz
Memory clock - 1,100MHz
3DMark06 - 17,234 (Score was lower than stock SSC by 50 points.)
Kept the Core and Shaders in the same spot, and lowered the memory only.
Core clock - 730MHz
Shader clock - 1,810MHz
Memory clock - 1,090MHz
3DMark06 - 17,159 (Score was lower than stock SSC by 125 points.)
Raised the memory, and lowered the core still keeping it linked to Shaders.
Core clock - 720MHz
Shader clock - 1,785MHz
Memory clock - 1,100MHz
3DMark06 - 17,079 (Score was lower than stock SSC by 205 points.)
Unlinked the core and shaders, for largest OC yet...
Core clock - 740MHz
Shader clock - 1,846MHz
Memory clock - 1,100MHz
3DMark06 - 16,818 (Score was lower than stock SSC by 466 points.)
De-installed Riva Tuner, and returned to stock SSC Clock speeds:
Core clock - 675MHz (Stock GX2 SSC speed)
Shader clock - 1,674MHz
Memory clock - 1,050MHz
3DMark06 - 17,350 (Score went up 66 points over the origional stock SSC numbers.)
Conclusion...
There is currently no advantage for me to OC my GX2 SSC right now...
In my mind, one of two reasons is why.
1) The GX2 runs fast enouigh already, to fill it's data path between it and the PC, so OC'ing the card won't do too much for you...
2) A Q6600 @ 3.4GHz is too slow to take advantage of OC'ing a GX2 SSC. I now believe this is the real issue if I want my score to climb any higher.
A quad core processor running at 3.4GHz, is indeed a bottleneck to a GX2...
I can't fix no-1 even if it was the issue, but intend to work more on number 2.
For right now, until I get my Q6600 running faster than 3.4GHz, I am going to run my GX2, just the way EVGA made it.
I don't want the extra heat on the card by OC'ing it, nor do I think there is any performance for me to be had by doing so.
Not as long as I am limping along at 3.4!!
This strikes me a rather demanding... Imagine the poor SOB running his processor at stock speed, with GX2 installed.
Ouch!! That's gunna hurt...
The card does do a number on my games even at 1920 x 1200. It is a beast, and I am having a blast with it.