Hello,

I have been having this problem for almost a year now and so far I can't seem to find a solution for this.

The problem is that, when waking up my PC from Sleep Mode, I sometimes randomly get a "no signal" message on my monitor screen. The system itself is waking up normally when I press a key or use the mouse but the screen just keeps saying that there's no signal and stays black. And I can't do anything.

Waiting a while in this situation will make the PC automatically reboot itself, after which the screen turns on normally. Logging in and looking at the Reliability Monitor shows 3 errors that happened before the automatic reboot during the black screen:

1) That Windows has been shut down incorrectly.

2) That Windows didn't work properly with the following error (translating it from Dutch):
The computer has restarted after a bugcontrol. The bugcontrol is 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff803a960a370, 0x0000000000000000). A dump file is saved in: C:\Windows\MEMORY.DMP. Rapport-id: 327d2b22-fb82-4f0e-adf5-907f0e9c8fc3.

3) That Windows was shut down unexpectedly with the following error:
Name of problem event: BlueScreen
Code: 133
Parameter 1: 1
Parameter 2: 1e00
Parameter 3: fffff803a960a370
Parameter 4: 0
Versie besturingssysteem: 10_0_16299
Servicepack: 0_0
Product: 256_1
Versie van besturingssysteem: 10.0.16299.2.0.0.256.48
Landinstelling-id: 1043

Because the last error contains "BlueScreen", I figured that an invisible BSOD might have happened when I woke up my PC whilst my screen was black. Also, Windows has made a Memory dump file which is 771MB in size (no idea how to share this).
The problem is completely random; there are times in which the screen turns on normally after waking up the PC and times in which it does not. I really don't know what the trigger is. I have Ultra Fast boot enabled. Reformatting and doing a clean install of Windows didn't help.
 
The dump file shows that the crash was caused by nvlddmkm.sys (nVidia graphics driver) running at IRQL 2 for an extended period of time. This generally indicates a fault in the driver, and Windows crashed to prevent the system from hanging for an indefinite period of time.
The issue is that I've had this problem with several nVidia WHQL drivers over the past year.
Googling my problem shows that several other users are having this same issue, for example: http://www.techsupportforum.com/forums/f299/bsod-coming-out-of-sleep-mode-nvlddmkm-sys-1113986.html

Here are my specs:
Asrock Pro4 Z77 motherboard
i5-3570K (not oc'ed)
EVGA GTX 660Ti 2GB (not oc'ed) with 388.13 WHQL drivers
1 TBB Western Digital HDD
8 GB RAM
Windows 10 Pro Fall Creators Update x64 bit (also happened on Win10 before the Fall Creators Update)
 
Really hoping and looking forward to fix this issue. Appreciate any help.

If you are suspending to ram, turn this off in the BIOS. Make sure your BIOS is up to date, motherboard and video card. You can ask evga tech support if there is a new BIOS for your 660ti, I recall some models offered a UEFI BIOS available.

Sorry for bumping this thread again but I think I'm pretty sure now about the cause of this problem; it's the Ultra Fast Boot. 
 
For a long time now, I have been using Fast Boot and this issue after Sleep Mode didn't occur once. As soon I enabled Ultra Fast Boot again, the problem came back (No signal screen after Sleep Mode)
 
The probability of this issue occurring seems to be far greater if I put my PC into Sleep Mode while I have software running like a browser for example. But then again, it says that the nvlddmkm.sys (nVidia graphics driver) is the cause of this problem because it's running at IRQL 2 for an extended period of time.
 
There is a very small vBIOS update for my 660Ti but I was told by support that it merely adds support for other types of GPU's and that it doesn't support UEFI. So that I can't enable Ultra Fast boot with this vBIOS update. 
 
I really want to use Ultra Fast boot but I can't seem to know how to fix this problem when I enable it.
 
Any thoughts on this?

Sajin
Glad you were able to figure it out. Support told you there isn't a uefi vbios update for the 660 ti? Might want to point them to this post then... https://forums.evga.com/FindPost/2739231

I already have a UEFI vbios installed, version 80.04.4B.00.F0. Ultra Fast Boot works but with the random problem that I'm describing. Support told me that there is a newer vBIOS update but without UEFI support, which is 80.04.4B.00.60. It only adds support for certain GPU (memories).