KB891711.EXE

"Galen" wrote in message
...
Curiouser and curiouser... See also this:



Sorry, I couldn't get that link to do anything.

I have to go down into the village to pick up a package from UPS in about
((..omitted..))
there running for a day or two. Will let you know if there's a problem with
it down there.

Should be interesting. Identical machine, two different connections. For that
matter, I *can* dial-up connect the machine I'm on now. I keep the dial-up as a
backup for my broadband, though I've only ever used it to check mail when the
broadband flunks out. I have to leave shortly, but if your results are
interesting, I'll give it a go later tonight.

- Bill

The 891711 issue that causes the reboot isn't related to whether it is
dialup or broadband. It's related to how the system deals with graphics ...
thus, it would seem to be only a processor/video card issue.

"Bill Leary" wrote in message
...
"Galen" wrote in message
...
Curiouser and curiouser... See also this:



Sorry, I couldn't get that link to do anything.

I have to go down into the village to pick up a package from UPS in about
((..omitted..))
there running for a day or two. Will let you know if there's a problem
with
it down there.

Should be interesting. Identical machine, two different connections. For
that
matter, I *can* dial-up connect the machine I'm on now. I keep the
dial-up as a
backup for my broadband, though I've only ever used it to check mail when
the
broadband flunks out. I have to leave shortly, but if your results are
interesting, I'll give it a go later tonight.

- Bill

In ,
Bill Leary had this to say:

My reply is at the bottom of your sent message:

"Galen" wrote in message
...
Curiouser and curiouser... See also this:



Sorry, I couldn't get that link to do anything.

I have to go down into the village to pick up a package from UPS in
about ((..omitted..))
there running for a day or two. Will let you know if there's a
problem with it down there.

Should be interesting. Identical machine, two different connections.
For that matter, I *can* dial-up connect the machine I'm on now. I
keep the dial-up as a backup for my broadband, though I've only ever
used it to check mail when the broadband flunks out. I have to leave
shortly, but if your results are interesting, I'll give it a go later
tonight.

- Bill

Contents of the original post that you couldn't get the link to work for:

Now this may be a false hope but I just ran Microsofts "Regclean" and
haven't
had a freeze-up for several hours. Maybe that update enters something in the
registry which doesn't get removed when uninstalling it via add/remove.
Perhaps others who are more knowledgeable may know?
That sort of figures somehow. If the registry is re-routing things through a
program that doen't exist it would freeze the pc?
Knowing my luck it will be back tomorrow!!!!
Hillneerg

Anyhow, my package came in. I have a laptop sitting down there running as we
speak with my father to call me should it go down (I also have the IP
address and set the firewall to give a response to pings) and it's still up
and running. I got 100 blank DVDs for the low price of $30 which is why I
was going down for the USP package.

These tests, in my case, aren't really THAT accurate once again. These are
simple boxes with little installed on them other than what I consider
required software. Namely a full time AV app and a firewall. Everything else
is not loaded, no Word, Office, or anything like that. No games, no tweaks,
not anything that hasn't been installed other than those two applications, a
reg cleaner that's not running full time, and a quick fix application that
isn't running all the time.

Galen
--
Signature changed for a moment of silence.
Rest well Alex and we'll see you on the other side.

In article , =?Utf-8?B?
SGlsbG5lZXJn?= says...

Now this may be a false hope but I just ran Microsofts "Regclean" and haven't
had a freeze-up for several hours. Maybe that update enters something in the
registry which doesn't get removed when uninstalling it via add/remove.
Perhaps others who are more knowledgeable may know?
That sort of figures somehow. If the registry is re-routing things through a
program that doen't exist it would freeze the pc?
Knowing my luck it will be back tomorrow!!!!

I only found four registry entries; same four on each computer. The one that
works, and the one that crashes.

--
Norman
~Win dain a lotica, En vai tu ri, Si lo ta
~Fin dein a loluca, En dragu a sei lain
~Vi fa-ru les shutai am, En riga-lint

"Justin Thyme" wrote in message
...

"Kevin Moore" wrote in message
...
Ken, have you checked the ScanDefrag logs to see what has
changed and/or notified the programs authors ??



I have followed your suggestion and will advise here if I hear anything
from
the ScanDefrag group.

Thanx,

Ken Bland



I received a prompt reply from the ScanDefrag group. Here is the answer:

There have been numerous problems with that patch, and has been
all over the newsgroups. Hopefully MS will fix it soon, and integrate
it into the kernel instead of loading it as a service. In the meantime
you may not want to use Restrictive mode, or disable the patch
temporarily using msconfig startup (tab), when running ScanDefrag.

Thanks
Bill Blanton

Well done to you Ken, for flagging it to the ScanDefrag group - and an
especial 'well done' to Bill Blanton for responding so promptly.

Mart


"Justin Thyme" wrote in message
...

"Justin Thyme" wrote in message
...

"Kevin Moore" wrote in message
...
Ken, have you checked the ScanDefrag logs to see what has
changed and/or notified the programs authors ??



I have followed your suggestion and will advise here if I hear anything
from
the ScanDefrag group.

Thanx,

Ken Bland



I received a prompt reply from the ScanDefrag group. Here is the answer:

There have been numerous problems with that patch, and has been
all over the newsgroups. Hopefully MS will fix it soon, and integrate
it into the kernel instead of loading it as a service. In the meantime
you may not want to use Restrictive mode, or disable the patch
temporarily using msconfig startup (tab), when running ScanDefrag.

Thanks
Bill Blanton

