black screen in Catalina

I'm suffering from a black screen on my MacBook Pro after every sleep event.

Only way out is to hit the off button and restart every single time.

Does anyone have a solution?

Thanks

Posted on Oct 9, 2019 7:04 AM

Reply
Question marked as Top-ranking reply

Posted on Oct 11, 2019 7:03 PM

Well everyone, if you need the solution, it's possible. It's just worst-case scenario.


I can confirm that IF YOU HAVE A CURRENT TIME MACHINE BACKUP from pre-Catalina install, this problem can be fixed by doing a clean install of macOS 10.15 Catalina on a freshly formatted drive. This requires you to install macOS 10.15, set up the machine as a new computer, and then use Migration Assistant to transfer your old user data back into your machine. To follow this process:


  1. Make sure you have a working Time Machine backup from before your macOS Catalina install - DO NOT PROCEED IF YOU DON'T, or you will lose your data
  2. Boot into recovery mode by powering on the machine and holding Command ⌘ + R
  3. Use Disk Utility in Recovery Mode to reformat (erase) your system ("Macintosh HD", or whatever you named it) drive or the container that hosts the system drive and "data" drive.
  4. Select the appropriate file format for your machine's needs (seek other articles to find this out)
  5. Close Disk Utility after complete, and use the "Reinstall macOS" feature of Recovery Mode to reinstall 10.15
  6. Allow the process to complete
  7. Set up the machine as if it were a brand new device - don't transfer your data in this process
  8. Verify that your new install of macOS 10.15 Catalina is no longer exhibiting the wake/sleep issues
  9. Use Migration Assistant in the Utilities folder to transfer your user data back from your Time Machine backup to your fresh install of macOS - OR, if you prefer, take this opportunity to start "fresh" and only transfer back the specific data that you think you'd like to keep.


This is the most complete and time consuming way this could be resolved, but the issue has been solved for me. It must be caused by some sort of user-land kext or daemon, or something that is changed by performing a clean macOS 10.15 install and then transferring your user data.


NOTE: Only do this is you had the forethought to have a working and complete backup with Time Machine prior to installing macOS Catalina. I cannot stress this enough if you are new at this...


Good luck, and godspeed!

Similar questions

154 replies

Oct 17, 2019 7:48 AM in response to KevoMoo

You said it, releasing software and hardware with bugs reminds me of another coMpany that we will not naMe here, but they have blue screens of death instead of black screens of death. I guess Apple is following this model now release and fix later? I’ve been a loyal Apple customer and early adopter since the 90’s even when they were going under and selling their rights to produce macs. Not sure if you all remember that but google Umax supermac or power computing and yes I owned one of those as well a quad processor supermac which blew away my Apple 9500/180MP powermac.


Ok with all that said I’ve been around for a while Apple and I don't know what’s going on there, but we would like you to take notice and stop releasing Inferior or problematic software and hardware. Just take the time to get it right the first time, there is no reason to rush a full release every 6-10 months. Having things like this happen only hurts your image and takes loyalists like myself and others to a place we wouldn’t have considered months ago and thats going the way of your competitors. I have NOT upgraded to the new iPhone from my XS Max, since the upgrade to the new phone is so minimal its just not worth it and I do NOT need a 3rd camera with a dog photo feature, this is not innovation, its just sad. I have been considering leaving the Apple ecosystem and going to the other offerings that have more innovative cutting edge features. I would love to help R&D take your product to the next level and bring Apple back to the roots of being an innovator and industry leader, instead of a trend follower trying to catch up with its competition.


When Steve Jobs came back to the company in the 90’s he reduced the extensive product line to streamline efficiency and quality. I see a similar trend with the current offerings that mirror the Apple of the 90’s having too many product lines along having with quality issues. I’m sorry for the rant here, but I’m just a frustrated Apple loyalist that would like to see this issue along with several others be resolved for good, so we can go back to the Job’s level of perfection Apple has strayed from. I have so many more things to say, but I will stop here.


Please fix your software bug(this is not hardware related), I would be open to test out a full video driver replacement if it was available, I believe this is the issue(just sifting through log files), but what do I know.


</end soapbox>

Oct 17, 2019 11:48 AM in response to Jeff Collier

Whats even more odd is I copied that driver back into the extensions folder and it's all working.


I did however remove ALL extensions except AppleMobileDevice.kext and then copy them back in after a restart. So in fact it might be a permissions error or something along those lines. It will ask you to authenticate when you copy them back in, so that will associate them with your user and this system again. That might be the fix, try this people.


Remove ALL extensions except AppleMobileDevice.kext in your /Library/Extensions/ folder (put them in a safe folder on your desktop to reinstall)

