Suddenly my gpu is not functioning as it was. I am running a gadget called GPU Meter and it shows that the GPU Clock is at 928MHz but that the usage is at 0%. Normally it is bouncing around at about 70 to 90 percent. I have changed nothing and not even done any MS updates lately. I've suspended a few of the wu to see if another would run and I have the same results.

I had had the cfg file set to run 3 tasks at a time and that wasn't working so I changed it to 2 tasks with the same results. Now I have it at one task and still nothing. If it weren't for the .04 cpu, the wu would never progress at all.

I've checked to make sure that everything is clean and the temp is running at 45C which is about 10 to 15 degrees cooler than normal.

Does anyone have any ideas what might be wrong?

Allen

---

Suddenly my gpu is not functioning as it was. I am running a gadget called GPU Meter and it shows that the GPU Clock is at 928MHz but that the usage is at 0%. Normally it is bouncing around at about 70 to 90 percent. I have changed nothing and not even done any MS updates lately. I've suspended a few of the wu to see if another would run and I have the same results.

I had had the cfg file set to run 3 tasks at a time and that wasn't working so I changed it to 2 tasks with the same results. Now I have it at one task and still nothing. If it weren't for the .04 cpu, the wu would never progress at all.

I've checked to make sure that everything is clean and the temp is running at 45C which is about 10 to 15 degrees cooler than normal.

Does anyone have any ideas what might be wrong?

Allen

Are you saying that you have no GPU tasks running or there is 1 when there should be more? The 0% load on the GPU would seem to indicate you have no tasks running.
If you have any tasks running on the GPU. Then you might want to start by opening Task Manager and check the Processes tab to make sure the app is actually running.
If it is you might want to try GPUz and see what it displays for the GPU usage. Maybe your gadget is broken.

When you see Running (0.04 CPU + 1 GPU) that doesn't mean the CPU is being used. The 0.04 is a percentage of CPU time the BOINC client uses when deciding how much work to request.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Suddenly my gpu is not functioning as it was. I am running a gadget called GPU Meter and it shows that the GPU Clock is at 928MHz but that the usage is at 0%. Normally it is bouncing around at about 70 to 90 percent. I have changed nothing and not even done any MS updates lately. I've suspended a few of the wu to see if another would run and I have the same results.

I had had the cfg file set to run 3 tasks at a time and that wasn't working so I changed it to 2 tasks with the same results. Now I have it at one task and still nothing. If it weren't for the .04 cpu, the wu would never progress at all.

I've checked to make sure that everything is clean and the temp is running at 45C which is about 10 to 15 degrees cooler than normal.

Does anyone have any ideas what might be wrong?

Allen

Are you saying that you have no GPU tasks running or there is 1 when there should be more? The 0% load on the GPU would seem to indicate you have no tasks running.
If you have any tasks running on the GPU. Then you might want to start by opening Task Manager and check the Processes tab to make sure the app is actually running.
If it is you might want to try GPUz and see what it displays for the GPU usage. Maybe your gadget is broken.

When you see Running (0.04 CPU + 1 GPU) that doesn't mean the CPU is being used. The 0.04 is a percentage of CPU time the BOINC client uses when deciding how much work to request.

Hal,
Yes, I am running (trying to) one task now, but when this slowdown occurred I was running 3 tasks with no trouble. I will try the GPUz and see what it says and I will also make sure that all tasks are running in task manager and I'll get back to you when I find out.

Thanks for the response!

---

Hal,

Can't figure it out. I came down to check on the computer and it was running the one wu with no trouble. I returned it to running 3 and it is now doing that with no trouble. I can only figure that either some hardware is going bad or I had a glitch in the system and it is clear now.

I did go into the bios and looked around. I did check on the gpu pci-e and made sure it was set properly and then saved and rebooted.

I did experienced a few lock-ups of the system before this odd occurrence reared it's ugly head. Now running three wu's and temp is 56c and usage is 65-90% so things are back to normal for now.

Thanks for explaining the .04cpu, I had no idea, I just figured it needed that much cpu for the wu to run on the gpu....stupid me.

Thanks for now! I hope this adventure is over but if it is not, I'll be sure to look you up again. BTW, all the work showed up in the task manager. By the time I got to the GPUz, the machine had locked up and when I rebooted everything was working fine again.

---

Hal,

Can't figure it out. I came down to check on the computer and it was running the one wu with no trouble. I returned it to running 3 and it is now doing that with no trouble. I can only figure that either some hardware is going bad or I had a glitch in the system and it is clear now.

I did go into the bios and looked around. I did check on the gpu pci-e and made sure it was set properly and then saved and rebooted.

