The Correct Motherboard Chipset Install Order

On a fresh Windows install, the order you load drivers in isn't a superstition; it's the difference between a clean Device Manager and a list of mystery devices with yellow triangles. The chipset is the traffic controller for your motherboard's buses, so when it goes in last, everything installed before it can end up mapped to the wrong lanes or half-recognized. Load things in the sequence the hardware expects and each later driver slots neatly onto a foundation that's already correct. Here's the order that works and the reasoning behind each stage.

1. 1

   Understand why order matters

   The chipset driver teaches Windows how your motherboard's internal pathways are laid out: the PCIe lanes, the USB controllers, the power management links, and the connections between the CPU and everything else. Until Windows knows that map, other drivers are attaching to a foundation that isn't fully defined yet. Install a network or audio driver before the chipset and it may bind to a controller Windows only partly understands, leaving you with odd errors that persist even after the chipset finally goes in. Loading the chipset first means every later driver lands on hardware Windows already describes correctly.

2. 2

   Start from a clean, updated Windows

   Begin with a completed Windows installation that has been through at least one pass of Windows Update. Open Settings, go to Windows Update, and click Check for updates, then install what it finds and reboot. Windows ships with generic drivers that keep the screen, mouse, and network working well enough to do this. Getting Windows itself current first prevents it from fighting you later by swapping in its own driver mid-process. Once updates are done and the system is stable at the desktop, you have the clean baseline you need before touching vendor drivers.

3. 3

   Install the chipset driver first

   This is the keystone. Download the chipset package for your exact motherboard model from the board maker's official support page, then run it and follow the prompts. On Intel platforms this is often called the Chipset Device Software; on AMD it's typically the AMD chipset driver package. It may not appear to do much visibly, but it's registering all those buses and controllers with Windows. Reboot when it finishes, even if the installer doesn't demand it. Everything you install after this point depends on the map this step just laid down, so don't skip the restart.

4. 4

   Add storage and management drivers next

   With the buses defined, load the drivers that sit closest to the platform itself. On Intel systems this includes the Management Engine (ME) interface and, if applicable, the Rapid Storage Technology (RST) driver for your storage controller. On AMD systems the chipset package often covers these already, so check what's actually listed as separate. These low-level components handle storage access and background platform functions, and having them in place early keeps later devices from misreading how disks and controllers are wired. Reboot afterward if prompted before moving up the stack.

5. 5

   Install networking, then audio

   Now bring the system online properly and give it sound. Install the wired LAN driver and, if you have it, the Wi-Fi and Bluetooth drivers, all from your board maker's official support page. A working network lets Windows fetch anything it still needs. Once networking is solid, install the audio driver, commonly a Realtek or vendor-branded package. Audio drivers ride on the buses the chipset already mapped, which is why they come after it rather than before. Reboot when each installer asks, and confirm sound plays and the network connects before continuing.

6. 6

   Install the GPU driver last

   Save the graphics driver for the end. By now the chipset has defined the PCIe lanes your graphics card actually uses, so the GPU driver installs onto a fully described slot instead of a placeholder. Get the driver from the graphics chip maker's official page or your board or laptop vendor for integrated graphics. Choose a clean install if the installer offers it, then reboot. Installing the GPU last also avoids the common mess of a high-resolution driver loading before the platform underneath it is ready, which can cause flickering or resolution problems on a fresh setup.

7. 7

   Verify no unknown devices remain

   Finish by auditing your work. Right-click the Start button and choose Device Manager, then look down the whole list for any yellow warning triangles, question marks, or entries under "Other devices." Each one is a piece of hardware still missing its proper driver. Right-click any problem entry, choose Properties, and read the Details tab's Hardware Ids to identify what it is, then find the matching driver on the appropriate official support page. A clean Device Manager with no unknown devices means your install order did its job and every component is talking to Windows correctly.