Thanks for the help Byron. Those are all good suggestions, however I have tried them already. Well, I cleaned desktop insides about a year ago. I could do this again. [As a side note, would a overheating CPU really show this behavior?] I also made sure that the BOINC manager was set at 100% CPU. Would it be worth while and lower the CPU time to, say, 10% to see what happens?
And also in the beginning, I mistyped by service pack. I typed SP2, when I should have typed SP3.
Aside from the looking into overheating and CPU time, I may have to just accept this...
Quote:
Quote:
I changed my CPU from 90% to 100% using the web interface, which was suggested in the post you linked in a previously reply.
Also I should have mentioned it's possible the setting for the cpu time is set in the Boinc Manager, just in case that's what is actually being used, that would be located under Advanced in the processor usage tab under the setting "use at most 100% cpu time" in the Boinc Manager.
When you start up Boinc Manager copy and paste the message log here, if you'd like us to determine if your settings are global or local instead.
Well, I cleaned desktop insides about a year ago. I could do this again.
(As a side note, would a overheating CPU really show this behavior?]
An over heating cpu is one of the top reasons for the type of behaviour your pc has shown with the screen saver and the error you had. It's right up there with software conflict. Try speedfan or a similar type prog to see what the temps are. BTW a year is too long by most standards between pc cleanings.
Quote:
I also made sure that the BOINC manager was set at 100% CPU. Would it be worth while and lower the CPU time to, say, 10% to see what happens?
Yes since your pc is a single core cpu. This is mainly a problem in multi-cpu system but I've read others with single core cpu's have had the same problems with the error you had with havng it lower, and changing it to 100% helped them. Doesn't mean the same is happening here so adjusting that setting is worth a try for sure with regards to the screensaver, but could get the error mentioned in the work being done.
Quote:
Aside from the looking into overheating and CPU time, I may have to just accept this...
Have you tried running chkdsk /f rather than a standard disk check?
Screensaver problems as well as the error you had, are one of the harder ones to narrow down, but if it worked correctly with the setup you have now, it should be albe to again, providing there isn't a hardware/software issue introduced into the system that continues to prevent it. Could also still be a hardware issue, with the video card, RAM, motherboard ect. or even software, but in the end you may be right, and you might not be able to track down the cause. I"m still interested in seeing the WU you've been working on clear with no problems so we can for the moment eliminate the error.
I set the CPU time from 100% to 10% to no avail. Still the same. Now, I have the time back up to 100%. And still the same.
I have not cleaned out the chasis yet, due to lack of time, but I will get to this ASAP. Maybe tonight, I hope.
Yes, I have done both the chkdsk, and the standard scan.
You know, really, this problem (or annoyance rather) came from out of nowhere. One day, the screen saver motion was smooth as silk. The next, choppy or jittery. To my best knowledge, nothing on my system changed between the two. It's a total mystery. Anyway, I'll give the case inards a good blow and hopefully, that will be it.
Thanks for staying with me!
Quote:
Quote:
Well, I cleaned desktop insides about a year ago. I could do this again.
(As a side note, would a overheating CPU really show this behavior?]
An over heating cpu is one of the top reasons for the type of behaviour your pc has shown with the screen saver and the error you had. It's right up there with software conflict. Try speedfan or a similar type prog to see what the temps are. BTW a year is too long by most standards between pc cleanings.
Quote:
I also made sure that the BOINC manager was set at 100% CPU. Would it be worth while and lower the CPU time to, say, 10% to see what happens?
Yes since your pc is a single core cpu. This is mainly a problem in multi-cpu system but I've read others with single core cpu's have had the same problems with the error you had with havng it lower, and changing it to 100% helped them. Doesn't mean the same is happening here so adjusting that setting is worth a try for sure with regards to the screensaver, but could get the error mentioned in the work being done.
Quote:
Aside from the looking into overheating and CPU time, I may have to just accept this...
Have you tried running chkdsk /f rather than a standard disk check?
Screensaver problems as well as the error you had, are one of the harder ones to narrow down, but if it worked correctly with the setup you have now, it should be albe to again, providing there isn't a hardware/software issue introduced into the system that continues to prevent it. Could also still be a hardware issue, with the video card, RAM, motherboard ect. or even software, but in the end you may be right, and you might not be able to track down the cause. I"m still interested in seeing the WU you've been working on clear with no problems so we can for the moment eliminate the error.
I highly doubt that it's your computer that's causing the screensaver problem. I'm running XP service pack 3 (and have been since before I joined), my computer is not overheating, none of my WU's have encountered errors, and my computer has no problems whatsoever with the CDPN, primegrid, or LHC@home screensavers. I'm running 6.2.19 and I noticed the screensaver issue for Einstein pop up about the time you did. I haven't changed any of my settings that could correspond with the screensaver problem popping up, so it's probably not your setting issues either. Most likely, there was some sort of update to the WU's or such that 6.2.19 didn't like. What I recommend is that you switch your screensaver settings over to blank screen (or something other than BOINC) so that your computer doesn't waste time and effort trying to fix the screensaver. Either that or try downgrading BOINC to an older version.
~ Mary :)
~It only takes one bottle cap moving at 23,000 mph to ruin your whole day~
I'm running 6.2.19 and I noticed the screensaver issue for Einstein pop up about the time you did. I haven't changed any of my settings that could correspond with the screensaver problem popping up, so it's probably not your setting issues either. Most likely, there was some sort of update to the WU's or such that 6.2.19 didn't like. What I recommend is that you switch your screensaver settings over to blank screen (or something other than BOINC) so that your computer doesn't waste time and effort trying to fix the screensaver. Either that or try downgrading BOINC to an older version.
~ Mary :)
Don't think it's likely (though I guess not impossible) this is a 6.2.19 issue for him, since he upgraded to 6.2.19 with the screensaver issue. I also don't remember any update to the stock application during the time frame both of you appear to have started noticing the issue. If I'm not mistaken 6.04 was released in Aug or so. I will agree though it may be we never do find anything that can be pointed to on the pc.
I would like to also suggest rather than just setting the screensaver to blank maybe trying the Beta 6.09 application. I believe there is a difference in the graphics application from the stock 6.04. If nothing else if it doesn't work and you're not going to use the graphics anyway, you will at least be able to do the tasks faster.
Thanks for the suggestions. I will try the beta and report what happens.
BTW Bryon, I cleaned the chasis interior focusing on the CPU and surround area as best I could without a can of air duster. [It did needed the cleaning, regardless of this problem.] Perhaps I could do a better job with a can of air, but the screensaver problem persists. I am not against trying again...
In the meantime, I'll tryout the beta version.
Quote:
Quote:
Oy MMCC,
I'm running 6.2.19 and I noticed the screensaver issue for Einstein pop up about the time you did. I haven't changed any of my settings that could correspond with the screensaver problem popping up, so it's probably not your setting issues either. Most likely, there was some sort of update to the WU's or such that 6.2.19 didn't like. What I recommend is that you switch your screensaver settings over to blank screen (or something other than BOINC) so that your computer doesn't waste time and effort trying to fix the screensaver. Either that or try downgrading BOINC to an older version.
~ Mary :)
Don't think it's likely (though I guess not impossible) this is a 6.2.19 issue for him, since he upgraded to 6.2.19 with the screensaver issue. I also don't remember any update to the stock application during the time frame both of you appear to have started noticing the issue. If I'm not mistaken 6.04 was released in Aug or so. I will agree though it may be we never do find anything that can be pointed to on the pc.
I would like to also suggest rather than just setting the screensaver to blank maybe trying the Beta 6.09 application. I believe there is a difference in the graphics application from the stock 6.04. If nothing else if it doesn't work and you're not going to use the graphics anyway, you will at least be able to do the tasks faster.
Thanks for the suggestions. I will try the beta and report what happens.
BTW Bryon, I cleaned the chasis interior focusing on the CPU and surround area as best I could without a can of air duster. [It did needed the cleaning, regardless of this problem.] Perhaps I could do a better job with a can of air, but the screensaver problem persists. I am not against trying again...
I'd hold off on the opti app till you're able to do a better cleaning of the case with the can of air. If there is a heat problem the opti app will just make it worse and could also cause other problems. You'll also need the speedfan to check the temps after you install the opti app to make sure it's not going to cause heat problems.
It's up to you naturally, but I'd clean the pc out, check the temps with speedfan, and then if the temps check out ok with no other apparent problems, install the opti app.
I cleaned out the chasis extremely well, which sadly did not make a difference, and now I have installed the 6.09 Beta version....which is not yet working for me. I've posted the problem in the 6.09 Beta thread.
Quote:
Quote:
Mary and Byron,
Thanks for the suggestions. I will try the beta and report what happens.
BTW Bryon, I cleaned the chasis interior focusing on the CPU and surround area as best I could without a can of air duster. [It did needed the cleaning, regardless of this problem.] Perhaps I could do a better job with a can of air, but the screensaver problem persists. I am not against trying again...
I'd hold off on the opti app till you're able to do a better cleaning of the case with the can of air. If there is a heat problem the opti app will just make it worse and could also cause other problems. You'll also need the speedfan to check the temps after you install the opti app to make sure it's not going to cause heat problems.
It's up to you naturally, but I'd clean the pc out, check the temps with speedfan, and then if the temps check out ok with no other apparent problems, install the opti app.
I cleaned out the chasis extremely well, which sadly did not make a difference, and now I have installed the 6.09 Beta version....which is not yet working for me. I've posted the problem in the 6.09 Beta thread.
Thanks for the help Byron.
)
Thanks for the help Byron. Those are all good suggestions, however I have tried them already. Well, I cleaned desktop insides about a year ago. I could do this again. [As a side note, would a overheating CPU really show this behavior?] I also made sure that the BOINC manager was set at 100% CPU. Would it be worth while and lower the CPU time to, say, 10% to see what happens?
And also in the beginning, I mistyped by service pack. I typed SP2, when I should have typed SP3.
Aside from the looking into overheating and CPU time, I may have to just accept this...
RE: Well, I cleaned desktop
)
An over heating cpu is one of the top reasons for the type of behaviour your pc has shown with the screen saver and the error you had. It's right up there with software conflict. Try speedfan or a similar type prog to see what the temps are. BTW a year is too long by most standards between pc cleanings.
Yes since your pc is a single core cpu. This is mainly a problem in multi-cpu system but I've read others with single core cpu's have had the same problems with the error you had with havng it lower, and changing it to 100% helped them. Doesn't mean the same is happening here so adjusting that setting is worth a try for sure with regards to the screensaver, but could get the error mentioned in the work being done.
Have you tried running chkdsk /f rather than a standard disk check?
Screensaver problems as well as the error you had, are one of the harder ones to narrow down, but if it worked correctly with the setup you have now, it should be albe to again, providing there isn't a hardware/software issue introduced into the system that continues to prevent it. Could also still be a hardware issue, with the video card, RAM, motherboard ect. or even software, but in the end you may be right, and you might not be able to track down the cause. I"m still interested in seeing the WU you've been working on clear with no problems so we can for the moment eliminate the error.
I set the CPU time from 100%
)
I set the CPU time from 100% to 10% to no avail. Still the same. Now, I have the time back up to 100%. And still the same.
I have not cleaned out the chasis yet, due to lack of time, but I will get to this ASAP. Maybe tonight, I hope.
Yes, I have done both the chkdsk, and the standard scan.
You know, really, this problem (or annoyance rather) came from out of nowhere. One day, the screen saver motion was smooth as silk. The next, choppy or jittery. To my best knowledge, nothing on my system changed between the two. It's a total mystery. Anyway, I'll give the case inards a good blow and hopefully, that will be it.
Thanks for staying with me!
Oy MMCC, I highly doubt
)
Oy MMCC,
I highly doubt that it's your computer that's causing the screensaver problem. I'm running XP service pack 3 (and have been since before I joined), my computer is not overheating, none of my WU's have encountered errors, and my computer has no problems whatsoever with the CDPN, primegrid, or LHC@home screensavers. I'm running 6.2.19 and I noticed the screensaver issue for Einstein pop up about the time you did. I haven't changed any of my settings that could correspond with the screensaver problem popping up, so it's probably not your setting issues either. Most likely, there was some sort of update to the WU's or such that 6.2.19 didn't like. What I recommend is that you switch your screensaver settings over to blank screen (or something other than BOINC) so that your computer doesn't waste time and effort trying to fix the screensaver. Either that or try downgrading BOINC to an older version.
~ Mary :)
~It only takes one bottle cap moving at 23,000 mph to ruin your whole day~
RE: Oy MMCC, I'm running
)
Don't think it's likely (though I guess not impossible) this is a 6.2.19 issue for him, since he upgraded to 6.2.19 with the screensaver issue. I also don't remember any update to the stock application during the time frame both of you appear to have started noticing the issue. If I'm not mistaken 6.04 was released in Aug or so. I will agree though it may be we never do find anything that can be pointed to on the pc.
I would like to also suggest rather than just setting the screensaver to blank maybe trying the Beta 6.09 application. I believe there is a difference in the graphics application from the stock 6.04. If nothing else if it doesn't work and you're not going to use the graphics anyway, you will at least be able to do the tasks faster.
Mary and Byron, Thanks for
)
Mary and Byron,
Thanks for the suggestions. I will try the beta and report what happens.
BTW Bryon, I cleaned the chasis interior focusing on the CPU and surround area as best I could without a can of air duster. [It did needed the cleaning, regardless of this problem.] Perhaps I could do a better job with a can of air, but the screensaver problem persists. I am not against trying again...
In the meantime, I'll tryout the beta version.
RE: Mary and Byron, Thanks
)
I'd hold off on the opti app till you're able to do a better cleaning of the case with the can of air. If there is a heat problem the opti app will just make it worse and could also cause other problems. You'll also need the speedfan to check the temps after you install the opti app to make sure it's not going to cause heat problems.
It's up to you naturally, but I'd clean the pc out, check the temps with speedfan, and then if the temps check out ok with no other apparent problems, install the opti app.
Hi Bryon, I cleaned out
)
Hi Bryon,
I cleaned out the chasis extremely well, which sadly did not make a difference, and now I have installed the 6.09 Beta version....which is not yet working for me. I've posted the problem in the 6.09 Beta thread.
RE: Hi Bryon, I cleaned
)
Hi, saw the message and responded to it here
Hi MMCC, Saw this post in
)
Hi MMCC,
Saw this post in another thread, I tend to agree with you
It would seem to be that or a less attractive task of uninstalling the video card and reinstalling it and so on with no better chance of success.
How's the new opti app going? Are the temps still in a comfortable range?