Windows 10 Fall Creators update 10.00.16299.00

Gary and Richie,

Thanks for the suggestions.  I actually had the "plug in another monitor" idea myself, and with your suggesting it, intend to have a try tomorrow (I happen have an older spare monitor around, so won't have to disturb a machine, but will have to pull the affected case out from the furniture).

Richie, the machine is question is my wife's primary use machine, so I'd like reasonable hope that the Vulkan Developer Beta is not likely to cause harm, and is likely to be reversible.  

When I made my post I had no idea how new Fall Creators Update actually was, but a few searches suggest it is less than 24 hours old in general public distribution.  Quite possibly my main need is to wait a bit for Nvidia to get told that others have problems, and to fix them in a driver revision.  While I assume Nvidia had a version to work against in house some time back, there is nothing like exposing code to tens of thousands of users to show what has been missed.

I must considerably revise my description of the details of my problem, but after some invasion of the hardware, and multiple software installations and tests, the basic fact remains that on my offending system, BOINC only says it sees one GPU, and only runs Einstein work on that one GPU.  Oddly it is using the less capable GPU, which is not installed in the top PCIe slot, and is not the GPU connected to the system monitor.

I did try the Vulkan Beta developer's driver, and saw no difference in behavior, so I have reverted to the most recent production Nvidia driver release.

HOWEVER, I was over-generalizing in claiming that the two GPU cards were not seen by Windows, Nvidia or both.

In fact all of HWINFO, GPU-Z, and the Windows Control Panel Device Manager Display Adapter list both cards I currently have installed.  As of now (not yesterday) that is an GTX 1050 in the top PCIe slot, which is driving the system monitor, and which is not noticed by BOINC, and not used for Einstein work, and a 750 Ti which is in a lower PCIe slot, and is not currently connected to anything.

During my fiddling around, I did boot the system with separate monitors attached to these two cards, and pixels were indeed sent to both of them.  So it seems the system including Windows has much awareness that they both exist.

I updated the BOINCmgr to the current recommended version, without change in my situation.  I checked that my cc_config.xml had the line to instruct that all GPUs be used (it already did).

The reason for swapping in the 1050 for the 970 is that I had always planned that as the final configuration for this machine, and while I was fiddling around I preferred to get to that final configuration sooner.

I still have hope that a new release of something, or new wisdom on something to try, will get both cards doing something useful.  If not, I should pull out the 750Ti, as I am getting less BOINC work done and consuming more power than I think would the the case were only the 1050 in the box.  I'm quite afraid that when the Windows Fall Creators Update is installed on my other two GPU systems it will ruin their ability to use both cards, also.

The only idea I have at the moment is to install up-to-date versions of Afterburner and Nvidia Inspector, which might perhaps remove a monitoring anomaly, but are unlikely to correct my inability to have BOINC see both cards and use them.

I'm not much of a  BOINC forum participant. Do you think I should attempt to start a thread there on this problem?

Gary, I've created a thread on the BOINC user forum "Questions and Problems" 

Here is the beginning of the event log for the system in question in the current (undesirable) state:

10/18/2017 4:59:56 PM | | Starting BOINC client version 7.8.3 for windows_x86_64

10/18/2017 4:59:56 PM | | log flags: file_xfer, sched_ops, task, http_debug
10/18/2017 4:59:56 PM | | Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8
10/18/2017 4:59:56 PM | | Data directory: C:\ProgramData\BOINC
10/18/2017 4:59:56 PM | | Running under account Beth
10/18/2017 4:59:58 PM | | CUDA: NVIDIA GPU 0: GeForce GTX 750 Ti (driver version 387.92, CUDA version 9.1, compute capability 5.0, 2048MB, 1689MB available, 1606 GFLOPS peak)
10/18/2017 4:59:58 PM | | OpenCL: NVIDIA GPU 0: GeForce GTX 750 Ti (driver version 387.92, device version OpenCL 1.2 CUDA, 2048MB, 1689MB available, 1606 GFLOPS peak)
10/18/2017 4:59:58 PM | | app version refers to missing GPU type intel_gpu
10/18/2017 4:59:58 PM | Einstein@Home | Application uses missing intel_gpu GPU
10/18/2017 4:59:58 PM | | Host name: Stoll8
10/18/2017 4:59:58 PM | | Processor: 4 GenuineIntel Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz [Family 6 Model 60 Stepping 3]
10/18/2017 4:59:58 PM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 fma cx16 sse4_1 sse4_2 movebe popcnt aes f16c rdrandsyscall nx lm avx avx2 vmx tm2 pbe fsgsbase bmi1 smep bmi2
10/18/2017 4:59:58 PM | | OS: Microsoft Windows 10: Core x64 Edition, (10.00.16299.00)
10/18/2017 4:59:58 PM | | Memory: 7.95 GB physical, 15.95 GB virtual
10/18/2017 4:59:58 PM | | Disk: 1.82 TB total, 1.73 TB free
10/18/2017 4:59:58 PM | | Local time is UTC -6 hours
10/18/2017 4:59:58 PM | | Config: GUI RPCs allowed from:
10/18/2017 4:59:58 PM | | 192.168.1.100
10/18/2017 4:59:58 PM | | 192.168.1.101
10/18/2017 4:59:58 PM | | 192.168.1.102
10/18/2017 4:59:58 PM | | 192.168.1.103
10/18/2017 4:59:58 PM | | 192.168.1.104
10/18/2017 4:59:58 PM | | 192.168.1.105
10/18/2017 4:59:58 PM | | 192.168.1.106
10/18/2017 4:59:58 PM | | 192.168.1.107
10/18/2017 4:59:58 PM | | 192.168.1.108
10/18/2017 4:59:58 PM | | 192.168.1.109
10/18/2017 4:59:58 PM | | 192.168.0.100
10/18/2017 4:59:58 PM | | 192.168.0.101
10/18/2017 4:59:58 PM | | 192.168.0.102
10/18/2017 4:59:58 PM | | 192.168.0.103
10/18/2017 4:59:58 PM | | 192.168.0.104
10/18/2017 4:59:58 PM | | 192.168.0.105
10/18/2017 4:59:58 PM | | 192.168.0.106
10/18/2017 4:59:58 PM | | 192.168.0.107
10/18/2017 4:59:58 PM | | 192.168.0.108
10/18/2017 4:59:58 PM | | 192.168.0.117
10/18/2017 4:59:58 PM | | 192.168.0.157
10/18/2017 4:59:58 PM | | 192.168.0.109
10/18/2017 4:59:58 PM | | 192.168.0.160
10/18/2017 4:59:58 PM | | 192.168.0.151
10/18/2017 4:59:58 PM | | 192.168.0.145
10/18/2017 4:59:58 PM | | 192.168.0.170
10/18/2017 4:59:58 PM | | Config: use all coprocessors
10/18/2017 4:59:59 PM | Einstein@Home | URL http://einstein.phys.uwm.edu/; Computer ID 10659288; resource share 99
10/18/2017 5:00:04 PM | Einstein@Home | General prefs: from Einstein@Home (last modified ---)
10/18/2017 5:00:04 PM | Einstein@Home | Computer location: home
10/18/2017 5:00:04 PM | | General prefs: using separate prefs for home
10/18/2017 5:00:04 PM | | Preferences:
10/18/2017 5:00:04 PM | | max memory usage when active: 4069.28 MB
10/18/2017 5:00:04 PM | | max memory usage when idle: 7324.70 MB
10/18/2017 5:00:05 PM | | max disk usage: 60.00 GB
10/18/2017 5:00:05 PM | | max CPUs used: 3
10/18/2017 5:00:05 PM | | (to change preferences, visit a project web site or select Preferences in the Manager)
10/18/2017 5:00:05 PM | | [http] HTTP_OP::init_get(): https://einsteinathome.org/rss_main.php