https://www.primegrid.com/result.php?resultid=1044031858

This is the most absurd task I have gotten.
Even though it looks like in the output file that it was using the maximum capability of my card, I watched it in BOINC stats and it was barely moving .0002 every 6 seconds.
In all my time on BOINC I have never seen a 100+ day completion time.

I looked in the PG stats for GPU and this is a #27 card, but still...114 days? Crazy!

https://www.primegrid.com/result.php?resultid=1044031858

This is the most absurd task I have gotten.
Even though it looks like in the output file that it was using the maximum capability of my card, I watched it in BOINC stats and it was barely moving .0002 every 6 seconds.
In all my time on BOINC I have never seen a 100+ day completion time.

I looked in the PG stats for GPU and this is a #27 card, but still...114 days? Crazy!

It appeared to be about 95% done when it was aborted.

https://www.primegrid.com/result.php?resultid=1044031858

This is the most absurd task I have gotten.
Even though it looks like in the output file that it was using the maximum capability of my card, I watched it in BOINC stats and it was barely moving .0002 every 6 seconds.
In all my time on BOINC I have never seen a 100+ day completion time.

I looked in the PG stats for GPU and this is a #27 card, but still...114 days? Crazy!

Is this a DYFL task? (we can't see the task in the link until it is finished running). Even if so, that is likely an incorrect estimate or there is something wrong with your computer. I ran some GFN-22 tasks, which are almost as long as DYFL, on a GT 1030 and they took 11 days, so I would expect DYFL on a GTX 1050 ti to take somewhere around 6 or 7 days.

If you can use HarwareInfo64 or some similar program to check the utilization of your GPU it would be good. (Task Manager in Windows will not report GPU utilization accurately, btw, so additional software is required). If GPU usage is close to 100% then it is likely just an overestimate by BOINC.

I have a 1050ti and a DYFL task takes just over 7 days and a GFN22 task takes just over 5 days.
That's likely an inaccurate measurement.
Like Kellen said, use a 3rd party program to check the GPU usage. Also check your temperatures to make sure things aren't throttling down to prevent melting.

One other thought.
I was doing driver updates the other night around the time this task started having problems. The studio driver updated ok, but I was having issues with game driver installing.
Would this cause problems? One driver being a higher version than the other?
It did not affect anything that runs on my old 650, but maybe it messed with the 1050?
Just something that has been running around in my brain lately.

It appeared to be about 95% done when it was aborted.

Now that's weird!
Everything I read showed it was not even really started.
Where did you read this information at so I can read it next time I get a weird reading?

Well, BOINC should have been showing you the correct completion time. I'm not sure why it wasn't. BOINC is notorious for this, however.

I looked in the stderr.txt output. While the task is running, this is in a file in the slot directory where the task is running. Once the task is over, it's included in the task page: https://www.primegrid.com/result.php?resultid=1044031858

Near the top of the stderr output, it says that the expected run time is 117 hours. This is usually pretty accurate.

While it doesn't tell you directly how far along it is, you can make a decent guess by reading between the lines.

Each time the task was stopped and restarted, which happened many times, it tells you how many iterations are remaining. The first time it restarted, there were 66 million iterations to go. The final time it restarted, there were 4 million iterations to go. So it had to be at least about 95% done.

I was doing driver updates the other night around the time this task started having problems. The studio driver updated ok, but I was having issues with game driver installing.
Would this cause problems?

It's hard to say if this did cause problems, but it certainly can cause problems.

I recommend never upgrading drivers -- or anything -- while there are tasks in progress.