Lost multi-GPU BOINC capability with Windows 10 Fall Creators Update

Message boards : Questions and problems : Lost multi-GPU BOINC capability with Windows 10 Fall Creators Update
Message board moderation

To post messages, you must log in.

1 · 2 · Next

AuthorMessage
archae86

Send message
Joined: 18 Jan 08
Posts: 36
United States
Message 82089 - Posted: 19 Oct 2017, 3:18:21 UTC

I have run three systems with dual dis-similar GPUs running Einstein applications under BOINC for many months.
Yesterday I was an early adopter after production release of the Windows 10 Fall Creators Update 10.00.16299.00 on one of those systems.

Ever since then BOINC on startup only has messages relating to one of the two GPUs installed in the system, and only runs Einstein work on that one. Oddly it is the less capable GPU, of older generation, in a lower priority PCIe slot, which is not connected to a monitor.

I downloaded from Nvidia and installed the currently recommended driver AFTER I did the Windows 10 update.
At the suggestion of someone on the Einstein forum I also tried the current beta developer's Vulkan driver, with no difference observed.

The system in question is listed here at Einstein.

Operating System: Microsoft Windows 10 Core x64 Edition, (10.00.16299.00)
CPU: Intel i3-4130 (Haswell)
GPU seen by BOINC: GTX 750 Ti in lower PCIe slot, not connected to any monitor or other device
GPU not mentioned or used by BOINC: GTX 1050 in top PCIe slot, driving a monitor
Nvidia driver installed: 387.92

While in my first Einstein post on this topic I claimed that other elements of the system only saw one GPU, that was wrong. The monitoring programs HWiNFO and GPU-Z report on both GPUs. Both GPUs are listed in the Control Panel Device Manager Display Adapter section.

When I have made (several) new attempts at display driver installation, my general practice has been this sequence:
1. run the uninstaller for the current driver as found in the Control Panel Programs and Features section
2. reboot to Windows Safe miminal
3. run DDU in the preferred mode
4. reboot and run the Nvidia installer, ticking the clean install box, and selecting on the graphics driver (no optional components)
5. reboot again and run BOINCMgr

I'm typing these detailed notes on another system, and find that I can't get a stable representation of the startup logging on the system of interest through BoincTasks for some reason, so I'll edit this message after posting or add a reply with that information after I post this.

While it could be that my loss of multi-GPU capability with the Fall Creators Update is coincidence, I'm concerned that for systems as I configure them it might be systematic, in which case I shall soon lose about half my total Einstein contribution capacity. I'd appreciate any ideas for things I might try.
ID: 82089 · Report as offensive
archae86

Send message
Joined: 18 Jan 08
Posts: 36
United States
Message 82090 - Posted: 19 Oct 2017, 3:23:22 UTC - in response to Message 82089.  

Here is the early part of the BOINCMgr event log for the system in this condition:

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
ID: 82090 · Report as offensive
Profile Jord
Volunteer moderator
Project administrator
Avatar

Send message
Joined: 29 Aug 05
Posts: 13466
Netherlands
Message 82091 - Posted: 19 Oct 2017, 5:33:25 UTC - in response to Message 82090.  
Last modified: 19 Oct 2017, 5:43:30 UTC

The one thing I saw was a missing Intel GPU complaint, so advice is to reinstall the Intel (motherboard chipset) drivers as well. I read yesterday someplace that there are new ones with support for this version of Windows. Have to check later where I saw that, when my desktop computer has started, am now answering via my phone.

Edit: ah no, they were in the WPA2 break context.
Please do not private message me for tech support, these will be ignored!
ID: 82091 · Report as offensive
archae86

Send message
Joined: 18 Jan 08
Posts: 36
United States
Message 82096 - Posted: 19 Oct 2017, 12:24:41 UTC - in response to Message 82091.  

Ageless wrote:
The one thing I saw was a missing Intel GPU complaint, so advice is to reinstall the Intel (motherboard chipset) drivers as well.

I actively don't want to run BOINC work on any of my Intel GPUs, and as I only run Einstein, I accomplish that with an application preference setting at my Einstein web site account preferences by location. I also don't have a monitor connected to the motherboard graphics output on any of my systems.

Given that, do you advise Intel driver updating as appropriate for me?
ID: 82096 · Report as offensive
Profile Jord
Volunteer moderator
Project administrator
Avatar