I did experienced a few lock-ups of the system before this odd occurrence reared it's ugly head. Now running three wu's and temp is 56c and usage is 65-90% so things are back to normal for now.

Thanks for explaining the .04cpu, I had no idea, I just figured it needed that much cpu for the wu to run on the gpu....stupid me.

Thanks for now! I hope this adventure is over but if it is not, I'll be sure to look you up again. BTW, all the work showed up in the task manager. By the time I got to the GPUz, the machine had locked up and when I rebooted everything was working fine again.

Maybe the driver crashed & recovered? That normally results in tasks running very quickly and generating all errors... so I don't know. If it happens again maybe just give the system a cold boot and see what it does from there.

Many get get confused on the CPU portion of GPU tasks. Normally asking why their tasks don't run faster when they increase the value for it.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

I do have another question. The gpu usage is very strange compared to the way it used to run under v7. While it sometimes runs at 65-90%, sometimes it stays at 0% for 15 or 20 seconds and then bounces up to 80% or there abouts for a couple of seconds and then takes a break again. Right now it just jumped to 38% and then stopped for a few seconds and then bounce back to 80%. Now it's at 14%.
Is this normal???

Allen

BTW, why does your medal show that you are in the upper 5% of work done when mine shows 1% and you have done 7 times more work than I have??

---

BTW, why does your medal show that you are in the upper 5% of work done when mine shows 1% and you have done 7 times more work than I have??

Medals are linked to RAC, not to credit.

Sleepy

Can't figure it out. I came down to check on the computer and it was running the one wu with no trouble...

