computer tech help

Post Reply New Topic

kazanscube here, I'd like to present the following conundrum which I'm currently trying to resolve.
Basically, I can't seem to figure out why I incur the ,"no signal message" when I start up my pc? Yes, I've done some various searching on the internet to determine the root source be it the following issues.
1bad/defective power supply< this is not the case for my entire motherboar comes on and I'm able to use all my components except my graphics card presents the above mentioned error
2improperly seated ram- nope<I have removed all 4 sticks of memory and reseated them properly and in correct positions as such, so that does not seem to the source.
3crappy hdmi cable< not really for, I've used this same cable to connect to my blu ray player-tv and it works in that scenario.
4.doa graphics card< I'm not sure on this speculation for, I recently had previous graphics card than the one I currently use. ** previous graphics card xfx R9 390 8gb *current pny Nvidia Geforce 950
5. non-working pci express lane(s) <I'm going to doubt the possibility of such then again my onboard lan uses the pci express 1x lane wherein, would not one work means the rest work?

Lastly, windows downloaded the newest NVidia drivers despite the fact, I don't currently have my video card installed rather, I've been using my onboard graphics till I can figure this crap out..

Any help will be appreciated..

"No Signal" typically is put on the screen not by your PC itself but by the processor inside your screen. It's merely telling you that the screen is on but it's not receiving a signal from the PC. This message may appear several times between turning on your system and Windows finally allowing you to log in as the video hardware gets initialized. If you are seeing it *after* Windows boots up and you see the login screen or desktop, it's very likely a problem with your video card (or embedded video hardware if no separate card).

If you are only seeing it during boot up and then not again until the next time you boot up, it is completely normal and tells you the screen is up and running correctly and is waiting for the PC to finish booting up. In that case it can be simply ignored.

I only receive the no signal message whenever I have installed on my graphics card not, when I'm using on my onboard graphics chip, yet I received this message with two different graphics which I'm used on my motherboard. As, I had stated in my previous post, windows update downloaded the Nvidia graphics driver yetm this action happened when my discrete graphics card was not installed which makes me wonder, that is strange indeed unless, there is the possibility I could install my card oncemor and I might not get the stupid message? I'm not sure if this is relevant or not? But, I had to reboot my system many times for my onboard audio chip to be detected as was the audio driver for chip too?

There is usually a BIOS setting to tell the system to initialize the on-board graphics or slotted card for the boot process. If this doesn't match what you are trying to connect to, there won't be a signal to the monitor until windows loads and does its own hardware detection.

Yes, I did go into bios originally when installing my graphics card and set it to use pci express slot 1 as well disable onboard graphics but, still received the stupid message therefore, I'm at a loss as this happened with both graphics cards I had tested..

Basics:
Does the PCIe card show in Device Manager?
Have you installed the drivers for your board chipset?

1. no the graphic card does not show up in the device manager.
2. Yes, I did install the chipset driver right after installing window 10 pro 64bit version

If your monitor is saying "no signal" when you turn your PC on, I wouldn't worry about it as long as it's otherwise working fine. Sometimes displays and video cards take a few seconds to initialize at startup.

BTW, why did you switch from an R9 390 to a GTX 950? I've heard the R9 390 is supposed to be better than the GTX 970.

Well, finally was able to not only get my graphics card detected and is working in optimal order. the main reason for the problem was due to Windows 10 Pro 64bit being wonky about things..
Now as to why, I switched graphics card? Well, the R9 390 was so massive I found it hard installing with it creating cable management problems even, if I have a atx mobo and Full tower case.

Congratulations!

What wonkiness did you run into, out of curiosity?

As long as you get a signal on both screens after logging in to windows, this is a non-issue.
I myself get the bootscreen/bios statements on my secondary screen (laptop+screen setup, the laptop is the primary screen according to the BIOS), but i simply ignore it since it works as intended when windows starts loading.

What sort of wonkiness? Well, Windows 10 Pro as Windows 8 when it was initially released had the same problem as, both OS tended to not detect the graphics card in a fairly quick manner. In that in both of those scenarios I had to uninstall & reinstall the graphics card multiple time among many reboots for both Windows OS's to finally acknowledge such.. I had read about this with both systems therefore, maybe not all persons encountered this issue but, some did like myself. I hope I have presented myself and my difficulty in a clear manner.

Thank you. I've heard & read about the difficulties with some fairly recent ATI cards not being recognized by Windows / initialized by the BIOS (but only for specific boards & BIOS versions). We've also seen a few in our IT dept. where the graphics card will not be able to correctly talk to the BIOS in some PCI-e slots, but work beautifully in others. Sometimes it'll even be the opposite of what the manual seems to indicate (if there are multiple x16 slots).

I've noticed that on install, Win10 may not need as many reboots, but it does a huge number of largely undocumented updates & saves them up for the few reboots. This results in an only partially functional system until it is done. And some hardware may not be fully functional until the last reboot. Something else I've noticed is that with some advanced video cards, MS will install with a basic driver for that brand (based on the hardware ID). Then the user/tech installs the latest driver set from the card maker or card chipset maker. Then windows will *reload* the latest version of the original install driver *because it thinks it is newer*. The OS at that point is a mess and the system drops back to the basic drivers. Sort of, because it's running off the ones loaded but the libraries on the disk are now potentially a mixed set.

Here's our procedure for GPU graphics cards (ie non-servers):
1. Install/update windows.
2. Run all updates, get all reboots out of the way. Verify system is stable.
3. Enter safe mode, uninstall the video drivers.
4. Manually install the latest drivers downloaded from ATI or card vendor.