MBP Ret 13 late 2012, sleep wake failure and black screen 90% of time.

[idch]

Almost half a year ago problem occurred - one day, after I opened lid - screen gone all glitchy and blurry (this is unique glitch - I did not find it on google images on any other mac), and stays like this until I reboot (even apple on the lid stays active, macbook won't go to sleep after this glitch). After that, I got "sleep wake failure" report and... Black screen. For about month or something like this. I use external monitors after this glitch everytime.

The thing is. I do not believe that this is hardware problem, I see this as software problem. Because if I won't close the lid for a sec and disable sleep state forever - screen will work like a charm.

Something, some program, daemon, code, I don't know, something gives this weird bug, that I for so long assumed was hardware problem.

I wan't to see logs and discover, which daemon/program causes this sleep wake and screen glitch, so I can delete it, and everything will be the same again.

Glitch started on Yosemite. Or I don't know. Maybe JRM causes this and it's new version causes this.

Where can I see global logs etc, or maybe suggestions, how can I catch this program, that breaks my screen?

 

[maflynn]

Downgrade to Mavericks to see if the problem disappears and/or load the beta (or wait for the final version) of El Cap. Personally, I'd look to bring it into apple for an examination just to be sure its not a hardware issue.

 

[idch]

Actually I was able to find logs, in Console.

So I have something like this:

9/8/15 2:01:25.049 PM com.apple.AmbientDisplayAgent[193]: AMBD Agent: xpc connection became invalid during event handler
9/8/15 2:01:25.085 PM DMProxy[549]: AMBD Services: connection interrupted: com.apple.AmbientDisplayAgent (Connection interrupted)
9/8/15 2:01:25.093 PM com.apple.AmbientDisplayAgent[193]: AmbientDisplayAgent started
9/8/15 2:01:25.096 PM com.apple.AmbientDisplayAgent[193]: AMBD initializing devices
9/8/15 2:01:25.107 PM WindowServer[163]: CGXSetDisplayColorProfileAndTransfer: Display 0x0b4221b5: Unit 1; ColorProfile { 1872639016 }; TransferFormula (1.000000, 1.000000, 1.000000)
9/8/15 2:01:25.127 PM com.apple.AmbientDisplayAgent[193]: AMBD Agent: xpc connection became invalid during event handler
9/8/15 2:01:31.449 PM com.apple.xpc.launchd[1]: (com.apple.spindump[550]) Service exited with abnormal code: 75
9/8/15 2:01:31.449 PM com.apple.xpc.launchd[1]: (com.apple.spindump) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.


Maybe this has something to do with not working display?

 

[idch]

Just to finish this thread. I was able to fix the problem - it was some kind of widget program for top bar in macos. During start of the display it started also with all other programs. Program crashed and silently crashed "turn on display when lid opens" job. Mind the "silent" word. Job to turn display on returned SUCCESS but actually let the exact process to turn display on to silently die (for whatever reason, this widget program crashed and its exception swallowed "turn on display" job crashing it and making crash silent)

Soooo macos thought that display was on, but it actually did not turn on

Thank universe I had some brain cells to check system logs and uninstall programs one by one to check it.

I set there for half a year with clamshell mode and cheap external screen Thinking that screen of my MBP 13" died for good

 

[norwaypianoman]

Thanks for sharing this. I have a normal Sleep Wake Failure - after updating my Macbook Pro 2012 Pro 13" - 1 TB Crucial SSD - 16 GB Ram from Mojave to Catalina in May 2021.

a) But I have started to uninstall widgets and programs that I never will use, and see if the problem is programs that keeps the Mac awake.

b) It can also be my updated battery that needs service.

 

[norwaypianoman]

Update Around June 11th: The Sleep / Wake Error just disappeared.

Elimination: I cannot find any Apple Security updates. My Macbook was not on automatic system update.

Reason: Unknown.

Theory: A third party software changed and updated, and the problem just disappeared, and system just works.

Theory 2: Microsoft Edge is able to block the machine from being turned off. It might have been the culprit. Even when "off".