NEW 3.2E cpu not recognized in WIN XP home!!!!

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

OK, Ready???
My DELL MOBO crashed. Got a replacement from ASUS (P4S8X-MX).
Reinstalled my 1.7 P4, ran just fine!!!! So, of course I said "I know, a
NEWER, FASTER cpu would be nice. So, put together the money and bought and
installed A NEW 3.2E, W/800FSB. Couldn't wait to try DOOM again. ANYWAY,
upon initial install the MOBO see's the new chip correctly, as soon as I get
into WINDOWS the CPU gets knocked down to a 2128MHZ @533 FSB HUH?? ASUS was
nice enough to RMA the board (figuring something was up with it) But upon a
NEW install....SAME PROBLEM!! Got a 500 watt psu
1 gig corsair memory
180 Maxtor drive (not sata)
MSI Graphics card
And yes this is an OEM version of WINXP home. Just as an aside, I have a
BRANDY new puter w/win64 in it I am not using because I can't get on the net
with it. I use AOL and they have NO CONFIGURATIONS for it (that was a rant)
and I just can't wait till someone out there tells me this OEM version is SO
propritary that I can't use it EITHER!!!! just a moment,.......I need to
take a breath. Anyway, ANY ideas will be entertained.

Thanks
Bob R
 
Bob said:
OK, Ready???
My DELL MOBO crashed. Got a replacement from ASUS (P4S8X-MX).
Reinstalled my 1.7 P4, ran just fine!!!! So, of course I said "I know, a
NEWER, FASTER cpu would be nice. So, put together the money and bought and
installed A NEW 3.2E, W/800FSB. Couldn't wait to try DOOM again. ANYWAY,
upon initial install the MOBO see's the new chip correctly, as soon as I get
into WINDOWS the CPU gets knocked down to a 2128MHZ @533 FSB HUH?? ASUS was
nice enough to RMA the board (figuring something was up with it) But upon a
NEW install....SAME PROBLEM!! Got a 500 watt psu
1 gig corsair memory
180 Maxtor drive (not sata)
MSI Graphics card
And yes this is an OEM version of WINXP home. Just as an aside, I have a
BRANDY new puter w/win64 in it I am not using because I can't get on the net
with it. I use AOL and they have NO CONFIGURATIONS for it (that was a rant)
and I just can't wait till someone out there tells me this OEM version is SO
propritary that I can't use it EITHER!!!! just a moment,.......I need to
take a breath. Anyway, ANY ideas will be entertained.

Thanks
Bob R

Of course, the Pentium-4 3.2E Prescott CPU is so much
different from the earlier Tualatin or Northwood 1.7 GHz
CPU that a different Windows XP HAL would be needed. The
recourse would be to do a clean install of Windows XP with
the new motherboard and CPU. That was all that was changed?

If Dell-branded Windows XP does not install properly, then
it has just informed you that it is Dell-proprietary in
that essential driver files, such those needed for the 3.2E
Prescott CPU, might simply not be present.

But if the clean installation succeeded, be prepared for
the cross-rants from those who feel that you have violated
the EULA.
 
Thank you for the fast reply!!! Is it possible,to reinstall WIN XP without
totally redoing everything? I think in the past (it might have been in
win95) I was able to reinstall the op-sys right over the existing op-sy
giving me a fresh system, thereby, I might be able to make this painless.
Otherwise, I do have NORTON ghost. but i'd really rather not. I guess the
same questions would apply, should I have to PURCHASE yet ANOTHER op-system,
not OEM

AHH Computers, The "promise" of the future.
 
Just because the Mother Board smoked should not mean your copy of Windows is
smoked (in my opinion) also.
Check with ASUS for any driver/bios updates.

Jim
 
Bob said:
OK, Ready???
My DELL MOBO crashed. Got a replacement from ASUS (P4S8X-MX).
Reinstalled my 1.7 P4, ran just fine!!!! So, of course I said "I know, a
NEWER, FASTER cpu would be nice. So, put together the money and bought and
installed A NEW 3.2E, W/800FSB. Couldn't wait to try DOOM again. ANYWAY,
upon initial install the MOBO see's the new chip correctly, as soon as I get
into WINDOWS the CPU gets knocked down to a 2128MHZ @533 FSB HUH?? ASUS was
nice enough to RMA the board (figuring something was up with it) But upon a
NEW install....SAME PROBLEM!! Got a 500 watt psu
1 gig corsair memory
180 Maxtor drive (not sata)
MSI Graphics card
And yes this is an OEM version of WINXP home. Just as an aside, I have a
BRANDY new puter w/win64 in it I am not using because I can't get on the net
with it. I use AOL and they have NO CONFIGURATIONS for it (that was a rant)
and I just can't wait till someone out there tells me this OEM version is SO
propritary that I can't use it EITHER!!!! just a moment,.......I need to
take a breath. Anyway, ANY ideas will be entertained.

