Is this dangerous? 4 beeps but boots fine

Hi Guys,

I face exactly the same problem after I replaced my old RTX card with a new RTX3070
4 short beeps but systems boots no problem and other than that everything works like a charm
I tried multiple memory tests and GPU tests (10hrs stress tests) but no issues at all.
Replaced memory modules, with the new set - still the same beeping.
I'm now 95% confident this is probably caused by MB being confused with RTX30X0 GPUs and flagging them as faulty. (I checked with my brother's GTX970 and no beeps)

@wportx, you mentioned some advanced bios settings changes. Can you be more specific please?
What exactly did you change?

Has anyone tried to update bios to F52? Did it work?

Thanks


my build:
Ryzen 7 3700x
Gigabyte B450 Gaming X
Gigabyte RTX3070 Eagle OC
16GB HyperX Fury Black 3200Mhz
GIGABYTE P850GM 850W Gold
2TB Samsung 970 EVO Plus
AMI Bios F51
 
Last edited:
Hello, Folks!

Just adding myself to the list of people affected by this problem.

I was confronted with the same issue last november 25th, 2020. I boght a Strix 3080, as a gift for me, to replace my good old Strix 1080Ti. After installing the 3080 on my motherboard the beeps started. In my case the first beep is the usual BIOS's one, followed by four quick beeps. If I install the 1080Ti back or disable the CSM option on the BIOS (I'm using the latest one for my motherboard model at the time of writing: 1802) the beeping stops, but I'm no longer able to load windows (CSM disabled).
Apart from that, everything is runnig fine, no errors, no underperformance...the system is a-okay.

I wonder, there is a option on the BIOS somewhere (couldn't find it before this post) on the PCIe menu...it's a combo box where you can select PCIe Gen2, 3 and 4. Would that be helpfull in any way to solve this issue? I mean, to change it to PCIe4? I know the 9700k+Z390 is PCIe3...
Edit: Recorded a video to show in detail what happens.
 
Last edited:
Hello!

I don't know why I didn't check it before, but over on the ROG Strix 3080's support page on the Asus website, the newest bios version address this issue specifically:


Version V2
2020/12/14 8.55 MBytes
RTX3080 bios update tool
-Further optimize the performance for 0dB fan feature
-Fixed motherboard “beeping” bug during computer start-up

I just found out about that and...updating the BIOS is always nerve wracking, but since the 3080 Strix got dual bios, I'll give it a try later today.
 
Seems to be happening with loads of RTX 30 cards, mine included. I disabled CSM and it stopped but then returned. Feels like it only beeps on occasion. I suspect it could be a few things. One is a delay in detection of the display port connection. Another is the zero idle fan setting. I'm leaning towards the latter. Possibly, the BIOS detects the fans aren't spinning and creates a failure warning for the device.
 
Actually, scratch the above. I use my monitor for my laptop via HDMI and my desktop via DP (to the RTX 3090). Whenever I boot up after having had the monitor switched to HDMI (even if I swap back to DP before booting) I get the beeps. If I reboot again, no beeps.
 
I had the same issue with my Aorus Z370 Gaming 5 motherboard and the new RTX 3090FE, disabled CSM in bios but the I got no beeps at all, after a bit of rummaging I found that disabling fast boot cured it.
I must say that even with CSM enabled and with the 4 short beeps, the PC ran as good as ever, it's just alarming when you get different beeps at boot.
 
evohicks said:
I had the same issue with my Aorus Z370 Gaming 5 motherboard and the new RTX 3090FE, disabled CSM in bios but the I got no beeps at all, after a bit of rummaging I found that disabling fast boot cured it.
I must say that even with CSM enabled and with the 4 short beeps, the PC ran as good as ever, it's just alarming when you get different beeps at boot.
Click to expand...

I've not had fast boot enabled. With the swapping between the HDMI and DP cables, the problem is there. It feels like there is a delay in the card registering that it's connected to the DP cable. So, allowing more time for that e.g. non-fast boot could be a fix. My belief is that there is some kind of registration delay from when the card is on and registering an output.
 
You must log in or register to reply here.
Back
Top Bottom