I am getting plenty of validate errors lately. Could someone look into the server to see what is going on? Example work units that are getting validate errors for their results include work units 260747742, 260762949, 260774277, and 260745047.

Another work unit that resulted in validate errors is work unit 260747648.

New validate error: work unit 260786638

And another one bites the dust due to validate errors: work unit 260784171

One more looking like it will die due to validate error: 260791824

I will not report more soon because I am draining my work unit queue in preparation for a BOINC upgrade because BOINC 6.10.60 just got released, and my MilkyWay@home queue got drained.

I also have new validate errors (error rate is between 10-15 %).

Yes I think they are all de_separation_10_3s_free_1 type. May also have max # of error/total/success tasks of 1, 9, 6. Been happening for some time now, I aborted many before switching to another project.

OK I am getting loads of validate errors on all 5 of mine!
One, maybe too much overclocking, 5?
we have a serverside problem methinks!

Yep, de_separation_10_3s_free_1 are causing trouble.
Checked a couple of them and had like half of them not validating :(

Been away from the Project for a while, restarted today - reckon I hexed it :)

Same here - its the _10_3s_free WUs. Happening on both machines on 5850s as well as 5970s. Validate errors mostly - couple of other types, but those small number of "non _free" types was me settling in. Runs to about 40% dead WUs overall.

Majority of the those _10_3s_free types falling over. Going to switch Project's for a short while until this one settles back again.

Regards
Zy

Trying one more thing .... set nnt on both machines and aborted all _free's, see if the ones left go through error free - I suspect so, but giving it a whirl, should nail it one way of the other.

EDIT
Its definitely the _10_3s_free's. I aborted those in the queue on both machines, and validate errors stopped, all other types went through no bother. Something is amiss with the _free's, and need stopping at the server

Regards
Zy

same here both machines 2x4870 1x6950

Watch Out with these ...... I was originally worried re temperatures. I monitored the non free's and they are normal, the _frees are all crunching at around +10 degrees above normal on the card VRMs.

That will put the card into very hot territory without the User knowing unless the card VRM is being monitored. The card will show a slightly upped GPU temperature, but still appears ok, however a check on the VRM temperatures is a different matter.

The _free's are heating up the VRMs alarmingly - if you are still running the WUs, watch your VRMs like a hawk.

Its time to freeze all WUs, its too dangerous for VRMs on the _free's.

Regards
Zy

I've been having all the same issues today.

I have been just keeping an eye on it though and aborting any WU that comes up as the "free_1" name.

Seems everything else is working just fine.

If you have a Radeon HD 6xxx series card, you should not have to abort results due to the risk of overheating the VRM. AMD implemented PowerTune in these cards to automatically underclock the GPU by various levels if the code being sent to it would force the GPU over power usage limits until it reaches an underclocking level that would allow it to run under power usage limits, and then restore the clock once the power-hungry code goes away.

Two more validate errors: work units 261192073 and 261168214

One more: work unit 261208862

Two more: 261218718 and 261221074

Yep, all free_ wu's have a validate error. Off to DNETC until this gets resolved...

Yep, all free_ wu's have a validate error. Off to DNETC until this gets resolved...