Im using an ASrock A520-HDV motherboard, and when i was rebooting my computer to boot it into windows (i have windows 10 and arch linux installed) it showed the grub menu for 1 second and then the screen went totally black, so i pushed the reset button of my case, but when i did that the computer didnt POST and it started to beep 3 consecutive times followed by 1 beep, then stopping and doing it all over again, i reseted the cmpuer with the power supply and it booted normally, but i want to know what those beeps mean, i also checked the motherboard’s manual and it doesnt say anything
Do these help in any way? (From https://itigic.com/beeps-on-asus-msi-asrock-and-gigabyte-motherboards-meanings/?expand_article=1 )
Short and constant beeps: error with RAM memory refresh.
Two short beeps: RAM parity error.
Three short beeps: RAM read / write test failed.
Four short beeps: system clock error.
Five short beeps: CPU error.
Six short beeps: keyboard controller error, or keyboard not detected.
Seven short beeps – General error, usually due to CPU or RAM.
Eight short beeps: graphics card error, check that it is installed correctly and that the power cables are connected.
Nine short beeps: ROM error. A Clear CMOS generally does not solve.
Ten short beeps: ROM read / write error. A Clear CMOS could fix it.
Eleven short beeps: CPU cache check failed.
should i run memtest? it is working normally right now, and this has never happened
Could be an indication of RAM that’s becoming unstable. If it was me, I’d run different memtests (prime95, OCCT, TM5), but that would take probably three to four hours, and I’m particular about RAM stability. Running whatever built in memtest you have is likely sufficient.
In case the ram is becoming unstable, there is a way to fix it without changin the ram or i have to change it?
I’d just start by re-seating the sticks and not bother with the memtest gauntlet unless it happens again or your computer starts doing anything else odd. I was having no issues but a single game crashing on me every couple hours once. It took testing the ram a dozen hours before it ever showed itself and I had to loosen my timing a bit to fix it. A one off incident, I wouldn’t do anything for.
If you have multiple sticks, you can remove a bad one until you can replace it. Many memory modules have a lifetime warranty so you can often get them replaced by the manufacturer. I don’t think there’s a scenario where the system will stay stable with a bad stick installed.
i already tested the ram, 0 errors, i think it is something with grub, probably because i configured it to be able to work with secure boot, i already had that problem before (but without the beeps, only the black screen, that was problably because i pressed the reset button too fast and it triggered something) anyway, thank you
You can loosen the timings or turn off XMP (which resets your RAM to the guaranteed-stable JDEC timings), which might solve any instability but would lower your RAM performance, but if it’s already at JDEC spec and unstable, replacement is your only option.
i already tested the ram, no errors, it was grub related
Hey, easy fixes are the best fixes!
So I would take out and reseat the RAM