Thanks
Bob R

http://michaelstevenstech.com/XPrepairinstall.htm
 
Check the specs of your MB. Looks like it only supports 533 FSB. Where it
is an ASUS board, you can probably overclock to 800 FSB. Go to the ASUS
site an review the info there.

Woody
 
woody said:
Check the specs of your MB. Looks like it only supports 533 FSB. Where it
is an ASUS board, you can probably overclock to 800 FSB. Go to the ASUS
site an review the info there.

Woody

If the OP had just swapped the motherboard and CPU but kept
everything else, including the memory, then the CPU is under-
clocked. The motherboard needs DDR400 memory modules in order
to run at 800 MHz and take advantage of the Prescott CPU.
 
OK, Ready???
My DELL MOBO crashed. Got a replacement from ASUS (P4S8X-MX).
Reinstalled my 1.7 P4, ran just fine!!!! So, of course I said "I know, a
NEWER, FASTER cpu would be nice. So, put together the money and bought and
installed A NEW 3.2E, W/800FSB. Couldn't wait to try DOOM again. ANYWAY,
upon initial install the MOBO see's the new chip correctly, as soon as I
get
into WINDOWS the CPU gets knocked down to a 2128MHZ @533 FSB HUH?? ASUS
was
nice enough to RMA the board (figuring something was up with it) But upon
a
NEW install....SAME PROBLEM!! Got a 500 watt psu
1 gig corsair memory
180 Maxtor drive (not sata)
MSI Graphics card
And yes this is an OEM version of WINXP home. Just as an aside, I have a
BRANDY new puter w/win64 in it I am not using because I can't get on the
net
with it. I use AOL and they have NO CONFIGURATIONS for it (that was a
rant) and I just can't wait till someone out there tells me this OEM
version is SO
propritary that I can't use it EITHER!!!! just a moment,.......I need to
take a breath. Anyway, ANY ideas will be entertained.

Thanks
Bob R

If you're going to run 64-bit, then run an operating system that has been
around and running 64-bit for years now - ie. GNU/Linux.


--
When Microsoft stops treating its customers as thieves, I might consider
running Windoze again. Of course, I wouldn't allow it to access the
Internet. Windoze has no place on the Internet.

View Some Common Linux Desktops ...
http://linclips.crocusplains.com/index.php
 
Perhaps I should have been a little more specific. The memory was swapped to
maximize the board, so there is 400DDR memory on board as per ASUS spec. The
latest BIOS revision is also installed, As mentioned earlier, at initial
boot (after bios revision) the system comes up correctly ie: 3200mghz and
400DDR with a 800FSB. The problem is, as soon as I go onto WINDOWS and go
back to check BIOS, it is downgraded to 2128mhz and a 533 FSB. All the
Windows patches are installed. This version of Windows is approximatly 4
years old and is of the OEM version (DELL)
 
If you have another copy of Windows try a clean install (It will run for a
limited time without registering it) and see if the problem still exist.
This will at least eliminate anything that may be different with the Dell
OEM version of Windows.

Jim
 
Bob said:
Perhaps I should have been a little more specific. The memory was swapped to
maximize the board, so there is 400DDR memory on board as per ASUS spec. The
latest BIOS revision is also installed, As mentioned earlier, at initial
boot (after bios revision) the system comes up correctly ie: 3200mghz and
400DDR with a 800FSB. The problem is, as soon as I go onto WINDOWS and go
back to check BIOS, it is downgraded to 2128mhz and a 533 FSB. All the
Windows patches are installed. This version of Windows is approximatly 4
years old and is of the OEM version (DELL)

I think there is a HAL problem. First, the ASUS motherboard
uses a SiS chipset, if I am not mistaken whereas Dell is an
Intel shop. Second, the Intel 3.2E CPU is a Prescott with HT
capability. I'd follow up the recommendation to do a repair
install. Afterwards, add SP2. If this approach fails with the
Dell Windows XP cdrom, then get a non-branded OEM, full version
or a retail full version of Windows XP (with SP2).
 
