NickR wrote:
> On September 27th, when I was shutting down my PC, there were pending windows
> updates and it shows a progress 1 of 1 installing updates during shutdown.
> Some time into the process I got an svchost.exe - Application Error.
>
> The instruction at 0x745f2780 referenced memery at 0x00000000. The memory
> could not be read. After that errror the machine would no longer respond.
>
> Now every time I boot, about a minute after windows boots, regardless if I
> login or just leave the login prompt up, I get the same error. If I send the
> bug report or click OK or Cancel to the error, windows stops respond and will
> not even shut down.
>
> My system is no longer usable.
As has now been reported in many places, this very frustrating problem
appears to have started sometime after the July updates.
See this thread in the
"microsoft.public.windows.server.update_servic es" newsgroup:
http://www.microsoft.com/communities...4-e79c86974dce
You can read the many suggested solutions, but to see what I've tried
you can start with my responses to Lawrence Garvin on 9-15-2006.
There are apparently many manifestations of this problem, with some
folks like you experiencing it at boot time, some while Windows is
running, and others at shutdown time when an update is pending (which
is the problem I'm experiencing on numerous computers). The common
factors are that it started after the July updates, and it occurs when
or after an update is attempted.
As I explained in detail there, to troubleshoot this I have disabled
all non-Microsoft startup programs, services, drivers, handlers,
components, BHOs, shell extensions, toolbars, etc., as well as many
Microsoft services I don't need. With Windows running at bare minimum,
I still have this problem. I also tried several suggested solutions,
all to no avail.
I am convinced this is a Microsoft problem induced by a recent update,
and may very well involve MSI.DLL. However, the suggested hotfix 914810
does not fix it, but instead changes the error to '0x476122d0'.
Uninstalling that hotfix makes it revert to the '0x745f2780' error. Of
course MSI.DLL did not get replaced recently, so there is obviously
some other factor involved.
For many of us this is becoming a critical situation, and we need a fix
very soon. The extremely frustrating thing about it is that no one can
tell us if or when Microsoft might even start to look at it, or how we
can get their attention to do so.
John Gruener
Americomp, Inc.