rec.autos.simulators

CPU WONT LOAD CORRECTLY

Tim

CPU WONT LOAD CORRECTLY

by Tim » Sat, 10 Mar 2001 12:42:32

PIII 1Ghz cpu
CUSL2 mb

It worked prior to shipping but when it arrvived the heatsink had fallen off
Remounted it, there was no apparent damage anywhere

Upon booting, it defaults to 500mhz
Tried reseating CPU it automattically goes to bios
Tried changing to 1000Mhz but still resets to 500 and loads bios
The only thing that works is manually setting to 100/100/33
It loads at 750Mhz and everything works fine
Have re-seasted all parts to no avail

Any ideas?

THANKS
Tim

daxe

CPU WONT LOAD CORRECTLY

by daxe » Sat, 10 Mar 2001 15:21:03



Since it loads at 750Mhz, that would indicate that you have a P3/1G
with a 133fsb (7.5x133=1000 - 7.5x100=750).  Are you using PC133
DIMMs?

The p3/1G with the 100fsb has a 10x multiplier and uses PC100 DIMMs.
They are not the same chip.

~daxe

Charlie

CPU WONT LOAD CORRECTLY

by Charlie » Sat, 10 Mar 2001 17:07:24

try resetting the cmos with the jumper on the MB. Uusally just have to shut
down machine. Change over jumper to other postion for 10 or 15 secs. change
jumper to orig. position and reboot. Definetly need 133mhz ram.

  Charlie B



> >PIII 1Ghz cpu
> >CUSL2 mb

> >It worked prior to shipping but when it arrvived the heatsink had fallen
off
> >Remounted it, there was no apparent damage anywhere

> >Upon booting, it defaults to 500mhz
> >Tried reseating CPU it automattically goes to bios
> >Tried changing to 1000Mhz but still resets to 500 and loads bios
> >The only thing that works is manually setting to 100/100/33
> >It loads at 750Mhz and everything works fine
> >Have re-seasted all parts to no avail

> >Any ideas?

> Since it loads at 750Mhz, that would indicate that you have a P3/1G
> with a 133fsb (7.5x133=1000 - 7.5x100=750).  Are you using PC133
> DIMMs?

> The p3/1G with the 100fsb has a 10x multiplier and uses PC100 DIMMs.
> They are not the same chip.

> ~daxe

Tim

CPU WONT LOAD CORRECTLY

by Tim » Sat, 10 Mar 2001 22:35:48

It is 133 memory, one chip
I will try that
Thanks


> try resetting the cmos with the jumper on the MB. Uusally just have to
shut
> down machine. Change over jumper to other postion for 10 or 15 secs.
change
> jumper to orig. position and reboot. Definetly need 133mhz ram.

>   Charlie B




> > >PIII 1Ghz cpu
> > >CUSL2 mb

> > >It worked prior to shipping but when it arrvived the heatsink had
fallen
> off
> > >Remounted it, there was no apparent damage anywhere

> > >Upon booting, it defaults to 500mhz
> > >Tried reseating CPU it automattically goes to bios
> > >Tried changing to 1000Mhz but still resets to 500 and loads bios
> > >The only thing that works is manually setting to 100/100/33
> > >It loads at 750Mhz and everything works fine
> > >Have re-seasted all parts to no avail

> > >Any ideas?

> > Since it loads at 750Mhz, that would indicate that you have a P3/1G
> > with a 133fsb (7.5x133=1000 - 7.5x100=750).  Are you using PC133
> > DIMMs?

> > The p3/1G with the 100fsb has a 10x multiplier and uses PC100 DIMMs.
> > They are not the same chip.

> > ~daxe

daxe

CPU WONT LOAD CORRECTLY

by daxe » Sun, 11 Mar 2001 08:14:12

I have this same CPU (P3/1G/133fsb) and the CUSL2-C Mobo.  I'll follow
this thread to see if I can help you further.

