How To Check Chipset Driver Version On Windows 10 And 11: A Technical Step-by-Step Guide

To identify your motherboard's active chipset driver version on Windows, open Device Manager, expand the System Devices category, right-click a primary controller such as the Intel SMBus or AMD PCI Bus, and view the version under the Driver tab. Validating this version against the latest package release from Intel or AMD ensures optimal PCI Express lane distribution, power state management, and overall system stability.

System Requirements & Pre-Check Diagnostic Essentials

The motherboard chipset acts as the central communications hub of your computer, routing data between the Central Processing Unit (CPU), system memory, graphics cards, and peripheral storage interfaces. Unlike graphics drivers, chipset drivers are primarily a collection of configuration files (such as Intel INF files) and specialized bus drivers (such as AMD PEP or GPIO drivers) that instruct the operating system how to interface with onboard silicon.

Checking these versions is a crucial troubleshooting step when experiencing USB dropouts, system sleep-state failures, or storage throughput degradation. Before query execution or diagnostic testing, prepare the following resources to ensure an efficient audit.

• Essential Diagnostic Tools: Windows Device Manager (devmgmt.msc), System Information Utility (msinfo32), and Windows PowerShell with administrative privileges.
• Prerequisite Knowledge: The exact model of your motherboard (such as ASUS ROG STRIX Z790-E or Gigabyte B650 AORUS ELITE) and the CPU architecture (Intel Core or AMD Ryzen).
• Estimated Duration: 5 to 10 minutes.
• Financial Cost: $0 (utilizes native operating system utilities and official manufacturer verification channels).

Methodical Walkthrough to Identify Your Motherboard's Chipset Driver Version

Step 1: Identify Your Motherboard Model and Current Chipset

Before verifying driver versions, you must determine what chipset architecture is soldered onto your motherboard.

1. Press the Windows Key + R on your keyboard to open the Run dialog box.
2. Type msinfo32 into the text field and press Enter to launch the System Information panel.
3. In the System Summary window, locate the BaseBoard Manufacturer and BaseBoard Product entries in the right-hand pane.
4. Note down the values. For example, a BaseBoard Product of Prime Z690-A indicates an Intel Z690 chipset, while a B650M DS3H indicates an AMD B650 chipset.

Step 2: Access Device Manager and Expand System Devices

Windows manages core motherboard controllers under a specific subsystem category in the Device Manager.

1. Right-click the Start Menu button and select Device Manager from the power user menu, or type devmgmt.msc into the Run dialog box and press Enter.
2. Scroll down the alphabetically ordered hardware tree until you find System devices.
3. Click the arrow icon to the left of System devices to expand the category. This action exposes the core silicon controllers managed by the chipset drivers.

Step 3: Locate and Inspect Core Chipset Components

Because a chipset consists of multiple controllers, there is no single entry labeled Chipset Driver. Instead, you must inspect specific anchor components based on your processor platform.

For Intel-based motherboards:

1. Scroll down the System devices list to find the Intel SMBus Controller or the Intel LPC Controller (sometimes labeled as the eLPC Controller or Low Pin Count Controller).
2. Right-click Intel SMBus Controller and select Properties.
3. Click the Driver tab at the top of the properties window.
4. Locate the Driver Version field. This displays the currently active Intel Chipset Device Software version (for example, 10.1.19444.8378).

For AMD-based motherboards:

1. Scroll down the System devices list to locate the AMD PCI Bus, AMD GPIO Controller, or AMD SMBus.
2. Right-click AMD PCI Bus (which manages the communications pathway between the CPU and external PCIe expansion cards) and select Properties.
3. Navigate to the Driver tab.
4. Read the version listed next to Driver Version (for example, 5.12.0.38).

Pro-Tip: AMD chipset packages contain several distinct drivers. While the AMD PCI Bus driver is the most reliable indicator of your overall chipset driver status, you should also check the AMD GPIO Controller and AMD I2C Controller versions within this same list to ensure the complete package installed correctly.

Step 4: Extract Driver Versions via Windows PowerShell

If you are managing remote workstations or prefer a command-line interface, Windows PowerShell can query the Plug and Play (PnP) driver database directly to retrieve chipset version numbers without clicking through graphical menus.

1. Press the Windows Key, type PowerShell, right-click Windows PowerShell, and select Run as Administrator.
2. To extract Intel chipset driver information, type the following command exactly as shown, then press Enter:

Get-PnpDevice -PresentOnly | Where-Object {$_.FriendlyName -match "Intel.*SMBus|Intel.*LPC"} | Get-PnpDeviceProperty -KeyName DEVPKEY_Device_DriverVersion

1. To extract AMD chipset driver details, input this command and press Enter:

Get-PnpDevice -PresentOnly | Where-Object {$_.FriendlyName -match "AMD.*PCI|AMD.*GPIO"} | Get-PnpDeviceProperty -KeyName DEVPKEY_Device_DriverVersion

1. The output console will return the precise driver version strings currently registered by the Windows kernel for those hardware IDs.

Intel vs. AMD Chipset Architecture & Versioning Conventions

