1) Message boards : Number crunching : I'm not being given any new work? (Message 1963923) Posted 8 Nov 2018 by Karsten Vinding Post: Thanks for the answers. I have reduced the cache. I'll let it run for some time, and see if job gets downloaded at one point. I already use Boinctasks, and have done so for many years. I find it better than boinc manager in many ways, and it lets me monitor more computers easily. Edit: I just found the error: A few days ago I changed the app that I crunch Setiv8 with to an optimized version for my Ryzen CPU. The app was mentioned in another thread. In editing app_info.xml I accidentally put in a extra pair of <app_info> </app_info> around the newly edited field, with the file names for the new app. This of course confused boinc (it didn't show any errors though), and made it think that the file ended after the first </app_info>, after which all my GPU setiv8 apps where. I removed these extra lines, restarted boinc, and work was sent to my PC immediatly. Previously the servers saw that I didn't have valid programs for my request and acted accordingly. I was basically only asking for AP work for my GPU, and that is hard to come by. This was all my own fault, but it was a very hard error to find...

2) Message boards : Number crunching : I'm not being given any new work? (Message 1963894) Posted 8 Nov 2018 by Karsten Vinding Post: Thanks for all the suggestions. I'll try to reduce my cache size. I still think the problem is elsewhere though. My computer clearly asks the seti server for work, but gets the reply that no work is available. Which is untrue, as there are several 100 thousands of WU's available. 21:36:44 | SETI@home | Requesting new tasks for AMD/ATI GPU 21:36:44 | SETI@home | [sched_op] AMD/ATI GPU work request: 346244.03 seconds; 1.00 devices 21:36:46 | SETI@home | No tasks are available for SETI@home v8 The servers dont repond that I have reached some limit (e.g. the 100 tasks limit), just that no work is avaiable for setiathome v8. The servers dont know the internal debit of my boinc client. It simply responds to the request from my client. If my client asks for 50.000 seconds of work, the server tries to answer that request based upon previous numbers for crunch time and of course given the 100WU restriction and availability of work. For some reason that doesn't work. I would like to know the reason why.

3) Message boards : Number crunching : I'm not being given any new work? (Message 1963806) Posted 7 Nov 2018 by Karsten Vinding Post: As my settings are right now I have Seti at 160 resource share. Other projects are at 1 or 2 in resource share. They are basically only backups. But do occasionally run a few wu's. My cache is set at 0.75 / 2.25. The other projects are getting work. Right now its mostly Collats, as its the only backup project I have allowed to use the GPU. At the moment I have 5 backup projects, adding up to 8 in resource share (3 at 2 and 2 at 1). So about 1/20 of the resource share. Collats has a 2 points resource share, so 1/80 of the GPU resource share. Shouldnt prevent Seti from getting work for a whole week. My number are actually carefully selected, to get the resource shares I want. When I check the scheduling priority for Seti vs Collats i get this. Seti: Scheduling priority -0.78 Collats: Scheduling priority -235.23 If I understand these numbers, Seti has much higher priority right now. I have been running BOINC for many many years, and understand the inner workings of the scheduler to some extend. Something is wrong that is preventing my host from picking up work. The work is being requested from the server, just not handed out. I'm of to bed, will see when I have the time to look into this again. Work is being done afterall, so its no disaster.

4) Message boards : Number crunching : I'm not being given any new work? (Message 1963796) Posted 7 Nov 2018 by Karsten Vinding Post: Nonono. That line was from another project, and I only added it as an example of what was shown when boinc does not ask for work. Here it is in its completenes. yoyo@home 11/7/2018 09:45:27 PM Not requesting tasks: don't need (CPU: job cache full; AMD/ATI GPU: not highest priority project) Seti looks like this: SETI@home 11/7/2018 09:44:58 PM Requesting new tasks for AMD/ATI GPU My PC is requesting tasks! Just not given any!