When you say it works to manually set 100/100/33, try setting manually
to 133/133/33 and see if that works.  That's what is behind the auto
detect setting for that CPU.

~daxe



>It is 133 memory, one chip
>I will try that
>Thanks



>> try resetting the cmos with the jumper on the MB. Uusally just have to
>shut
>> down machine. Change over jumper to other postion for 10 or 15 secs.
>change
>> jumper to orig. position and reboot. Definetly need 133mhz ram.

>>   Charlie B




>> > >PIII 1Ghz cpu
>> > >CUSL2 mb

>> > >It worked prior to shipping but when it arrvived the heatsink had
>fallen
>> off
>> > >Remounted it, there was no apparent damage anywhere

>> > >Upon booting, it defaults to 500mhz
>> > >Tried reseating CPU it automattically goes to bios
>> > >Tried changing to 1000Mhz but still resets to 500 and loads bios
>> > >The only thing that works is manually setting to 100/100/33
>> > >It loads at 750Mhz and everything works fine
>> > >Have re-seasted all parts to no avail

>> > >Any ideas?

>> > Since it loads at 750Mhz, that would indicate that you have a P3/1G
>> > with a 133fsb (7.5x133=1000 - 7.5x100=750).  Are you using PC133
>> > DIMMs?

>> > The p3/1G with the 100fsb has a 10x multiplier and uses PC100 DIMMs.
>> > They are not the same chip.

>> > ~daxe

Tim

CPU WONT LOAD CORRECTLY

by Tim » Sun, 11 Mar 2001 11:15:53

I did try it and it did not work
Im pretty sure I tried all four settings but I cant remember what the 3rd
one was
Just got back home so Im looking at the manual to see where the CMOS jumpers
are
? so far, can you tell what would of caused this?
And if so, is the potential bad part the CPU or the MB

:)


> I have this same CPU (P3/1G/133fsb) and the CUSL2-C Mobo.  I'll follow
> this thread to see if I can help you further.

> When you say it works to manually set 100/100/33, try setting manually
> to 133/133/33 and see if that works.  That's what is behind the auto
> detect setting for that CPU.

> ~daxe



> >It is 133 memory, one chip
> >I will try that
> >Thanks



> >> try resetting the cmos with the jumper on the MB. Uusally just have to
> >shut
> >> down machine. Change over jumper to other postion for 10 or 15 secs.
> >change
> >> jumper to orig. position and reboot. Definetly need 133mhz ram.

> >>   Charlie B




> >> > >PIII 1Ghz cpu
> >> > >CUSL2 mb

> >> > >It worked prior to shipping but when it arrvived the heatsink had
> >fallen
> >> off
> >> > >Remounted it, there was no apparent damage anywhere

> >> > >Upon booting, it defaults to 500mhz
> >> > >Tried reseating CPU it automattically goes to bios
> >> > >Tried changing to 1000Mhz but still resets to 500 and loads bios
> >> > >The only thing that works is manually setting to 100/100/33
> >> > >It loads at 750Mhz and everything works fine
> >> > >Have re-seasted all parts to no avail

> >> > >Any ideas?

> >> > Since it loads at 750Mhz, that would indicate that you have a P3/1G
> >> > with a 133fsb (7.5x133=1000 - 7.5x100=750).  Are you using PC133
> >> > DIMMs?

> >> > The p3/1G with the 100fsb has a 10x multiplier and uses PC100 DIMMs.
> >> > They are not the same chip.

> >> > ~daxe

daxe

CPU WONT LOAD CORRECTLY

by daxe » Sun, 11 Mar 2001 14:21:07

If you can get it to boot and run with 100/100/33 then I would say it
is neither the CPU nor the Mobo but the ram which is at fault since

Since  the Mobo is not autodetecting the CPU correctly it probably
isnt autodetecting the right core voltage either.  Have you checked
this out?  You can also increase the fsb speed incrementally with the
CUSL2 bios.  Have you tried running, say 101/101/34 or something like
that?

