What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
If Windows crashes with amdacpbus.sys beside a stop code, start by treating it as an AMD Audio Co-Processor driver problem—not as a reason to delete the file. Record the exact stop code, boot into Safe Mode if necessary, install the computer maker’s current audio and chipset drivers, and then roll back the change if the crash began after an update. Repair Windows system files only after the driver path has been addressed. If the PC cannot boot, use Windows Recovery Environment and, if needed, installation media made on a blank USB drive of at least 8 GB.
What “amdacpbus.sys failed” actually tells you
Windows displays the module that was executing when a stop error occurred after the words “What failed:”. Microsoft cautions that a blue screen may be caused by hardware, a device driver, or software. The filename therefore identifies the first investigation target, not a guaranteed root cause.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Microsoft Windows 11 (USB) | $128.99 | Buy on Amazon |
| 2 |
|
Tech-Shop-pro Compatible with install Key Included USB For Windows 11 Home OEM Version 64 bit.... | $48.00 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
amdacpbus.sys is associated with the AMD Audio Co-Processor (ACP) driver path. ACP handles platform audio functions on systems that use it, so conflicts can appear after changes to audio, chipset, graphics, Bluetooth, Windows, or manufacturer utilities. A damaged memory module, another kernel driver, or corrupted Windows components can still produce a crash while this module is on the stack.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems- Delete
amdacpbus.sysfrom the Windows folder. - Download a replacement copy from an unofficial “DLL” or driver site.
- Assume that reinstalling a generic AMD package is safer than the package supplied for your exact computer model.
Capture the evidence before changing anything
Write down the full stop message and what happened immediately before the first crash. The distinction matters because the safest next step differs for a new driver, a Windows update, and a crash that appeared without any software change.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
- Stop code: Common examples include
SYSTEM_SERVICE_EXCEPTION,SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, andIRQL_NOT_LESS_OR_EQUAL. Record any parameter values shown as well. - Timing: Note whether the restart began after a Windows, audio, chipset, graphics, Bluetooth, or original-equipment-manufacturer (OEM) utility update.
- Pattern: Record whether the crash occurs during startup, when waking from sleep, when connecting headphones or a monitor, or while launching a game.
- Recent changes: Include new peripherals, firmware, overclocking settings, antivirus products, and driver-cleanup tools.
Leave files in C:WindowsMinidump intact. These small crash dumps can later help distinguish an ACP driver conflict from a broader hardware or memory fault.
Choose the least disruptive remedy
Use this order unless a particular symptom points to a different branch. Updating or reverting a driver preserves applications and personal files; reset and reinstall options are much more disruptive.
| Remedy | Best fit | Personal-file impact | Reversible? | Important qualification |
|---|---|---|---|---|
| Windows Update and OEM driver installation | Windows still starts, or Safe Mode starts | Normally none | Usually; a later rollback may be available | Use the package for the exact model before a generic package |
| Device Manager rollback | Crash began immediately after a driver update | None | Yes, if the previous driver remains available | The Roll Back Driver button may be unavailable |
| Remove a recent update in Recovery Environment | Normal startup is impossible after an update | Normally none | Yes, by reinstalling the update later | Use the update-removal option that matches the recent change |
| System Restore | A restore point predates the crashes | Personal files are normally retained; applications and drivers installed after the point can be removed | Usually, by choosing another restore point | Restore points are not guaranteed to exist |
| Startup Repair | Windows cannot complete startup | Normally none | Not a driver rollback | It targets boot problems, not every ACP driver conflict |
| Reset or clean installation | Other recovery methods fail or Windows is badly damaged | Can remove apps and, depending on the choice, personal data | Not without backups or installation media | Back up files first and read every erase warning |
Step 1: Start in Safe Mode when normal startup loops
Safe Mode loads Windows with a limited set of drivers and services. If the machine remains stable there, you can remove or replace the suspect package without the full third-party driver stack running.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →- Interrupt startup only when Windows cannot complete a normal boot; after several failed starts, Windows should open Windows Recovery Environment automatically.
- Choose Troubleshoot, then Advanced options, then Startup Settings, and select Restart.
- At the Startup Settings screen, choose Enable Safe Mode. Use Enable Safe Mode with Networking only if you need network access and the system is stable enough to use it.
- Once in Safe Mode, copy important documents to another drive before making driver changes.
If Windows starts normally, you can still use Safe Mode as a controlled test. A crash that disappears there points toward a driver or service loaded during a normal boot, but it does not prove that ACP is the only cause.
Step 2: Install the correct audio and chipset drivers
Run Windows Update first
- Open Settings and go to Windows Update.
- Select Check for updates and install all applicable updates.
- Open Advanced options and review Optional updates for driver packages when that section is present.
- Restart, then reproduce the activity that normally triggers the blue screen.
Windows Update may not offer the newest or most suitable ACP package for every laptop or desktop. If the crash persists, continue with the model-specific package rather than repeatedly installing the same update.
Inspect Device Manager
- Right-click Start and open Device Manager.
- Expand System devices and inspect entries referring to AMD audio, ACP, or an audio co-processor. Also inspect Sound, video and game controllers.
- Look for a yellow warning icon. Open a relevant device, choose Properties, and read the General tab for a status code.
- On the Driver tab, record the provider, date, and version before changing it.
Do not remove an unknown system device simply because its name contains AMD. Record its identity first so that you can restore the original package if a test makes startup worse.
Prefer the computer maker’s package
Go to the support page for the exact computer model and operating-system edition. Install the manufacturer’s audio and chipset packages in the order the manufacturer specifies, then restart. Laptop models often combine an AMD ACP component with custom audio codecs, power management, hotkeys, or firmware; a package intended for a different model can create a new conflict.
Recommended Free Tools
If no suitable OEM package is available, compare the installed version with the matching package on AMD’s official driver portal. Match the Windows edition, system architecture, processor family, and release notes. Install one relevant package at a time, restart, and test before changing another driver. That sequence makes it possible to identify which change affected the crash.
Step 3: Roll back the change that preceded the crash
Use Device Manager rollback
- Open Device Manager and locate the ACP or related audio device.
- Open Properties, select the Driver tab, and choose Roll Back Driver if the button is enabled.
- Select a reason, confirm, and restart.
Rollback is appropriate when the blue screen started immediately after a driver update and the prior package is still stored on the system. If the button is disabled, do not force it by deleting driver-store files.
Remove a recent Windows update
From Windows Recovery Environment, choose Troubleshoot, Advanced options, and Uninstall Updates. Select the most relevant quality or feature update, restart, and test. If Windows still boots, the same recovery function can be reached through Settings and the recovery options for installed updates, depending on the Windows build.
Use System Restore
In Windows Recovery Environment, select Troubleshoot, Advanced options, then System Restore. Pick a restore point dated before the first amdacpbus.sys crash and review the affected programs before confirming. System Restore changes drivers, system files, and installed applications; it is not a substitute for backing up personal files.
AMD release notes document ACPBus/I2STDM uninstall workarounds for particular embedded Catalyst packages. That is evidence that an ACP fix can depend on the platform and driver version; it is not a universal instruction to uninstall ACP components on every Windows computer. Treat any package-specific workaround as a reversible test only when it matches your model, Windows build, and driver release.
Rank #2
- Video Link to instructions and Free support VIA Amazon
- Great Support fast responce
- 15 plus years of experiance
- Key is included
Step 4: Repair Windows components after the driver path
Run the following from an elevated Command Prompt after addressing the driver. These commands repair the Windows component store and protected system files; they do not replace the need for a compatible OEM driver.
- Open Windows Terminal (Admin) or Command Prompt (Admin).
- Enter
DISM.exe /Online /Cleanup-Image /RestoreHealthand wait for it to finish. Do not close the window while the percentage appears stalled. - Enter
sfc /scannowand wait for verification to reach 100 percent. - Restart Windows and test the same workload that previously caused the stop error.
Microsoft community answers commonly recommend this DISM-then-SFC order. It is a repair step, not proof that corrupted system files caused the original crash. If either command reports that it could not complete, note the exact message before trying repeated driver changes.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Step 5: Check for memory, hardware, and competing drivers
If the blue screen continues with a known-good OEM driver, investigate beyond ACP.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Event Viewer: Open Event Viewer, select Windows Logs, then System, and inspect errors and warnings immediately before and after the crash time. Correlate device, power, storage, and driver events rather than treating every red icon as a cause.
- Windows Memory Diagnostic: Open Start, type Windows Memory Diagnostic, choose the restart-and-check option, and allow the test to complete. Memory errors can cause different stop codes while the same driver appears in the report.
- Minidumps: Preserve files in
C:WindowsMinidump. Do not overwrite them while repeatedly forcing restarts; they may be needed for a debugger or qualified technician. - Hardware changes: Remove recently added USB audio devices, docks, Bluetooth adapters, or displays and test one change at a time. Return any overclock or undervolt to its default setting.
- Firmware and storage: Check the computer maker’s firmware notes and verify that the system drive has normal health and free space before attempting a major Windows recovery.
A failure that follows the machine across driver versions, occurs in Safe Mode, or appears with unrelated stop codes deserves hardware diagnostics rather than endless ACP reinstalls.
If Windows will not boot at all
Use the built-in Recovery Environment
Windows Recovery Environment can launch automatically after failed boots. You can also reach it from Settings through System, Recovery, and Advanced startup when Windows can remain running long enough. Its tools include:
- Startup Repair for boot configuration and startup files.
- System Restore for returning system files, drivers, and applications to an earlier restore point.
- Uninstall Updates for removing a recent quality or feature update.
- Command Prompt for advanced offline troubleshooting.
- Reset this PC and reinstall choices when less disruptive methods fail.
Try the least disruptive option that fits the timing of the failure. Reset and reinstall choices can remove applications and data, so copy files first whenever the storage is accessible.
Create recovery media on another computer
If the affected PC cannot open Recovery Environment and you do not have a recovery drive, Microsoft says to create Windows installation media with the Media Creation Tool on another working PC.
- Use a blank USB flash drive with at least 8 GB of space.
- Back up anything on that USB first; creating installation media erases the drive.
- Finish creating the media, connect it to the affected computer, and boot from the USB. The boot-menu key varies by manufacturer.
- At Windows Setup, do not choose the install button. Select Repair my PC to open Windows Recovery Environment.
- Use Startup Repair, update removal, System Restore, or Command Prompt in the same least-disruptive order.
The USB provides access to recovery tools; it does not directly repair amdacpbus.sys and it does not guarantee that a clean installation will preserve applications or files.
Windows version and platform cautions
Recovery instructions apply to both Windows 10 and Windows 11, but their support status differs. Microsoft ended Windows 10 support on October 14, 2025. Existing Windows 10 recovery tools may still operate, yet ongoing security and update support is not the same as on a supported Windows 11 installation. Confirm the edition and build before downloading a driver or installation image.
ACP behavior is platform-specific. The same AMD package can behave differently on an OEM laptop, a desktop motherboard, and an embedded system. Always record the exact model, Windows build, ACP/audio driver version, and BIOS or firmware version when seeking help. A generic package change should be a testable, reversible step—not a permanent replacement for the OEM package.
When to stop troubleshooting yourself
Stop and obtain professional assistance if the system cannot stay on long enough to back up data, memory diagnostics report errors, storage health is failing, the machine overheats or powers off independently of the blue screen, or recovery tools repeatedly fail. Provide the technician with the stop code, crash timing, driver versions, Event Viewer entries, and the contents of C:WindowsMinidump. That evidence is more useful than a claim that the AMD file is “bad.”
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
