• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Hyperthreading help

yertleq

Junior Member
Question: Does the memory need to be Dual channel in order for hyperthreading to work?

I have a new asrock 775v88, and a Intel 630 3.0Ghz, running XP Pro and can't figure out how to get the hyperthreading to work.

I do know the hyperthreading option is set to auto in the BIOS.
 
Well it sounds like it's turned on in the BIOS already. How do you know it's not working? Is this a new build?? The ram doesn't need to be in dual channel for hyperthreading to work, however your perfromance will suffer greatly if you aren't running dual channel.
 
Go to device manager, and click the plus where it says computer. Does it say APCI multi-proccessor PC? If it does, go to task manager, click on view, cpu history, and select show one graph per CPU. Did you do a fresh install of windows, or did you use a hard drive that already had windows on it?
 
Again, and read carefully 😉 in device manager, IT IS NOT HYPERTHREADING, it is standard PC, I even gave you the link to the microsoft article, so I do know how to tell if it is hyperthreading. As to your question about the about the hard drive, yes it was a fresh install, I got a new SATA drive, and it runs this way with the SATA drive by itself, or with the IDE drives plugged in too.

And to answer Blain, yes I did say I know that hyperthreading is enabled in the BIOS, and that article is one I had looked at, although I am not yet ready to begin overclocking, I just want to make sure the CPU and MB are working correctly first.
 
Did you flash the bios to the latest version?
If you did, did you clear the CMOS and redo your settings?
Often the bios doesn't function properly until this is done, though it appears to be correct...
 
Originally posted by: yertleq
Again, and read carefully 😉 in device manager, IT IS NOT HYPERTHREADING, it is standard PC, I even gave you the link to the microsoft article, so I do know how to tell if it is hyperthreading. As to your question about the about the hard drive, yes it was a fresh install, I got a new SATA drive, and it runs this way with the SATA drive by itself, or with the IDE drives plugged in too.

And to answer Blain, yes I did say I know that hyperthreading is enabled in the BIOS, and that article is one I had looked at, although I am not yet ready to begin overclocking, I just want to make sure the CPU and MB are working correctly first.

You said it didn't show 2 proccessors in device manager, you didn't specify that it said standard PC, either hyperthreading was not enabled when you installed windows, or it's not working properly and a bios update may be neccessary. And AUTO does not neccesarrily mean it will be enabled..
 
Originally posted by: yertleq
It does not show in device manager as 2 processors per This Link, nor in the performance tab of the task manager.

And yes, it is a new build

I said per the link, which DOES say standard PC.

And to Blain again, I also said the perfomance tab of task manager does not show 2.

I will check for a BIOS update...
 
No, the only options are Auto, and Disable.

I have figured it out from one of stevty's comments about the windows installation.

While I was doing the install, I was origionally having problems with the setup hanging at the "starting up windows" point. See this article 310760, so I attempted to select a different HAL, see this article 216251.

I clearly chose the wrong HAL, but 2 questions now are 1) can I fix it without reinstalling, and 2) what would be the correct HAL?
 
Follow up:

The BIOS update made the windows install run fine with ACPI as it defaults, so I didn't even try to choose a different HAL. Sorry I put this in a hardware thread when it turned out to be a OS issue.
 
Back
Top