Forum Home
Press F1
 
Thread ID: 139326 2015-04-15 00:58:00 Black screen boot Tbird650 (6754) Press F1
Post ID Timestamp Content User
1398578 2015-04-15 08:11:00 The problem can be many things, including ( as already mentioned) either Power related or Graphics drivers.

Since windows is loading in the background:

Couple of things to try --
1. See if the computer will start in safe mode, sometimes if its graphics safe mode works, if it does remove the drivers or run system restore back to when it was OK.
2. It could just be Explorer is not loading correctly. press ctrl+Alt+Del If the task manager opens, look in the processes tab to see if explorer.exe is running, if it is, right click it / End task then:

1. Click File
2. Click New Task
3. Type explorer.exe
4. Click ok

If you suddenly get a desktop then its software related normally.

Theres a few other things to try as well, have a read of Windows_7_Black_Screen_of_Death (visihow.com)

Like this article :D "Don’t forget to cross your fingers." After every option.
wainuitech (129)
1398579 2015-04-15 09:03:00 Thanks. A lot of good leads to pursue!
I can say that the graphics driver is the latest available. (I could try a roll back I suppose.)
Just today a dozen updates came down the pipe, 9 of which are security updates. It might be that one cures the problem...
OK, so I'm now going to wait till tomorrow morning and see if the black screen returns. From there I'll try one thing at a time and test over following days.
Meantime Ill look at upgrading the card. It's old anyway. Or perhaps I'll research dual monitors from the mobo.
Tbird650 (6754)
1398580 2015-04-15 12:04:00 Do you shut it down or put it to sleep? some hardware combinations just don't resume from sleep well.
Otherwise try the onboard graphics as speedy suggested and see what happens, it'll reduce the load on the PSU as well.

I've had a PC go completely dead on me, no response to power button, nothing, won't boot at all. Then unplugged it for 10 mins, problem fixed. All because I tried sleep instead of shut down on otherwise perfectly stable hardware. My main PC I sleep all the time though, even with an SSD it starts up much faster this way :)
dugimodo (138)
1398581 2015-04-15 23:41:00 dugimodo, 98% of the time I shut down completely. I always shut down overnight. As you say, sleep isn't totally stable.

Reverting to onboard graphics would be an option if it will drive both monitors. Yet to test.

The PC booted up with working graphics this morning. So I didn't get to test out any of the remedies mentioned above.

Keeping options open, I decided to email Computer Lounge requesting a recommendation for an upgraded card:
www.computerlounge.co.nz
I note the spec is PCI-E 3.0 16x. Studying PCI-E I believe its' backwards compatible with my PCI-E 2.0 slot. Please confirm
Tbird650 (6754)
1398582 2015-04-19 22:45:00 Have been trying some things and have learnt a bit more. The machine cold booted (morning) twice fine, then the 3rd time black screen. Reboots during the days were fine. Even shutting down for a couple of hours, restart was fine.

Run a Malwarebytes scan, all clear.
Run SFC scannow. Windows repaired some files.
Checked SSD.
Removed graphics card and driver, then connected to onboard graphics. Installed driver, both monitors work. But then...
Cold boot in the morning has the #2 monitor showing splash, etc but when it gets to desktop also goes black. A reboot some minutes later has both monitors with splash, etc then finally login window with monitor #1. At this stage #2 monitor is black which I think is normal. Logging in has both monitors working normal and perfect for the rest of the day.

When black screen event occurs, ctrl-alt-del does not work. Windows welcome is heard. It's almost like something needs to warm up to start working nicely.

One thing I'm trying next is to swap the main display to the #2 monitor.

Monitors: one is 8yo Chimei, other slightly newer Viewsonic..
Tbird650 (6754)
1398583 2015-04-19 23:48:00 Not to be alarmist but it could possibly be a hardware fault, some components will work ok most of the time once running and warmed up despite being a little bit faulty and causing issues when first powered up. If it is though there may be nothing you can do but keep using it and hope it doesn't get worse. You could try cold booting off a linux live CD or USB stick a few times to see if it still happens but intermittent faults are the hardest to prove.

Also check the basics, make sure the power cords are firmly inserted and ditto for the monitor cables, try unplugging them and plugging them back in a few times. If using a multi-board make sure it's not loose in the power sockets. If using cables that can be secured try screwing up the retaining screws (a lot of people including myself never bother to screw them on). Any electrical connection that's not 100% can act the way you describe, once current starts to flow it acts to keep the connection working but before that it may not work. Some circuits use a wetting current to maintain a good connection to get around this issue. en.wikipedia.org

One of my monitors at work goes black from time to time, it's the multiboard I bump with my feet at fault and I really should replace it.
dugimodo (138)
1398584 2015-04-22 21:20:00 could possibly be a hardware faultThanks. I tried some of the suggestions. Another power lead, socket, multi-box etc., no difference.
Swapping the monitors so #2 is the main one showed something about the Chimei. The system boots to desktop and displays perfectly on the Viewsonic but many of the pages I might want to open require the Chimei to display on. Unplugging and re-plugging a few times over several minutes and the Chimei comes to life. The little green LCD is glowing the whole time though.
So at this moment I'm thinking the Chimei monitor is getting lazy and needs a warmup period. To narrow down and verify the problem I have another smaller monitor to swap in.
Tbird650 (6754)
1398585 2015-04-23 03:08:00 I had this problem with both my Win 8, first then my Win7 which I substituted in, turned out to be the Viewsonic monitor causing the problem but it seems to work ok on a Linux boot!!!??? zqwerty (97)
1 2