Hi there! I'm seeing a lot of MW tasks come up with computation errors. Here is the top of my event log:

Sat 26 Oct 2013 16:13:41 WST | | Starting BOINC client version 7.0.27 for x86_64-pc-linux-gnu
Sat 26 Oct 2013 16:13:41 WST | | log flags: file_xfer, sched_ops, task
Sat 26 Oct 2013 16:13:41 WST | | Libraries: libcurl/7.26.0 OpenSSL/1.0.1e zlib/1.2.7 libidn/1.25 libssh2/1.4.2 librtmp/2.3
Sat 26 Oct 2013 16:13:41 WST | | Data directory: /var/lib/boinc-client
Sat 26 Oct 2013 16:13:41 WST | | Processor: 4 GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz [Family 6 Model 15 Stepping 11]
Sat 26 Oct 2013 16:13:41 WST | | Processor: 4.00 MB cache
Sat 26 Oct 2013 16:13:41 WST | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dtherm tpr_shadow vnmi flexpriority
Sat 26 Oct 2013 16:13:41 WST | | OS: Linux: 3.2.0-4-amd64
Sat 26 Oct 2013 16:13:41 WST | | Memory: 3.87 GB physical, 7.45 GB virtual
Sat 26 Oct 2013 16:13:41 WST | | Disk: 29.33 GB total, 17.73 GB free
Sat 26 Oct 2013 16:13:41 WST | | Local time is UTC +8 hours
Sat 26 Oct 2013 16:13:41 WST | | No usable GPUs found
Sat 26 Oct 2013 16:13:41 WST | | Config: GUI RPC allowed from:
Sat 26 Oct 2013 16:13:41 WST | | A new version of BOINC is available. <a href=http://boinc.berkeley.edu/download.php>Download it.</a>
Sat 26 Oct 2013 16:13:41 WST | Milkyway@Home | URL http://milkyway.cs.rpi.edu/milkyway/; Computer ID 526415; resource share 120
Sat 26 Oct 2013 16:13:41 WST | Einstein@Home | URL http://einstein.phys.uwm.edu/; Computer ID 7674445; resource share 60
Sat 26 Oct 2013 16:13:41 WST | DistrRTgen | URL http://boinc.freerainbowtables.com/distrrtgen/; Computer ID 75834; resource share 100
Sat 26 Oct 2013 16:13:41 WST | Poem@Home | URL http://boinc.fzk.de/poem/; Computer ID 164940; resource share 240
Sat 26 Oct 2013 16:13:41 WST | rosetta@home | URL http://boinc.bakerlab.org/rosetta/; Computer ID 1624264; resource share 150
Sat 26 Oct 2013 16:13:41 WST | | General prefs: from http://bam.boincstats.com/ (last modified 13-Dec-2012 02:08:24)
Sat 26 Oct 2013 16:13:41 WST | | Host location: none
Sat 26 Oct 2013 16:13:41 WST | | General prefs: using your defaults
Sat 26 Oct 2013 16:13:41 WST | | Reading preferences override file
Sat 26 Oct 2013 16:13:41 WST | | Preferences:
Sat 26 Oct 2013 16:13:41 WST | | max memory usage when active: 2380.60MB
Sat 26 Oct 2013 16:13:41 WST | | max memory usage when idle: 3570.89MB
Sat 26 Oct 2013 16:13:41 WST | | max disk usage: 11.73GB
Sat 26 Oct 2013 16:13:41 WST | | suspend work if non-BOINC CPU load exceeds 96 %
Sat 26 Oct 2013 16:13:41 WST | | (to change preferences, visit the web site of an attached project, or select Preferences in the Manager)
Sat 26 Oct 2013 16:13:41 WST | | Not using a proxy


Please note I've OC'd to 3.8 GHz, RAM @ 840 MHz. My 6770/5770 Xfire is not considered usable by BOINC :(

So, Einstein, rosetta & POEM all run fine, but their tasks only use one core each, while MW runs all 4.

I'm really not sure where to begin looking for the source of the computation errors, so any advice would be most appreciated!

The erroring tasks are all of type "Milkyway@Home Separation (Modified Fit) v1.28", and they have the error message:

../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_separation__modified_fit_1.28_x86_64-pc-linux-gnu: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by ../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_separation__modified_fit_1.28_x86_64-pc-linux-gnu)