Send message
Joined: 29 Aug 05
Posts: 13466
Netherlands
Message 82097 - Posted: 19 Oct 2017, 13:45:11 UTC - in response to Message 82096.  

Your given log says something different:
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

If you don't want to use the Intel GPU then don't select it in the Project preferences, at Einstein at https://einsteinathome.org/account/prefs/project

Adding Intel chipset drivers, or in the least making sure that the correct ones are installed, increases the way all parts of your motherboard interact with the operating system, so I would certainly try it. https://downloadcenter.intel.com/

Last for my part for now, what does Microsoft say about it? You have reported it to them as well, haven't you?
Please do not private message me for tech support, these will be ignored!
ID: 82097 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 3658
United Kingdom
Message 82099 - Posted: 19 Oct 2017, 14:43:10 UTC - in response to Message 82097.  
Last modified: 19 Oct 2017, 15:14:09 UTC

Your given log says something different:
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

If you don't want to use the Intel GPU then don't select it in the Project preferences, at Einstein at https://einsteinathome.org/account/prefs/project
Note that that part of the log refers to app version, not to any current tasks. Once you have run a given application type - even just once as a test - the <app_version> record for that application, and the corresponding downloaded files, remain in client_state.xml and the project folder respectively - for ever. (unless you do a 'reset project')

I thought there was an issue on Github (it might even have been originated by the Einstein project) requesting a mechanism for removing stale app_version records from client hosts at server request, but I can't find it just now.

Edit - I've just looked at my oldest working machine, and client_state.xml lists 22 different <app_version> records for Einstein, and the project directory lists 30 application binary files totalling 445 MB - that includes several graphics app files, with the oldest binaries dating back to 2009. I'm not even running Einstein on that machine at the moment!
ID: 82099 · Report as offensive
archae86

Send message
Joined: 18 Jan 08
Posts: 36
United States
Message 82100 - Posted: 19 Oct 2017, 15:05:25 UTC - in response to Message 82097.  

Ageless wrote:
Your given log says something different:
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

If you don't want to use the Intel GPU then don't select it in the Project preferences, at Einstein at https://einsteinathome.org/account/prefs/project

Adding Intel chipset drivers, or in the least making sure that the correct ones are installed, increases the way all parts of your motherboard interact with the operating system, so I would certainly try it. https://downloadcenter.intel.com/

Last for my part for now, what does Microsoft say about it? You have reported it to them as well, haven't you?

I have the "use INTEL GPU" option deselected on all four locations shown for my Einstein preferences, and have for many months. However, as Richard's comment hints, it is true that I tried running Einstein tasks of some type on the Intel on-CPU GPU on one or more of my hosts in the past, and this system is probably one of them.

As I have some lingering hope that some dangling leftover in my BOINC setup may be a part of this, a full reset and re-install is likely something I'll try within the week, if I don't stumble on some resolution sooner. On the way there, I may pull the 750 Ti (the "extra" card in a non primary PCIe slot) out of the box, and check that BOINC is then able and willing to use the 1050 primary card.

I've probably never updated the chipset drivers on this system since I built it, so I'll take a look at the link you provided, and assuming I think I understand what to do, perform an update.

I have not reported this to Microsoft, and have no idea of a suitable reporting point. If you have a suggestion, I'm all ears. At the moment, since all of GPU-Z, HWiNFO, and the Windows Control Panel device list show the GTX 1050, and BOINC seems not to see it, I'm inclined to regard this is at least in part a BOINC problem, and not necessarily a purely Microsoft or Nvidia problem. I don't know whether my starting this thread constitutes reporting this experience to BOINC. If not, is there someplace I should make a report?
ID: 82100 · Report as offensive
Profile Jord
Volunteer moderator
Project administrator
Avatar

Send message
Joined: 29 Aug 05
Posts: 13466
Netherlands
Message 82102 - Posted: 19 Oct 2017, 15:26:38 UTC - in response to Message 82100.  

At the moment, since all of GPU-Z, HWiNFO, and the Windows Control Panel device list show the GTX 1050, and BOINC seems not to see it, I'm inclined to regard this is at least in part a BOINC problem, and not necessarily a purely Microsoft or Nvidia problem.
Okay, so as every time that Microsoft updates their operating system, the day after that people flock to the BOINC or project forums with missing items that BOINC should fix, because Microsoft updated their operating system... see where I am going with this?

Before you updated Windows, everything was working fine, all your GPUs were recognized.
After you updated Windows, everything is not working fine, not all your GPUs are recognized.
How is that a BOINC problem then? Did BOINC update as well at the same time as your Windows did?

