Hi SyKy - cheers for checking back.
Nope still not working (as in my previous post cut and pasted here) =
> Quote
> "I'll report back tomorrow with
![[sad] [sad] [sad]](/data/assets/smilies/sad.gif)
or

> Well it's a
![[sad] [sad] [sad]](/data/assets/smilies/sad.gif)
> I did it all last night.
> re ran the 823980 patch as suggested by SyKy
> did a trendmicro housecall online scan
> ran SpyBot (latest dat file)
> ran AdaWare (latest dat file)
> ran McAfee (latest dat file)
> Checked that my W2K pro was fully up to date thro mickysoft update scan.
> dissabled my LAN to isolate the PC
> all to no avail
> so will keep searching for the cause
> you can see know where my sig comes from !
However this morning I got this from another site I have been in comunication with =
Hi,
Sorry I didn't get back to you sooner..
I recently found a solution to the problem I was having that might work for you. After my last crash I decided to hit "Cancel" instead of "OK" to fire up the Visual Studio debugger to see what happened. I looked at the call stack and saw that the process that actually generated the error was something called "SENS", which is a service that svchost.exe hosts.
To make a long story short, SENS is the "System Event Notification Service" which "Tracks system events such as Windows logon, network, and power events. Notifies COM+ Event System subscribers of these events". I disabled this service and haven't had the problem again..
There's a more detailed write-up at
Since you're getting the svchost crash shortly after connecting to the internet it sounds like it could be this System Event Notification Service that's causing the problem.
Thanks again for visiting and writing!
-Hugues
I'll have a look tonight and report back tomorrow.
JB - N.W. - UK....
If at first you don't succeed, keep at it until you can't even think straight !
JB - N.W. - UK....
If at first you don't succeed, keep at it until you can't even think straight !