Aborted by user
9 Jan 2015 17:15:38 UTC
Topic 197917
(moderation:
On one of my systems I constantly get wu's, but most of them are marked as 'aborted by user' very quick.
Now, since I'm shure that I did not abord any wu, can someone explain what happens here? Is it due to the server problems, should I set to NNT? It happens on one of my systems only,
http://einsteinathome.org/host/6801076/tasks
Aborted by user
)
They're getting aborted on start, or prior to start, then reported on the next scheduler contact, all within a minute.
Interesting host with a NV, a AMD/ATI and a Intel GPU:
Computer 6801076
Claggy
Check in Boinc's event log if
)
Check in Boinc's event log if there are any hints there and maybe post some of the messages here.
I would also try to reboot the system to see if that helps.
"Exit status 201 (0xc9)" is
)
"Exit status 201 (0xc9)" is
#define EXIT_MISSING_COPROC 201
- the translations into client state outcomes haven't been updated at this project since BOINC clients started using an updated set of exit codes two or three years ago.
If BOINC thinks your GPU has gone walkabout, I suggest you reboot the machine and pay special attention to BOINC's startup messages.
After reboot: 09.01.2015
)
After reboot:
09.01.2015 23:34:55 | | Starting BOINC client version 7.4.36 for windows_x86_64
09.01.2015 23:34:55 | | log flags: file_xfer, sched_ops, task, coproc_debug
09.01.2015 23:34:55 | | Libraries: libcurl/7.39.0 OpenSSL/1.0.1j zlib/1.2.8
09.01.2015 23:34:55 | | Data directory: C:\ProgramData\BOINC
09.01.2015 23:34:55 | | Running under account Alex
09.01.2015 23:34:55 | | [coproc] launching child process at C:\Program Files\BOINC\boinc.exe
09.01.2015 23:34:55 | | [coproc] relative to directory C:\ProgramData\BOINC
09.01.2015 23:34:55 | | [coproc] with data directory "C:\ProgramData\BOINC"
09.01.2015 23:34:55 | | CUDA: NVIDIA GPU 0: GeForce GTX 750 Ti (driver version 347.09, CUDA version 7.0, compute capability 5.0, 2048MB, 1946MB available, 1489 GFLOPS peak)
09.01.2015 23:34:55 | | CAL: ATI GPU 0: AMD Radeon HD 7700 series (Capeverde) (CAL version 1.4.1848, 1024MB, 984MB available, 3520 GFLOPS peak)
09.01.2015 23:34:55 | | OpenCL: NVIDIA GPU 0: GeForce GTX 750 Ti (driver version 347.09, device version OpenCL 1.1 CUDA, 2048MB, 1946MB available, 1489 GFLOPS peak)
09.01.2015 23:34:55 | | OpenCL: AMD/ATI GPU 0: AMD Radeon HD 7700 series (Capeverde) (driver version 1642.5 (VM), device version OpenCL 1.2 AMD-APP (1642.5), 1024MB, 984MB available, 3520 GFLOPS peak)
09.01.2015 23:34:55 | | OpenCL: Intel GPU 0: Intel(R) HD Graphics 4000 (driver version 9.18.10.3257, device version OpenCL 1.2, 1624MB, 1624MB available, 45 GFLOPS peak)
09.01.2015 23:34:55 | | OpenCL CPU: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 1.2, device version OpenCL 1.2 (Build 66956))
09.01.2015 23:34:55 | | OpenCL CPU: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1642.5 (sse2,avx), device version OpenCL 1.2 AMD-APP (1642.5))
09.01.2015 23:34:55 | | NVIDIA library reports 1 GPU
09.01.2015 23:34:55 | | Host name: Data-Assim
09.01.2015 23:34:55 | | Processor: 8 GenuineIntel Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz [Family 6 Model 58 Stepping 9]
09.01.2015 23:34:55 | | 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
09.01.2015 23:34:55 | | OS: Microsoft Windows 7: Ultimate x64 Edition, Service Pack 1, (06.01.7601.00)
09.01.2015 23:34:55 | | Memory: 7.87 GB physical, 15.74 GB virtual
09.01.2015 23:34:55 | | Disk: 292.87 GB total, 196.07 GB free
09.01.2015 23:34:55 | | Local time is UTC +1 hours
09.01.2015 23:34:55 | | VirtualBox version: 4.3.20
09.01.2015 23:34:55 | | Config: use all coprocessors
May need some time to get new work. I'll post the results tomorrow.
@ Claggy:
:)) , I have two of them!
No, they still fail. Will
)
No, they still fail.
Will wait until the system is full up and running again, let's see what happens then.