No output to monitor after recent storms (PC was off)

Soldato
Joined
11 Oct 2011
Posts
3,335
Location
UK
Hi all,

As above

Not my PC, but one I'm going to take a look at tomorrow

Guy says it appears to power up, fans, etc but no output

My first guess is PSU... Anything else to check?

Thanks :)
 
if the PC powers up etc it sounds like it may have friend the GPU.

try the clear cmos but then try a different output port on the gpu, check gpu power cables and try a re seat of the gpu as well.

if he has a on board gpu try that or if you have a spare gpu take it with you to rule it out
 
if the PC powers up etc it sounds like it may have friend the GPU.

try the clear cmos but then try a different output port on the gpu, check gpu power cables and try a re seat of the gpu as well.

if he has a on board gpu try that or if you have a spare gpu take it with you to rule it out

I'm guessing it is going to have an onboard only (haven't seen it yet) but he is not a gamer so just guessing until tomorrow

If I can confirm that it is powering up correctly I will try my GPU in it... No chance of damaging my own GPU?
 
Depends on what is the cause of the "no output". If the motherboard is fried then the probability of your GPU frying if you plug into it is quite high. If it's just a case of the PSU has given up the ghost, then you won't do any damage. Good luck :)
 
Depends on what is the cause of the "no output". If the motherboard is fried then the probability of your GPU frying if you plug into it is quite high. If it's just a case of the PSU has given up the ghost, then you won't do any damage. Good luck :)

Quite wary to put my GPU in it then haha

I'll see if I have a cheapo one anywhere if it comes to that haha
 
Before trying graphic cards, I'd want to try another monitor. It's possible the monitor has just blown a fuse.

I did think that, and will still check it, but the guy said he thinks there is a "no signal" message on the monitor so that seems to be okay
 
I had this same problem with my computer after the storms, I just turned everything off at the plug for 20 minutes and then it all worked fine. Not sure what caused it though.
 
User says this fixed itself while powered off overnight

So likely that whatever it was, a CMOS reset would have probably solved it
 
Back
Top Bottom