BSOD and not booting/posting after removing GPU

[quinncooper1988]

Specs:

i5 Skylake 4ghz
XFX850watt Gold PSU
16GB RAM DDR4 2666
Gigabyte Gaming K3
R9 390
Win 10

I was running a crossfire set up with two 390's until I sold my primary card. I then moved the secondary card into the primary slot to make use of it's 16x speed.

When I booted it up today, everything worked as it should, expect a minute into booting while it was updating a game, I got the BSOD.

I powered the machine down, and tried to reboot. Everything whirred up as normal, but nothing displayed on the screen, waiting perhaps 15secs, the PC would then power itself down... 5 or so seconds later, boot itself back up and go through the same process unless I forced a power down.

Speaking to a friend they had something similar albeit they didn't do anything with the GPU, they removed the battery on the MB and put back in, and everything worked as it should thereafter.

Do you think this could be a driver issue? (I hadn't wiped/reinstalled the drivers while removing the GPU) or could it be something else?

Both GPU's worked fine before, and they're hardly used as I use the PC mainly for Lightroom and Photoshop.

 

[Sohom]

No extra cables. Got satas but no 6/8pin blocks

ok, no issues there as you tested with two cables... It seems your gpu is faulty but i still cant believe it that if the gpu was faulty how did you get the performance of crossfire... So, i guess the component causing the issue is confirmed... I do believe though that the gpu never was working and actually you were using a single gpu all this time...

 

[quinncooper1988]

Crossfire had been stuttery for me on a lot of games. But I put this down to 1: its crossfire... 2: 2nd slot is only 4x speed.

So thought it was generally normal in those circumstances.

I've never had any crashes. Faults. Hardware detectors picked up the 2nd GPU (this one) fine every time and reported back fan speed/memory clock/usage etc etc

Some games (not all). Usage during crossfire for the 2nd GPU only would often go 100%>0%>100%>0% and so on. While the first GPU was always around 97% ish.

90% of the time since I've had crossfire I turned it off. Due to stutters and that one card was sufficient.

Stuttering wasn't in all games though either. Titanfall 2 I think, seemed to run fine (unless there was no mgpu support for that and it ran in single GPU mode) but was getting crazy fps at the extreme presets.

So never doubted the GPU didn't work, more crossfire didn't work how I expected

 

[Sohom]

Crossfire had been stuttery for me on a lot of games. But I put this down to 1: its crossfire... 2: 2nd slot is only 4x speed.

So thought it was generally normal in those circumstances.

I've never had any crashes. Faults. Hardware detectors picked up the 2nd GPU (this one) fine every time and reported back fan speed/memory clock/usage etc etc

Some games (not all). Usage during crossfire for the 2nd GPU only would often go 100%>0%>100%>0% and so on. While the first GPU was always around 97% ish.

90% of the time since I've had crossfire I turned it off. Due to stutters and that one card was sufficient.

Stuttering wasn't in all games though either. Titanfall 2 I think, seemed to run fine (unless there was no mgpu support for that and it ran in single GPU mode) but was getting crazy fps at the extreme presets.

So never doubted the GPU didn't work, more crossfire didn't work how I expected

Ok, that explains it. because in titanfall 2, crossfire performance was stuttery but not when using sli. I actually dislike the idea of sli or crossfire except for ethereum or bitcoin mining rigs.... Hope you have warranty on the graphics card left... My advice would be always go for single good gpu than dual gpu's...

 

[quinncooper1988]

Thanks a lot for all your help Sohom! Really appreciate it

I'm hoping I've got warranty left on it too now. Definitely won't be looking into mgpu again. as say for most part id turned off the second GPU either stutters or lack of support.

See what they'll do about this whether repair or send a new unit out and perhaps look at going for a 1080 or vega depending how that pans out (have freesync)

 

[Sohom]

Thanks a lot for all your help Sohom! Really appreciate it

I'm hoping I've got warranty left on it too now. Definitely won't be looking into mgpu again. as say for most part id turned off the second GPU either stutters or lack of support.

See what they'll do about this whether repair or send a new unit out and perhaps look at going for a 1080 or vega depending how that pans out (have freesync)

Glad that i could help... Hope everything turns out good... Dont go with 1080 if you have a 1080p or a 1440p display, rather go for 1070 because thats the sweet spot; You can obviously wait for vega or get a 1080ti, if you are planning for 4k but then also they struggle with 4k...

 

[quinncooper1988]

I'm running 1440 and no plans of going 4K. Thanks for the tip on the 1070, save me a few ££'s

 

[quinncooper1988]

So... some further info and confusion.

I got an Nvidia GPU off my mate that's a known working card. Plugged that into PCIe slot 1 and it did NOT work. Exact same issues as my card.

Tried slot 2 and the same.

Tried on NO GPU using integrated and booted up fine.

Plugged my GPU into slot 1 and his GPU into slot two, connected the display into my slot 1 GPU. And it worked. As normal.


So somehow my GPU works but ONLY with two GPU's present on the motherboard. Despite them being one AMD and one Nvidia so aren't compatible by any stretch. And somehow it works.

When only one GPU plugged into slot one. Nothing works.

Checked BIOS and couldn't see anything obvious that I needed to change.

So I'm rather baffled to be honest.


Anyone come across this before, suggestions?

Thanks

 

[quinncooper1988]

Seems I've got it working now.

Just doing a furmark GPU stress test and all looking good.

Hadn't done anything in particular, only this time reseated GPU in PCIe 1 but did not connect the power cables. Started up fine. Powered down and connected power cables restarted and it booted up, which I was t expecting.

Installed drivers and running furmark. Can only suggest it wasn't seated properly or a loose connection. How, I don't know as they'd been taken in and out many times and pushed in hard to make sure. But. Only logically explanation