the thread just ate my response.
this has been the most mind boggling install in my nearly two decades of IT.
So, 2010 Mac Pro 5,1 dual Xeon, 64GB RAM running Win 7 of SSD, Win 10 on HDD
Display1 is Samsung with a max resolution of 1920x1080
Display2 is Samsung 1200x1920 (portrait)
Display3 is Samsung 1920x1080
Display4 is Samsung 4:3, only using it with AMD5770 and NvidiaGT120 to see if there is any display whatsoever and Display4 never sees connection to Nvidia 1660 Ti
trial and error,
Assume fails result in shutdown and cold restart.
1)
Nvidia 1660 Ti in PCIe 16x 1
Result: does not fit, it's butting against the chassis, it's like 1/2mm off but it wont sit level.
2)
Nvidia 1660 Ti in PCIe 16x 2
Result: fits, starts up, but no display what so ever
3)
Nvidia 1660 Ti in PCIe 16x 2
AMD5770 in PCIe 16x 1
boot to Win7, install drivers, prompted to reboot.
Reboot.
No display on Nvidia 1660 Ti, but reboots and display on AMD5770
4)
shutdown
Nvidia 1660 Ti in PCIe 16x 2
NvidiaGT120 in PCIe 16x 1
Result: BSOD at boot
Nvidia 1660 Ti in PCIe 16x 2
NvidiaGT120 in PCIe 4x RAID
Result: BSOD boot
Thinking; bad card? Fans are spinning but thats not a measure of working
So now I'm thinking send back or check power? OS?
5)
AMD5770 in PCIe 16x 1
Boot to Windows 10
Install drivers
Shutdown,
install Nvidia 1660 Ti in PCIe 16x 2
reboot
Result: Now I'm seeing display from HDMI to HDMI, I connect the two DP to HDMI to the other two displays
6)
Boot to Windows 7
Nvidia 1660 Ti in PCIe 16x 2
AMD5770 in PCIe 16x 1
No display on Nvidia 1660 Ti
Install drivers
Shutdown, uninstall Nvidia 1660 Ti, restart
install Nvidia 1660 Ti in PCIe 16x 2
Shutdown, install Nvidia 1660 Ti into PCIe 16x 2
uninstall and reinstall driver
Result: Display working on Nvidia 1660 Ti
7)
Shutdown
remove AMD5770 from PCIe 16x 1
boot to Win7
No display
...this goes on, and I'm still in Windows 7
At some point I uninstall the drivers and loose the display on Nvidia 1660 Ti again
I reinstall several times and nothing is happening on Nvidia 1660 Ti, high fans, no display, I think I tried a PRAM zap about 3x at this point
Windows Device Manager sees this is a MSI GeForce 1660Ti, but no display
GPU-Z utility sees the GPU as Generic, but does see it's an MSI device but erroneously reporting 1GB VRAM and is actually slower than AMD5770
did I blow up the card?
The next combo is something like:
try Win 10. Nvidia 1660 Ti is not having any issue, I screwed something up in Win 7
I notice Win 7 does complete boot but no display. I can hear the MS login chime, and the fans on the card are at full draw
disable Nvidia 1660 Ti from device manager, uninstall drivers from from device manger, reinstall driver, reboot and now I have display on Nvidia 1660 Ti
Windows Device Manager sees Nvidia 1660 Ti as correct, GPU-Z sees the card as correct as well; 6GB DDR6, 1536 Cuda cores, etc. running quiet as a church mouse.
the next thing I notice off of Nvidia 1660 Ti is after I arrange the displays and set the resolution
Nvidia 1660 Ti output config is as follows Display Port (DP) (Position 1), HDMI (POS 2), DP(...3), DP(...4)
Display1 is fuzzy, the cable is DP to HDMI from POS 1 on the GPU
Display2 is fine: cable is HDMI to HDMI (POS 2)
Display3 is fuzzy: cable is DP to HDMI (POS 3)
Swap cable from POS 1 to Display 2
Display 2 looks fine
Swap cable from POS 2 (HDMI to HDMI) to Display 3
Display 3 looks fine
Display 1 is blurred, no shimmery artifacts or anything, it just looks crappy. I tried 60Hz., 59 Hz and 50Hz. No dice
This becomes DP to HDMI cable musical chairs for a while and settles on Display 2 and 3 look fine, Display 1 needs to get dropped down from 1920x1080 to 1680x1050(?) and appears to work.
I googled this, and it does appear to be an issue for many Nvidia users, the fix is sometimes waiting for new drivers but likely I will pick up two DP to DVI cables and try those
So with all that I'm putting all other troubleshooting on hold. I'm rendering surfaces in nearly reatime and for S&G's I ran Skyrim balls-to-the-wall and it did not stutter so I'll come back to this at some time soon, just not now.
