Archived from groups: microsoft.public.windowsxp.hardware (More info?)
Well, I've been working for some time on trying to get my
computer in a proper working condition. Unfortunately, all
my attempts have failed and now Windows does along with
them. For those of you who haven't pieced together my
multiple threads about my process now get to hear my
story. My computer consists of an AMD Athlon XP 2000+.
However, when I started my computer for the first time and
tried to install Windows it took approximately 38 hours.
Now, unless Windows' estimated time algorithm is out of
wack, or my computer was having some hardware problems.
Now unfortunately, I decided to change my BIOS settings to
comply with some of those wonderful STOP errors. This
caused my computer to lock up and not boot. I went to my
motherboard and used the jumper to reset the CMOS. This
set my FSB to 100 MHz, which was the default for the BIOS,
which made my processor go from a XP 2000+ to an AMD 1250.
I had posted a help message on this forum in order to find
out why my computer would not run properly when my FSB was
at 133 MHz, but it would at 100MHz. I talked to a friend
about my problem and he suggested that I step the FSB by
small increments until I could not get Windows to boot.
This would still allow me to get the most power out of my
processor as possible, while not causing the system to
crash continuously. I got to 110 MHz before Windows could
no longer boot. So I reset my clock back to 100 MHz, and
to my suprise, Windows refuses to boot, even in safe mode.
It restarts as soon as it finishes loading Mup.sys.
Normally, it shows my boot screen, flashes a stop error
for about 1/10 of a second, and then reboots.
I let a friend borrow my CD in order to repair his
installation, but unfortunately, he lost it on me. So now
I'm stuck without a Windows XP CD. So I borrowed my
brother's, and when I try to enter the recovery console,
it detects my HD as being 244 MB when it is 80 GB. It
attempts to examine the "Startup Environment" but halts at
that point.
So here's where I have some questions. First, how can I
get Windows to boot properly? I doubt that it is going to
be impossible to recover the Stop error code, because the
screen passes by too fast to catch. I believe it also
restarts before the graphics card can finish drawing the
screen. Secondly, how could I get Windows to work properly
with a FSB of 133 MHz? Thirdly, why didn't Microsoft put a
timer into the Stop screen so that people could actually
have time to read it?
Answers to any of these questions would be greatly
appreciated.
Evan
Well, I've been working for some time on trying to get my
computer in a proper working condition. Unfortunately, all
my attempts have failed and now Windows does along with
them. For those of you who haven't pieced together my
multiple threads about my process now get to hear my
story. My computer consists of an AMD Athlon XP 2000+.
However, when I started my computer for the first time and
tried to install Windows it took approximately 38 hours.
Now, unless Windows' estimated time algorithm is out of
wack, or my computer was having some hardware problems.
Now unfortunately, I decided to change my BIOS settings to
comply with some of those wonderful STOP errors. This
caused my computer to lock up and not boot. I went to my
motherboard and used the jumper to reset the CMOS. This
set my FSB to 100 MHz, which was the default for the BIOS,
which made my processor go from a XP 2000+ to an AMD 1250.
I had posted a help message on this forum in order to find
out why my computer would not run properly when my FSB was
at 133 MHz, but it would at 100MHz. I talked to a friend
about my problem and he suggested that I step the FSB by
small increments until I could not get Windows to boot.
This would still allow me to get the most power out of my
processor as possible, while not causing the system to
crash continuously. I got to 110 MHz before Windows could
no longer boot. So I reset my clock back to 100 MHz, and
to my suprise, Windows refuses to boot, even in safe mode.
It restarts as soon as it finishes loading Mup.sys.
Normally, it shows my boot screen, flashes a stop error
for about 1/10 of a second, and then reboots.
I let a friend borrow my CD in order to repair his
installation, but unfortunately, he lost it on me. So now
I'm stuck without a Windows XP CD. So I borrowed my
brother's, and when I try to enter the recovery console,
it detects my HD as being 244 MB when it is 80 GB. It
attempts to examine the "Startup Environment" but halts at
that point.
So here's where I have some questions. First, how can I
get Windows to boot properly? I doubt that it is going to
be impossible to recover the Stop error code, because the
screen passes by too fast to catch. I believe it also
restarts before the graphics card can finish drawing the
screen. Secondly, how could I get Windows to work properly
with a FSB of 133 MHz? Thirdly, why didn't Microsoft put a
timer into the Stop screen so that people could actually
have time to read it?
Answers to any of these questions would be greatly
appreciated.
Evan
Facebook
Twitter
Instagram