To understand whether your installed driver is outdated, you must understand the differences between Intel and AMD driver structures. Intel distributes the Intel Chipset Device Software, which is not a traditional driver but a collection of INF configuration files that rename generic Windows system entries to their correct Intel hardware naming schemes. AMD, conversely, distributes actual driver binaries that actively manage hardware states, such as power plans and USB communication lines.

The table below contrasts the technical characteristics, target devices, and versioning paradigms for both platforms.

Resolving Device Manager Misidentifications & Driver Mismatches

Scenario 1: The Chipset Controller Displays a Yellow Exclamation Mark or "Unknown Device"

• Root Cause: Windows has failed to map the hardware ID of the SMBus, LPC, or GPIO controller to an active driver structure, leaving the system component in an unconfigured state. This commonly occurs after a clean reinstall of Windows before any motherboard drivers have been applied.
• Actionable Fix: Obtain the hardware ID of the unknown device by right-clicking it in Device Manager, selecting Properties, navigating to the Details tab, and selecting Hardware Ids from the dropdown. Match the Vendor ID (VEN_8086 for Intel, VEN_1022 for AMD) and Device ID. Download the offline chipset executable installer from your motherboard manufacturer support page, extract it, run the installer as an administrator, and reboot your system.

Scenario 2: Intel Chipset Driver Version is Displayed as Year 1968 (Release Date 07/18/1968)

• Root Cause: This is an intentional design choice by Intel. Intel backdates all its INF configuration files to July 18, 1968—the day Intel was founded. This extremely old date ensures that the Windows Operating System driver rank engine will prioritize any newer custom third-party drivers or specific manufacturer updates over the generic Intel INF files.
• Actionable Fix: Do not attempt to update or roll back this driver based on the date. To verify if your driver is current, look solely at the numerical version string (e.g., 10.1.19444) rather than the release date of 1968, and compare that sequence to the latest release on the Intel download portal.

Scenario 3: AMD Chipset Installer Fails or Throws "Error 1720" During Installation

• Root Cause: Leftover registry entries, corrupt Windows Installer service configurations, or conflicting driver footprints from a previous AMD platform installation block the installer execution script.
• Actionable Fix: Download and run the AMD Cleanup Utility to strip all legacy display and chipset registry blocks from your OS. Next, open a Command Prompt with administrative rights and run the command sfc /scannow to repair any damaged Windows installer modules. Restart your PC, temporarily disable third-party antivirus utilities, and run the AMD Chipset Software installer directly from your local root directory (typically C:).

Scenario 4: USB Ports Drop Connection Under Heavy System Load After a Driver Update

• Root Cause: Power management protocols (specifically PCIe Link State Power Management or USB Selective Suspend) within the updated AMD GPIO or Intel PCIe Controller drivers are turning off controller hubs to conserve energy, resulting in packet loss for high-bandwidth peripherals.
• Actionable Fix: Open Device Manager, expand Universal Serial Bus controllers, select your primary host controller, open its Properties, navigate to Power Management, and uncheck "Allow the computer to turn off this device to save power." Additionally, check for a motherboard BIOS update, as newer BIOS packages often contain updated AGESA (for AMD) or microcode (for Intel) fixes that address USB controller instability.

Frequently Asked Questions

Is it necessary to update chipset drivers regularly?

No, chipset drivers do not require monthly updates like graphics card drivers. You should only update your chipset drivers when installing a new CPU, performing a clean installation of Windows, encountering system stability issues like unexpected restarts, or when the motherboard manufacturer issues a critical security patch in their documentation.

What is the difference between an Intel INF utility and a standard driver?

An Intel INF utility is an information file that does not contain executable code or driver binaries. It simply contains text-based configuration instructions that identify the hardware to the operating system, change generic device names to their correct branding, and configure system resources. A standard driver, such as an AMD PCI Bus driver, contains active compiled machine code that manages data transmission and hardware states.

Why does my chipset driver version in Device Manager differ from the package version I downloaded?

A chipset installer is a bundled suite containing multiple discrete drivers (such as GPIO, I2C, SMBus, and PSP). The installer suite version (e.g., AMD Chipset Software 6.02.22.053) refers to the collective installer wrapper, whereas the individual drivers installed to your system components will have their own independent, lower-level version numbers (e.g., AMD PCI Bus Driver 5.12.0.38) within Device Manager.

Can a faulty chipset driver cause Blue Screen of Death (BSOD) errors?

Yes. Because chipset drivers govern critical operations like memory controller communications, PCIe lane routing, and CPU power state transitions, a corrupted or incompatible chipset driver can easily trigger critical system errors. Common stop codes associated with faulty chipset files include SYSTEM_SERVICE_EXCEPTION, DRIVER_IRQL_NOT_LESS_OR_EQUAL, and CLOCK_WATCHDOG_TIMEOUT.

Optimize Your Motherboard's Performance and Stability

Ensure your system hardware operates at maximum efficiency by cross-referencing your detected driver versions with the latest validated releases from your motherboard manufacturer. For enterprise IT architectures, remote system audits, and comprehensive endpoint hardware deployment support, contact our systems engineering team today to schedule an operational health audit.