Several symptoms, not sure what's causing it...

thebigdipper316

Prominent
Dec 23, 2017
2
0
510
Hi all, here goes:

Upon turning on my PC over the past couple of months I found that it gets as far as the "Press F2" screen (not sure what it's called) but it won't boot the OS from the hard drive. Repeated restarts (sometimes 1, sometimes 3 or more) got it to boot properly.

I ran the hard drive error check but that brought back nothing of concern.

THEN...

Over the last week I've had 3 crashes - no blue screen, nothing in the Windows Reliability report thing, just complete seize-ups. The sound goes to a constant tone and the screen stays on, frozen on the last thing I was doing before the crash, and I had to power it off and on to get it working, which resulted in some more of the above issue.

Now, after the 3rd crash, it won't boot the OS at all, no matter how many times I restart it, nor will it allow me to press F2 or Delete to get into the motherboard settings.

While I built this PC myself, with plenty of advice from others, I'm in no way an expert, and in particular I've little experience with troubleshooting - this is my first real problem in the 3 years I've had it. Despite that, I've played it safe and gone into the guts of the thing and tried the following:

Detached and reattached all cables
Swapped cables for spares/Tried cables in different slots (I don't know what they're called - the ones that connect the hard drive to the motherboard and the power cables mainly)
Powered on with nothing plugged in

None of that changed the outcome.

THEN...

Almost ready to give up, I noticed that one of the two fans on my graphics card wasn't spinning. I've tried different power cables to it, but no change.

So my question is this:

Does this sound like the graphics card's fan problem is causing all these issues? Or is that irrelevent? Could it be the motherboard or the hard drive or something else entirely?

Like I say, I'm no expert, so I'd really appreciate some expert advice on what the issue is, and how I'd go about fixing it.

Thank you so much in advance, I'd be scuppered without this site and you wonderful people.

Ok, here are the specs, as best as I can detail:

Motherboard: ASUS M5 A97 R2.0
CPU: AMD FX 6300
Memory: 2x 4GB Corsair Vengeance LP
Graphics Card: Sapphire HD 7870 GHz Edition
HDD: WD Caviar Blue 500GB
OS: Windows 10 Pro x64
PSU: XFX Pro 550w
 
Solution
You have components that are relatively power hungry, yet you don't mention the power supply. So that's where I'd start. Nothing is going to work if there's no power.

I'd either try another power supply in this system, or try your power supply in a working system.

I don't think the fan is the cause. It could be a motherboard issue because other than the power supply, the motherboard is the one thing that could cause everything to not work.

MasterWigu

Honorable
Aug 19, 2016
121
2
10,765
I can't check if the stopped fans can be a problem or not, because some GPU's can be working with the fans stopped.

Given all the problems, did you try reseting the CMOS? By removing the battery or shorting the jumper on the motherboard?
 
You have components that are relatively power hungry, yet you don't mention the power supply. So that's where I'd start. Nothing is going to work if there's no power.

I'd either try another power supply in this system, or try your power supply in a working system.

I don't think the fan is the cause. It could be a motherboard issue because other than the power supply, the motherboard is the one thing that could cause everything to not work.
 
Solution

thebigdipper316

Prominent
Dec 23, 2017
2
0
510


Thank you for the suggestion. I hadn't tried this, but I just did the jumper method and it didn't solve the problem. Is it worth me doing the battery method just in case?




Thank you for responding. You're right, I forgot the PSU, sorry about that.

It's an XFX Pro 550w. Unfortunately I don't have the option to test it as you suggest. Before I pay a pro to do that, is there any other test or indicator I can try that may clue me in as to whether it's this or the motherboard that's the cause?