Tag Archives: troubleshooting

3CX, Phone System, SIP-T41S, SIP-T42S, SIP-T46S, SIP-T48S, SIP-T53, Yealink

Yealink Handset Crackling or Buzzing from Handset and Speakerphone

Leave a comment

You may occasionally notice that your Yealink phone starts crackling or buzzing.  This has most commonly been observed after the phone has been in operation for sometime without being rebooted or after a firmware update.

Below are some troubleshooting steps that you can try to resolve the buzzing and crackling

  • Try restarting the Yealink Phone (You can either remove the Power or Ethernet Cable if using PoE, alternatively just hold down the X key until you are prompted to restart the phone)
  • Try a Factory Reset on the Phone, ensure that you have all the required settings to reconfigure the device after the factory reset.
  • Update the phone firmware to the latest release and then perform a factory reset prior to configuring or provisioning the phone again.
  • Confirm if crackling or buzzing is just occurring from the handset or also from the speakerphone.  If just the handset exhibits the issue then the cable or handset may need to be replaced.
  • Ensure that the VoIP/SIP Phone System is up to date
  • Ensure that you are using the most appropriate voice Codecs for your phones and the SIP Trunk. (A-law is commonly used in Europe and u-law is generally used in the United States)
BSOD, SBS 2011, Small Business Server 2011, Windows, Windows 7, Windows Server 2008 R2

Windows Kernel Power Event ID 41 Error

Leave a comment

Windows 7 or Windows Server 2008 R2 may restart unexpectedly, you may get a brief glimpse of a BSOD (Blue Screen of Death) and then find yourself back at the Windows login prompt.  When you inspect the Windows Event Log you will find the following event logged

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Event ID: 41
Level: Critical
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

The additional info under the event is important because the various bug check codes can indicate different causes.

EventData
BugcheckCode          0
BugcheckParameter1    0x0
BugcheckParameter2    0x0
BugcheckParameter3    0x0
BugcheckParameter4    0x0

Having faced this error recently it eventually turned out that the problem was due to incompatible memory (not faulty memory).  The batch of machines in question were all branded but due to an error with the manufacturers memory compatability matrix had been supplied with the wrong additional memory modules.  When we reverted the machines to the standard 2GB module that was already installed they operated perfectly, we eventually arranged for the additional modules to be swapped and that was the end of the issue.

An important thing to remember is that a memory checker will not show that your memory is faulty if it just incompatible with your particular system or mainboard.

Your system or mainboard manufacturers support should be able to confirm memory compatability and advise on the correct upgrade/type for your system