I set it up and ran it through once -- no lockup -- but in doing so I noticed the checkpoint file and wondered if that might be to blame. Can I bench 'from the checkpoint somehow? I'm not sure how to do this in the bench but I'll fiddle around a bit.

Full disclosure: this is a 1080 Ti running in an eGPU enclosure over Thunderbolt 3

So there's a whole other kettle of fish thrown in to the mix.
Does it lock if the Video card is physically in that machine? (ie take the Thunderbolt connection out of the mix. I've seen several reviews where certain benchmarks won't complete on certain systems when running GPUs in external enclosures over Thunderbolt, yet will run on a different motherboard. Various hardware/BIOS/driver incompatibilities between different motherboards & external units).Grant
Darwin NT

Full disclosure: this is a 1080 Ti running in an eGPU enclosure over Thunderbolt 3

So there's a whole other kettle of fish thrown in to the mix.
Does it lock if the Video card is physically in that machine? (ie take the Thunderbolt connection out of the mix. I've seen several reviews where certain benchmarks won't complete on certain systems when running GPUs in external enclosures over Thunderbolt, yet will run on a different motherboard. Various hardware/BIOS/driver incompatibilities between different motherboards & external units).

Any other system you can run the eGPU on?
If it runs OK on all other systems & GPUs, then that just leaves Thunderbolt as the issue.
Be it drivers or hardware.
Any updated Thunderbolt drivers/BIOS for the motherboard or the eGPU unit about?Grant
Darwin NT

Any other system you can run the eGPU on?
If it runs OK on all other systems & GPUs, then that just leaves Thunderbolt as the issue.
Be it drivers or hardware.
Any updated Thunderbolt drivers/BIOS for the motherboard or the eGPU unit about?

Well I have 3 matching cards in another machine -- I'm not really interested in moving hardware around because, like I said, the card runs 3D apps just fine -- it's been running our game for 4 hours now, it's cleared over a hundred SETI work units, and the same workunit runs start to finish in the benchmark.

And yes, I checked drivers.

I hacked the XML to clear the checkpoint but still locked up after-- I must not have done it right. I'm not sure if there's a proper way to do that.

Seemed like we had a winner but then lockup at 95.38%. After restart it resumed from a CP from around 91% and locked up again shortly afterward.

I'm growing uncomfortable with so many hard shutdowns on this system -- I'm over 10 now and I'm worried about FS corruption on a machine I need to work on. I've run it 5 or 6 times in the benchmark but in BOINC it always brings down my machine.

If you aren't really interested in anything diagnostic I'll abort this task and see if any others cause problems.

If you aren't really interested in anything diagnostic I'll abort this task and see if any others cause problems.

Well, app behavior should be the same being run under BOINC or not, provided you supplied same command line switches.
Absence of lockups in offline run tells that there could be some interference fro boinc per se. Worth to consult with BOINC devs/boards if BOINC itself communicates with GPU while scientific app running.SETI apps news
We're not gonna fight them. We're gonna transcend them.

When the client starts up it queries drivers for how many devices there are. After that it doesn't touch drivers again. It knows which GPUs are in use by simply keeping track of which GPUs it has assigned tasks to.

If you mean boinc_get_opencl_ids() it queries drivers to get available platform and device ids and then returns ones matching requested device. Apart from driver queries its code runs entirely in science app.

I am having an issue with an AMD/ATI Radeon V5900 GPU in one of my machines. I recently updated the driver as I had noticed that BOINC was not recognizing the GPU. When I checked the driver, it had never been updated. Therefore, I checked the AMD website for this card and found the most recent driver for Windows 7, date 02/15/2017. I updated the drive with this one: https://support.amd.com/en-us/download/workstation/previous/graphics?os=Windows%207%20-%2064&rev=15.201.2401.1009. Once installed, I restarted BOINC and it recognized the GPU and was able to download WUs. However, it appears that any WUs that it tries to process end in errors. I have attached it to two separate projects (Einstein and Seti) and both end with errors. In most cases, both process a WU for about 25 seconds and then say it is done and move on to the next one. I detached Einstein as I had heard about a minimum RAM requirement and I may not have enough to process these, but I thought Seti would work as the identical computer I have processes Seti WUs just fine.

Here is a WU from the computer (C1) that errors out: https://setiathome.berkeley.edu/result.php?resultid=6438007814
Here is a WU from the computer (C2) that processes just fine: https://setiathome.berkeley.edu/result.php?resultid=6415146737

Following is first few lines from the BOINC Event Log for information:

Computers C1 and C2 are nearly identical in that they were both purchased at the same time and contained the exact same hardware. The only difference now is that the hard drives were updated to SSDs and the SSD manufacturer's are different. I performed the same upgrade on C2's GPU driver as C1. It too had issues with Einstein GPU WUs, but I switched to Seti GPU WUs and no issues since.

If anyone has any ideas as to what the issue might be I would be very interested to know. If additional information is required, just ask an d I will get it.