intel chip, intel board... but no dice. help?

Can someone help me try to figure out what's up with this?



I have an intel D815EEA mobo, which has been running a 600EB P3 (flip
chip 370) for some time and everything works fine. I recently picked up
a cheap 1Ghz P3 to make the machine a little more usable.

The problem is, although the 1G passes through the bios and stuff fine,
the machine reboots itself right before XP is about to load (right
before the logo would pop up). Swapping back in the 600EB everything
works fine...


For reference, the chip says:

1000/256/133/1.75v
L123A723-0243
PENTIUM III SL52R


... which ought to work according to...
support.intel.com/support/motherboards/desktop/d815eea/sb/cs-013068.htm
... right? Am I reading something wrong here? Is the chip just bad or
something? I'm using the latest bios version (p11) and there are no
cpu-speed jumpers on the board that I can see.... anyone have any ideas?

____
- Quartz -
there are 10 types of people in the world: those who get this joke, and
those who don't.

On Sun, 18 Sep 2005 16:34:05 -0400, Quartz
wrote:

I have an intel D815EEA mobo, which has been running a 600EB P3 (flip
chip 370) for some time and everything works fine. I recently picked up
a cheap 1Ghz P3 to make the machine a little more usable.

The problem is, although the 1G passes through the bios and stuff fine,
the machine reboots itself right before XP is about to load (right
before the logo would pop up). Swapping back in the 600EB everything
works fine...

Are you certain the heatsink is on good, that it wasn't
overheating? If you had tried reinstalling it multiple
times, that's probably not the problem but one time, maybe.

It should use more power too, is your power supply adequate?
You might take voltage readings. Also check it with
memtest86+. IIRC, the "EB" P3 was a 133MHz FSB CPU, so it
shouldn't be an issue of a higher memory bus speed from the
new CPU, though if you had changed no jumpers or bios
settings, we'd be assuming the speed but perhaps not proven
yet? Memtest86+ will also show the operational speed of the
CPU, not just what it's "supposed" to be.



For reference, the chip says:

1000/256/133/1.75v
L123A723-0243
PENTIUM III SL52R


.. which ought to work according to...
support.intel.com/support/motherboards/desktop/d815eea/sb/cs-013068.htm
.. right? Am I reading something wrong here? Is the chip just bad or
something? I'm using the latest bios version (p11) and there are no
cpu-speed jumpers on the board that I can see.... anyone have any ideas?

You could try clearing CMOS. I

Are you certain the heatsink is on good, that it wasn't
overheating?

yeah, that was the first thing everyone thought. but after a couple
reboots when I reach in touch the sink, it's only slightly warm, and if
I shut the machine off and pull the chip out it's not even warm at all.


It should use more power too, is your power supply adequate?

it certainly ought to be. I forget which is in there right now, but it's
somewhere in the 300-500 range. as for cards, I've got a geforce 4
mx440, a scsi card, and a firewire card (which has no devices plugged
into it).... I mean, does the 1g use like 100 watts or something?

You might take voltage readings. Also check it with
memtest86+. IIRC, the "EB" P3 was a 133MHz FSB CPU, so it
shouldn't be an issue of a higher memory bus speed from the
new CPU, though if you had changed no jumpers or bios
settings, we'd be assuming the speed but perhaps not proven
yet?

it's been running with that ram for a while with no problems, I doubt
that's the problem.

Memtest86+ will also show the operational speed of the
CPU, not just what it's "supposed" to be.

well, the bios shows it as a 1g 133 chip and gives me all the stepping
foo and such, I'd assume that it would cycle it down or something if
it's not supported at that speed.


You could try clearing CMOS. I

is there a reliable way to do this from the hardware side? the bios only
has one 'reset settings' type option which I already tried... would
yanking the battery do anything for me?


____
- Quartz -
there are 10 types of people in the world: those who get this joke, and
those who don't.

On Sun, 18 Sep 2005 23:26:06 -0400, Quartz
wrote:


Are you certain the heatsink is on good, that it wasn't
overheating?

yeah, that was the first thing everyone thought. but after a couple
reboots when I reach in touch the sink, it's only slightly warm, and if
I shut the machine off and pull the chip out it's not even warm at all.

If heatsink wasn't making good contact, it would not be
overly warm. A CPU core is rather low mass, partial
heatsink contact would cool it off quite quickly, such that
it didn't feel hot by the time you could get the heatsink
off to check it. Even so, this is no further evidence of an
actual problem and with the P3 having integral thermal
shutoff, I would doubt it's overheating, especially since
one can pull the 'sink and see if there was a clear imprint
of the CPU core. In some cases (with aluminum based 'sink
and optimal/minimal heatsink compound) you can even see the
imprint of the corners of the CPU on the 'sink, meaning it
must be making good contact unless the heatsink itself was
horribly irregular on the bottom.




It should use more power too, is your power supply adequate?

it certainly ought to be. I forget which is in there right now, but it's
somewhere in the 300-500 range. as for cards, I've got a geforce 4
mx440, a scsi card, and a firewire card (which has no devices plugged
into it).... I mean, does the 1g use like 100 watts or something?


Wattage rating means less if it's a generic. I've a 400W
generic (sitting unused) that is inferior to the typical
name-brand 250W. An upper end P3 might use 40W, but if your
PSU can actually deliver 150W combined 3V/5V, (for whole
system use of course) then it should be ok... but is still
something to investigate, take voltage readings.



You might take voltage readings. Also check it with
memtest86+. IIRC, the "EB" P3 was a 133MHz FSB CPU, so it
shouldn't be an issue of a higher memory bus speed from the
new CPU, though if you had changed no jumpers or bios
settings, we'd be assuming the speed but perhaps not proven
yet?

