Solved PROCESS1_INITIALIZATION_ERROR 0x000000b6

[milindsmart]

Start with the checklist for http://www.sevenforums.com/tutorials/219533-troubleshooting-windows-7-failure-boot.html which we've not heard back on yet.

I actually have run most of the steps in the troubleshooting guide, but hadn't put them in a single place, which I have now done, check my previous post.

Why are you off running third-rate repairs when there are a whole list of extant steps you've yet to report back upon given to you by the top tech forums on the web, where most of the repair protocols for Win7 were developed during beta?

I copied the original Ntdll.dll from the original Windows 7 SP1 MSDN ISO directly from DigitalRiver, into the Windows\System32\ directory where it WASN'T PRESENT at all. With respect, Greg, could it have damaged the OS just to have restored an important system file?

Have you tried System Restore to the oldest restore point from the disk?

As I have mentioned in the previous post, there are NO system restore points. If there were, it might have saved the day.

Your Disk Management is atrocious and evinces a way of doing things that will only lead to these problems again and again.

Yeah, I thought allocating different partitions for different purposes was a good way of doing organizing disks, and I won't be doing so the next time. It is not ideal, I agree, but is it unstable/ugly in any real way?

 

[gregrocker]

CCleaner does not wipe out System Restore points unless you specifically tell it to.

Did you try adding Win7 to boot from Windows 8 using EasyBCD as I suggested earlier, since you didn't reply?

Did you try all of the other boot repairs I suggested earlier throughout this thread?

Have you checked all of the causes of the crash parameters which Archie posted?

 

[Arc]

CCleaner wipes restore points, if it is asked to do so.

View attachment 299600

But it does never touch the latest one. It is out of access all the times. So, at least one restore point must be there.

Greg, I simply wonder why the OP is not doing what is needed and doing what is not needed and making the situation worse.

 

[milindsmart]

CCleaner does not wipe out System Restore points unless you specifically tell it to.

Did you try adding Win7 to boot from Windows 8 using EasyBCD as I suggested earlier, since you didn't reply?

Did you try all of the other boot repairs I suggested earlier throughout this thread?

Have you checked all of the causes of the crash parameters which Archie posted?

Ah, then it's definitely not CCleaner. I wonder what it is. I would have only disabled system restore if there was an extreme crunch in space and I needed something extremely urgently. Both of which haven't happened. No idea how they all got wiped

Yes I added Win7 to the Windows 8 BCD, it successfully starts the animation, and BSODs at the same point. Had replied in my reply to your first post on this thread.

Others : Changing active driver letter, copying boot files to C drive - tried, no difference. Virus scan by F-Secure - clean.

Stop STOP 0x0000006B: PROCESS1_INITIALIZATION_FAILED
Usual causes: Hard drive, Cables, Missing boot files, Disabled driver

The first parameter is 0xC000007A. Which is the NTSTATUS.
STATUS_PROCEDURE_NOT_FOUND: Indicates the specified procedure address cannot be found in the DLL.

...

Ran seatools short tests, they're all good. Seems like pure OS file corruption.

 

[gregrocker]

Copying boot files is not enough, it must be followed by marking Active and running Startup Repairs.

I would not waste any more time but browse in to back up your files and everything else needed from the preparatory steps of Clean Reinstall - Factory OEM Windows 7 then follow the rest of those steps to get and keep a perfect install.

 

[milindsmart]

I think I'm being read wrong... I have executed all the fixes suggested in this entire thread. I have uploaded logs wherever I could get my hands on them.

Greg, please at least list the problems with my disk management... I've been wondering all this time what the problem is, minus Programs partition for windows 8 which is merely a chosen location for Programs, not by applying any hacks. Anyway, windows 7 has been installed in the bog standard manner.

Arc, I don't normally run off and install the first thing I get. But except SFC, all the other steps have shown that the problem does not lie in hardware or BCD related settings. Only thing other than some form of corruption is a bootkit as you said, which I am wondering how to check. F-Secure did not mention any bootkit-checks. Should I use AVG?

The problem definitely not common. Startup repair should have worked well, like this one.

Once repeated applications of Startup repair and SFC fail, I already know that this isn't going to be simple. Putting individual system files into a directory does not result in a stable system, I know. My idea is definitely to run a repair install once I can boot.

So please tell me why it appears like I'm not taking advice.

 

[gregrocker]

Just back up your data from Win7 and the adjacent Primary, power down to unplug the WIn8 HD, boot into WIn7 installer, use the Drive Options in Steps 7 and 8 of Clean Install Windows 7 to delete the Primary partitions, create a new OS partiiton in the space. It will issue a System Reserved partition.

If you wanted to be cleaner, back up all of your data, delete all partitions, then create a new Win7 and data partition for storage or even to link to your User folder libraries so you can keep the image backup smaller with just the OS and programs.

I think where you went wrong is deleting the system Reserved partition. Sometimes its not possible to move the System boot files to C so its best to keep SysRserved until you mark C Active and run the Repairs and it starts up marked System. Then you can delete SysReserved since you know it wont' be needed. I try to follow that principle always so that if C won't take up the boot you can go back. Sometimes these things remain mysteries.

What isn't a mystery are tens of thousands of perfect installs out there for those who stick with the steps, tools and methods in Clean Reinstall - Factory OEM Windows 7
which compile everything that works best, and is the same for retail.

 

[milindsmart]

Oh and Happy New Year, to you Greg, Arc and to sevenforums at large

 

[gregrocker]

And to you. Wish we had better news. But we are glad to help and will stick with you until you get it the way you want.

 

[milindsmart]

Thanks. And aah... I give up trying to resuscitate this system. I kinda know the reason why it's messed beyond repair :
Some time ago this installation changed its drive letter to T:. According to various places, including this forum, I left it alone as long as it was working. Now when I regenerated the boot files, somehow it got the sense to call itself C:. But when SFC checks files, it encounters a bad mixture of C:\ and T:\ hardlinks. No wonder it gives more than 10k entries in the CBS log file. Literally everything is an integrity violation.

So I'll sit today or tomorrow and do a clean reinstall.

About the disk partitioning, why is it better to have one big data partition rather than many small ones, like in my Disk 1?

 

[milindsmart]

Ok I was occupied with some other things, and the other windows was working fine, so this fell lower on the priority list. Meanwhile, I also learned a lot about booting, and with no real need to hurry up about that installation, am even more keen to force it to work.. so I'm back to haunt you guys

Specifically, can anyone analyze my SFC logs? They're attached here. They contain a lot of nonfile entries... like one named 016dd2fdac3816d0990ef71a86b49ca5 ... version 6.1.7601.17933 ... What are they actually?

My reasoning is, there's one way for it to be (essentially) unsalvageable : extensive file corruption... So I just want to prove that all these files are actually corrupt.

 

[Arc]

Specifically, can anyone analyze my SFC logs? They're attached here.

Where?

Attach it in your next post.

 

[milindsmart]

Sorry, thought it linked back to the other post of mine that had this attached....

View attachment 305795

 

[milindsmart]

Specifically, can anyone analyze my SFC logs? They're attached here.

Where?

Attach it in your next post.

Any updates, Arc?

 

[NoelDP]

You have some MAJOR problems!

Just looking at the last POQ was enough...

POQ 2008 ends.
000021da [SR] Repair complete
000021db [SR] Verifying 1 components
000021dc [SR] Beginning Verify and Repair transaction
000021dd (F) STATUS_OBJECT_NAME_NOT_FOUND #1145286# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES), oa = @0x17dc70->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[122]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-d..frameworks-usermode_31bf3856ad364e35_6.1.7601.17803_none_fb416b4f0bdbe260"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0x17dd60, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
[EMAIL="000021de@2013/11/20:22:49:07.765"]000021de@2013/11/20:22:49:07.765[/EMAIL] (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(2057): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
000021df (F) STATUS_OBJECT_NAME_NOT_FOUND #1145285# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingDirectory(...)
000021e0 (F) STATUS_OBJECT_NAME_NOT_FOUND #1145284# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingDirectory(flags = 0, da = (SYNCHRONIZE), oa = @0x17e678->SIL_OBJECT_ATTRIBUTES {s:40; on:"amd64_microsoft-windows-d..frameworks-usermode_31bf3856ad364e35_6.1.7601.17803_none_fb416b4f0bdbe260"; a:(OBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|FILE_OPEN_FOR_BACKUP_INTENT), dir = NULL, disp = Invalid)

Most normal x64 systems have around 120-150 POQ sections - your managed to get to 2008 before being crashed by a registry error.

It looks to me like a complete folder of components is missing.

I can only suggest a repair install.

 

[milindsmart]

Wow so 2008 POQs isn't normal... I found the log absurdly long, but didn't know if that would be the case with any SFC run on any machine.

How would this have happened? Some wrong addressing followed by writing in the wrong location perhaps?

Nevertheless, how would I do a repair install without being able to boot into windows?

Thanks for the analysis. Can you tell me some more about what might have gone wrong, just for my reference?

 

[NoelDP]

I've never seen a POQ higher than 300 before - it means that SFC is attempting to repair each component individually.

Sorry, I was asked to read the SFC, rather than the thread, so that's what I did
If you can't boot the system as it stands (even in Safe Mode?) then there's not a lot you can do except a clean/custom install. I really don't see me being able to fix that number of errors this side of Christmas ;(

You need to check the HDD (if you haven't already) before attempting anything.

As far as what went wrong is concerned, I'm tempted to accuse you of use of a Registry Cleaner - but it could be simply a wrong-time/wrong-place kind of thing, and a power failure messed with everything.

I assume that you've attempted System Restore back to when you had a functional system?

 

[milindsmart]

No safe mode... System restore mysteriously shows no restore points at all.

Whoa christmas.. I thought it should take a day or two... I guess I'll settle with reinstalling, nothing is worth so much of anyone's time.

HDD checked, no problems.
Uh... maybe I did run a registry cleaner sometime before it went belly up... CCleaner is safe right? Of course, it's definitely got something to do with this other disk on which I installed windows 8. In fact they coexisted for only 1-2 days. And who knows what else....

 

[gregrocker]

Be sure to unplug all other HD's during the reinstall, from the booted Win7 installer System Recovery Options
Command line run Diskpart Clean Command to clear old boot code and the partition table.

Then if you'll stick closely to these same steps as for a Clean Reinstall - Factory OEM Windows 7
you'll get and keep a perfect install. Pay particular attention to how drivers are best handled in Win7 since some go wrong trying to apply XPired methods there. The tools and methods which work best are compiled in the tutorial based on what works best in tens of thousands of installs we've helped with here.

 

[milindsmart]

Alright it's done, I installed a fresh copy of windows 7. Along with IE 11, it's so blazing fast I doubt I'll even install chrome now. Thanks Greg, Arc, and Noel.

I have created a disk image backup, as well as user folder backup. Is it incremental? If not, what incremental backup options are there built into windows, or using MS tools?