Re: WinXP doesn't start

From: WinGuy (no_spam_at_nomail.bot)
Date: 12/27/04


Date: Mon, 27 Dec 2004 16:06:39 GMT


"Rob" <Rob@discussions.microsoft.com> wrote in message
news:5E175C88-615A-4712-B4A0-138F3C0D1EB6@microsoft.com...
> My computer stopped booting properly. I get the following error message
> when
> I try booting from a CD. Booting from HD results in continuous reboots:
>
> A problem has been detected and windows has been shut down to prevent
> damage
> to your computer.
>
> If this is the first time you've seen this stop error screen, restart your
> computer. If this screen appears again, follow these steps:
>
> Check to be sure you have adequate disk space. If a drier is identified in
> the stop message, disable the driver or check with the manufacturer for
> driver updates. Try changing video adapters.
>
> Check with your hardware vendor for any BIOS updates. Disable BIOS memory
> options such as caching or shadowing. If you need to use safe mode to
> remove
> or disable components, restart your computer, press F8 to select Advanced
> Startup options, and then select safe mode.
>
> Technical Information:
>
> *** stop: 0x0000007e (0xc0000005,0x784bffaa,0xf8989460,0xf8989160)
>
> Symptons:
> - Computer gives choice to boot in safe mode, normal, etc....
> - When normal boot is chosen it starts boot process then reboots.
> - When safe mode is chosen it starts loading drivers and then reboots. The
> last driver I see being loaded looks like it says "agp40.sys" or something
> real similar.
> - When I try booting with Win install CD I get the above error.
> - When I try booting with a BartPE boot disc I get the above error.
>
> Computer Specs:
> - P4 1.4Ghz
> - Abit BW7 Motherboard
> - 512 Mb PC 133
> - Western Digital 120GB HD
> - Sony CD burner
> - Creative CD drive
> - 3.5 Floppy drive
> - GeForce FX5200 video card
> - Windows XP Pro w/SP2
> - Norton AV and Firewall
>
> I have done the following to troubleshoot:
>
> 1. Removed all cards except video, disconnected secondary IDE cable,
> replaced HD with known good drive and replaced memory with known good
> DIMM. -
> No change on boot
>
> 2. Replaced AGP video adapter with another AGP adapter. - No change on
> boot.
>
> 3. Replaced AGP video adapter with a PCI video adapter. - No change on
> boot.
>
> 4. Changed Keyboard. - No change on boot.
>
> 5. Disconnected Logitech trackball. - No change on boot.
>
> 6. Loaded failsafe setting in BIOS - No change on boot.
>
> Is there anything else I should look at? At this point the only thing I
> can
> think of is a motherboard problem
>
> Thanks

Can you, by any chance, use the VGA option to boot into safe mode? That's
only 256 colors and 640x480, but it might rule out a bad graphics driver
(especially if you try it again with a known good PCI graphics card, check
BIOS in case it can have AGP slot disabled manually).

Can you boot from the CD to the Recovery Console and take a look at the
C:\%windir%\ntbtlog.txt file for some hints? A problem driver might show up
within the last 3 lines. I doubt this is it, but you could try disconnecting
all IDE devices (including Drive A if you have one, this might require
telling BIOS you have no Drive A for the system to try to boot) except for C
and replacing or swapping its flat ribbon cable, a failing device might be
interferring electrically with the controller chip on the motherboard.
Although you replaced RAM, you might try making a bootable memory test
floppy from http://www.memtest.org/ since it can be run without booting
Windows. If it runs ok with known good memory then it's probably a device or
a driver instead something on the motherboard.

Can you boot to an old Windows 98 or ME floppy? It's won't recognize a NTFS
formatted drive (so don't bother trying to access drive C), but you just
want to know if you can boot in a minimal operating system environment. If
you can boot that way and do things without getting an error then do you
have another HDD around that you could try installing some sort of operating
system to? That could rule out a failing or damaged HDD.

Winguy



Relevant Pages

  • Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
    ... >>>I'm starting to suspect bad hardware. ... > All I changed was adding nosmp to the kernel boot line. ... >>it's where I think you should try the new driver. ... I did not try booting it with nosmp. ...
    (Linux-Kernel)
  • boot/startup help
    ... A couple days ago it was booting and I could get into the shell over ... I'm completely new to os9, but a very experienced unix guy. ... I booted it via bootp and end up at the same ... with it set to 7 it autoboots following the boot order (scsi ...
    (comp.os.os9)
  • Re: boot/startup help
    ... A couple days ago it was booting and I could get into the shell over ... at the other end of the mvme serial console line where I'm running ... I booted it via bootp and end up at the same ... full disk boot log -- this is with the front panel hex dial set to ...
    (comp.os.os9)
  • WinXP doesnt start
    ... My computer stopped booting properly. ... - When normal boot is chosen it starts boot process then reboots. ... Replaced AGP video adapter with another AGP adapter. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Compatibility question: OSX with classic
    ... OS9 and somewhere along the line it stopped booting in 9 all ... it won't boot OS 9. ... Some CPU upgrades need a firmware update to allow OS 9 booting. ... at the documentation for the upgrade. ...
    (comp.sys.mac.system)