As a Windows user, I'm not familiar with the mantra for obtaining and installing a missing Linux library, but I'm sure somebody here is.

Hi Richard, thanks very much for your prompt reply! I will do some searching when I get home regarding that library, but I'm afraid I may have a later version installed & not sure if I can safely roll back to an earlier version... Anyway, hopefully some googlefu may inform. Also, if anyone else can add something to point me in the right direction, I would be most grateful.

Hokai, apparently Debian 7 uses glibc 2.13 originally. I've found download links for newer glibc's, but should I go for 2.14, as required by MW, or 2.18, the latest? I'm thinking 2.14 seems safer, unless someone knows of a good reason to go with an even later version...

edit: also thought it worth mentioning that the 'separation' and 'nbody' tasks don't fail due to computation error, just 'modfit'.

Hokai, apparently Debian 7 uses glibc 2.13 originally. I've found download links for newer glibc's, but should I go for 2.14, as required by MW, or 2.18, the latest? I'm thinking 2.14 seems safer, unless someone knows of a good reason to go with an even later version...

edit: also thought it worth mentioning that the 'separation' and 'nbody' tasks don't fail due to computation error, just 'modfit'.

Let me start off by saying I am NOT a Linux guy...but I have seen LOTS of problems from Linux folks when using the wrong 'libraries'. I personally might go with the 2.14, but would download and save the 2.18 libraries for later on, or in case you switch to other projects that require them.

As for the units failing go to the News section of these message forums and read and post in the appropriate section there. The Admins are actively responding in there, not that they aren't here too, but that one is specifically for those problems while this one is more generic.

Thank you for the thread redirect! I'll make a new thread there if I have further issues.

I'm getting glibc 2.14 from here, all versions to 2.18 are currently available. Hopefully this gets the modfit tasks completing successfully!

Thank you for the thread redirect! I'll make a new thread there if I have further issues.

I'm getting glibc 2.14 from here, all versions to 2.18 are currently available. Hopefully this gets the modfit tasks completing successfully!

Modified Fit work units still require the use of a Double Precision capable card. Neither of your cards meet that requirement. The separation and n-body work units compute on your CPU.

Thank you for the thread redirect! I'll make a new thread there if I have further issues.

I'm getting glibc 2.14 from here, all versions to 2.18 are currently available. Hopefully this gets the modfit tasks completing successfully!

Modified Fit work units still require the use of a Double Precision capable card. Neither of your cards meet that requirement. The separation and n-body work units compute on your CPU.

At least some of the Modified Fit units run on cpu's, I have my gpu's elsewhere right now and am still finishing Modified Fit units just fine using just my cpu's.

Thank you for the thread redirect! I'll make a new thread there if I have further issues.

I'm getting glibc 2.14 from here, all versions to 2.18 are currently available. Hopefully this gets the modfit tasks completing successfully!

Modified Fit work units still require the use of a Double Precision capable card. Neither of your cards meet that requirement. The separation and n-body work units compute on your CPU.

At least some of the Modified Fit units run on cpu's, I have my gpu's elsewhere right now and am still finishing Modified Fit units just fine using just my cpu's.

And the OP's log shows:

Sat 26 Oct 2013 16:13:41 WST | | No usable GPUs found

He's a CPU-only cruncher.

I'm getting errors as well. I crossposted to anandtech's DC forum here's my post with the info. it's the milkyway@home 1.02 opencl units that are erroring for me on 2 different good cards and idk why. the same units are running just fine on my 7950s

http://forums.anandtech.com/showthread.php?p=35669593#post35669593

heres my log output from when i started to when i started and ended two tasks which errored out.

