Beeps on boot

[ubuysa]

Agreed it's 4 beeps, SYSTEM_TIMER_FAILURE.

First thing to try is removing three RAM sticks and try it on just one stick. Try it again on each of the 4 sticks, one at a time. See whether you get the 4 beeps on each of the RAM sticks.

Late edit after a bit of research: Once you've tried it with all four RAM sticks in individually, try booting again four times and rotate the RAM sticks through the four slots so that each time you boot each RAM stick is in a different slot.

Edit: Also try the suggestion from @Nursemorph to remove and reseat the CMOS battery. TBH, and to be on the safe side, I'd replace the battery - they cost pennies.

 

[VexedED209]

Interesting thank you, I'll do some research on removing the CMOS battery and resetting it and see what happens. Good suggestion on the ram sticks, I'll try that too.

It has been back to pc specialist for this issue plus other issues and on the email I received they claimed that is a normal beep but with limited knowledge I was fairly sure that multiple beeps on booting isn't normal.

What issues is this likely to cause, would it explain fairly frequent crashes?

Again thanks for the patience, I know this is probably very basic stuff for a lot of you.

 

[VexedED209]

You will find the CMOS battery about 3/4 of the way down your board (looking very much like a watch battery)...just pop it out, wait 30 seconds, pop it back in. However, as Ubyusa notes, easier to just replace it in case it's faulty

As to the clocks, the Real Time one is related to the BIOS and that level of the system...the clock you see in Windows is updated via Windows. Or at least that's how I understand it..pretty sure both are unrelated to each other

Ahhh I see, thanks so much.

One of the issues I sent it back for the bios kept losing the xmp profile and the ram was running at approx 2500mhz, I assumed the beeps were something to do with that, the bios now shows them running at 3600mhz but the beeps persist, to which they claimed were normal. Guess I'll have to sit on the phone for an hour again to speak to someone.

Again, thanks for all your advice to everyone that posted.

 

[ubuysa]

One of the issues I sent it back for the bios kept losing the xmp profile and the ram was running at approx 2500mhz, I assumed the beeps were something to do with that, the bios now shows them running at 3600mhz but the beeps persist, to which they claimed were normal. Guess I'll have to sit on the phone for an hour again to speak to someone.

Ah. Remove any and all overclocks, not just on the RAM but on the CPU and GPU if you're using them. You need to test the PC at stock frequencies.

It's entirely possible that the RAM overclock has damaged one (or more) of the RAM sticks. Be sure to properly test with each RAM stick.

It's even worth downloading Memtest, make a bootable USB stick from the extracted tool, and boot that USB stick and Memtest will start running. Leave it running until it's completed all four iterations of the various tests, on your 32GB of RAM that could take more than 24 hours.

 

[VexedED209]

Ah. Remove any and all overclocks, not just on the RAM but on the CPU and GPU if you're using them. You need to test the PC at stock frequencies.

It's entirely possible that the RAM overclock has damaged one (or more) of the RAM sticks. Be sure to properly test with each RAM stick.

It's even worth downloading Memtest, make a bootable USB stick from the extracted tool, and boot that USB stick and Memtest will start running. Leave it running until it's completed all four iterations of the various tests, on your 32GB of RAM that could take more than 24 hours.

To be honest you've lost me there, clearly you've got an incredible amount of knowledge in this stuff but it all goes way over my head.

I haven't done any overclocking myself so there's nothing to undo from my end unless the rams are factory oc'ed to run at 3600mhz and you're suggesting I change that? I wouldn't know where to start. And I don't expect you guys to walk me through it and I don't want to bumble through issues potentially making it worse.

You've answered my question by confirming there is a problem, from there I think I'm going to have to throw it back to pcs to work out which is frustrating but that's what it is.

Again thanks for all the advice and what not, it's helped a lot.

 

[ubuysa]

You said it kept losing the xmp profile and xmp is a RAM overclocking tool.

But if you're not comfortable with troubleshooting then sending it back to PCS would be wiser.

 

[VexedED209]

You said it kept losing the xmp profile and xmp is a RAM overclocking tool.

But if you're not comfortable with troubleshooting then sending it back to PCS would be wiser.

Ah right, not a clue, when I spoke to my friend is who far more tech savvy about the ram sitting at 2500mhz, he asked me to load the bios and see if it was enabled (there was a profile already there) when it was on it would run at 3600 bit Everytime the pc was shut down it would be off at 2500mhz again, so assume that profile is set by pcs by default? 🤷‍♂️.

 

[ubuysa]

Ah right, not a clue, when I spoke to my friend is who far more tech savvy about the ram sitting at 2500mhz, he asked me to load the bios and see if it was enabled (there was a profile already there) when it was on it would run at 3600 bit Everytime the pc was shut down it would be off at 2500mhz again, so assume that profile is set by pcs by default? [emoji2369].

Yes it probably was set by PCS, but RAM is a very likely cause of the beeps you're hearing, so it's essential to have the RAM running at its stock speed for testing purposes.

 

[VexedED209]

Yes it probably was set by PCS, but RAM is a very likely cause of the beeps you're hearing, so it's essential to have the RAM running at its stock speed for testing purposes.

Yeah I get what you're saying. Again I wouldn't know where to start with that so I'll contact PCS.

Thanks to everyone that posted!

 

[Martinr36]

Yeah I get what you're saying. Again I wouldn't know where to start with that so I'll contact PCS.

Thanks to everyone that posted!

When you contact them, point them to this thread

 

[carrot_monkey]

It is entirely possible it is monitor related as @steaky360 suggested...it is quite common for slightly older monitors (and some newer ones) to cause the system issues if it is not turned on before the PC itself....have seen plenty where the computer beeps then loads normally. Try as posted and turn the monitor on first and then power on the system and see if that stops it

Hi

I have experienced the same issue with my new machine and I have found that the solution is it turn the monitor on before booting up.

If I restart it is fine (which makes sense as the monitor is running already).

Bit frustrating to begin as this is brand new and also I do remember that the first time I boot up it did not beep at all. Come to think of it though, most probably I connected everything up and the monitor was still on first time I boot up so it wouldn't appear then.

Hey as long as it doesn't evolve into a bigger issue (I cannot see why) then I can live with it I suppose.

Also I would like to point out that if I boot up without turning the monitor on the beeps indicating GPU error will sound and there will be a white light on the motherboard where the GPU LED error is (I assume that's what that LED is for)

I dag around the internet and this seems to be an issue with the X570 since it's early days. Wouldn't some software update fix it?

thanks all

 

[coolbeans2me]

Just had a similar issue but with some different beeps and mine does seem to be monitor related. I'm using the samsung G7 oddysey and it has the annoying habit of turning off automatically when powering down and taking a while to power on when it detects a signal from my gpu. I found that turning it on and holding it in the menu to stop it turning off before I boot up my PC stops the beeps. Here is a video for reference.