Message boards :
Number crunching :
Aborted by User??
Message board moderation
Author | Message |
---|---|
Bill G Send message Joined: 1 Jun 01 Posts: 1282 Credit: 187,688,550 RAC: 182 |
I seem to be having a bunch of Aborted by User WUs which of course show up as Errors. When I look at the Task Results it seems to say there was an error. Am I doing something wrong as this computer was just having the current Invalids until recentl?. The computer is: http://setiathome.berkeley.edu/show_host_detail.php?hostid=7226971 SETI@home classic workunits 4,019 SETI@home classic CPU time 34,348 hours |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14649 Credit: 200,643,578 RAC: 874 |
The actual error message is Exit status 201 (0xc9) EXIT_MISSING_COPROC Although BOINC thinks you have a GPU, it isn't the right type (CUDA) for the tasks you've been issued. Quite possibly Windows 10 up to its driver updating tricks again (there was a new NVidia driver release this morning - within the last couple of days, anyway). |
AyalaZero Send message Joined: 14 Aug 05 Posts: 21 Credit: 10,910,119 RAC: 0 |
It's likely still due to the Server going down. The new Nvidia driver seems to be working fine for me. I'd wait about a week, see if it goes back to normal. |
William Send message Joined: 14 Feb 13 Posts: 2037 Credit: 17,689,662 RAC: 0 |
I traced that error here. If the problem persists, start from there and my following posts. Else, from Richard's comment I'd say you are looking at an update artifact. [and we need to see if we can get a better error message coded - one that doesn't aggrevate the user] I'm out for the weekend, I hope somebody else can assist further if necessary. A person who won't read has no advantage over one who can't read. (Mark Twain) |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14649 Credit: 200,643,578 RAC: 874 |
It's likely still due to the Server going down. The new Nvidia driver seems to be working fine for me. I'd wait about a week, see if it goes back to normal. Not the server problem. These are new workunits created today, and Bill's wingmates don't have any problems with them. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14649 Credit: 200,643,578 RAC: 874 |
... it isn't the right type (CUDA) for the tasks you've been issued. Correction - they're Astropulse tasks, like in the thread William linked, so it's probably the OpenCL support which has gone AWOL again. Similar troubleshooting process: restart BOINC (heck, why not reboot the computer to be safe), and look at BOINC's startup messages. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14649 Credit: 200,643,578 RAC: 874 |
The most recent AP task which ran detected OpenCL Platform Name: NVIDIA CUDA Name: GeForce GTX 750 Ti Vendor: NVIDIA Corporation Driver version: 358.50 Version: OpenCL 1.2 CUDA That was yesterday morning - task 4498598077 Then there are a bunch supposedly still in progress - are they still displayed in BOINC Manager? If so, what 'Status' is shown? And all AP tasks issued after 04:00 today have failed immediately. I can't see any sign of the host contacting the servers between midnight and 4am (UTC) - that sounds like the sort of timetable for Microsoft to be messing with drivers. |
Bill G Send message Joined: 1 Jun 01 Posts: 1282 Credit: 187,688,550 RAC: 182 |
... it isn't the right type (CUDA) for the tasks you've been issued. I have been off fixing the problem. I noticed that there was no OpenCL for that computer and realized that it had upgraded the OS to a newer release of the Insider Win10. That is actually a reinstall of windows so it changed to drivers and after I reloaded/upgraded the drivers for the NVIDIA card I now have OpenCL again and I am sure the problem is gone. Sorry to have bothered all of you and thanks for your help. Someday I may actually remember what is going on. SETI@home classic workunits 4,019 SETI@home classic CPU time 34,348 hours |
Bill G Send message Joined: 1 Jun 01 Posts: 1282 Credit: 187,688,550 RAC: 182 |
And you were correct about the timing Richard. I forgot that I told this computer to update to the new OS last night when I went to bed and the install must have been going on most of that time and the system was waiting for me to logon this morning, so BOINC does not start running until I log on. I was easily confused this morning as TeamViewer upgraded yesterday and there a few things going on with that as well. (I monitor the computers remotely from my laptop). Again, Thank You SETI@home classic workunits 4,019 SETI@home classic CPU time 34,348 hours |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.