10/30/2013 5:49:12 AM Starting BOINC client version 6.10.58 for windows_x86_64
10/30/2013 5:49:12 AM log flags: file_xfer, sched_ops, task
10/30/2013 5:49:12 AM Libraries: libcurl/7.19.7 OpenSSL/0.9.8l zlib/1.2.3
10/30/2013 5:49:12 AM Data directory: C:\ProgramData\BOINC
10/30/2013 5:49:12 AM Running under account user
10/30/2013 5:49:12 AM Processor: 3 AuthenticAMD AMD Phenom(tm) II X3 720 Processor [Family 16 Model 4 Stepping 2]
10/30/2013 5:49:12 AM Processor: 512.00 KB cache
10/30/2013 5:49:12 AM Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 htt pni cx16 syscall nx lm svm sse4a osvw ibs skinit wdt page1gb rdtscp 3dnowext 3dnow
10/30/2013 5:49:12 AM OS: Microsoft Windows 7: x64 Edition, Service Pack 1, (06.01.7601.00)
10/30/2013 5:49:12 AM Memory: 3.98 GB physical, 7.97 GB virtual
10/30/2013 5:49:12 AM Disk: 59.90 GB total, 20.50 GB free
10/30/2013 5:49:12 AM Local time is UTC -7 hours
10/30/2013 5:49:13 AM ATI GPU 0: ATI unknown (CAL version 1.4.1848, 2048MB, 3379 GFLOPS peak)
10/30/2013 5:49:13 AM ATI GPU 1: ATI Radeon HD5800 series (Cypress) (CAL version 1.4.1848, 1024MB, 2816 GFLOPS peak)
10/30/2013 5:49:13 AM SETI@home Application uses missing NVIDIA GPU
10/30/2013 5:49:13 AM Milkyway@Home URL http://milkyway.cs.rpi.edu/milkyway/; Computer ID 222113; resource share 900
10/30/2013 5:49:13 AM SETI@home URL http://setiathome.berkeley.edu/; Computer ID 5553231; resource share 100
10/30/2013 5:49:13 AM No general preferences found - using BOINC defaults
10/30/2013 5:49:13 AM Reading preferences override file
10/30/2013 5:49:13 AM Preferences:
10/30/2013 5:49:13 AM max memory usage when active: 2039.88MB
10/30/2013 5:49:13 AM max memory usage when idle: 3671.78MB
10/30/2013 5:49:13 AM max disk usage: 10.00GB
10/30/2013 5:49:13 AM suspend work if non-BOINC CPU load exceeds 25 %
10/30/2013 5:49:13 AM (to change preferences, visit the web site of an attached project, or select Preferences in the Manager)
10/30/2013 5:49:13 AM Using proxy info from GUI
10/30/2013 5:49:13 AM Not using a proxy
10/30/2013 5:49:13 AM SETI@home Restarting task 14oc08ad.14450.13978.3.12.178_2 using setiathome_v7 version 700
10/30/2013 5:49:13 AM SETI@home Restarting task 06mr09ae.10741.1708.3.12.250_0 using setiathome_v7 version 700
10/30/2013 5:49:13 AM Milkyway@Home Restarting task ps_modfit_15_3s_bpl_128wrap_2_1382698503_786527_0 using milkyway_separation__modified_fit version 128
10/30/2013 5:49:13 AM Milkyway@Home Restarting task ps_modfit_15_3s_bpl_128wrap_2_1382698503_786526_0 using milkyway_separation__modified_fit version 128
10/30/2013 5:49:13 AM Milkyway@Home Sending scheduler request: To fetch work.
10/30/2013 5:49:13 AM Milkyway@Home Reporting 2 completed tasks, requesting new tasks for GPU
10/30/2013 5:49:14 AM Milkyway@Home Scheduler request completed: got 2 new tasks
10/30/2013 5:49:14 AM Milkyway@Home General prefs: from Milkyway@Home (last modified 29-Oct-2013 08:46:08)
10/30/2013 5:49:14 AM Milkyway@Home Host location: none
10/30/2013 5:49:14 AM Milkyway@Home General prefs: using your defaults
10/30/2013 5:49:14 AM Reading preferences override file
10/30/2013 5:49:14 AM Preferences:
10/30/2013 5:49:14 AM max memory usage when active: 2039.88MB
10/30/2013 5:49:14 AM max memory usage when idle: 3671.78MB
10/30/2013 5:49:14 AM max disk usage: 10.00GB
10/30/2013 5:49:14 AM suspend work if non-BOINC CPU load exceeds 25 %
10/30/2013 5:49:14 AM (to change preferences, visit the web site of an attached project, or select Preferences in the Manager)
10/30/2013 5:50:20 AM Milkyway@Home Sending scheduler request: To fetch work.
10/30/2013 5:50:20 AM Milkyway@Home Requesting new tasks for GPU
10/30/2013 5:50:21 AM Milkyway@Home Scheduler request completed: got 0 new tasks
10/30/2013 5:50:21 AM Milkyway@Home Message from server: Project has no tasks available
10/30/2013 5:51:26 AM Milkyway@Home Sending scheduler request: To fetch work.
10/30/2013 5:51:26 AM Milkyway@Home Requesting new tasks for GPU
10/30/2013 5:51:28 AM Milkyway@Home Scheduler request completed: got 0 new tasks
10/30/2013 5:51:28 AM Milkyway@Home Message from server: Project has no tasks available
10/30/2013 5:51:34 AM Milkyway@Home task ps_modfit_15_3s_bpl_128wrap_2_1382698503_786527_0 suspended by user
10/30/2013 5:51:34 AM Milkyway@Home task ps_modfit_15_3s_bpl_128wrap_2_1382698503_786526_0 suspended by user
10/30/2013 5:51:34 AM Milkyway@Home task ps_nbody_10_18_dark_1382698503_174922_0 suspended by user
10/30/2013 5:51:34 AM Milkyway@Home task ps_nbody_10_18_dark_1382698503_174921_0 suspended by user
10/30/2013 5:51:34 AM Milkyway@Home task ps_nbody_10_18_dark_1382698503_174919_0 suspended by user
10/30/2013 5:51:34 AM Milkyway@Home task de_nbody_10_18_dark_1382698503_174917_0 suspended by user
10/30/2013 5:51:34 AM Milkyway@Home task de_nbody_10_18_dark_1382698503_174916_0 suspended by user
10/30/2013 5:51:34 AM Milkyway@Home task de_nbody_10_18_dark_1382698503_174915_0 suspended by user
10/30/2013 5:51:34 AM Milkyway@Home task de_nbody_10_18_dark_1382698503_174912_0 suspended by user
10/30/2013 5:51:34 AM Milkyway@Home task de_nbody_10_18_dark_1382698503_174902_0 suspended by user
10/30/2013 5:51:34 AM Milkyway@Home task ps_modfit_15_3s_bpl_128wrap_2_1382698503_786525_0 suspended by user
10/30/2013 5:51:34 AM Milkyway@Home task ps_modfit_15_3s_bpl_128wrap_2_1382698503_751856_3 suspended by user
10/30/2013 5:51:36 AM Milkyway@Home Starting de_separation_DR8_84_Rev_4_1_1382698502_1674473_1
10/30/2013 5:51:36 AM Milkyway@Home Starting task de_separation_DR8_84_Rev_4_1_1382698502_1674473_1 using milkyway version 102
10/30/2013 5:51:36 AM Milkyway@Home Starting de_separation_DR8_84_Rev_4_1_1382698502_1655610_2
10/30/2013 5:51:36 AM Milkyway@Home Starting task de_separation_DR8_84_Rev_4_1_1382698502_1655610_2 using milkyway version 102
10/30/2013 5:51:38 AM SETI@home Sending scheduler request: To fetch work.
10/30/2013 5:51:38 AM SETI@home Reporting 1 completed tasks, requesting new tasks for CPU
10/30/2013 5:51:40 AM SETI@home Scheduler request completed: got 1 new tasks
10/30/2013 5:51:42 AM SETI@home Started download of 22mr08ad.22905.3753.9.12.2
10/30/2013 5:51:44 AM SETI@home Finished download of 22mr08ad.22905.3753.9.12.2
10/30/2013 5:51:44 AM Milkyway@Home Computation for task de_separation_DR8_84_Rev_4_1_1382698502_1674473_1 finished
10/30/2013 5:51:44 AM Milkyway@Home Starting de_modfit_16_3s_128wrap_1_1382698503_778990_3
10/30/2013 5:51:44 AM Milkyway@Home Starting task de_modfit_16_3s_128wrap_1_1382698503_778990_3 using milkyway_separation__modified_fit version 128
10/30/2013 5:51:45 AM Milkyway@Home Computation for task de_separation_DR8_84_Rev_4_1_1382698502_1655610_2 finished
10/30/2013 5:51:45 AM Milkyway@Home Starting de_modfit_15_3s_bpl_128wrap_2_1382698503_746194_2
10/30/2013 5:51:45 AM Milkyway@Home Starting task de_modfit_15_3s_bpl_128wrap_2_1382698503_746194_2 using milkyway_separation__modified_fit version 128
10/30/2013 5:52:20 AM Milkyway@Home task ps_modfit_15_3s_bpl_128wrap_2_1382698503_786527_0 resumed by user
10/30/2013 5:52:20 AM Milkyway@Home task ps_modfit_15_3s_bpl_128wrap_2_1382698503_786526_0 resumed by user
10/30/2013 5:52:20 AM Milkyway@Home task ps_modfit_15_3s_bpl_128wrap_2_1382698503_786525_0 resumed by user
10/30/2013 5:52:20 AM Milkyway@Home task ps_nbody_10_18_dark_1382698503_174922_0 resumed by user
10/30/2013 5:52:20 AM Milkyway@Home task ps_nbody_10_18_dark_1382698503_174921_0 resumed by user
10/30/2013 5:52:20 AM Milkyway@Home task ps_nbody_10_18_dark_1382698503_174919_0 resumed by user
10/30/2013 5:52:20 AM Milkyway@Home task de_nbody_10_18_dark_1382698503_174917_0 resumed by user
10/30/2013 5:52:20 AM Milkyway@Home task de_nbody_10_18_dark_1382698503_174916_0 resumed by user
10/30/2013 5:52:20 AM Milkyway@Home task de_nbody_10_18_dark_1382698503_174915_0 resumed by user
10/30/2013 5:52:20 AM Milkyway@Home task de_nbody_10_18_dark_1382698503_174912_0 resumed by user
10/30/2013 5:52:20 AM Milkyway@Home task de_nbody_10_18_dark_1382698503_174902_0 resumed by user
10/30/2013 5:52:20 AM Milkyway@Home task ps_modfit_15_3s_bpl_128wrap_2_1382698503_751856_3 resumed by user
10/30/2013 5:52:21 AM Milkyway@Home Restarting task ps_modfit_15_3s_bpl_128wrap_2_1382698503_786527_0 using milkyway_separation__modified_fit version 128
10/30/2013 5:52:21 AM Milkyway@Home Restarting task ps_modfit_15_3s_bpl_128wrap_2_1382698503_786526_0 using milkyway_separation__modified_fit version 128

