PDA

View Full Version : Random Black Screen on Boot - Asus ROG G750JS (Windows 10)



alan.goncalves
02-19-2017, 01:49 PM
Good morning!

My name is Alan and I have an Asus ROG G750JS laptop with Windows 10 installed. Since January, my laptop starts to boot with a random black screen like the video below. I don't know what's happening, but if I try 2 ou 3 times again, the system start normally.

If I put a HDMI cable during the black screen, the Windows login screen will show on my TV. Has anyone had the same problem? Is there a solution?

Vídeo with the black screen:



https://www.youtube.com/watch?v=e3VAYeucUXI&feature=youtu.be

Note: When I say "black screen", it means that the screen did not turn on.

Julskey
02-19-2017, 03:34 PM
If that black screen that you said comes gain, try to put some light from a flashlight/torch against the screen and try to look for signs of display graphics.

Could be that you have a dying backlight. Have similar issues with some old external monitors, no back light (caused by bad electrolytic capacitors).

For your case, it might be loose cables/connectors or broken cable at the hinges.

alan.goncalves
02-19-2017, 04:10 PM
If that black screen that you said comes gain, try to put some light from a flashlight/torch against the screen and try to look for signs of display graphics.

Could be that you have a dying backlight. Have similar issues with some old external monitors, no back light (caused by bad electrolytic capacitors).

For your case, it might be loose cables/connectors or broken cable at the hinges.

But think with me. The computer only has these problems when it boots, when it starts, everything works perfectly!

And I very much doubt that it is a problem with cables or broken connectors, because after the notebook is turned on, I can move as much as I want on the notebook screen that the image does not disappear.

patrioticalien
02-19-2017, 04:31 PM
But think with me. The computer only has these problems when it boots, when it starts, everything works perfectly!

And I very much doubt that it is a problem with cables or broken connectors, because after the notebook is turned on, I can move as much as I want on the notebook screen that the image does not disappear.


If you are able to switch to the intel integrated GPU, try that - if it boots up without the black screen issue, when using the intel GPU then it works. Which this could possible mean a faulty GPU.
If you switch to intel GPU and still boots with the same issue, could be a cable/screen issue.

Can you do this as well,
Can you create a Dxdiag of your PC and attach it? - could be a driver issue, which might be the cause.
Create a dxdiag, go to windows, enter, run, dxdiag, save then upload here.

Other things which are needed to be asked:
1) When did this start occurring? i.e. started to happen when i updated my drivers/windows or added a game/program
2) Is windows 10 the original O.S., If not was it an upgrade? - how was it installed i.e. clean install or just upgraded from the previous windows version x.
3) Is windows 10 fully updated?

alan.goncalves
02-19-2017, 05:09 PM
If you are able to switch to the intel integrated GPU
I think I can not do this, but I'll search if that's possible



Can you do this as well,
Can you create a Dxdiag of your PC and attach it? - could be a driver issue, which might be the cause.
Create a dxdiag, go to windows, enter, run, dxdiag, save then upload here.
Here is the file link: https://drive.google.com/file/d/0B-kVrTmiDKTlRUVZZ3JtZnNiMk0/view?usp=sharing


1) When did this start occurring? i.e. started to happen when i updated my drivers/windows or added a game/program
I think it started after installing a Developer Preview Windows version, but I unstall and Install a no preview version


2) Is windows 10 the original O.S., If not was it an upgrade? - how was it installed i.e. clean install or just upgraded from the previous windows version x.
The windows is original and was installed on Windows 8.1 that came from the factory.


http://imageshack.com/a/img923/1900/wMnHh6.png


3) Is windows 10 fully updated?
Yes, it is fully updated


http://imageshack.com/a/img923/7127/5YZTEL.png

Bravoexo
02-20-2017, 03:41 PM
Try disabling Fastboot

alan.goncalves
02-21-2017, 02:17 AM
Try disabling Fastboot

I have made the settings so that fastboot is turned off:

http://imagizer.imageshack.us/v2/1024x768q90/922/rOLCFE.png

http://imagizer.imageshack.us/v2/1024x768q90/924/9eqg3l.jpg

I'll conduct some tests over the next few days to see how the notebook behaves. Thank you very much for the support of the community. Thank you for now!

alan.goncalves
02-21-2017, 12:15 PM
I have made the settings so that fastboot is turned off:

http://imagizer.imageshack.us/v2/1024x768q90/922/rOLCFE.png

http://imagizer.imageshack.us/v2/1024x768q90/924/9eqg3l.jpg

I'll conduct some tests over the next few days to see how the notebook behaves. Thank you very much for the support of the community. Thank you for now!

Trouble continues even though fastboot is disabled :(

Julskey
02-21-2017, 03:52 PM
We can't see fast boot in your BIOS picture. Fastboot in bios settings is different from fast startup in windows settings.

Julskey
02-21-2017, 03:55 PM
have you tried to fully uninstall gpu drivers using DDU? If not, it is worth a try. Then install the latest drivers from NVIDIA.

Armesis
02-23-2017, 07:24 PM
This is a common problem with new rog laptops, it means the screen will fail soon. Ive replaced mine once already after 5 months, and the problem is coming back again.

alan.goncalves
02-23-2017, 11:55 PM
I will try to take my notebook to Asus technical support. The problem is that it does not exist in Brazil and it is an Asus here refuses a support for notebooks from other countries like The United States, as is my case. :(

alan.goncalves
02-26-2017, 02:08 AM
http://imagizer.imageshack.us/v2/1024x768q90/923/kr97kx.jpg

I do not know why, but by changing this property in the notebook's BIOS, the problem has stopped occurring. Could anyone tell me the reason?

I will follow in the next 3 days how the computer behaves, however, in several tests, the problem has disappeared! :p