"Windows could not start because of the following ..." ASUS A7S333Motherboard

[W. Watson]

The message in the subject line continues as "file is missing or corrupt:
\winnt\system32\config\system. You can attempt to repair ...". This happens to my XP
Pro system during bootup when I try to change my cpu speed from 1.1GHz to 1.5GHa. The
ASUS A7S3333 motherboard is capable of 1.7GHz. How do I correct this? I've done a
search of ""Windows could not start because" in Google and have gotten a number of
hits. None really reveals a solution, first message in a thread--can't go further, or
seems to apply in my situation.
--
Wayne T. Watson (Watson Adventures, Prop., Nevada City, CA)
(121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
Obz Site: 39° 15' 7" N, 121° 2' 32" W, 2700 feet
(Formerly Homo habilis, erectus, heidelbergensis and now sapiens)

Sign in Programming Department: Mistakes made while you wait.

Web Page: <home.earthlink.net/~mtnviews>

 

[Malke]

The message in the subject line continues as "file is missing or
corrupt: \winnt\system32\config\system. You can attempt to repair
...". This happens to my XP Pro system during bootup when I try to
change my cpu speed from 1.1GHz to 1.5GHa. The ASUS A7S3333
motherboard is capable of 1.7GHz. How do I correct this? I've done a
search of ""Windows could not start because" in Google and have gotten
a number of hits. None really reveals a solution, first message in a
thread--can't go further, or seems to apply in my situation.

Since we don't know what you've looked at, I can't address the searches
you've done. However, just because a motherboard is capable of
supporting a faster processor doesn't mean your particular processor
can be overclocked like that. What processor do you actually have?

Malke

 

[W. Watson]

W. Watson wrote:




Since we don't know what you've looked at, I can't address the searches
you've done. However, just because a motherboard is capable of
supporting a faster processor doesn't mean your particular processor
can be overclocked like that. What processor do you actually have?

Malke

AMD Athlon XP 1700+, ASUS Socket A 462.

Amazingly, I was able to talk with ASUS this morning and got some help on this. I say
amazingly because it's rare to actually talk with a human in tech support. I'm
downloading some chipset files for IDE and AGP that they think may fix the problem. I
hope.

I'm not sure where I got the idea the board would support 1.7G, but according to
ASUS, the 'limit' is 1.5GHz. I used Everest to detail my system, and it says I have
the above AMD cpu, but, in talking with ASUS, I get the impression it's really not
1700. Everest also reports in another place that its a AMD Athlon XP, 1100. That
seems like a report on what it's actually running as right now.

In any case, I still downloading the chipset updates. Perhaps I'll have good luck in
another hour.
--
Wayne T. Watson (Watson Adventures, Prop., Nevada City, CA)
(121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
Obz Site: 39° 15' 7" N, 121° 2' 32" W, 2700 feet
(Formerly Homo habilis, erectus, heidelbergensis and now sapiens)

Sign in Programming Department: Mistakes made while you wait.

Web Page: <home.earthlink.net/~mtnviews>

 

[Malke]

AMD Athlon XP 1700+, ASUS Socket A 462.

Amazingly, I was able to talk with ASUS this morning and got some help
on this. I say amazingly because it's rare to actually talk with a
human in tech support. I'm downloading some chipset files for IDE and
AGP that they think may fix the problem. I hope.

I'm not sure where I got the idea the board would support 1.7G, but
according to ASUS, the 'limit' is 1.5GHz. I used Everest to detail my
system, and it says I have the above AMD cpu, but, in talking with
ASUS, I get the impression it's really not 1700. Everest also reports
in another place that its a AMD Athlon XP, 1100. That seems like a
report on what it's actually running as right now.

In any case, I still downloading the chipset updates. Perhaps I'll
have good luck in another hour.

Good. I'm glad you got an answer. I thought you were overclocking that
baby beyond its ability.

Malke

 

[W. Watson]

W. Watson wrote:




Good. I'm glad you got an answer. I thought you were overclocking that
baby beyond its ability.

Malke

Well, I got a couple of answers. Neither of which I particularly like. This morning
when I talked to their tech guy, I said I checked the temp and it was OK. They sent
me a fairly long laundry list of other things to check: memory, pci slots, power
supply, clearing cmos, changing pci cards to new slots, updating chip drivers, ... I
decided to see if drivers would help. The tech sent me two: one for IDE and one for
AGP. No change. I called again tonight, and the next guy said its a XP Pro problem,
not theirs or AMD.

Pause. I just got off the phone for the second call. He put me through to a higher
tech support guy. He said I'd have to adjust the SPD levels for the memory, and told
me to get a program called cpu-z, which will read these values out of memory, and
into the SPD portion of BIOS. We went through a boot up without the values, so I
would know where to insert these values. I got the program but it couldn't dig them
out, so it showed a grayed out table. Now I need to open up the computer and find out
who the mfger is and use it to go to their web site to find out the values. Well, off
I go to return -- probably tomorrow. What an ordeal.

--
Wayne T. Watson (Watson Adventures, Prop., Nevada City, CA)
(121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
Obz Site: 39° 15' 7" N, 121° 2' 32" W, 2700 feet
(Formerly Homo habilis, erectus, heidelbergensis and now sapiens)

Sign in Programming Department: Mistakes made while you wait.

Web Page: <home.earthlink.net/~mtnviews>

 

[Quietman]

The AMD XP 1700+ runs at 1.467ghz with a FSB of 11 x 133mhz.

There are however three versions of the 1700 but only the voltage
requirements seem to be different for each.

 

[W. Watson]

Well, I got a couple of answers. Neither of which I particularly like.
This morning
when I talked to their tech guy, I said I checked the temp and it was
OK. They sent
me a fairly long laundry list of other things to check: memory, pci
slots, power
supply, clearing cmos, changing pci cards to new slots, updating chip
drivers, ... I
decided to see if drivers would help. The tech sent me two: one for IDE
and one for
AGP. No change. I called again tonight, and the next guy said its a XP
Pro problem,
not theirs or AMD.

Pause. I just got off the phone for the second call. He put me through
to a higher tech support guy. He said I'd have to adjust the SPD levels
for the memory, and told me to get a program called cpu-z, which will
read these values out of memory, and into the SPD portion of BIOS. We
went through a boot up without the values, so I would know where to
insert these values. I got the program but it couldn't dig them out, so
it showed a grayed out table. Now I need to open up the computer and
find out who the mfger is and use it to go to their web site to find out
the values. Well, off I go to return -- probably tomorrow. What an ordeal.

End of story. The machine is now running at 1.5GHz, and I'm not getting any boot up
messages. Never did figure out how to get the SPD values, serial presence detect. It
was very difficult (impossible) to get from the memory mfger, since the chip really
didn't have a good ID on it. It was a Micron look-a-like. However, by playing with
the frequency and multiplier PLUS the frequency ratio, I got the speed to 1.5GHz. I
think the trick was to not use Auto for the freq ratio, and select 1:1 instead.

--
Wayne T. Watson (Watson Adventures, Prop., Nevada City, CA)
(121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
Obz Site: 39° 15' 7" N, 121° 2' 32" W, 2700 feet
(Formerly Homo habilis, erectus, heidelbergensis and now sapiens)

Sign in Programming Department: Mistakes made while you wait.

Web Page: <home.earthlink.net/~mtnviews>