Hi, I'm trying to run Athlon 2000+ on MSI K7T Turbo (ms-6330) with
flashed BIOS, 352 MB PC133 ram, Win XP SP1, but with very little
success. The system runs OK if I have the CPU FSB jumper set to 100MHz
(the CPU speed is ~ 1250MHZ). If I take the jumper out, the CPU runs on
its normal 1660 MHz frequency, and Windows load pretty much as they
should. The problems occur when I try to run some CPU intensive
applications (such as seti@home), when everything just freezes (after 1-
2 minutes). This is very frustrating because I paid for one thing, but
I'm forced to have something else.

Thanks

--
Orin

If you don't mind getting in your computer, you might want to re-set your
CMOS. I found out mine is programmable (and was programmed by an excellent
group of unfriendlies). Do this by pulling the battery for about 2 minutes.
You will have to reflash the BIOS, and you may want to set an access
password for the BIOS if you have that option.


"Orin" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi, I'm trying to run Athlon 2000+ on MSI K7T Turbo (ms-6330) with
> flashed BIOS, 352 MB PC133 ram, Win XP SP1, but with very little
> success. The system runs OK if I have the CPU FSB jumper set to 100MHz
> (the CPU speed is ~ 1250MHZ). If I take the jumper out, the CPU runs on
> its normal 1660 MHz frequency, and Windows load pretty much as they
> should. The problems occur when I try to run some CPU intensive
> applications (such as seti@home), when everything just freezes (after 1-
> 2 minutes). This is very frustrating because I paid for one thing, but
> I'm forced to have something else.
>
> Thanks
>
> --
> Orin

On Thu, 4 Sep 2003 03:55:39 -0500, "David Burnett"
<(E-Mail Removed)> wrote:

>If you don't mind getting in your computer, you might want to re-set your
>CMOS. I found out mine is programmable (and was programmed by an excellent
>group of unfriendlies). Do this by pulling the battery for about 2 minutes.
>You will have to reflash the BIOS, and you may want to set an access
>password for the BIOS if you have that option.
>
>


So you're implying that some hostile group gained control of your PC,
went in and changed the CMOS settings, but not erasing or reflashing
the BIOS, so all you needed do to recover was restore the defaults?
To what end? It's so unlikely that the odds would favor you dreaming
up the whole event.


Dave

Orin,

In years past I've had similar problems. In my case, the problem was that
the heatsink and fan (HSF) were not good enough and the chip would overheat
and then freeze up (whereas when I ran the chip at a slower speed it would
run indefinitely). I know this because once I replaced the HSF all the
problems went away. I can't say I've had an overheating problem with any
Athlon XP chips lately, but I'm also much more careful with my cooling
solutions than I used to be.

Good luck,

Mike

"Orin" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi, I'm trying to run Athlon 2000+ on MSI K7T Turbo (ms-6330) with
> flashed BIOS, 352 MB PC133 ram, Win XP SP1, but with very little
> success. The system runs OK if I have the CPU FSB jumper set to 100MHz
> (the CPU speed is ~ 1250MHZ). If I take the jumper out, the CPU runs on
> its normal 1660 MHz frequency, and Windows load pretty much as they
> should. The problems occur when I try to run some CPU intensive
> applications (such as seti@home), when everything just freezes (after 1-
> 2 minutes). This is very frustrating because I paid for one thing, but
> I'm forced to have something else.
>
> Thanks
>
> --
> Orin

In article <aYM5b.168788$(E-Mail Removed)>,
(E-Mail Removed) says...
> Orin,
>
> In years past I've had similar problems. In my case, the problem was that
> the heatsink and fan (HSF) were not good enough and the chip would overheat
> and then freeze up (whereas when I ran the chip at a slower speed it would
> run indefinitely). I know this because once I replaced the HSF all the
> problems went away. I can't say I've had an overheating problem with any
> Athlon XP chips lately, but I'm also much more careful with my cooling
> solutions than I used to be.
>
> Good luck,
>
> Mike


Hi Mike, I doubt that the HSF would cause those problems, I have Spire's
Falcon Rock II cooler, and at lower speed my CPU heats to about 44 C,
today, god knows how, I managed to complete one seti@home work unit (on
1660 MHz freq.), and the temperature never went over 60 C. Still, it
might be worth looking into, at this point I'll try anything.


--
Orin