PrimeGrid
Please visit donation page to help the project cover running costs for this month

Join PrimeGrid

Returning Participants

Community

Leader Boards

Results

Other

drummers-lowrise
1) Message boards : Number crunching : Pierre de Fermat's Birthday Challenge (Message 111782)
Posted 3 hours ago by tng*Project donor
What's clear is that a lot more computing power was online than usual. Some of it was came from our other sub projects, but most did not. People either moved computers from other projects to PrimeGrid, or turned on computers that weren't usually crunching, or payed for some cloud servers for that extra push. And I'm sure some people came here just for the challenge. I suspect many of those are members of the teams at the top of the leader board since those teams organize their challenges.

But I don't have hard numbers.


A cold front allowed me to run more systems.
2) Message boards : Number crunching : Badges II (Message 111694)
Posted 1 day ago by tng*Project donor
3) Message boards : Number crunching : Pierre de Fermat's Birthday Challenge (Message 111686)
Posted 1 day ago by tng*Project donor

Add it all up, and it sounds like these errors happened because the task was started while Windows 10 was doing an automatic driver update. Also, because it only takes a second or two for a task to fail like that, when the driver is in fact updated, a whole bunch of tasks will fail because of it.

It sounds like there's nothing much to worry about here, except, of course, for the possibility of Win 10 updating the driver when you're 99% done on a long GPU task.


Windows 10 updates have been very annoying the last couple of days (lousy timing). I have had multiple systems where updates started, broke the graphics driver, and then didn't complete, resulting in lots of error tasks. These systems ended up with blank screens (maybe a mouse pointer). This persisted after an ACPI shutdown and reboot. A hard power cycle brought them back, updates completed, and the drivers were working.

I'm now checking constantly for problem systems.
4) Message boards : Number crunching : Waiting for wingmen... (Message 111173)
Posted 15 days ago by tng*Project donor
Assuming this was a snap shot and not an updating table, it's cool I'm on it in 4 spots. TNG I think is most with 7? and Scott is at 6.


Right, I got curious about it and took a look. It's a one time thing.


Thanks for sharing the info -- interesting.
5) Message boards : Proth Prime Search : Computation Errors (Message 110217)
Posted 68 days ago by tng*Project donor
Try the usual suspects. Turn off over clocking. Blow the dust out of the computer. Make sure it's not overheating. Reseat the memory.


Bump your fan speeds up if you can.
6) Message boards : Generalized Fermat Prime Search : 919444^1048576+1 is prime! (Message 109996)
Posted 75 days ago by tng*Project donor
Now we should all flip over to GFN-21 and see what happens.


There's still GFN-21 manual sieving work available.
7) Message boards : Sophie Germain Prime Search : 4888 (Message 108493)
Posted 163 days ago by tng*Project donor
I feel like a last 5k pool should be formed here. I bid July 19.

July 31
8) Message boards : Number crunching : Badges - Full Sets! (Message 108427)
Posted 165 days ago by tng*Project donor
brings all active subprojects back to sapphire or better.
9) Message boards : Number crunching : Badges II (Message 108426)
Posted 165 days ago by tng*Project donor
10) Message boards : Number crunching : LLR 3.8.20 Going Live! (Message 108026)
Posted 184 days ago by tng*Project donor
You will need to:

1) Totally exit BOINCMgr (not just minimize!)
2) Create a {BOINCDataFolder}\projects\www.primegrid.com\app_config.xml, copy/paste this into it, and then ReplaceAll "NumProcs" with whatever value you want it to be. If you decide to give different NumProcs to different apps, then make sure to realize that each app occurs twice in this file, and to make sure each pair is consistent with each other.
3) Restart BOINCMgr


BOINC restart is not needed when you create or modify app_config.xml. It is enough to do this:
- create/update app_config.xml: file;
- disable option "Leave non-GPU tasks in memory while suspended" (Options/Computing preferences/Disk and memory tab);
- suspend all PrimeGrid tasks (or easier suspend CPU usage);
- reload config files (Options/Read config files);
- resume tasks.

Note: after doing this GUI still will display previous CPU count for apps. This is display bug only, number of running tasks and their command line will be adjusted properly.


After resuming tasks, you may need to force an update on the primegrid project to download more tasks if you are decreasing the number of CPUs for a subproject.


Next 10 posts
[Return to PrimeGrid main page]
Copyright © 2005 - 2017 Rytis Slatkevičius (contact) and PrimeGrid community. Server load 3.73, 3.54, 3.35
Generated 20 Nov 2017 | 19:30:56 UTC