The problem is real simple... I have processing and GRU processing suspended, yet jobs are starting and running. All the jobs flipped to 'suspended -user requrest'. about 30min later my machine started lagging and I noticed that jobs were running. just a couple at first, then slowly more started. BOIND Mgr is acting like my preference don't exist.

Version is 7.24.1
Win 11
Project: Doesn't matter. I've had NFS, Asteroids, Cosmology, MilkyWay, and Einstein all run the past 4 hours.

If you are using the BOINC Manager task bar icon menu, the suspend menu feature is only for 60 minutes. You need to suspend projects or individual tasks via the BOINC Manager program proper through the Projects or Tasks tabs and left panels.

I'm using the menu option 'Activity' to suspend. Didn't realize it was a 60 min timer.

I'm using the menu option 'Activity' to suspend. Didn't realize it was a 60 min timer.

That is odd. I have always found using suspend from the activity menu to suspend till I change it back again. What happens if you go to the projects tab and then suspend all projects from there?

Same problem here. One machine on which Boinc is running does not obey the suspend command in local preferences. Suspend from ------ to ------.
For another machine, I have requested ten days of work. Instead, I get one task at a time.

Which project?

---

BOINC (for Android) 8.0.0

Which project?

Einstein.
What I do not understand is that it was running perfectly before. I have the latest version on two laptops. On one this suspension problem has cropped up.
Is there some malware? The Einstein problem has been solved.
















-

Here, too, I have a problem with suspending the task, but in the opposite sense.
Client running, data processing in progress (Boinc client uses CPU) However after 3...5 or sometimes 14 minutes Boinc client cpu usage stops and won't restart. (only by restarting the client) Einstein and Milkyway are running, both projects do the same thing. Meanwhile, there are no disk or network operations and client status is always "Running".
The "Suspend if there is no mouse or keyboard in the last XX minutes" function has no effect on this.
This is annoying because the client runs like this unnecessarily.
Idea or suggestion?

---

Boinc 7.24.1; Win 10 Pro

Please post the first 30-40 lines of your BOINC Event Log (CTRL+SHIFT+E) after a BOINC client start.
Also, check that your client (boinc.exe) starts up without any command line attributes added.

Only "boinctray.exe" and "boincmgr.exe /a /s" will start with the system.
Where can I see the startup and attributes of "boinc.exe"?
.
This is the log after program startup:
1/21/2024 9:10:36 PM | | Starting BOINC client version 7.24.1 for windows_x86_64
1/21/2024 9:10:36 PM | | log flags: file_xfer, sched_ops, task
1/21/2024 9:10:36 PM | | Libraries: libcurl/8.2.1-DEV Schannel zlib/1.2.13
1/21/2024 9:10:36 PM | | Data directory: C:\ProgramData\BOINC
1/21/2024 9:10:36 PM | |
1/21/2024 9:10:36 PM | | No usable GPUs found
1/21/2024 9:10:36 PM | | Windows processor group 0: 4 processors
1/21/2024 9:10:36 PM | | Host name: Nas
1/21/2024 9:10:36 PM | | Processor: 4 GenuineIntel Intel(R) Atom(TM) CPU D510 @ 1.66GHz [Family 6 Model 28 Stepping 10]
1/21/2024 9:10:36 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 cx16 movebe syscall nx lm tm2 pbe
1/21/2024 9:10:36 PM | | OS: Microsoft Windows 10: Professional x64 Edition, (10.00.19045.00)
1/21/2024 9:10:36 PM | | Memory: 1.98 GB physical, 2.61 GB virtual
1/21/2024 9:10:36 PM | | Disk: 118.68 GB total, 89.95 GB free
1/21/2024 9:10:36 PM | | Local time is UTC +1 hours
1/21/2024 9:10:36 PM | | No WSL found.
1/21/2024 9:10:36 PM | Einstein@Home | General prefs: from Einstein@Home (last modified 20-Jan-2024 18:05:57)
1/21/2024 9:10:36 PM | Einstein@Home | Host location: none
1/21/2024 9:10:36 PM | Einstein@Home | General prefs: using your defaults
1/21/2024 9:10:36 PM | | Reading preferences override file
1/21/2024 9:10:36 PM | | Preferences:
1/21/2024 9:10:36 PM | | - When computer is in use
1/21/2024 9:10:36 PM | | - 'In use' means mouse/keyboard input in last 1.00 minutes
1/21/2024 9:10:36 PM | | - don't use GPU
1/21/2024 9:10:36 PM | | - max CPUs used: 4
1/21/2024 9:10:36 PM | | - Use at most 20% of the CPU time
1/21/2024 9:10:36 PM | | - suspend if non-BOINC CPU load exceeds 25%
1/21/2024 9:10:36 PM | | - max memory usage: 0.60 GB
1/21/2024 9:10:36 PM | | - When computer is not in use
1/21/2024 9:10:36 PM | | - max CPUs used: 4
1/21/2024 9:10:36 PM | | - Use at most 65% of the CPU time
1/21/2024 9:10:36 PM | | - suspend if non-BOINC CPU load exceeds 30%
1/21/2024 9:10:36 PM | | - max memory usage: 0.99 GB
1/21/2024 9:10:36 PM | | - Suspend if no input in last 1440.00 minutes
1/21/2024 9:10:36 PM | | - Store at least 1.00 days of work
1/21/2024 9:10:36 PM | | - Store up to an additional 2.00 days of work
1/21/2024 9:10:36 PM | | - max download rate: 2048000 bytes/sec
1/21/2024 9:10:36 PM | | - max upload rate: 512000 bytes/sec
1/21/2024 9:10:36 PM | | - max disk usage: 5.00 GB
1/21/2024 9:10:36 PM | | - (to change preferences, visit a project web site or select Preferences in the Manager)
1/21/2024 9:10:36 PM | | Setting up project and slot directories
1/21/2024 9:10:36 PM | | Checking active tasks
1/21/2024 9:10:36 PM | Einstein@Home | URL https://einstein.phys.uwm.edu/; Computer ID 13172211; resource share 100
1/21/2024 9:10:36 PM | Milkyway@home | URL http://milkyway.cs.rpi.edu/milkyway/; Computer ID 1016309; resource share 100
1/21/2024 9:10:36 PM | | Setting up GUI RPC socket
1/21/2024 9:10:36 PM | | Checking presence of 89 project files
1/21/2024 9:10:36 PM | | Suspending network activity - time of day
1/21/2024 9:10:46 PM | | Suspending computation - CPU is busy

