URGENT - Stuck at motherboard splash screen after installing new GPU with one beep

SkyHawksGamers

Reputable
May 18, 2014
82
0
4,630
Hello. This is a serious issue for me and I honestly have no idea how to solve it. Any help would be greatly appreciated.

This is what has happened:

  • ■ Firstly, my computer was working fine yesterday. My specs are an i7 3770k, a GTX 660, and 8GB of Patriot RAM.
    ■ I received my new GTX 1060 today and replaced the GTX 660 with it. The installation went fine and I grounded myself beforehand.
    ■ After attempting to start the computer again, I saw the Gigabyte splash screen that usually appears for about two seconds before booting Windows. I also heard the signature "beep" - I believe it's known as a "POST beep" - that my computer has always made.
    ■ The computer is effectively stuck on the splash screen, and I am unable to input any commands - e.g. to go into the BIOS - although the keyboard itself is working, as I am able to enable and disable caps lock and such.
    ■ So far I have heard of two main solutions, which are: clearing the CMOS and updating the BIOS. I am not familiar with how to do either of these.
    ■ Sadly, I also do not know my motherboard model, since my PC was pre-built. However, it is Gigabyte, and all of its exposed features can be seen in the images below.
    ■ I have found what looks to be two pins labelled "CLR_CMOS" (shown in the last image) but I do not know how to activate them.
    ■ I have reason to believe that removing the GTX 1060 or putting my old GTX 660 back in would allow my PC to start normally again, although I do not want to do this unless it's truly necessary.
    The issue can clearly be seen in the video below.
[video="https://www.youtube.com/watch?v=TrBRRkZ_CKE"][/video]

Images of the motherboard:
http://postimg.org/gallery/1ekwd0rwi/

Thank you so much for any help. Please be as thorough as possible with solutions as I am fairly ignorant when it comes to motherboard/BIOS issues.

EDIT: SOLVED IT!

Following this video step-by-step fixed it for me. It was a BIOS issue. https://www.youtube.com/watch?v=aKTNwboL9Ho
Thank you all, nonetheless. I hope it fixes it for you, too.