At least some of the Modified Fit units run on cpu's, I have my gpu's elsewhere right now and am still finishing Modified Fit units just fine using just my cpu's.

Good to know, I stand corrected. Thanks

I'm getting errors as well. I crossposted to anandtech's DC forum here's my post with the info. it's the milkyway@home 1.02 opencl units that are erroring for me on 2 different good cards and idk why. the same units are running just fine on my 7950s

If you notice the 7950 is running Boinc 7.0.64 while one of the others is running 6.10.58, try upgrading and see if that fixes it. Yes some projects take advantage of the newer Boinc programming while other projects do not, I don't know if MW does or not, but it's worth a try unless you can't upgrade for another reason.

One other thing one of your pc's, the same one with the older version of Boinc, says this in your listing showing your gpu's:
[2] AMD ATI unknown (2048MB) driver: 1.4.1848

Are you using the brand new R series gpu's? If so you will definitely need a much newer version of Boinc, ie the latest Beta, for Boinc to figure out what kind of card that is.

no i am using a 6970 and a 5870 in the other rig. i just updated to the latest version of BOINC and am still getting errors, and additionally the 5870 is no longer being issued work units. I ran driversweeper and fresh installed a few different drivers as well and no dice. the rig will soon have a second 5870 added to it as well once i retrieve it from a friends.