If the computer clock/time go back tasks (app processes) stop (exit) but BOINC continue to show them "Running"
(at least this happens on BOINC 6.10.58 (and less), I don't know if this happens on current versions of BOINC)

Usually the scenario is:
- computer clock go too fast and after some time is too far in the future
- then Windows syncs time (from CMOS or Internet) to the correct (= for all programs this looks like "go back in time")

In this case:
- tasks (app processes) stop (exit) after 30 seconds
- BOINC continue to show them "Running"

- BOINC restarts the tasks after the "missing" time period expires


Can somebody test this on new BOINC?
E.g. set the computer clock 3 minutes back (and wait/look what happens in the next 5 minutes)
 

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Can't figure it out. I came down to check on the computer and it was running the one wu with no trouble...

If the computer clock/time go back tasks (app processes) stop (exit) but BOINC continue to show them "Running"
(at least this happens on BOINC 6.10.58 (and less), I don't know if this happens on current versions of BOINC)

Usually the scenario is:
- computer clock go too fast and after some time is too far in the future
- then Windows syncs time (from CMOS or Internet) to the correct (= for all programs this looks like "go back in time")

In this case:
- tasks (app processes) stop (exit) after 30 seconds
- BOINC continue to show them "Running"

- BOINC restarts the tasks after the "missing" time period expires


Can somebody test this on new BOINC?
E.g. set the computer clock 3 minutes back (and wait/look what happens in the next 5 minutes)
 

You mean like when the clock changes for Daylight Saving Time? Which happened recently. I can't say I have ever seen BOINC kill apps when the time or date changes.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

You mean like when the clock changes for Daylight Saving Time? Which happened recently. I can't say I have ever seen BOINC kill apps when the time or date changes.

BOINC keeps track of all all times in UTC internally, and only applies a time zone offset when needed for user display. So, a DST change automatically applied by the OS doesn't affect BOINC at all: if you run any of the (many) projects which set their deadlines to an integral number of days, you can see the hour's shift showing up in task deadlines in the days and weeks leading up to a clock change.

BOINC doesn't like if if you change the real underlying system clock, rather than just the TZ offset - especially if you move the clock back to an earlier time. That used to be a big problem in the days of Windows 95/98/XP, when it was too easy to change the system date from the clock in the system tray. Bored office workers planning their holidays or looking forward to the next colleague's birthday party caused endless problems.....

(I had a Boss once who kept putting customer orders into the database several weeks in the future. All the official order-takers had their computers locked down solid - by me - but the Boss needed an administrative account...)

BTW, why does your medal show that you are in the upper 5% of work done when mine shows 1% and you have done 7 times more work than I have??

Medals are linked to RAC, not to credit.

Sleepy

Boy, it's great to keep on learning everyday. Thanks sleepy!!

---

Can't figure it out. I came down to check on the computer and it was running the one wu with no trouble...

If the computer clock/time go back tasks (app processes) stop (exit) but BOINC continue to show them "Running"
(at least this happens on BOINC 6.10.58 (and less), I don't know if this happens on current versions of BOINC)

Usually the scenario is:
- computer clock go too fast and after some time is too far in the future
- then Windows syncs time (from CMOS or Internet) to the correct (= for all programs this looks like "go back in time")

In this case:
- tasks (app processes) stop (exit) after 30 seconds
- BOINC continue to show them "Running"

- BOINC restarts the tasks after the "missing" time period expires


Can somebody test this on new BOINC?
E.g. set the computer clock 3 minutes back (and wait/look what happens in the next 5 minutes)
 

Interesting. I do remember when this used to happen in the past, as Richard has pointed out. It was quite strange. Apparently it doesn't happen anymore though. I do wonder if somehow this one system didn't get caught in the twilight zone of the time change we just went through. I just checked on it and it is running 3 wu's and running them all properly. However, it was locked up this morning when I checked on it. Gave it a cold boot and it's been working fine since.....knock on wood!

---

You mean like when the clock changes for Daylight Saving Time? Which happened recently. I can't say I have ever seen BOINC kill apps when the time or date changes.

BOINC keeps track of all all times in UTC internally, and only applies a time zone offset when needed for user display. So, a DST change automatically applied by the OS doesn't affect BOINC at all: if you run any of the (many) projects which set their deadlines to an integral number of days, you can see the hour's shift showing up in task deadlines in the days and weeks leading up to a clock change.

BOINC doesn't like if if you change the real underlying system clock, rather than just the TZ offset - especially if you move the clock back to an earlier time. That used to be a big problem in the days of Windows 95/98/XP, when it was too easy to change the system date from the clock in the system tray. Bored office workers planning their holidays or looking forward to the next colleague's birthday party caused endless problems.....

(I had a Boss once who kept putting customer orders into the database several weeks in the future. All the official order-takers had their computers locked down solid - by me - but the Boss needed an administrative account...)

I've seen this type of message in BOINC rather often New system time (1459473685) < old system time (1459475125); clearing timeouts. I was thinking it happened at DST, but it is only when the system clock changes. I did notice there is only a New system time message when the clock is set backward. Perhaps that is only due to the clearing timeout message?

If the systems time were off by day/week BOINC could abort tasks thinking they have missed their deadline. Probably the phrasing of saying a clock change would cause BOINC to exit the apps is what my brain got hung up on. Which is in a way correct if BOINC has aborted all of the tasks for the app.

In the Win 9x era I, on more than one occasion, nerfed my system time opening from the trey. Which really annoyed me because I've been oddly fixated with having the correct time. Which started when I was rather little before we even had a computer at home.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

You mean like when the clock changes for Daylight Saving Time? Which happened recently. I can't say I have ever seen BOINC kill apps when the time or date changes.

BOINC keeps track of all all times in UTC internally, and only applies a time zone offset when needed for user display. So, a DST change automatically applied by the OS doesn't affect BOINC at all: if you run any of the (many) projects which set their deadlines to an integral number of days, you can see the hour's shift showing up in task deadlines in the days and weeks leading up to a clock change.

BOINC doesn't like if if you change the real underlying system clock, rather than just the TZ offset - especially if you move the clock back to an earlier time. That used to be a big problem in the days of Windows 95/98/XP, when it was too easy to change the system date from the clock in the system tray. Bored office workers planning their holidays or looking forward to the next colleague's birthday party caused endless problems.....

(I had a Boss once who kept putting customer orders into the database several weeks in the future. All the official order-takers had their computers locked down solid - by me - but the Boss needed an administrative account...)

I've seen this type of message in BOINC rather often New system time (1459473685) < old system time (1459475125); clearing timeouts. I was thinking it happened at DST, but it is only when the system clock changes. I did notice there is only a New system time message when the clock is set backward. Perhaps that is only due to the clearing timeout message?

If the systems time were off by day/week BOINC could abort tasks thinking they have missed their deadline. Probably the phrasing of saying a clock change would cause BOINC to exit the apps is what my brain got hung up on. Which is in a way correct if BOINC has aborted all of the tasks for the app.

In the Win 9x era I, on more than one occasion, nerfed my system time opening from the trey. Which really annoyed me because I've been oddly fixated with having the correct time. Which started when I was rather little before we even had a computer at home.

I found some very nasty timer loops in the code, which made implicit assumptions that time always increased monotonically. The intention was clear: don't waste time by repeating the same action more often than once every 10 seconds, or whatever. But the implementation was sloppy: set a marker time, and wait until the current time was 10 seconds later. But if time turns back by a month, your 10-second delay becomes a month and 10 seconds.....

See http://boinc.berkeley.edu/trac/ticket/588

I think your 'clearing timeouts' message dates from when they cleared that bug, five years after I'd notified them.