- Joined
- Aug 12, 2005
- Messages
- 754 (0.11/day)
Processor | Intel Core i7 4790K |
---|---|
Motherboard | Asus Z97i Plus |
Cooling | Antec Kuhler 620 + Gentle Typhoon 3000RPM |
Memory | A-DATA XPG V2 DDR3-2400 16GB |
Video Card(s) | MSI GTX 970 Gaming 4G |
Storage | Samsung 850 Ev0 500GB |
Display(s) | Qnix QX2710 @100Hz |
Case | Silverstone SG13 |
Audio Device(s) | Onboard |
Power Supply | Silverstone SX-500LG |
Mouse | Logitech G602 |
Keyboard | Corsair K70 Lux |
Software | Windows 10 Pro |
Benchmark Scores | Not interested in benchmarks |
[Solved]Getting blank screen upon loading desktop (Win8/Palit GTX670/ASRock Z68 E4)
Hi,
Today I woke up in the morning and turned on the PC. Great! No display. Actually it showed the messages in the POST screen and even the Windows 8 boot screen. But at soon as it entered desktop (I use autologin) the monitor would not get display. It looks as if when the video driver gets loaded, something goes wrong.
This happened couple of days ago as well. But switching the cable to the 2nd DVI port and reverting back to the old port fixed the problem. But this time, it didn't work.
After hitting reset button a few times, I managed to go into recovery mode. For some reason, shift + f8 doesn't work at all. (UEFI issue with this board? Some say there is.)
Anyways, safemode worked and I removed the nVidia driver (310.90), intel video driver and virtu MVP driver and rebooted. I also disabled iGPU from UEFI. Now I could get into Windows but it was using a generic VGA driver. Windows automatically updated the driver and asked me to reboot. (Before rebooting, I found one unusual thing. Not sure whether it is related to this issue. The mouse clicks didn't work. For example, I opened Windows explorer using win + e but I could not close it by clicking on the close button on the title bar. The click registered because the visual indication of clicking it was shown. Just that it didn't work. Windows is broken?)
Anyway, upon reboot, the blank screen problem was back.
Then I tried if I could boot by connecting the display to the 2nd DVI port. Woah! It wouldn't show anything on screen even at POST. DVI port 1 always showed something at POST. Does that mean something could be wrong with the video card? Or, is it by design?
Then I switched back to the 1st DVI port, went into UEFI and enabled the iGPU. Switched the display cable to iGPU's DVI port and checked if it worked fine. Woah! No display even at POST.
The I just hit the clear CMOS button to load defaults UEFI settings. Nope, that didn't fix it.
Now I cannot get it to POST even with the 1st DVI port on the video card.
So I gave up and went I work. I'm typing this on my way to work.
When I get back home, I'm thinking of doing the following things.
1. Remove the video card from the PC and try to get some display output off the iGPU. If I manage to get it, I will have something to pursue at. If I don't get a display, I don't know what to do other than to RMA the board.
2. If I manage to get the display at POST with the 1st DVI port on the video card, I will do a system reset and see if it fixed anything. (especially if the problem was with Windows in the first place.)
3. If I manage to reinstall/reset windows and fix the problem, it could have been caused by buggy Virtu drivers. There isn't a win8 driver for virtu. I was told by Virtu support to install the MVP software. But it installed as a trial anyways. I have a feeling all this was because of this virtu software.
Anything else I should try?
Btw, specs are in the sig.
Hi,
Today I woke up in the morning and turned on the PC. Great! No display. Actually it showed the messages in the POST screen and even the Windows 8 boot screen. But at soon as it entered desktop (I use autologin) the monitor would not get display. It looks as if when the video driver gets loaded, something goes wrong.
This happened couple of days ago as well. But switching the cable to the 2nd DVI port and reverting back to the old port fixed the problem. But this time, it didn't work.
After hitting reset button a few times, I managed to go into recovery mode. For some reason, shift + f8 doesn't work at all. (UEFI issue with this board? Some say there is.)
Anyways, safemode worked and I removed the nVidia driver (310.90), intel video driver and virtu MVP driver and rebooted. I also disabled iGPU from UEFI. Now I could get into Windows but it was using a generic VGA driver. Windows automatically updated the driver and asked me to reboot. (Before rebooting, I found one unusual thing. Not sure whether it is related to this issue. The mouse clicks didn't work. For example, I opened Windows explorer using win + e but I could not close it by clicking on the close button on the title bar. The click registered because the visual indication of clicking it was shown. Just that it didn't work. Windows is broken?)
Anyway, upon reboot, the blank screen problem was back.
Then I tried if I could boot by connecting the display to the 2nd DVI port. Woah! It wouldn't show anything on screen even at POST. DVI port 1 always showed something at POST. Does that mean something could be wrong with the video card? Or, is it by design?
Then I switched back to the 1st DVI port, went into UEFI and enabled the iGPU. Switched the display cable to iGPU's DVI port and checked if it worked fine. Woah! No display even at POST.
The I just hit the clear CMOS button to load defaults UEFI settings. Nope, that didn't fix it.
Now I cannot get it to POST even with the 1st DVI port on the video card.
So I gave up and went I work. I'm typing this on my way to work.
When I get back home, I'm thinking of doing the following things.
1. Remove the video card from the PC and try to get some display output off the iGPU. If I manage to get it, I will have something to pursue at. If I don't get a display, I don't know what to do other than to RMA the board.
2. If I manage to get the display at POST with the 1st DVI port on the video card, I will do a system reset and see if it fixed anything. (especially if the problem was with Windows in the first place.)
3. If I manage to reinstall/reset windows and fix the problem, it could have been caused by buggy Virtu drivers. There isn't a win8 driver for virtu. I was told by Virtu support to install the MVP software. But it installed as a trial anyways. I have a feeling all this was because of this virtu software.
Anything else I should try?
Btw, specs are in the sig.
Last edited: