GPU detection failed, error 0xc0000005

Message boards : Questions and problems : GPU detection failed, error 0xc0000005
Message board moderation

To post messages, you must log in.

AuthorMessage
JakubH

Send message
Joined: 8 May 19
Posts: 2
Czech Republic
Message 91441 - Posted: 8 May 2019, 18:02:26 UTC
Last modified: 8 May 2019, 18:36:39 UTC

Hello,
I am having a problem, BOINC cannot detect my intel GPU. When it tries to, the detection appearently fails and exits with status 0xc0000005 (not 5, there is C at the front). I have tried googling it, but without any meaningfull result. I tried reinstalling the intel GPU driver, but that did not help. I used to have a dedicated nvidia GPU in my notebook, but it stopped working some time ago and I disabled it in bios, so I think that should not be the problem. Computations on the intel GPU used to work, but then it stopped. It was longer time ago, so I dont really remember if I changed something in the notebook.
I would appriciate any help with this, maily what the error code actually means and what might be wrong. Posting a couple of lines from the event log.
Thanks,
JakubH

2019-05-07 15:14:59 |  | Starting BOINC client version 7.14.2 for windows_x86_64
2019-05-07 15:14:59 |  | log flags: file_xfer, sched_ops, task
2019-05-07 15:14:59 |  | Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8
2019-05-07 15:14:59 |  | Data directory: C:\ProgramData\BOINC
2019-05-07 15:14:59 |  | Running under account jakub
2019-05-07 15:15:09 |  | GPU detection failed: process exited with status 0xc0000005: (unknown error)
2019-05-07 15:15:09 |  | No usable GPUs found
2019-05-07 15:15:09 |  | Host name: Jakub-PC
2019-05-07 15:15:09 |  | Processor: 4 GenuineIntel  Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz [Family 6 Model 58 Stepping 9]
2019-05-07 15:15:09 |  | 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 cx16 sse4_1 sse4_2 popcnt aes f16c rdrandsyscall nx lm avx vmx smx tm2 pbe fsgsbase smep
2019-05-07 15:15:09 |  | OS: Microsoft Windows 10: Professional x64 Edition, (10.00.17134.00)
2019-05-07 15:15:09 |  | Memory: 7.90 GB physical, 23.90 GB virtual
2019-05-07 15:15:09 |  | Disk: 464.34 GB total, 142.17 GB free
2019-05-07 15:15:09 |  | Local time is UTC +2 hours
2019-05-07 15:15:09 |  | No WSL found.
2019-05-07 15:15:09 |  | VirtualBox version: 6.0.2
2019-05-07 15:15:09 | PrimeGrid | Found app_config.xml
2019-05-07 15:15:09 |  | Config: GUI RPCs allowed from:
ID: 91441 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 4183
United Kingdom
Message 91442 - Posted: 8 May 2019, 18:38:31 UTC - in response to Message 91441.  

Any error code like that is pretty much guaranteed to be a Microsoft Windows NT status code, and very hard for anyone except a programmer to track down.

0xc0000005 is
STATUS_ACCESS_VIOLATION

The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s [read or write].
With a history like yours, it's possible that left-over code from the nvidia GPU is trying, but failing, to get information about the card you disabled.

I'd suggest that you run a utility like Display Driver Uninstaller to clean out the old, unwanted, code, reboot, and then run the Windows 10 updater to replace the intel driver that you do still want.
ID: 91442 · Report as offensive
JakubH

Send message
Joined: 8 May 19
Posts: 2
Czech Republic
Message 91448 - Posted: 9 May 2019, 10:20:40 UTC - in response to Message 91442.  

Thank you very much, that helped!
Using the utility you recommended, cleaning the nvidia leftovers removed the error, but BOINC was still unable to detect the intel GPU. So I also removed the intel driver and then installed it again from intel website. After restart, BOINC succesfully detected the intel GPU.
Thank you again,
JakubH
ID: 91448 · Report as offensive
rmunderw

Send message
Joined: 8 Jun 09
Posts: 3
Canada
Message 91645 - Posted: 28 May 2019, 2:19:46 UTC - in response to Message 91441.  

