Endlessly repeated automated BOINC message "setting not configured to use GPU"

FurryGuy
FurryGuy
Joined: 20 Mar 05
Posts: 1
Credit: 8,354,642
RAC: 4,702
Topic 222103

Every time I start BOINC I get an automated message my Einstein@home settings do not allow for fetching nVidia GPU tasks.  The project needs to stop doing that!

I get it already, you don't need to nag and nag and NAG!

I deliberately choose to not allow GPU tasks on one of my computers, using the GPU by BOINC tasks causes the OS to become unstable.  Unstable to the point of getting repeated BSOD.  Unstable to the point I can not do any Windows 10 updates on the PC, they fail to install.

Another Win10 PC that has a different nVidia video card doesn't have this problem of instability.  The PC temp on both machines may run HOT (170+F for the GPUs and similar temps for the CPU cores) when BOINC uses the GPU, but that is to be expected with such intense and prolonged usages.

I freely give access to my computers to run BOINC tasks, but if this spam messaging continues I will consider no longer letting Einstein be an active project.

mikey
mikey
Joined: 22 Jan 05
Posts: 6,601
Credit: 605,739,293
RAC: 865,469

FurryGuy wrote:Every time I

FurryGuy wrote:

Every time I start BOINC I get an automated message my Einstein@home settings do not allow for fetching nVidia GPU tasks.  The project needs to stop doing that!

I get it already, you don't need to nag and nag and NAG!

I deliberately choose to not allow GPU tasks on one of my computers, using the GPU by BOINC tasks causes the OS to become unstable.  Unstable to the point of getting repeated BSOD.  Unstable to the point I can not do any Windows 10 updates on the PC, they fail to install.

Another Win10 PC that has a different nVidia video card doesn't have this problem of instability.  The PC temp on both machines may run HOT (170+F for the GPUs and similar temps for the CPU cores) when BOINC uses the GPU, but that is to be expected with such intense and prolonged usages.

I freely give access to my computers to run BOINC tasks, but if this spam messaging continues I will consider no longer letting Einstein be an active project.

This is not generated by Einstein it 's generated by Boinc itself and is simply a reminder that there are other things you could be doing with your machine. It is limited to one Project so if you are attached to multiple Projects you won't see multiple Projects saying 'Im here too'.

Cameron
Cameron
Joined: 26 Apr 05
Posts: 12
Credit: 24,437,352
RAC: 54,373

mikey wrote: This is not

mikey wrote:
This is not generated by Einstein it 's generated by Boinc itself and is simply a reminder that there are other things you could be doing with your machine. It is limited to one Project so if you are attached to multiple Projects you won't see multiple Projects saying 'Im here too'.

 

It might be generated by BOINC but it's not limited to 1 project.

