Request and question in one: my home-built PC has a Base System Device without a driver. i installed teh chipset package, but it's still there. i'd love to know how to identify it properly. Is there a reliable way to map it to a specific driver from ASRock or my PC maker? i'd really prefer to avoid driver updater tools, so official sources only. Thanks in advance for any pointers.
MYSTERY BASE SYSTEM DEVICE IN DEVICE MANAGER. HOW TO FIND THE RIGHT DRIVER
did u install teh PC makers package or teh generic one from ASRock?
sorry forgot to say i installed teh generic chipset package, not the PC makers.
Open Device Manager > device > Properties > Details > Hardware Ids 🤦 The
VEN_xxxx&DEV_xxxxpart identifies the vendor and device. searching that ID (or checking teh INF files in a driver package) tells you which package covers it.been there man +1 same here fingers crossed 🤞
help!! i swear system is cursed. have u checked your ms-dos settings? 😤 mine were reset after an update what am i doing wrong??
Common mappings: SM Bus Controller usually needs the chipset package; PCI Simple Communications Controller is often teh Management Engine interface; Data Acquisition and Signal Processing Controller often relates to thermal or platform drivers. lmk how it goes
@sorent613 turns out 4CoreDual-SATA2 Bios 2.10 for DOS did include it, I just needed to reboot after the instlal... thanks!
Related topics
- PCI Data Acquisition And Signal Processing Controller After A Clean Install. What Is It And Do I Need It?
- REQUEST: DRIVER FOR PCI SIMPLE COMMUNICATIONS CONTROLLER ON MY DESKTOP
- Found The Right Driver For SM Bus Controller Using Hardware IDs
- which asrock package fixes the unknown device with a yellow mark??
- Mystery SM Bus Controller in Device Manager. How to find the right driver
- Found the right driver for Unknown device using hardware IDs
Reply to this topic
Sign in or create an account to reply.
