Member Avatar for SkateX

Synopsis:

  • NEW computer build with good hardware

  • While playing audio speakers pop, crackle and audio lags randomly and intermittently.

Troubleshooting steps taken so far:

  • Uninstall all audio drivers, let Windows install default audio drivers

  • Install the latest Realtek High Definition Audio drivers (12/8/2015)

  • Go into Sounds - Playback - Speakers - Disable all enhancements

  • Changed the advanced sound features to 16 bit, 44100 Hz (CD Quality) basically the lowest setting

  • Checked speakers will cell phone to ensure it wasn't just bad speakers

  • Plugged speakers into headphone port on front of tower to ensure it wasn't just a bad connection on back panel

  • Installed all Windows Updates

  • Installed the lastest Nvidia GPU driver

  • Checked task manager to ensure normal operating performance

PC Specs:

  • Operating System: Windows 10 Enterprise 64-bit (10.0, Build 10586)

  • System Manufacturer: ASUS

  • BIOS Date: 08/18/15 10:48:41 Ver: 26.01

  • Processor: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz (4 CPUs), ~3.3GHz

  • Memory: 16384MB RAM

  • DirectX Version: 12

  • Card name: NVIDIA GeForce GTX 970

  • 5 Contributors
  • 4 Replies
  • 357 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by saxon747

Dani AI

Generated

Complement to the thread: a few focused diagnostics and tests that commonly isolate intermittent popping, crackling and lag on new Windows builds. These notes build on points from (chipset/firmware), (hardware-vs-software test), (resource conflicts) and the suggestion from about hardware faults.

Run a DPC/latency trace to find the offending driver or device (common culprits: USB, network, storage and audio drivers). Latency tools will show long ISR/DPC times; when a driver tops the list, update/roll back that driver or temporarily disable the device and retest. A clean boot (third‑party services disabled) is a quick software check to rule out background audio hooks or overlays.

Isolate hardware next. Test audio through a different path (USB headset or external USB DAC, or a discrete PCIe sound card). If the problem disappears on an external device but persists on onboard audio, the motherboard or onboard codec is likely at fault and RMA/refund becomes reasonable. Booting a Linux live USB is an effective cross‑OS check: persistence of the symptom under Linux points strongly to hardware; disappearance points to Windows/driver interaction.

System and firmware checks that often help: ensure chipset and UEFI/BIOS are current, try a High Performance power profile and temporarily disable aggressive CPU C‑states, and scan for system-level errors in Event Viewer around the time of glitches. Safe, non-destructive checks include file-integrity scans:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Note: BIOS/firmware updates and changing BIOS power settings carry risk—backup settings and proceed cautiously. If onboard audio fails all isolation tests, follow up with a hardware swap (USB card or PCIe) to confirm and pursue an RMA.

Recommended Answers

All 4 Replies

Member Avatar for rproffitt

I see no mention of motherboard chipset drivers. Since it's from Asus, check the site for this model. And you have this Enterprise OS so tap your IT to fix it.

Member Avatar for rubberman

It could also be a faulty hardware issue. Is this a desktop or a laptop? If desktop, have you tried an add-on audio card and disabling the integrated one? Also, try booting a Linux live DVD and playing some audio to see if it has the same problem. If so, then you can be pretty sure it is a hardware issue.

Member Avatar for rch1231

My guess would be a IRQ conflict which Windows has always had issues allocating properly.

Click "Start," then click "Control Panel" to open the Control Panel window. Double-click the "System" icon to open the "System Properties" window.

Click the "Hardware" tab, then click the "Device Manager" button. This opens the Device Manager.

Click the "View" menu at the top of the Device Manager window. Select "Resources by type" from the drop-down list. This displays a list of resource types.

Click the expansion box next to the "Interrupt request (IRQ)" icon. This displays a list of system devices and the IRQ numbers assigned to them. Devices with conflicting IRQs will be identified by an exclamation mark inside a yellow circle. Make a note of the IRQ number issued to the conflicting devices.

Member Avatar for saxon747

New buld .This sounds like a hard wear issu.Is it a new motherbroad .Then have it sent back as that what most likely the issue.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.