Lakario
09-16-05, 07:14 AM
I need some guidance on a serious problem that arose today. I was switching motherboards so that I could send my main one away for RMA and after moving everything I attempted to boot, but I was greeted with a "PROCESS1_INITIALIZATION_FAILED" BSOD as soon as Windows finished loading. I proceeded to revert back to my old motherboard and low and behold I am still getting this stop error. I attempted to reinstall XP and this error came up again, so I went into the recovery console and ran chkdsk on my main drive and tried again- no dice. I then proceeded to run a FIXMBR on the recovery console which seems to have orphaned almost all of the files on one of my partitions. I then installed a backup HDD, and ran a fresh XP install on that drive. As soon as the installation began XP went ahead and tried fixing all the orphaned file links for me (110gb) and then installed Windows.
After I got XP installed on this backup drive I went to examine the file structure on the damaged partition and although every file is there, the majority of them do not work. So I am left with two problems, firstly I cannot boot off my main system drive without encountering PROCESS1_INITIALIZATION_FAILED and secondly, almost all the files on one of my drives do not work anymore. I am not sure what to do and this is driving me crazy, if anyone could offer some info on where to go with this I would be eternally grateful. I would like to <b>avoid</b> formatting my main drive at all costs, so if there is <i>anything</i> I can do, please tell me.
<u>Details of the BSOD:</u>
PROCESS1_INITIALIZATION_FAILED
***STOP: 0x0000006B (0xC000007A, 0x00000008, 0x0000000, 0x00000000)
Note for you google fiends: I am not running GoBack on my machine.
<u>Details regarding orphaned files:</u>
Basically, everytime I try to open the majority of the files on the orphaned drive they fail to execute. If it is an archive it will report as corrupted and if it is an executable a command line window pops open saying, "Program is too big to fit in memory." All the file sizes are still correct, but most everything will not run. I have run a chkdsk on the orphaned partition fruitlessly, but I do not yet wish to run a defrag because I am afraid that moving the files may lose them permanently. I ran a utility called Active Undelete to attempt to recover some of the orphaned files, however, the recovered files were also inoperable. Please help. :(
Update: I am currently running a low-level sector-by-sector scan on my drive to see if I can recover the orphaned files, but I am still not very hopeful.
After I got XP installed on this backup drive I went to examine the file structure on the damaged partition and although every file is there, the majority of them do not work. So I am left with two problems, firstly I cannot boot off my main system drive without encountering PROCESS1_INITIALIZATION_FAILED and secondly, almost all the files on one of my drives do not work anymore. I am not sure what to do and this is driving me crazy, if anyone could offer some info on where to go with this I would be eternally grateful. I would like to <b>avoid</b> formatting my main drive at all costs, so if there is <i>anything</i> I can do, please tell me.
<u>Details of the BSOD:</u>
PROCESS1_INITIALIZATION_FAILED
***STOP: 0x0000006B (0xC000007A, 0x00000008, 0x0000000, 0x00000000)
Note for you google fiends: I am not running GoBack on my machine.
<u>Details regarding orphaned files:</u>
Basically, everytime I try to open the majority of the files on the orphaned drive they fail to execute. If it is an archive it will report as corrupted and if it is an executable a command line window pops open saying, "Program is too big to fit in memory." All the file sizes are still correct, but most everything will not run. I have run a chkdsk on the orphaned partition fruitlessly, but I do not yet wish to run a defrag because I am afraid that moving the files may lose them permanently. I ran a utility called Active Undelete to attempt to recover some of the orphaned files, however, the recovered files were also inoperable. Please help. :(
Update: I am currently running a low-level sector-by-sector scan on my drive to see if I can recover the orphaned files, but I am still not very hopeful.