Are you using a intel 530 GPU? if so it is the newest driver from Intel is causing the problem. A work around is to roll back the driver. Start Boinc with the old driver and then with Boinc running upgrade to the new Intel driver. Down side is you have to repeat every time you stop Boinc or reboot the computer. Or just run on the old driver and don't upgrade until something gets fixed. Intel must have changed a call procedure.
ID: 91645 · Report as offensive
Stick

Send message
Joined: 10 Oct 09
Posts: 27
United States
Message 91715 - Posted: 5 Jun 2019, 5:11:13 UTC

I just did the latest Windows feature update - to Windows 10, version 1903 (from version 1803) and now have essentially the same problem. That is, my GPU is no longer recognized by BOINC. (BTW - The update took a little more than 3 hours.) A bit later, when I discovered the missing GPU issue, I looked for the latest Intel Driver, downloaded and installed it after using DDU to clear the old one. It didn't help. And neither did doing a BOINC Repair Install.

Bottom line - if you are thinking about the latest Windows feature update, waiting a while is probably probably a good idea.
ID: 91715 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 14286
Netherlands
Message 91716 - Posted: 5 Jun 2019, 7:17:44 UTC - in response to Message 91715.  

Non-detection of GPUs is almost always caused by lack of correct drivers, a problem with the newest drivers (try older ones) or Windows installing its own drivers which may lack required components.

Reinstalling BOINC only removes the program and puts it back in the directory. It won't change how hardware is detected.
Please do not private message me for tech support, these will be ignored!
ID: 91716 · Report as offensive
Stick

Send message
Joined: 10 Oct 09
Posts: 27
United States
Message 91743 - Posted: 6 Jun 2019, 19:33:15 UTC - in response to Message 91716.  

Ageless,

Thank you for the quick reply. I've tried several earlier Intel drivers and none of them work. So, I'm beginning to think that this time, it's not the driver. And I'm wondering if the new Windows Feature Update has a bug - maybe related to OpenCL. What do you thinK?

Stick
6/5/2019 3:13:01 PM | | Starting BOINC client version 7.14.2 for windows_x86_64
6/5/2019 3:13:01 PM | | log flags: file_xfer, sched_ops, task
6/5/2019 3:13:01 PM | | Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8
6/5/2019 3:13:01 PM | | Data directory: C:\ProgramData\BOINC
6/5/2019 3:13:18 PM | | OpenCL CPU: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 7.6.0.1125, device version OpenCL 2.1 (Build 0))
6/5/2019 3:13:18 PM | | No usable GPUs found
6/5/2019 3:13:18 PM | | app version refers to missing GPU type intel_gpu
6/5/2019 3:13:18 PM | collatz | Application uses missing intel_gpu GPU
6/5/2019 3:13:18 PM | collatz | Missing coprocessor for task collatz_sieve_91d26a92-7679-4b4c-9bd4-77ed8de7b9d3_0
6/5/2019 3:13:18 PM | | app version refers to missing GPU type intel_gpu
6/5/2019 3:13:18 PM | Einstein@Home | Application uses missing intel_gpu GPU
6/5/2019 3:13:18 PM | | app version refers to missing GPU type intel_gpu
6/5/2019 3:13:18 PM | SETI@home | Application uses missing intel_gpu GPU
6/5/2019 3:13:18 PM | | app version refers to missing GPU type intel_gpu
6/5/2019 3:13:18 PM | SETI@home | Application uses missing intel_gpu GPU
6/5/2019 3:13:18 PM | SETI@home | Missing coprocessor for task 11mr13ag.16322.108298.10.37.103_1
6/5/2019 3:13:18 PM | SETI@home | Missing coprocessor for task 11mr13ag.16311.108298.9.36.106_0
6/5/2019 3:13:18 PM | SETI@home | Missing coprocessor for task blc25_2bit_guppi_58406_22221_HIP20056_0089.29461.409.21.44.122.vlar_0
6/5/2019 3:13:18 PM | SETI@home | Missing coprocessor for task blc25_2bit_guppi_58406_20894_HIP20019_0085.30397.0.22.45.182.vlar_0
6/5/2019 3:13:18 PM | | Host name: LAPTOP-4OIEUSPG
6/5/2019 3:13:18 PM | | Processor: 4 GenuineIntel Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz [Family 6 Model 142 Stepping 9]
6/5/2019 3:13:18 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
6/5/2019 3:13:18 PM | | OS: Microsoft Windows 10: Core x64 Edition, (10.00.18362.00)
6/5/2019 3:13:18 PM | | Memory: 7.88 GB physical, 9.13 GB virtual
6/5/2019 3:13:18 PM | | Disk: 905.26 GB total, 814.17 GB free
ID: 91743 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 14286
Netherlands
Message 91744 - Posted: 6 Jun 2019, 20:07:59 UTC - in response to Message 91743.  

