PROCESS1_INITIALIZATION_ERROR 0x000000b6

milindsmart · 10 Feb 2014

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 · 10 Feb 2014

milindsmart said:

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

Where?

Attach it in your next post.

milindsmart · 10 Feb 2014

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

Attachment 305795

milindsmart · 17 Feb 2014

Arc said:

milindsmart said:

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

Where?

Attach it in your next post.

Any updates, Arc?

NoelDP · 17 Feb 2014

You have some MAJOR problems!

Just looking at the last POQ was enough...

Code:

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)
000021de@2013/11/20:22:49:07.765 (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 · 17 Feb 2014

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 · 17 Feb 2014

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 · 17 Feb 2014

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 · 17 Feb 2014

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 · 11 Mar 2014

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?