Vista - Vista Blue Screen after Microsoft auto updates 2Sept

I let Vista do two updates on my Tosh A300-1BZ Laptop - I think 1 was an IE8
compatibility update, the second a windows defender patch and the third
(enabled in error) was a "windows live essentials" update which I cancelled
half way through (by hitting Cancel and then Yes etc).

The updater reported two updated done one cancelled and requested a reboot.

After re-boot all I get after the initial Microsoft "bar graph" loading icon
is a blue screen and "STOP: c0000139 (Entry Point Not Found) The procedure
entry point ntoskrnl.Ex1AcquireFastMutex could not be located in the dynamic
link library HAL.dll."

I've tried using repair windows using F8 and from a Vista Ultimate DVD
(which reports no errors) and using system restore to a previous point which
reports success but on re-boot the laptop still blue screens with the same
report.

Of course Tosh just say restore your Laptop to its original state - they
would wouldn't they!

HELP please:-(
Thanks in anticipation - Peter

Can you boot into Safe Mode? Have you tried the Boot Repair option when
booting from the DVD?

SC Tom

"webworks" <webworks@xxxxxx> wrote in message
news:EF0AE9D1-F863-440F-85D8-35C0E45AD9C5@xxxxxx

Hi Tom,
Thanks for the reply - running through the sequences again my blue screen
has now gone (I can't get that far!)

Booting from a borrowed genuine Vista Ultimate inc SP1 DVD I get to the
"Install Now" screen and choose the Repair option.

System Recovery then finds my Vista Installation and I get the System
Recovery Options screen. I've tried Startup Repair - which initially reports
"Startup Repair could not detect a problem." and in the details "Boot status
indicates that OS booted successfully". HOWEVER, when I reboot Startup Repair
then kicks in again and reports "Windows cannot repair this computer
automatically" and in the details " Number of repair attempts 23 and Startup
Repair has tried several times but cannot find the cause of thie problem"
(though all test results show "completed Successfully. Error code = 0x0)

I've also tried System Restore (which reports success but still doesn't get
me to a good boot).

PS: No, I can't boot into safe mode. Choosing F8 then Safe mode on start up
from HD now takes me into System Recovery and the same old "cannot
automatically repair"

Of course I've run the memory diagnostics (all OK).

All this from a Microsoft Update to a perfect machine that has never blue
screened before in 1 yr of ownership:-(

PS: Just tried a system restore again and that took me back (or so it said)
do 1 day before the crash. NOW I HAVE THE BLUE SCREEN CRASH AGAIN;-)

"webworks" <webworks@xxxxxx> wrote in message
news:80127F84-8C25-405D-A1CB-E867E44E2C73@xxxxxxI don't really think it was the update, but more likely the canceling of the
update during install. Most OS's aren't real happy with that.
Unfortunately, I don't how to get around that unless you have a viable
back-up of your hard drive. Looks like a Toshiba restore is in your near
future unless someone else has an idea or two. Unfortunately Vista doesn't
have the in-place upgrade option like XP and previous versions did. In
Vista, you have to be able to get into Windows to start it. Well, duh! If
it's working, it doesn't need fixing.

SC Tom

Hi Tom,

Yes I'm beginning to think I may be heading for a restore. I won't lose much
data as that is backed up - it's just the pain of all those personal configs,
downloaded apps and widgets as the machine gets used for my business and my
hobby - ham radio.

I get really Pi$$ed that we pay top whack for genuine software and get ZERO
support unless we pay some more. If updater had said "this process cannot be
cancelled" then I wouldn't have cancelled it!!! The fact that I can't even
roll back or as you say re-install Vista without losing everything is just
plain dumb.

Not having a good day (week!) Peter

Hi, Peter.

To slightly ease the pain of reinstalling, can you run Windows Easy
Transfer? Run it before you re-install, saying "this is the old computer"
and aim at a data partition (which won't get reformatted) on your hard
drive, or to a USB flash drive or whatever storage device you have
available. Then, after the reinstallation, run WET again from the "new
computer". This won't make the transition completely painless, but it can
help a lot.

RC
--
R. C. White, CPA
San Marcos, TX
rc@xxxxxx
Microsoft Windows MVP
Windows Live Mail 2009 (14.0.8089.0726) in Win7 Ultimate x64

"webworks" <webworks@xxxxxx> wrote in message
news:ACDE561C-B144-408D-A806-A43B59730420@xxxxxx

Doesn't Windows have to be working for WET to run, or am I mistaken? I was
under the assumption that it only worked with two different PC's, both
running Windows, albeit different versions.
http://support.microsoft.com/kb/928635/en-us
http://support.microsoft.com/kb/928634/

SC Tom

"R. C. White" <rc@xxxxxx> wrote in message
news:O33EqLLLKHA.5732@xxxxxx

Hi, Tom.
Well, that's the reason for having WET. But it can be used in unintended
ways.

I used it recently to migrate my tweaks and settings from Win7 RC to Win7
RTM on my one and only computer. I've been dual-booting for years, so I
just created my new volume (Drive C and installed Win7 RTM there. Then I
rebooted into Win7 RC on Drive X:, which I had not (and still have not)
deleted. In Win7 RC on X:, I ran WET and had it store its output onto Drive
C: - since I had already installed RTM and wouldn't be reformatting that
volume again. Then I rebooted into RTM on Drive C: and ran WET to transfer
settings from the *.MIG file into wherever they belong in RTM, mostly into
the C:\Users\RC folder tree.

And I did preface my suggestion with, "...can you run Windows Easy
Transfer?", since I was not sure just how far Peter could get in the boot
process. He said he had managed to System Restore to a day before the
crash, so he evidently does have SOME control of the computer and just might
be able to run WET.

RC
--
R. C. White, CPA
San Marcos, TX
rc@xxxxxx
Microsoft Windows MVP
Windows Live Mail 2009 (14.0.8089.0726) in Win7 Ultimate x64

"SC Tom" <sc@xxxxxx> wrote in message
news:uaoHhgNLKHA.5068@xxxxxx

I stand corrected.
I don't know how he's running SR since he can't even get into Safe Mode.
Maybe booting from the Vista DVD? Anyhow, he said all he got from it is the
original BSOD.

SC Tom

"R. C. White" <rc@xxxxxx> wrote in message
news:O5n2eTOLKHA.5068@xxxxxx