I have it reminding me for Einstein as well as Milkyway (which I re attached to a couple of days ago.)

 Einstein is reminding me about the CPUs (I'm happy with just my GPU contributing)

Milkyway is reminding me about my GPU. (which might actually be usable to to project this time round) if the card can do DP.

I'll be checking that out when my current Einsein queue is completed.

 

It looks like its projects that provide CPU and GPU work where user settings for whatever reason indicate your not allowing work for both resource types.

mikey
mikey
Joined: 22 Jan 05
Posts: 6,601
Credit: 605,739,293
RAC: 865,469

Cameron wrote: mikey wrote:

Cameron wrote:

mikey wrote:
This is not generated by Einstein it 's generated by Boinc itself and is simply a reminder that there are other things you could be doing with your machine. It is limited to one Project so if you are attached to multiple Projects you won't see multiple Projects saying 'Im here too'.

 

It might be generated by BOINC but it's not limited to 1 project.

I have it reminding me for Einstein as well as Milkyway (which I re attached to a couple of days ago.)

 Einstein is reminding me about the CPUs (I'm happy with just my GPU contributing)

Milkyway is reminding me about my GPU. (which might actually be usable to to project this time round) if the card can do DP.

I'll be checking that out when my current Einsein queue is completed.

 

It looks like its projects that provide CPU and GPU work where user settings for whatever reason indicate your not allowing work for both resource types.

It should be only one Project per time, but yes it could rotate thru all the Projects you are attached too on that pc, or be stuck on one Project. I see both on my pc's.

Tsarstepan
Tsarstepan
Joined: 11 Mar 20
Posts: 3
Credit: 1,626,240
RAC: 5,093

FurryGuy wrote:Every time I

FurryGuy wrote:
Every time I start BOINC I get an automated message my Einstein@home settings do not allow for fetching nVidia GPU tasks.  The project needs to stop doing that! I get it already, you don't need to nag and nag and NAG! I deliberately choose to not allow GPU tasks on one of my computers, using the GPU by BOINC tasks causes the OS to become unstable.  Unstable to the point of getting repeated BSOD.  Unstable to the point I can not do any Windows 10 updates on the PC, they fail to install. Another Win10 PC that has a different nVidia video card doesn't have this problem of instability.  The PC temp on both machines may run HOT (170+F for the GPUs and similar temps for the CPU cores) when BOINC uses the GPU, but that is to be expected with such intense and prolonged usages. I freely give access to my computers to run BOINC tasks, but if this spam messaging continues I will consider no longer letting Einstein be an active project.

I had a similar error message (not for this one) but for Asteroids@Home claiming my GPU's driver wasn't up to date though I went through hell getting it up to date after experiencing this error message at an off and on/randomish basis. I basically suspended the project out of resignation.

Harri Liljeroos
Harri Liljeroos
Joined: 10 Dec 05
Posts: 623
Credit: 866,863,916
RAC: 1,101,671

I remember something that

I remember something that this message was related to a bug in later versions of Boinc (starting from 7.16.5). It had something to do with missing CC_config.xml file. You can create one in Boinc manager's advanced view -> Options -> Event log options. You may need to restart Boinc to take full effect of those options.

mikey
mikey
Joined: 22 Jan 05
Posts: 6,601
Credit: 605,739,293
RAC: 865,469

Harri Liljeroos wrote: I

Harri Liljeroos wrote:

I remember something that this message was related to a bug in later versions of Boinc (starting from 7.16.5). It had something to do with missing CC_config.xml file. You can create one in Boinc manager's advanced view -> Options -> Event log options. You may need to restart Boinc to take full effect of those options. 

It's a 'feature' supporting the different Projects that you aren't crunching for but have in your Project list. I get one now saying World Community Grid is not set up to use my  Nivida gpu......they DON'T HAVE ANY GPU TASKS and haven't had any for a long  time!!! The  Projects asked for this so it was added to support them in one of the releases, maybe 7.14.2. The Projects asked for EVERY Project to be able to say 'I'm here too' every single time but the Programmers said one at a time is enough.

Harri Liljeroos
Harri Liljeroos
Joined: 10 Dec 05
Posts: 623
Credit: 866,863,916
RAC: 1,101,671

The bug I remember was

The bug I remember was something that the GPU message was just about the only message that was shown in the event log because the default values for event log options were not set if there were no cc_config file present.

mikey
mikey
Joined: 22 Jan 05
Posts: 6,601
Credit: 605,739,293
RAC: 865,469

Harri Liljeroos wrote: The

Harri Liljeroos wrote:

The bug I remember was something that the GPU message was just about the only message that was shown in the event log because the default values for event log options were not set if there were no cc_config file present. 

Yes I think they created one in all the new versions if it isn't already there to fix that.

Keith Myers
Keith Myers
Joined: 11 Feb 11
Posts: 925
Credit: 924,185,082
RAC: 2,633,648

No, they just fixed the

No, they just fixed the bugfix that broke the original generation of the stock cc_config options.  Another DA fubar issue again.

And the problem of the OP of the nag messages is fixed in the latest client.

 

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.