As some may have noticed my GPU died last week.
So i bought a new one.
All i got was checking Signal.
So i thougt either the PSU and or mobo died also.
First i replaced the PSU, no change.
Today i replaced the mobo, and wtf i still get the s same error.
Any help is much appreciated.

---

With each crime and every kindness we birth our future.

As some may have noticed my GPU died last week.
So i bought a new one.
All i got was checking Signal.
So i thougt either the PSU and or mobo died also.
First i replaced the PSU, no change.
Today i replaced the mobo, and wtf i still get the s same error.
Any help is much appreciated.

Well logic suggests that you still have something connected that has been there all along, so memory, have you changed that.

Also I once had a bad USB drive that stopped the machine booting.

Other than that I cannot think of anything.

---

As some may have noticed my GPU died last week.
So i bought a new one.
All i got was checking Signal.
So i thougt either the PSU and or mobo died also.
First i replaced the PSU, no change.
Today i replaced the mobo, and wtf i still get the s same error.
Any help is much appreciated.

Try a different monitor, or repower your existing monitor.

Claggy

My answer may seem impertinent, since I am sure you have already checked what I am suggesting to do.
But since nothing seems to work, here my remote 0.02 cents:

Has your new MoBo an internal GPU?
In that case you should probably deactivate that from the BIOS.
So, that would be reconnecting the monitor to the MoBo, change the BIOS setting, connect to the external GPU and hope for the best! ;-)

I am very sorry if I said something which is totally not reflecting your configuration (e.g. a high standard mobo usually has no embedded GPU), but I could not resist trying to help! :-)

Sleepy

Or try a different (VGA) cable.

---

As some may have noticed my GPU died last week.
So i bought a new one.
All i got was checking Signal.
So i thougt either the PSU and or mobo died also.
First i replaced the PSU, no change.
Today i replaced the mobo, and wtf i still get the s same error.
Any help is much appreciated.

Same thing as when I bought the R9 290X for my older ACER computer. No matter what I did, including upgrading the BIOS, "no signal" was the only thing the monitor said. I tried hundreds of different ideas for a solution, but nothing helped.

That computer worked fine with the R7870 (until the sleeve bearings on that cards fan finally gave up), and of course with the original HD4850, which it still runs with now.

So, I finally gave up and bought a new computer, which had a GTX 980 in it. I was still curious of course about the R9 290X, so I put it in this new computer, and there was no problems at all. I may install it properly this winter, but for now I only run it with the GTX980.

There are thousands of questions and answers on the net about this issue of no signal, with certain GPU and MOBO combinations though. That issue is not uncommon, and most of them doesn't seem possible to solve.

Edit: Since you have a much newer MOBO though, I remember another guy with a similar problem, with a new MOBO, who found that if he unplugged the computer from the mains voltage totally, and then held down the start button for 30 seconds, the next time he plugged it in to the mains voltage (the wall socket), and pushed the start button, the GPU would all of a sudden come alive, and the problem was solved.


Strange solution, but he got several answers to that thread, where other people with similar issues also managed to fix their "no signal" problem in the same way.

This sounds logical. It's most likely a BIOS conflict. I was under the impression you also need to remove the battery from the MoBo to do a total reset though. I have a similar problem with the Re-Released 6970 with the firmware dated Early 2014. It will work in 2 of my boards but won't even post in the other two even though the BIOS is the latest version. The two boards that won't post is an Intel server board the other an Intel desktop board. It works fine in a HP workstation and a ECS desktop board. Sometimes the different firmwares just won't work together, the only solution is to find a pair that will work.

Also I might add the major difference in the 6970 ROMs is the Newer one is UEFI certified, the older ones from 2010 aren't. You can't change it back to the 2010 ROM either, I've already tried. All it displays with the 2010 ROM is a Black screen, i.e. No Signal...

What helped me was: power down pc.
Unplug.
Remove graphics card.
power up.(yes, without graphics card)
Wait 3 minutes.
Power down with power button.
Disconnect from outlet.
Put graphics card in and power up.

This way, the computer "learns" to not have a graphics card and next time, when powered up will extensively search for a new one.

This may take up to 15 minutes.

Booting without anything conected doesnt work either.

---

With each crime and every kindness we birth our future.

I suspect you exceeding the pci-x limit on power draw or you did not turn the internal video card off in the bios

see if you can turn off the integrated video first or set video to pci-x first

if that don t help you can get a lil pci-x riser cable that has a power plug on it to supply more power to the card to circumvent the pci-x limits

cable is 6 bucks or so on amazon

I run one of those cables on one of my shitty celeron boards ...
i stuck a 980TI on it and no boot added the cable put power to it card now runs like a charm

you can see the machine in my computers it s the ms- one

http://setiathome.berkeley.edu/show_host_detail.php?hostid=7772586

---

I came down with a bad case of i don't give a crap

Can you get to the MoBo BIOS and switch to Legacy mode verses UEFI Boot? Some boards give that option.

that has nothing to do with a no post legacy and uefi is just to boot but he has no post no vid situation

---

I came down with a bad case of i don't give a crap

The mobo dont have internal graphics.

No i cant go to BIOS

---

With each crime and every kindness we birth our future.

can you take a pic of the board or at least give me a model number so i can look it up?

---

I came down with a bad case of i don't give a crap

can you take a pic of the board or at least give me a model number so i can look it up?

Assus sabertooth 990fx

---

With each crime and every kindness we birth our future.

The mobo dont have internal graphics.

No i cant go to BIOS

Too bad. I've determined that's why my Newer ROM won't work on my Intel boards, a UEFI conflict. If you could use an older GPU you could probably get to the BIOS and try different settings.
Oh well...

I am going on record as saying I think it is the CPU itself. This has happened to me before, and is the reason I am running an i7 950, instead of my old i7 980.

I did everything Mike has done, and when I replaced the CPU, everything worked.

Steve

---

Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website

The mobo has cpu LED.
I dont think thats the Problem.

---

With each crime and every kindness we birth our future.

how many pci-x does that board have and did you try all of them with that card ?

also reset the bios with the clear cmos jumper on the board and try again the 990 should have no issues with that card

---

I came down with a bad case of i don't give a crap

Mine did to when it died.
I replaced everything else first, because that was the last thing I thought was wrong. I spent $450 for a new motherboard, substituted a 1300 watt PSU, and still it didn't work. I removed RAM chips, one after another, and still nothing. As soon as I replaced the CPU with an old one, everything worked.

Steve

---

Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website

Mine did to when it died.
I replaced everything else first, because that was the last thing I thought was wrong. I spent $450 for a new motherboard, substituted a 1300 watt PSU, and still it didn't work. I removed RAM chips, one after another, and still nothing. As soon as I replaced the CPU with an old one, everything worked.

Steve

Steve might not be wrong here

also reseating the cpu would be something to try

---

I came down with a bad case of i don't give a crap