J
Jim Graham
I work at a University, and we have incorporated Windows
XP SP2 into an update CD for students to use. I would say
that 10% of all XP Home machines (and a few Pro) have had
the blue screen with the STOP c0000135 WINSRV problem on
boot that many people have been reporting in these
forums. This has to be a problem with SP2. Please do not
post links to KB article 173309, as this DOES NOT APPLY.
Also please do not post links to KB article 875350, as
the steps contained therein cannot be performed. Also,
copying winsrv.dll from XP Gold, SP1, and a working SP2
does not work. I believe that these issues point to a
corrupt registry hive, but why so many computers? I'm
working on profiling these machines to dertermine if they
have something in common, like a chipset, processor, or
brand... If everyone that has this problem could post
their system specs, I believe that would help us out a
lot...
XP SP2 into an update CD for students to use. I would say
that 10% of all XP Home machines (and a few Pro) have had
the blue screen with the STOP c0000135 WINSRV problem on
boot that many people have been reporting in these
forums. This has to be a problem with SP2. Please do not
post links to KB article 173309, as this DOES NOT APPLY.
Also please do not post links to KB article 875350, as
the steps contained therein cannot be performed. Also,
copying winsrv.dll from XP Gold, SP1, and a working SP2
does not work. I believe that these issues point to a
corrupt registry hive, but why so many computers? I'm
working on profiling these machines to dertermine if they
have something in common, like a chipset, processor, or
brand... If everyone that has this problem could post
their system specs, I believe that would help us out a
lot...