I doubt the version of BOINC is going to be a problem - as the Manager program is separate to the boinc program and as long as both of their respective filenames are what each expects to "see" (irrespective of version number) then neither will care too much.
re: app_config
This is my version:
This for an older CPU and older (single) GPU, both of which are less powerful than yours. So, I doubt that this is the issue - but if you want to edit your file to the values shown in mine then try it - so, just suspend any MW tasks, find the "app_config.xml" file within the ProgramData/BOINC/projects/milkyway.cs.rpi.edu_milkyway folder and right click on the filename and select "Notepad" to Open it, change the values and then save it.<app_config>
<app>
<name>milkyway</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>1.0</gpu_usage>
<cpu_usage>0.75</cpu_usage>
</gpu_versions>
</app>
</app_config>
Note that "max_concurrent" will limit the max number of concurrent tasks but if you are not using CPUs for MW, then this is fine...but in the future if you do use CPUs for this project you'll only get 2 tasks at once.
Then go back to BOINC Manager and click on "Options> Read config files" and then re-allow any MW tasks.
Your current setting of <gpu_usage>0.1</gpu_usage> is allowing 10 instances of the projects tasks to run on each GPU...that may be too much even for a high end GPU. So, using <gpu_usage>1.0</gpu_usage> for now will at least get you going.
Then go back to BOINC Manager and click on "Options> Read config files" and then re-allow any MW tasks.
If that works in terms of allowing tasks to flow, the next step is to change the <gpu_usage>1.0</gpu_usage> value to <gpu_usage>0.5</gpu_usage> - this will then allow 2 instances of the project tasks to run concurrently.
Then go back to BOINC Manager and click on "Options> Read config files" and then re-allow any MW tasks.
re: app_info.xml
Also: you may want an "app_info.xml" file within the MW project directory which contains the following code:
re: GPU settings<app_info>
<app>
<name>milkyway</name>
</app>
<app_version>
<app_name>milkyway</app_name>
<coproc>
<type>NVIDIA</type>
<count>1.0</count>
</coproc>
</app_version>
</app_info>
This time, suspend ALL crunching and close BOINC Manager down.
Within the ProgramData/BOINC directory is a file called "cc_config.xml". Once you find this, open it with Notepad and look within the file for the following line:
If it's there (exactly as shown above) then BOINC should use both GPUs for crunching. If the value is "0" then change it to "1".<use_all_gpus>1</use_all_gpus>
Then save the file, close Notepad and then resume BOINC Manager.
re: Deferring tasks
In simple terms, BOINC has a built-in mechanism (the client-side "scheduler") where it "knows" your crunching history and it assigns a "weighting" to each project. This then means that you are not in full control of which tasks are given "priority"...and it will stay that way until BOINC Manager "decides" that you have now crunched enough tasks of each project to give them all equal "weight".
https://boinc.berkeley.edu/wiki/REC-based_scheduler
The advice here is to try a couple of things:
1) Try setting ALL projects to "Won't get new tasks" and then RESET each of the projects listed with BOINC Manager - do this once you have NO tasks to crunch (otherwise it'll simply abort them all and if you are halfway through a task then any crunching would be wasted).
2) Set the cache to be a bit higher than you would normally use on the "troublesome project" (in this case MW) as the revised schedular (in v7.x of BOINC) needs about 10+ tasks to reset it's internal settings for the "REC" (Recent Estimated Credit).
Then only allow MW to download tasks and give it a couple of hours.
See if any of the above helps.
regards
Tim
PS: If any other forum members can correct any mistakes I've made please mention it and I'll update the above.