Hi all,
I've built a new pc containing a Gigabyte z77-hd3 motherboard, i7 2600k CPU, 4x4GB DDR3 corsair vengeance ram, EVGA GTX 580 gpu, ocz vertex 2 ssd and I put my corsair 650w tx psu in there.
My problem is, as soon as I power up the system it will constantly beep similar to a truck backing up. This will go on for about 10 minutes while I am able to do my browsing etc, then it will stop. This is a huge annoyance as I use this while people are sleeping.
The second problem, probably linked to this is when I restart my PC after the beeping has stopped, it will hang on the Gigabyte bios screen and not let me do anything or boot.
I will then have to turn my pc off by the power and leave it for 10 seconds. When I turn it back on the beeping begins again, and the same story happens as above.
Now I have turned my pc on without RAM, gpu, cpu, drives and fans. The beeping still exists. Obviously I hear the beeping for about three seconds when the ram and cpu are out.
But yea, it's obviously my motherboard.
Any advice on a fix or should I send this back?
Thanks
chris
I've built a new pc containing a Gigabyte z77-hd3 motherboard, i7 2600k CPU, 4x4GB DDR3 corsair vengeance ram, EVGA GTX 580 gpu, ocz vertex 2 ssd and I put my corsair 650w tx psu in there.
My problem is, as soon as I power up the system it will constantly beep similar to a truck backing up. This will go on for about 10 minutes while I am able to do my browsing etc, then it will stop. This is a huge annoyance as I use this while people are sleeping.
The second problem, probably linked to this is when I restart my PC after the beeping has stopped, it will hang on the Gigabyte bios screen and not let me do anything or boot.
I will then have to turn my pc off by the power and leave it for 10 seconds. When I turn it back on the beeping begins again, and the same story happens as above.
Now I have turned my pc on without RAM, gpu, cpu, drives and fans. The beeping still exists. Obviously I hear the beeping for about three seconds when the ram and cpu are out.
But yea, it's obviously my motherboard.
Any advice on a fix or should I send this back?
Thanks
chris