Color Profile Issue Vista x64

Hi..
I’m having the a problem but on Windows Vista Business X64. I installed an Acer LCD (X223w Q) yesterday for desktop expansion and updated its drivers automatically it installed the device drivers from God knows where and  since then the Photoshop has gone all crazy it always asks to select color profile when opening the file. Claiming that "The RGB document "try.bmp" has a file format that doesn't support embedded color profiles". It does the same for everything.
I’ve tried your solution from the following link
http://lalor.net/index.php/2009/02/photoshop-colour-management-reset/
but the the OS doesn’t allow me to remove any color profile claiming that its system profile and can’t be removed. I’ve un-installed LCD drivers but it color profile Acer X223W is still showing in the advanced panel in ICC profile along with sRGB IEC61966-2.1 both have a file name and a class name 'display' written against them..
I've uninstalled and reinstalled graphics drivers as well as photoshop but nothing seems to be working. No matter what profile I select the photoshop opens it in a dark tint. How ever when I press Ctrl + Y to switch to Proof Colors its gets back to normal colors (My proof settings are set to Monitor RGB)
Following are my System Details
Machine : Lenovo 3000 n200
OS: Windows Vista Business x64
Graphic Card : Nvidia Geforce Go 7300
I've never have had this problem before the installation of drivers for that LCD. And after searching the internet for over a day its driving me crazy
Please review the attachment for details.
I’d really appreciate if anyone could look into this issue..

Well, why not simply set the monitor to sRGB again? The location of the physical files is C:\Windows\System32\Drivers\Printers\Color. You can delete the profile from there. Also reset PS' color management completely (Edit --> Color). I'm sure the warning has its reasons because based on your (wrong) monitor profile PS thinks it needs to compensate based on your CM policies...
Mylenium

