This chapter covers driver conflicts, a common source of system instability and hardware failures on Windows, macOS, and Linux. For the CompTIA A+ 220-1102 exam, driver conflicts fall under Objective 3.1 (Given a scenario, troubleshoot common Windows, macOS, and Linux problems). Approximately 10-15% of the exam's troubleshooting questions involve driver-related issues, making this a critical topic. You will learn to identify, diagnose, and resolve driver conflicts using built-in tools like Device Manager, Driver Verifier, and system logs.
Jump to a section
Imagine a symphony orchestra where each musician (hardware device) has its own sheet music (driver) that tells them exactly how to play their part. The conductor (operating system) coordinates the musicians, ensuring they play together harmoniously. Now suppose two musicians have conflicting sheet music—the clarinetist has one version that says 'play C-sharp' while the flutist's sheet says 'play C-natural' at the same moment. The result is a dissonant sound (system instability). Worse, if the conductor hands out different sheet music for the same instrument—say, two different driver files for the same sound card—the musician becomes confused, plays wrong notes, or stops playing entirely (device failure or blue screen). In a computer, driver conflicts occur when two or more drivers attempt to control the same hardware resource, use conflicting IRQ lines, memory addresses, or I/O ports, or when incompatible driver versions are loaded for the same device. Just as a conductor must ensure each musician has the correct, unique sheet music, the operating system's Plug and Play manager allocates resources to avoid conflicts. When it fails—due to legacy non-PnP devices, buggy drivers, or manual resource assignment—the system experiences crashes, freezes, or devices that simply don't work. The solution is to isolate the conflicting drivers, update or roll back to compatible versions, and ensure resource assignments are unique, much like giving each musician their own unambiguous part.
What Are Driver Conflicts and Why Do They Exist?
A driver conflict occurs when two or more device drivers attempt to use the same system resource—such as an interrupt request (IRQ) line, I/O port address, memory address range, or direct memory access (DMA) channel—simultaneously. In modern systems, Plug and Play (PnP) and ACPI (Advanced Configuration and Power Interface) manage resource allocation automatically. However, conflicts still arise due to:
Legacy devices that are not PnP-compliant.
Buggy or poorly written drivers.
Driver updates that overwrite or install incompatible versions.
Multiple drivers claiming the same device (e.g., a printer with both manufacturer and generic drivers).
Resource exhaustion in systems with many devices.
How Driver Conflicts Work Internally
When the system boots, the BIOS/UEFI enumerates hardware devices. The operating system's PnP manager then assigns resources to each device based on its requirements. Each device's driver registers with the I/O manager, requesting specific resources. The PnP manager resolves conflicts by negotiating with devices, but if a device is non-PnP (e.g., an ISA card), it may claim fixed resources that conflict with PnP devices.
Conflict Example: - Device A requests IRQ 5, I/O port 0x300-0x31F. - Device B requests IRQ 5, I/O port 0x300-0x31F. - Both drivers load, but only one can control the resource. The result: one or both devices fail, or the system crashes.
Key Components, Values, Defaults, and Timers
IRQ Lines: Standard IRQs: 0 (timer), 1 (keyboard), 3 (COM2/4), 4 (COM1/3), 6 (floppy), 7 (LPT1), 8 (RTC), 12 (PS/2 mouse), 14 (primary IDE), 15 (secondary IDE). Modern systems use IRQ sharing via PCI/PCIe, but conflicts still occur with legacy devices.
I/O Ports: Ranges like 0x2F8-0x2FF (COM2), 0x378-0x37F (LPT1).
Memory Addresses: Video memory at 0xA0000-0xBFFFF.
DMA Channels: DMA 0-3 for 8-bit, 4-7 for 16-bit. Conflicts common with sound cards and parallel ports.
Driver Verifier (Windows): Built-in tool that stresses drivers to detect illegal function calls, memory leaks, and other violations. Default settings: standard flags (e.g., special pool, IRQL tracking).
Device Manager (Windows): Shows resource assignments by device. Yellow exclamation mark indicates a problem. Double-click device > Resources tab to see conflicts.
Configuration and Verification Commands
#### Windows
- Device Manager: devmgmt.msc
- Driver Verifier: verifier.exe (GUI) or verifier /flags 0x209BB /driver <driver.sys> (command line).
- System Information: msinfo32.exe > Components > Problem Devices.
- Driver Query: driverquery /v (lists all drivers with module name, display name, and state).
- Driver Rollback: Device Manager > Driver tab > Roll Back Driver.
- Enable/Disable Device: devcon disable <hardware-id> or Device Manager.
#### macOS
- System Information: Apple menu > About This Mac > System Report > Hardware > USB, Thunderbolt, etc.
- Kernel Extensions (kexts): kextstat | grep -v com.apple to list third-party drivers.
- kextunload/kextload: sudo kextunload /System/Library/Extensions/SomeDriver.kext
#### Linux
- lsmod: List loaded kernel modules.
- lspci -v: Show PCI devices with IRQ and memory info.
- dmesg: Kernel ring buffer; look for 'conflict' or 'resource' messages.
- modprobe: sudo modprobe -r <module> to remove, sudo modprobe <module> to load.
- /proc/interrupts: Shows IRQ assignments per CPU.
- /proc/ioports: Shows I/O port allocations.
Interaction with Related Technologies
Plug and Play (PnP): Automatically allocates resources. Conflicts occur when a device is not PnP or when PnP is disabled in BIOS.
ACPI: Manages power states and resource enumeration. ACPI errors can cause driver conflicts.
Virtualization: Hyper-V, VMware, and VirtualBox assign virtual resources to guest VMs. Conflicts can occur if host drivers interfere with virtual device drivers.
Driver Signing: Windows 10/11 enforce driver signature enforcement (64-bit). Unsigned drivers may fail to load, causing device issues.
Windows Update: Can automatically install driver updates that conflict with existing drivers. Windows 10/11 'Driver Updates' in Windows Update often cause conflicts.
Common Driver Conflict Scenarios
Legacy Sound Card vs. Integrated Audio: An old ISA sound card using IRQ 5 conflicts with a PCI sound card using the same IRQ. Solution: Disable the legacy device in Device Manager or change its resources manually.
Printer Driver Clash: Installing a manufacturer's PCL6 driver over a generic HP driver causes print spooler crashes. Solution: Remove all printer drivers and reinstall the correct one.
Network Adapter Conflict: Two network cards (e.g., onboard Ethernet and a USB Wi-Fi adapter) both try to use the same IRQ. Solution: Move the USB adapter to a different port or update drivers.
Graphics Driver Conflict: After a Windows update, the generic Microsoft Basic Display Adapter driver loads alongside the NVIDIA driver, causing screen flickering. Solution: Use DDU (Display Driver Uninstaller) in Safe Mode to remove all display drivers, then install the correct driver.
Identify the Symptoms
The first step is recognizing driver conflict symptoms. Common signs include: a device showing a yellow exclamation mark in Device Manager, system crashes (BSOD) with error codes like DRIVER_IRQL_NOT_LESS_OR_EQUAL or DRIVER_POWER_STATE_FAILURE, random freezes, devices that work intermittently, or the system failing to boot. In Linux, look for kernel oops or 'resource conflict' messages in dmesg. In macOS, check for kernel panics or devices not appearing in System Information. Document the exact error message and when the issue started (e.g., after a driver update, new hardware installation, or Windows Update).
Check Device Manager for Conflicts
On Windows, open Device Manager (devmgmt.msc). Look for devices with a yellow exclamation mark, red X, or down arrow. Right-click the problematic device, select Properties, and go to the General tab for error code. Common codes: Code 12 (This device cannot find enough free resources), Code 28 (Drivers are not installed), Code 31 (Driver failed to load), Code 43 (Windows has stopped this device because it has reported problems). Click the Resources tab to see the conflicting resource list—e.g., 'IRQ 5 in use by device B'. If the Resources tab shows no conflicts but the device is still problematic, the conflict may be with a driver that is not properly releasing resources.
Use System Information to Confirm
Run msinfo32.exe and expand Components > Problem Devices. This lists devices with issues and the corresponding error code and status. Also, under Hardware Resources > Conflicts/Sharing, you can see which resources are shared. A sharing entry is normal for PCI devices (e.g., IRQ 16 shared by multiple PCI devices), but a conflict entry (red) indicates two devices claiming the same resource exclusively. For example, 'IRQ 5 - Device A and Device B - Conflict'. In Linux, use 'cat /proc/interrupts' and 'cat /proc/ioports' to see allocations. Look for lines where two devices claim the same address range.
Isolate the Conflicting Driver
To isolate which driver is causing the conflict, disable one of the suspected devices in Device Manager (right-click > Disable device). Reboot and see if the problem resolves. If it does, you have identified the conflicting device. Alternatively, boot into Safe Mode (Windows: F8 or Shift+Restart > Troubleshoot > Advanced options > Startup Settings > Safe Mode). In Safe Mode, only essential drivers load; if the problem disappears, a third-party driver conflict is likely. In Linux, boot into runlevel 1 (single-user mode) or with 'nomodeset' kernel parameter. In macOS, boot into Safe Mode (hold Shift) to load only essential kernel extensions.
Resolve the Conflict
Once the conflicting driver is identified, choose a resolution method: (1) Update the driver: Right-click device > Update driver > Search automatically. (2) Roll back the driver: If the issue started after a driver update, use Roll Back Driver. (3) Uninstall the driver: Right-click > Uninstall device, then reboot to let Windows reinstall the driver automatically. (4) Manually change resources: In Device Manager > Properties > Resources tab, uncheck 'Use automatic settings' and change IRQ, I/O range, or memory address to a free one. This is rarely needed with modern PnP systems but works for legacy devices. (5) Use Driver Verifier: Run 'verifier.exe' to stress-test drivers and identify faulty ones. (6) Disable the conflicting device permanently if not needed. (7) Use System Restore to revert to a previous state before the conflict.
Verify Resolution and Prevent Recurrence
After resolving the conflict, reboot and verify that the device works correctly and the symptoms are gone. Check Device Manager for any remaining warning icons. Run a stress test if the conflict caused crashes (e.g., use Windows Memory Diagnostic or Prime95). To prevent recurrence, avoid installing multiple drivers for the same device, disable automatic driver updates via Windows Update (Group Policy: 'Do not include drivers with Windows Updates'), and keep a backup of stable drivers. For enterprise environments, use WSUS or SCCM to control driver deployments. Document the conflict and resolution in a knowledge base for future reference.
In a large enterprise with thousands of Windows 10/11 workstations, driver conflicts are a frequent helpdesk ticket. One common scenario involves USB docking stations. When a user connects a Dell D6000 docking station to a laptop, the docking station's DisplayLink driver may conflict with the laptop's built-in Intel graphics driver. The result: external monitors flicker or show no signal, and the system may BSOD with error VIDEO_TDR_FAILURE. The root cause is that both drivers attempt to control the same display adapter resources. The solution is to update the DisplayLink driver to the latest version (which is designed to coexist with Intel graphics) or to disable the Intel driver for the docking station's video output. In production, IT teams often deploy a script that checks for known conflicting driver versions and updates them via SCCM.
Another scenario involves network printers in a hospital. A Kyocera printer is installed with both the manufacturer's KX driver and a generic HP PCL6 driver (because a previous technician used the 'Add Printer' wizard and selected the wrong driver). When users print, the print spooler crashes because both drivers claim the same printer port. The fix: remove all printer drivers via Print Management (printmanagement.msc), delete the driver files from C:\Windows\System32\spool\drivers, and reinstall only the correct Kyocera driver. To prevent recurrence, IT implements a group policy that restricts driver installation to approved signed drivers.
A third scenario involves a small business using a legacy serial barcode scanner. The scanner uses a USB-to-serial converter that requires a Prolific PL2303 driver. If the user installs a counterfeit PL2303 chip (common on eBay), the driver detects the fake chip and refuses to load (Windows Code 10). The conflict is between the driver's digital signature check and the hardware's non-standard chip ID. The workaround: use an older driver version that doesn't have the anti-counterfeit check, or replace the converter with a genuine FTDI chip. In this case, the 'conflict' is not between two drivers but between the driver and the hardware, which the exam considers a driver compatibility issue.
The 220-1102 exam tests driver conflicts under Objective 3.1 (Troubleshoot common Windows, macOS, and Linux problems). Specific sub-objectives include: 'Identify common symptoms and resolve driver issues' and 'Use appropriate tools to troubleshoot drivers'. The exam expects you to know:
Symptoms: Yellow exclamation mark in Device Manager, BSOD with driver-related error codes (DRIVER_IRQL_NOT_LESS_OR_EQUAL, DRIVER_POWER_STATE_FAILURE, VIDEO_TDR_FAILURE), device not working, system freeze, or boot failure.
Tools: Device Manager (most important), Driver Verifier, System Information (msinfo32), Event Viewer (System logs), Safe Mode, System Restore, and Roll Back Driver.
Resolution steps: Update driver, roll back driver, uninstall and reinstall, disable device, use System Restore, or use Driver Verifier to identify the faulty driver.
Common wrong answers: Candidates often choose 'Reinstall the operating system' as a first step—this is too drastic and not a troubleshooting best practice. Another trap: 'Change the IRQ in BIOS'—modern systems use PnP; manual IRQ changes are rarely needed and can cause more conflicts. Also, 'Run CHKDSK' is a disk error tool, not relevant to driver conflicts. 'Use System File Checker (SFC)' is for system file corruption, not driver conflicts, though it can fix corrupted driver files.
Edge cases: The exam may present a scenario where a device works in Safe Mode but not normal mode—this is a classic sign of driver conflict (or faulty driver). Another scenario: a USB device that works on one port but not another—this could be a resource conflict on that USB controller. The exam loves to ask about Driver Verifier: remember that enabling Driver Verifier on the system driver can cause a boot loop; you must boot into Safe Mode and run 'verifier /reset' to disable it.
Elimination strategy: If the question describes a device with a yellow exclamation mark, the answer is almost always Device Manager first. If the question mentions a BSOD after a driver update, the answer is Roll Back Driver. If the question involves multiple devices sharing an IRQ, the answer is to update drivers or disable one device.
Driver conflicts occur when two or more drivers claim the same system resource (IRQ, I/O port, memory address, DMA channel).
The primary symptom is a yellow exclamation mark in Device Manager, but also BSODs, freezes, or device failures.
Use Device Manager to check for resource conflicts; use Driver Verifier to stress-test drivers.
Resolution steps: update, roll back, uninstall/reinstall, disable device, or use System Restore.
Safe Mode loads only essential drivers; if the problem disappears, a third-party driver is likely the cause.
Driver conflicts can occur on all operating systems: Windows, macOS, and Linux.
Always verify resolution by rebooting and testing the device thoroughly.
Prevent conflicts by controlling driver updates via Group Policy or WSUS.
These come up on the exam all the time. Here's how to tell them apart.
Device Manager
GUI tool for viewing and managing devices and drivers.
Shows resource conflicts (IRQ, I/O, memory) in the Resources tab.
Allows driver update, rollback, disable, and uninstall.
Best for initial diagnosis and resolution.
Cannot stress-test drivers or detect subtle corruption.
Driver Verifier
Command-line or GUI tool that stresses drivers to detect violations.
Does not show resource assignments but catches illegal function calls, memory leaks, etc.
Used after Device Manager identifies a suspicious driver.
Can cause system instability during testing (run in test environment).
Requires reboot to enable/disable; can cause boot loops if misconfigured.
Mistake
Driver conflicts always show a yellow exclamation mark in Device Manager.
Correct
Not always. Some conflicts cause system crashes or freezes without any warning in Device Manager. For example, a driver that causes memory corruption may lead to a BSOD without any Device Manager error. Always check Event Viewer and use Driver Verifier to catch subtle conflicts.
Mistake
Updating a driver always fixes conflicts.
Correct
Driver updates can actually introduce conflicts. A newer driver may be incompatible with existing hardware or other drivers. Rolling back to a previous version is often the fix. Always verify the driver version's release notes for known issues.
Mistake
Windows Update drivers are always safe and compatible.
Correct
Windows Update drivers are generic and may not include manufacturer-specific optimizations. They can conflict with OEM drivers. Many IT professionals disable driver updates via Windows Update to avoid this.
Mistake
Driver conflicts only happen on Windows.
Correct
macOS and Linux also experience driver conflicts. On macOS, kernel extensions (kexts) can conflict, causing kernel panics. On Linux, kernel modules can claim overlapping resources, leading to dmesg errors. The troubleshooting methods differ but the concept is universal.
Mistake
Reinstalling the operating system is the best way to fix driver conflicts.
Correct
Reinstalling the OS is a last resort. Driver conflicts are usually resolved by updating, rolling back, or removing the conflicting driver. Reinstalling the OS is time-consuming and may not prevent the conflict from recurring if the same drivers are reinstalled.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
The most common cause is installing multiple drivers for the same device—for example, a generic driver from Windows Update and a manufacturer-specific driver. This often happens with printers, graphics cards, and network adapters. The solution is to remove all drivers for the device and install only the correct one. Use the 'Uninstall device' option in Device Manager and delete the driver package from the driver store if necessary.
Open Driver Verifier (verifier.exe) and select 'Create custom settings (for code developers)'. Choose standard settings (e.g., Special pool, Pool tracking, IRQL tracking). Then select 'Select driver names from a list' and choose the suspect driver(s). Reboot—the system will stress the driver. If a violation occurs, a BSOD with a bug check code will point to the faulty driver. To disable Driver Verifier, boot into Safe Mode and run 'verifier /reset'.
Yes. VIDEO_TDR_FAILURE (Timeout, Detection, and Recovery) occurs when the graphics driver does not respond within a specified timeout (default 2 seconds). This is often due to a conflict between the graphics driver and another driver (e.g., a capture card or virtualization software). To fix, update the graphics driver, roll back if recently updated, or disable the conflicting device. Also, increase the TDR timeout via registry (TdrDelay) as a temporary workaround.
Use the following commands: 'dmesg | grep -i conflict' to see kernel messages about resource conflicts. 'cat /proc/interrupts' shows IRQ assignments; look for multiple devices sharing the same IRQ line (though sharing is normal for PCI). 'cat /proc/ioports' shows I/O port allocations. 'lspci -v' shows PCI device resources. If a module is suspected, use 'lsmod' to list loaded modules and 'modprobe -r' to remove it.
A driver conflict is when two drivers try to use the same resource (IRQ, I/O, memory). A driver compatibility issue is when a driver is not designed for the current operating system version (e.g., a Windows 7 driver on Windows 10) or is incompatible with the hardware (e.g., a driver for a different chipset). Both can cause device failure, but conflicts involve resource contention, while compatibility issues involve API or architecture mismatches.
In enterprise environments, yes. Automatic driver updates can introduce conflicts with custom or manufacturer-specific drivers. Use Group Policy: Computer Configuration > Administrative Templates > Windows Components > Windows Update > 'Do not include drivers with Windows Updates' set to Enabled. On standalone PCs, you can pause driver updates via Settings > Windows Update > Advanced options > Pause updates, but this is temporary.
Boot into Safe Mode (F8 or Shift+Restart > Troubleshoot > Advanced options > Startup Settings > Safe Mode). In Safe Mode, the conflicting driver may not load, allowing you to access Device Manager. Disable or uninstall the problematic driver. If you can't boot into Safe Mode, use System Restore from the Windows Recovery Environment (WinRE). If all else fails, use a bootable USB to access the system and rename/delete the driver file (e.g., C:\Windows\System32\drivers\bad.sys).
You've just covered Troubleshoot: Driver Conflicts — now see how well it sticks with free 220-1102 practice questions. Full explanations included, no account needed.
Done with this chapter?