Mysterious beeps on my ASUS Ivy Bridge system

g00ey

Distinguished
Aug 15, 2009
470
0
18,790
Every now and then (maybe a few times per week) I hear two pungent piezoelectric beeps in the system and I'm baffled as to what it comes from. I didn't install any speaker onto the motherboard when I built the system 9 months ago. When the two beeps come I notice that the computer also drops the network connection for about a second and then it comes back. I can't say that I'm disturbed by those beeps but they sound like coming from some sort of alarm signal.

I looked into the event log but I cannot isolate any failure or error event correlated to these beeps.

In an earlier case of such mysterious beeps (a 5-6 years old forum thread so it may be obsolete). it was suggested to check for "unknown devices" in the device manager. I checked the device manager and it does indeed have quite a lengthy list of "unknown devices". When checking the vendor and hardware ID, all those "unknown devices" can be traced to different functions of the main CPU. I've tried to get rid of 'em by installing drivers for 'em but I've failed. Since the system appears to work fine I didn't try to take further measures about it.

It's an ASUS WS motherboard with UEFI BIOS btw and an LGA2011 socket. I use ECC ram with a Xeon E5. The sound card is an ASUS Xonar Essence STX.

Does anyone know what's going on?
 
Solution
I have isolated the source of these beeps and it turns out that they come through the sound card and not from the internal motherboard speaker/buzzer.

It's a high pitched double beep and today it occurred right after boot. The temperatures were pretty low as is expected on a freshly booted up system. The BIOS is now up to date.

I could suspect that it is a background application such as a calendar or scheduler, but then the ethernet connection shouldn't drop momentarily.

I also discovered why the GPU was so hot. It turns out that steam.exe tends to start itself and run in the background even though I'm not gaming. While it's running, it hogs one CPU core and maxes out the GPU. If I kill steam.exe with the task manager, the GPU goes...

g00ey

Distinguished
Aug 15, 2009
470
0
18,790
There are a lot of software suggestions you come with :). I tried HWMonitor right now and the monitor software provied by ASUS, and AIDA64. The HWMonitor is very detailed and report many temperatures; one for each DIMM, one for each CPU core plus the whole package, and the hard drives. According to the software there are about 20 temperature sensors in the system, I find it hard to believe.

The CPU temperatures reported by HW monitor ranges between 40°C and 53°C. The GPU sits at 71°C but seems to be happy with it. Strangely, I'm not doing anything 3D right now. There is one other temperature that is high and that is the readings from a channel called "TMPIN3" which reports temperatures between 62°C and 67°C. AIDA reports the same temperature for one of the sensors classified as a CPU sensor.

The ASUS monitor reports that the CPU temperature is around 65°C. Maybe it is the CPU fan that isn't strong enough. The CPU's TDP is 130W and the cooler is a big Noctua NH-14 with ultra-silent resistors keeping the fans down at 6-700 rpm. I suppose I could lower the resistance and see how things go from there. I saw that there is a new BIOS update so I'll try installing it to boot.

Or you mean that the driver issues in the Device Manager is due to a faulty motherboard? Btw, the motherboard is an ASUS P9X79 WS.

EDIT: I did a short stress test with AIDA and the temperature climbed up to 72-73°C, and the CPU fan went up to 860 rpm. AIDA reports 6 temperature sensors just for the CPU, unbelievable! I checked and found out that some DDR3 memory modules actually come with thermal sensors, particularly ECC modules.
 

g00ey

Distinguished
Aug 15, 2009
470
0
18,790
I have isolated the source of these beeps and it turns out that they come through the sound card and not from the internal motherboard speaker/buzzer.

It's a high pitched double beep and today it occurred right after boot. The temperatures were pretty low as is expected on a freshly booted up system. The BIOS is now up to date.

I could suspect that it is a background application such as a calendar or scheduler, but then the ethernet connection shouldn't drop momentarily.

I also discovered why the GPU was so hot. It turns out that steam.exe tends to start itself and run in the background even though I'm not gaming. While it's running, it hogs one CPU core and maxes out the GPU. If I kill steam.exe with the task manager, the GPU goes back down to normal values. The maximum temp (allowed at the heat spreader, T_case) is 98°C so I take it that the 70°C is normal. The maximum temp for the CPU is 70°C (not sure which sensor though) so it is possible that this may have been exceeded.

I have now deleted the steam.exe file and all the system files in the steam directory, perhaps this could solve the issue. I couldn't find the launcher of the steam file in the registry. I found an XML-formatted config file along with the steam.exe and it appears to get started by the task scheduler 20 minutes after logon.
 
Solution