Posts by Stick

1) Message boards : Projects : News on Project Outages (Message 113024)
Posted 1 Nov 2023 by Stick
Post:
Apparently, Milkyway@Home has been offline for a few hours now. Getting messages like 11/1/2023 5:04:08 PM | | Project communication failed: attempting access to reference site.
2) Message boards : Projects : News on Project Outages (Message 106096)
Posted 14 Nov 2021 by Stick
Post:
Looks like Collatz is back up now.
3) Message boards : Projects : News on Project Outages (Message 106086)
Posted 14 Nov 2021 by Stick
Post:
Apparently, the Collatz website has been down for a while.
4) Message boards : Projects : News on Project Outages (Message 104397)
Posted 17 May 2021 by Stick
Post:
Collatz is back online now/
5) Message boards : Projects : News on Project Outages (Message 104393)
Posted 16 May 2021 by Stick
Post:
Collatz appears to be down - website not coming up, BOINC can't upload or download.
6) Message boards : Questions and problems : GPU detection failed, error 0xc0000005 (Message 91769)
Posted 8 Jun 2019 by Stick
Post:
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.
7) Message boards : Questions and problems : GPU detection failed, error 0xc0000005 (Message 91763)
Posted 8 Jun 2019 by Stick
Post:
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
8) Message boards : Questions and problems : GPU detection failed, error 0xc0000005 (Message 91762)
Posted 7 Jun 2019 by Stick
Post:
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
9) Message boards : Questions and problems : GPU detection failed, error 0xc0000005 (Message 91747)
Posted 6 Jun 2019 by Stick
Post:
Thank you Ageless! No rush and sleep well.
10) Message boards : Questions and problems : GPU detection failed, error 0xc0000005 (Message 91745)
Posted 6 Jun 2019 by Stick
Post:
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
11) Message boards : Questions and problems : GPU detection failed, error 0xc0000005 (Message 91743)
Posted 6 Jun 2019 by Stick
Post:
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
12) Message boards : Questions and problems : GPU detection failed, error 0xc0000005 (Message 91715)
Posted 5 Jun 2019 by Stick
Post:
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.
13) Message boards : BOINC Manager : What's new in 7.8.0?? (Message 79774)
Posted 25 Jul 2017 by Stick
Post:
I've just heard that there was an operational oopsie behind the scenes at LHC - a mistake cancelled a number of active tasks.

It happens. But I think BOINC is definitely off the hook for this one.

I agree. My thought, when I first posted, was that 7.8.0 had somehow been complicit in the LHC server and my client getting out of sync. But it definitely looks like LHC deserves all the blame and 7.8.0 is off the hook.

EDIT: "It happens." - a quote from one of the great minds of our era - Forrest Gump
14) Message boards : BOINC Manager : What's new in 7.8.0?? (Message 79745)
Posted 23 Jul 2017 by Stick
Post:
Richard,
Thank you for the quick reply. LHC has been struggling with some bigger problems lately - so my report turning out to be an LHC problem, too, is not a surprise. I just wanted to make sure BOINC was aware of it. But - Toby's reply seems to put my 7.8.0 concerns to bed.
Stick
15) Message boards : BOINC Manager : What's new in 7.8.0?? (Message 79743)
Posted 23 Jul 2017 by Stick
Post:
I recently updated to 7.8.0 and had a minor issue on LHC with tasks not listed on the LHC web-site and then aborted by project. Here is the link to the message I posted on the LHC message boards: Tasks aborted by project and BOINC 7.8.0

If this is the wrong thread to post this on, please move to wherever is appropriate.
16) Message boards : Questions and problems : Possible compatibility issue between VB 4.3.12 and Windows 10 (Message 65559)
Posted 23 Nov 2015 by Stick
Post:
FYI: I recently posted a couple of messages on the vLHC Communication with VM Hypervisor Failed forum which describe some problems I encountered using the standard BOINC download of BOINC 7.6.9, VirtualBox 4.3.12 for Windows 64-bit on my Windows 10 laptop. The problems went away when I updated to VirtualBox 5.0.10.
17) Message boards : Projects : News on Project Outages (Message 59903)
Posted 21 Jan 2015 by Stick
Post:
Stick -- note, it is not a 'they' Slicker is a one man shop there.

Thanks! I imagine he is a very busy man right now.

I've been a Collatz member for several years now and until recently it has run like clockwork. Hope he can figure things out!
18) Message boards : Projects : News on Project Outages (Message 59896)
Posted 21 Jan 2015 by Stick
Post:
Collatz was up for a short time last night but is down again. There was a very short note about the problem on the home page which I will try to paraphrase here. Unfortunately, I did not read it as carefully as I now wish.

Basically, it has been a recurring problem with DB indexing that is somehow related to the nightly back-up process. They rebuild the indexes and attempt to replicate the problem, but haven't been able to. Then the problem comes back later and crashes the server again. In other words, they are still scratching their heads.
19) Message boards : Projects : News on Project Outages (Message 59685)
Posted 16 Jan 2015 by Stick
Post:
Collatz is back!


Looks like it's down again.
20) Message boards : Questions and problems : Unintentional "Return Results Immediately" (Message 39786)
Posted 22 Aug 2011 by Stick
Post:
I just had a MW unit fail to validate after reporting 2 seconds after finishing (and NNT was not set).

Event log:
8/21/2011 9:04:24 PM | Milkyway@home | Computation for task ps_separation_82_2s_mix0_1_1170906_0 finished
8/21/2011 9:04:24 PM | Test4Theory@Home | Resuming task uc_1313873249_238_0 using cernvm version 603
8/21/2011 9:04:26 PM | Milkyway@home | Sending scheduler request: To fetch work.
8/21/2011 9:04:26 PM | Milkyway@home | Reporting 1 completed tasks, requesting new tasks for CPU
8/21/2011 9:04:28 PM | Milkyway@home | Scheduler request completed: got 1 new tasks


Error text:
<core_client_version>6.12.33</core_client_version>
<![CDATA[
<stderr_txt>
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4'
Error reading astronomy parameters from file 'astronomy_parameters.txt'
Trying old parameters file
Using SSE3 path

</stderr_txt>
]]>


Next 20

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.