No signal problem

[MilosL]

Hi guys

So my PC lost signal on my monitor one time and I do not know why. What happens is that When I click on the ON switch it boots up for a second or 5 and then my pc turns itself off. The second time it seems to boot normally, but there is no signal on monitor

 

This is a list of things I have tried:

 

Tried a different HDMI cable
Tried a DVI cable
Tried another monitor
Replaced GPU by a new one
Changed RAM stick to other slots
(PSU being broken is small chance. Got a new one 6 months ago and I have about 120 Watts to spare)
I made sure all the cables are in there correctly.

This is a list of my specs:

Gigabyte Radeon R9 270X 2GB but now it is a Gigabyte GTX 1060 3GB
Ryzen 5 1500X
ASUS PRIME B350-M 
8GB RAM x1
1 HDD

620W PSU

So I do not know what could be wrong. Could it be the CPU or the is it the RAM stick. Or could it be my motherboard's PCIe slot. I have 1 x16 slot so I can not test it on another. All fans spin and the LED on my Motherboard turns on too.

Does anyone have an idea of what could be wrong and how I can fix it?

[TheKent]

Have you tried booting the computer without a PCI-E video card, and use the integrated graphics on your motherboard?

It's important that you physically remove the video card before testing, not just switching the cables, or else it wouldn't be much of a troubleshoot attempt.

Does it then still boot and shutdown immediately on cold boot when you use the integrated graphics?

Does the monitor get signal on the second attempt? This could help you isolate the problem, or exclude the video card, at least. 

 

Here's how your I/O should look like, pic taken from the motherboard manual, page 1-8. LINK TO MANUAL

Just have to say that Asus has done a really crap job on the documentation of this board. My guess for troubleshooting this board, would be to connect your computer case speaker to the motherboard, if it has one. If anything is wrong, it should beep in a certain manner that indicates where the fault is located. If it finds no errors, normally a single beep is emitted. I haven't been able to find any manual to "decrypt" these beeps, so you should dig into Google if you want to troubleshoot further.

[MilosL]

Thanks for replying,

 

Unfortunately I do not have any integrated graphics included. So I won't be able to use that. I have also attached a speaker,  but no sound was provided with the boot up. What I have also tried is another CPU, but unfortunately, I still have no signal. What did change was that when I changed the CPU my first Boot was normal. I did not have to click on the ON switch for a second time to turn on my pc. 

 

Any chance you now know what's going on?

 

 

On 3/30/2019 at 1:09 AM, TheKent said:

Have you tried booting the computer without a PCI-E video card, and use the integrated graphics on your motherboard?

It's important that you physically remove the video card before testing, not just switching the cables, or else it wouldn't be much of a troubleshoot attempt.

Does it then still boot and shutdown immediately on cold boot when you use the integrated graphics?

Does the monitor get signal on the second attempt? This could help you isolate the problem, or exclude the video card, at least. 

 

Here's how your I/O should look like, pic taken from the motherboard manual, page 1-8. LINK TO MANUAL

Just have to say that Asus has done a really crap job on the documentation of this board. My guess for troubleshooting this board, would be to connect your computer case speaker to the motherboard, if it has one. If anything is wrong, it should beep in a certain manner that indicates where the fault is located. If it finds no errors, normally a single beep is emitted. I haven't been able to find any manual to "decrypt" these beeps, so you should dig into Google if you want to troubleshoot 

 

[Chippyz]

5 minutes ago, MilosL said:

Thanks for replying,

 

Unfortunately I do not have any integrated graphics included. So I won't be able to use that. I have also attached a speaker,  but no sound was provided with the boot up. What I have also tried is another CPU, but unfortunately, I still have no signal. What did change was that when I changed the CPU my first Boot was normal. I did not have to click on the ON switch for a second time to turn on my pc. 

 

Any chance you now know what's going on?

 

 

 

Could be broken RAM,mobo or even PSU.

Which PSU and RAM exactly?

[TheKent]

 

11 minutes ago, MilosL said:

Thanks for replying,

 

Unfortunately I do not have any integrated graphics included. So I won't be able to use that. I have also attached a speaker,  but no sound was provided with the boot up. What I have also tried is another CPU, but unfortunately, I still have no signal. What did change was that when I changed the CPU my first Boot was normal. I did not have to click on the ON switch for a second time to turn on my pc. 

 

Any chance you now know what's going on?

 

 

 

The speaker should have emitted a noise if something was wrong with the memory or CPU, but that's just what seems logical to me.

What I would do from here is start taking out components (RAM, CPU) and try turning the computer on. This is to help to try isolate the problem.

The speaker should at least emit noise when RAM or CPU is completely missing. If the motherboard refuses to give any sort of error/debug codes, it could be a faulty motherboard or PSU, as @Chippyz suggested.

Just read that there should be a few LED's on the motherboard indicating any errors, but I can't find any proof of that in the motherboard's manual...

 

I wouldn't immediately suspect RAM to be the culprit here, because I can't recall a computer in those cases shutting itself down immediately after being turned on, but I could of course mistaken.

 

I'm sorry for not checking that the Ryzen didn't sport integrated graphics! 

 

Quick tip from this forum post with a somewhat similar problem with the same motherboard: https://forum-en.msi.com/index.php?topic=292898.0

 

Quote

I found the problem and fixed it. Thank you for your reply!

It sounds very silly , I have to apologize for wasting your time, there was a standoff touching the mobo bottom causing a short....