edit: upon a quick check, it seems that updating my client actually has disallowed me from running my 6970 and 5870 congruently. the updated client seems to have disabled the card in a computing capacity arbitrarily without any discourse for myself to go about re-enabling my 5870. reverting back to the old version from the installer i still had enabled me to start using the cards simultaneously again.

Suddenly, all errors on an AMD system with pair of gtx460
http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=285405&offset=0&show_names=0&state=0&appid=

other systems are intel cpu and no errors.

no i am using a 6970 and a 5870 in the other rig. i just updated to the latest version of BOINC and am still getting errors, and additionally the 5870 is no longer being issued work units. I ran driversweeper and fresh installed a few different drivers as well and no dice. the rig will soon have a second 5870 added to it as well once i retrieve it from a friends.

edit: upon a quick check, it seems that updating my client actually has disallowed me from running my 6970 and 5870 congruently. the updated client seems to have disabled the card in a computing capacity arbitrarily without any discourse for myself to go about re-enabling my 5870. reverting back to the old version from the installer i still had enabled me to start using the cards simultaneously again.

Next time try rebooting the pc but with a 2nd monitor plugged into the 2nd card, Windows has a bad habit of 'saving resources' by turning off things it thinks you don't need, such as a gpu with no monitor attached. You can also use a 'dummy plug' you can easily make yourself with directions from here:
http://www.overclock.net/t/384733/the-30-second-dummy-plug

