[SOLVED] No monitor signal during boot

[DejanSRB]

Hi, about a week ago i've performed a clean install of windows 10 on my computer. Formatted everything and installed a new operating system. Everything ran smoothly for approx. Few days. Then the other day i noticed that after my computer went to sleep, and i moved the mouse to bring it back, it would not give me the screen. I restarted the computer and it seemed fine. Few days later to last friday, and when i turned my computer on i would get no screen whatsoever. The computer would post just fine but during the process of boot and loading andeven after my monitor was not getting any signal. I so far i went ahead and did a cmos reset, and found out that power cycling the system (unplugging it from the line, holding the power button for about 30 seconds and then plugging it back in) would allow it to boot normally with screen. Im suspecting that this is a gpu driver issue but im not 100% certain. So any recommendations to where i should look would be welcome. Thanks!

Specs:
MB: Gigabytw GA H61M-ds2
CPU: intel i5-3470
Gpu: gigabyte geforce gtx 960
Ram 12gb ddr 3 ram

 

[Colif]

Try turning fast startup off - https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html

it won't help sleep but it might fix the startup issue.
Its possibly a driver on PC doesn't like the new power modes in win 10 and just doesn't start from the power mode used by fast startup. What windows does by default is, instead of turning PC off when you shut it down, it would use a hybred hibernate mode and put PC to sleep. when you start PC up, its already got copies of all drivers in ram so it should boot up fast, but old drivers that weren't written to use Fast startup can bug out

now it could be GPU but Nvidia drivers well and truly written to cope with that mode. Where did you get drivers from? Did windows provide them or did you dl from Nvidia?


Do you have last bios on motherboard? which revision of motherboard do you have as there 7 of them, and all would have different drivers - not that it is likely to matter as looking at rev 5, the only drivers you have are Intel Management Engine Interface and Audio, which both shouldn't have anything to do with video.

You may need to turn sleep mode off

 

[DejanSRB]

So i got some updates on this. Today when my brother tried to turn on the PC, it would turn on, turn off and then turn on but would give no post sounds at all. The fans would be spinning, everything would power up but it would not boot or give screen signal. So i went ahead, disconnected all the peripherals from the computer, disconnected it from the mains, took out the CMOS battery, and basically performed a CMOS reset by holding down the power button for about 30 seconds. Then i took out both RAM sticks, gave the contacts a clean and same with the RAM sockets on the motherboard. Put the ram memory back in, re-inserted the CMOS battery and viola it booted properly. I'm typing this message from my PC now. I'm still highly confused as to what caused it to act like this. Now it's working completely normally. I will keep monitoring over the next few days to see if this will re-occur. Hopefully not (fingers crossed).

Addendum: I have the Revision 2.0 of the motherboard, BIOS version F7. I could go ahead and flash the bios and update it to the currently available F9 version if this issue returns, i'm not exactly sure if i shoud use the F10a as it's beta bios and i'm not sure how stable that would be.

 

[Colif]

I would only upgrade to F9 as well.

did you change fast startup settings?

it could be the powering PC off like you did with cmos meant it started from shut off state instead of the power saving state windows 10 tries to use with fast startup. Unless you had turned that off already. even the new version of your bios isn't written for win 10

 

[DejanSRB]

I would only upgrade to F9 as well.

did you change fast startup settings?

it could be the powering PC off like you did with cmos meant it started from shut off state instead of the power saving state windows 10 tries to use with fast startup. Unless you had turned that off already. even the new version of your bios isn't written for win 10

I had the fast startup disabled from the very start. As soon as i had the windows installed, fast startup was one of the first things i disabled. Im starting to think that the issue was caused by a badly slotted ram. As i re-slotted them yesterday while methodically removing/replacing parts to see if one of the components had failed, and it booted just fine. This morning aswell, booted with no issues.

 

[Colif]

possible, though strange it starts happening without you doing anything inside case. Try checking ram just to make sure they okay.
I would try running memtesst86 on each of your ram sticks, one stick at a time, up to 8 passes. Only error count you want is 0, any higher could be cause of the problem. Remove/replace ram sticks with errors.