Windows only using one core on a dual core system

[tricon]

I'm running Windows xp media center edition 2005 with a core duo T2300. Device manager
reports both cpus, however task manager graphs only one.

www.rollscythe.com/images/taskmngr.JPG
I cannot set an affinity for any programs either. Cpuz reports the correct processor,
but the option to select different proccessor cores is disabled.

www.rollscythe.com/images/cpuzdvmngr.JPG
I've checked the bios to make sure its set to use both cores, which it is. I also
have Windows xp pro installed on a usb hdd which I booted from, it shows two graphs
in task manager as it should. So its not a hardware issue as far as I can tell since
one install of windows works fine using two cores. What would cause one install
of Windows not to use both cores and what can be done to remedy it? Thank you!

 

[mechBgon]

Welcome to the Forums In the Device Manager, if you expand Computer, is it ACPI Multiprocessor PC? If not, what's it say instead?

 

[tricon]

Yes, it does show it as an ACPI Multiprocessor PC.

 

[mechBgon]

Huh Try having it redetect for hardware changes, maybe?

 

[tricon]

)= Sadly no luck trying to detect new hardware changes, however I read somthing about modifing a HAL file on another thread. Any ideas?

 

[imported_lparkin]

You should make sure that both cores are enabled in the bios of the machine. They probably are because Windows is seeing two, but you ought to make sure.

 

[Skitzer]

I thought the Media Center Edition was based on the XP Home OS. XP Home is single processor only isn't it?

 

[tricon]

I'm not sure if its based on XP home or not but I know it supports dual core cpus as I have another computer with media center running on a Pentium D 830

http://www.rollscythe.com/images/mcedual.JPG

 

[Maximilian]

Did it ever work with two cores? Or has it always been that way. If so you may need a BIOS upgrade, check the mobo manufacturers site to see if theyve updated support for core duo cpu's.

 

[tricon]

No, it has been only using one core since windows was installed recently. I thought it was a bios issue as well at first, but I booted from another install of windows and it worked fine with both cores.

 

[TonyRic]

MCE is based on PRO not HOME. Even if it were home, you are limited to one PHYSICAL processor, not one core. Home will work with Hyperthreading and Dual Cores without any problem. But, since this is MCE which is Pro based, this is OT.

If I were you, I would send a bug report to Microsoft. They should be able to help you out with your problem. If ACPI is showing multiprocessor, and showed cpu0 and cpu1, then it is simply a task manager problem. That app is not the end all be all and is frequently unable to do its job properly (This is based on personal knowledge and experience).

 

[MrChad]

In Task Manager, under View / CPU History, is the "One Graph per CPU" option checked?

 

[tricon]

Thank you everyone for your help...problem solved, the solution...

I modified my boot.ini file with the parameters '/usepmtimer' and '/numproc=2' as well as replaced the files 'ntkrnlmp.exe', 'ntoskrnl.exe', 'ntkrpamp.exe', 'ntkrnlpa.exe', 'halmacpi.dll', and 'hal.dll' with the ones from another install of media center and from various sites. After rebooting both cores were operational.

www.rollscythe.com/images/dualcore.JPG

Im not sure if changing the boot.ini file actually had any effect or not though, because I changed it back the the unmodified version and both cores still worked.

 

[beer]

I've seen this before, but only coming out of a major OEM's production factory (actually pre-production internal use, but that's besides the point). It is actually possible to install the 'wrong' HAL, but the Windows setup (the traditional way most users install their OS) should install this correctly. This problem should only really occur when other methods are used to install the OS.

When this happens - the wrong HAL on on a dual-core machine, bad things happen. I work in device driver development...random blue screens and driver anomolies

 

[ForumMaster]

great that you managed to fix your prob. just one question, why are you running your cpu at such a slow speed? why is it at 990Mhz instead of it's rated 1.66Ghz?

 

[gwag]

Originally posted by: ForumMaster
great that you managed to fix your prob. just one question, why are you running your cpu at such a slow speed? why is it at 990Mhz instead of it's rated 1.66Ghz?

they throttle back when not doing anything i suspect, it is 2006.

 

[tricon]

Yeah exactly, when the cpu is under load is runs at 1.6xx