Message boards :
Number crunching :
Aborted by User, but not
Message board moderation
Author | Message |
---|---|
Send message Joined: 26 May 11 Posts: 32 Credit: 45,604,212 RAC: 2,314 ![]() ![]() |
FYI, I am getting "aborted by user" errors the last few days computer #410714 with 2 GTX 570's, These historically have done a lot of work for the site, .... If anyone has any feedback, please advise. I have searched the message boards for this error, and nothing turned up... Other sites, Seti, GPUGrid... crunching well and have no issues... |
Send message Joined: 4 Sep 12 Posts: 219 Credit: 456,474 RAC: 0 ![]() ![]() |
If you probe a little deeper, you can see better diagnostic information. Your most recent example was task 1342970392. That says additionally: Client state Aborted by user BOINC is failing to see your GPU properly. Your computer 410714 is running Windows 10, which hasn't really stabilised yet. In particular, Windows 10 has a habit of updating your hardware drivers whether you want it to or not: and the drivers Microsoft supplies may not always include the ecosystems (like OpenCL runtime support) that scientific computing requires. I suggest your first step might be to replace the current drivers for your NVIDIA GeForce GTX 570 with certified drivers downloaded directly from http://nvidia.com |
Send message Joined: 26 May 11 Posts: 32 Credit: 45,604,212 RAC: 2,314 ![]() ![]() |
Current Status, still need help... Navida driver was and is current ver 358.91 dated 9 NOV 2015. System was rebooted. Boinc runs the GPUs successfully on SETI, POEM, Asteroids, and GPUGrid. All other system drivers were checked for current and found to be so by a non windows driver update program. I have unattached and reattachecd to Milkyway. And I just allowed Milkyway to get new tasks, and they still error out with the 201 (0xc9) EXIT_MISSING_COPROC This computer was running Milkyway successfully a number of days ago... The only major changes was to eliminate and reinstall Microsoft SQL 2012, which I am still having issues with on the reinstall. Why this would effect only Milkyway??? So, I am ready for new ideas to try. |
Send message Joined: 7 Sep 09 Posts: 5 Credit: 104,244,527 RAC: 4,642 ![]() ![]() ![]() |
Yeah mine is doing the same thing that you have described. Driver's the same and everything. Need some kind of resolve. |
Send message Joined: 4 Sep 12 Posts: 219 Credit: 456,474 RAC: 0 ![]() ![]() |
Nvidia driver was and is current ver 358.91 dated 9 NOV 2015. Where did you download/install that from? Microsoft or NVidia? |
Send message Joined: 26 May 11 Posts: 32 Credit: 45,604,212 RAC: 2,314 ![]() ![]() |
Nvidia, I always use Nvidia GeForce Experience icon (prior to that direct from the Nvidia web site. I never let windows update the Nvidia drivers. And the GeForce Experience alerts me when new updates are available, which is ahead of the windows updates! |
Send message Joined: 26 May 11 Posts: 32 Credit: 45,604,212 RAC: 2,314 ![]() ![]() |
And I just downloaded and reinstalled the current driver. Allowed new tasks from Milkyway, and they continued to bomb. I then released GPU tasks for Seti and Asteroid's and both are crunching normally. |
![]() ![]() Send message Joined: 8 May 09 Posts: 3339 Credit: 524,010,781 RAC: 0 ![]() ![]() ![]() |
And I just downloaded and reinstalled the current driver. Allowed new tasks from Milkyway, and they continued to bomb. I then released GPU tasks for Seti and Asteroid's and both are crunching normally. Maybe MW isn't ready for the newest driver yet? MW is planning on upgrading the Server side of their software soon, it is more than one generation old, maybe that will fix it. |
Send message Joined: 26 May 11 Posts: 32 Credit: 45,604,212 RAC: 2,314 ![]() ![]() |
Just did a cold boot, and tried again, and it is working. Did not do anything else to the system... go figure. So, end of issue as I know it... |
Send message Joined: 7 Sep 09 Posts: 5 Credit: 104,244,527 RAC: 4,642 ![]() ![]() ![]() |
Mine is still doing it |
Send message Joined: 7 Sep 09 Posts: 5 Credit: 104,244,527 RAC: 4,642 ![]() ![]() ![]() |
11/17/2015 6:15:27 PM | | CUDA: NVIDIA GPU 0: GeForce GTX 980 Ti (driver version 358.91, CUDA version 7.5, compute capability 5.2, 4096MB, 4025MB available, 6916 GFLOPS peak) 11/17/2015 6:15:27 PM | | App version needs OpenCL but GPU doesn't support it 11/17/2015 6:15:27 PM | Milkyway@Home | Application uses missing NVIDIA GPU 11/17/2015 6:15:27 PM | | App version needs OpenCL but GPU doesn't support it 11/17/2015 6:15:27 PM | Milkyway@Home | Application uses missing NVIDIA GPU 11/17/2015 6:15:27 PM | | App version needs OpenCL but GPU doesn't support it 11/17/2015 6:15:27 PM | | Processor: 12 GenuineIntel Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz [Family 6 Model 63 Stepping 2] 11/17/2015 6:15:27 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 dca pbe fsgsbase bmi1 smep bmi2 11/17/2015 6:15:27 PM | | OS: Microsoft Windows 10: Core x64 Edition, (10.00.10586.00) 11/17/2015 6:15:27 PM | | Memory: 15.90 GB physical, 18.28 GB virtual 11/17/2015 6:20:17 PM | | App version needs OpenCL but GPU doesn't support it 11/17/2015 6:20:17 PM | | App version needs OpenCL but GPU doesn't support it 11/17/2015 6:20:17 PM | Milkyway@Home | [error] App version uses non-existent NVIDIA GPU 11/17/2015 6:20:17 PM | Milkyway@Home | [error] App version uses non-existent NVIDIA GPU 11/17/2015 6:20:17 PM | Milkyway@Home | [error] Missing coprocessor for task de_modfit_fast_15_3s_136_noconst_sim1Aug1_3_1446686708_6009162_0; aborting 11/17/2015 6:20:17 PM | Milkyway@Home | [error] Missing coprocessor for task de_80_DR8_Rev_8_5_00004_1446686708_6773763_3; aborting 11/17/2015 6:20:17 PM | Milkyway@Home | [error] Missing coprocessor for task de_modfit_fast_15_3s_136_noconst_sim1Aug1_3_1446686708_6009167_0; aborting 11/17/2015 6:20:17 PM | Milkyway@Home | [error] Missing coprocessor for task de_80_DR8_Rev_8_5_00004_1446686708_6771036_2; aborting 11/17/2015 6:20:17 PM | Milkyway@Home | [error] Missing coprocessor for task de_modfit_fast_15_3s_136_noconst_sim1Aug1_3_1446686708_6009166_0; aborting 11/17/2015 6:20:17 PM | Milkyway@Home | [error] Missing coprocessor for task de_80_DR8_Rev_8_5_00004_1446686708_6769467_3; aborting 11/17/2015 6:20:17 PM | Milkyway@Home | [error] Missing coprocessor for task de_modfit_fast_15_3s_136_noconst_sim1Aug1_3_1446686708_6009165_0; aborting 11/17/2015 6:20:17 PM | Milkyway@Home | [error] Missing coprocessor for task de_80_DR8_Rev_8_5_00004_1446686708_6757959_1; aborting 11/17/2015 6:20:17 PM | Milkyway@Home | [error] Missing coprocessor for task de_modfit_fast_15_3s_136_noconst_sim1Aug1_3_1446686708_6009164_0; aborting 11/17/2015 6:20:17 PM | Milkyway@Home | [error] Missing coprocessor for task de_80_DR8_Rev_8_5_00004_1446686708_6694374_4; aborting 11/17/2015 6:20:17 PM | Milkyway@Home | [error] Missing coprocessor for task de_modfit_fast_15_3s_136_noconst_sim1Aug1_3_1446686708_6009163_0; aborting 11/17/2015 6:20:17 PM | Milkyway@Home | [error] Missing coprocessor for task de_80_DR8_Rev_8_5_00004_1446686708_6691878_3; aborting 11/17/2015 6:20:17 PM | Milkyway@Home | [error] Missing coprocessor for task de_modfit_fast_15_3s_136_noconst_sim1Aug1_4_1446686708_6009168_0; aborting |
Send message Joined: 18 Jan 15 Posts: 23 Credit: 150,312,324 RAC: 0 ![]() ![]() |
I am having the same issue with mine system. It started doing it right after the last Big update from Microsoft for windows 10. As soon as the download was complete and reinstalled the whole operating system that's when I started getting the same error messages and I have all the latest drivers from NVidia thru the manager. This really sucks. |
Send message Joined: 18 Jan 15 Posts: 23 Credit: 150,312,324 RAC: 0 ![]() ![]() |
It has been confirmed with the help of other users on GPU message board and the test I did this morning that uninstalling all Nvidia drivers "and" Geforce experience manager (which I probably didn't have to do but I did it anyway) and then reinstalling them back again should solve the problem with Boinc Manager not seeing the GPU or the message (GPU missing) for whatever project your running. Me personally I was using windows 10 and Microsofts last big update installed there best video driver instead of leaving the ones from nivida (latest ones) which Boinc manager didn't like. Either way I have my GPU running again on Boinc Manager correctly. Hope this helps. Rich. |
Send message Joined: 7 Sep 09 Posts: 5 Credit: 104,244,527 RAC: 4,642 ![]() ![]() ![]() |
Yes, that did it. Dumped all the drivers etc. and reinstalled fresh ones. Everything is working OK for now. Just have to wait and see. |
![]() ![]() Send message Joined: 13 Dec 12 Posts: 101 Credit: 1,782,758,310 RAC: 0 ![]() ![]() ![]() |
Quick question please guys/girls..... If I only want to run GPU tasks and not the larger CPU tasks, which preferences do I switch off in my M@H settings? I'm unsure between MilkyWay@Home MilkyWay@Home N-Body Simulation Milkyway@Home Separation Milkyway@Home Separation (Modified Fit) Thank you |
Send message Joined: 4 Sep 12 Posts: 219 Credit: 456,474 RAC: 0 ![]() ![]() |
Use CPU Enforced by version 6.10+ no |
©2025 Astroinformatics Group