Ditto, Bill. Thank you.
-------
May I report that I've just heard from Jim Eshelman about the KB891711
problem.
He is unable to offer anything new to our discussion.
His recommendation is to disable or uninstall the update until MS offers a
new fix.
He seems to think the problem is restricted to Win9X machines, but I think
some W2K boxes have been hit, too.
I have no idea yet what the cause may be, despite several earlier promising
suggestions.
--
Jack E. Martinelli 2002-05 MS MVP for Shell/User / DTS
Help us help you: http://www.dts-L.org/goodpost.htm

http://www.microsoft.com/athome/secu...t/default.aspx
In Memorium: Alex Nichol
http://www.microsoft.com/windowsxp/e...ts/nichol.mspx
Your cooperation is very appreciated.
------
"Mart" wrote in message
...
Well done to you Ken, for flagging it to the ScanDefrag group - and an
especial 'well done' to Bill Blanton for responding so promptly.

Mart


"Justin Thyme" wrote in message
...

"Justin Thyme" wrote in message
...

"Kevin Moore" wrote in message
...
Ken, have you checked the ScanDefrag logs to see what has
changed and/or notified the programs authors ??



I have followed your suggestion and will advise here if I hear anything
from
the ScanDefrag group.

Thanx,

Ken Bland



I received a prompt reply from the ScanDefrag group. Here is the
answer:

There have been numerous problems with that patch, and has been
all over the newsgroups. Hopefully MS will fix it soon, and integrate
it into the kernel instead of loading it as a service. In the meantime
you may not want to use Restrictive mode, or disable the patch
temporarily using msconfig startup (tab), when running ScanDefrag.

Thanks
Bill Blanton

My feelings also, nice job.

--
Mart wrote:
Well done to you Ken, for flagging it to the ScanDefrag group - and an
especial 'well done' to Bill Blanton for responding so promptly.

Mart

Jack,

The problem absolutely affects Win2k as well as WinME (see my threads from
last month in the microsoft.public.win2000.windows_update forum). Apparently
everyone was still oblivious to this issue in February, as not one person
responded to any of my threads. In any event ...

Once 891711 has been installed, the problem seems to arise due to a problem
with the hardware and or drivers not being able to process graphics
properly. It appears that 891711 is intercepting some of the graphic data
and "re-handling" it.

Intel systems appear to be nearly, if not completely unaffected by the
problem, which tells me that the patch was most likely tested on Intel
machines only.

Non-Intel hardware appears to be solely or mostly affected by this problem.
In particular, older AMD systems are universally afflicted. I can only
speculate that this has something to do with the way interrupts are handled
at the processor. In any event, further testing on this patch with non-Intel
systems needs to be done.

This is not a software issue, although many deceptive symptoms make it
appear so. Exiting game software, running your cursor over hot-links,
anti-virus activity, changing windows, stacking windows, etc. -- any number
of graphic related events will cause the reboot or "BSOD". In many cases, an
891711-afflicted system will apparently reboot itself for no reason at all.

Hopefully you can send that information "upstairs".


"Jack E Martinelli" wrote in message
...
Ditto, Bill. Thank you.
-------
May I report that I've just heard from Jim Eshelman about the KB891711
problem.
He is unable to offer anything new to our discussion.
His recommendation is to disable or uninstall the update until MS offers a
new fix.
He seems to think the problem is restricted to Win9X machines, but I think
some W2K boxes have been hit, too.
I have no idea yet what the cause may be, despite several earlier
promising
suggestions.
--
Jack E. Martinelli 2002-05 MS MVP for Shell/User / DTS
Help us help you: http://www.dts-L.org/goodpost.htm

http://www.microsoft.com/athome/secu...t/default.aspx
In Memorium: Alex Nichol
http://www.microsoft.com/windowsxp/e...ts/nichol.mspx
Your cooperation is very appreciated.
------
"Mart" wrote in message
...
Well done to you Ken, for flagging it to the ScanDefrag group - and an
especial 'well done' to Bill Blanton for responding so promptly.

Mart


"Justin Thyme" wrote in message
...

"Justin Thyme" wrote in message
...

"Kevin Moore" wrote in message
...
Ken, have you checked the ScanDefrag logs to see what has
changed and/or notified the programs authors ??



I have followed your suggestion and will advise here if I hear
anything
from
the ScanDefrag group.

Thanx,

Ken Bland



I received a prompt reply from the ScanDefrag group. Here is the
answer:

There have been numerous problems with that patch, and has been
all over the newsgroups. Hopefully MS will fix it soon, and integrate
it into the kernel instead of loading it as a service. In the meantime
you may not want to use Restrictive mode, or disable the patch
temporarily using msconfig startup (tab), when running ScanDefrag.

Thanks
Bill Blanton

The issue has nothing to do with ScanDefrag; it is merely one of many
programs that will trigger a reboot due to 891711 on machines that have the
affected hardware.

"Justin Thyme" wrote in message
...

"Justin Thyme" wrote in message
...

"Kevin Moore" wrote in message
...
Ken, have you checked the ScanDefrag logs to see what has
changed and/or notified the programs authors ??



I have followed your suggestion and will advise here if I hear anything
from
the ScanDefrag group.

Thanx,

Ken Bland



I received a prompt reply from the ScanDefrag group. Here is the answer:

There have been numerous problems with that patch, and has been
all over the newsgroups. Hopefully MS will fix it soon, and integrate
it into the kernel instead of loading it as a service. In the meantime
you may not want to use Restrictive mode, or disable the patch
temporarily using msconfig startup (tab), when running ScanDefrag.

Thanks
Bill Blanton