Please open BOINC Manager, then press CTRL+SHIFT+F.
In the window that opens check coproc_debug and click Save.
Now exit BOINC & restart it in your normal way.

When you now check the event log (CTRL+SHIFT+E) it'll have more information about the coprocessor/GPU. Could you post that event log, please?
Please do not private message me for tech support, these will be ignored!
ID: 91744 · Report as offensive
Stick

Send message
Joined: 10 Oct 09
Posts: 27
United States
Message 91745 - Posted: 6 Jun 2019, 20:23:14 UTC - in response to Message 91744.  

6/6/2019 4:15:20 PM | | Starting BOINC client version 7.14.2 for windows_x86_64
6/6/2019 4:15:20 PM | | log flags: file_xfer, sched_ops, task, coproc_debug
6/6/2019 4:15:20 PM | | Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8
6/6/2019 4:15:20 PM | | Data directory: C:\ProgramData\BOINC
6/6/2019 4:15:20 PM | | Running under account HarrisNotebook2
6/6/2019 4:15:20 PM | | [coproc] launching child process at "C:\Program Files\BOINC\boinc.exe"
6/6/2019 4:15:20 PM | | [coproc] with data directory "C:\ProgramData\BOINC"
6/6/2019 4:15:21 PM | | OpenCL CPU: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 7.6.0.1125, device version OpenCL 2.1 (Build 0))
6/6/2019 4:15:21 PM | | [coproc] No NVIDIA library found
6/6/2019 4:15:21 PM | | [coproc] No ATI library found.
6/6/2019 4:15:21 PM | | [coproc] clGetDeviceInfo failed to get device extensions for device 0
6/6/2019 4:15:21 PM | | No usable GPUs found
6/6/2019 4:15:21 PM | | app version refers to missing GPU type intel_gpu
6/6/2019 4:15:21 PM | collatz | Application uses missing intel_gpu GPU
6/6/2019 4:15:21 PM | collatz | Missing coprocessor for task collatz_sieve_91d26a92-7679-4b4c-9bd4-77ed8de7b9d3_0
6/6/2019 4:15:21 PM | | app version refers to missing GPU type intel_gpu
6/6/2019 4:15:21 PM | Einstein@Home | Application uses missing intel_gpu GPU
6/6/2019 4:15:21 PM | | app version refers to missing GPU type intel_gpu
6/6/2019 4:15:21 PM | SETI@home | Application uses missing intel_gpu GPU
6/6/2019 4:15:21 PM | | app version refers to missing GPU type intel_gpu
6/6/2019 4:15:21 PM | SETI@home | Application uses missing intel_gpu GPU
6/6/2019 4:15:21 PM | SETI@home | Missing coprocessor for task 11mr13ag.16322.108298.10.37.103_1
6/6/2019 4:15:21 PM | SETI@home | Missing coprocessor for task 11mr13ag.16311.108298.9.36.106_0
6/6/2019 4:15:21 PM | SETI@home | Missing coprocessor for task blc25_2bit_guppi_58406_22221_HIP20056_0089.29461.409.21.44.122.vlar_0
6/6/2019 4:15:21 PM | SETI@home | Missing coprocessor for task blc25_2bit_guppi_58406_20894_HIP20019_0085.30397.0.22.45.182.vlar_0
6/6/2019 4:15:21 PM | | Host name: LAPTOP-4OIEUSPG
6/6/2019 4:15:21 PM | | Processor: 4 GenuineIntel Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz [Family 6 Model 142 Stepping 9]
6/6/2019 4:15:21 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
6/6/2019 4:15:21 PM | | OS: Microsoft Windows 10: Core x64 Edition, (10.00.18362.00)
6/6/2019 4:15:21 PM | | Memory: 7.88 GB physical, 9.13 GB virtual
6/6/2019 4:15:21 PM | | Disk: 905.26 GB total, 814.52 GB free
6/6/2019 4:15:21 PM | | Local time is UTC -4 hours
6/6/2019 4:15:21 PM | | No WSL found.
6/6/2019 4:15:21 PM | | VirtualBox version: 5.2.30
6/6/2019 4:15:21 PM | collatz | URL https://boinc.thesonntags.com/collatz/; Computer ID 821926; resource share 20
6/6/2019 4:15:21 PM | collatz | Your current settings do not allow tasks from this project. To fix this, you can change Project Preferences on the project's web site.
6/6/2019 4:15:21 PM | Einstein@Home | URL http://einstein.phys.uwm.edu/; Computer ID 12571639; resource share 30
6/6/2019 4:15:21 PM | LHC@home | URL https://lhcathome.cern.ch/lhcathome/; Computer ID 10499236; resource share 30
6/6/2019 4:15:21 PM | Milkyway@Home | URL http://milkyway.cs.rpi.edu/milkyway/; Computer ID 747776; resource share 30
6/6/2019 4:15:21 PM | PrimeGrid | URL http://www.primegrid.com/; Computer ID 946211; resource share 10
6/6/2019 4:15:21 PM | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 8346841; resource share 60
6/6/2019 4:15:26 PM | LHC@home | General prefs: from LHC@home (last modified 25-Sep-2017 18:17:13)
6/6/2019 4:15:26 PM | LHC@home | Host location: none
6/6/2019 4:15:26 PM | LHC@home | General prefs: using your defaults
6/6/2019 4:15:26 PM | | Preferences:
6/6/2019 4:15:26 PM | | max memory usage when active: 4033.36 MB
6/6/2019 4:15:26 PM | | max memory usage when idle: 7260.05 MB
6/6/2019 4:15:26 PM | | max disk usage: 100.00 GB
6/6/2019 4:15:26 PM | | max CPUs used: 3
6/6/2019 4:15:26 PM | | (to change preferences, visit a project web site or select Preferences in the Manager)
6/6/2019 4:15:26 PM | | Setting up project and slot directories
6/6/2019 4:15:26 PM | | Checking active tasks
6/6/2019 4:15:26 PM | | Setting up GUI RPC socket
6/6/2019 4:15:26 PM | | Checking presence of 222 project files
ID: 91745 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 14286
Netherlands
Message 91746 - Posted: 6 Jun 2019, 20:55:01 UTC - in response to Message 91745.  

