Odd LCD Backlight Behavior

Have you turned off the auto adjust brightness option in the display settings?

 

Did you unstick the automatically adjust brightness as ambient light changes?

 

can you post your console output?

 

K, start by removing your lexmark drivers and parallels. When you're done, repair your disk permissions. Try that to start and report back.

 

Just try one at a time with a restart in between. They should be fine now... but say something if it's not!

 

i have the same problem, i dont have Parallels in my mbp.

 

Have you tried Fusion? I prefer it to Parallels personally. As far as the console goes, make sure you have one of the sub categories selected to see any output.

 

update i think everytime you use discrete graph card will cause the problem.

ps. im using 2011 15' hi end mbp

 

Anything's possible. Can you post your console output? Lets find out Other applications can do that as well, it doesn't necessarily have to be Parallels.

 

update: i think i found the fault app.
after i quit gfxCardStatus, everything going fine.

update again:
think im wrong, still got the problem, when i running discrete graph card.

 

Code:

 11-7-16 上午02:59:25	gfxCardStatus[3545]	The following notification has been triggered:
NSConcreteNotification 0x116300350 {name = NSApplicationDidChangeScreenParametersNotification; object = <NSApplication: 0x10021b0c0>}
11-7-16 上午02:59:25	gfxCardStatus[3545]	getMuxState was successful (count=1, value=0x00000001).
11-7-16 上午02:59:25	gfxCardStatus[3545]	Updating status...
11-7-16 上午02:59:25	gfxCardStatus[3545]	Intel HD Graphics 3000 in use. Sweet deal! More battery life.
11-7-16 上午02:59:25	[0x0-0x235235].com.apple.Console[3478]	Sat Jul 16 02:59:25 Liu-CAOmatoMacBook-Pro.local Console[3478] <Error>: kCGErrorFailure: _CGSLockWindow: Cannot synchronize window backing surface
11-7-16 上午02:59:25	[0x0-0x235235].com.apple.Console[3478]	Sat Jul 16 02:59:25 Liu-CAOmatoMacBook-Pro.local Console[3478] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
11-7-16 上午02:59:27	gfxCardStatus[3545]	getMuxState was successful (count=1, value=0x00000001).
11-7-16 上午02:59:27	gfxCardStatus[3545]	Writing preferences to disk
11-7-16 上午02:59:27	gfxCardStatus[3545]	Successfully wrote preferences to disk.
11-7-16 上午03:00:11	gfxCardStatus[3545]	The following notification has been triggered:
NSConcreteNotification 0x1163007a0 {name = NSApplicationDidChangeScreenParametersNotification; object = <NSApplication: 0x10021b0c0>}
11-7-16 上午03:00:11	gfxCardStatus[3545]	getMuxState was successful (count=1, value=0x00000000).
11-7-16 上午03:00:11	gfxCardStatus[3545]	Updating status...
11-7-16 上午03:00:11	gfxCardStatus[3545]	AMD Radeon HD 6750M in use. Bummer! Less battery life for you.
11-7-16 上午03:00:11	gfxCardStatus[3545]	Updating process list...
11-7-16 上午03:00:13	gfxCardStatus[3545]	getMuxState was successful (count=1, value=0x00000001).
11-7-16 上午03:00:13	gfxCardStatus[3545]	Writing preferences to disk
11-7-16 上午03:00:13	gfxCardStatus[3545]	Successfully wrote preferences to disk.

 

Sorry, I should have been a bit more specific. If you look at the left of the console, you will see a subcategory at the top called "console messages." Click that, then

File>Save a Copy As... and upload the output file to here.

 

here you go. i clicked gfxCardStatus off and quit all app i was running, then run MplayerX again to make sure my mbp start using discrete graph card. then my macbook pro will be fine. after i start running gfxCardStatus again, the problem will show up.

thank you for all your help all the way.

 

I am having the same issue.

But in addition to this issue, after the 10.6.8 update when I use the expose to put my display to sleep (top right corner) the display wouldn't come back on after about 2 or three times in a row of doing this, but the keyboard lights up. I have to shut the lid, let it sleep, and pray my display comes back on and or push the power button, etc. to try to get the screen to come back on.

I was also experiencing battery life issues after the update to 10.6.8 but I found out the problem was a conflict with Parallels 6 and the Windows Applications folder.

Here is the thread I started on this: http://forums.macrumors.com/showthread.php?t=1187192