The last time Microsoft updated Windows, it caused the Seti screen saver not to work anymore as it should have. Eventually Microsoft came out with a fix for this. It was their bug.
Yes, it's possible that BOINC's method of detecting the GPUs is causing friction with Windows method of showing multiple GPUs, perhaps that their Augmented Reality addition is causing this, or cannot work with all GPUs, or I don't know.

To report bugs to Microsoft, you can use the Feedback Hub app. This does require a Microsoft Live Account or Facebook login.

You can also enable the coproc_debug flag in Advanced View->Options->Event Log Options, exit & restart BOINC and then post the log of that. Perhaps that it shows what happens with the missing GPU. Also know that 99% of problems with the detection of GPUs is due to (bad) drivers. That an older GPU is detected fine with newer drivers says nothing in this.
Please do not private message me for tech support, these will be ignored!
ID: 82102 · Report as offensive
Juha
Volunteer developer
Volunteer tester
Help desk expert

Send message
Joined: 20 Nov 12
Posts: 801
Finland
Message 82103 - Posted: 19 Oct 2017, 16:01:08 UTC - in response to Message 82100.  

Could you copy-paste the output of clinfo here? If it didn't come with the drivers you can download it from here.
ID: 82103 · Report as offensive
archae86

Send message
Joined: 18 Jan 08
Posts: 36
United States
Message 82104 - Posted: 19 Oct 2017, 16:19:21 UTC - in response to Message 82103.  

Could you copy-paste the output of clinfo here? If it didn't come with the drivers you can download it from here.

Interesting: this viewpoint only mentions the 750 Ti and not the 1050

Number of platforms: 1
Platform Profile: FULL_PROFILE
Platform Version: OpenCL 1.2 CUDA 9.1.0
Platform Name: NVIDIA CUDA
Platform Vendor: NVIDIA Corporation
Platform Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer


Platform Name: NVIDIA CUDA
Number of devices: 1
Device Type: CL_DEVICE_TYPE_GPU
Device ID: 4318
Max compute units: 5
Max work items dimensions: 3
Max work items[0]: 1024
Max work items[1]: 1024
Max work items[2]: 64
Max work group size: 1024
Preferred vector width char: 1
Preferred vector width short: 1
Preferred vector width int: 1
Preferred vector width long: 1
Preferred vector width float: 1
Preferred vector width double: 1
Max clock frequency: 1254Mhz
Address bits: 14757395255531667488
Max memory allocation: 536870912
Image support: Yes
Max number of images read arguments: 256
Max number of images write arguments: 16
Max image 2D width: 16384
Max image 2D height: 16384
Max image 3D width: 4096
Max image 3D height: 4096
Max image 3D depth: 4096
Max samplers within kernel: 32
Max size of kernel argument: 4352
Alignment (bits) of base address: 4096
Minimum alignment (bytes) for any datatype: 128
Single precision floating point capability
Denorms: Yes
Quiet NaNs: Yes
Round to nearest even: Yes
Round to zero: Yes
Round to +ve and infinity: Yes
IEEE754-2008 fused multiply-add: Yes
Cache type: Read/Write
Cache line size: 128
Cache size: 81920
Global memory size: 2147483648
Constant buffer size: 65536
Max number of constant args: 9
Local memory type: Scratchpad
Local memory size: 49152
Error correction support: 0
Profiling timer resolution: 1000
Device endianess: Little
Available: Yes
Compiler available: Yes
Execution capabilities:
Execute OpenCL kernels: Yes
Execute native function: No
Queue properties:
Out-of-Order: Yes
Profiling : Yes
Platform ID: 00364200
Name: GeForce GTX 750 Ti
Vendor: NVIDIA Corporation
Driver version: 387.92
Profile: FULL_PROFILE
Version: OpenCL 1.2 CUDA
Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer
ID: 82104 · Report as offensive
Juha
Volunteer developer
Volunteer tester
Help desk expert

Send message
Joined: 20 Nov 12
Posts: 801
Finland
Message 82105 - Posted: 19 Oct 2017, 17:37:45 UTC - in response to Message 82104.  

Looks like a driver bug to me. I don't really know where to report it. Nvidia has a thread for Fall Creators Update in GeForce forums but I don't know if that's the right place for computing related issues. There is also Developer forums but no threads about FCU.
ID: 82105 · Report as offensive
archae86

