Thread 'GPU detection failed, error 0xc0000005'
Message boards : Questions and problems : GPU detection failed, error 0xc0000005
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 8 May 19 Posts: 2 
|
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 ·  |
|
Send message Joined: 5 Oct 06 Posts: 5131 
|
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_VIOLATIONWith 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 · |
|
Send message Joined: 8 May 19 Posts: 2
|
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 · |
|
Send message Joined: 8 Jun 09 Posts: 3 
|
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 · |
|
Send message Joined: 10 Oct 09 Posts: 34 
|
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 · |
 Jord Send message Joined: 29 Aug 05 Posts: 15573 
|
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. ID: 91716 · |
|
Send message Joined: 10 Oct 09 Posts: 34
|
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 ID: 91743 · |
|
Jord Send message Joined: 29 Aug 05 Posts: 15573
|
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? ID: 91744 · |
|
Send message Joined: 10 Oct 09 Posts: 34
|
6/6/2019 4:15:20 PM | | Starting BOINC client version 7.14.2 for windows_x86_64 ID: 91745 · |
|
Jord Send message Joined: 29 Aug 05 Posts: 15573
|
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. ID: 91746 · |
|
Send message Joined: 10 Oct 09 Posts: 34
|
Thank you Ageless! No rush and sleep well. ID: 91747 · |
|
Jord Send message Joined: 29 Aug 05 Posts: 15573
|
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.0internally 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. ID: 91761 · |
|
Send message Joined: 10 Oct 09 Posts: 34
|
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 · |
|
Send message Joined: 10 Oct 09 Posts: 34
|
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 ID: 91763 · |
|
Send message Joined: 10 Oct 09 Posts: 34
|
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 · |
|
Jord Send message Joined: 29 Aug 05 Posts: 15573
|
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 ID: 91772 · |
|
Send message Joined: 5 Oct 06 Posts: 5131
|
6/6/2019 4:15:21 PM | | [coproc] clGetDeviceInfo failed to get device extensions for device 0Update. 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 · |
Copyright © 2024 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.