Latest Update Cooked my XP system

[GaryDean]

Yesterday afternoon (10/14/06) the latest Windows update began installing
when I shut down my system. I came back to see it still running 2 hours
later. I waited until it had been running for 5 hours when I turned the
system off. It booted up with a problem directing me to the fix. I applied
the fix. Now I get svchost.exe Application error dialog saying...

The instruction at "0x745f2780" referenced memory at "0x00000000". The
memory could not be read.

What can I do?

 

[Shenan Stanley]

Yesterday afternoon (10/14/06) the latest Windows update began
installing when I shut down my system. I came back to see it still
running 2 hours later. I waited until it had been running for 5
hours when I turned the system off. It booted up with a problem
directing me to the fix. I applied the fix. Now I get svchost.exe
Application error dialog saying...
The instruction at "0x745f2780" referenced memory at "0x00000000". The
memory could not be read.

What can I do?

Boot to safe mode - system restore to the day before the patches started
applying...

 

[(PeteCresswell)]

Per GaryDean:

The instruction at "0x745f2780" referenced memory at "0x00000000". The
memory could not be read.

What can I do?

Restore from that "good" system image that you burned once you had your install
working the way you wanted and then apply whatever incremental
changes/application installations that you kept notes of since that last image
was burned.

Tongue-in-cheek..... but seriously, it works for me with an adolescent abusing
my system day-after-day.

I use TeraByte's DOS "Image" utility. Works like a charm.

 

[dev]

/GaryDean/ said:

Yesterday afternoon (10/14/06) the latest Windows update began installing
when I shut down my system. I came back to see it still running 2 hours
later. I waited until it had been running for 5 hours when I turned the
system off. It booted up with a problem directing me to the fix. I applied
the fix. Now I get svchost.exe Application error dialog saying...

The instruction at "0x745f2780" referenced memory at "0x00000000". The
memory could not be read.

Do try Stanley's suggestion. But sometimes that doesn't do the deed.
Pete's implied advice is more encompassing - an imaging utility that
will restore EVERY file and setting to what it was - in minutes, not hours.

Image for Windows (IFW) and Image for DOS (free with IFW) are excellent
for that purpose.
Check out http://terabyteunlimited.com - perhaps take the 30 day free
test drive.
But be SURE that you understand what you are doing before attempting a
restore, or bad things could happen.^

Also consider configuring Windows Update to notify you, but not install,
until you say so.

 

[(PeteCresswell)]

Per dev:

But be SURE that you understand what you are doing before attempting a
restore, or bad things could happen.^

And (I should have said it up front) learn to segregate your system from your
data - keeping the data preferably on a separate drive.. but at least under a
single parent directory.

You will be a *very* unhappy camper after that re-image if it also clobbers all
of your data.

Keeping it all in one place isn't rocket science.. but it does take a little
attention to detail and digging. For instance, you have to diddle the registry
to coerce "Favorites" to your data drive or folder.

 

[Guest]

Here's your fix...you'll need to contact microsoft to get the patch...

http://support.microsoft.com/kb/916089

 

[Nick]

Hi there,

I have had a staff member mention this problem to me also,

the 916089 fix doesn't seem to talk about any error codes 0x745f2780 in the
symptoms portion of http://support.microsoft.com/kb/916089

are you sure this is the correct link?

thanks.

N.