Process1_Initialization_Failed Windows XP Setup

[SLCentral]

Hey guys,

I'm building a new system, and I'm using a Seagate 80GB 7200RPM SATA hard drive in it, with my onboard SATA controller. The computer does recognize the drive with no problem (as does fdisk), but when Windows Setup loads, I get a BSOD saying Process1_Initialization_Failed, and I have to restart. Therefore, I can't format the drive or get into the Recovery Console. I formatted the drive with Fdisk using a 98 boot disk (floppy), and that did no good either. I'm stuck.

 

[MrChad]

Did you load your SATA controller drivers when XP setup first started (Press F6 to load third-party drivers...)?

 

[SLCentral]

No, I didn't. Would not loading htem give that error? Last time I didn't load them and I get in setup, no hard drives were found.

 

[Nothinman]

I would run memtest and verify the hardware is good, even if the drive isn't seen you shouldn't get that process initilization error.

 

[SLCentral]

Weird, I took out the hard drive, and I loaded up Windows, and the same thing happened. I tried the system with each stick of RAM only (there are two 256MB sticks) to see if one stick is bad, but the problem happened still. Memtest is running now, but I'm not sure what the problem is here, its strange considering they are all new parts (with the expcetion of the RAM, HDD, and CD-ROM Drive), and this same problem happened with my previous Shuttle system (that used the same CD-ROM drive, RAM, and Hard Drive).

 

[SLCentral]

Memtest found nothing, this is so weird...could it be my XP CD or no?

 

[tennesota]

Any luck Dan?

 

[SLCentral]

No . I don't know whats going on, even if the HDD isn't even in the system, it still gives me the error, so I'm thinking the RAM, but its a big coincidence that both sticks don't work...I'll pull some from my G5 and test it in this computer, hopefully that'll work :-\.

 

[NogginBoink]

-from the recovery console run chkdsk on the c:\ drive (with /p switch)
-ensure smss.exe is in the system32 folder

 

[SLCentral]

Originally posted by: NogginBoink
-from the recovery console run chkdsk on the c:\ drive (with /p switch)
-ensure smss.exe is in the system32 folder

The problem is that I can't even get into the Windows Setup (when it Says Starting Windows on the blue bar in the Setup screen in DOS, it just gives me the BSOD), so I can't get to the recovery console. And since Windows isn't even installed, the smss.exe isn't going to be there, also considering the HD hasn't been partitioned yet.

 

[Sianath]

Hardware troubleshooting sucks

 

[SLCentral]

God yeah . Any ideas before I pull the RAM and try another stick?

 

[tennesota]

Can you try a different CDROM drive?

 

[SLCentral]

Just tried another CD-ROM drive, no luck .

 

[XBoxLPU]

http://www.osr.com/ddk/ddtools/bccodes_8gfb.htm

STOP 0x0000006B Process1_Initialization_Failed
Applies To
This article was previously published under Q163240
SYMPTOMS
When it restarts, a computer running Windows NT may get the following Blue Screen STOP message:

Stop 0x0000006B (0xC0000034, 0x00000002, 0x00000000, 0x00000000)
Process1_Inialization_Failed.
CPUID : Genuine Intel IRQL:0 SYSVER 0xF0000xxx
The first parameter in the STOP code, 0XC0000034, means:

STATUS_OBJECT_NAME_NOT_FOUND

Object name not found.
CAUSE
This error is caused by a missing system file (usually Ntdll.dll in the %systemRoot%\system32 directory.
RESOLUTION
To resolve the problem, do either of the following:
If Windows NT is installed on a FAT partition, start the computer into MS-DOS and copy the Ntdll.dll from the Windows NT compact disc.
If Windows NT is installed on an NTFS partition, you can do either of the following:
Perform a parallel installation and copy the Ntdll.dll file from the Windows NT compact disc.

-or-
Restart your computer with the three Windows NT Setup disks.

NOTE: To perform a system repair, you must copy a fixed version of the Setupdd.sys file from Windows NT 4.0 Service Pack 2 or later to setup disk two.
Select "R" to repair your Windows NT installation.
Select only Verify Windows NT System Files and then continue.
After you replace the Ntdll.dll file with the a copy from the Windows NT compact disc, press F3 to exit Repair. Restart the computer and also restart Windows NT.

NOTE: If the Ntdll.dll file was corrupted due to a bad block, you must rename the file before copying the new version of the file.
If the restart results in the same error, repeat the above procedure, but repair ALL files when asked during the repair process.

http://www.computing.net/windowsnt/wwwboard/forum/21584.html

hmm

 

[tennesota]

I wish I could you help you out. I have the same mobo that I plan to use for a new build but I currently do not have a processor for it. I might have the processor by next weekend but I will be out of town for about 10 days so I will not get to use it until I get back into town. I currently plan to use PATA drives in my new setup; I have never tried SATA drives.

 

[SLCentral]

I've been researching the problem, and it has something to do with the file system of the drive (FAT or NTFS). Since this drive was pulled from my G5, I am guessing that there is some hidden partition that Apple put on the drive that I am not sure about, and although I've tried formatting multiple times, I'm not really sure if that got rid of the partition. Maybe I should put the drive back in my G5 and format it there?

 

[tennesota]

What brand of drive? If it were my drive I would use the drive manufacturers set of utilities to 'write zeroes' to the drive. With a drive that size it would take several hours but IMHO it would be well worth it.

 

[SLCentral]

It is a Seagate. Where can I find that software?

 

[farscape]

Had a prob a little while back when installing XP. Had to go into BIOS and set it for default setup. Installed fine after that. Then went back and set BIOS for how I wanted it.

 

[SLCentral]

Put in a Hitatchi ATA HDD, NEW, and it still gives me the error...:-\.

 

[SLCentral]

Anyone have any ideas?

 

[SLCentral]

Just put in new RAM, still doesnt work . Reset the BIOS with the jumper and the battery, still doesn't work. I'm stuck. I have the feeling a boot record being stored somehow in the computer is screwing it up, but I'm not sure.

 

[Sianath]

If you tried setup on a brand new Hitachi drive and got the same error, it can't be caused by anything on the disk itself. The same problem with two separate physical disks eliminates the disk itself as cause (unless there is something in common about the disks - i.e. both from the same machine originally, formatted with some piece of software pre-installation, etc).

Now, that isn't to say the problem couldn't be in the disk controller, or something like that. I'll dig a little for you when I get back to work and see what I can find.

 

[SLCentral]

The Hitachi drive is brand new, but what really gets by me is how the same error could happen on my old Shuttle XPC too. I could understand the error being repeated if I used ths same motherboard, but this is an entirely new mobo, so what else could it possibly be? it doesn't add up.