update BSOD

[scooter]

What's up with "Windows Update"?

I run Windows XP pro with service pack 1.

the following updates immediately BSOD upon install:
KB837001, KB826939, KB823741, KB835732 AND KB826942. This
is a real pain because this situation forces me to
download and install every update individually which means
logging on and off and rebooting 40 some times just to
update windows when Micro$ofts "best" crashes
irrecoverably at least once a month on my test system.

I don't attempt to install those updates on my other
systems because it is an unknown issue about what kind of
data corruption the BSOD's might cause.

Can't you guys get anything right????
..

[GG]

Do you think you might have a hardware problem?

"scooter" > wrote in message
...
> What's up with "Windows Update"?
>
> I run Windows XP pro with service pack 1.
>
> the following updates immediately BSOD upon install:
> KB837001, KB826939, KB823741, KB835732 AND KB826942. This
> is a real pain because this situation forces me to
> download and install every update individually which means
> logging on and off and rebooting 40 some times just to
> update windows when Micro$ofts "best" crashes
> irrecoverably at least once a month on my test system.
>
> I don't attempt to install those updates on my other
> systems because it is an unknown issue about what kind of
> data corruption the BSOD's might cause.
>
> Can't you guys get anything right????
> .
>
>

[GG]

Do you think you might have a hardware problem?

"scooter" > wrote in message
...
> What's up with "Windows Update"?
>
> I run Windows XP pro with service pack 1.
>
> the following updates immediately BSOD upon install:
> KB837001, KB826939, KB823741, KB835732 AND KB826942. This
> is a real pain because this situation forces me to
> download and install every update individually which means
> logging on and off and rebooting 40 some times just to
> update windows when Micro$ofts "best" crashes
> irrecoverably at least once a month on my test system.
>
> I don't attempt to install those updates on my other
> systems because it is an unknown issue about what kind of
> data corruption the BSOD's might cause.
>
> Can't you guys get anything right????
> .
>
>

[Chad Harris]

Scooter--

Your BSODs probably *don't have a thing to do with Microsoft getting
something wrong or those updates.* Security sites aren't reflecting your
experience at all. There is a high 70's if not 80% chance a driver or other
hardware problem is the cause of your current blue period. These updates
are the result of trying to correct some vulnerabilities and 3/4 are deemed
critical, but *they* are not causing your BSOD's. To context the BSOD's
you might:

1) Type "eventvwr.msc" (no quotes) in the run box and see what information
you have in the two lists application and system.

2) If you hit the Windows+Pause Break key>System Startup Button>Take Tick
out of "Automatically restart" and google the error messages of those
BSOD's I'll bet you find that they are umbrellas for a gamut of driver or
hardware related problems. If you run down the error messages on those
BSODs, that'll get you moving toward the real problem.

For context on the hotfixes:

MS Warns of a Score of Security Flaws
http://news.com.com/2100-7349_3-5190818.html

For example one of them
http://www.microsoft.com/technet/security/bulletin/ms04-014.mspx covers
this security flaw

http://www.securityspace.com/smysecure/catid.html?id=12207

and interestingly was discovered and a remedy developed for Microsoft by a
19-year old from Aberdeen named Matt Thompson:
http://news.com.com/2100-7349_3-5190818.html

Chad Harris


"scooter" > wrote in message
...
> What's up with "Windows Update"?
>
> I run Windows XP pro with service pack 1.
>
> the following updates immediately BSOD upon install:
> KB837001, KB826939, KB823741, KB835732 AND KB826942. This
> is a real pain because this situation forces me to
> download and install every update individually which means
> logging on and off and rebooting 40 some times just to
> update windows when Micro$ofts "best" crashes
> irrecoverably at least once a month on my test system.
>
> I don't attempt to install those updates on my other
> systems because it is an unknown issue about what kind of
> data corruption the BSOD's might cause.
>
> Can't you guys get anything right????
> .
>
>

[Chad Harris]

Scooter--

Your BSODs probably *don't have a thing to do with Microsoft getting
something wrong or those updates.* Security sites aren't reflecting your
experience at all. There is a high 70's if not 80% chance a driver or other
hardware problem is the cause of your current blue period. These updates
are the result of trying to correct some vulnerabilities and 3/4 are deemed
critical, but *they* are not causing your BSOD's. To context the BSOD's
you might:

1) Type "eventvwr.msc" (no quotes) in the run box and see what information
you have in the two lists application and system.

2) If you hit the Windows+Pause Break key>System Startup Button>Take Tick
out of "Automatically restart" and google the error messages of those
BSOD's I'll bet you find that they are umbrellas for a gamut of driver or
hardware related problems. If you run down the error messages on those
BSODs, that'll get you moving toward the real problem.

For context on the hotfixes:

MS Warns of a Score of Security Flaws
http://news.com.com/2100-7349_3-5190818.html

For example one of them
http://www.microsoft.com/technet/security/bulletin/ms04-014.mspx covers
this security flaw

http://www.securityspace.com/smysecure/catid.html?id=12207

and interestingly was discovered and a remedy developed for Microsoft by a
19-year old from Aberdeen named Matt Thompson:
http://news.com.com/2100-7349_3-5190818.html

Chad Harris


"scooter" > wrote in message
...
> What's up with "Windows Update"?
>
> I run Windows XP pro with service pack 1.
>
> the following updates immediately BSOD upon install:
> KB837001, KB826939, KB823741, KB835732 AND KB826942. This
> is a real pain because this situation forces me to
> download and install every update individually which means
> logging on and off and rebooting 40 some times just to
> update windows when Micro$ofts "best" crashes
> irrecoverably at least once a month on my test system.
>
> I don't attempt to install those updates on my other
> systems because it is an unknown issue about what kind of
> data corruption the BSOD's might cause.
>
> Can't you guys get anything right????
> .
>
>