To update motherboard chipset drivers, identify your exact chipset, download the current chipset package from the chipset maker (AMD) or your board maker (Intel and AMD), run the installer, restart, and then confirm in Device Manager that no entries show a warning icon. The whole job takes about 15 minutes on a normal system, and the only part that goes wrong often is picking the wrong download. This guide walks through each step for both platforms, adds a short decision flow so you do not update when there is no reason to, and lists the signs that mean you should stop and contact support.
Scope note: the chipset package is separate from the BIOS, graphics, audio and network drivers, so updating one does not update the others. Menu names on vendor sites change, so follow the on-screen wording and your board manual, and always follow the manufacturer’s instructions for your model.
What a chipset driver does and why the source matters
The chipset sits between the processor and most of the other hardware on the board: extra USB ports, SATA ports, some M.2 slots, the PCIe lanes that are not wired directly to the CPU, and several power-management and system-management functions. Windows ships generic drivers for most of this, so a fresh install usually boots and works. The vendor package replaces generic entries with ones that identify the real hardware, and on AMD platforms it can also install a power plan and low-level system components.
Two sources are normal, and which one you pick depends on the platform. AMD publishes a single chipset package for its desktop platforms on its own support site. Intel publishes a chipset device software package, often called the INF utility, and most board makers also mirror a version of it on the product page for your exact board. Both routes are legitimate. The mistake to avoid is a third-party mirror or a driver-finder site, because you lose the release notes and the ability to confirm the package matches your hardware.
| Platform | Primary source | Secondary source | What the package typically contains | Watch out for |
|---|---|---|---|---|
| AMD desktop | AMD support site, chipset section | Board maker’s download page for your model | Chipset and system drivers, plus a power plan | Choosing the package for the wrong socket family |
| Intel desktop | Intel download center, chipset device software | Board maker’s download page for your model | INF files that name the chipset devices correctly | Installing an older INF over a newer one |
| Prebuilt or laptop | The PC maker’s support page for your serial or model | Chipset maker, only if the PC maker has stopped updating | Packages tuned by the PC maker | Generic packages can override vendor-tuned power settings |
Step 1: Find out which chipset you have
You need the board model, and from it the chipset family. There are four reliable ways to read it, and the first one needs nothing but Windows.
- Press the Windows key plus R, type
msinfo32, and press Enter. Look at the BaseBoard Manufacturer, BaseBoard Product and Processor lines. The product line holds the board model, such as a name that includes the chipset letter and number. - Read the board itself. The model is printed on the PCB, often between the PCIe slots or near the CPU socket, and the chipset heatsink or a label sometimes carries the chip family.
- Check the box, invoice or the original manual if you still have them.
- Use a hardware information utility from a reputable publisher and read its Mainboard tab. Cross-check the result against the board maker’s product page.
Write down three things: the board model, the CPU socket, and your Windows version (Windows 10 or 11, 64-bit). Those three facts decide which download page you open. If msinfo32 returns a generic or blank board name, which happens on some prebuilt systems, use the PC maker’s support page and your serial number instead of the chipset maker’s site.
Step 2: Decide whether you should update at all
Updating is not always the right answer. A chipset package is low risk, but any install can change behavior, and “newer” does not always mean “needed”. Use this short decision flow before you download anything.
| Question | If yes | If no |
|---|---|---|
| Is anything broken: USB devices dropping, SATA drive missing, sleep or wake failing, yellow warning marks in Device Manager? | Update now, then retest the symptom | Go to the next question |
| Did you just reinstall Windows, change the CPU or flash a new BIOS? | Update once, after the BIOS and before other drivers | Go to the next question |
| Does the release note for the new package mention your platform or a fix you care about? | Update at a convenient time | Go to the next question |
| Is the installed package more than a year old and the system is stable? | Optional; do it when you have a spare half hour | Leave it alone |
Treat the last row honestly. Chipset updates rarely change gaming performance, so a stable machine does not need a monthly refresh. A reasonable habit is to check at build time, after major Windows feature updates, and when a symptom appears.
Step 3: Update chipset drivers on an AMD board
- Open the AMD support site and find the chipset section for desktop processors. Choose your socket family and then the chipset that matches your board, or choose the board maker’s page if AMD’s list does not name your exact chipset.
- Pick your Windows version and download the chipset software installer. Save it somewhere you can find it, such as the Downloads folder.
- Create a restore point. Search for “Create a restore point” in the Start menu, select your system drive, and press Create.
- Close other programs and run the installer as an administrator. Accept the defaults unless the release notes tell you otherwise.
- When the installer finishes, restart even if it does not ask you to. Many entries do not take effect until the next boot.
- After the restart, open Settings, then Apps, and confirm the AMD chipset entry is listed with the newer version number.
One AMD-specific point: the package can install a power plan. If you use a custom Windows power plan, check Power Options afterward and choose the plan you want. A mismatch here causes complaints about fan noise or idle clocks that people wrongly blame on the update itself.
Step 4: Update chipset drivers on an Intel board
- Open your board maker’s support page for your exact model, find the chipset section, and note the version and date of the package. If you prefer the source, the Intel download center hosts the chipset device software.
- Download the installer for your Windows version. Do not mix an installer meant for a different chipset generation, even if the file name looks similar.
- Create a restore point as described above.
- Run the installer, accept the licence terms, and let it finish. The Intel package mostly writes INF files, so it can look as if nothing happened. That is normal.
- Restart, then open Device Manager and expand System devices. Entries that were generic should now carry specific names.
Intel boards also have separate packages for the management engine interface, the storage controller and the Wi-Fi and Bluetooth hardware. If Device Manager still shows an unknown device after the chipset package, one of those may be missing rather than the chipset itself. If you are comparing boards or checking which CPU generation a board supports before updating, the guide to which CPU fits which board covers the socket and chipset pairing.
Step 5: Confirm the update worked
Work through this checklist after the restart. Each line takes under a minute.
| Check | Where to look | Pass looks like |
|---|---|---|
| Installed version | Settings, Apps, installed list | New version number appears for the chipset package |
| No warning icons | Device Manager, expand every category | No yellow triangle and no “Unknown device” entries |
| USB behavior | Plug in a keyboard, mouse and a storage device | All devices detected and stay connected |
| Storage visible | File Explorer or Disk Management | Every SATA and NVMe drive shows with its normal capacity |
| Sleep and wake | Put the PC to sleep, then wake it | Wakes without a blank screen or a restart |
| Event log | Event Viewer, Windows Logs, System | No repeating driver or hardware errors since the reboot |
If you use several M.2 drives, confirm they all still appear, because some boards share lanes between slots. The article on M.2 slots, keys, lengths and sharing explains why a drive can disappear for reasons unrelated to drivers.
Troubleshooting a failed or odd chipset update
Most failures fall into a handful of patterns. Work from the simplest fix to the most disruptive.
- The installer refuses to run or says the platform is not supported. You probably have the package for another chipset family or an architecture mismatch. Go back to Step 1, re-read the board model, and download from the page for that model.
- The install finishes but a device still shows a warning. Open its properties, read the hardware ID, and search that string on your board maker’s page. The device may belong to a different package.
- Problems start right after the update. Open Device Manager, right-click the affected device, and choose Properties, then Driver, then Roll Back Driver if the button is available. If not, use the restore point you made, which reverts system files and driver registrations.
- Random freezes persist. Chipset drivers are rarely the cause of freezes. Memory settings, a BIOS profile, a failing power supply or an overheating component are more common. Check temperatures and revert any overclocking profile before blaming the package.
When to stop and contact support or replace hardware
Stop updating and contact the board maker if the system fails to boot after a BIOS flash, if devices vanish and return at random, or if Windows reports hardware errors in Event Viewer that survive a clean reinstall. A repeating pattern on a clean install suggests a hardware fault or a seating issue, not a software one. Do not keep installing alternate packages from random sites; every extra install makes the fault harder to trace.
If the board is still within its warranty period, describe what you tried, including the package names and the order of steps, because support will ask. If the board is out of warranty and the same symptoms follow you through a clean reinstall, treat a replacement as the realistic option rather than an endless series of driver changes. If you are unsure about opening the case, reseating components or flashing firmware, ask a qualified technician.
Related guides
- Noctua Nh-D15 Vs Thermalright Peerless Assassin 120
- Sustainable Gaming Pc Power Supply Efficiency Guide
- Thermal Paste Application Method For Lga1851
Frequently asked questions
How often should I update chipset drivers?
There is no fixed schedule. A sensible rhythm is a check when you build or reinstall Windows, after a major Windows feature update, when you install a new CPU or BIOS version, and whenever you see odd USB, SATA or sleep behavior. If the system is stable and the package on your PC is only a few months old, leaving it alone is reasonable. Chipset packages rarely change frame rates, so they are about stability and device recognition rather than speed.
Is it safe to use a driver updater utility instead of the manufacturer download?
It is safer to avoid them. Generic updater tools match hardware IDs loosely, may offer packages for a different chipset family, and often bundle extras you did not ask for. The chipset maker and your board maker both publish free packages with release notes. Download from those pages, check that the product name matches your board or chipset, and install one package at a time so you know which change caused a problem if one appears.
Do I need to update chipset drivers after a BIOS update?
Not always, but it is a good moment to check. A BIOS update changes how the board describes its hardware to Windows, and a newer chipset package sometimes lists support for those changes in its release notes. Update the BIOS first, boot into Windows, then install the chipset package if the notes mention your platform or if Device Manager shows unknown devices. Keep the order consistent so any new issue can be traced to one step.
Will a chipset driver update improve gaming performance?
Usually not in a measurable way. The chipset package handles the links between the CPU and storage, USB, networking and power management. On AMD systems the package can also carry a power plan, which may change how quickly cores ramp up, so a small difference is possible. On Intel systems the package mostly installs INF files that label devices correctly. Treat it as maintenance that prevents problems, not as an upgrade.
What if the installer says it is already up to date but Device Manager shows an unknown device?
Note the hardware ID from the unknown device’s properties and search that exact string on your board maker’s support page. The unknown entry may belong to a different component, such as a management engine interface, a Wi-Fi card or a storage controller, which comes from a separate package. If the board maker has no matching download, run Windows Update once, reboot, and check again before reinstalling anything.
