WMI Provider Host high high CPU usage and constant errors in Event log

I have an Inspiron 3737 Laptop running latest W10 version 21H2 and have experienced problems with the CPU constantly running at 100% for some time, with the 'WMI Provider Host' process taking up to 45% CPU. This makes everything run dead slow. When I look at the 'Windows\WMI-Activity->Operational' Event Log I see pairs of warnings and errors occurring twice every SECOND. This looks quite bad.

Warning: Namespace = root\wmi; NotificationQuery = select * from biosevent; UserName = XXXXXXXXX\xxxxxx; ClientProcessID = 15852, ClientMachine = XXXXXXXXXX; PossibleCause = Temporary

Error: Id = {00000000-0000-0000-0000-000000000000}; ClientMachine = XXXXXXXX; User = XXXXXXXX\xxxxxx; ClientProcessId = 15852; Component = Unknown; Operation = Start IWbemServices::ExecNotificationQuery - root\wmi : select * from biosevent; ResultCode = 0x80041032; PossibleCause = Unknown

I think the process ID referred to is the Dell Quick Set process.

I am reasonably "technical" and I have spent a lot of time searching the internet about this issue and seen similar issues in the Dell Community, but nothing exactly the same. Certainly not Garmin Express as reported  by Saintsfc76 in a 2020 post on this discussion. To summarise it appears the WMI Provider Host should normally have a low CPU impact but is being affected by another process(s). If I go into Services.msc and restart the WMI Provider Host it reports that 4 other services are affected and also need to be restarted: IP Helper, Intel(R) Rapid Storage Technology: Dell Data Vault Service API & Dell Data Vault Collector.

I have had some success with restarting WMI Provider Host and killing some of the Dell processes like Quick Set, Data Vault etc. At the moment my CPU seems to be running more normally but I cannot stop the WMI errors occurring. I am suspicious that a Dell process is to blame. 

Can anyone help me to understand his issue better? I would really like to stop the repeated WMI Provider Host errors on the assumption that this was the root cause of the high CPU state.

Martin

P.S. I know my machine is 8 years old but I have looked after it and kept all my software up to date. Unfortunately it is not compatible with Windows 11 (shame on Microsoft) so the clock is ticking but I don't want to give up on it just yet. It has a 17" screen and those models are pricey.