Restart

Then copy them all back into the /Library/Extensions/ folder.

Restart

and then test.


All is working for me with ALL extensions.

Oct 17, 2019 12:05 PM in response to Jeff Collier

I removed the following files from /Library/Extensions and it now works fine.


CalDigitHDProDrv.kext

HighPointIOP.kext

HighPointRR.kext

MCTTrigger6USB.kext

MCTTriggerGraphics.plugin

Trigger5Core.kext


I then reinstalled the removed files and rebooted and it works perfect. Not sure if it has to do with permissions as those files had to be reauthorized when I put them back in the /Library/Extensions folder. Hope this helps you all.

Oct 17, 2019 1:48 PM in response to josepalvarezperez

@josepalvarezperez


Do this:


Remove ALL extensions except AppleMobileDevice.kext in your /Library/Extensions/ folder (put them in a safe folder on your desktop to reinstall)

Restart

Then copy them all back into the /Library/Extensions/ folder. (you will have to authenticate to copy into the folder this is normal)

Restart

and then test.


All should be working like normal.

Oct 17, 2019 4:28 PM in response to Ri2

It appears the Automatic Graphic Switching option is not the solution - some of us don't have that option, and for those that have it, it doesn't seem to work properly either.


The issue, and a possible solution/workaround, seemed to indicate files/device drivers located in the /Library/Extensions folders that are causing the issue. Have a look at the later pages of this thread, specifically on Page 7, where a few people pointed which files in the /Library/Extensions are causing issues. You'll likely find one or more of those related to display graphics that causes issues. For my case, it was the MCTTriggerGraphics.plugin and Trigger5Core.kext files that are causing issues.


To resolve this, make a copy of the file elsewhere (i.e. on a folder on your Desktop), then delete those files from /Library/Extensions, and restart your Mac. Test it after restart to see if it fixes your problem.


Some people had luck by then copying those files back to /Library/Extensions (you'll need to reauthenticate when you copy the files back), but for my case those files causes issues so I'll have to leave them out of /Library/Extensions. I'm fine with it since I don't use any of those devices anymore.


Hope this helps.

Oct 18, 2019 4:36 PM in response to kelyndie23

Detailed fix:

1.. Delete these 3 files from the Library/Extensions/ directory:

    • MCTTrigger6USB.kext MCTTriggerGraphics.plugin and Trigger5Core.kext

2.. Reboot your machine.

3.. Go to your trash bin and put the files back (it will ask you to authorize them again with your password).


This seems to have worked for the majority of us that started this thread. If you still have problems, try resetting your PRAM by holding CMD + OPT + P + R at the same time when booting up your machine for 12 seconds, then release them at the same time.


I think if you delete those Library files and then put them back after reboot you should be good to go.


Oct 19, 2019 9:57 AM in response to KevoMoo

I was also having this issue, and struggled for about a week trying to figure it out. In my case, the issue was caused by some drivers installed by a USB adapter made by a company called j5create. In my "/Library/Extensions/" folder I deleted "MCTTrigger6USB.kext", "MCTTriggerGraphics.plugin", and "Trigger5Core.kext", which were the drivers installed by j5create. Put my computer to sleep, waited 30 seconds, opened it back up an the display came back.


I also checked their website and there's a notice on their driver's download page:


At this time, our display driver software does not fully support macOS® 10.15 Catalina. We recommend all users delay in updating to the new operating system until official j5create drivers are released.

https://en.j5create.com/pages/drivers


I haven't used the USB adapter in awhile so I just left it deleted.


If you don't have a device like this but you're still experiencing issues, I'd suggest looking in your "/Library/Extensions" folder, Google search the name of the drivers, and delete any that deal with the display.


Hope this helps!

Mar 10, 2020 10:04 AM in response to sahil216

Thank you! This solved my problem since I took it a step further.

It alleviates the pain somehow with no lock for 8 hours, but since I keep it at home and nobody else is using it, I deactivated "Require password" altogether.

It tried without it and I saw it works and then I put it back on.

It's a miracle! It works as expected now!


PS:

I have a MackBook Pro Retina, late 2015 and 2 external monitors.

The HP monitor on HDMI never had a problem.

The issue was with an old Led Cinema Display 27" on Thunderbolt - it remained black after screen lock


I noticed it is not about the display not powering back on, since I could see notifications popping up on the screen but the lock screen was not showing to be able to type the password.

It remained black. It seemed a problem with the screen lock, rather than power.


Deactivating screen lock and reactivating seems to have solved the issue for me.



This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

black screen in Catalina

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.