I uninstalled 7.0.28 and downgraded to 7.0.27 and the problem went away. 7.0.28 on Win7 64 bit works fine.
I can't reproduce the problem using 7.0.28 myself on Windows Vista 64-bit using two HD 6970 GPUs and Catalyst 12.2. All WUs crunching happily...
Quote:
It worked for a week or so now all mine are erroring out again after trying to update the drivers. Should have left it alone.
It seems that the BOINC client up-/downgrade didn't really have an impact right? If it all, this appears to be a driver related issue, which is in fact also much more likely...
Cheers,
Oliver
I only had the problem with 7.0.28 on XP 32 bit. When I rolled back to 7.0.27 the errors went away. When I tried to update driver from 12.1 to 12.4 the errors came back. Rolling back to driver 12.1 and the errors stopped again. I've had no problems on Win7 64 bit with 7.0.28. Hope this helps to clarify things pertaining to my situation. I saw others with the same error issues and thought what had worked for me might work for them.
i've just completed two wu's with another on the way, one of which has successfully validated. cpu use is about 20% with only one other core active fro crunching on core2duo (use max 75% of processors in system)
this can't be helpful, but what i did was:
uninstall 12.1 driver
reboot
install 12.4 driver
reboot
realize that OpenCL is not working - uninstall 12.4 driver
reboot
install 12.6(beta) driver
reboot
as soon as boinc starts, it immediately crashes with bsod
reboot into safe mode, uninstall 12.6(beta)
reboot
install 12.1 driver *again*
reboot
become totally surprised when BRP4 wu's crunch for more than 30 seconds
sleep
Why oh why did I "upgrade" to BOINC 7.0.28 and ATI 12.6 stable releases?
Now all my wu's crash. reverting to old drivers and BOINC does not help so far.
I am not happy.
You didn't... you upgraded to 7.0.27; all your fails are showing you as using 7.0.27
The error There was an error while deleting the color transform. (0x7e3) - exit code 2019 (0x7e3) can be caused by an unfinished installation, a partial file erasure, incorrect deletion of utilities or components. It could also be caused if your personal computer is contaminated with a virus or spyware infection or by an incorrect shutdown of the personal computer. Any of the above actions may well result in the removal or corruption of Windows system data files. This corrupted system file will give you absent and incorrectly linked documents and files needed for the accurate working of the application.
So how do you fix it?
Well, first off, if you really wanted to use 7.0.28, then actually install 7.0.28. It's now the recommended version, so you can just go to http://boinc.berkeley.edu/download.php and get it from there.
But you may also want to check your system for:
1. Viruses (scan with an up-to-date anti-virus scanner, include the BOINC Data directory in your scan, but only scan there while BOINC isn't running).
2. Malware. Get a good anti-malware scanner, like Superantispyware (http://www.superantispyware.com/) or Malwarebytes (http://www.malwarebytes.org/) and run with it after you updated it. Make sure it scans inside your BOINC Data directory, but only scan there while BOINC isn't running.
3. Damaged system files. Run sfc /scannow from a command line. You're likely required to be administrator for this, so use Start->All Programs->Accessories->right click on Command Prompt, choose "Run as administrator", acknowledge. Then just type in sfc /scannow and hit Enter. make sure you have your Windows DVD handy.
4. Damaged drivers. Follow this FAQ to get rid of the drivers completely, you can then install the newer drivers without problems.
the error first appeared after the 7.0.27->7.0.28 and amd 12.1->12.6 "upgrade," so i tried to roll back boinc first. then the gfx drivers.
tried sfc /scannow with no apparent effects.
now upon any ati install i get a warning message, but nothing in the install log that indicates a problem.
gpuz and driver caps both report functioning opencl, collatz crunches away happily.
no combination of uninstalling, driver sweep in safe mode, reinstalling v12.1/12.6 or 7.0.27/7.0.28 or anything else stops the errors. argh.
i'm really disappointed in myself for breaking a (finally) well-functioning einstein cruncher, but then again have no idea how i got it working in the first place, so hello again, collatz....
after in inordinate amount of fiddling i found that the ati driver version was stuck somehow at 12.3, despite uninstalls, device manager driver uninstall, driver sweep in safe mode, manual deletion of files, etc.
for now everything works. under winxp 32bit, sp3,
USE 12.1 DRIVERS ONLY
boinc 7.0.28 seems ok so far. i will report back with any success/failure.
This one is really mysterious, we get quite a lot of these errors, but from just a few hosts (< 10).
The hosts in question have different GPUs (Juniper, Cedar, Redwood, Cypress...all from the Evergreen family but that could be a coincidence) and different drivers (1.4.1646, 1.4.1332, 14.1016 ...). But all have the same OS: Win XP Professional x86, SP 3. That seems to be statistically significant, there are not that many XP Pro hosts left.
I'm afraid that doesn't solve your problem, but at least it excludes a few things.
RE: RE: I uninstalled
)
I only had the problem with 7.0.28 on XP 32 bit. When I rolled back to 7.0.27 the errors went away. When I tried to update driver from 12.1 to 12.4 the errors came back. Rolling back to driver 12.1 and the errors stopped again. I've had no problems on Win7 64 bit with 7.0.28. Hope this helps to clarify things pertaining to my situation. I saw others with the same error issues and thought what had worked for me might work for them.
i've just completed two wu's
)
i've just completed two wu's with another on the way, one of which has successfully validated. cpu use is about 20% with only one other core active fro crunching on core2duo (use max 75% of processors in system)
this can't be helpful, but what i did was:
uninstall 12.1 driver
reboot
install 12.4 driver
reboot
realize that OpenCL is not working - uninstall 12.4 driver
reboot
install 12.6(beta) driver
reboot
as soon as boinc starts, it immediately crashes with bsod
reboot into safe mode, uninstall 12.6(beta)
reboot
install 12.1 driver *again*
reboot
become totally surprised when BRP4 wu's crunch for more than 30 seconds
sleep
saints be praised!
Hmmm...all this Makels you
)
Hmmm...all this Makels you wonder how reliable the AMD driver installer and uninstalled) work.
Glad you got it working now, tho. Happy crunching
HB
Why oh why did I "upgrade" to
)
Why oh why did I "upgrade" to BOINC 7.0.28 and ATI 12.6 stable releases?
Now all my wu's crash. reverting to old drivers and BOINC does not help so far.
I am not happy.
RE: Why oh why did I
)
You didn't... you upgraded to 7.0.27; all your fails are showing you as using 7.0.27
The error There was an error while deleting the color transform. (0x7e3) - exit code 2019 (0x7e3) can be caused by an unfinished installation, a partial file erasure, incorrect deletion of utilities or components. It could also be caused if your personal computer is contaminated with a virus or spyware infection or by an incorrect shutdown of the personal computer. Any of the above actions may well result in the removal or corruption of Windows system data files. This corrupted system file will give you absent and incorrectly linked documents and files needed for the accurate working of the application.
So how do you fix it?
Well, first off, if you really wanted to use 7.0.28, then actually install 7.0.28. It's now the recommended version, so you can just go to http://boinc.berkeley.edu/download.php and get it from there.
But you may also want to check your system for:
1. Viruses (scan with an up-to-date anti-virus scanner, include the BOINC Data directory in your scan, but only scan there while BOINC isn't running).
2. Malware. Get a good anti-malware scanner, like Superantispyware (http://www.superantispyware.com/) or Malwarebytes (http://www.malwarebytes.org/) and run with it after you updated it. Make sure it scans inside your BOINC Data directory, but only scan there while BOINC isn't running.
3. Damaged system files. Run sfc /scannow from a command line. You're likely required to be administrator for this, so use Start->All Programs->Accessories->right click on Command Prompt, choose "Run as administrator", acknowledge. Then just type in sfc /scannow and hit Enter. make sure you have your Windows DVD handy.
4. Damaged drivers. Follow this FAQ to get rid of the drivers completely, you can then install the newer drivers without problems.
Oh my ... but doesn't Windows
)
Oh my ... but doesn't Windows allow to restore the system state to checkpoints that are created before each driver installation?
HBE
no windows restore on this
)
no windows restore on this box, so no dice.
the error first appeared after the 7.0.27->7.0.28 and amd 12.1->12.6 "upgrade," so i tried to roll back boinc first. then the gfx drivers.
tried sfc /scannow with no apparent effects.
now upon any ati install i get a warning message, but nothing in the install log that indicates a problem.
gpuz and driver caps both report functioning opencl, collatz crunches away happily.
no combination of uninstalling, driver sweep in safe mode, reinstalling v12.1/12.6 or 7.0.27/7.0.28 or anything else stops the errors. argh.
i'm really disappointed in myself for breaking a (finally) well-functioning einstein cruncher, but then again have no idea how i got it working in the first place, so hello again, collatz....
:(
after in inordinate amount of
)
after in inordinate amount of fiddling i found that the ati driver version was stuck somehow at 12.3, despite uninstalls, device manager driver uninstall, driver sweep in safe mode, manual deletion of files, etc.
for now everything works. under winxp 32bit, sp3,
USE 12.1 DRIVERS ONLY
boinc 7.0.28 seems ok so far. i will report back with any success/failure.
the saga
)
the saga continues....
after almost a week of perfect function after sorting out the 12.1 driver, the "color transform" error #2019 has returned.
nothing has changed driver-wise, i rebooted to clear memory to no avail.
anyone have ideas as to why the system would suddenly throw errors?
no OC, no temperature problems, etc.
thank you.
This one is really
)
This one is really mysterious, we get quite a lot of these errors, but from just a few hosts (< 10).
The hosts in question have different GPUs (Juniper, Cedar, Redwood, Cypress...all from the Evergreen family but that could be a coincidence) and different drivers (1.4.1646, 1.4.1332, 14.1016 ...). But all have the same OS: Win XP Professional x86, SP 3. That seems to be statistically significant, there are not that many XP Pro hosts left.
I'm afraid that doesn't solve your problem, but at least it excludes a few things.
Cheers
HB