Yup that's what I have right now 466.11 drivers. And every single thing runs on my system without any issues or instability except RF9. So my deduction is that it probably is something to do with the drivers as marcushh777 says but I'm thinking it is some call to a low level library function that is happening in the RF code. Some obscure conflict that most likely will be hard to find without my actual machine to observe while running. Probably would have to use a software debugger maybe even at the assembly level to actually step through and trap the fault. And I suppose they are not going to go that far for one customer. If things do not improve after installing Win 10 and latest drivers I will be done for life with RF and will definitely let everyone else know about my unpleasant experience. Pretty much completely useless response from tech support, ... basically I'm on my own. I don't care about the cost or the lost money, I'm just really disappointing in not being able to use the product now that we are getting close to good flying weather. My solution so far has been to install on another machine that I have here and use it, ... not optimal but it works. Not really what I want, it's kind of like getting the very last piece of cake that everyone else didn't want and they have poked it with their fork and tossed it around, lolThe Zotac 1060 is an Nvidia card.
The latest drivers for the 1060 (version 466.11) are the same drivers for Windows 7 64bit and 10, 64bit and the same driver I am using for my 2080 video card
RF9.5 and RF-X work perfect on my Win10 system.
Zotac GTX 1060 and GTX 670 (Tail_Spin's old card) use the same recommended drivers on the Nvidia web site, version 466.11