The 2nd monitor only has to be connected during the bootup process, not full time, so an extension cable from a 2nd monitor will work just fine.

no i am using a 6970 and a 5870 in the other rig. i just updated to the latest version of BOINC and am still getting errors, and additionally the 5870 is no longer being issued work units. I ran driversweeper and fresh installed a few different drivers as well and no dice. the rig will soon have a second 5870 added to it as well once i retrieve it from a friends.

edit: upon a quick check, it seems that updating my client actually has disallowed me from running my 6970 and 5870 congruently. the updated client seems to have disabled the card in a computing capacity arbitrarily without any discourse for myself to go about re-enabling my 5870. reverting back to the old version from the installer i still had enabled me to start using the cards simultaneously again.

Next time try rebooting the pc but with a 2nd monitor plugged into the 2nd card, Windows has a bad habit of 'saving resources' by turning off things it thinks you don't need, such as a gpu with no monitor attached. You can also use a 'dummy plug' you can easily make yourself with directions from here:
http://www.overclock.net/t/384733/the-30-second-dummy-plug

The 2nd monitor only has to be connected during the bootup process, not full time, so an extension cable from a 2nd monitor will work just fine.

Even a second cable from the same monitor - most good LCDs these days will have at least two of VGA, DVI, HDMI - and quite possibly a spare VGA (blue plugs) and DVI (while plugs) cable as well. Video cards often come with DVI-to-VGA adapters - with a pocketful of spares like that, you can fake up any number of connections.

ill try this if a fix is found for the errors. right now updating the client to that version is pointless anyways because doing so made my 6970 instantly fail all GPU work units anyways making updating a moot point. At least with the old version i can run both congruently and run some of the GPU work units. And the card isn't technically disabled, its showing up as enabled in device manager and in drivers the same with both versions. The version switch was also done without a reboot (i rebooted to see if the card would start getting them, but when i switched back to the old version it instantly started working so i didn't bother rebooting again, making the first reboot redundant), telling me the card was detecting fine to begin with, BOINC was just disabling it as a compute card

no i am using a 6970 and a 5870 in the other rig. i just updated to the latest version of BOINC and am still getting errors, and additionally the 5870 is no longer being issued work units. I ran driversweeper and fresh installed a few different drivers as well and no dice. the rig will soon have a second 5870 added to it as well once i retrieve it from a friends.

