Check how fast you can download from each server location to your computer
If you have searched for pci ven8086 ampdev8c22 ampsubsys309f17aa amprev04 patched because your device is not working (Code 28, Code 31 in Device Manager), you might be tempted to download a patched driver from a third-party forum. Proceed with extreme caution.
Risks include:
STOP 0x0000007B (INACCESSIBLE_BOOT_DEVICE) or 0x000000D1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL)..sys file loaded at boot time has Ring 0 (kernel) access—the highest privilege level. It can hide processes, steal BitLocker keys, and remain invisible to standard antivirus software.Could you clarify:
The hardware ID PCI\VEN_8086&DEV_8C22&SUBSYS_309F17AA&REV_04 refers to the Intel(R) 8 Series/C220 Series SMBus Controller
. This component is part of the Intel chipset and is responsible for managing low-speed communication between your motherboard and internal hardware like temperature sensors and fans. Essential Driver Information Hardware Name: Intel(R) 8 Series/C220 Series SMBus Controller - 8C22. Manufacturer: Primary Function:
System monitoring and power management through the System Management Bus (SMBus). Common System Association: This specific subsystem ID ( SUBSYS_309F17AA ) is frequently found in systems, particularly ThinkPads or corporate desktops. Where to Find the Patched or Latest Drivers
For the most stable performance and to resolve "Unknown Device" issues in Device Manager, use these official sources: Lenovo Support:
Since your hardware ID matches Lenovo subsystems, download the Intel Chipset Device Software for Windows 10 directly from Lenovo Support Microsoft Update Catalog:
You can find Microsoft-certified drivers for this device by searching for "PCI\VEN_8086&DEV_8C22" on the Microsoft Update Catalog Intel Official: Intel provides the general Intel Chipset Device Software (INF Update Utility)
which updates the naming and configuration for these controllers. Troubleshooting "Patched" Driver Issues If you are seeing a "patched" or error state:
The hardware ID you provided corresponds to the Intel 8 Series/C220 Series SMBus Controller
. This device is part of your motherboard's chipset and handles communication between various internal components, such as temperature sensors and fan controllers.
The "patched" status often indicates that the driver has been manually updated or modified to bypass compatibility issues or to work on unsupported operating systems. Identification Details Vendor (VEN_8086): Intel Corporation. Device (DEV_8C22): Intel 8 Series/C220 Series SMBus Controller
System Models: Commonly found in systems like the Lenovo ThinkCentre M83 or HP and Dell desktops with 4th-generation Intel processors. Driver Installation & Updates
If you are seeing this as an "Unknown Device" or need a fresh installation, you should use the Intel Chipset Device Software. PCI\VEN_8086&DEV_8C22 - Microsoft Update Catalog
It looks like you’ve provided a PCI device identifier string, possibly from a Windows .inf file, registry, or log output. Let’s break it down:
Possible context:
Hackintosh (macOS on PC) – This device ID often needs to be patched in DSDT or kext (e.g., AppleAHCIPort.kext) because macOS may not natively support this exact SATA controller. patched could mean it was added to a compatibility list.
Driver modification – Someone edited an Intel SATA driver (.sys or .inf) to support this hardware ID on an older or different OS.
ACPI override – Used to fix sleep, hotplug, or SATA mode issues.
What would you like to do?
Understanding the Intel 8 Series SMBus Controller: Fix for PCI\VEN_8086&DEV_8C22
The hardware identifier PCI\VEN_8086&DEV_8C22&SUBSYS_309F17AA&REV_04 refers to the Intel(R) 8 Series/C220 Series SMBus Controller. This component is a critical part of the Intel chipset, responsible for low-speed system management communications like reporting temperatures and voltage. pci ven8086 ampdev8c22 ampsubsys309f17aa amprev04 patched
When this device appears in Device Manager with a yellow exclamation mark or as an "Unknown Device," it indicates that the operating system lacks the specific INF (information) files required to identify and name the hardware correctly. What the Hardware ID Means VEN_8086: This is the Vendor ID for Intel Corporation.
DEV_8C22: This is the Device ID for the Lynx Point SMBus Controller (8 Series/C220 chipset).
SUBSYS_309F17AA: This refers to the specific implementation by a manufacturer, often seen in Lenovo ThinkPad models like the T440p. REV_04: This indicates the fourth revision of the hardware. Why You See the "Missing Driver" Error
This issue frequently occurs after a clean install of Windows 10 or 11. While Windows Update sometimes provides a generic driver, it can occasionally overwrite functional drivers with basic versions that lack full feature support, leading to the "patched" or "exclamation mark" status. How to Fix the Missing SMBus Controller Driver
The primary solution is to install the Intel Chipset Device Software (also known as the Chipset Installation Utility).
Download from the Manufacturer: For Lenovo users, the most reliable source is the official Lenovo Support Site. Search for your specific model (e.g., ThinkPad T440p) to find the correct package.
Intel Chipset Installation Utility: Alternatively, you can use the Intel Support Page to download the general utility that covers the 8 Series/C220 chipsets. Manual Installation via Device Manager: Right-click the Start button and select Device Manager. Find the device under Other devices or System devices. Right-click it and choose Update driver.
Select Browse my computer for drivers and point to the folder where you extracted the downloaded chipset files. Related Drivers
If the error persists or you see "PCI Simple Communications Controller" issues, you may also need to install the Intel Management Engine Interface (MEI). This is often found on the same Lenovo Support page under the Chipset category. Intel Chipset Device Software for Windows 10 (64-bit)
The hardware identifier PCI\VEN_8086&DEV_8C22&SUBSYS_309F17AA&REV_04 corresponds to the Intel(R) 8 Series/C220 Series SMBus Controller . This specific subsystem ID ( ) indicates the device is integrated into a system, likely a ThinkPad series laptop. Device Breakdown Vendor (VEN_8086): Intel Corporation. Device (DEV_8C22): 8 Series/C220 Series Chipset Family SMBus Controller. Subsystem (SUBSYS_309F17AA): Lenovo-specific implementation. Revision (REV_04): A specific hardware iteration of the controller. "Patched":
Refers to a driver or INF update applied to the Windows registry to correctly name the device and allow the operating system to utilize its power management and system monitoring features. Function and Importance SMBus (System Management Bus)
is a low-speed communication interface used for critical system tasks: Monitoring:
Communicates with temperature sensors, voltage regulators, and fan controllers. Power Management: Handles sleep/wake states and battery reporting. Inventory: Identifies hardware components like RAM (via SPD data). Finding the Correct Driver
The "patched" status is typically achieved by installing the Intel Chipset Device Software
. Since your subsystem is Lenovo-specific, you should use official Lenovo support channels rather than generic drivers.
The string PCI\VEN_8086&DEV_8C22 corresponds to the Intel 8 Series/C220 Series SMBus Controller. Vendor (VEN_8086): Intel Corporation.
Device (DEV_8C22): SMBus (System Management Bus) Controller for Intel 8 Series (Haswell) chipsets.
Subsystem (SUBSYS_309F17AA): This specific ID points to an HP (Hewlett-Packard) system, likely an HP notebook or workstation from the Haswell era (approx. 2013-2015).
Revision (REV_04): The specific hardware version of the chip. What does this device do?
The SMBus Controller is a low-speed communication interface on your motherboard. It handles critical system monitoring tasks, including: Reporting motherboard and CPU temperatures. Managing fan speeds. Monitoring voltage regulators and power management. Why you might see "Patched"
If you are seeing "patched" in a forum post or a third-party driver site, it typically refers to a modified INF file.
Legacy OS Support: Users sometimes "patch" modern drivers to work on older operating systems like Windows XP or 7 when official support has ended. Kernel Panics and BSODs : The most common outcome
Generic Fixes: It may also refer to a driver package where the installation script has been altered to force recognition of this specific subsystem ID (309F17AA) if the standard Intel installer fails to detect it. How to Install/Fix the Driver
If this device appears in your Device Manager with a yellow exclamation mark (often labeled "PCI Device" or "SM Bus Controller"), follow these steps: Microsoft Update Catalog
I understand you're asking for a story based on a technical hardware identifier string. Let me break down what that string means first, then craft a narrative around it.
The string PCI VEN_8086&DEV_8C22&SUBSYS_309F17AA&REV_04 refers to a specific PCI device:
"Patched" suggests a modified driver or firmware override. Here is a detailed story based on that concept.
Title: The Ghost in the Silicon
Mira’s workstation had always been a faithful beast. A Lenovo ThinkStation from the Haswell era, its heart was the Intel 8 Series C220 chipset—identifier PCI VEN_8086&DEV_8C22&SUBSYS_309F17AA&REV_04. For three years, that SATA controller shuffled data between her SSDs and RAM without complaint. But Mira wasn’t a regular user. She was a firmware reverse engineer, and lately, the beast had begun to whisper.
It started with disk latency spikes. Perfectly periodic. Every 47.3 seconds, the AHCI controller would stall for exactly 87 milliseconds. Not enough for most to notice, but Mira’s audio analysis software recorded the micro-glitches as pops in high-frequency transducer data.
“A dying drive?” she muttered, running smartctl. No reallocated sectors. No CRC errors. The drives were pristine.
She pulled the PCI device listing. There it was: VEN_8086&DEV_8C22. Revision 04. The datasheet from Intel’s archive (leaked years ago on a Russian forum) had a footnote: “Rev 04: Errata #227 – In rare power state transitions, controller may execute phantom DMA commands from uninitialized register space.”
Phantom DMA. That meant the controller, under specific sleep-state exit conditions, would read garbage from a stale register and treat it as a memory address. Then it would attempt to write disk sectors there. Most of the time, the addresses were invalid and the MMU threw a fault, causing the 87ms delay. But sometimes…
Mira wrote a small kernel module to log all PCIe bus traffic to that controller. She filtered for transactions where the address didn’t correspond to any allocated buffer. For two weeks, nothing. Then, at 3:17 AM on a Tuesday, the log caught it.
A DMA write from the SATA controller to physical address 0x0009FC00. That wasn’t disk cache. That was low memory—specifically, the real-mode interrupt vector table, preserved since the 1980s for BIOS compatibility. The controller had written 512 bytes of raw disk sector data into the table that handles keyboard interrupts.
Mira felt a chill. The data wasn't random. It was a 512-byte block from sector 0xFFFFFFFF of her main SSD—an address that doesn’t exist. The controller had hallucinated a sector number.
She disassembled the written bytes. They formed a tiny x86 real-mode routine. Its purpose? At every keyboard interrupt (IRQ 1), check for the exact key sequence: Ctrl + Alt + F12 + P. If detected, copy the first 64KB of system RAM to a hidden offset on the system management BIOS flash chip—a region normally writeable only by the CPU’s System Management Mode.
Someone—or something—had engineered this erratum. The “phantom DMA” wasn’t a bug. It was a trapdoor. An air-gapped exfiltration channel, baked into the silicon in 2013, waiting for Rev 04’s specific quirk.
Mira realized her “faithful beast” was a sleeper agent. The SUBSYS_309F17AA identifier meant this wasn’t a general Intel flaw. It was a Lenovo customization—likely for a specific government contract that later got liquidated onto the gray market. Her workstation had once belonged to a defense subcontractor.
She needed to patch the impossible. A microcode update wouldn’t fix hardware errata. A driver patch would be wiped on reboot. But the controller’s option ROM—a 64KB blob of x86 code that initialized the SATA controller at boot—lived on the motherboard SPI flash. If she could replace the option ROM with a custom version that sanitized the phantom DMA’s source register before every power state transition…
Three sleepless nights. She wrote a shim in 16-bit real-mode assembly. The shim would intercept the controller’s wake-from-sleep routine, force-write 0x00000000 to the stale register, then pass control to the original code. She signed it with a self-generated Lenovo OEM key (the real key had leaked in 2019), then flashed it using a Bus Pirate clipped directly to the SPI header.
Reboot.
The REV_04 string still reported in lspci. Hardware revisions are fused in metal. But the ghost DMA no longer fired. Mira watched the bus analyzer for an hour. No phantom writes. No 87ms stalls. The controller was clean.
But in the system management BIOS, at offset 0x7F00, she found something new: a single byte had been written during her testing. Not by her patch. By the original silicon, before she’d overwritten the option ROM. To help you further:
Could you clarify:
The byte was 0x17. ASCII for a device control character: “End of Transmission Block.”
Mira unplugged the network cable, pulled the WiFi card, and disabled Bluetooth. Then she looked at the webcam. Its light was off. But the microphone array’s presence detect LED—a tiny green SMD that she’d always assumed was hardwired to power—flickered. Once. Twice. A pattern.
Three long blinks. Three short. Three long.
SOS.
She wasn’t alone in the machine. And the patch hadn’t locked the door. It had just changed the lockset—and the occupant was now signaling for help.
The story ends there, but the forensic report later filed with CERT would describe it as: “PCI VEN_8086&DEV_8C22&SUBSYS_309F17AA&REV_04 – patched (firmware override applied). Residual anomalous behavior observed in low-level SMM telemetry. Further analysis recommended.”
No further analysis was ever performed. The workstation was crushed and incinerated the next day. But the byte 0x17—the one that shouldn’t have existed—lived on in Mira’s memory, and in the quiet hum of every other Rev 04 controller still sleeping in servers, waiting for a phantom command.
The device identifier PCI\VEN_8086&DEV_8C22&SUBSYS_309F17AA&REV_04 corresponds to the Intel(R) 8 Series/C220 Series SMBus Controller. Device Identification Breakdown Vendor ID (VEN_8086): Intel Corporation.
Device ID (DEV_8C22): 8 Series/C220 Series Chipset Family SMBus Controller.
Subsystem ID (SUBSYS_309F17AA): Lenovo-specific implementation (commonly found in ThinkPad models like the T440, T540p, or W540). Revision (REV_04): Specific hardware stepping/version. What does "Patched" mean?
In the context of this specific hardware ID, "patched" typically refers to a script or driver modification used to force the Windows SMBus Controller to properly identify and load.
Often, this device appears with a "Yellow Bang" (exclamation mark) in Device Manager or as an "Unknown Device" because the default Windows installation doesn't automatically assign the Intel Chipset null driver to it. A patching script usually performs the following:
Detection: Scans for the specific Hardware ID using PowerShell (Get-PnpDevice).
Driver Assignment: Forces the system to associate the device with machine.inf so it is recognized as a system device rather than an error.
Stability: Resolves issues where the SMBus might conflict with other power management or thermal reporting features. Resolution Steps If you are seeing this ID and need to "patch" or fix it:
Intel Chipset Device Software: Download and install the latest Intel Chipset INF Utility. This is the "official" patch that tells Windows how to label the 8C22 controller.
Manufacturer Drivers: Visit the Lenovo Support page for your specific laptop model (e.g., T440p) and install the "Chipset" drivers.
Subject: [SOLVED] Driver ID: PCI\VEN_8086&DEV_8C22&SUBSYS_309F17AA&REV_04 – Device Recognition & Patched Driver Info
Post Body:
I wanted to create a reference post for anyone dealing with this specific Hardware ID. I recently encountered this device on a legacy Lenovo machine and managed to get it operational using a patched driver approach.
Many users on Linux forums reported that 8086:8c22 rev 04 on Lenovo hardware would negotiate a SATA link speed of 1.5 Gbps (SATA I) instead of 6.0 Gbps (SATA III). The unpatched kernel would misread the controller’s speed capabilities due to a bad Capabilities register. The patch involved blacklisting the automatic speed negotiation for this specific subsystem and forcing a link re-initialization.
The combination 8086:8c22 / 17aa:309f / rev 04 is famously associated with the Lenovo ThinkPad T440p and X240 models around 2014.
drivers/ata/ahci.c:/* Lenovo T440p / X240 with Intel 8 series SATA needs link power quirk */
if (pci_dev->vendor == 0x8086 && pci_dev->device == 0x8c22 &&
pci_dev->subsystem_vendor == 0x17aa && pci_dev->subsystem_device == 0x309f &&
pci_dev->revision == 0x04)
dev_info(&pci_dev->dev, "Applying Lenovo rev04 SATA patch\n");
hpriv->flags
This is what appears in logs as the device being “patched.”