it's been running with that ram for a while with no problems, I doubt
that's the problem.

Memtest86+ will also show the operational speed of the
CPU, not just what it's "supposed" to be.

well, the bios shows it as a 1g 133 chip and gives me all the stepping
foo and such, I'd assume that it would cycle it down or something if
it's not supported at that speed.

Probably right then, though 'something' is wrong, best to
get another confirmation when the opportunity arises, IMO.




You could try clearing CMOS. I

is there a reliable way to do this from the hardware side? the bios only
has one 'reset settings' type option which I already tried... would
yanking the battery do anything for me?

Disconnect AC to the PSU, then either pull the battery for
~10 minutes or use the clear-cmos jumper (should be shown in
your manual or look around near the battery, though
sometimes further away from it).

Quartz, , the necrotic, spur-galled toilet cleaner, and
itinerant dealer in small goods and general pedlar, objurgated:

Can someone help me try to figure out what's up with this?



I have an intel D815EEA mobo, which has been running a 600EB P3 (flip
chip 370) for some time and everything works fine. I recently picked
up a cheap 1Ghz P3 to make the machine a little more usable.

The problem is, although the 1G passes through the bios and stuff
fine, the machine reboots itself right before XP is about to load
(right before the logo would pop up). Swapping back in the 600EB
everything works fine...


For reference, the chip says:

1000/256/133/1.75v
L123A723-0243
PENTIUM III SL52R


.. which ought to work according to...
support.intel.com/support/motherboards/desktop/d815eea/sb/cs-013068.htm
.. right? Am I reading something wrong here? Is the chip just bad or
something? I'm using the latest bios version (p11) and there are no
cpu-speed jumpers on the board that I can see.... anyone have any
ideas?

There may be something wrong with the cpu, but you should eliminate XP as
the problem before you conclude anything. Do this:

http://kadaitcha.cx/xp_how_to.html#b
Take the link to "Parallel Installation", then read the section called
"Install Windows XP to a new folder".

XP is known for not working with different chipsets. It is likely that XP is
trying to load the wrong microcode into the CPU, hence the reboot.

XP is known for not working with different chipsets. It is likely that XP is
trying to load the wrong microcode into the CPU, hence the reboot.

hmm... well that's interesting. I'll have to check that.


____
- Quartz -
there are 10 types of people in the world: those who get this joke, and
those who don't.

[heatsink]

hmm... well, lemme buy some more thermal grease and slap it on just to
make sure.



Wattage rating means less if it's a generic.

yeah I know, but what I'm getting at is that I've never had problems
with this before when taxing the system, so...

this mobo also has onboard voltage sensor readings, they've never shown
anything to be wrong before, should I trust them?



Probably right then, though 'something' is wrong, best to
get another confirmation when the opportunity arises, IMO.

yeah... I was hoping someone had a simple answer, but it looks like I
just have to run down the list and check things one by one.



Disconnect AC to the PSU, then either pull the battery for
~10 minutes or use the clear-cmos jumper (should be shown in
your manual or look around near the battery, though
sometimes further away from it).

err... there is a distinct lack of labeled jumpers on this board, other
than the 'special bios config' one.

____
- Quartz -
there are 10 types of people in the world: those who get this joke, and
those who don't.

http://kadaitcha.cx/xp_how_to.html#b
Take the link to "Parallel Installation", then read the section called
"Install Windows XP to a new folder".

hmm... is there any reason I'd *need* to install it to the same drive?
(as opposed to just stuffing an xbox HD or something in there and
installing to that)

____
- Quartz -
there are 10 types of people in the world: those who get this joke, and
those who don't.

On Mon, 19 Sep 2005 16:48:29 -0400, Quartz
wrote:


[heatsink]

hmm... well, lemme buy some more thermal grease and slap it on just to
make sure.



Wattage rating means less if it's a generic.

yeah I know, but what I'm getting at is that I've never had problems
with this before when taxing the system, so...

While that it a reasonable presumption, now your faster CPU
has a higher PSU load. With that in mind, it's still among
possible culprits.



this mobo also has onboard voltage sensor readings, they've never shown
anything to be wrong before, should I trust them?

yes/no/maybe.

you can trust then within the context of having trusted them
previously? If you want an accurate voltage reading, you
will have to use a multimeter to measure at the connector to
the load (for this purpose, a drive connector, or
motherboard connector, etc), BUT, the deviation of an
onboard sensor is somewhat linear with amperage such that if
it were off and you were aware of it, you can still use the
software report to note a relative change in voltage.



Probably right then, though 'something' is wrong, best to
get another confirmation when the opportunity arises, IMO.

yeah... I was hoping someone had a simple answer, but it looks like I
just have to run down the list and check things one by one.

Well the simple answer is it should work. Who knows, maybe
you received that one CPU out of a million that's defective
in some way? Odds are against it, but that doesn't help
that 1 person figure out what's going on.





Disconnect AC to the PSU, then either pull the battery for
~10 minutes or use the clear-cmos jumper (should be shown in
your manual or look around near the battery, though
sometimes further away from it).

err... there is a distinct lack of labeled jumpers on this board, other
than the 'special bios config' one.

Special bios config? Odd, try it.

On Mon, 19 Sep 2005 16:27:02 -0400, Quartz
wrote:


XP is known for not working with different chipsets. It is likely that XP is
trying to load the wrong microcode into the CPU, hence the reboot.

hmm... well that's interesting. I'll have to check that.


Since you continue to use the same board, you're using the
same chipset. It's even the same family of CPU, just one
with a higher multiplier and "Maybe" a different stepping.
XP should not be the problem unless there was already some
kind of timing bug that only surfaced due to the higher
performing CPU.