EVGA

Precision X GPU2 is actually GPU1

Author
Syan48306
Superclocked Member
  • Total Posts : 211
  • Reward points : 0
  • Joined: 2012/04/09 22:07:46
  • Status: offline
  • Ribbons : 2
2017/03/16 15:46:39 (permalink)
I've got a problem with Precision X my new 1080Ti's. It's swapped the two GPUs where GPU2 while it's actually GPU1. Afterburner can "change GPU assignment" but it doesn't look like Precision X has this ability, does it? How do you guys deal with this mixup and what is the solution to fix it? 
 


i7 2700K @ 5.0Ghz
Asus Maximus IV Extreme-Z
EVGA GTX 690
Corsair Vengeance 16GB 1866
Corsair 800D with RX360 Custom Water Loop
#1

15 Replies Related Threads

    ty_ger07
    Insert Custom Title Here
    • Total Posts : 21171
    • Reward points : 0
    • Joined: 2008/04/10 23:48:15
    • Location: traveler
    • Status: offline
    • Ribbons : 270
    Re: Precision X GPU2 is actually GPU1 2017/03/16 17:16:41 (permalink)
    This is an NVIDIA related driver thing. It isn't really a driver bug exactly, but it becomes a problem when software engineers (Precision's developement team in this example) assume that the first video card entry is #1 and the second entry is #2. In reality, the cards could have been stored in the driver's hardware index in any order. The easiest solution would be for Precision's software developement team to incorporate an option to switch the order the cards are listed. Until then, the only "fix" that I know of is for you to simply remember that the order is reversed.

    Since this has been a known issue for at least a year, I wouldn't hold my breath for NVIDIA or EVGA to create a fix.

    ASRock Z77 • Intel Core i7 3770K • EVGA GTX 1080 • Samsung 850 Pro • Seasonic PRIME 600W Titanium
    My EVGA Score: 1546 • Zero Associates Points • I don't shill

    #2
    Syan48306
    Superclocked Member
    • Total Posts : 211
    • Reward points : 0
    • Joined: 2012/04/09 22:07:46
    • Status: offline
    • Ribbons : 2
    Re: Precision X GPU2 is actually GPU1 2017/03/16 17:20:49 (permalink)
    Man... that's no good. It's not just a set it and forget it thing. It's all wrong in the OSD as well. I went as far as to try to swap the card orders and reinstall the drivers with just one card plugged in. 
     
    No luck. 
     
    If EVGA doesn't get a fix in soon, I'll probably just go and use Afterburner :/

    i7 2700K @ 5.0Ghz
    Asus Maximus IV Extreme-Z
    EVGA GTX 690
    Corsair Vengeance 16GB 1866
    Corsair 800D with RX360 Custom Water Loop
    #3
    ty_ger07
    Insert Custom Title Here
    • Total Posts : 21171
    • Reward points : 0
    • Joined: 2008/04/10 23:48:15
    • Location: traveler
    • Status: offline
    • Ribbons : 270
    Re: Precision X GPU2 is actually GPU1 2017/03/16 17:38:13 (permalink)
    You might as well switch to Afterburner.  As I said, this will almost certainly not be resolved any time soon.
     
    From over a year ago:
    http://forums.evga.com/FindPost/2394806
     
    schmorblatz
    Same here with my Sigs. It is VERY annoying. I already posted here about this issue, but nobody cares...
     
    Have a look to device manager. Right click the GPUs, you should get the same wrong order (Bus PCI #).
     
    This seems to be a very common issue. Many monitoring apps do not report correctly multi GPU setups. I don't think it is mobo related, but software related.
     
    CPUID HWMonitor gives correct results (GPU 1 is first, GPU is 2nd and so on). Have a try.
     
    The reason is lazy use of NVAPI, or NVAPI bug.
     
    Technical hypothesis (and workaround for coders : it worked for me) :
     
    The enumeration function NvAPI_EnumPhysicalGPUs() fills an array with physical GPU handles, and gives the GPU count. (these handles are needed to communicate with GPUs). But the array is not sorted. Most monitoring applications consider that 1st physical GPU handle matches the 1st slot, 2nd the 2nd and so on. This is untrue (the array seems to be filled more or less randomly by the driver call). Another function has to be called to get the bus ID from the physical handle : NvAPI_GPU_GetBusId(), and the array has to be sorted according to BUS ID. (a simple bubble sort and bob's your uncle... ). Even device manager don't care about this.
     
    I just read NVidia documentation, and I wrote my own tiny monitoring app using NVAPI so I get the correct order. (hopefully I am only interested in temps : o/c functions need the top secret "non disclosure" API).

    Note: he provided examples which are easily reproducible and even provided a solution which he tested by writing his own monitoring application.  How much easier could he have made it for the Precision development team to research and correct this issue?  Instead, "nobody [at EVGA] cares". 
    post edited by ty_ger07 - 2017/03/16 17:46:50

    ASRock Z77 • Intel Core i7 3770K • EVGA GTX 1080 • Samsung 850 Pro • Seasonic PRIME 600W Titanium
    My EVGA Score: 1546 • Zero Associates Points • I don't shill

    #4
    z999z3mystorys
    CLASSIFIED Member
    • Total Posts : 4480
    • Reward points : 0
    • Joined: 2008/11/29 06:46:22
    • Location: at my current location
    • Status: offline
    • Ribbons : 23
    Re: Precision X GPU2 is actually GPU1 2017/03/16 18:28:21 (permalink)
    I noticed that the folding at home application does the same thing, keeps my two 1080s in reverse order.
    post edited by z999z3mystorys - 2017/03/16 18:33:57
    #5
    Cool GTX
    EVGA Forum Moderator
    • Total Posts : 30975
    • Reward points : 0
    • Joined: 2010/12/12 14:22:25
    • Location: Folding for the Greater Good
    • Status: offline
    • Ribbons : 122
    Re: Precision X GPU2 is actually GPU1 2017/03/16 20:49:08 (permalink)
    http://www.evga.com/precisionxoc/
    Version 6.1.2Release: 3/16/2017
     
    bcav noticed it first here
    https://forums.evga.com/FindPost/2631381
     

    Learn your way around the EVGA Forums, Rules & limits on new accounts Ultimate Self-Starter Thread For New Members

    I am a Volunteer Moderator - not an EVGA employee

    https://foldingathome.org -->become a citizen scientist and contribute your compute power to help fight global health threats

    RTX Project EVGA X99 FTWK Nibbler EVGA X99 Classified EVGA 3080Ti FTW3 Ultra


    #6
    bcavnaugh
    The Crunchinator
    • Total Posts : 38977
    • Reward points : 0
    • Joined: 2012/09/18 17:31:18
    • Location: USA Affiliate E5L3CTGE12 Associate 9E88QK5L7811G3H
    • Status: offline
    • Ribbons : 282
    Re: Precision X GPU2 is actually GPU1 2017/03/16 21:35:49 (permalink)
    See Thread EVGA Precision XOC 6.1.2 Released #1
    post edited by bcavnaugh - 2017/03/16 21:38:06

    Associate Code: 9E88QK5L7811G3H


     
    #7
    ty_ger07
    Insert Custom Title Here
    • Total Posts : 21171
    • Reward points : 0
    • Joined: 2008/04/10 23:48:15
    • Location: traveler
    • Status: offline
    • Ribbons : 270
    Re: Precision X GPU2 is actually GPU1 2017/03/17 06:46:21 (permalink)
    I don't see any mention in the changelog indicating that the GPU order thing has finally been fixed in the latest version.

    ASRock Z77 • Intel Core i7 3770K • EVGA GTX 1080 • Samsung 850 Pro • Seasonic PRIME 600W Titanium
    My EVGA Score: 1546 • Zero Associates Points • I don't shill

    #8
    Syan48306
    Superclocked Member
    • Total Posts : 211
    • Reward points : 0
    • Joined: 2012/04/09 22:07:46
    • Status: offline
    • Ribbons : 2
    Re: Precision X GPU2 is actually GPU1 2017/03/17 07:49:52 (permalink)
    I'm not gonna lie, I'm really disappointed. I went as far as to reformat my entire PC and install everything with just one GPU and then once I got everything up and running, plug in the second GPU. Apparently that doesn't fix the problem either. 
     
    There's something fundamentally wrong with the nvidia drivers or Precision X because going from 1 GPU to 2 GPUs on the 1080Ti still ends up flipping them around. 
     
    Precision X NEEDS the option to swap the naming around...
     
    Off to download afterburner 

    i7 2700K @ 5.0Ghz
    Asus Maximus IV Extreme-Z
    EVGA GTX 690
    Corsair Vengeance 16GB 1866
    Corsair 800D with RX360 Custom Water Loop
    #9
    bcavnaugh
    The Crunchinator
    • Total Posts : 38977
    • Reward points : 0
    • Joined: 2012/09/18 17:31:18
    • Location: USA Affiliate E5L3CTGE12 Associate 9E88QK5L7811G3H
    • Status: offline
    • Ribbons : 282
    Re: Precision X GPU2 is actually GPU1 2017/03/17 08:43:47 (permalink)
    It is really not a big deal.
    Just wait and see what happens when you TRY to run GOW4 with a GTX 1080Ti Graphics Card.

    post edited by bcavnaugh - 2017/03/19 18:51:45

    Attached Image(s)


    Associate Code: 9E88QK5L7811G3H


     
    #10
    Squall_Rinoa86
    FTW Member
    • Total Posts : 1735
    • Reward points : 0
    • Joined: 2010/07/26 14:09:48
    • Location: The Empire State -> Hyde Park
    • Status: offline
    • Ribbons : 5
    Re: Precision X GPU2 is actually GPU1 2017/03/19 18:22:15 (permalink)
    Syan48306
    I'm not gonna lie, I'm really disappointed. I went as far as to reformat my entire PC and install everything with just one GPU and then once I got everything up and running, plug in the second GPU. Apparently that doesn't fix the problem either. 
     
    There's something fundamentally wrong with the nvidia drivers or Precision X because going from 1 GPU to 2 GPUs on the 1080Ti still ends up flipping them around. 
     
    Precision X NEEDS the option to swap the naming around...
     
    Off to download afterburner 




    I've had this issue for about a year with a Precision update.

    ASUS GPU Tweaker has them in correct order, as does SPECCY. It's generally speaking related to just Precision X.

    Don't hold your breath on them fixing it tho.




    PSU: EVGA SuperNOVA 1300 G2
    My Affiliate Code: AN1FW0VMG6
    #11
    squall-leonhart
    CLASSIFIED Member
    • Total Posts : 2904
    • Reward points : 0
    • Joined: 2009/07/27 19:57:03
    • Location: Australia
    • Status: offline
    • Ribbons : 24
    Re: Precision X GPU2 is actually GPU1 2017/03/20 04:33:29 (permalink)
    blaming evga or nvidia for an issue caused by windows itself.....

    CPU:Intel Xeon x5690 @ 4.2Ghz, Mainboard:Asus Rampage III Extreme, Memory:48GB Corsair Vengeance LP 1600
    Video:EVGA Geforce GTX 1080 Founders Edition, NVidia Geforce GTX 1060 Founders Edition
    Monitor:BenQ G2400WD, BenQ BL2211, Sound:Creative XFI Titanium Fatal1ty Pro
    SDD:Crucial MX300 275, Crucial MX300 525, Crucial MX300 1000
    HDD:500GB Spinpoint F3, 1TB WD Black, 2TB WD Red, 1TB WD Black
    Case:NZXT Phantom 820, PSU:Seasonic X-850, OS:Windows 7 SP1
    Cooler: ThermalRight Silver Arrow IB-E Extreme
    #12
    bcavnaugh
    The Crunchinator
    • Total Posts : 38977
    • Reward points : 0
    • Joined: 2012/09/18 17:31:18
    • Location: USA Affiliate E5L3CTGE12 Associate 9E88QK5L7811G3H
    • Status: offline
    • Ribbons : 282
    Re: Precision X GPU2 is actually GPU1 2017/03/20 09:29:45 (permalink)
    squall-leonhart
    blaming evga or nvidia for an issue caused by windows itself.....


    They need to Blame Someone, it is the way of life now.
    Not many users clean out or Delete the Video Key, I do this between each driver change.
    It is to bad that DDU does not clear this Registry Key.
    post edited by bcavnaugh - 2017/03/20 09:35:02

    Associate Code: 9E88QK5L7811G3H


     
    #13
    red2k
    New Member
    • Total Posts : 9
    • Reward points : 0
    • Joined: 2008/09/23 02:45:33
    • Status: offline
    • Ribbons : 0
    Re: Precision X GPU2 is actually GPU1 2017/06/07 10:49:14 (permalink)
    I also have this problem currently with my two GTX 1080 Ti FTW3's using Precision XOC 6.1.6. If there is a simple registry value to change or something I would do it myself. Anyone know of where the values may be stored?
    #14
    VVhiplash
    iCX Member
    • Total Posts : 392
    • Reward points : 0
    • Joined: 2011/06/15 11:42:22
    • Location: U.S.A
    • Status: offline
    • Ribbons : 1
    Re: Precision X GPU2 is actually GPU1 2017/11/25 19:11:22 (permalink)
    bcavnaugh
    squall-leonhart
    blaming evga or nvidia for an issue caused by windows itself.....


    They need to Blame Someone, it is the way of life now.
    Not many users clean out or Delete the Video Key, I do this between each driver change.
    It is to bad that DDU does not clear this Registry Key.


    What do you mean by clear out or delete the video key? I'd love to try this to see if I can use it as a fix for mine. My video cards have reported as "swapped" in the nvidia control panel for more than 2 years :P lol

    ll Steiger-Dynamics Maven ll Intel i7-5930k 4.2Ghz ll ASRock X99 Extreme6/AC ll Liqmax II 240 ll GeiL Super-Luce 32gb 2666mhz ll (x2)EVGA GTX 980 SC ll Samsung XP941 500gb and 850 Pro 1TB ll EVGA PS 1000W Platinum ll
    #15
    Sajin
    EVGA Forum Moderator
    • Total Posts : 49165
    • Reward points : 0
    • Joined: 2010/06/07 21:11:51
    • Location: Texas, USA.
    • Status: online
    • Ribbons : 199
    Re: Precision X GPU2 is actually GPU1 2017/11/26 03:20:39 (permalink)
    VVhiplash
    bcavnaugh
    squall-leonhart
    blaming evga or nvidia for an issue caused by windows itself.....


    They need to Blame Someone, it is the way of life now.
    Not many users clean out or Delete the Video Key, I do this between each driver change.
    It is to bad that DDU does not clear this Registry Key.


    What do you mean by clear out or delete the video key? I'd love to try this to see if I can use it as a fix for mine. My video cards have reported as "swapped" in the nvidia control panel for more than 2 years :P lol

    He is talking about deleting the video key inside the registry...

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video (highlight the Video key and press the delete key.)

    NOTE: When deleting the video key you will be prompted with an error saying "Error deleting key, Cannot delete Video: Error while deleting key." Just ignore the error and select OK, all keys within the Video key will be deleted except for ones that cannot be deleted.
    #16
    Jump to:
  • Back to Mobile