OK, thanks for that. The error requires me to dig through the source code, which I'll do tomorrow (it's 11pm here).
I'll be back on this.
Please do not private message me for tech support, these will be ignored!
ID: 91746 · Report as offensive
Stick

Send message
Joined: 10 Oct 09
Posts: 27
United States
Message 91747 - Posted: 6 Jun 2019, 21:11:56 UTC - in response to Message 91746.  

Thank you Ageless! No rush and sleep well.
ID: 91747 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 14286
Netherlands
Message 91761 - Posted: 7 Jun 2019, 19:37:40 UTC - in response to Message 91745.  

Okay, so the message means that BOINC cannot read what kind of OpenCL your Intel GPU supports.
It should report e.g.
x86_64 with minimum requirement of SSE 4_2````Compute Device Type: CL_DEVICE_TYPE_GPU``Compute Device Name: Intel(R) Kabylake Mobile Graphics Controller``Compute Device Version: OpenCL 2.1``Compute Device Driver Version: 20.19.15.9999``Compute Device OpenCL C Version: OpenCL C 2.0````Compute Device Type: CL_DEVICE_TYPE_CPU``Compute Device Name: Genuine Intel(R) CPU 0000 @ 2.60GHz``Compute Device Version: OpenCL 2.1 (Build 10245)``Compute Device Driver Version: 5.2.0.10245``Compute Device OpenCL C Version: OpenCL C 2.0
internally to BOINC - it will show part of this information at GPU detection: OpenCL version, driver version.