Similar Messages

  • IPhoto fix that worked for me (Coregraphics & Adobe Color Profiles issues)

    Ok, I posted a few days back in reference to getting help with my iPhoto. I do apologize on the fact this is quite the long post but maybe it will be easy to understand for those who are like me and not all that computer literate. I searched all the discussions and used all the different advice from different people but had no luck. I was able to FINALLY get iPhoto up and running again last night after doing just a few simple things. Please note that this may not work for everyone. Also please note that I AM NOT an expert in dealing with computers and working with computers. It's just that my ADD kicks in when something needs fixing and I won't stop till its finished. Below are a few lines from the crash report that I was getting each time I attempted to open iPhoto from my Macbook Pro Late 2011 running 10.8.3.
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGBUS)
    Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000024
      VM Regions Near 0x24:
    --> __PAGEZERO             0000000000000000-0000000000001000 [    4K] ---/--- SM=NUL  /Applications/iPhoto.app/Contents/MacOS/iPhoto
        VM_ALLOCATE            0000000000001000-0000000000055000 [  336K] ---/--- SM=NUL 
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   com.apple.CoreGraphics                  0x9678ec6c color_space_create_adobe_rgb_1998 + 28
    1   com.apple.CoreGraphics                  0x9666dd70 CGColorSpaceCreateAdobeRGB1998 + 32
    2   com.apple.CoreGraphics                  0x9642b46b CGColorSpaceCreateWithName + 652
    3   com.apple.geode                         0x01079d4a +[DGColorSpace initialize] + 1018
    4   libobjc.A.dylib                         0x90267600 _class_initialize + 305
    5   libobjc.A.dylib                         0x902674c8 prepareForMethodLookup + 78
    6   libobjc.A.dylib                         0x90267337 lookUpMethod + 81
    7   libobjc.A.dylib                         0x902672e1 _class_lookupMethodAndLoadCache3 + 47
    8   libobjc.A.dylib                         0x90266ac1 objc_msgSend + 81
    9   com.apple.geode                         0x010798a0 +[DGContextMgr newBitmapContextCached:accelerated:] + 61
    10  com.apple.geode                         0x0107985e +[DGContextMgr newBitmapContextWithAcceleration:] + 49
    11  com.apple.RedRock                       0x02647bf6 -[Godot loadGeode] + 1261
    12  com.apple.RedRock                       0x026448a8 -[Godot init] + 1571
    13  com.apple.RedRock                       0x026437d2 +[Godot initGodotApp] + 108
    14  com.apple.iPhoto                        0x00083be8 0x55000 + 191464
    15  com.apple.iPhoto                        0x0008236b 0x55000 + 185195
    16  com.apple.Foundation                    0x9a3bc4cf __NSFireDelayedPerform + 413
    17  com.apple.CoreFoundation                0x95ed1416 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 22
    18  com.apple.CoreFoundation                0x95ed0db5 __CFRunLoopDoTimer + 709
    19  com.apple.CoreFoundation                0x95eb5bc2 __CFRunLoopRun + 1842
    20  com.apple.CoreFoundation                0x95eb502a CFRunLoopRunSpecific + 378
    21  com.apple.CoreFoundation                0x95eb4e9b CFRunLoopRunInMode + 123
    22  com.apple.HIToolbox                     0x9052af5a RunCurrentEventLoopInMode + 242
    23  com.apple.HIToolbox                     0x9052abf5 ReceiveNextEventCommon + 162
    24  com.apple.HIToolbox                     0x9052ab44 BlockUntilNextEventMatchingListInMode + 88
    25  com.apple.AppKit                        0x923c39aa _DPSNextEvent + 724
    26  com.apple.AppKit                        0x923c31dc -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119
    27  com.apple.AppKit                        0x923b963c -[NSApplication run] + 855
    28  com.apple.AppKit                        0x9235c666 NSApplicationMain + 1053
    29  com.apple.iPhoto                        0x00064c99 0x55000 + 64665
    30  com.apple.iPhoto                        0x000642e5 0x55000 + 62181
    -Run and attempt to repair any Color Profiles that may need to be fixed. There were 4 that could not be fixed for me. Locate these profiles and move them to your desktop (Note: I was still able to open and use all applications in my Adobe CS6 Master Collection after moving these profiles but you may want to check just to be sure if you are using Adobe).
    -Even though I had done this many times, run the Disk Utility App in your Utilities Profile and Verify and Repair any permission needed (For me, I had none at this time that needed to be repaired).
    -Next, I did an Apple Hardware Test. For me and the model Macbook Pro I am using, I had to restart my computer and when the screen went black for me at restart about the time the start up sound is about to come on, I pressed ALT-D. On some models you just have to press D. I did disconnect everything prior to doing this except the power cord and the Internet. I did a full AHT test that took about an hour or so. If you get an error code, be sure and right it down whereas your issue may be something different than mine and this will not apply to you. There were no problems from the test and then restarted the computer.
    -At restart I decided to get into the OS X Recovery by pressing Command-R to either start from scratch or find some other way to fix the issue because I was tired of racking my brain on this and was about to throw the computer in to the wall.
    http://support.apple.com/kb/HT4718 For help or questions on the OS X Recovery Process
    -Once in the OS X Recovery from the Mac OS X Utilities Pane, I selected reinstall and then I selected my current Hard Drive. Luckily by doing this (not that I was aware or anything, but none of my files or folders were deleted and it only reinstalled Mountain Lion and whatever else it needed)
    -This process took about an hour and once finished, I restarted my computer
    -I logged back in to my account but did not attempt iPhoto at this time. Instead I immediately checked to make sure that 10.8.3 was what was reinstalled back on my Mac. I then checked for Software Updates which I had a few and installed these updates.
    -I then went back to the Disk Utilities App from my Utilities folder and Verified the Disk and Disk Permission. To my surprise, many of the files that were in the iPhoto crash thread (posted above) were now showing up as needing to be repaired. I repaired what needed to be repaired.
    -I verified all my Color Profiles to make sure none were showing up again (which there were none that needed to be repaired)
    -I did a check check of some Adobe CS6 Apps just to verify they were opening and working correctly
    -I restarted my Mac (Once again) and logged back in. I opened up iPhoto and everything worked and is working PERFECTLY. I then re-connected my printers and my Time Machine and performed a back up before importing photos back in to iPhoto. I DO WISH NOW THOUGH THAT I HADN'T DELETED AND RE-INSTALLED IPHOTO but it is nice being able to start over and organize iPhoto a little better than before.
    I am sorry this is such a long post but for people like me who are not professionals in the computer department, sometimes it's good to "dumb" things done so that us "average joes" can understand a little better. Hopefully this will work for those who are having issues like mine. Thanks for all the help from everyone from my previous posts.

    Tom:
    To help prevent loss like you experienced see the tip at the end of my signature.
    Do you Twango?
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
    I've written an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

  • Intel-Mac Color Profile Issues

    Afternoon Folks,
    Just picked up my 15" MPB this past Friday. My iMac had packed it in, so went for broke and got a 15", with 2GB of RAM and the 256MB video.
    So..besides the Type-1 font problem, I have a HUGE problem with Color Profiles.
    In Adobe Photoshop CS my RGB values are not being displayed properly. I am using the IEC-61966-2.1 profile in Photoshop, CorelDraw, Dreamweaver and Ilustrator. Images that worked on my old Mac are being mucked with somehow.
    Example. I have a bunch of vectors files for a client that use the following values:
    RGB = 41-56-91
    CMYK = 91-80-39-31
    Hex = 29385B
    (you can view thsi color on brooksbrothers.com)
    but if I touch the old files with any app on the new system, the values get changed. I take an existing CDR file, open it in CorelDraw and export to JPG, and the value is change on the blue. I take an existing jpg, open it with Photoshop, close the file, and re-open it and the value is changed.
    I can't afford to re-do all the colors for this client, as they really like this shade of blue. Is anyone else dealing with this nightmare?
    Anyone else think Apple jumped the gun on the chip-set switch?
    Sincerely,
    Scott

    FYI, I haven't done any major profile tweaks or anything, just running on default. But I have noticed the color profile of the general OS is considerably warmer on my screen, thus affecting warm colors like yellows, oranges, and greens for me.
    I colored an illustration on my MBP in Flash, and when I checked it on my G4 and other monitors, a lot of my warms were hot and not so great.
    Not sure why this is, but I am a bit concerned, as color is very important to my work. This is my first laptop, but I expected color issues on laptops to be somewhat resolved at this point. In many ways, I prefer the way colors look on my MBP, so maybe the world will just change for me

  • Quicktime/iTunes Full Screen Color Profile Issues?

    I'm running Yosemite now, but this has been an issue long before I upgraded from Mavericks as well.  The default color calibration in OSX is overly bright and blown out on my monitor, so I have a custom calibration set up and in use on my Mac Mini. The profile I created looks great for general viewing, movies or anything else I want to do.
    However...there seems to be an issue with Quicktime in either the app itself or when playing a movie from my iTunes library. If I play a movie in a window there are no issues, but the problem comes when I play a video in full screen mode. The color calibration looks just fine UNTIL the play controls automatically disappear from the screen. That's when it seems to go back to the default color profile that's blown out and muddy looking. Move the mouse so the controls come back up, color profile goes right back to the one I have set....until they go off the screen again, when the default profile is back.
    Anyone else experiencing this and maybe found a workaround or way to fix it?  I've found a couple mentions of it on the web in forums, but no answers or even replies were ever given.

    Me too and it's very annoying. Exactly the same symptoms of the colour changing when the fullscreen controls disappear.
    I've used a colormunki to create a custom profile for my monitor for photoshop use. Has everyone else done something similar?
    I created the profile before Mavericks & Yosemite updates so I might try deleting it and creating a new one to see if that helps.

  • Color Profile issues with CS5

    I´ve been having some issues with the color profiles since I´ve installed the CS5 on my laptop (Windows 7 ultimate).
    To describe what I mean please see the images:
    Every time I open Photoshop or Illustrator this message apppears:
    so I hit ok, but I´m not sure if this affect the artworks that will be printed, I use the CMYK Mode but the colors does not match very well.
    Hope you can help me
    Thanks in advance,
    Diana.

    You have some serious reading up on color management to do... I strongly suggest you sift through the Illustrator/InDesign/Photoshop forums and the web in general. Short version: Using RGB profiles makes no sense whatsoever if you are working in CMYK but in reverse working in CMYK does not make sense if you are only printing at home/ displaying graphics on your own computer. Anyway, this is an infinitely complex topic, so realyl, do some reading and then ask more specific questions in the program-centric forums...
    Mylenium

  • Color profile issue

    I´ve color calibrated my macbook pro with Supercal app, which is far superior than Apple built in color profiler. But now I'm having problems during rendering in final cut pro x 10.0.6. It makes a random bug, flipping or rotating frames, and crossing colors. I've tried deleting renders files. Same issue. I've found a similar post about final cut not being able to deal with custom color profiles. I´ve been using also an x-rite profile with no problem, but i really don´t like the profile. It is good to show more tonal values on shadows and highlights, but reds appear very magenta.
    Anyone with this problem? Any workaround?
    Thanks,
    Pablo

    The renders are Ok if I use the default profile. The problem is that I would like to use the calibrated one to color grade my videos. The default color profile is not so good (and my macbook now has a year old). What I´m doing now is grade with the calibrated profile, then erase all the renders, change to the default profile, and render again.
    But it´s a pain to do it like that.

  • Color Profile issues / Colors darken when saving as png/jpg

    Hello Adobe Community!
    I got a problem with the color settings / profiles in Photoshop and I hope someone can help me.
    For the record: I Am working an a PC (Windows 7) with Photoshop CS4.
    I work on a digital painting in Photoshop and to keep track of my progression I save frequently as pngs.
    I noticed that the colors don't match and are much darker as you can see in the picture below:
    I tried the things suggested in many forums, checking and converting my color profiles. For many that seemed to fix it, but not for me.
    In the source space you can see the Profile I am using.
    Many suggested when saving for web and devices one should untick the "convert to sRGB" checkbox, but for me, that didn't change anything and the colors were still messed up.
    I hope someone has a solution for this problem. After trying so many things I'm getting quite desperate!

    always CONVERT to sRGB (if not already there) when saving for the web and unmanages apps
    there are both pros and cons for tagging/untagging images for the web
    the slight darkening and saturation difference i see in in your posted image is expected between managed and unmanaged apps, but you didn't embed a profile so it is my guess what you are seeing there
    to duplicate the phenomenon, in Photoshop, open your tagged sRGB image, then
    View> Proof Setup: Monitor RGB (be sure to turn it back off)
    the shift you see there is the difference between sRGB and your monitor profile (Photoshop is in essence stripping the sRGB profile and sending the RGB numbers straight through to the monitor with no changes)
    as you probably know, Photoshop normally transforms (changes) the source colors to the monitor profile...

  • Lightroom 4.4 export color profile issues

    Hello,
    My problem is that when I export JPG's from Lightroom (100% / sRGB / sharpen for screen) the picture seems to lack contrast and the colors look less saturated (Looks like this everywhere, including Windows Preview, Firefox, Photoshop..). If I select Soft Proofing and sRGB, the colors look correct.
    Also if I take a screen capture and save it as JPG, the colors look similar to my preview in Lightroom.
    I have tried to export in sRGB, Adobe RGB and ProPhoto RGB color profiles but none of them looks the same as LR preview.
    Thanks

    This looks like Lightroom is choking on a bad monitor profile, especially if Lightroom and Photoshop are not in agreement (because they should be, always - but it can happen that they react differently to a bad profile).
    Is your monitor calibrated/profiled? What calibrator? Or if not, are you using a monitor profile provided by the monitor manufacturer? (they're sometimes defective).
    Export to Adobe RGB and open it in Photoshop. Put Ps and Lr side by side and make a screenshot of that. If they're different, I bet it's the monitor profile. The reason for testing this with an Adobe RGB export (and not sRGB) is to rule out any normal gamut clipping.

  • Monitor/Photoshop/Color profile issue

    heyz! yesterday i changed my monitor profile from srgb to prophoto rgb while viewing some images in photoshop. they displayed the same colors after the change, but today i opened photoshop again and with the same images and all the colors were dissaturated. ive done some search and found the probable cause is a ”broken” monitor profile, or one that doesnt match its capabilities. i changed to adobe rgb, reopened photoshop and that image seems to look right, but i think still not how i remember it from yesterday. my question is: is this really the problem and is there a way i can find whats the largest color space my monitor can display without reading its tech book?( cos its long lost)
    thanks!
    ps: when changing the monitor profile to prophoto i also played with color settings in ps and set it to prophoto/adobe rgb, but that image has an embedded profile and i chose preserve embedded profile when opening it, so i dont think thats the problem.

    If there's a question here it's pretty vague. So, here's how it works, in general terms:
    A monitor profile is a description of the monitor's native color space. And as such it also defines the gamut of your monitor. But the profile doesn't actually "handle" anything, it doesn't do anything - it's just a description.
    Photoshop's color management system is where things are handled. Here, the document color profile is converted, on the fly, into the monitor profile, and these modified RGB values are sent to the monitor. That's all there is to it - a straight and perfectly normal profile conversion. RGB values are remapped to produce the same color.
    Any profile can be converted into any other. But any colors in the source color space that would fall outside the target color space, are just clipped to the gamut limit, and they're effectively gone forever. If you have a ProPhoto file displayed on a standard monitor, it's reasonable to assume that a lot of gamut clipping has occurred before it hits the screen, because the monitor color space is a lot smaller.
    A standard traditional monitor has a native color space that is very close to sRGB. That's why you can use sRGB as display profile, although of course a calibrator will make one that is much more accurate. This is also why sRGB is the standard for web, because it will display roughly right even without any color management.
    Some monitors have a larger color space, and are close to Adobe RGB. These are relatively expensive and are known as wide gamut. If you have such a monitor, it can only be used with full end-to-end color management. In the absence of color management, sRGB material will not display correctly on these monitors, but considerably oversaturated. This is the implication you have to accept when you buy a wide gamut monitor.

  • Lightroom 4 Color Profile issue

    I'm having real issues with my exported images from Lightroom 4. When editing the files in LR all the colors are fine, however when I export the images look over saturated and often horrible.
    For a better understanding of what I'm doing in terms of exporting, I've gone into more detail (with example images) on my blog, here: http://www.dannypaynephotography.com/blog/2013/04/colour-profile-conundrum/
    To clarify, I'm using a windows 7 laptop with Lightroom 4, using the built in monitor which has been freshly calibrated using a Spyder2express.
    Thanks!
    Danny

    This has to be a bad monitor profile.  Lightroom, Windows Photo Viewer and Firefox are all fully color managed and should, in theory, display identically. But a broken monitor profile can sometimes affect different applications differently.
    The Spyder 2 express is not a great calibrator. It's now outdated, but even while it was current it quickly got a bad reputation, and rightfully so. Luckily ColorVision/Datacolor cleaned up their operation, and Spyder 3 and 4 are considered very good, with vastly improved sensors.
    To test this, you can try to set sRGB as default monitor profile in Windows, instead of the Spyder profile. Control Panel > Color Management > Devices. I'm assuming, since this is a laptop screen, that it isn't wide gamut.

  • Aperture 2.1.4 to PS CS4 External Editor Color Profile issues????

    Anyone else experience this?
    I shoot Nikon D700 and D90 with sRGB color space. When I send a file to CS4 via external editor, PS prompts that my embedded color space is Adobe 1998. ***??????
    I immediately went and checked all my settings on my camera and they're fine. Is this Aperture's doing? PS? maybe even SL?
    Dazed and Confused
    Message was edited by: rtd2870

    Aperture uses the Adobe 1998 color space as it has a wider color gamut than sRGB. Like most things in Aperture, you choose your color space on export.
    sRGB is used primarily for the web, and some printers that accept RGB files ask for sRGB because their printers can't match the Adobe 1998 Gamut.
    If your camera is capable of shooting Adobe 1998, you should, but it doesn't really matter when shooting RAW.
    DLS

  • Weird color profile issue

    I'm a photographer and I use the latest version of Adobe Lightroom and Photoshop CS4 in my work flow. I use a Colorvision Spyder to calibrate my display and print using printer profiles. When I save a file that will be used on the Internet I convert it to sRGB prior to saving it. The file looks fine in LR, PS, Safari and Preview and seems to print fine but when viewed using Quicklook or a colorspace unaware browser, like Firefox, everything has a weird cyan cast.
    Prior to upgrading to Snow Leopard, everything looked and worked as expected.
    I don't know what else to check.

    Apple have changed the default gamma in Snow Leopard from 1.8 to 2.2
    When I upgraded my system I noticed that the display profile had been changed from the calibrated one I set up in Leopard to one just called 'iMac'.
    Perhaps something similar happened to your set up. Have you checked that the colour profile in Displays preferences has not been changed?
    Other than that, I don't know what else to suggest.

  • Color profile problem after installing CS4

    OK.
    First, let me post these side-by-side comparisons:
    As you can see in Image 1 (the "before," left-side photo in each comparison), the colors and overall appearance are distorted. I've read things about gamma but it's all confusing to me. This is surely a color profile problem, right? The transition among pixels that involve colors of yellow and gray is rocky, grainy, and the flat out color is just wrong. Now this color problem affects pictures when opened in both Photoshop 7.0 and the standard Windows Photo Viewer. Meaning, whenever I open pictures in both PS 7.0 and Windows Photo Viewer (my default viewer), this color problem totally messes up certain photos and really damages my ability to edit. I'm an avid photo editor and it's imperative I have proper color display so that I can accurately edit. Keep in mind that certain pictures do not take on this error. When a photo is generally brighter, the distortion is basically invisible. It's photos that are dark or have dark portions in them that display the distortion.
    *Note: I took these before-and-after pictures with my camera, because screencapping would not work, since you all don't have the same color profile issue on your computer. That's the only way I can show you!
    HOWEVER, when I open photos in another standard Windows application, "Microsoft Office Picture Manager," the color problem is magically erradicated altogether. It shows photos as I've been seeing them all along, until I installed CS4 about two weeks ago. Before installing CS4, everything was fine and I had been using Photoshop 7 for years and have never had a problem. I'm guessing CS4 messed something up. It had to have. Just FYI, I uninstalled CS4, hoping it would reverse the problem. But still, the color issue persists in PS 7 and in my regular Windows Photo Viewer.
    Since images display their true form in Windows Office Picture Manager, I don't think I need to calibrate my screen. Or do I? I've read things about it, and to some people, it's not necessary. Right? Okay. I really hope someone can give some advice! Thank you!
    P.S. Here's the original photo. On my screen, it looks distorted when opened in photoshop or opened w/the viewer. However, here on Firefox, it's fine.

    You should try to familiarize yourself with the concepts of color management.
    It's kind of too in-depth a subject to walk you through from a cold start here...  There are a lot of good resources out there to help you get started.  For example, in just a few seconds Google turned up this:
    http://www.adobepress.com/articles/article.asp?p=1315593
    The one thing to remember is this:  There is NO quick solution, easy set of defaults, or direct answer to making your setup do what you want without your having to understand color management.
    People may tell you to calibrate your monitors, or use a particular color profile as a default, or whatever, and they may have good, solid reasons for telling you those things, but if you don't attempt to get your mind around color management it will always seem as though something isn't working right, or is simply magic, which will be frustrating to you.
    Here are some basic questions to ponder:
    What image color profile is your image carrying?
    Is your monitor a wide-gamut display and do you have a color profile set up for it?  What kind of monitor is it?
    What version of Windows are you running?
    Do you know the difference between a color-managed app and one that is not color-managed?
    Which of the apps you're using/showing above are color-managed?
    What are your settings in Edit - Color Settings?
    Take some time and do some research, get your head around the concepts, and it will all make more sense I promise you.
    -Noel

  • Monitor color profiles go away when screensaver runs

    When I exit the screensaver on my Mac Pro (Leopard 10.5.5) my color profile is completely wrong with both screens washed out as if they had some awful default profile applied.
    I can fix this by entering Preferences and then selecting Display. As soon as I do that, the correct color profile is loaded and everything is fine.
    Obviously that is incredibly annoying.
    Does anyone know why the screensaver would cause the color profile to go away and/or why exiting the screensaver would not restore it?

    I've been having the same problem with my Mac Pro, though it only happens on one of the two connected screens.
    I upgraded from the original GeForce 7300 GT graphics card to an 8800 GT I got from the local Apple store. Rather than box up the 7300 and throw it on a shelf, I moved the it to the top, 8 lane PCIe slot and installed the 8800 in the bottom, 16 lane slot. In stead of putting full load on one card, I plugged one monitor (1024x768) into the 7300, and the other (1024x1280) into the 8800.
    The larger monitor, plugged into the 8800, appears to exhibit the color profile issue for a split second before as the screen saver activates, and often (but not always) when coming out of the screen saver. Opening the monitors pane will load the proper profile, but cycling in and out of the screen saver a few times (the number varies, I've seen anywhere from one to five cycles) can also bring up the correct profile.
    In addition, cycling the screen saver will some times result in it deactivating and just sitting at a black screen... The monitor will be on (not in power saving mode), but will only display black. Flinging the mouse back up to the hot corner to cycle on the screen saver results in a momentary flicker of the desktop just before the saver comes up.
    The 7300 screen behaves as expected when the 8800 is having problems, throughout the cycling and all.

  • Losing monitor color profiles

    When I plug or unplug an external monitor (dualhead2go, projector, single monitor) on my MBP mid-2010, I frequently lose the color profile associated with the laptop screen or external monitor. Typically the windows take on a very dark color and are almost unreadable.
    I have to go to the display preferences, color tab, and click on the appropriate profile to fix the problem. Often I have to close and reopen apps to get them to switch back, too.
    Software is uptodate of course. Running 10.7.3. Anyone else experience this?

    I've been having the same problem with my Mac Pro, though it only happens on one of the two connected screens.
    I upgraded from the original GeForce 7300 GT graphics card to an 8800 GT I got from the local Apple store. Rather than box up the 7300 and throw it on a shelf, I moved the it to the top, 8 lane PCIe slot and installed the 8800 in the bottom, 16 lane slot. In stead of putting full load on one card, I plugged one monitor (1024x768) into the 7300, and the other (1024x1280) into the 8800.
    The larger monitor, plugged into the 8800, appears to exhibit the color profile issue for a split second before as the screen saver activates, and often (but not always) when coming out of the screen saver. Opening the monitors pane will load the proper profile, but cycling in and out of the screen saver a few times (the number varies, I've seen anywhere from one to five cycles) can also bring up the correct profile.
    In addition, cycling the screen saver will some times result in it deactivating and just sitting at a black screen... The monitor will be on (not in power saving mode), but will only display black. Flinging the mouse back up to the hot corner to cycle on the screen saver results in a momentary flicker of the desktop just before the saver comes up.
    The 7300 screen behaves as expected when the 8800 is having problems, throughout the cycling and all.

Maybe you are looking for