sql 2005 installation fails

Hi all,
Just tried to install sql 2005 on a 12 core amd opteron 2431 machine with 4 gb ram.
Setup failes with the following eventlog entry while installing db service
Description:
Application popup: sqlservr.exe - Application Error : The instruction at "0x02019027" referenced memory at "0x00000182". The memory could not be "read".
Already tried to disable one processor (6 cores) in bios and using single core processor driver, both did not help.
Any help is highly appreciated!
TIA
acki4711

I do understand that the issue you are having relates to a Micrsoft bug that causes SQL 2005 to fail when the number of cores in a processor is not a power of two. This means that your current 6 core processors are not usable without operating a clunky and unacceptable workaround from Microsoft.For reference here is the details of the Microsoft bug http://support.microsoft.com/kb/954835/en-us
Hope this helps, Dave.

@Dave,
I have a 2 proc. machine with 6 cores on each processor. With one or two processors activated it's always a power of two (6/12).
But even if I install single proc. HAL setup fails.
@Satya
Have 32 GB of RAM, tried on 2 different (with equal hw layout) servers so the memory is not the case
Please advice
acki4711

6 is not a power of 2. Do the math. Powers of 2 are 2, 4, 8, 16,.... etc.
I believe dave.robinson is correct. Read his post again and follow the link he posted.
Your 6 cores will be a problem if you do not use one of the workarounds suggested in the hyperlink posted by Dave above.

I agree with Dave & David...
It seems to be the same issue as suggested by Dave.
The best thing will be to try the workarounds as suggested in the link and let all of us know if it fixes the issue.
Cheers...!!!!

I do agree with all above comments about the failed of sql installation. I would like to suggest check out security of your system.some times antivirus didn't allow installation due to the presence of some malwares.

To be fair, powers of 2 are *1*, 2, 4, 8, 16 ... etc.

have a look : http://social.technet.microsoft.com/Forums/ja-JP/sqlsetupandupgrade/thread/cc82ee25-c867-4538-ba98-e9ea91aa7632
The method 2 of article link by Dave has resolved the problem