i would DDU your current drivers and reinstall completely fresh. to rule it out.
some of your errors seem consistent with driver issues, CL_INVALID_COMMAND_QUEUE. one of these instances happened within minutes of your CL_OUT_OF_HOST_MEMORY error and are likely linked to the same driver crash event.
did you DDU the old drivers before updating? if not, you should do that and try again. if you have some driver corruption, sometimes it can linger across driver installs and upgrades and issues will persist until you remove every last trace of the old drivers and start again. the best way to run DDU is to boot into safe mode, run it there, then reboot and install new drivers fresh.
it might also be an issue with the latest drivers. try an older version, like around 525.xx or so.
Just updated via a clean install to 537.42 and the first WU errored out, still being worked on by another host. But all other WU are completing OK with no driver crash.
So don't know if it was the clean install which helped or the new driver version.
Just updated via a clean install to 537.42 and the first WU errored out, still being worked on by another host. But all other WU are completing OK with no driver crash.
So don't know if it was the clean install which helped or the new driver version.
...
Sounds good.
Would be of interest to know which method you used for the clean install.
Just use the one built into the driver installer. It removed the old driver then rebooted to remove it. The system restarted with the default video driver then I had to re-run the nVidia installer -- it didn't auto-continue after the restart.
Then restarted BOINC and retrieved a new batch of WU's and only the first errored out, all others completed and validated. The WU which errored out was successfully completed by another user's host.
I suspected that BOINC and the All-Sky Gravitational Wave search on O3 v1.04 app was having a resource contention when my screen saver (ElectricSheep Gold) or any app with GPU acceleration (Firefox) were used -- that's when the driver would crash before.
But the WU which errored out happened after the screen saver was on and running and only errored out when the monitor was turned off by my power plan.
But allowing the same thing to happen to the other WUs didn't generate the same issue, all subsequent WU's completed in the same conditions.
So...don't know.
I'll report back if I get any other GPU apps assigned to me to compare buut so far, I'm only getting All-Sky Gravitational Wave search on O3 v1.04 WUs.
i would DDU your current
)
i would DDU your current drivers and reinstall completely fresh. to rule it out.
some of your errors seem consistent with driver issues, CL_INVALID_COMMAND_QUEUE. one of these instances happened within minutes of your CL_OUT_OF_HOST_MEMORY error and are likely linked to the same driver crash event.
_________________________________________________________________________
I'm about to leave town for a
)
I'm about to leave town for a week so I'll triage the potential driver issue when I return.
Thanks for the detailed and accurate analysis of the crash logs to point me in a direction.
I just updated the nVidia
)
I just updated the nVidia driver to 537.34 and all tasks failed.
examples:
https://einsteinathome.org/workunit/752170493
https://einsteinathome.org/workunit/752170555
did you DDU the old drivers
)
did you DDU the old drivers before updating? if not, you should do that and try again. if you have some driver corruption, sometimes it can linger across driver installs and upgrades and issues will persist until you remove every last trace of the old drivers and start again. the best way to run DDU is to boot into safe mode, run it there, then reboot and install new drivers fresh.
it might also be an issue with the latest drivers. try an older version, like around 525.xx or so.
_________________________________________________________________________
... try 537.42 and be sure
)
... try 537.42 and be sure to put a check mark on the field "perform a clean installation" ...
EDIT: ... have to do a "custom installation" to see that field !!!
no that's not what I'm
)
no that's not what I'm referring to. "clean installation" can still leave some remnants.
you really have to use DDU to get it all.
https://www.guru3d.com/download/display-driver-uninstaller-download/
_________________________________________________________________________
Yes, I know, but thanks
)
Yes, I know, but thanks anyway.
BUT, I have never ever had a problem with moving to new Nvidia GPU driver versions.
Maybe just luck ....
Have you all a nice weekend ...
S-F-V
Just updated via a clean
)
Just updated via a clean install to 537.42 and the first WU errored out, still being worked on by another host. But all other WU are completing OK with no driver crash.
So don't know if it was the clean install which helped or the new driver version.
Error:
https://einsteinathome.org/workunit/752518219
Success:
https://einsteinathome.org/workunit/752518551
https://einsteinathome.org/workunit/752518220
https://einsteinathome.org/workunit/752518216
lohphat wrote: Just updated
)
Sounds good.
Would be of interest to know which method you used for the clean install.
Nvidia or DDU ?
S-F-V
Just use the one built into
)
Just use the one built into the driver installer. It removed the old driver then rebooted to remove it. The system restarted with the default video driver then I had to re-run the nVidia installer -- it didn't auto-continue after the restart.
Then restarted BOINC and retrieved a new batch of WU's and only the first errored out, all others completed and validated. The WU which errored out was successfully completed by another user's host.
https://einsteinathome.org/workunit/752518219
I suspected that BOINC and the All-Sky Gravitational Wave search on O3 v1.04 app was having a resource contention when my screen saver (ElectricSheep Gold) or any app with GPU acceleration (Firefox) were used -- that's when the driver would crash before.
But the WU which errored out happened after the screen saver was on and running and only errored out when the monitor was turned off by my power plan.
But allowing the same thing to happen to the other WUs didn't generate the same issue, all subsequent WU's completed in the same conditions.
So...don't know.
I'll report back if I get any other GPU apps assigned to me to compare buut so far, I'm only getting All-Sky Gravitational Wave search on O3 v1.04 WUs.