I've been trying to diagnose a serious and frustrating problem all
weekend.
My Dell Inspiron 9400 Windows XP SP2 crashes out to a BSOD with a stop
error code of 0x0000008E everytime I try to install updates using
Windows Update.
I've had to disable automatic updates to stop it from happening
everytime I boot up.
I tried System restore, Dell diagnostics scans on the hardware,
reducing hardware acceleration, virus scans + more..
It even happens in safe mode if I try to install updates manually
downloaded from the Windows Update site.
I really want to try to repair the OS but Dell don't supply the OS CD
with their machines anymore.
I can't find a single relavent article in the Windows KB for the
particular stop error code caused my Windows Update.
What is going on?!
Please help..
Thanks,
sanc
thanks.
http://www.updatexp.com/stop-messages.html
http://aumha.org/win5/kbestop.htm
http://www.theeldergeek.com/stop_error_messages.htm
If its a driver problem then how can System Restore and Safe Mode fail
to work? I tried restoring to a point many weeks ago and it still
crashes out. it used worked fine then.
This, coupled with a clean diagnostics run of the hardware make no
sense at all.
There were 5 pending Windows Updates. 1 of them DID install
succesfully. I rebooted and tried one of the other 4 and it BSOD'd.
these other 4 updates just don't want to be installed even if I try to
download them from the Windows update site and run them manually. It
just crashes again.
sanc
I suggest posting your question in
news://msnews.microsoft.com/microsoft.public.windowsupdate
to reach those who specialize in such problems.
--
Frank Saunders, MS-MVP OE/WM
Reply in newsgroup
http://www.fjsmjs.com
"They who would give up an essential liberty for temporary security, deserve
neither liberty or security"
I have been googling the net for so many hours now trying to find
someone wiht the same problem. No it seems as I have found one.. but
there is not solution to the problem.
Did you ever find a solution?
Please post it here. I have seen similar problems from a couple of
other news groups but still no solution. Like this one:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windowsupdate&mid=dcb34ca3-fba2-404d-8f59-076aa9608640
I have a Dell Precision M70.
Hope someone comes up with a solution..
Best regards
Flemming Gravesen
Yes, there is another person with same problem in this other group.
This guy had the same blue screen last saturday, exactly the same time
I got it. Windows must have pushed one of the updates then.. look
there:
> >
> > I have been googling the net for so many hours now trying to find
> > someone wiht the same problem. No it seems as I have found one.. but
> > there is not solution to the problem.
> >
> > Did you ever find a solution?
> > Please post it here. I have seen similar problems from a couple of
> > other news groups but still no solution. Like this one:
Hi Guys
A very frustrating problem, I know. I've had quite a few of these over
the years (My day-job is repairing the un-repairable) and it has ALWAYS
come down to RAM - ALWAYS (yes, I repeated ALWAYS).
Save yourself a lot of time and hassle and replace the RAM with NEW
quality RAM.
Lol - I'm not hoping this helps - I know it helps.
Regards
Marcellus
Not true.
Thanks to all!
Pablo, you haven't quoted any of the previous message so we don't know
exactly what the issue is. If you are getting this error when doing a
windows update it's best to post your question to the experts in the windows
update newsgroup.
news://msnews.microsoft.com/microsoft.public.windowsupdate. Before posting
there you might want to scan the posts to see if there is a resolution.
When posting make sure you give all relevant information.
I have also included a link to a list of MS public newsgroups.
http://www.aumha.org/nntp.htm
In the future I would recommend you don't post a new question as a reply to
someone else's thread - called hijacking. It's best if you make a new post
giving all the important background for your situation.
By the way your English was quite understandable - much better than my
Spanish.
--
Rock [ MVP User/Shell]
/Flemming
sanctifyer skrev:
I am a PC Tech up in Nova Scotia, Canada and I have 3 different
systems, all exhibiting the EXACT SAME PROBLEM.
Yes.... we have exhausted the usual suspects for a Stop 0x8e error,
with no resolution. I have this occuring on a Dell, IBM and an A-open
clone.... ALL HARDWARE tests out fine on all three..... but they DO
share one common problem that I have not see mentioned by anyone
else..... Has anyone else been nailed by that latest virus circulating
through Windows Messenger????? The one with something like "is this
you in this picture....."???
All three systems that I have this problem with, ALL had been nailed by
this virus. All were working properly, and had no issues with Windows
Update prior to being infected...... so to me, it's gotta be a registry
entry of some form that has been changed.
I am doubting it has to do with the Windows Installer, as SOME updates
will install (when done manually, so the offending updates do not try
to install).
Other weird things I have noticed...
On at least 1 system (the A-open clone), the last updates that appear
in Add/Remove were dated 11/27/2006 and 11/13/2006. Pretty good
considering today's date is 10/23/2006. (Tried uninstalling and
re-installing the updates manually. Some installed properly, some
caused a Stop 0x8E)
NOTE: Before someone makes the comment that their date MAY have been
set wrong when they were installed the first time, remember.... Windows
Updater will not work when the clock is not set correctly, and no, the
date was not incorrectly sent anyway.
I have thrown everything I can think of at these machines. They all
work with no issues as long as the Automatic Updates and Automatic
Updates Scheduler are disabled, but I cannot find anything more.
I am really hoping we can come up with a resolution for this as 2 of
the systems are business machines, which would be a HUGE deal to have
to wipe and reload.
Hope this helps.......
Also note:
The Windows Updates that are causing these systems to reboot are as
follows:
KB922819
KB919007
KB925486
KB923414
I have successfully installed the following updates manually:
KB923191
KB920685
KB924191
KB924496
Any assistance with resolving this would be GREATLY APPRICIATED!!!!
Troy
Hi - I'm a PC tech in the UK. I have a client PC (Dell Dimension 4600)
that was hit by the virus (the client said "it had a photo for me to
look at, and it's not worked right since"). There were no BSODs before
finally removing the virus, but now I get the 0x0000008E about 60
seconds after booting, every time.
It does not BSOD in safe mode. I've updated the Nvidia drivers, BIOS,
swpped in RAM etc. and still no fix. The first BSOD was Saturday, when
I removed the virus and all its little friends and attempted an MS
update - that first BSOD was right in the middle of the update.
I've also tried restoring SP2 from disk, but no luck.
-- Jason
The closest MS has come to a solution is to update the video drivers. I
downloaded the Intel drivers and it said "not allowed to update this
machine". I downloaded from Dell, but the driver was >6mths old. I
re-downloaded from Intel and recovered the unzipped files from the Temp
directory while it was giving me the "not allowed" message, and I
managed to get the latest video driver on but the crash kept happening.
You've got to admire this Dell / MS / Intel ring of obscurity.
I've uninstalled half the software and all the peripheral h/w. No joy
Eventually, I stopped it crashing by disabling auto updates (suspending
the thread with SysInternal's process explorer).
Anyone come up with an answer yet? MS is still telling me the video
driver's duff even though the page I am auto-redirected to specifies
the wrong error-type.
Pete
I've had my system board replaced by Dell and its still there.
sanc
This is one of those crashes that will have a hotfix in a few months, you
wait and see. It'll start affecting tons of people and MS will finally wake
up. Of course that doesn't do us any good, but I'm still working on this one
for a customer so if I find an answer I'll post it here.
I have got this problem, that has occured after a virus attack! I have
cleaned what i can, run all sorts of removal tools, and reinstalled windows
over the current version. However, the problem still exists, and i can only
assume that the registry is still infected. I have searched everywhere for a
solution but to no avail. any help would be greatly appreciated.
sanc
If it's a malware infection and you can't sort it out, then do a clean
install.