Depending on project, you may be suffering from lack of memory. Would running out cause the client to crash out?

My desktop computer is i5 (2400) / 8 gb ram / gtx 550 ti; ssd... and I experience the same on this machine.

Depending on project, you may be suffering from lack of memory. Would running out cause the client to crash out?

---

Boinc 7.24.1; Win 10 Pro

Update:
I checked Win 10's "Resource Monitor" and the free memory is really running out over time. However, this did not affect the operation of the Boinc client, but I noticed something else.
I used the machine intermittently (I will write about this below), and the Boinc client calculation always restarted fine. As it was set. Then, after some manual "manipulation", the calculation did not start again in the boinc client, even though there was free memory. The boinc client remained inactive and required a restart to function normally.
.
Then I changed the ram: 2 GB > 2 x 2 GB / dual. In other words, the machine now has 4 GB of RAM. I also cleaned Win 10 of unnecessary programs and services. Hibernation turned off, all other "power-saving" functions turned off, Powershell >> Get-AppxPackage .. etc. (as far as I could and dared..)
Win 10 swap file > manual > 2000 MB - 4000 MB
Then I changed some Boinc client functions:
- Switch between tasks time: 10 minutes.
- Requesting a task at the checkpoint time: 30 seconds.
- Storage at least day: 0.1
- up to additional day: 0.3
I hope that this way the content of the ram is updated (replaced) more often than the free memory space runs out (if this is the problem)
.
Then I used the machine (consciously) intermittently again and after a few used the client remained passive again. There was already plenty of free memory.

---

Boinc 7.24.1; Win 10 Pro

Update 2:
The Milkyway project's CPU usage sometimes drops to zero and stays that way. Especially if there is little (free) memory in the machine. Or if a background application with a high CPU/RAM requirement starts. After that, Milkyway won't restart hours later, and BOINC client task switching doesn't work either. (I spent many, many hours looking at Resource Monitor and the Boinc client)
I reproduced the error six times out of seven attempts on three computers using the following steps:
- the system/boinc client starts (Milkyway is running).
- I filled the RAM with data (free memory is about zero)
- I started Win-Defender from a .bat file with command line delay
- Windows-Defender completely loads the cpu/ram
- Milkyway detects high CPU usage and shuts down
- Windows-Defender ends (a lot of memory is freed up!)
- Milkyway did not start again, or stopped after 1...2 minutes, but the status changed to "Running".
- Milkyway project (not a task) manual suspension > another project (Einstein for me) starts immediately and works normally.
- The operation of the Milkyway project is restored only after the Boinc client is restarted (until the next shutdown)
***
Notes:
- then the Milkyway project does not freeze, it simply does not work
- this stop also stops the Boinc client in the sense that task switching does not work. Because of this, other projects do not start either.
- the result of the "load test" was the same for other cpu-loading programs (browser, etc.), so the problem is not caused by the operation of the antivirus
- With little free memory, Milkyway sometimes crashes even without heavy CPU load
- The other project that works for me is Einstein. This does not cause an error. It did not stop even with multiple and persistent cpu/ram overloads. It can be seen from the cpu usage that Einstein is also struggling, but he is pulling himself together. Its resource management is programmed to be very robust.
- when I realized this (three days ago) I stopped the Milkyway project. Only Einstein starts and has collected more credits in three days than previously in a week and a half.
***
Screenshots:

.
Milkyway CPU usage decreased before the computation stopped:

.
Einsten projekt memory management works (I've never seen one in the Milkyway!):

.
I hope I wasn't imagining it...

---

Boinc 7.24.1; Win 10 Pro

After stopping Einstein project manually, the MilkyWay project is activated, it does not work:

---

Boinc 7.24.1; Win 10 Pro