XP crash on startup

  • Thread starter Thread starter Jerry
  • Start date Start date
J

Jerry

I've seen two instances of the following problem on
customers' machines. Any ideas?

Shortly after the XP logo shows on startup, a bluescreen
stop code flashes so quickly that you can't read it and
the process starts over. Same thing in safe mode and last
known good config. Could not get into either system to
change post-crash behavior, since neither had an ERD and
both had unknown recovery console admin passwords
configured, so I couldn't get in to RC by booting from
the CD. In both cases, the customers saw countdown
messages before the problem began, indicating Blaster
worm, but I've cleaned Blaster off many XP workstations
that were otherwise unharmed. Does it crater some systems?

Booting from the CD and choosing the repair option
changed the failure - it didn't crash, but got hung with
a black screen and nothing but the mouse pointer. An in-
place reinstall was required to recover the system, but I
would rather find a less onerous fix. Has anyone seen
this, and if so, can you at least tell me what the stop
code or fix was?

Thanks.
 
Jerry,

I've got the same problem and as you can see lots of new
reports coming up on this newsgroup. I only have an OEM
XP disk, and the only option I get is the "reset to day 1"
option. We you able to get to where you only have to do a
partial install?

If I borrow a friend's "real" XP disk set, can I boot up
windows from there? Was hoping that if I could boot into
windows from a CD, that Norton's might actually do
something. Right now, I can only get to DOS (old 98
floppy) and the Norton doesn't do anything with my NTFS
drive. FYI, the NTFS reader on www.ntfs.com shows that
most files are still on the disk.

Ideas appreciated.
 
read this:
WARNING: Bug in patch Q811493 and rollup KB826939

Hi Microsoft Guys, it does not help at all, to rename a
bugy Patch (Q811493) or to include this bugy patch in to
a rollup with different name (Rollup KB826939).

Attention all XP-Pro Users!!

After installation of the Patch Q811493 or the Rollup
KB826939, you may experience the following errors: -
the computer can be started only in save modus
- the JAVA support not more available
- XP desktop design not available
- System crashes similar to the blaster crashes.

The kind of error depends on, how the patch (rollup) has
been installed. If as a bulk with other patches, you are
in real trouble and new XP Installation may be required,
otherwise just deinstall the buggy patch and your system
is OK.


P.S: for any contact use a form at www.psaweb.net
 
I tried to do the low-impact reinstall by selecting
the "repair" option after booting from the CD, but it
didn't recover either system. That is the only low-impact
way of reinstalling XP that I know of. If you do an in-
place reinstall into the same directory, unlike Win9x, it
loses track of the installed applications and user
accounts.

When you boot from an XP CD, it launches XP setup, and
you then have 3 choices: enter Recovery Console, run
Repair or Install XP.

Recovery Console is a command line interface that allows
you do a limited set of things and it is best not to mess
with it unless you really know what you are doing. There
is a good chance I could fix my problem from RC if I knew
what the stop code was, I could try other less
destructive things, but unfortunately, Microsoft chose
the wrong default for XP crash recovery (restart, instead
of halt).

Repair tries to replace missing or damaged files, but it
hasn't worked very well in my experience.

Install will let you do a side-by-side install into a new
directory, and I have fixed a few systems in this way,
where the boot volume became unmountable. It only has a
chance of working if the problem area is common to
multiple installations on the same hard drive partition.
Install will also let you install over the top of the XP
directory that had been working, but this is pretty close
to doing a system restore, the difference being that it
doesn't wipe out all of your documents and data, in spite
of its warnings that it will do so. Strangely, it does
seem to crater some of the data. Before doing this type
of install, I pull the hard drive out and slave it into
another machine so I can copy the data off and restore it
later.

Regarding Norton, I have been bugging them for some time
to come up with a solution for scanning NTFS drives after
booting from their CD. I tried the free (read only)
version of NTFSDos to boot from a floppy and then scan
from the CD, but Norton requires so much conventional
memory that there isn't enough left to run it after
loading NTFSDos and the real mode CD drivers. NAV 2004
just came out, but we don't have it in the shop yet, so I
don't know if they have addressed this issue. I haven't
tried running Norton from the CD after booting into
Recovery Console.

Jerry
 
Back
Top