Black screen, PC still running.

Ahlbeck

Reputable
Aug 23, 2015
2
0
4,510
So I'm currently trying to fix my brothers PC (A prebuilt Acer Predator G3620).

As the title suggest he gets a black screen after awhile. This seems to be at random but occurs 5-10min into booting up. Afterwards I can't seem to start it without turning the pc off and on again even though it seems to run perfectly fine.

I have tried:

a different GPU

Settings for screen saver

A different monitor cable

Now I'm currently trying to check the RAM.

Im thinking it's the mobo or PSU but seeing as it starts i dunno. I checked other threads about this here and on google but I need all the help I can get seeing as my brother is very flustered about this.

edit: I have now tried a diffrent PSU but that one might be busted as well? Since I got the same result that is. And I tried a different monitor and got the same result.
 
Solution
I'd try reseating all the cables and connections. Since you already tried another GPU, monitor, and PSU, they're not the problem. Any luck w/ the RAM test? Also, what about running in SafeMode, or even a bootable Linux Live CD, and leave it on for an hour or so to see if it's a Windows problem.
I'd try reseating all the cables and connections. Since you already tried another GPU, monitor, and PSU, they're not the problem. Any luck w/ the RAM test? Also, what about running in SafeMode, or even a bootable Linux Live CD, and leave it on for an hour or so to see if it's a Windows problem.
 
Solution

Ahlbeck

Reputable
Aug 23, 2015
2
0
4,510


Hey Liquid.

I made sure to reseat all the cables/connections while testing another PSU. Still going for the RAM approach. I'll try the safe mode. What would most likely be 'broken' at this point?

Thank you!
 
Based on current test results, along w/ hardware tested, I'd say an odd OS bug, or a motherboard, if RAM and PSU check out. This is why I was thinking about the bootable Ubuntu Linux OS disc. Being that it runs from the CD itself, if it's a hardware problem, you should get the same result. If not, most likely the Windows install or driver hiccup.