How do I figure out if I have a bad card? Ran GPU Shark program - how interpret?

Big Jeff

Distinguished
Oct 26, 2009
61
0
18,640
I have two 560 Ti's in SLI - been having issues in a game (ArchAge) - trying to determine if I have a bad card or? From another post - pretty sure I am going to upgrade to a 970 - but all on backorder - meanwhile trying to solve this with the 560's.

Is there a way for a novice like myself to check these cards? I ran Furmark benchmark - no issues, ran fine, based on the web list of scores mine did fine (did not crash).

The GPU Shark part of that program - showed me big differences between the two cards - is this normal?

Different drivers?
Different BIOS versions?
One card shows 2x the memory? (cards are physically identical)

Is this normal or did I screw something up when I put these in 2+ years ago? Should I try to update these somehow or?

GPU Shark v0.9.1
(C)2013 Geeks3D - www.geeks3d.com
----------------------------------------
Elapsed time: 00:03:10
GPU 1 - NVIDIA GeForce GTX 560 Ti
- GPU: GF114
- Bus ID: 2
- Device ID: 10DE-1200
- Subvendor: ASUS (1043-8390)
- Driver version: 9.18.13.4411
- NV driver branch: r343_98-7
- OS: Windows 8.1 64-bit build 9600
- Bios version: 70.24.21.00.02
- GPU memory size: 1024MB
- GPU memory type: 256-bit GDDR5
- GPU memory location: GPU dedicated
- GPU temp: 37.0°C (min:37.0°C - max:41.0°C)
- Fan speed: 22.0% / 1200.0 RPM
- GPU cores: 384
- TDP: 170 Watts
- # Pstates: 3
- Current Pstate: P12
- Core: 50.0MHz
- Mem: 135.0MHz
- VDDC: 0.950V
- GPU and memory usage:
- GPU: 0.0%, max: 3.0%
- GPU memory: 12.5%
- GPU memory controller: 7.0%
- Limiting policies (NVIDIA):
- no limitation
- Current active 3D applications:
--> glcnd.exe microsoft.reader_8wekyb3d8bbwe (PID: 3336)
--> dwm.exe (PID: 1012)
--> explorer.exe (PID: 3704)
--> furmark.exe (PID: 3920)
--> gpushark.exe (PID: 416)


GPU 2 - NVIDIA GeForce GTX 560 Ti
- GPU: GF114
- Bus ID: 1
- Device ID: 10DE-1200
- Subvendor: ASUS (1043-8390)
- Driver version: 9.17.10.3347 ig4icd64.dll
- NV driver branch: r343_98-7
- OS: Windows 8.1 64-bit build 9600
- Bios version: Intel Video BIOS
- GPU memory size: 2108MB
- GPU memory type: 256-bit GDDR5
- GPU memory location: GPU dedicated
- GPU temp: 43.0°C (min:43.0°C - max:48.0°C)
- Fan speed: 28.0% / 1350.0 RPM
- GPU cores: 384
- TDP: 170 Watts
- # Pstates: 3
- Current Pstate: P8
- Core: 405.0MHz
- Mem: 324.0MHz
- VDDC: 0.950V
- GPU and memory usage:
- GPU: 0.0%, max: 19.0%
- GPU memory: 12.5%
- GPU memory controller: 3.0%
- Limiting policies (NVIDIA):
- no limitation
GPU 3 - Intel(R) HD Graphics 3000
- GPU: SandyBridge(GT2)
- Device ID: 8086- 122
- Subvendor: ASUS (1043-844D)
- OS: Windows 8.1 64-bit build 9600
- GPU cores: 12
- TDP: 95 Watts

Any help/suggestions appreciated - realize I am a pretty green novice.

 
Solution

frag06

Honorable
Mar 17, 2013
1,353
0
11,960


The Gigabyte G1 is in-stock at Newegg.

Are you having any issues in other games?
 

Big Jeff

Distinguished
Oct 26, 2009
61
0
18,640
Well that is the only game I am playing currently - but no issues with playing back video, etc.. In ArchAge it is fine in the lowest graphic settings - turn it up at all and within 5 min my computer does a full shut down/reboot. I had been running the new Nvidia drivers for a week+ prior to that - so not thinking it was driver related.

I know the 560 Ti's are a bit outdated and it's time to upgrade - I just want to check if they are ok as I can move them into SLI mode on two of my teenager machines (each has a build with 1x 560 Ti). I didn't want to move a potentially defective card.

Newegg shows that Gigabyte card sold out also. I was hoping for the MSI or the ASUS 970......Newegg is suppose to email me if/when they come back available.
 

frag06

Honorable
Mar 17, 2013
1,353
0
11,960


Try one card at a time. If the same problem occurs with one card and not the other, you know there is something wrong with one of the cards.

Oftentimes, when you get random shutdowns under load the PSU is a likely cause. But it would be best to test the cards before looking into that.

I suggest you run Firestrike or Valley on each card. First together and then if the problem persists, try each one separately.
 
Solution