Serious Windows 2000 Update issues!

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

FYI

I have come across a serious issue with recent Windows 2000 Updates.

Details:

Tested on PIII and P4 platforms (using different motherboard mfg.), video,
NIC and Audio onboard, no additional devices or cards.

I started with systems that had been updated with SP4 and were current on
updates as recent as 30 days ago. I also rebuilt these systems and started
with SP4 (no other software or updates) and then ran Updates - Same results.

One of the updates released in the past 30 days apparently breaks 2000 such
that it continually reboots (without generating any errors). It gets as far
as the blue screen just prior to the login prompt and then suddenly goes back
to BIOS and restarts the process.

I am able to get into Safe Mode and will try to isolate the actual update(s)
in question over the next week.

Regardless of hardware, and software installed, the issues is constant and
easily reproducible.

Thanks,

Danny
 
Check the event log for the stop error.

http://msdn.microsoft.com/library/d..._f55acfed-3296-4e84-8885-c3162fd0ddbf.xml.asp

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| FYI
|
| I have come across a serious issue with recent Windows 2000 Updates.
|
| Details:
|
| Tested on PIII and P4 platforms (using different motherboard mfg.), video,
| NIC and Audio onboard, no additional devices or cards.
|
| I started with systems that had been updated with SP4 and were current on
| updates as recent as 30 days ago. I also rebuilt these systems and
started
| with SP4 (no other software or updates) and then ran Updates - Same
results.
|
| One of the updates released in the past 30 days apparently breaks 2000
such
| that it continually reboots (without generating any errors). It gets as
far
| as the blue screen just prior to the login prompt and then suddenly goes
back
| to BIOS and restarts the process.
|
| I am able to get into Safe Mode and will try to isolate the actual
update(s)
| in question over the next week.
|
| Regardless of hardware, and software installed, the issues is constant and
| easily reproducible.
|
| Thanks,
|
| Danny
 
Dump screen was all but worthless - when I was able to get one.

Only thing was 0X00000..... and a comment that was so vague it served
absolutely no purpose other than to say look at the dump logs...

I've been up and down at this, and the fact that two completely different
platforms had the exact same errors and symptoms leaves me thinking MS
probably made another bobo - Like NT4 SP2 (where the SCSI drivers only
supported a small handful of disks and controllers).

Unless Microsoft want's to pay my consulting fees ($125/Hr.), this will have
to take a back burner.

If and when I have time, I'll investigate and report in detail. For now, I
have a work around - Install XP upgrade over the top; and you lose little, if
anything.

Problem solved - At a price ($99 for one customer and $199 for another -
cost of XP Home and Pro upgrades).

Thanks,

Danny
 
Yes, 0X00000..... is quite worthless. Probably a hardware/driver
incompatibility issue.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Dump screen was all but worthless - when I was able to get one.
|
| Only thing was 0X00000..... and a comment that was so vague it served
| absolutely no purpose other than to say look at the dump logs...
|
| I've been up and down at this, and the fact that two completely different
| platforms had the exact same errors and symptoms leaves me thinking MS
| probably made another bobo - Like NT4 SP2 (where the SCSI drivers only
| supported a small handful of disks and controllers).
|
| Unless Microsoft want's to pay my consulting fees ($125/Hr.), this will
have
| to take a back burner.
|
| If and when I have time, I'll investigate and report in detail. For now,
I
| have a work around - Install XP upgrade over the top; and you lose little,
if
| anything.
|
| Problem solved - At a price ($99 for one customer and $199 for another -
| cost of XP Home and Pro upgrades).
|
| Thanks,
|
| Danny
 
I don't agree.

If it was simply a driver problem, the issue would have shown up some time
ago. Only after recent updates did the problem appear.

I NEVER do hardware updates from Microsoft - MS Hardware drivers are less
reliable (my opinion) than those from original H/W manufacturer, and one
should only use OEM drivers in my opinion.

The problem is impacting the kernel in a manner that causes a reboot so
transparent it leaves no log trail.

As I said, it only happens after installing Microsoft updates released in
the past 30 to 60 days. No other updates or drivers cause the problem to
appear - I tested for that.

Thanks,

Danny
 
Since 'safe mode' works I'd look at the applications that run at startup and
any services/ drivers beyond basics required to start the OS.

Microsoft doesn't do driver development. They get them from the hardware
manufacturer's. The harm comes from the potential of mis-reading the actual
hardware and or installing drivers that the firmware doesn't currently
support.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
|I don't agree.
|
| If it was simply a driver problem, the issue would have shown up some time
| ago. Only after recent updates did the problem appear.
|
| I NEVER do hardware updates from Microsoft - MS Hardware drivers are less
| reliable (my opinion) than those from original H/W manufacturer, and one
| should only use OEM drivers in my opinion.
|
| The problem is impacting the kernel in a manner that causes a reboot so
| transparent it leaves no log trail.
|
| As I said, it only happens after installing Microsoft updates released in
| the past 30 to 60 days. No other updates or drivers cause the problem to
| appear - I tested for that.
|
| Thanks,
|
| Danny
 
Back
Top