Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: PROCESS1_INITIALIZATION_ERROR 0x000000b6

22 Nov 2013   #11
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Quote   Quote: Originally Posted by milindsmart View Post
Are you sure that Windows will not boot into IDE when AHCI was used to install it? I recall being able to switch freely and feel the significant difference in speed.
Almost. It does not.

Quote   Quote: Originally Posted by milindsmart View Post
Marking C as active now, after switching to the 100MB system partition, I don't know, but I think there will be absolutely no change. I have been debugging bcd and bootmgr related issues for a while now, and BSODs aren't a part of it... at that level, things fail much more clearly

Any chance with analyzing the SFC logs?
One try is worthy. But, you have to set the storage controllers to its original mode, and the windows 8 HDD should not be connected while running startup repair.
There should be only one active partition in the entire system.


My System SpecsSystem Spec
.
23 Nov 2013   #12
milindsmart

Windows 7 Home Premium x64
 
 

Windows defender offline does not run. I tried both with a USB stick, as well as a DVD.

It shows the error : "The app can't be started.

Error: Unable to detect a Windows system drive. This could be due to missing drivers, an encrypted drive, or a corrupted Windows installation.
Error code: 0x8004cc01"

Have seen a few questions on Microsoft answers, but no real remedies for this one. Does this really indicate a problem?

As I expected, no change when I move active drive to the windows drive.
My System SpecsSystem Spec
25 Nov 2013   #13
milindsmart

Windows 7 Home Premium x64
 
 

Any ideas? I really don't mind laboriously setting things right, don't want to reinstall.
My System SpecsSystem Spec
.

25 Nov 2013   #14
gregrocker

 

If you are following Troubleshooting Windows 7 Failure to Start then you'd have seen that there are other bootable AV's provided, as well as a step to change the Active partition from System Reserved to C if it will not start after Startup Repair - Run up to 3 Separate Times. Then run the repairs again.

If this is Disk1 in your screenshot then you changed the Partition Marked Active from C to System Reserved which had been previously deleted, so to assure it will serve as the System partition I would copy into it the hidden System boot files from C before running the 3 separate repairs. You must unhide these files first in Folder Options>View.

Make sure all other HD's are unplugged and the OS HD is set first HD to boot in BIOS setup.

As a last resort you can also try installing EasyBCD to WIndows 8 to add Win7 to a Dual Boot menu to see if it will pick it up. If not then it is likely corrupted beyond repair.

In that case you're best off doing a perfect Clean Reinstall - Factory OEM Windows 7 (same for retail) with all other HD's unplugged. To get it cleanest delete Sys Reserved and C to recreate them in that space with installer's Drive Options, shown in Steps 7 and 8 of Clean Install Windows 7

I would not move programs off of C because when installed they become a part of the OS and should remain with it and its image. Making self-defeating moves like that can indicate that you've bollixed your OS from other tweaks that are absolutely unnecessary in Win7, which is not XP. If you will stick with the steps in the tutorial then you will get and keep a perfect install for as long as you do. The steps are based on what has worked best in tens of thousands of installs we have helped with here.
My System SpecsSystem Spec
26 Nov 2013   #15
milindsmart

Windows 7 Home Premium x64
 
 

Thanks for responding.
Ah yes I had forgotten those, sorry... I ran MBAM from windows 8, and detected a few keygens in my documents folder, which I deleted. Nevertheless not what I would have hoped for to find a virus in.

Some boot files exist ONLY in the system reserved drive now, specifically bcd.

I will try adding it as a boot option in the windows 8 bootmgr menu.
UPDATE : I tried that, no difference. Obviously there is something wrong with the boot files and/or drivers.

In your last paragraph, I presume you refer to the drive called Programs. That is actually a drive I use in windows 8 for installation of programs. I haven't used any hacks or tweaks for it ; I just choose that location every time manually when I'm installing programs. Isn't that perfectly safe?
Anyway, my windows 7 installation was perfectly conventional. It was intended as a stable OS for use by all members of my house and games, so there were no "smart" ideas implemented here. Which makes me even more sure that this windows should be perfectly salvageable.

With regard to reinstallation :
I am normally quite open to the idea, and keep reinstalling OSes as and when there's something to gain. The problem in this case is that it's about 1.5 years old, and fully updated, fast, rock solid stable, with a lot of programs installed, all drivers installed. Uncharacteristically, this time I'm much more resistant to reinstalling windows. I realize that this means more work for some of you guys, but I'm really keen this time to repair this windows to working state. As it is, there are two further avenues available which occur to _me_ alone, and I'm nowhere close to as knowledgeable and skilled as you(Greg and Arc) and many other members here.

  1. Investigate the SFC logs, and find the exact files which sfc is barfing on. That would definitely be a start.. The thing annoying about SFC is that instead of complaining about not being able to verify files, it could have an option replace them with the fresh copies from the installation disc.
  2. Worst case, install windows 7 on another partition, then slowly copy over suspected corrupted key system files. This is effectively a repair install, but one that Microsoft in its infinite wisdom has not provided /s
The cause of this is very important to consider : after some potential mangling while booting windows 8, the windows 7 installation (on next boot) suddenly complained about a lack of two drivers. Means file corruption. Since booting couldn't have corrupted winsxs, I would not pick on it, so that leaves out only the boot chain, which is ntoskrnl, hal.dll, drivers, and other KEY system files. Which aren't unique to my system.

