Installation Problem

[Gary]

I'm performing a clean installation of Windows XP Home
Edition on a Soyo KD400 Ultra Platinum mother board with
an AMD Athlon XP 2800+ processor, Western Digital 120 MB
Ultra ATA 100 hard drive, two Kingston KVR333/512 memory
modules and a Radeon 7500 AGP 4X Video card.

The drive is partitioned into 2 60mb partitions and
formatted for NTFS.

The OS installation copied files to the drive and then
rebooted to the Windows installation screen. A couple of
minuts after reboot the system returned toe following
error:

"Setup failed to install the product catalogs, this is a
fatal error."

"Setup could not register the OLE control
c:\windows\system 32\initpkidll because of the following
error"

"DLLregisterserver returned error 3221225477 (CD000005)"

"The signature for Windows XP Home Edition setup is
invalid error code is 800b0001 Unknown trust provider"

Does anyone have a solution?

 

[Michael McCartney [MSFT]]

The most common causes of this problem are the following:
Damaged drive partitions
damaged installation cd
bad hardware or out of date/misconfigured system bios.

Granted, this is a bit open ended so I will try to narrow down a few
prospects and a course of action going forward.

If you suspect damaged drive partitions repartition the drive so that the
install directory is 8gig or less and try it again. If that succeeds then
its hitting a drive translation problem. Make certain you have the right
cabling for the drives and that they are jumpered correctly. Also, do not
use any third party partitioning programs but let the installation process
create the partitions on the drive.

If you suspect a damaged installation cd take the cd to a known working
system and drag and drop its entire contents onto a temporary directory on
the hard drive. If it gives you file copy errors then you know its a bad cd.

Bad hardware ...well, no way to narrow that down easily. Usually, if the
drive is ok and the media is ok then suspect bad memory (this is because of
memory mapped io failure). Remove half of the memory and try the install.
If that fails then switch it with the other half. It would be VERY wierd
for all ram to be bad.

If you suspect a bad bios and there are no bios updates then try forcing a
standard hal
(http://support.microsoft.com/default.aspx?scid=kb;en-us;216251). If doing
this works then there is some problem in either the acpi table structure of
the bios you are using or errors in irq routing/steering tables. Work with
the motherboard manufacter on that one.

 

[Gary]

Michael, Thank-you for yor prompt response. Following my
initial posting I tried repartitioning and reformatting
the drive and reinstalling Windows XP and received the
following error messages:

"A problem has been detected. Windows has been shut down
to prevent damage to your system''

The problem seems to be caused by the following file
KsecDD.sys.

Restart computer. If screen appears again follow the
steps below.

Make sure hardware is properly installed
Disable memory options such as caching or shadowing

Tech information:
Stop 0X000000050 (0XF7A3E9F8, 0X00000000, 0XF77A159C,
0X00000000)

KsecDD.sys address F77A159C base at F7799000

Date Stamp 3b7d8379"

Since then I have reformatted and rinstalled several times
with the errors toggling between the above errors and
errors described in my initial posting.

I've tried the following:

Updated BIOS to Soyo's latest for this mother board.
Following that I repartitioned and reinstalled the OS with
the same results.

Removed one memory module and tried reinstalling the OS
with no change. Removed that module and replaced it with
the second module. With that module I got the following
error:

"Page Fault in nonpaged area Stop 0x00000050 (0xE146F258,
0x00000000, 0xBF86DC9E, 0x00000000. The rest of the
errors were similar to those specified above except that
win32k.sys was identified as the problem file at address
BF86DC9E Base at BF800000, Datestamp 3d6e5e5. This is the
first and onle time win32k.sys appeard in the error
messages. Other than this once they have been
consistently those described above or from my initial
posting.

I ran Western Digital's diagnostics on the drive which
detected no problems. I am using the cable supplied with
the drive which is an 80 conductor cable for the UDMA
drives. I have also tried another cable that is supposed
to be UDMA 100 compliant. Tried jumpering the drive for
cable select and as a master with no slave.

Tried loading from another Windows XP disk that I have
used successfully in the past, no luck here.

Used the BIOS failsafe settings to no avail.

Repartitioned the hard drive for 8 gig and reinstalled the
OS with no change in errors.

Tried forcing the standard HAL as you sggested. The only
selection available was "Standard PC with C-Step i486.
The OS would not install with that configuration either.

I've been through the BIOS setup and nothing jumps out at
me as odd for any of the settings, but that doesn't mean I
haven't overlooked something.

 

[Michael McCartney [MSFT]]

When you force the hal the list starts at the bottom (wierd, its always
been that way though) you need to page up until you get to the one that
just says "standard hal".

Really sounds like bad memory. Does this board use Rambus memory? Because
Rambus works in pairs and must be terminated (if all slots are not full) it
is incredibly hard to troubleshoot it. Right now the whole scenario REALLY,
REALLY sounds like bad memory.

 

[Gary.]

Thanks for the additional information. I'll give HAL
another try. The board uses DDR memory. The Kingston
KVR333/512 is one of the memory modules listed by Soyo as
compatible with the board but maybe there is an issue with
the modules I have. I'll pick up another memory module
(different manufacturer)and try that to see what happens.

 

[Gary]

Checked the HAL list again and found the Standard PC.
Tried that with no luck. I tried reformatting the drive
in FAT 32 and loading XP to no avail. Tried FAT 32 with
Standard HAL and it loaded. Tried reformating to NTFS and
Standard HAL but XP would not load. Tried FAT 32 and
standard HAL again but XP wouldn't load.

 

[George Ellis]

For a memory issue, you can try running the MS diagnostic.

http://oca.microsoft.com/en/windiag.asp