Results 1 to 10 of 10

Thread: Windows XP boot/reboot[KILLED]

  1. #1

    Thread Starter
    So Unbanned DiGiTaIErRoR's Avatar
    Join Date
    Apr 1999
    Location
    /dev/null
    Posts
    4,111

    Windows XP boot/reboot[KILLED]

    I boot XP... it goes to a black screen.. blue screen(background color)... reboots.

    ***.
    Last edited by DiGiTaIErRoR; May 17th, 2004 at 08:30 AM.

  2. #2
    Hyperactive Member CyberSurfer's Avatar
    Join Date
    Aug 2000
    Location
    Old London Town
    Posts
    425
    This happened to my housemate recently, problem was a corrupted FS. Boot to the XP recovery console and run chkdsk a couple of times until no more errors are reported.

  3. #3
    Frenzied Member Ideas Man's Avatar
    Join Date
    Aug 2002
    Location
    Australia
    Posts
    1,718
    Did you do a major hardware change recently? You may have to repair your installation of XP.

    Boot off the CD, Press Enter, F8, R to repair, not the first repair but the second.
    I use Microsoft Visual Basic 2005. (Therefore, most code samples I provide will be based around the .NET Framework v2.0, unless otherwise specified)

  4. #4

    Thread Starter
    So Unbanned DiGiTaIErRoR's Avatar
    Join Date
    Apr 1999
    Location
    /dev/null
    Posts
    4,111
    I took out a floppy drive, because I never use it.

    I'll try the recovery.

  5. #5
    Frenzied Member DeadEyes's Avatar
    Join Date
    Jul 2002
    Posts
    1,196
    Could it be that the boot sequence trys to load from floppy first
    but becuase there is no floppy drive it's messing up.

  6. #6
    Frenzied Member Ideas Man's Avatar
    Join Date
    Aug 2002
    Location
    Australia
    Posts
    1,718
    Nah, he said that he boots XP, gets a blue screen (critical stop, BSOD) and then it reboots. The boot order wouldn't affect it because Windows wouldn't load at all if it did.
    I use Microsoft Visual Basic 2005. (Therefore, most code samples I provide will be based around the .NET Framework v2.0, unless otherwise specified)

  7. #7
    Frenzied Member Ideas Man's Avatar
    Join Date
    Aug 2002
    Location
    Australia
    Posts
    1,718
    Actually try booting into Safe Mode, if you can boot into Safe Mode, then it's something that starts up like a faulty driver or something. If it doesn't boot into safe mode, then do recovery/repair.
    I use Microsoft Visual Basic 2005. (Therefore, most code samples I provide will be based around the .NET Framework v2.0, unless otherwise specified)

  8. #8

    Thread Starter
    So Unbanned DiGiTaIErRoR's Avatar
    Join Date
    Apr 1999
    Location
    /dev/null
    Posts
    4,111
    I don't get a BSOD, it just reboots. I don't have the CD, so I can't recover.

    I'm thinking I'll just kill it.... It's on this machine(has 2K and 98 too). I never liked XP anyway.

  9. #9
    Frenzied Member Ideas Man's Avatar
    Join Date
    Aug 2002
    Location
    Australia
    Posts
    1,718
    The BSOD only appears for an instant, it's very quick. Try the safe mode idea anyway.

    Also, how could you not like XP? I love it, best thing since sliced bread .
    I use Microsoft Visual Basic 2005. (Therefore, most code samples I provide will be based around the .NET Framework v2.0, unless otherwise specified)

  10. #10

    Thread Starter
    So Unbanned DiGiTaIErRoR's Avatar
    Join Date
    Apr 1999
    Location
    /dev/null
    Posts
    4,111
    Originally posted by Ideas Man
    The BSOD only appears for an instant, it's very quick. Try the safe mode idea anyway.

    Also, how could you not like XP? I love it, best thing since sliced bread .
    Safe mode doesn't work.

    The fact that it doesn't boot correctly should be an obvious reason.

    Other than the obvious(?):

    Poor memory(resource) management, I loves my Win2k!
    Specifically when attempting to multi-task. Which, to me, is a requirement!
    General bugginess(yes, vague, I know)

    I use the Advanced Server edition of Windows 2000(no IIS installed though). Perhaps that's why it's so stable and performs excellently. Without any of the superfluous baggage that XP has.

    I'm not trying to sound like XP is all bad. I like the systray being able to hide icons. It seems XP can utilize my CPU better, but not manage memory anywhere near as well as Win2k(when the system is being pushed).

    For example... in XP if I'm rendering then multi-tasking is basically not going to happen(atleast not at an acceptable response time*cough*minutes*cough*). In Windows 2k however, I could be rendering, open Photoshop(while rendering, it's no problem for 2K), chat with a few friends, and be listening to Winamp all the while. And all basically seamlessly(depending on the rendering's memory requirements). Worst case, Win2k will take upto a few seconds to respond(again, I loves my Win2k).

    Yea... I'm a power user though. Most standard users probably wouldn't notice XP's problems.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width