So in case it's too much work to guide step-by-step, I would love if you can just give hints and ideas. I'm quite willing to do the potentially time-consuming legwork to execute them. Maybe it's that I'm considering this a challenge.
My System SpecsSystem Spec
26 Nov 2013   #16
gregrocker

 

A heavily infected system may not yet be disinfected so it's best to run the bootable AV's from
Troubleshooting Windows 7 Failure to Start to make sure .

Then it still may not repair if System files have been damaged, which you can repair by running SFC /SCANNOW Run in Command Prompt at Boot, if necessary up to 3 separate times if it finds bad files.

If you have been running the Startup Repairs with the Win8 drive connected then it won't repair Win7. It needs to be the only drive plugged in, set first to boot in BIOS setup, with Sys Reserved marked Active first, then run Startup Repair - Run up to 3 Separate Times with reboots no matter what it reports.

If this fails move the Active flag to C to do the repairs again.

If the boot files are corrupted beyond repair then try using Win8 boot manager to start it by adding it with EasyBCD from Win8.
My System SpecsSystem Spec
31 Dec 2013   #17
milindsmart

Windows 7 Home Premium x64
 
 

Sorry for the loong delay, was caught up. I have made some progress recently..

I was looking at this article that told me to replace ntdll.dll as it might have been corrupt. More out of curiosity, I checked the folder for ntdll intending to verify that the filesize and dates are the same. And shockingly, it was NOT THERE!! No wonder the system wasn't starting.

So I copied the file from the Windows 7 SP1 install.wim. So now it still BSODs, but about 10s into the boot animation, much after the blobs of colour converge (the previous point at which it used to BSOD). The bugcheck parameter has changed :

Attachment 299529

What I want to know is, how could SFC not have been able to fix it? I searched and found no mention of any ntdll in the CBS log file. How could startup repair have not found it among so many runs that I gave it? What might be going on?
My System SpecsSystem Spec
31 Dec 2013   #18
gregrocker

 

There's a whole list of extant steps you've yet to report back upon.

Start with the checklist for Troubleshooting Windows 7 Failure to Boot which we've not heard back on yet.

Have you tried System Restore to the oldest restore point from the disk?
My System SpecsSystem Spec
31 Dec 2013   #19
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.

No doubt that the system is beyond repair.

Better you install windows afresh. If you fail to install too, then you need to change the sata cables, apply the cables in the unused ports on the motherboard. And test your HDD using Seatools for DOS.

Let us know the results.

And dont try random fixes available over net.
My System SpecsSystem Spec
31 Dec 2013   #20
milindsmart

Windows 7 Home Premium x64
 
 

Here is the checklist with the items I have tried :

1. If possible unplug all other HD's. Boot into BIOS setup by tapping the key given for this on first boot screen, check that Windows 7 HD is detected and set to boot first (after CD/DVD drive). --------- Done

2. Try booting into Safe Mode with Networking to install, update and run a full scan with Malwarebytes. --------- Does not boot, same BSOD

3. If Safe Mode is not working, download, burn to CD or write to flash stick, boot the disk and run a full scan with Windows Defender Offline. If it fails try one of these FREE Bootable AntiVirus Rescue CDs burned to CD using Windows Image Burner or ImgBurn. You can also move the HD to another PC to scan it with Malwarebytes. ------------ scanned with MBAM from windows 8, Boot scan using F-Secure in progress, no malware found yet.

4. If infection cleans up enough that Windows 7 will start then run SFC -SCANNOW Command to check for damaged System files. ------------ Done, it fails, please check my earlier posts

If not post back the virus scan results in our Security forum for expert help.

5. Once the System is clean if it won't start boot into System Recovery Options via the F8 menu or disk as shown in tutorial, run Startup Repair repeatedly up to 3 separate times with reboots in between each - no matter what it reports. ----------- Done, 1st try says it could not find cause of problem, 2nd and 3rd says it could not find problem. Continues to BSOD.

6. If you need an installer for your licensed version to boot to run Repairs or possible Clean Reinstall, download the latest official Win7 installer w/SP1 ISO, burn to DVD or write to flash stick using Windows 7 USB-DVD Download Tool. -------- Done, using.

7. If no installation shows up to repair when booting into DVD System Recovery Options or Repair CD, or Startup Repair won't work after several tries, click through to System Recovery Options, open a Command Line to use the Bootrec.exe tool which is demonstrated most fully in Steps 1-3 here. ------------ NA, installation shows up in the screen,

8. If these fail, try running System Restore from Recovery Options list working chronologically backward to find a bootable configuration. If those fail, from Recovery Options open a Command Line to run SFC -SCANNOW Run in Command Prompt at Boot. ---------------- There are NO system restore points. I don't know how it happened. Probably CCleaner wiped them one of those times I ran it. Stupid me. Mentioned in 1st post.

9. As a last resort boot free Partition Wizard bootable CD to Explore C to see if your files are intact and post back a camera snap of drive map for more help. Make sure C or the 100mb System Reserved partition (preferred) is marked Active, then click on HD to highlight it, from Disk tab select Rebuild MBR, Apply. --------------------- Done, no difference. please check earlier posts.

If Windows 7 doesn't start and you restored Active flag, run Startup Repair 3 Separate Times. If marking 100mb Active fails to Repair x3, then mark Windows 7 partition itself Active and try above steps again. Make sure the Windows 7 HD is set first to boot in BIOS setup. --------------------- Done, no difference. please check earlier posts.
My System SpecsSystem Spec
Reply

 PROCESS1_INITIALIZATION_ERROR 0x000000b6




Thread Tools Search this Thread
Search this Thread:

Advanced Search



Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 19:41.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App