[SOLVED] 2 BIOS beeps but computer works fine

[leonthelatino]

Motherboard: Gigabyte B360 HD3 ATX LGA1151
RAM: G.Skill Aegis 16 GB (2 x 8 GB) DDR4-2400 CL15

Hello, first post on the forums.

Recently I started getting two quick bios beeps while using my computer. I looked them up and they meant there was memory parity error. This made no sense to me as I had recently replaced my memory. I tested them using Memtest86 and both of my memory sticks passed. I also updated my bios to the latest version but I am still getting those dang beeps. I've also reseated my RAM just to make sure, but again I'm still getting the beeping. I am at a loss at what is causing this problem. My PC is working fine. I have zero issues and am able to use it for gaming everyday (Black Ops Cold War and League mostly) and experience no problems playing. The only thing is the beeps; they keep happening.

Any help would be greatly appreciated as the beeping is starting to get more and more on my nerves. Thanks in advance.

 

[Darkbreeze]

Gigabyte, two SHORT beeps, system fine/normal.

https://www.gigabyte.com/Support/FAQ/816

If it bothers you, I'd simply unplug the system speaker, until and unless you have some problem at some point, in which case you can then plug it back in in order to determine the error code. Unless of course there are any debug lights staying on abnormally or other problems happening, which it sounds like there is not.

 

[leonthelatino]

The beeping is coming from my headphones though. Would that mean they are not bios beeps and something else instead? I can't unplug my headphones because that's how I play games.

 

[Darkbreeze]

I've never known BIOS error beeps to come through headphones. If in fact that's "a thing", it's a really new thing. When, exactly, do the beeps occur?

 

[leonthelatino]

They just occur at random times. After reading your reply and thinking about it for a bit, I went ahead and updated my sound drivers; they were out of date. I suspect now that might be the issue. I will report back to see if that fixes the issue.

 

[Darkbreeze]

Definitely COULD be the case. I'd recommend that you visit the motherboard product page and update ALL of the drivers for chipset, LAN, WiFi, audio and also make sure that you are currently running the MOST recent non-beta BIOS version as well.

For the chipset, when possible, I like to get the chipset driver directly from Intel, so the 300 series chipset drivers are available here:

https://downloadcenter.intel.com/download/29634/Chipset-INF-Utility


That driver is from May of 2020. If there is a more recent one available through the motherboard manufacturer, which in this case there is, dated June of this year, I will usually recommend getting whichever one is the newest but in this case they are probably both the same chipset driver version since the Intel one was released at the very end of May and the Gigabyte one was from the beginning of June, so likely they are identical and you can use either one. Normally, I recommend whichever is newer and that is USUALLY the one from Intel. Same goes for the chipset drivers on AMD based boards, if you ever work with any of those.

 

[leonthelatino]

I think updating the drivers has solved the issue. I should have thought of the simplest thing first. Thanks for the help, I appreciate it.

 

[Darkbreeze]

For sure Leon. From one Leo to another, my pleasure.