Until 2 minutes ago, when starting, my PC would beep 5 times(well, 2 times, 5 beeps each), but it was booting fine, I read that it means "CPU failure"(Z270X-UD5, AMI BIOS), yet it was working fine, just a bit slow when booting(some 15-20 secs on black screen with just a blinking highlight(like in cmd). I just fixed it by resetting the bios. But what could've been the problem? It wasn't like that when I first booted it up(after assembling it myself of course), it started doing that 2 or 3 weeks ago.
5 short beeps means CPU error, I checked since thats a Gigabyte board and I googled it GIGABYTE GA-Z270X-UD5 (rev. 1.0) BIOS Beep Codes | DDR4Motherboard Looks like you need to check your processor mate
Could be bent pin(s) in the socket, or some failure within the CPU. I'd get that checked out immediately, if I were you.
I reset the bios and it works fine. I was working fine from February to 2-3 weeks ago. I haven't disassembled anything.
So that was 10 short beeps, CMOS error, thank god I have dual UEFI BIOS on my motherboard just encase one blows up I have the reserve
well, it's fixed, I was just curious what it could've been because it still worked without problems, once it got into windows.
Consult the manual trust me they always have the answers mine has a Boot order config in mine that some idiot called "Robert" scribbled in at 3am in the morning telling me to correct a boot order config....
It has LED codes, nothing about beeps. I can't see the LEDs from where I sit and I would have to disconnect everything to get it out of it's current place. --- Post updated --- And there are no errors now, so- no way to know what it was complaining about.
well get it up on the table get it all hooked up pop the side panel off and fire up the computer and watch the motherboard
Just a PSA: when you have a beep codes, and your motherboard also has a POST code indicator of some sort, either numbers or LEDs, on the board, open the computer up, and see what POST ccode you have. That will be a lot faster and more accurate than trying to work out beep codes, as there will usually be a lot more information in a POST code, or a loop of codes, than a beep code.
It was fixed before I even wrote this thread. I just wanted to know why it could have been doing that(5 beeps, pause, 5 beeps).