~daxe



>I did try it and it did not work
>Im pretty sure I tried all four settings but I cant remember what the 3rd
>one was
>Just got back home so Im looking at the manual to see where the CMOS jumpers
>are
>? so far, can you tell what would of caused this?
>And if so, is the potential bad part the CPU or the MB

>:)



>> I have this same CPU (P3/1G/133fsb) and the CUSL2-C Mobo.  I'll follow
>> this thread to see if I can help you further.

>> When you say it works to manually set 100/100/33, try setting manually
>> to 133/133/33 and see if that works.  That's what is behind the auto
>> detect setting for that CPU.

>> ~daxe



>> >It is 133 memory, one chip
>> >I will try that
>> >Thanks



>> >> try resetting the cmos with the jumper on the MB. Uusally just have to
>> >shut
>> >> down machine. Change over jumper to other postion for 10 or 15 secs.
>> >change
>> >> jumper to orig. position and reboot. Definetly need 133mhz ram.

>> >>   Charlie B




>> >> > >PIII 1Ghz cpu
>> >> > >CUSL2 mb

>> >> > >It worked prior to shipping but when it arrvived the heatsink had
>> >fallen
>> >> off
>> >> > >Remounted it, there was no apparent damage anywhere

>> >> > >Upon booting, it defaults to 500mhz
>> >> > >Tried reseating CPU it automattically goes to bios
>> >> > >Tried changing to 1000Mhz but still resets to 500 and loads bios
>> >> > >The only thing that works is manually setting to 100/100/33
>> >> > >It loads at 750Mhz and everything works fine
>> >> > >Have re-seasted all parts to no avail

>> >> > >Any ideas?

>> >> > Since it loads at 750Mhz, that would indicate that you have a P3/1G
>> >> > with a 133fsb (7.5x133=1000 - 7.5x100=750).  Are you using PC133
>> >> > DIMMs?

>> >> > The p3/1G with the 100fsb has a 10x multiplier and uses PC100 DIMMs.
>> >> > They are not the same chip.

>> >> > ~daxe

Jeff Shar

CPU WONT LOAD CORRECTLY

by Jeff Shar » Sun, 11 Mar 2001 20:00:47

For peace of mind you might want to download and run this utility from
intel to positively id the cpu.

http://support.intel.com/support/processors/tools/frequencyid/



Tim

CPU WONT LOAD CORRECTLY

by Tim » Mon, 12 Mar 2001 02:03:10

Ill try that


> If you can get it to boot and run with 100/100/33 then I would say it
> is neither the CPU nor the Mobo but the ram which is at fault since

> Since  the Mobo is not autodetecting the CPU correctly it probably
> isnt autodetecting the right core voltage either.  Have you checked
> this out?  You can also increase the fsb speed incrementally with the
> CUSL2 bios.  Have you tried running, say 101/101/34 or something like
> that?

> ~daxe



> >I did try it and it did not work
> >Im pretty sure I tried all four settings but I cant remember what the 3rd
> >one was
> >Just got back home so Im looking at the manual to see where the CMOS
jumpers
> >are
> >? so far, can you tell what would of caused this?
> >And if so, is the potential bad part the CPU or the MB

> >:)



> >> I have this same CPU (P3/1G/133fsb) and the CUSL2-C Mobo.  I'll follow
> >> this thread to see if I can help you further.

> >> When you say it works to manually set 100/100/33, try setting manually
> >> to 133/133/33 and see if that works.  That's what is behind the auto
> >> detect setting for that CPU.

> >> ~daxe



> >> >It is 133 memory, one chip
> >> >I will try that
> >> >Thanks



> >> >> try resetting the cmos with the jumper on the MB. Uusally just have
to
> >> >shut
> >> >> down machine. Change over jumper to other postion for 10 or 15 secs.
> >> >change
> >> >> jumper to orig. position and reboot. Definetly need 133mhz ram.

