Unsolved

This post is more than 5 years old

Closed

2 Intern

 • 

1.3K Posts

27515

July 16th, 2007 18:00

D620 - Not utilizing both cores???

I recently was "upgraded" to a D620 (from D600) at work, but the D620 runs like a one legged dog. Now, the D620 came with a hard drive encryption program called PointSec, but my other work laptop, a D610, also has PointSec and the performance impact was neglible.

My theory is that the new D620 is not utilizing both cores on the processor as Task Manager is showing only one CPU graph (instead of two). My XPS720 shows four graphs (quad core), my wife's Core Duo E1705 shows two graphs... but not the D620. I personally think the reason for this is because the IT person that setup the system used the wrong hard drive image. I found shortcuts to hardware utilities for hardware that doesn't exist (for example, shortcuts to the Intel Wireless client, despite the system having a Dell wireless card).

I've done some digging around and it seems Microsoft released a patch for multi-core processors (KB896256) which I have installed to no avail. It seems XP may have different version of the ntoskrnl.exe and hal.dll files for single and dual core processors; if the hard drive image used for my machine had the single core versions... sigh....

I get the feeling I am out of luck since I personally cannot reformat and reinstall XP on the machine. Here's what I've tried so far... if anyone has any suggestions beyond what I list, let me know.

- Ensured Dual Core Support enabled in BIOS
- Installed KB896256 Patch
- Registry Tweak related to KB896256 Patch
- Installed Dell NSS
- Re-installed Intel Chipset Drivers

11 Legend

 • 

87.5K Posts

 • 

321.3K Points

July 16th, 2007 18:00

You are correct that the HAL is different. Here's some information that may help:

http://www.myitforum.com/articles/15/view.asp?id=8997

2 Intern

 • 

1.3K Posts

July 16th, 2007 18:00

Thanks ejn63. Under the Device Manager the computer is listed as "Advanced Configuration and Power Interface (ACPI) PC" and under the details, the hardware details shows ACPIPIC_UP.
 
If I read the information in the link you provided correctly, it seems I am stuck with that HAL unless the system has windows reinstalled. Sigh... and IT departments wonder why people don't like them.
 
Thanks again,
-Cade

120 Posts

July 17th, 2007 12:00

I hate stating the obvious, but are you sure it's a dual core cpu? The 620's came in both flavors. If it is a dual core cpu you can change it in Device Manager. Update driver, Don't Search I will choose, ACPI Multiprocessor, done! You do not have to reinstall Windows. You might ask your IT dept if it's okay as they may have a reason for not enabling dual core CPU's (application problems, etc.).
 
Good luck,
Thom

2 Intern

 • 

1.3K Posts

July 17th, 2007 15:00

tsharar -- No problem... the obvious is often not so obvious. I'm fairly confident it's a dual core: ;-)
 
 
I tried to manually change the 'driver' but Windows does not give me the option for the ACPI Multiprocessor. Even unchecking the option 'Show compatiable hardware' still does not yield any options other than what is already installed (Advanced Configuration and Power Interface (ACPI) PC" and "Standard PC."

120 Posts

July 17th, 2007 15:00

You're right, it's a dual core. What's strange is the way the PC is listed. It should be ACPI Uniprocessor PC & give you the option to change it. Do you know if you have full Admin rights to the local PC? Sounds like they may have these locked down pretty tight, but I would definitely get with the IT folks to see what gives. No much sense in limiting it like that.
 
Thom

2 Intern

 • 

1.3K Posts

July 17th, 2007 16:00

My user was a member of the local computer Admin group. I suspect that whoever setup the machine used an image that had not been properly configured. They recently rolled out about 130 D620s in my department and at least 7 of my immediate co-workers all have the exact same issue as I do. Someone made a big mistake... but more than likely, the IT guys don't care. It seems like a format/reinstall or re-image with a properly configured image is what it takes to solve this problem. Something tells me they won't touch re-imaging 130 machines with a 10' pole...   
No Events found!

Top