Send message
Joined: 18 Jan 08
Posts: 36
United States
Message 82107 - Posted: 19 Oct 2017, 18:16:24 UTC - in response to Message 82105.  

Juha wrote:
Looks like a driver bug to me. I don't really know where to report it. Nvidia has a thread for Fall Creators Update in GeForce forums but I don't know if that's the right place for computing related issues. There is also Developer forums but no threads about FCU.

I've made a post in the Nvidia Fall Creators thread you mentioned. Possibly they will advise me if there is a better place.

Is it pointless for me to uninstall the (recommended by Nvidia for Fall Creators Edition) 387.92 driver and try 385.41, which is only a couple of months old and works for me on another un-updated system? Or are older Nvidia drivers pretty much guaranteed not to work on an updated system?

Thanks
ID: 82107 · Report as offensive
Juha
Volunteer developer
Volunteer tester
Help desk expert

Send message
Joined: 20 Nov 12
Posts: 801
Finland
Message 82109 - Posted: 19 Oct 2017, 18:40:32 UTC - in response to Message 82107.  

I suppose it can't hurt to try an older driver.

I think you have plenty of GPUs around so what you could try is replacing the 1050 with another 750 to see if the issue is in multi GPU support in general or multi GPU generations.
ID: 82109 · Report as offensive
archae86

Send message
Joined: 18 Jan 08
Posts: 36
United States
Message 82110 - Posted: 19 Oct 2017, 18:52:38 UTC - in response to Message 82109.  

Juha wrote:
I think you have plenty of GPUs around so what you could try is replacing the 1050 with another 750 to see if the issue is in multi GPU support in general or multi GPU generations.

As it happens, at the transition the top slot was a 970. I swapped in the 1050 after some hours of unsuccessful fiddling, figuring there might be a difference, and that in any case my plan all along had been to run that card in that system.

So the combinations tried so far are:
1. 970 (Maxwell2) in primary slot with 750 Ti (Maxwell) in secondary slot--only the 750 Ti is seen and used by BOINC.
2. 1050 (Pascal) in primary slot with 750 Ti (Maxwell) in secondary slot--only the 750 Ti is seen and used by BOINC.

At one point I had about five total 750/750 Ti cards. I'll poke around and see if I can find one to try swapping in the primary slot. I'm not sure to what degree Maxwell and Maxwell2 cards can be consider same/different generations.

I think I'll try the somewhat older driver option first. If that fails and I don't get a bright new idea, I actually plan to pull the 750 Ti out and check that the 1050 alone is detected and operates correctly, then try adding the 750 without doing uninstall, DDU, install.
ID: 82110 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 3658
United Kingdom
Message 82111 - Posted: 19 Oct 2017, 19:07:35 UTC - in response to Message 82110.  
Last modified: 19 Oct 2017, 19:08:00 UTC

There is one alternative possibility: that you have coincidentally suffered a hardware failure of the primary slot. I'd suggest a brief test with the currently-working 750 Ti card (solo) in the primary slot.
ID: 82111 · Report as offensive
Profile Richie

Send message
Joined: 2 Jul 14
Posts: 174
Finland
Message 82112 - Posted: 19 Oct 2017, 19:30:50 UTC

This idea is really blind fishing, but did you have hybrid sleep enabled on the power options before the Fall Creators Update? I've seen many notes that this Windows update has forcefully enabled hybrid sleep or fast boot, no matter how that option was set before the update. On my computer that happened also. I wonder if that could mess the proper identification of what has been installed on the pci-e slots.
ID: 82112 · Report as offensive
archae86

Send message
Joined: 18 Jan 08
Posts: 36
United States
Message 82114 - Posted: 19 Oct 2017, 20:38:58 UTC - in response to Message 82112.  

My power option remains the high performance one, and clicking around I could not find anything turned on to allow optional lower CPU states, any form of sleeping or hibernation, and such.

However, clicking the "choose what the power button" does item revealed to me that "turn on fast startup" was checked under the shutdown settings. Maybe the update did that to me, as I think my policy is no to enable it.

I've turned that off. The comment claims it does not apply for restarts, so I plan to do a full cold shutdown before I make another configuration change, just in case that fixes things.

Meanwhile I did install Nvidia's 385.41 driver, a relatively recent one which is successfully supporting a somewhat different two-GPU configuration on another of my systems (not yet OS upgrarded) but is not recommended by Nvidia for this OS update. It made no difference that I could detect. The system works, BOINC runs Einstein, but Clinfo reports only one card, BOINC startup messages only discuss one card, and only one Einstein task runs. (on the 750 Ti).

