Re: P5B Plus Q6600 only uses one core

Paul <nospam@xxxxxxxxxx> wrote in news:f5pgj0$5ca$1@xxxxxxxx:

Jim Krol wrote:
I just set up a new system using the P5B Plus and a q6600 processor.
It appears that it is only using one of the cores on the processor.
Windows task manager only shows one window. The system runs slower
than the old 2.6G processor it was supposed to replace. Is the
processor bad or did I do something stupid in the setup or bios? I
did upgrade to the new bios 604, which didn't help.


This put me on the right track, but alas there is no joy in Mudville.
When I try to set up HAL in the setup the only option I get is i486 c-
<something> None of the acpi options.WinXP x64 gives me the multi option
but crashes when windows reboots to install. Is there something I have
to set in bios to tell it to run multiprocessor mode.I took the default
configuration in the bios. It looks like the bios is not telling windows
that it has a multiprocessor installed.Do I need to RMA this board
again! The first one would not even POST. I have always used the other
"A" companies motherboards and never had a problem. People have always
given great Kudos to Asus boards so I thought I'd try one. This
experience has not endeared me to Asus. Even a cheapo ECS board i used
came right up in multiprocessor mode. Any bios settings I should try??
Or, is there another 2 week RMA in my future.

Thanks,
JK


Thanks,

Jim Krol

The first thing I'd check - go to Device Manager, check the "Computer"
entry. The subentry underneath it is the HAL or Hardware Abstraction
Layer.

For the more trivial HAL changes, you change the "Driver" for the HAL
entry. That process is described in an example here:

http://support.microsoft.com/kb/237556/en-us

If the computer was using a HAL of "Standard PC", you'd be in a real
mess. If, on the other hand, you're at "ACPI Uniprocessor PC", it
is going to be five minutes work to update the driver so that it
reads "ACPI Multiprocessor PC". Once you reboot, Task Manager should
start to show all your cores.

In the BIOS, there has to be support for ACPI. Occasionally, a bad
BIOS design will upset the repair install you are doing, and
bugger up the HAL entry. You have to make sure, that all the necessary
features have been turned on in the BIOS, before doing the repair
install. Otherwise, you'll need to fix Suspend To RAM with
programs like Microsoft's "dumppo", and mess around with
HAL changes and the like.

HTH,
Paul





.

Relevant Pages

  • Re: I need Help. "No Safe Mode" and...? Possibly an opportunity to recover.
    ... "For someone who knows what they're doing, changing the bios to boot from ... but clear instructions are in the MSKB or link I give them ... Also having experienced the boot to windows problem early on as a beginner, ... Anyone can think of dozens of hardware related reasons why someone can't get ...
    (microsoft.public.windowsxp.basics)
  • Re: CD-ROM & Floppy Drives Dont Work
    ... many things that could well have been done to a W98 [any ... W98 Windows Explorer in either ... Find out if the 6 year old knows how to get into the BIOS, ... See if it will boot from the CD. ...
    (microsoft.public.windowsxp.hardware)
  • Re: more blue screen misery
    ... Bios doesnt seem to indicate any problems. ... Safemode stops after this driver is shown on the screen -- AGP440.sys ... A description of the Safe Mode Boot options in Windows XP ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: more blue screen misery
    ... Have you looked in the BIOS? ... Safemode stops after this driver is shown on the screen -- AGP440.sys ... A description of the Safe Mode Boot options in Windows XP ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: I need Help. "No Safe Mode" and...? Possibly an opportunity to recover.
    ... > from CD or running a repair install of WIndows is not a big effort.For ... > the MSKB or link I give them every single time I mention going into bios ... > 5) I can think of dozens of reasons why a computer might not get all the ... I was responding originally to your comment that: ...
    (microsoft.public.windowsxp.basics)