Windows 10: LG Gram Crashing with the error "Host process for windows service stopped working" in...

Hi, The reliability monitor showed this when I woke up the laptop from sleep mode to see it restarted. There are also a few other errors such as IntelAudioService stop working.From what I could tell, there was no error screen, I only noticed these from reliability monitor.

:)

 

Host Process for Windows Services has stopped working

everytime i start up my computer i get the error "Host Process for Windows Services has stopped working" i cant play games without it, is there any fix?

 

Nokia Service Layer Host Process Has Stopped Working

I've just updated to version 7.1.30.8 of Nokia's PC Suite and on doing so I get a message telling me that there is an update for my phone waiting for download... same old story: 'Nokia Service Layer Host has stopped working'... EXCEPT this time it seems
to be immune to the fixes listed here. I've tried disabling internet sharing (which worked last time) but Nokia's tool crashes still.



Any further suggestions, other than buying a new phone?



p.s. do Nokia even realise that Window's Vista exists??????

 

Host processes for Windows tasks - stopped working

Hi, in reply to previous correspondents. I tried the Forum suggested by 'jdc1' and while there have been many viewers there is no suggestion of remedy - so far.
Searching further in this matter I find that a similar post also appears in this Forum - see here:
Host Process For Windows Tasks stopped working, Windows 10 1903
and once again many viewers but no remedy.
In Reliability Monitor there is a link to: How to report an error: I followed this link to Microsoft Community - see here:
https://answers.microsoft.com/en-us/...c-db4c1d0592f3
Where there are numerous complainants for this problem. There is one reply ( to-date) of a suggested solution by Microsoft which appears not to be the cure and quite a few more insistent*Devil posts for Microsoft to get this sorted.
The posts themselves include suggested cures like sfc/scannow and DISM which I like many others have tried to no avail. There seems to be a strong leaning towards blaming the 1903 update for this error. One person does indicate a solution which worked for him which is to via System & Storage to click the box to run now and remove earlier Windows Updates. I have just tried this myself and will report the result within the next few days.
Other correspondents are awaiting for further answers in the 'Community' from Microsoft.
So once again time will tell but it would appear that Microsoft are dragging their heels on this one.
Cheers.
.