edit: upon a quick check, it seems that updating my client actually has disallowed me from running my 6970 and 5870 congruently. the updated client seems to have disabled the card in a computing capacity arbitrarily without any discourse for myself to go about re-enabling my 5870. reverting back to the old version from the installer i still had enabled me to start using the cards simultaneously again.

Next time try rebooting the pc but with a 2nd monitor plugged into the 2nd card, Windows has a bad habit of 'saving resources' by turning off things it thinks you don't need, such as a gpu with no monitor attached. You can also use a 'dummy plug' you can easily make yourself with directions from here:
http://www.overclock.net/t/384733/the-30-second-dummy-plug

The 2nd monitor only has to be connected during the bootup process, not full time, so an extension cable from a 2nd monitor will work just fine.

Even a second cable from the same monitor - most good LCDs these days will have at least two of VGA, DVI, HDMI - and quite possibly a spare VGA (blue plugs) and DVI (while plugs) cable as well. Video cards often come with DVI-to-VGA adapters - with a pocketful of spares like that, you can fake up any number of connections.

Hey it is only 7AM, it is too early to be learning my one new thing today!! Thanks I did not know that!!!

ill try this if a fix is found for the errors. right now updating the client to that version is pointless anyways because doing so made my 6970 instantly fail all GPU work units anyways making updating a moot point. At least with the old version i can run both congruently and run some of the GPU work units. And the card isn't technically disabled, its showing up as enabled in device manager and in drivers the same with both versions. The version switch was also done without a reboot (i rebooted to see if the card would start getting them, but when i switched back to the old version it instantly started working so i didn't bother rebooting again, making the first reboot redundant), telling me the card was detecting fine to begin with, BOINC was just disabling it as a compute card

Of course they failed, they were downloaded under an older version of Boinc and since you are now using a newer version any existing units WILL ALWAYS fail, this is just one of the many security checks Boinc has. Most projects just resend you the same units back again though under the new version. That's one reason you either just accept that it's going to happen, or set the pc to no new tasks prior to updating.

ill try this if a fix is found for the errors. right now updating the client to that version is pointless anyways because doing so made my 6970 instantly fail all GPU work units anyways making updating a moot point. At least with the old version i can run both congruently and run some of the GPU work units. And the card isn't technically disabled, its showing up as enabled in device manager and in drivers the same with both versions. The version switch was also done without a reboot (i rebooted to see if the card would start getting them, but when i switched back to the old version it instantly started working so i didn't bother rebooting again, making the first reboot redundant), telling me the card was detecting fine to begin with, BOINC was just disabling it as a compute card

Of course they failed, they were downloaded under an older version of Boinc and since you are now using a newer version any existing units WILL ALWAYS fail, this is just one of the many security checks Boinc has. Most projects just resend you the same units back again though under the new version. That's one reason you either just accept that it's going to happen, or set the pc to no new tasks prior to updating.

Sorry, that's one thing you need to UN-learn today.

It shouldn't matter one jot which version of BOINC you use, either to download or to run tasks. And for the vast majority of projects, it doesn't. I test pretty much every version of BOINC that's compiled, and change them at will - I cycled through v7.2.23/v7.2.25/v7.2.26 several times in one day, earlier this week, to diagnose a BOINC installer problem. No tasks were hurt in the course of that test, and no security violations were triggered.

Now, that's a generalisation, and a statement of policy. There are certain boundaries that shouldn't be crossed, because there were major design changes which introduced incompatibilities - downgrading from BOINC v7 to BOINC v6 (any versions) is a case in point. But that would show itself by abandoning tasks on restart, not erroring them when they attempt to run.

Now, it's perfectly possible that some applications or tasks may have difficulties with an upgrade or downgrade - though I don't, in all honesty, know how that could come about. If so, the project concerned has problems, either with its programming, or with its interfacing with the BOINC infrastructure. That may be the case here - it certainly happened in the case of the early testing of N-Body, which is what drew me here - but I'm not in a position to test on ATI hardware.