This post is more than 5 years old
2 Intern
•
219 Posts
0
64775
April 18th, 2015 10:00
SM Bus Controller Problem
If I'm asking this question in the wrong forum, please advise. Thanks.
I have a Dell Inspiron 620, 64 bit, running Win7, SP1.
Device Manager shows SM Bus Controller does not have a driver, and can't find one. I used the Intel Driver Update Utility to identify my driver, downloaded and installed the driver. Everything about the download and install looked normal, but after restart, Device Manager still showed No Driver. I tried a manual installation and got a Windows Error
I double checked the Intel Driver version, it shows as 15.28.23.64.4101 (9.17.10.4101). When I check the Intel HD Graphics Properties, it shows the device is working normally and the Driver Version is 9.17.10.4101, which is what the Intel Driver Update Utility said it should be. Is that driver NOT the missing driver referred to in Device Manger for the SM Bus Controller? I'm thoroughly confused. Can anybody help me? Thanks.
rdunnill
6 Professor
•
8.8K Posts
1
April 18th, 2015 19:00
I am unfamiliar with the version numbers, but installing the latest Win7 Intel chipset drivers should work. I did update them on an OptiPlex 390, which shares its motherboard with the Inspiron 620.
It shouldn't matter if other drivers are already installed; you should be able to update the chipset drivers to the latest version. For some reason, the Windows 7 SP1 install disk often has some of the chipset drivers, but not the SM Bus one.
RoHe
10 Elder
•
45.2K Posts
2
April 18th, 2015 19:00
Except the error message in your OP says Intel HD Graphics, so it's not a chipset driver.
There's a chipset driver for your model here. It may not be the latest, but install it and see if the SMB error goes away in Device Manager.
You may want to install it after rebooting in Safe Mode (reboot and press F8 before Windows starts to load. Select Safe Mode + Networking from the menu.)
After installing the chipset (either in normal or Safe Mode), shut down normally and reboot normally. Then check Device Manager.
rdunnill
6 Professor
•
8.8K Posts
0
April 18th, 2015 13:00
The SM Bus driver is part of the chipset driver package. I suggest that you go to Intel's download site and update your chipset drivers. Afterwards, try to update your onboard video driver there.
I am not sure if Dell supported Windows 7 for use with the 620.
shelquis
2 Intern
•
219 Posts
0
April 18th, 2015 13:00
You did notice I said " I used the Intel Driver Update Utility to identify my driver, downloaded and installed the driver"?.
I bought the computer new from Dell with Win7 installed? Why wouldn't they support it?
rdunnill
6 Professor
•
8.8K Posts
0
April 18th, 2015 14:00
No, I didn't. Meanwhile, this is a very common problem. The 'SM Bus' driver is part of the chipset drivers package, and its malfunctioning is remedied via reinstalling the chipset driver package.
I didn't know that. Some of these older models were supported for Vista, but not 7.
rdunnill
6 Professor
•
8.8K Posts
0
April 18th, 2015 16:00
Intel Chipset Software Installation Utility
A missing SM Bus driver is a symptom of incorrect chipset driver installation. We regularly get complaints here concerning this issue.
shelquis
2 Intern
•
219 Posts
0
April 18th, 2015 16:00
I used the Intel Driver Update Utility to identify my driver, downloaded and installed the driver. Everything about the download and install looked normal, but after restart, Device Manager still showed No Driver.
Is there some other driver that I need besides the one Intel identified (15.28.23.64.4101 (9.17.10.4101).)?
shelquis
2 Intern
•
219 Posts
0
April 18th, 2015 17:00
If you have a fresh install of the operating system on your computer,
I had to reinstall Win7 abut a month ago.
run the Intel® Chipset Software Installation Utility to make sure the operating system recognizes the chipset components.
Looking at the Intel® Chipset Software Installation Utility, it appears I should install v.10.0.26. Agree? If so, should I run it now?
It is important to run the utility before installing any other device drivers or service packs.
Well, it's too late for that now. I have no recollection of the sequence I installed device drivers. SP1 was (I believe) installed simultaneously with Win7. How do I proceed from here?
shelquis
2 Intern
•
219 Posts
0
April 18th, 2015 19:00
Thanks. I'm done for the night. I'll try this tomorrow and get back to you. Thanks.
shelquis
2 Intern
•
219 Posts
0
April 19th, 2015 06:00
OK. Problem solved. Thanks to you both, RoHe and rdunnill. I installed v. 10.0.26, and that cleared everything up. The SM Bus Controller error went away, and the Intel Chipsets now show up in Device Manager under System devices (and they hadn't before).
rdunnill
6 Professor
•
8.8K Posts
0
April 19th, 2015 10:00
Glad we could help!
RoHe
10 Elder
•
45.2K Posts
0
April 19th, 2015 13:00
Glad you got it sorted...But...:emotion-60:
Now you have to think about why the chipset driver suddenly disappeared (or got corrupted) in the first place.
rdunnill
6 Professor
•
8.8K Posts
0
April 19th, 2015 16:00
For some reason, the Windows 7 SP1 install disk will install most of the chipset driver set, apart from the SM Bus one. As the OP had reinstalled Windows, it may be that the driver was never properly installed.
RoHe
10 Elder
•
45.2K Posts
0
April 19th, 2015 18:00
Maybe I missed it, but I don't see where the OP reinstalled Windows....
All I see is an attempt to reinstall the chipset, which is why I suggested some additional steps to make sure the system isn't having problems that could have caused the SM bus driver to disappear...
shelquis
2 Intern
•
219 Posts
0
April 20th, 2015 08:00
Thinking back on it, I believe the chipset driver was not installed when I reinstalled Win7 SP1 about a month ago but I didn't realize it at the time. I thought all necessary drivers had been installed. I believe I remember seeing the SM Bus Controller error a couple of weeks ago but ignored it because it wasn't causing a problem. Well, while trying to troubleshoot a new problem, I thought that the SM Bus Controller problem may be a solution (but it wasn't). :(