PC startup stuck on MB splash

Solution
The first thing you should do is to try and make sure everything is seated properly. Make sure the graphics card is in the motherboard securely, the RAM, etc. It could be that when you tripped over the cable that something was pulled/shaken loose. If a component is in, but not secure, then it could shake slightly and work then after a hard stomp beside the PC get shaken again and stop functioning. That is your best chance of fixing it cheaply and quickly.

After you do that, if the problem persists, you could try downloading a BIOS update and installing from inside the BIOS, as it could be an issue with the motherboard and not related to the HDMI cable getting pulled. The motherboard could also have been damaged, however, and ultimately...
Wow I thought I had posted the whole story but I guess not.

OK SO
December 2015 I had my PC attached to my TV instead of my monitor . I tripped over the HDMI cable and broke the end in the PC. I shut down the PC took the HDMI part out, got a new cable, but when I booted up I got stuck on the MB splash screen. I decided to leave it until a few weeks ago. All of a sudden it's a-ok, then yesterday it did the same thing.

My specs are as follows:

CPU -AMD something, I don't remember at the moment
MB - ASUS DDR3 2100+
Ram - Corsair Vengeance 2 X 4GB sticks
HD - Western Digital Blue 640 Gigs
Graphics - EVGA GeForce GTX 770
Power Supply - Corsair CS 750M

The only thing I've noticed that might help is that on the MB there's a little two digit screen the displays Letters and numbers (I assume some start up code) it goes through until it flashes 99 then goes black along with the power and reset buttons the MB has next two it (normally they glow red)

Thanks for reading
-Anthony
 
The first thing you should do is to try and make sure everything is seated properly. Make sure the graphics card is in the motherboard securely, the RAM, etc. It could be that when you tripped over the cable that something was pulled/shaken loose. If a component is in, but not secure, then it could shake slightly and work then after a hard stomp beside the PC get shaken again and stop functioning. That is your best chance of fixing it cheaply and quickly.

After you do that, if the problem persists, you could try downloading a BIOS update and installing from inside the BIOS, as it could be an issue with the motherboard and not related to the HDMI cable getting pulled. The motherboard could also have been damaged, however, and ultimately need replaced. But obviously you wouldn't want to do that until you have tried everything else first.
 
Solution
If it's stuck on the BIOS SPLASH, then how does one go about updating the BIOS ?? makes me wonder a bit.. But anyways, most of what IInuyasha74 said is true.. My suggestion what would be to try and rebuild all components - CPU, RAM, Hard disk et all -- take them all out and re-install them again.. If you are lucky, You'll probably get away by fixing/tightening some loose connections and your worries would be over.. Otherwise you may have to replace the M'board if a core component is damaged..

A trip to the local repair shop, might be a very good idea but only of their charges are less than 20-30% cost of a new Mboard..
 
He said it hangs on the BIOS splash screen, not that it was unresponsive. Any number of errors could be occurring. He didn't mention if he tried to get into the BIOS or not, which would just take the push of a button. His motherboard may also have a built-in flash utility to let him flash the BIOS from a USB stick without having the system powered up at all. Asus places this feature on many of their motherboards.
 
Howdy! Sorry for the long response wait. IInuyasha, you were right/your suggestion worked!

I went ahead and disconnected everything, moved my graphics card to a different slot (I wondered if maybe that particular slot caused a problem? I doubt it since my motherboard doesn't any built in display and I was still able to see my Bios splash screen) BUT I then reconnected everything and it's working fine now! I guess something had been dislodged a bit, but I don't really have any way of knowing. Either way I'm happy and thankful for your suggestion.