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
On Fri, 09 Mar 2001 03:42:32 GMT, "Tim" <[email hidden]>
wrote:
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
Quoted text (14 lines)
>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?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
"daxe" <[email hidden]> wrote in message
news:[email hidden]...
off
Quoted text (7 lines)
> On Fri, 09 Mar 2001 03:42:32 GMT, "Tim" <[email hidden]> > wrote: > > >PIII 1Ghz cpu > >CUSL2 mb > > > >It worked prior to shipping but when it arrvived the heatsink had fallenQuoted text (21 lines)
> >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 >It is 133 memory, one chip
I will try that
Thanks
Charlie B <[email hidden]> wrote in message
news:0b0q6.1233$[email hidden]...
> try resetting the cmos with the jumper on the MB. Uusally just have toshut
> down machine. Change over jumper to other postion for 10 or 15 secs.change
fallen
Quoted text (12 lines)
> jumper to orig. position and reboot. Definetly need 133mhz ram. > > Charlie B > "daxe" <[email hidden]> wrote in message > news:[email hidden]... > > On Fri, 09 Mar 2001 03:42:32 GMT, "Tim" <[email hidden]> > > wrote: > > > > >PIII 1Ghz cpu > > >CUSL2 mb > > > > > >It worked prior to shipping but when it arrvived the heatsink hadQuoted text (24 lines)
> 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 > > > >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
On Fri, 09 Mar 2001 13:35:48 GMT, "Tim" <[email hidden]>
wrote:
Quoted text (48 lines)
>It is 133 memory, one chip >I will try that >Thanks > >Charlie B <[email hidden]> wrote in message >news:0b0q6.1233$[email hidden]... >> 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 >> "daxe" <[email hidden]> wrote in message >> news:[email hidden]... >> > On Fri, 09 Mar 2001 03:42:32 GMT, "Tim" <[email hidden]> >> > wrote: >> > >> > >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 >> > >> >> >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
:)
daxe <[email hidden]> wrote in message
news:[email hidden]...
Quoted text (62 lines)
> 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 > > > On Fri, 09 Mar 2001 13:35:48 GMT, "Tim" <[email hidden]> > wrote: > > >It is 133 memory, one chip > >I will try that > >Thanks > > > >Charlie B <[email hidden]> wrote in message > >news:0b0q6.1233$[email hidden]... > >> 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 > >> "daxe" <[email hidden]> wrote in message > >> news:[email hidden]... > >> > On Fri, 09 Mar 2001 03:42:32 GMT, "Tim" <[email hidden]> > >> > wrote: > >> > > >> > >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 > >> > > >> > >> > > >
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
the CPU and Mobo *run*, but just won't run @ 133.
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
On Sat, 10 Mar 2001 02:15:53 GMT, "Tim" <[email hidden]>
wrote:
Quoted text (76 lines)
>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 > >:) > > >daxe <[email hidden]> wrote in message >news:[email hidden]... >> 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 >> >> >> On Fri, 09 Mar 2001 13:35:48 GMT, "Tim" <[email hidden]> >> wrote: >> >> >It is 133 memory, one chip >> >I will try that >> >Thanks >> > >> >Charlie B <[email hidden]> wrote in message >> >news:0b0q6.1233$[email hidden]... >> >> 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 >> >> "daxe" <[email hidden]> wrote in message >> >> news:[email hidden]... >> >> > On Fri, 09 Mar 2001 03:42:32 GMT, "Tim" <[email hidden]> >> >> > wrote: >> >> > >> >> > >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 >> >> > >> >> >> >> >> > >> >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/
On Fri, 09 Mar 2001 03:42:32 GMT, "Tim" <[email hidden]>
wrote:
Quoted text (19 lines)
>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 > >Ill try that
daxe <[email hidden]> wrote in message
news:[email hidden]...
jumpers
to
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 PC100DIMMs.
Quoted text (23 lines)
> > 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 > the CPU and Mobo *run*, but just won't run @ 133. > > 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 > > > > > On Sat, 10 Mar 2001 02:15:53 GMT, "Tim" <[email hidden]> > wrote: > > >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 CMOSQuoted text (29 lines)
> >are > >? so far, can you tell what would of caused this? > >And if so, is the potential bad part the CPU or the MB > > > >:) > > > > > >daxe <[email hidden]> wrote in message > >news:[email hidden]... > >> 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 > >> > >> > >> On Fri, 09 Mar 2001 13:35:48 GMT, "Tim" <[email hidden]> > >> wrote: > >> > >> >It is 133 memory, one chip > >> >I will try that > >> >Thanks > >> > > >> >Charlie B <[email hidden]> wrote in message > >> >news:0b0q6.1233$[email hidden]... > >> >> try resetting the cmos with the jumper on the MB. Uusally just haveQuoted text (30 lines)
> >> >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 > >> >> "daxe" <[email hidden]> wrote in message > >> >> news:[email hidden]... > >> >> > On Fri, 09 Mar 2001 03:42:32 GMT, "Tim" <[email hidden]> > >> >> > wrote: > >> >> > > >> >> > >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 aQuoted text (10 lines)
> >> >> > They are not the same chip. > >> >> > > >> >> > ~daxe > >> >> > > >> >> > >> >> > >> > > >> > > >Tried shorting out CMOS, no luck
Using 100/100/33 I can get it up to 900 Mhz safely @120/120/40 but anything
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
daxe <[email hidden]> wrote in message
news:[email hidden]...
Quoted text (12 lines)
> > 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 > the CPU and Mobo *run*, but just won't run @ 133. > > 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? > > ~daxeStill 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
On Mon, 12 Mar 2001 04:01:53 GMT, "Tim" <[email hidden]>
wrote:
Quoted text (25 lines)
>Tried shorting out CMOS, no luck >Using 100/100/33 I can get it up to 900 Mhz safely @120/120/40 but anything >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 > >daxe <[email hidden]> wrote in message >news:[email hidden]... >> >> 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 >> the CPU and Mobo *run*, but just won't run @ 133. >> >> 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 > >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
daxe <[email hidden]> wrote in message
news:[email hidden]...
> 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?


