So definitely something wrong with your drivers.
Best install Display Driver Uninstaller and run it to remove all Intel drivers. Then install a driver, like the newest. Start BOINC, check the event log. No GPU detected? Exit BOINC, run DDU and remove the Intel drivers again (probably reboot). Then install an earlier driver. Start BOINC, check event log, is the GPU detected? Etc.

This may take a while, but it's the best you can do.
Please do not private message me for tech support, these will be ignored!
ID: 91761 · Report as offensive
Stick

Send message
Joined: 10 Oct 09
Posts: 27
United States
Message 91762 - Posted: 7 Jun 2019, 21:12:28 UTC - in response to Message 91761.  

Ageless,

Thank you for the analysis. But I am skeptical that your recommendation will work. Thet is, everything was working fine until I installed the Windows Feature Update. (I don't know if the WFU installed a different driver or left the one which had been working.) But the problem started as soon as the update went into effect. Before I posted here, I had already used DDU and installed the latest Intel driver. And, per your first suggestion, I tried 3 different earlier Intel drivers using DDU each time,

I checked the MS website and saw several problem reports relating to the new feature update (although nothing directly related to display drivers or OpenCL). But there were a few negative comments about it being a sloppy release. Therefore, I am more inclined to revert back to my pre-Windows Feature Update status. If I still have driver issues then, I can troubleshoot them using an OS I have confidence in.

Again, thank you for your help on this! And, I will report back in a day or so when the reversion is complete.\

Stick
ID: 91762 · Report as offensive
Stick

Send message
Joined: 10 Oct 09
Posts: 27
United States
Message 91763 - Posted: 8 Jun 2019, 0:13:41 UTC - in response to Message 91762.  

Well reverting back to Windows v1803 was a lot easier than updating to v1903. Only took about 15 minutes vs. 3+ hours for the update. And, BOINC recognized my GPU immediately. Nothing else needed.

6/7/2019 6:23:52 PM | | Starting BOINC client version 7.14.2 for windows_x86_64
6/7/2019 6:23:52 PM | | log flags: file_xfer, sched_ops, task, coproc_debug
6/7/2019 6:23:52 PM | | Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8
6/7/2019 6:23:52 PM | | Data directory: C:\ProgramData\BOINC
6/7/2019 6:23:52 PM | | Running under account HarrisNotebook2
6/7/2019 6:23:55 PM | | [coproc] launching child process at "C:\Program Files\BOINC\boinc.exe"
6/7/2019 6:23:55 PM | | [coproc] with data directory "C:\ProgramData\BOINC"
6/7/2019 6:24:05 PM | | OpenCL: Intel GPU 0: Intel(R) HD Graphics 620 (driver version 24.20.100.6286, device version OpenCL 2.1 NEO, 3227MB, 3227MB available, 192 GFLOPS peak)
6/7/2019 6:24:05 PM | | OpenCL CPU: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 7.6.0.716, device version OpenCL 2.1 (Build 716))
6/7/2019 6:24:05 PM | | [coproc] No NVIDIA library found
6/7/2019 6:24:05 PM | | [coproc] No ATI library found.
6/7/2019 6:24:06 PM | | Host name: LAPTOP-4OIEUSPG
6/7/2019 6:24:06 PM | | Processor: 4 GenuineIntel Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz [Family 6 Model 142 Stepping 9]
6/7/2019 6:24:06 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
6/7/2019 6:24:06 PM | | OS: Microsoft Windows 10: Core x64 Edition, (10.00.17763.00)
6/7/2019 6:24:06 PM | | Memory: 7.88 GB physical, 9.13 GB virtual
6/7/2019 6:24:06 PM | | Disk: 905.26 GB total, 825.13 GB free
6/7/2019 6:24:06 PM | | Local time is UTC -4 hours
6/7/2019 6:24:06 PM | | No WSL found.
6/7/2019 6:24:06 PM | | VirtualBox version: 5.2.30
6/7/2019 6:24:09 PM | collatz | URL https://boinc.thesonntags.com/collatz/; Computer ID 821926; resource share 20
6/7/2019 6:24:09 PM | Einstein@Home | URL http://einstein.phys.uwm.edu/; Computer ID 12571639; resource share 30
6/7/2019 6:24:09 PM | LHC@home | URL https://lhcathome.cern.ch/lhcathome/; Computer ID 10499236; resource share 30
6/7/2019 6:24:09 PM | Milkyway@Home | URL http://milkyway.cs.rpi.edu/milkyway/; Computer ID 747776; resource share 30
6/7/2019 6:24:09 PM | PrimeGrid | URL http://www.primegrid.com/; Computer ID 946211; resource share 10
6/7/2019 6:24:09 PM | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 8346841; resource share 60
6/7/2019 6:24:14 PM | LHC@home | General prefs: from LHC@home (last modified 25-Sep-2017 18:17:13)
6/7/2019 6:24:14 PM | LHC@home | Host location: none
6/7/2019 6:24:14 PM | LHC@home | General prefs: using your defaults
ID: 91763 · Report as offensive
Stick

