No Video on Windows 7 Boot, Potential GPU Issue

[Xhavalor]

Hi all,

 

    During a particularly average gaming session of Supreme Commander all video output was lost. Upon restart, my GTX 780 still was able to output the initial motherboard BIOS screen and Windows 7 was able to display a error message (since I had to do a hard restart).

However, following the Windows intro sequence there was no video at all. As in, the monitor turned off as there was simply no output.

 

I swapped out the GTX 780 for a GTX 560 and saw that I booted fine, so the issue most probably pertains to the GPU.

 

My question to ya'll is this: why can the GTX 780 output the BIOS and Windows initialization screens fine but fail to display the OS proper? Seems strange the GPU only goes half the distance.

 

I have to add that I only recently updated to Nvidia's 326.19 Beta drivers, deciding to jump in after all the issues surrounding the prior 32x.xx revisions. Furthermore, my card is set to EVGA's factory overclock speeds for their GTX 780 ACX edition.

 

Driver issues? Card malfunction? 

 

 

[WoodenMarker]

Psu problem maybe? What's your psu?

[ShadyHost]

Maybe a driver corruption. I had something similar happen with dual 670s when someone was digging around on my power strip trying to plug the printer in. I was in the middle of a game and and my pc lost power. 

 

What I did was boot into safe mode, uninstall the driver, and then boot back into the regular Windows environment and reinstall the driver. 

 

 

Not sure if this is your exact issue though. 

[Xhavalor]

Psu problem maybe? What's your psu?

Corsair CX750. 

I had heard of PSU issues leading to these types of problems around the net. 

Maybe, maybe. 

[Xhavalor]

Maybe a driver corruption. I had something similar happen with dual 670s when someone was digging around on my power strip trying to plug the printer in. I was in the middle of a game and and my pc lost power. 

 

What I did was boot into safe mode, uninstall the driver, and then boot back into the regular Windows environment and reinstall the driver. 

 

 

Not sure if this is your exact issue though. 

That may be a viable solution. Thanks for the suggestion, I will attempt and perhaps report back.

[ShadyHost]

That may be a viable solution. Thanks for the suggestion, I will attempt and perhaps report back.

Did that fix your issue? I see you selected my post as best answer. 

[Xhavalor]

Did that fix your issue? I see you selected my post as best answer. 

Ah, yes. As you directed. It seems that, on the spur of the moment, driver conflicts began.

Re-installing worked. As a safe measure I went back a couple of driver revisions.

 

Thanks for the suggestion! It now seems so simple, but I was too blind to see it.