5) Message boards : Number crunching : I'm not being given any new work? (Message 1963790) Posted 7 Nov 2018 by Karsten Vinding Post: Thanks for your reply :) I'm definetely asking for work. When I'm not, my Boinc shows something like this: 11/7/2018 20:52:30 | Not requesting tasks: don't need (CPU: job cache full; AMD/ATI GPU: not highest priority project) Even if I manually set all my other projects to no new work, and update, I dont get work. I'm not a newbie at Boinc, have been with the project since day one. Boinc sees the GPU: 07-11-2018 21:32:30 | | OpenCL: AMD/ATI GPU 0: Radeon (TM) RX 480 Graphics (driver version 2686.5, device version OpenCL 2.0 AMD-APP (2686.5), 8192MB, 8192MB available, 6244 GFLOPS peak) And it also gets used for other projects. I have added the sced_op_debug, and restarted boinc. Then tried refeshing Seti. 07-11-2018 21:36:44 | SETI@home | Requesting new tasks for AMD/ATI GPU 07-11-2018 21:36:44 | SETI@home | [sched_op] CPU work request: 0.00 seconds; 0.00 devices 07-11-2018 21:36:44 | SETI@home | [sched_op] AMD/ATI GPU work request: 346244.03 seconds; 1.00 devices 07-11-2018 21:36:46 | SETI@home | Scheduler request completed: got 0 new tasks 07-11-2018 21:36:46 | SETI@home | [sched_op] Server version 709 07-11-2018 21:36:46 | SETI@home | No tasks sent 07-11-2018 21:36:46 | SETI@home | No tasks are available for AstroPulse v7 07-11-2018 21:36:46 | SETI@home | No tasks are available for SETI@home v8 07-11-2018 21:36:46 | SETI@home | Project requested delay of 303 seconds Its quite obvious that I'm asking for work, quite a lot of it (over 96 hours anyway). Why am I not given any? I find it curious that the server says no tasks available.... I think I'll try backing up my app_info.xml, and aplication files, and then reset the seti project. Then I'll see if it helps?

6) Message boards : Number crunching : I'm not being given any new work? (Message 1963765) Posted 7 Nov 2018 by Karsten Vinding Post: After watching this for about a week, I have to ask. Is anybody else having problems getting work? Is see this in BOINC messages: SETI@home 11/7/2018 7:10:10 PM update requested by user SETI@home 11/7/2018 7:10:10 PM Sending scheduler request: Requested by user. SETI@home 11/7/2018 7:10:10 PM Requesting new tasks for AMD/ATI GPU SETI@home 11/7/2018 7:10:13 PM Scheduler request completed: got 0 new tasks SETI@home 11/7/2018 7:10:13 PM No tasks sent SETI@home 11/7/2018 7:10:13 PM No tasks are available for AstroPulse v7 SETI@home 11/7/2018 7:10:13 PM No tasks are available for SETI@home v8 According to the server stats there is plenty of work, and noone else seems to be having problems getting work. I havent returned any bad results lately. I really cant figure out why I'm not getting work. Its only for the GPU that no work is fetched, the CPU got 100 task some 5 days ago. http://setiathome.berkeley.edu/results.php?hostid=862199

7) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1935221) Posted 11 May 2018 by Karsten Vinding Post: Well, then it seems that I, almost by chance, have found a good tool for the job. It does work well, its nice to have a tool that this reliably finds errors relatively fast. It does make experimenting and troubleshooting much easier.

8) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1935064) Posted 11 May 2018 by Karsten Vinding Post: I have been experimenting a little with Ryzen DRAM Calculator, and its so called "safe" settings. I made settings for 3533, 3400, and 3200, all with the safe calculations. 3533 didn't boot. And I honestly didn't expect it to. 3400 did boot, but windows crashed loading the desktop. Tried 3333 with the 3400 settings, and it booted and started correctly. Running RAM tester gave me an error within 1 minute. 3200 with safe settings, booted fine, but RAM tester threw an error after about 30 seconds. 3200 with bios defaults, but with 48 ohm ProcODT, runs fine. Default settings are a lot more relaxed, as far as I can see. So, I guess I'll stick to 3200 at (almost) default for now, which was really also what I was hoping for. My only problem with this is that the system should be able to run at the safe settings (at least at 3200), as they make sure that the specs of the actual ram is maintained. So the bios / agesa is not doing what it should.

9) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1935026) Posted 11 May 2018 by Karsten Vinding Post: I was reading some articles about finding a good memtester that would run in Windows. Finding that memtest64, wouldnt find errors, even with settings that eventually crashed, I tried to read up on it. I found a guy promoting "RAM test" (by Karhu software). A program that it seems is basically made for testing RAM on Ryzen CPU's (will work on others too) The downside was, it costs 10$ (9.99). After some time thinking about it, I decided to try it, and bought a license. Its not that much money anyway. And it has proven to be a good decision. I can run the program at 3200 for an hour (and more) without errors, but at 3266 I get an error from the program within 20 seconds (at a setting where the system could run 12+ hours yesterday). You can set the program to stop on errors or keep running. And you can set it to beep on eroors. It has helped me very much in finding reliable settings. I found that setting back GDM to auto did nothing, the system is still stable (perhaps its on pr. default at 3200), but the ProcODT has to be set at 48 ohm on my system, higher than that I get memory errors. I like the simplicity of it, and I like how fast it detects errors, at least on my system, when I push things too much.

10) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1934818) Posted 10 May 2018 by Karsten Vinding Post: Thanks for your comments. I will see if Gear Down Mode (GDM) could perhaps make my RAM stable at higher speed, but I'll have to measure real world performance to see whats fastest (3200 vs. eg 3400 w. GDM). 48 Ohms have helped me in the past, so that'll have to be tried out as well, allthough that would purely be for reliability. The system crashed at 3266 after many hours, so now I'm trying 3200, still with standard settings for now.

11) Message boards : Number crunching : Welcome to the 19 Year Club! (Message 1934700) Posted 9 May 2018 by Karsten Vinding Post: I will be joining the club in 9 days :) In fact it would have been before that. I created a Seti account in April 99, but somehow registered with a nonexistant mail adress. And back then I couldn't find a way to change it (I don't hink it was possible). So I created a new account, which I'm using to this date. Next year will be an aniversary. I wonder if the peoble behind the project will do something to celebrate it?

12) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1934690) Posted 9 May 2018 by Karsten Vinding Post: Yes, there are many many variables, and I just don't understand the technology well enough to do educated adjustments. I'll take the standard timings, and push the frequency as high as it will go, and leave it at that (for now). 3333 crashed after about 45 minutes. But 3266 does seem more stable. Its at about 1h45 mins now, so improved, but not definitively reliable yet. Time will tell. But 4011 is definately an improvement on my system. With 4009 I never reached 10 minutes without crashes at 3200.

13) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1934670) Posted 9 May 2018 by Karsten Vinding Post: The system was not stable at 3400. Had a blue screen after some time. Was also almost too good to be true :) Now I'm at 3333, lets see how that works. The fact that its able to boot at these settings is something new to my setup :)

14) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1934622) Posted 9 May 2018 by Karsten Vinding Post: Just an update. Yesterday I updated to the newly released 4011 bios for my board. There have been varying reports of succes, but on my system, with my G-Skill FlareX, that are rated to 3200Mhz, I seem to have gained complete stability at 3200Mhz. At least it ran for nearly 24h without crashing. Now I have even been able to boot and run at 3400Mhz, which I decided to try due to reports from another user with the same RAM. I have never been able to even boot at that speed before. Even at 3400, the system seems stable. I'll have to run it for some days before I can say for sure if its reliable, but it does seem the 4011 bios is an improvement over 4009.

15) Message boards : Number crunching : Back into the party! (Message 1933651) Posted 4 May 2018 by Karsten Vinding Post: I used to run it passively cooled with a heatsink on the CPU. Today I have a 120mm fan at low rpm pushing air across the heatsink. One of my Pi's (3B+) is in a closed case used as a media player for my TV. That one is passively cooled with a heatsink, and only runs two Wu's at one time.

16) Message boards : Number crunching : Back into the party! (Message 1933495) Posted 4 May 2018 by Karsten Vinding Post: My Pi 3B does the seti WU's in 10-16 hours or so. At least the ones that I can see right now have been in that time frame. Not a speed demon, but its a cheap low power device. I only run 3 WU's a time to keep temperatures down, it does get pretty hot. Make sure you've got sufficient cooling.

17) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1930981) Posted 20 Apr 2018 by Karsten Vinding Post: Yess the Zen+ is doing nice up until 4Ghz (plus a litlle more), but clearly still hits a frequency wall at higher frequencies. Voltage requirements for higher clocks then seem to go upwards quickly. Still this CPU will probably do up towards 4GHz with all cores loaded, if the cooling is sufficient, when set to automatic. I would also think about a good X370 board, they are probably going to be cheap now.

18) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1930939) Posted 19 Apr 2018 by Karsten Vinding Post: Well it seems our experiences match. I am actually considering the 2700X, perhaps even a new build with it. I agree that its a small evolution of the original Ryzens, but the Precision boost 2 technology does seem to work much better than Pb1. Perhaps to a point where I would leave the CPU at stock, and leave clocks up to its internal management. I don't have the money for the change right now, so It'll have to wait, and that wont be a problem. With some luck the prices will go down before I purchase, if I decide to do so.

19) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1930925) Posted 19 Apr 2018 by Karsten Vinding Post: Well, that test didn't last long. I installed the BIOS, went into BIOS, and set the same settings as before, with the exception of letting the RAM run at its specified 3200MHz. Booted windows and started using it. The computer crashed with a blue screen within 10 minutes.... I have rebooted now, with 3133MHz RAM, where it was stable on the 3805 Bios. I hope it still is.....

20) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1930919) Posted 19 Apr 2018 by Karsten Vinding Post: Have you tried the latest 4009 BIOS'es, or read anything about them? I'm downloading at the moment, will report if I see improvements.

Next 20

 
©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.