Send message
Joined: 10 Oct 09
Posts: 27
United States
Message 91769 - Posted: 8 Jun 2019, 21:01:45 UTC - in response to Message 91763.  
Last modified: 8 Jun 2019, 21:03:07 UTC

Well reverting back to Windows 10, v1809 was a lot easier than updating to v1903. Only took about 15 minutes vs. 3+ hours for the update. And, BOINC recognized my GPU immediately. Nothing else needed.

I did a little more experimenting after the above reversion. That is, I installed the latest Intel driver under Windows 10, v1809 and with that driver in place, BOINC couldn't find a GPU, (This was the same driver that was installed automatically as part of the latest Windows Feature Update - v1903 and caused the same "missing GPU" issue.

After that, I ran DDU again to remove v1903 Intel driver from Windows 10, v1809 and then I ran WU again to restore the v1809 driver. And I noticed that this WU driver download had 2 parts (both from Intel) - a Display part, dated 11/18/18 and an Extension part, dated 1/21/19. This makes me wonder if the problem with v1903 driver is a missing or incompatible Extension. But now that BOiNC is working again, I think I will leave things the way they are and forego more experimenting.
ID: 91769 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 14286
Netherlands
Message 91772 - Posted: 9 Jun 2019, 12:07:15 UTC - in response to Message 91769.  

Rule of thumb is never to use Windows Update for driver updates for GPGPU things. It may be fine for gaming, but general purpose GPU requires additional packages that Microsoft may not provide via Windows Update, because they are open source, because they clash with their own versions of it, or whatever their reason is. So always use the drivers from the GPU manufacturer's page. In this case Intel: https://downloadcenter.intel.com/product/80939/Graphics-Drivers
Please do not private message me for tech support, these will be ignored!
ID: 91772 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 4183
United Kingdom
Message 91833 - Posted: 14 Jun 2019, 9:34:00 UTC - in response to Message 91745.  

6/6/2019 4:15:21 PM | | [coproc] clGetDeviceInfo failed to get device extensions for device 0
Update. We have now established that this error is intrinsic to BOINC, and will occur when the new Intel Windows DCH drivers are installed - whether they are sourced from Microsoft or Intel.

BOINC v7.14.x will always fail to detect an iGPU with these drivers, but v7.16.x should work. It is anticipated that testing of the new client should start either over this weekend, or during the week commencing 17 June 2019.
ID: 91833 · Report as offensive

Message boards : Questions and problems : GPU detection failed, error 0xc0000005

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.