[SOLVED] Multiple beep codes coming from motherboard when playing games all the sudden. Help!

[gonfonix]

My motherboard: MSI B350m Bazooka

For a while now, I have had no issues with my computer. But starting 2 days ago, when playing Battlefield 1, I have heard some beeps coming from computer. During that time, there was two. When I looked this up, I saw (for a AMI BIOS), this means a memory issue. So I restarted my computer and checked my ram with Memtest64 and found no issues. So now, two days later, I was playing Battlefield 1 again and heard several beep codes non stop. It got to the point, that there were so many, that I lost count and they just kept coming. I am thinking I have a CPU issue or motherboard issue, but everything seems to be working just fine?

I recorded the sounds. Here is a link. Please listen carefully and help me! This is very important, as I need help for what is wrong. Thank you.

https://soundcloud.com/digitalfunky/weird-beep-noises-from-mobo

If it is difficult to hear the beeps, then I apologize for that. Just turn up your volume all the way.

Here are my system specs to help with the situation:

• GPU - EVGA Geforce GTX 1080 SC 8GB GDDR 5X @1.9GHz
• CPU - AMD Ryzen 7 1700 8 Core (16 Threads) @3.70GHz OC (1.275 volts) (stock cooler)
• RAM - Ballistix Sport LT 24GB Kit (8GBx3) DDR4 2400 MT/s
• MOBO - MSI B350M Bazooka Motherboard
• PSU - CORSAIR 650 watt 80+ Bronze Modular Power Supply
• STORAGE - Samsung 850 EVO 500GB SATA 6Gb/s SSD and TOSHIBA 1TB SATA 6Gb/s 7200 RPM 64MB Cache HDD
• CASE BRAND - Phanteks P400 TG
• OS - Windows 10 Pro

 

[ragnar-gd]

For a first, you get a point from me for creativity, uploading the BIOS beeps to soundcloud is just genius.
Unfortunately, BIOS-beeps are always a mistery, that usually only the producer - in this case MSI - can decipher. In former times these codes were mentioned in the manuals, but alas, no more.
Visit the MSI forums, in 80% of the cases they can help you there. Your soundcloud-idea can go a long way.
It can be a memory issue, be it damage, or failed overclocking, or overheating of some other components. I just can't say. Ask MSI, the board is new, they should have an answer.

 

[gonfonix]

For a first, you get a point from me for creativity, uploading the BIOS beeps to soundcloud is just genius.
Unfortunately, BIOS-beeps are always a mistery, that usually only the producer - in this case MSI - can decipher. In former times these codes were mentioned in the manuals, but alas, no more.
Visit the MSI forums, in 80% of the cases they can help you there. Your soundcloud-idea can go a long way.
It can be a memory issue, be it damage, or failed overclocking, or overheating of some other components. I just can't say. Ask MSI, the board is new, they should have an answer.

I made a MSI forum post just now. Thanks for the suggestion. However, I will take any feedback from this thread also if anyone has any help for me. Thanks.

 

[Sedivy]

From your manual:

If 3 long beeps are heard, remove all memory modules and try to install only one memory module in the DIMMA2 slot first and then restart the computer. If 1 long 2 short beeps are heard, remove and reinstall the graphics card and then restart the computer.

That being said your beeps are all over the place and are supposed to happen on boot, not just randomly.
Try Prime95 and see if it happens with just cpu load. If the test is ok, try Furmark or OCCT and see if it happens with just gpu load. If neither gives you reproducible beep, likely mobo or psu. OCCT will give you cpu+gpu load test to see if it's the psu (assumption that increased power draw is what causes them).
I agree msi will be the most likely place to explain the random beeps.

 

[gonfonix]

From your manual:

If 3 long beeps are heard, remove all memory modules and try to install only one memory module in the DIMMA2 slot first and then restart the computer. If 1 long 2 short beeps are heard, remove and reinstall the graphics card and then restart the computer.

That being said your beeps are all over the place and are supposed to happen on boot, not just randomly.
Try Prime95 and see if it happens with just cpu load. If the test is ok, try Furmark or OCCT and see if it happens with just gpu load. If neither gives you reproducible beep, likely mobo or psu. OCCT will give you cpu+gpu load test to see if it's the psu (assumption that increased power draw is what causes them).
I agree msi will be the most likely place to explain the random beeps.

Okay. Also how long should I run Prime95 for?

 

[Sedivy]

People will say run 24 hours to be absolutely certain of stability of overclock but you don't need that here, and even that I consider a little extreme.
I'd say 2-4 hours max and if there is indeed something wrong with the cpu, I'd expect beeps to happen long before even that, like within first 30 mins. All you're trying to do is reproduce the beeps reliably.
Keep an eye on temps when you're doing this. Use something like hwmonitor or hwinfo or...I forget what's the one to use with amd, I'll have to check, but just make sure your temps are not going over 85-90C. Abort if yes.
Did you run at least 8 passes with memtest? Anything less is not really indicative of stability. Pulling one stick is a quicker way of testing it.

 

[gonfonix]

People will say run 24 hours to be absolutely certain of stability of overclock but you don't need that here, and even that I consider a little extreme.
I'd say 2-4 hours max and if there is indeed something wrong with the cpu, I'd expect beeps to happen long before even that, like within first 30 mins. All you're trying to do is reproduce the beeps reliably.
Keep an eye on temps when you're doing this. Use something like hwmonitor or hwinfo or...I forget what's the one to use with amd, I'll have to check, but just make sure your temps are not going over 85-90C. Abort if yes.
Did you run at least 8 passes with memtest? Anything less is not really indicative of stability. Pulling one stick is a quicker way of testing it.

I found it the beeping was actually my battery backup system right next to my PC haha. So problem solved. Thanks for the help though!

 

[USAFRet]

Always:
Identify the problem before applying a solution.

 

[Sedivy]

Lol....
I'll remember this one for sure for future threads.