Dual NVIDIA GPU Configuration + AMD APU = Display nightmares

mustard010

Member
Sep 13, 2003
93
0
0
Hi all. I've been trying to run the following config to use Visual Studio 2010 + NVIDIA Parallel NSight (dual GPU for GPU debugging):

AMD APU A3
NVIDIA Geforce 520 Ti
NVIDIA Geforce 560 Ti
Gigabyte GA-A75-UD4H mobo.
550W Antec TruePower PS

Hypothetically, my build can power both video cards simultaneously correct? (note: no SLI/bridge) As in, upon build, Windows 7 should detect both cards?

Here is my issue. There is a x16 PCI-e and a x8 PCI-e. Whichever card is in the x16 slot is powered on and 'detected' by my computer. Is there any reason why the second video card won't work?

If it came down to purchasing the same 560 Ti, for identical builds, then I will be OK. However, I'm considering that this is an AMD APU issue and there is some sort of conflict. I would hate to return this (a pain) only to get an Intel-equivalent replacement.

In addition, is it reasonable to expect the on-board APU graphics will render the VGA/DVI mobo ports useless when a discrete GPU is installed?
 
Last edited:

greenhawk

Platinum Member
Feb 23, 2011
2,007
1
71
Hypothetically, my build can power both video cards simultaneously correct? (note: no SLI/bridge) As in, upon build, Windows 7 should detect both cards?

Whichever card is in the x16 slot is powered on and 'detected' by my computer. Is there any reason why the second video card won't work?

I'm considering that this is an AMD APU issue and there is some sort of conflict

is it reasonable to expect the on-board APU graphics will render the VGA/DVI mobo ports useless when a discrete GPU is installed?

1) if the computer powers up, it is generally off to a good start.

2) sounds like you might need to check the motherboard's bios to see what is needed to enable SLI (that is how both slots will be enabled). No need to add the SLI bridge on the cards. Though being a AMD board, you would be looking for crossfire references. Older boards needed a connector on the motherboard changed but that is going back a bit now.

3) having different GPUs in a system can cause issues, but the important thing to remember is NOT to install any GPU controlling software from any manufacture, just let windows control them.

4) it is normal for that to happen as the onboard GPU takes memory away from the system. Some boards do not allow you to change this feature while others have a bios option that allow you to select how it behavies when a GPU is in the main slot. My last computer did not give a choice, my current one does (gigabyte s775).
 

mustard010

Member
Sep 13, 2003
93
0
0
1) if the computer powers up, it is generally off to a good start.

2) sounds like you might need to check the motherboard's bios to see what is needed to enable SLI (that is how both slots will be enabled). No need to add the SLI bridge on the cards. Though being a AMD board, you would be looking for crossfire references. Older boards needed a connector on the motherboard changed but that is going back a bit now.

3) having different GPUs in a system can cause issues, but the important thing to remember is NOT to install any GPU controlling software from any manufacture, just let windows control them.

4) it is normal for that to happen as the onboard GPU takes memory away from the system. Some boards do not allow you to change this feature while others have a bios option that allow you to select how it behavies when a GPU is in the main slot. My last computer did not give a choice, my current one does (gigabyte s775).

Thanks. Both cards and both PCI-e work (I've swapped w/ only 1 running at one). I've looked for BIOS settings that will enable SLI to no avail. (There is one setting that will set if PCI/onboard will be the primary display... but has no effect).

I think I'm going to replace my motherboard now... I'm going to do (1) last hope-rescue and flash the BIOS to the current and see if there any new settings that appear. Considering the FM1 is somewhat new... I'm not surprised that it doesn't work out of the box.

Thanks for your help, google doesn't provide too many results for such a configuration.
 
Jan 27, 2009
182
0
0
Is the second card powered on at all? Or is it just not detected? It is a little difficult to determine from your original description.

If it 'powers up' then the next thing you should do is to boot into safemode (no graphics drivers are loaded, just vga drivers for maximum compatibility) and see what is detected from there. That should give you some information about whether it is a driver issue that is holding you back.

I know nVidia have previously done some funny things with their drivers in the past when an AMD gpu was also detected in the system. However it shouldn't effect what you are trying to achieve.
 

wahdangun

Golden Member
Feb 3, 2011
1,007
148
106
yeah i remember usually nvdia driver block physix support if the driver detect amd card. so maybe that was your problem
 

Lonbjerg

Diamond Member
Dec 6, 2009
4,419
0
0
yeah i remember usually nvdia driver block physix support if the driver detect amd card. so maybe that was your problem


PhysX has nothing to do with displays....PhysX is pure CUDA calaculations and dosn't affect displays.
 

Arkadrel

Diamond Member
Oct 19, 2010
3,681
2
0
This doesnt sound like a APU IGP issue.... more like someone haveing issues setting up SLI.
 

mustard010

Member
Sep 13, 2003
93
0
0
Is the second card powered on at all? Or is it just not detected? It is a little difficult to determine from your original description.

If it 'powers up' then the next thing you should do is to boot into safemode (no graphics drivers are loaded, just vga drivers for maximum compatibility) and see what is detected from there. That should give you some information about whether it is a driver issue that is holding you back.

I know nVidia have previously done some funny things with their drivers in the past when an AMD gpu was also detected in the system. However it shouldn't effect what you are trying to achieve.

The card powers up (fan blades are running). I'll give this a shot later [booting @safemode] and see what I can find