You really need to give us some more information if we are to help...

First off, what is the stop code? Without that, we might as well blame
sunspots for the BSOD. What kind of system? What other roles does the
server hold? What was your friend's stop code?

And let's get some more clarification on what you mean by "2k3 SP1 PDC."
Win2k3 (and Win2k) domain controllers all have read-write AD databases that
are synchronized-- there is no such thing as a "PDC" in Win2k3. There is,
of course, the "PDC Emulator" role that a DC can assume for legacy client
support, but that's a different issue. Are you saying that only DC's that
serve the "PDC Emulator" role are affected? Has this been verified using
ntdsutil? Have you tried to restore the last known good config? Any luck
with Safe mode? Did it ever properly load after the patches were applied?
How did you apply the patches?

There are lots of people on this list that are willing to help, but we need
something to work with.

t

----- Original Message -----
From: "Hamid . K" <elite_netbios (at) yahoo (dot) com [email concealed]>
To: <focus-ms (at) securityfocus (dot) com [email concealed]>
Sent: Friday, August 19, 2005 10:24 PM
Subject: New MS patches crashed my 2k3 SP1 PDC

> Hi list ,
>
> After deploying new set of microsoft patches released
> this months , we experienced a heavy crash on out
> domain controller systems which are based on windows
> 2003 SP1 !
> just after a clean install of last 5 patches ,
> windows will no more boot ! nice blue screen of death
> is what MS dedicated to us !
> another friend of mine , in his own network
> experienced the same . cool point is that _ONLY_ PDC
> systems are affected to this unexpected crash . no
> other 2k3 SP1 server had any problem with patches .
>
> anyone else have had same problem ?
> what the hell is going wrong ?
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - Find what you need with new enhanced search.
> http://info.mail.yahoo.com/mail_250
>
> ------------------------------------------------------------------------
---
> ------------------------------------------------------------------------
---
>
>
>

------------------------------------------------------------------------
---
------------------------------------------------------------------------
---

[ reply ]