> >> >>   Charlie B




> >> >> > >PIII 1Ghz cpu
> >> >> > >CUSL2 mb

> >> >> > >It worked prior to shipping but when it arrvived the heatsink had
> >> >fallen
> >> >> off
> >> >> > >Remounted it, there was no apparent damage anywhere

> >> >> > >Upon booting, it defaults to 500mhz
> >> >> > >Tried reseating CPU it automattically goes to bios
> >> >> > >Tried changing to 1000Mhz but still resets to 500 and loads bios
> >> >> > >The only thing that works is manually setting to 100/100/33
> >> >> > >It loads at 750Mhz and everything works fine
> >> >> > >Have re-seasted all parts to no avail

> >> >> > >Any ideas?

> >> >> > Since it loads at 750Mhz, that would indicate that you have a
P3/1G
> >> >> > with a 133fsb (7.5x133=1000 - 7.5x100=750).  Are you using PC133
> >> >> > DIMMs?

> >> >> > The p3/1G with the 100fsb has a 10x multiplier and uses PC100
DIMMs.
> >> >> > They are not the same chip.

> >> >> > ~daxe

Tim

CPU WONT LOAD CORRECTLY

by Tim » Tue, 13 Mar 2001 13:01:53

Tried shorting out CMOS, no luck

higher locks up PC or gets the blue screen
I have not tried changing the core voltage but its at 1.7
Also used Intel's processor frequency utility and it correctly identifies
the CPU at 1 Ghz and 133FSB

The memory is from crucial


> If you can get it to boot and run with 100/100/33 then I would say it
> is neither the CPU nor the Mobo but the ram which is at fault since

> Since  the Mobo is not autodetecting the CPU correctly it probably
> isnt autodetecting the right core voltage either.  Have you checked
> this out?  You can also increase the fsb speed incrementally with the
> CUSL2 bios.  Have you tried running, say 101/101/34 or something like
> that?

> ~daxe

daxe

CPU WONT LOAD CORRECTLY

by daxe » Wed, 14 Mar 2001 00:26:15

Still sounds to me like the memory is not PC133.  Try and  borrow some
known PC133 from someone and see if that helps.  With all you are
doing, it seems like the FSB is the stumbling point.  That would tend
to stumble when the RAM can't keep up.

Had you used this RAM in another situation previously?

~daxe



>Tried shorting out CMOS, no luck

>higher locks up PC or gets the blue screen
>I have not tried changing the core voltage but its at 1.7
>Also used Intel's processor frequency utility and it correctly identifies
>the CPU at 1 Ghz and 133FSB

>The memory is from crucial



>> If you can get it to boot and run with 100/100/33 then I would say it
>> is neither the CPU nor the Mobo but the ram which is at fault since

>> Since  the Mobo is not autodetecting the CPU correctly it probably
>> isnt autodetecting the right core voltage either.  Have you checked
>> this out?  You can also increase the fsb speed incrementally with the
>> CUSL2 bios.  Have you tried running, say 101/101/34 or something like
>> that?

>> ~daxe

Tim

CPU WONT LOAD CORRECTLY

by Tim » Thu, 15 Mar 2001 02:32:29

Everything was fine before we shipped it
The heatsink had fallen off in shipping and didnt notice until after he
turned it on and it locked at the black screen
Intel Freq Util correctly identifies the chip but that doesnt mean it wasnt
damaged, and thats what scaring me
The fan wires were crimped around the memory module and replaced that to no
avail
At 864mhz he is now getting errors in windows so Im really counting on that
memory being bad :)
Buying another stick tonight to try that

Thanks



rec.autos.simulators is a usenet newsgroup formed in December, 1993. As this group was always unmoderated there may be some spam or off topic articles included. Some links do point back to racesimcentral.net as we could not validate the original address. Please report any pages that you believe warrant deletion from this archive (include the link in your email). RaceSimCentral.net is in no way responsible and does not endorse any of the content herein.