From ASUS specs:

FSB
800*/533MHz
*The motherboard runs at FSB800 when in overclock mode.

Memory
2 x 184-pin DIMM Sockets support max. 2GB DDR400**/333 non-ECC DDR SDRAM
memory
- support DDR400/333 with FSB533
- support DDR333 with FSB800
**
1. When using an FSB800 CPU with 400MHz DDR memory, the motherboard runs at
333MHz by default.
2. When using an FSB533 CPU with 400MHz DDR memory, the motherboard runs at
400MHz.

http://www.asus.com/products4.aspx?modelmenu=2&model=494&l1=3&l2=12&l3=183

HTH

Woody
 
Perhaps I should have been a little more specific. The memory was swapped to
maximize the board, so there is 400DDR memory on board as per ASUS spec. The
latest BIOS revision is also installed, As mentioned earlier, at initial
boot (after bios revision) the system comes up correctly ie: 3200mghz and
400DDR with a 800FSB. The problem is, as soon as I go onto WINDOWS and go
back to check BIOS, it is downgraded to 2128mhz and a 533 FSB. All the
Windows patches are installed. This version of Windows is approximatly 4
years old and is of the OEM version (DELL)

Ahh... maybe it's simply too old to know about 800MHz, and therefore
assesses "over 400MHz therefore must be 533MHz" as a basis for
calculating the core speed. Let's try the math...

3200 / 800 = 400
400 x 533 = 2133

....yup, that fits. Is there any real adverse impact or speed issue,
or is this just cosmetic, i.e. old name for a new dog but the dog
still comes when it's called anyway?
 
cquirke said:
Ahh... maybe it's simply too old to know about 800MHz, and therefore
assesses "over 400MHz therefore must be 533MHz" as a basis for
calculating the core speed. Let's try the math...

3200 / 800 = 400
400 x 533 = 2133

...yup, that fits. Is there any real adverse impact or speed issue,
or is this just cosmetic, i.e. old name for a new dog but the dog
still comes when it's called anyway?

There might also be a bios update that could solve this
issue. The Prescott 3.2E CPU is a little different from
its predecessor Northwoods. Both the 800 MHz Northwoods
and Prescotts need to be double-clocked.
 
[/QUOTE]

OK, that answers Mistoffolees, perhaps?

Also suggests BIOS is OK.

Any patch to fix this, wouldn't be "critical" (not a safety/security
issue) and thus wouldn't have been aggressively pushed via Windows
Update or pulled via Automatic Update.

It would either be a trivial cosmetic fix affecting reporting only, or
a deep system code fix if there really were new processor
functionalities to be embraced. The latter would be a minefield for
testing to be safe as a retro-fit (high stakes if you screw up!), so
once again I doubt very much if it would be pushed out as a patch.
There might also be a bios update that could solve this

He's on the newest BIOS.
The Prescott 3.2E CPU is a little different from its predecessor
Northwoods. Both the 800 MHz Northwoods and Prescotts
need to be double-clocked.

The differences can go quite deep, and motherboard compatibility is
the usual battleground. Issues are:
- new (usually lower) voltage requirements
- possibly higher current draw requirements
- possible new socket
- new L2 cache capacity
- new base clock speed and/or core clock multipliers
- new processor features a la SIMD, EM64T, No-Execute, etc.
Compared to the above, describing the processor to the user is trivial
cosmetics, and something that BIOS appears to have got right.

I'm a bit concerned about motherboard compatibility in this case,
given that Asus describes 800MHz support as being "via overclocking",
which suggests it is NOT part of the motherboard chipset's feature
set. What motherboard chipset is it?



---------- ----- ---- --- -- - - - -
Don't pay malware vendors - boycott Sony
 
I don't know if I'm right here but I think XP home does not support multiple
CPUs and since someone mentioned that your CPU was a HT one, XP might be
having problems seeing 2 cpus (HT is seen as 2 CPUs)
Hope that helps.
 
Ravi said:
I don't know if I'm right here but I think XP home does not support
multiple CPUs


That's correct.

and since someone mentioned that your CPU was a HT one,
XP might be having problems seeing 2 cpus (HT is seen as 2 CPUs)


No. Although Hyperthreading is reported as two CPUs, it's not and Windows XP
Home can tell the difference. Unlike real dual CPUs, Windows XP Home *does*
support hyperthreading.
 
Back
Top