Dual core only shows 1 cpu in Task Manager

[cpu2]

I have an Athlon 3800 dual core that only shows 1 processor under windows task manager. I have downloaded Cpu-z and that only shows 1 core. Device manager under windows / system shows 2 processors, but the machine runs slow. Anyone any ideas?

 

[MountainKing]

Maybe you should try a clean install of Windows XP and see if this problem persists?

 

[cpu2]

Yes, sorry should have said. This was a new build. New install of both XP and have tried Vista on a VM. Both show only 1 CPU.
Any thing else?

 

[myocardia]

Install the AMD driver (the file that's second from the bottom), and the dual core optimizer, from this page: link.

 

[cpu2]

Many thanks,
I will try this when I go home lunch time. Will get back to you on the results.
cheers
steve

 

[cpu2]

No difference to task manager, but here is the output of cpuz

Number of processors 1
Number of cores 2 per processor
Number of threads 1 (max 2) per processor
Name AMD Athlon 64 X2 3800+
Code Name Manchester
Specification AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
Package Socket 939
Family/Model/Stepping F.B.1
Extended Family/Model F.2B
Brand ID 5
Core Stepping BH-E4
Technology 90 nm
Core Speed 2009.2 MHz
Multiplier x Bus speed 10.0 x 200.9 MHz
HT Link speed 1004.6 MHz
Stock frequency 2000 MHz
Instruction sets MMX (+), 3DNow! (+), SSE, SSE2, SSE3, x86-64
L1 Data cache 2 x 64 KBytes, 2-way set associative, 64-byte line size
L1 Instruction cache 2 x 64 KBytes, 2-way set associative, 64-byte line size
L2 cache 2 x 512 KBytes, 16-way set associative, 64-byte line size

 

[gramboh]

At the bottom of CPUz it should say:

Selection: Processor #1 (grayed out) then Cores: 2, Threads: 2

From the output above it seems to be saying that (2 cores per processor)?

Task manager under the 'Performance' tab should show two boxes for CPU usage history.

 

[cpu2]

Hi, yes, thats the point. Should being the operative.
I have checked to make sure that 1 graph per cpu is ticked, actually this option is greyed out also.

 

[stevty2889]

Look in device manager, under computer, does it say ACPI multiprocessor PC?

 

[cpu2]

from memory, NO. I am back at work now, and can check for definte later. but I am sure it just says ACPI.

 

[Fraggable]

Sounds to me like something is wrong in BIOS. Update your BIOS and verify that any options for dual-core CPUs, etc are set correctly. Maybe your CPU is a newer stepping that the BIOS doesn't fully support.

 

[cpu2]

I have done an update on the bios some time ago. This is what the cpuz shows

System Manufacturer System manufacturer
System Name System Product Name
System S/N System Serial Number
Mainboard Vendor ASUSTeK Computer INC.
Mainboard Model A8N32-SLI-Deluxe
BIOS Vendor American Megatrends Inc.
BIOS Version 1205
BIOS Date 04/28/2006

Not sure if there is anything newer for this machine./???

 

[Fraggable]

BIOS date 4/28/06? A year old? There's probably been 10 updates for it since then. And the core for your CPU is pretty new. That's where I'm putting my money, your BIOS doesn't have full capability for that core. Update it and see what happens.

EDIT: There has been 2 updates since then and a beta is also available. Try this: http://dlsvr03.asus.com/pub/ASUS/mb/socket939/A8N32-SLI%20Deluxe/A8N321303.zip

 

[cpu2]

Eventually (2hours later) managed to update the bios. What a nightmare, but still no difference. I have not checked all the settings yet (not quite sure what to look for) but still only shows 1 cpu in task manager.
Thanks for the help.

 

[undeclared]

Are you sure you didn't go into the store, say Athlon 64 X2 3800, then they gave you an Athlon 64 3800 instead?

It is possible, if the socket is AM2.

 

[myocardia]

Originally posted by: xtwells
It is possible, if the socket is AM2.

They made single core A64 3800's for Skt 939, also. Anyway, Steve, you're gonna have to reinstall Windows, unless you want to attempt trying to force Windows to let you change it's ACPI configuration. It's alot easier to reinstall, though, and always seems to work out better.

 

[cpu2]

But does not the reading from cpuz indicate otherwise. Heres the bit again
Number of processors 1
Number of cores 2 per processor
Number of threads 1 (max 2) per processor
Name AMD Athlon 64 X2 3800+
Code Name Manchester
Specification AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
Package Socket 939
Family/Model/Stepping F.B.1
Extended Family/Model F.2B
Brand ID 5
Core Stepping BH-E4
Technology 90 nm
Core Speed 2009.2 MHz
Multiplier x Bus speed 10.0 x 200.9 MHz
HT Link speed 1004.6 MHz
Stock frequency 2000 MHz

If reinstalling windows is the only way to go, then I better go. But not just yet. My nerves cant stand it

cheers for all the help

 

[five4o]

I had the same problem when I bought my X2 3800 in 2005.
I called MSI support and I think it was the bios or the AMD drivers, sorry I forgot exactly what it was.
I'm almost sure it was BIOS because every other time when I re-installed xp to the same system both cores showed up without any special drivers
so thats why I'm almost sure it was the BIOS.

 

[ItsOnlyMe]

This might help:-

http://www.handaware.com/multiprocessor_XP.html

It was posted here a little while ago and it worked for me.

Dave

 

[cpu2]

Thanks for the link Dave,
Will try this one later, it sure beats having to re-install windows. I have SATA drives which were not recognized in the original build and it took ages to get everything up and running.
will post back if I get it working.

 

[lopri]

Umm..

In Task Manager,

Go to 'View' menu -> Drop down menu pops up -> Highlight 'CPU History' -> Select 'One Graph per CPU'

Not sure if this was suggested (didn't read the whole thread, sorry) but it's one of those little thing that one can forget easily.

 

[cpu2]

yes, that was suggested.
But the previuos poster pointed me in the right dirrection
www.handaware.com/multiprocessor_xp.html

Now Im cooking.
Thanks to everyone for there suggestions. This has been a good news group - very helpfull unlike some where all you get is abuse becuase you don't know something others take for granted. All part of the learning curve.
Once again thanks to all