Same problem here - cannot upload. It got progressively worse over the last few (2? 3?) days, now NO UL going through, lots of HTTP errors in msgs tab. I shut down network activity, will keep it off until at least the PM is over today - I have plenty enough WUs for that - and hopefully the issue will be fixed by then!!!

O.K., now I use BOINC DEV-V6.6.37 and the ULs go through.. of couse not all but maybe every 4th..
So I have better chances to UL my results.

Maybe.. I don't know how the devs wanted to do it..
But better/well it would be: If an UL don't reach the UL server, stop all ULs for ~ 60 sec. and then again start one UL, again not possible to reach the UL server again ~ 60 sec. break of all ULs. And then again start one UL. If one UL go through an new UL start to do this procedure.
This wouldn't be a well idea?

Because how was is possible that my BOINC DEV-V6.6.38 collects ~ 400 results in the UL overview?

But if your PC make a RAC of ~ 52,000 he must UL ~ 600 to 3,000 results/day!
And if you use DEV-V6.6.38 which don't work well.. you should take a BOINC Version which isn't so buggy.
So I use now DEV-V6.6.37 which don't collects result ULs, this version make the ULs.

No, I can't use V6.6.36 with the 'crazy EDF GPU BUG'.

The UL function in DEV-V6.6.38 don't work well.
I hope in DEV-V6.10.x this UL function work better (like I posted in my upper post) or is disabled.

But if your PC make a RAC of ~ 52,000 he must UL ~ 600 to 3,000 results/day!
And if you use DEV-V6.6.38 which don't work well.. you should take a BOINC Version which isn't so buggy.
So I use now DEV-V6.6.37 which don't collect result ULs, this version make the ULs.

No, I can't use V6.6.36 with the 'crazy EDF GPU BUG'.

The UL function in DEV-V6.6.38 don't work well.
I hope in DEV-V6.10.x this UL function work better (like I posted in my upper post) or is disabled.

Crazy EDF GPU bug you say? Is that when BOINC process a few % of a GPU task, then moves to another, process a few % of a GPU task, then moves to another,process a few % of a GPU task, then moves to another...

I had started seeing that over the past few weeks. I thought my GF8500 was just starting to fail or something so stopped doing GPU tasks. As it was slow anyway.SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the BP6/VP6 User Group today!

Crazy EDF GPU bug you say? Is that when BOINC process a few % of a GPU task, then moves to another, process a few % of a GPU task, then moves to another,process a few % of a GPU task, then moves to another...

I had started seeing that over the past few weeks. I thought my GF8500 was just starting to fail or something so stopped doing GPU tasks. As it was slow anyway.

Correct..
And every suspended CUDA WU take system RAM.
And if you have maybe ~ 20 or 30 suspended CUDA tasks, your PC can't crunch because your system RAM is overloaded.