Chipset packages identify platform devices and may install functional components for power management, GPIO, SMBus, or other controllers, depending on the platform and package release. Intel specifically describes its Chipset INF Utility as installing INF information used primarily to display the correct product names in Device Manager; it is not a universal performance driver. AMD package contents and supported chipsets, processors, and Windows releases vary by release and must be checked in the posted release notes. For a self-built PC, use the exact motherboard model and hardware revision where the maker distinguishes revisions.
For a prebuilt or laptop, prefer the PC maker's model-specific package. Install only components listed for that hardware and Windows release; a general vendor support selector does not establish that every package supports every board.
A chipset driver does not draw anything or make a sound; its job is to describe the motherboard's own controllers to Windows so the operating system loads the right code for each one. It names the PCI Express lanes, the Sata and NVMe storage links, the SMBus that reads sensors, and the power management interface, so that later drivers for storage, USB, and networking attach to devices Windows can actually identify. Without it, the machine still boots, but Device Manager fills with unnamed controllers and the platform runs in a generic, conservative mode.
Package contents vary by chipset, processor generation, Windows release, and vendor build. Some AMD packages include processor power-management components; a separately visible AMD power plan is not universal on current platforms. Intel Management Engine and Rapid Storage Technology are separate platform components where the system maker lists them, not features supplied by the Chipset INF naming utility itself.
Expanded guide insight
The practical motherboard chipset context
Chipset packages give Windows the right names, relationships, and power-management rules for platform hardware. They are foundational, but they do not replace every individual driver.
Many chipset package entries are identification INF files.
Run Windows Update completely before manual chipset work.
Treat sleep and wake issues as platform-wide clues.
Take care: Identify an unknown device by Hardware IDs before installing a platform package manually.
Fast checks for common motherboard chipset problems
What you see
Likely area to check
Safe first move
PCI Device or SM Bus Controller is unknown
A platform component was not identified
Run Windows Update, including Optional updates
Code 10 or Code 43 appears after a change
The component is not loading correctly
Use rollback or a restart before reinstalling packages
Sleep or wake becomes unreliable
Power policy or platform driver mismatch
Run the Windows Power troubleshooter
Start with the lowest-risk check that matches what you see, then return to the detailed sections below if it does not resolve the issue.
Identify your exact device first
Open Device Manager and check System devices, where the chipset's named controllers appear once the driver is installed.
Look for entries under Other devices with a yellow warning; these are controllers the chipset file has not yet named.
Identify the CPU platform, AMD or Intel, since that decides which chipset package and companion drivers apply.
For a self-built PC, read the motherboard model and revision printed on the board itself.
For a prebuilt or laptop, use the service tag or model number on the chassis to reach the validated package.
On Intel systems, check whether a Management Engine interface entry is present, since it often accompanies the chipset file.
10/11 only where listed for the exact platform package
Delivered inside the Surface driver and firmware pack for the model
Scan the list first, then open the family that matches your hardware for the full reference.
Reference coverage summarizes the Windows releases discussed in this catalog; it is not certified compatibility. Confirm the exact device or PC model, hardware revision, current Windows release, and current package requirements on the publisher source before making a change.
Reference coverage: 10/11 only as listed in the release notes
AMD's Ryzen chipset package installs the components selected for supported AMD chipsets. Supported chipsets, processors, component drivers, and Windows versions vary by package, so use AMD's product selector and read Driver Details and the release notes. A visible AMD power plan is package- and platform-dependent, not evidence that every AM4 or AM5 system needs the same bundle. Prebuilt owners should first check the system maker's package.
How you recognize it
AMD Ryzen platform supported by the selected package release
Components listed by the installer and release notes
AMD chipset devices under System devices
Do not infer support from the AM4/AM5 socket alone; check the current package release notes.
Reference coverage: 10/11 only where listed for the exact platform package
Threadripper is AMD's high-end desktop and workstation platform, with its own sockets and chipsets separate from mainstream Ryzen. The chipset package handles the larger array of PCI Express lanes these boards expose along with the platform's power and storage controllers. Because the socket and chipset differ from consumer Ryzen, use the Threadripper-specific package rather than the mainstream one, matched to your exact board.
How you recognize it
Applies to AMD Threadripper workstation and high-end desktop boards
Boards expose a large number of PCI Express lanes
Uses a Threadripper-specific socket distinct from mainstream Ryzen
Reference coverage: 10 and 11 x64 where the package lists the chipset
Intel describes this utility as installing Windows INF information, primarily the product names shown for supported hardware in Device Manager. It generally does not install functional controller drivers or by itself improve performance. A PC or motherboard maker may provide a model-specific package; check the package's supported products before installing.
How you recognize it
Intel chipset product listed for the selected package
Provides INF names shown in Device Manager
Does not replace separate functional drivers
This INF utility primarily identifies supported hardware in Device Manager; it is not a universal performance driver.
Reference coverage: 10/11 only where listed for the exact platform package
The Management Engine interface driver connects Windows to a small typically-on subsystem on Intel platforms that handles power management and certain platform features. It is a companion to the chipset naming file and is frequently required alongside it for stable sleep and resume. Install it from the same source as the chipset package, matched to your board or system, rather than as a standalone afterthought.
How you recognize it
Appears as a Management Engine interface entry in Device Manager
Companion to the Intel chipset INF on Intel platforms
Linked to power management and platform stability
Often required alongside the chipset INF on Intel platforms.
Reference coverage: 10/11 x64 only where the selected RST package lists support
Intel RST supplies storage-controller, Raid, and VMD support on specifically listed Intel platforms. It is not a general performance upgrade for every single-drive system. Intel's current 20.2 package is scoped to 12th through 15th Gen Intel Core platforms, requires a VMD-capable Bios for VMD, and lists particular Windows 10/11 x64 releases; older generations use different packages. Prefer the PC or board maker's package when it is provided.
How you recognize it
Intel platform and controller listed in the selected RST package
Raid or VMD configured and supported by firmware
Exact processor generation and Windows release checked
Select RST by processor generation and controller mode; do not treat one package as universal.
Reference coverage: 10/11 only where listed for the exact platform package
These are the chipset packages ASUS validates for its motherboards, bundling the AMD or Intel platform driver with board-specific utilities and descriptors. For a self-built PC with an ASUS board, this tested package is a safer choice than the raw silicon-vendor file because it matches your exact model and revision. Read the board name from the silkscreen and select the corresponding download.
How you recognize it
Listed under a specific ASUS board model and revision
Bundles the AMD or Intel platform driver with ASUS utilities
Look up your ASUS board model for the tested chipset package and utilities.
Reference coverage: 10/11 only where listed for the exact platform package
Gigabyte publishes chipset packages per board, wrapping the AMD or Intel platform driver together with the descriptors and tools tested for that model. Because a similar-looking board may use a different chipset generation, the correct file is the one named for your exact board and revision. Confirm the model designation printed on the board before downloading.
How you recognize it
Listed under a specific Gigabyte board model and revision
Wraps the AMD or Intel platform driver for that board
Reference coverage: 10/11 only where listed for the exact platform package
MSI's chipset drivers are keyed to individual boards, delivering the AMD or Intel platform package validated for that model. On a self-built MSI system this tested version keeps the board's controllers, USB descriptors, and power tables aligned with the firmware. Identify the board from its silkscreen or box and pull the matching chipset download.
How you recognize it
Listed under a specific MSI board model
Delivers the AMD or Intel platform package for that board
Reference coverage: 10/11 only where listed for the exact platform package
ASRock provides chipset packages per motherboard, pairing the AMD or Intel platform driver with the descriptors tested for that model and revision. As with other board makers, the correct file depends on the exact board, since chipset generations differ across the range. Check the model name on the board when choosing the download.
How you recognize it
Listed under a specific ASRock board model and revision
Pairs the platform driver with board-specific descriptors
Reference coverage: 10/11 only where listed for the exact platform package
Dell validates chipset and I/O drivers for its complete desktop and laptop systems, tuned to the board and firmware Dell shipped in each unit. Because Dell boards often use customized power tables, this OEM package is a better fit than a generic AMD or Intel file. Use the service tag on the chassis to reach the exact drivers for your machine.
How you recognize it
Looked up by Dell service tag on the chassis
Tuned to Dell's customized board firmware and power tables
Prebuilt Dell systems use the service tag lookup for validated drivers.
Reference coverage: 10/11 only where listed for the exact platform package
Lenovo publishes chipset and I/O packages per machine type across its desktops and laptops, matching the platform driver to the firmware in that build. On ThinkPad and other business systems the validated package matters because power and I/O behavior are tuned as a set. Find the machine type on the unit's label and take the corresponding chipset download.
How you recognize it
Looked up by Lenovo machine type on the unit's label
Matches the platform and I/O driver to the system firmware
Look up your machine type for the correct chipset and I/O package.
Reference coverage: 10/11 only where listed for the exact platform package
HP ships customized chipset packages for its prebuilt desktops and laptops, aligned with the board and firmware in each configuration. Because HP boards carry their own descriptors and power settings, the model-specific package is the often the better choice over a generic silicon-vendor download. Identify the system by its product name or serial number to reach the right file.
How you recognize it
Looked up by HP product name or serial number
Customized to HP board firmware and descriptors
Prebuilt HP systems ship customized chipset packages; use the model lookup.
Reference coverage: 10/11 only where listed for the exact platform package
Acer validates chipset drivers for its desktops and laptops, matching the AMD or Intel platform driver to the board Acer shipped in each model. As with other prebuilt makers, the OEM package accounts for firmware and power tuning a generic file may not. Look the machine up by its model name to obtain the tested chipset download.
How you recognize it
Looked up by Acer model name
Matches the platform driver to Acer's shipped board firmware
Reference coverage: 10/11 only where listed for the exact platform package
Surface devices deliver chipset support inside a combined driver and firmware pack that Microsoft maintains per model, rather than as a separate chipset installer. Much of it also arrives through Windows Update, so keeping the system current usually keeps the platform drivers in step. If you need to refresh manually, install the Surface pack built for your exact device.
How you recognize it
Delivered inside the Surface driver and firmware pack for the model
Much of it arrives through Windows Update
No standalone chipset installer separate from the pack
Surface devices use a combined driver and firmware pack from Microsoft.
Device Driver Guide does not host, mirror, or alter driver files. The official-source citations below are maintained separately from this reference material and never point to third-party mirrors.
Where the correct package usually comes from
For a self-built desktop, the motherboard maker's support page for your exact board and revision is the right source. It carries a chipset package tested against that board, often bundled with board-specific utilities the raw silicon-vendor download omits. Choosing the wrong board revision can install descriptors that do not match your firmware, so confirm the model precisely before downloading.
For a prebuilt desktop, laptop, or Surface, prefer the system maker's support site with your service tag or model. OEM boards frequently use customized firmware and power tables, and their validated driver accounts for those where a generic AMD or Intel package would not. If Windows Update has already replaced an OEM chipset driver with a generic one, reinstalling the maker's package may restore the board-specific behavior.
Official sources and citations
These links serve two different purposes. A manufacturer support selector helps you find an exact model, but does not prove that a package or feature exists for every product in a family. Claim-specific documents explain the cited technology, requirement, lifecycle, or bounded package example. In either case, check the publisher domain, exact model and hardware revision, operating-system release, supported-products list, and package notes before making a change.
Microsoft Lifecycle: Lifecycle documentation for Windows 10 Home and Pro; separately governed editions and servicing channels can have different dates.
Microsoft Surface: Use this publisher-maintained page to match the exact Microsoft Surface model and operating-system release before selecting a package.
Device Driver Guide is an independent reference, not a repair or technical-support service. It does not host or mirror installers and receives no payment for these links. A named-model package example applies only to the systems and operating systems on that publisher page; it is not a recommendation to install the package across a family. Report a moved or incorrect link through the correction form.
Motherboard Chipset reference tables
Where the chipset package should come from
Your hardware
Correct source
Why it is better
What a generic file misses
Self-built desktop
Board maker page for the exact model and revision
Tested against your firmware
Board-specific utilities and descriptors
Prebuilt desktop
OEM support site by service tag or model
Matches customized power tables
OEM-tuned sleep and I/O behavior
Laptop
PC maker support site by model
Validated for the chassis and firmware
Model-specific power and USB tuning
AMD platform, any build
AMD or the maker chipset software
Installs the boost-aware power plan
The CPU does not run at designed boost
Surface
Surface driver and firmware pack, Windows Update
Platform support integrated per model
There is no standalone chipset installer
The right source depends on whether you built the machine or bought it whole.
Symptom to likely cause to first safe step
Symptom
Likely cause
First safe step
Yellow-marked unknown devices
Controllers the chipset INF generally is not named
Install the matching chipset package, then reboot
Storage slower than expected
Missing platform storage driver
Install the storage driver, confirm firmware mode matches
Sleep and resume misbehave
Missing power or Management Engine driver
Install the full chipset package and power components
AMD CPU will not boost
No AMD processor power plan present
Install AMD chipset software, select the plan, retest
USB ports dead after a Bios update
Descriptors no longer match firmware
Reinstall the board maker chipset package
Installer says unsupported platform
Wrong chipset generation downloaded
Confirm the exact board or system, get the matching version
Quiet chipset problems and the least disruptive way to address them.
AMD and Intel chipset packages compared
Aspect
AMD platform
Intel platform
Core package
Single chipset software bundle
Chipset INF naming utility
Power behavior
Installs the processor power plan and boost driver
Relies on the Management Engine interface
Storage driver
Handled within the bundle
Rapid Storage Technology where applicable
Companion pieces
Usually one installer
Management Engine, plus storage where used
Skip it and
CPU does not boost as designed
Sleep and resume turn erratic
The two platforms deliver chipset support differently, which changes what you install.
Fresh-install driver order
Order
Install
Why this position
1
Chipset package
Names the controllers so later drivers attach cleanly
2
Reboot
Lets Windows re-enumerate the bus
3
Storage and Management Engine
Depend on named controllers being present
4
Network
May restore connectivity for remaining downloads
5
Graphics and audio
Attach last to identified devices
The sequence that lets each driver attach to a correctly named controller.
When updating helps, and when it does not
Install the chipset driver early on a fresh Windows setup, before storage, network, graphics, and audio, so those drivers attach to correctly named controllers. Reinstall or update it when you change the CPU or motherboard, apply a firmware update that alters USB or storage descriptors, or when you are chasing a specific power, storage, or unknown-device problem. On AMD systems, install it to get the boost-aware power plan working.
There is no benefit to chasing every chipset release on a stable machine. Once the controllers are named, sleep works, and storage runs at expected speeds, the driver is doing its job and reinstalling it only risks disturbing a working setup. Treat firmware changes and hardware swaps as the real triggers rather than the version number alone.
Before you install anything
Determine whether you own a bare motherboard or a full prebuilt or laptop system, since the source differs.
Note the exact board model and revision, or the service tag or model number for a prebuilt.
Identify the CPU platform so you download the AMD or Intel package that matches.
On a fresh install, plan to run the chipset package first, before other device drivers.
Have any needed companion drivers in mind on Intel, such as the Management Engine interface.
How to update motherboard chipset drivers
1
Determine whether you own a board or a full system
If you built the PC, you will use the motherboard maker's page and your board model. If it is a prebuilt desktop, laptop, or Surface, use the OEM's site and its service tag or model lookup for validated drivers.
2
Install the chipset driver before other device drivers
On a fresh Windows install, run the chipset package first. It labels the motherboard's controllers so later drivers for storage, USB, and networking attach to correctly identified devices.
3
Add the platform companion drivers
On Intel systems, install the Management Engine interface and, where applicable, the storage technology driver. On AMD systems, the single chipset package handles these and installs the processor power plan.
4
Reboot and check Device Manager
Restart the computer, then open Device Manager and confirm there are no entries under Other devices with a yellow warning. A clean list means the chipset correctly enumerated the bus.
5
Verify the power plan and storage mode
Confirm the expected power plan is available and that storage reports the correct mode in the vendor utility. This catches cases where a generic driver loaded instead of the platform package.
Confirm the install actually worked
Open Device Manager and confirm there are no yellow-marked entries under Other devices.
Check that the chipset's controllers appear named under System devices.
Confirm the expected power plan is available and, on AMD, that the processor power plan is present.
In the vendor storage utility, confirm the controller reports the correct mode for how the drive is installed.
Reboot and re-open Device Manager to confirm the bus enumerated cleanly after the change.
Undoing a bad motherboard chipset install
If a chipset update causes unknown devices, storage regressions, or sleep problems, reinstall the package you trust for the board or system rather than removing it outright; a platform running without any chipset driver falls back to a generic, slower mode. On a prebuilt, reinstall the OEM package so the board-specific descriptors return.
Where a single companion driver is at fault, such as an Intel storage or Management Engine component, reinstall that piece from the same matching source rather than the whole platform bundle. After any change, reboot so Windows re-enumerates the bus, then confirm Device Manager is clean before deciding the rollback succeeded.
Downloading a package for the wrong chipset generation causes the installer to report an unsupported platform.
A missing Management Engine or power driver on Intel systems leads to erratic sleep and resume.
Skipping the AMD chipset package leaves the CPU without its boost-aware power plan.
Windows Update can replace an OEM chipset driver with a generic one that omits board-specific tables.
A firmware update that changes USB or storage descriptors can leave ports or drives misbehaving until the chipset driver is reinstalled.
Installing device drivers before the chipset file on a fresh setup can leave controllers unnamed.
Mistakes to avoid with motherboard chipset
Installing graphics or audio drivers before the chipset file, so controllers are left unnamed.
Skipping the AMD chipset package and then blaming the CPU for does not reach its boost speeds.
Grabbing a generic silicon-vendor file for a prebuilt, losing the OEM power and I/O tuning.
Downloading a package for the wrong chipset generation and forcing it past the unsupported warning.
Ignoring a firmware update that changed USB or storage descriptors until ports quietly fail.
Assuming the machine is fine because it boots, while it runs in a generic, conservative mode.
Leaving Windows Update's generic chipset driver in place instead of reinstalling the OEM build.
Situations readers arrive with
I just did a clean Windows install and Device Manager is full of unknown devices with yellow marks.
Those are controllers the chipset file has not named yet. Identify whether the CPU is AMD or Intel, then install the chipset package from your board or system maker before anything else. Reboot afterward so Windows re-enumerates the bus, and confirm the unknown entries have cleared.
My new AMD build feels sluggish under load and the CPU does not seem to be hitting its rated speeds.
The AMD chipset software installs the processor power plan and boost driver, and without it the CPU stays conservative. Install the current AMD chipset package for your board, then select the recommended power plan in Windows. Retest under load and confirm the plan is present in power options.
After a Bios update, half my USB ports stopped working.
A firmware update can change USB controller descriptors so the old driver no longer matches. Reinstall the current chipset package from your motherboard maker for your exact board revision. Reboot so the ports re-enumerate, then confirm Device Manager is clean before assuming a hardware fault.
The chipset installer keeps telling me my platform is unsupported.
That usually means the download is for a different chipset generation. Return to the vendor page, confirm your exact board or system model and revision, and pick the matching platform version. Do not force a neighboring package, since it can install descriptors that do not match your firmware.
My prebuilt used to sleep fine, but after a Windows update it wakes randomly and storage feels slow.
Windows Update may have swapped the OEM chipset driver for a generic one that omits board-specific tables. Reinstall the OEM chipset package from your system maker using the service tag or model. Reboot, then test sleep and confirm the storage driver reports the correct mode.
Symptom-by-symptom troubleshooting
Unknown devices with yellow marks in Device Manager
These are controllers the chipset INF did not name. Install the correct chipset package for your platform or OEM model, then reboot so Windows re-enumerates the bus.
NVMe or Sata storage performs below expectations
Install the platform storage driver, such as Intel Rapid Storage Technology on supported Intel boards, and confirm the controller mode in firmware matches how the drive was installed.
Sleep and resume behave erratically after a clean install
A missing power management or Management Engine driver often causes this. Install the full chipset package and the vendor's power components, then test sleep again.
AMD CPU does not boost as expected
Install the AMD chipset software so the AMD processor power plan and boost driver are present. Then select the recommended plan and retest under load.
Windows Update replaced the OEM driver with a generic one
On prebuilt systems, reinstall the OEM chipset package from the vendor site. OEM-customized drivers account for board-specific power and I/O tables that the generic version omits.
USB ports or headers stop working after a Bios update
Reinstall the current chipset package so the USB controller descriptors match the updated firmware. Prefer the motherboard maker's version for your exact board revision.
The chipset installer reports an unsupported platform
You likely downloaded a package for a different chipset generation. Return to the vendor page, confirm your board or system model, and download the matching platform version.
Frequently asked questions
Do chipset drivers actually improve performance?
They can. Correct storage, power management, and processor drivers let the platform run as designed. On AMD systems the chipset package installs the boost-aware power plan, which has a direct effect on CPU behavior.
I built my own PC. Where do I get chipset drivers?
Use your motherboard maker's support page and enter your exact board model. That package is tested against your board and often includes utilities the raw silicon-vendor download omits.
I have a prebuilt desktop or laptop. Same source?
No. Prefer the OEM's support site with your service tag or model number. OEM systems use customized firmware and power tables, so their validated driver is the safer choice.
What order should I install drivers on a fresh Windows setup?
Install the chipset driver first, reboot, then add storage, network, graphics, and audio. Installing chipset first helps ensure later drivers attach to correctly identified controllers.
Is the Intel Management Engine driver part of the chipset?
It is a companion component on Intel platforms and is frequently required alongside the chipset INF for stable power management. Install both from the same source.
Should I update the chipset driver regularly?
There is no need to chase every release. Update when you install Windows fresh, change the CPU or board, update firmware, or when you are troubleshooting a specific device or power problem.
Will a chipset driver update overwrite my Bios?
No. Chipset drivers are Windows software that describe the hardware to the operating system. Firmware updates are a separate process performed from the board's firmware utility.
Terms used on this page
Chipset INF
The file that names the motherboard's controllers so Windows loads the right drivers for them.
Management Engine
An Intel subsystem whose interface driver supports power management and platform features.
PCI Express lanes
The high-speed connections the chipset provides to graphics cards, storage, and add-in devices.
SMBus
A low-speed bus the chipset uses to read sensors and manage components on the board.
Processor power plan
The AMD power profile installed with the chipset package that enables designed boost behavior.
Bus enumeration
The process by which Windows discovers and identifies devices attached to the platform's buses.
Device Driver Guide stores a local consent preference to remember your choice. Replit Project Analytics may measure visits and selected site interactions. These local choices do not turn hosting analytics on or off. Custom events exclude form entries and other free-form content. No advertising scripts are active. Read the Cookie Policy.
