I'd say 50% of the time I wake my system (by pressing the space bar) it gets "stuck". I have three displays, when it fails to wake from sleep, the center and left displays are off and the right display is on but nothing shows on screen. The only way to get the computer running is to hold the power button to shut it off then turn it back on, after that the computer runs fine. I checked the Windows logs and all I can see is:
The following boot-start or system-start driver(s) failed to load:
cdrom
 
I don't have a CD drive in my computer. I did have a program in my computer to create .ISO files (don't remember the name) that put an icon in my tray related to a CD-ROM. That program has been uninstalled and the problem is still there.

I just uninstalled another .iso program and I'll see if the problem continues. Maybe a conflict with a Windows update?

This issue just started. I think it has to do with the program I installed to make ISO's from the discs I have. It installed a virtual CD drive as I don't have one and use an external one. The problem seems to be fixed after uninstalling PowerISO and the other one which I can't remember.

That's the only thing I could think that would be causing it.

Friendly view just shows cdrom (which I don't have).
 

Have you ever connected a USB CDRom drive



Yes I have. I used it with a program to make an .iso a while ago and forgot exactly what I was doing and which software I used. I changed the number from 1 to 3 in regedit. Let's see if the problem is solved.
 
Thanks :)

Nope. Happened again. I'll be doing a reinstall (for other reasons) so now I no longer care what was doing it. I'll make sure to check and see after adding a cdrom program if the problem reappears.

Not the original battery. Put a new one in the beginning of last year. Maybe I should just replace the battery, they are dirt cheap.

I've been dealing with this exactly thing and literally puling my hair out for nearly 15 months and only last week I got this under control.
It's not in your signature, are you on Windows 7 or 10?
 

Looking at post #6 will tell you that the OP is running windows 7.
 

 
 
Well.. doesn't  tell you per say win7, but yes I can see that now. I didn't pay enough attention to the screen shot of the system management thanks for pointing this out to me

It's sorta fixed. I'm not using sleep anymore and shut down my computer when I'm not using it.
 
A tip I received on another forum.

arestavo

HarryD
It's sorta fixed. I'm not using sleep anymore and shut down my computer when I'm not using it.
 
A tip I received on another forum.

And post #2 here 

I do have my memory set to a XMP profile and that bumped up my CPU also. So will that slight overclock cause the same issue you were seeing?

Update to the problem I was having.
 
I installed two GTX 1080's into my main computer, moved the GTX 980's into my racing sim rig (new build, still three displays). I am only using two 980's because of the micro ATX board I'm using (one 980 will be a spare). I'm using Windows 10 and haven't touched the default sleep settings. I noticed that when the computer woke up, I was greeted with the same issue (right display wouldn't turn on). I did a little investigating and found that I could just pull the cable from the back of the video card. There is a lock on the DP cable that should prevent this.
 
What was happening is that there is a little piece of metal that is bent to add rigidity to the I/O area of the Corsair 350D case that I'm using for the sim. The DP cable was hitting this metal and would not allow the cable to lock in place. I disassembled everything and broke that metal piece off. Now the cable can fully seat into the video card and I haven't had the issue of a display not turning on.
 
What lead me to this is that one time the center display wouldn't turn on and I never had an issue with the center display (it was always left or right). I unplugged it, plugged it back it and it turned on. I thought that was strange because the cable shouldn't pull out that easily. That's when I saw the metal piece.
 
I don't have my old case (Corsair 750D) so I can't be certain if that's what was causing the problem before.