EVGA 980 Ti Classified performing poorly in 3DMark Fire Strike

8BitSaint

Reputable
Oct 15, 2015
3
0
4,510
I just got my EVGA 980 Ti Classified from Newegg today, and I slapped it in my computer all excited and ready for some awesome gaming.

I immediately fired it up, started overclocking it, and decided to test it out in some games. However, I wasn't quite getting the performance I was expecting.

I decided to start up 3DMark Fire Strike and benchmark my system, and this is where my heart dropped.

Here is the link to my Fire Strike score. It's much lower than I was expecting, coming in at around 8300 total . This is far worse performance than the 2 970s I previously had (I decided to replace them due to overheating and space restrictions in my case). This score is including my overclocking (+450 GPU clock / +750 Mem clock).

Are these the kinds of scores I should expect from a card this high end? Or is there something wrong with my 980 Ti?

EDIT: Just for funsies, I decided to test out some less stressful games, and found out that PROJECT ZOMBOID is using between 45-60% of my GPU.
 

TofuLion

Admirable
there is definitely something wrong there. just out of curiosity, i ran firestrike on my own system and got a higher score. http://www.3dmark.com/3dm/8909649?

my CPU and GPU are overclocked quite a bit, but still... every component in your system is better than mine so my score should not be higher than yours.
 

8BitSaint

Reputable
Oct 15, 2015
3
0
4,510


That's what I thought. There's no way a high end overclocked card like this should be getting such low scores. I took my rig to work today to test out. I'm going to try reseating the GPU and see if that fixes anything.
 

8BitSaint

Reputable
Oct 15, 2015
3
0
4,510


I stupidly did not.

I did this morning, and I reseated it as well, which seemed to fix the issue. I also identified what the actual issue WAS. For some reason, the card wasn't leaving its idle clock states. It was stuck at very low clock speeds for some reason. Reinstalling the drivers wasn't enough to fix the issue though, I also had to reseat the card.