inspiron 24 5410 alder lake I5 missing smbus/spi controller drivers

Inspiron 24 5410 (intel).  Device manager shows 3 items under "other", with yellow ?.

 Quote  "The latest Intel ME driver Dell offers for Inspiron 24 5410 is 2208.16.0.2718, A01."

This was originally installed but failed to load the drivers for the SMbus/SPI controllers, that's why I went to the Intel support assistant, but that failed too.

So the problem still exits

Many thanks for clarifying yr initial response, the driver you identified resolved the smbus/spi controller issues.

Brilliant

I have passed this on to Dell, as I spent 2 hours on the phone with them and got no where.  I have passed on the info re the driver you identified, so they might include it in their support module for their Inspiron 24 5410

Glad that solved the problem... !

You never explained why the Chipset drivers were missing. Did you reinstall Windows or were the Chipset drivers missing, right from the beginning of time?

The Chipset driver is listed in a "funny" place for most Dell PC models these days. It's now typically listed under Utilities rather than under Drivers on the Drivers/Download Support page. In the past it was always under Drivers and I don't know why Dell moved it.

To complicate the matter, Dell is incorrectly listing an AMD Chipset under Drivers on the Support page for the Inspiron 24 5410. This PC doesn't have an AMD CPU, so that driver shouldn't even install. (I've notified my Dell tech contacts about this irrelevant driver.)

In reply, Its a new AIO, but frankly we dislike Win 11, from a support aspect its easier to support if all PCs use the same OS..  This therefore was a clean install, downloading all drivers the Dell support app gave.  Often find that the SMbus can be an issue, however in the past has been resolved by downloading chipset drivers.  Lesson learned with Dell - look at the utilities!

As a matter of interest I spent an hour with Dell Tech support, they had no idea where the SMbus/spi controller drivers were - I have sent the lady yr info!

The BIOS on this system is also a little unreliable - refused to go back to default settings (Ver 1.10).

Thanks again

Surprising that Windows didn't install the Chipset driver automatically during the clean install, or at least after you booted up and Windows Update scanned for updates.

SupportAssist can frequently overlook the Chipset driver, possibly because it's classified as "Utilities".

How did you try to reset BIOS to defaults? Did you get an error message? Has an admin password been set?

Don't know if you'd want to open the PC up, but one way to reset BIOS is to unplug power cord from PC, press/hold power button for ~15 sec. Then open it up, and remove motherboard battery. Press/hold power button for ~30 sec and then reinstall battery. Close up and BIOS should be back to default settings.

CAVEAT: That assumes default BIOS settings are suitable for your installed hardware and are appropriate for your user environment.

Re BIOS, first no other kit attached, yes we could remove the bios battery but wasn't necessary.

Here's what happened:

1. Dell initially indicated that there was a critical update for the BIOS, which was successfully installed, and I mean successful!

2.With the smb/spi issue I noticed the achi/nvme option  wasn't ticked. Ahh I said so ticked it and updated the BIOS and restarted updated the BIOS.  From then on the system wouldn't boot.

3. Next, was the option to (i) undo the change - no success, (ii) set back to defaults - no success.

4. Decided to reinstall Win 10, which was successful, however the BIOS now does have the ACHI/NVME box ticked.

All very strange, leaves questions as to why it wouldn't boot after the initial BIOS change, and why when reloading win10 why it would - something between BIOS & BCD?  

whatever the cause it says this latest BIOS version isn't stable.

Re:  leaves questions as to why it wouldn't boot after the initial BIOS change

Although it's too late, but I hope my answer can clear up your lingering question.  Your system may have shipped with SATA operation in RAID mode.  After you changed it to AHCI, the HDD/SSD could not boot because it didn't have a proper storage controller driver installed.  Usually, it could be resolved by allowing the BSOD (bluescreen) cycling through, on the third boot attempt, it would present you with the Recovery Environment options, selecting start up repair with option 4, system would restart in Safe Mode and gave Windows a chance to self installing AHCI controller driver.  Restart again, your system would have booted properly again.  

Re:  and why when reloading win10 why it would - something between BIOS & BCD? 

When you installed operating system again with storage controller already set in AHCI mode, a proper driver would be installed during installation, therefore, it would work after reboot.  At this point, if you mess with the BIOS settings and changing to RAID, your system will crash again.

For summary, if you need to change SATA operation mode in BIOS for whatever reason, you will need to boot into Safe Mode right after a change in BIOS, this would give your boot drive a chance to get proper controller driver installed.  You can also control the booting to Safe Mode using bcdedit method. 

@robmar1se  - @Chino de Oro  said it all, and types faster than I do.

Bottom line - stop messing about and start using this new PC.  LOL!