SET PATH=%PATH%;%ProgramFiles%\BOINC

SET PATH=%PATH%;"%ProgramFiles%\BOINC"

Ok, my first problem was caused by the path being wrong - fixed that and changed the SET MAXCPUUSAGE=80.0 - still does not work. The file changes but not the % CPU

Haven't batch files in a very long time - forgot %x is variables.

If I use the command line parameter now do I add the % ?

I run the batch file with:


D:\SETICPU.bat

D:\SETICPU.bat 80.0

The program is called Macro Expert by GrassSoft.

I am trying your batch file though.

HWND hWnd

hWnd = FindWnd("", "BOINCManagerSystray", FW_ALL, 1)
If (hWnd) Then
    SendKeys(hWnd, "{Shift-F10}")
    MenuSelect("Open BOINC Manager")
EndIf

The batch file seems to try to work, however, reguardless of what I set

SET MAXCPUUSAGE=%5 or SET MAXCPUUSAGE=%70 (in my two cases)

it changes the value to 95%

@echo off
rem
rem Change the maximum amount of CPU BOINC is allowed to use.
rem

SETLOCAL ENABLEEXTENSIONS ENABLEDELAYEDEXPANSION

rem Add BOINC's executables to the path for this script
SET PATH=%PATH%;%ProgramFiles%\BOINC

rem Determine the global prefs override file name and location
SET GLOBALPREFS=%ProgramData%\BOINC\global_prefs_override.xml

rem What Max CPU should BOINC be allowed to use?
SET MAXCPUUSAGE=%1

rem Modify the override file
echo ^<global_preferences^                                     >  %GLOBALPREFS%
echo   ^<cpu_usage_limit^>%MAXCPUUSAGE%^</cpu_usage_limit^>    >> %GLOBALPREFS%
echo ^</global_preferences^>                                   >> %GLOBALPREFS%

boinccmd --read_global_prefs_override

ModLoad: 69000000 00012000 C:\Windows\system32\aticalrt64.dll (6.14.10.227) (-exported- Symbols Loaded)
Linked PDB Filename : c:\workarea\8.591\drivers\cal\drivers\src\api\calrt\lib\build\w764a\B_rel\aticalrt64.pdb
File Version : 6.14.10.227
Company Name : Advanced Micro Devices Inc.
Product Name : AMD CAL runtime
Product Version : 6.14.10.227

ModLoad: 02ca0000 0043b000 C:\Windows\system32\aticaldd64.dll (6.14.10.227) (-exported- Symbols Loaded)
Linked PDB Filename : c:\workarea\8.591\drivers\cal\drivers\src\ddi\lib\build\w764a\B_rel\aticaldd64.pdb
File Version : 6.14.10.227
Company Name : Advanced Micro Devices Inc.
Product Name : AMD CAL DD
Product Version : 6.14.10.227

- Unhandled Exception Record -
Reason: Breakpoint Encountered (0x80000003) at address 0x0000000076E06060

That's all I needed.

From my FAQs:

This error can happen when a task has exceeded the maximum CPU time or maximum disk space. The abort message causes the science application to call DebugBreak() which causes the 0x80000003 error code.

The idea being that if either the memory or CPU usage has been exceeded then there is either a memory leak or an infinite loop that the project needs to debug. DebugBreak() will cause the Windows Debugger to start up and dump a stack trace of the stuff the application was doing, and report it back to the project.

Most of the times you come across this error message however is when you have manually aborted one or more tasks that were running at that time. Aborting running tasks will also call the DebugBreak() routine and do the same dump of information as before.

boincscr.exe in BOINC directory is NOT digitally signed.

Is it secure?

Which version of the client are you using?

boincscr.exe in BOINC directory is NOT digitally signed.

Is it secure?

In my system, the Segmentation fault appears in this point of coproc.cpp:

retval = (*__calInit)();

calInit is given by:

callib = dlopen("libaticalrt.so", RTLD_NOW);

These are the dependencies of the library:

[root@localhost ice]# ldd /usr/lib64/libaticalrt.so
ldd: warning: you do not have execution permission for `/usr/lib64/libaticalrt.so'
        linux-vdso.so.1 =>  (0x00007fff11fff000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f1a09bfb000)
        librt.so.1 => /lib64/librt.so.1 (0x00007f1a099f3000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f1a0976e000)
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f1a09554000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f1a09350000)
        libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f1a0913d000)
        libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f1a08e04000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f1a08a96000)
        /lib64/ld-linux-x86-64.so.2 (0x000000326a600000)
        libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f1a08893000)
        libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f1a08678000)

However the error is generated into libaticaldd.so that seems not directly related to libaticalrt.so from the dependencies.

I test this with the latest trunk version (8.11.0) and with ElecticFence active for catching the segmentation fault point.

Is your computer connected to the Internet when the BOINC service crashes?

It crashes even if i'm not connected.