My next plans are to try a power off reboot. If that does nothing, I'll uninstall the driver, DDU, open the box and remove the 750Ti, so it will be a single 1050 in the primary slot, install the up-to-date driver, and see what I get, If, as I expect, it sees and uses the 1050 in the primary slot, the problem definition remains a somewhat fuzzy scope of failure to get the CUDA environment informed of one of the two cards when I have either 970 + 750 Ti or 1050 + 750 Ti.

As some of our major contributors run husky multi-CPU systems, and some of those are Windows 10, I imagine there will be screaming soon if this is a general problem. However a look at the Einstein top 50 list shows the specific release version of this Windows update (10.00.16299.00) on only one system, which belongs to Mumak, which is a AMD Radeon RX Vega system, which does not exclude the prime possibilities.
ID: 82114 · Report as offensive
archae86

Send message
Joined: 18 Jan 08
Posts: 36
United States
Message 82116 - Posted: 19 Oct 2017, 21:34:00 UTC

Full cold reboot with fast startup turned off and still running the couple of months-old driver made no difference.

Then I removed the 750 Ti from the secondary slot, leaving untouched the 1050 in the primary slot, but doing a full driver uninstall, DDU, up-to-date driver install.

The 1050 was recognized by clinfo and by boinc, and an Einstein task is running on it as I type.

Over at the Nvidia forum, a user has posted a complaint asserting that he cannot use multiple GPUs. However he makes no reference to issues I recognize as CUDA recognition related, so possibly his problem is materially different from mine.

I've had about enough fun for today, so plan to leave the modern driver, one card, GTX 1050 in primary slot configuration running until tomorrow.

Tentatively, I think tomorrow I shall attempt simply adding back the 750Ti during power down with no driver uninstall, ... Assuming that puts me back where I've been, my next move will be to try a dual 750 Ti card configuration, using full driver clean changeover. As the two 750 Ti's will be the exact same EVGA model ID, if they work it may be that some aspect of non-similarity among multiple cards installed is a factor.

If that does not work, I'll just put the 1050 back in alone and wait to see if someone else learns something I can go to school on.
ID: 82116 · Report as offensive
Profile Richie

Send message
Joined: 2 Jul 14
Posts: 174
Finland
Message 82123 - Posted: 20 Oct 2017, 8:39:33 UTC
Last modified: 20 Oct 2017, 8:40:56 UTC

Ageless suggested to install/update the Intel chipset drivers. I just got a faint feeling of reading somewhere about multi-GPU problem (AMD/Nvidia) that seemed to be caused by insufficient Intel (GPU) drivers on the machine. Specifically on a modern platform with integrated Intel GPUs. I think that Intel chipset driver situation is what I would prioritize to check on.

What's the model of the motherboard on that computer? Could there be settings in the BIOS/UEFI that have an effect on the pci-e configuration? Also, if there's a newer BIOS/UEFI version available for that board I definitely recommend to go on and flash.
ID: 82123 · Report as offensive
archae86

Send message
Joined: 18 Jan 08
Posts: 36
United States
Message 82129 - Posted: 20 Oct 2017, 14:27:56 UTC - in response to Message 82123.  

What's the model of the motherboard on that computer? Could there be settings in the BIOS/UEFI that have an effect on the pci-e configuration? Also, if there's a newer BIOS/UEFI version available for that board I definitely recommend to go on and flash.
It is an Asrock Z87 Extreme3. I purchased it in early 2014, and the Asrock support page lists updated release dates later than that for almost everything.

Asrock pretty strongly advises not to update (especially the UEFI BIOS) unless you have a problem (probably because they have experience with users bricking their motherboards). Which is part of my defense for never having done so since I built the machine. But I clearly have a problem, and with each passing hour the lack of reports from other multi-GPU users strengthens the case that something in my particular system configuration contributes.

So I plan to gird my loins and go on an update binge today, prioritizing the BIOS at the top of the list. After I've gone through the Asrock support page for this motherboard, I'll try to see whether the Intel updater wants to do anything. I tried running that already on my primary system, and it professed to find no Intel products to update!?
ID: 82129 · Report as offensive
1 · 2 · Next

Message boards : Questions and problems : Lost multi-GPU BOINC capability with Windows 10 Fall Creators Update

Copyright © 2020 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.