Windows error 0x0000006B, 107

Detailed Error Information

DISK_CHANGE[1]

MessageThe program stopped because an alternate diskette was not inserted.
Declared inwinerror.h

This appears to be a raw Win32 error. More information may be available in error 0x8007006B.

PROCESS1_INITIALIZATION_FAILED[2]

This is a Blue Screen of Death stop code. More information is available in the Knowledge Base article Bug Check 0x6B: PROCESS1_INITIALIZATION_FAILED.

HRESULT analysis[3]

This is probably not the correct interpretation of this error. The Win32 error above is more likely to indicate the actual problem.
FlagsSeveritySuccess

This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.

Reserved (R)false
OriginMicrosoft
NTSTATUSfalse
Reserved (X)false
FacilityCode0 (0x000)
NameFACILITY_NULL[3][1]
DescriptionThe default facility code.[3][1]
Error Code107 (0x006b)

Possible solutions

7

Trouble displaying C# stack trace in WinDbg

c#
windbg
stack-trace
handle-leak

WinDbg attempts to interpret the native call stack as best it can, however to fully interpret the stack of a CLR application WinDbg needs to use an extension called SOS. This extension has a separate command CLRStack for viewing the stack information of CLR stacks. You will need to load the SOS extension first however using the .loadby sos clr command (or similar, I remember getting the correct version SOS to load could be a bit of a pain)

For more information see

answered on Stack Overflow Oct 23, 2012 by Justin • edited Oct 23, 2012 by Justin
5

Is there any solution to Process1_Initialization_Failed on Windows 7?

windows-7
bsod
system-restore

I've been having the same Issue (BSOD) on Windows 7 Ultimate 64bit on my HPDV4 Laptop and here's my solution. Get a copy of bootcat.cache from a working system of similar configuration and copy it here C:\Windows\System32\CodeIntegrity overwriting existing file.

This has been working 100% although just deleting the file doesn't help.

answered on Super User Jun 27, 2012 by Nash • edited Jul 15, 2012 by HackToHell
4

Is there any solution to Process1_Initialization_Failed on Windows 7?

windows-7
bsod
system-restore

This usually means there is a critical system file missing or corrupt, run an offline System File Checker from the Windows Recovery Environment.

Once you have the command prompt loaded in RE, run this command, this will scan all system files for corruption and improper versions, replacing them as needed. Hopefully it will get it booting again.

sfc /scannow /offbootdir=d:\ /offwindir=d:\windows

Source of Information

answered on Super User Aug 10, 2011 by Moab
4

Is there any solution to Process1_Initialization_Failed on Windows 7?

windows-7
bsod
system-restore

In my case the bootcat.cache was more of a symptom than the issue. The bootcat.cache file will not regenerate if the folder C:\Windows\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} has errors. Some virus scanners (McAfee in my case) sometimes screw up and this folder gets renamed to a tmp folder. After copying the bootcat.cache file from another PC, I boot into windows and do the following (Just doing the bootcat copying hasn't been all that stable for me):

  1. Search through all of the tmp***.tmp folders within C:\Windows\Sytem32\catroot and find the one with the most files. I've typically seen them around 800-1000 files, though this may vary I guess; I'm no expert.

  2. Copy these files into the {F750E6C3-38EE-11D1-85E5-00C04FC295EE} folder, overwriting when prompted. Then go and rename bootcat.cache in C:\Windows\System32\CodeIntegrity\ so if this doesn't work you can restore it.

  3. Reboot now and it should regenerate the bootcat.cache for your current PC. If not, you can always copy the {F750E6C3-38EE-11D1-85E5-00C04FC295EE} folder from a different PC, though some drivers may show as "unsigned" and you have to re-install them to make it go away.

We had a rash of these after a domain wide McAfee issue and either copying from the temp file or from another PC has worked on about 10 PCs and 3 servers with 2008 R2 installed so far.

Source: (SFW). Did not work for us as they said, but pointed me in the right direction.

answered on Super User Dec 7, 2012 by Derek McNelly • edited Dec 7, 2012 by terdon
3

Windows 7 - BSOD PROCESS1_INITIALIZATION_FAILED

windows-7
windows
64-bit
bsod

This can occur if the Bootcat.cache file is corrupted or the size of the file is different than it was at the last successful start.

The Bootcat.cache file is located at %SystemRoot%\system32\codeintegrity.

Start the computer from a Windows install or repair disk, or perhaps a Linux LiveCD or alike. Delete the Bootcat.cache file, and then restart the computer.

Source

answered on Super User Feb 24, 2014 by Ƭᴇcʜιᴇ007
3

Is there any solution to Process1_Initialization_Failed on Windows 7?

windows-7
bsod
system-restore

I ran into the same error today, but found a different cause. This page is one of the first Google results for the error, so in case anyone else finds this, here's what happened:

I was getting the same error on every boot. If I tried booting in safe mode, I could see that it would crash while loading CLASSPNP.SYS. I tried using the recovery console on my Windows 7 DVD, and before it finished loading, it would crash with a MEMORY_MANAGEMENT BSOD. That was mostly independent of my Windows install, so it's a sign that something was seriously wrong.

I burned a Memtest86+ CD and booted from that. Within seconds, it found massive errors in a chunk of memory:

Memtest errors

Removing the defective RAM stick solved the problem immediately. No files on disk were corrupt, they were just being corrupted while loading.

answered on Super User Oct 31, 2012 by gabedwrds
1

nasm/ld failing to do %include on cygwin

assembly
macros
include
cygwin
nasm

Your error was to assemble io.mac. It is a textfile which is included in sample.asm "as is". io.obj is not an assembled io.mac. With assembling io.mac you destroyed the original io.obj. But even if you extract the original io.obj from win_nasm_progs.zip you will fail. It is not a Windows file but a MS-DOS file (yes, this is very annoying). You can't either use the Linux file (io.o) because Cygwin needs Windows system calls. So you can't use the samples of Dandamudi's book outside of Linux. The only thing that comes to my mind is changing the calls in io.mac to calls to a C-function (and other adjusts) and linking the object file against GCC.

answered on Stack Overflow Dec 6, 2014 by rkhb
0

The LoadLibraryA method returns error code 1114 (ERROR_DLL_INIT_FAILED) after more than 1000 cycles of loading/unloading

c++
python
loadlibrary

Make sure that initialization code of the loaded/unloaded library doesn't leak memory. Many libraries expect to be loaded only once and not always clean up their resources properly.

E.g. in C++ file at the top level one can declare and initialize a variable like this:

AClass *a = new AClass(1,2,3);

The code would be executed when library is loaded automatically. Yet, now, it is impossible to free the hanging instance as library doesn't know precisely when/how it is going to be unloaded. In the case one can either replace "AClass *a" with "AClass a" or write your own DllMain for the library and free resources on DLL_PROCESS_DETACH.

If you have no control over the library's code, then it might make sense to create a cache of loaded libraries and simply never unload them. It is very hard to imagine that there would be unlimited number of libraries to overload such cache.

answered on Stack Overflow Jun 10, 2010 by Dummy00001
0

BSOD error 0x0000006B PROCESS1_INITIALIZATION_FAILED on boot

windows-7
windows
bsod
system-restore

If you can't boot, it sounds like you need a system repair.

  1. Get any Windows 7 disk.
  2. Reboot while tapping F2.
  3. Go into BIOS settings, and set your CD/DVD as first boot-able device.
  4. Insert the Windows 7 disk into the drive.
  5. Reboot.
  6. Follow these instructions. "Recover Windows 7 from a serious error". Do not choose Install!
  7. Choose REPAIR. This will not alter the program entries in the registry. You won't have to reinstall all your programs. It simply re-writes any original Windows system files.
  8. You will be asked for user name and password, to access the drive.
  9. Once REPAIR is done, reboot and do a check disk with /fix. This will repair any file, directory, or index problems.
  10. After this, delete the game's directory.
  11. Reboot.
  12. Then, download a Windows 7 registry cleaner, and clean it thoroughly. It will remove references to the uninstalled game.
  13. Reboot.
  14. Reinstall the game.

I wish you well.

answered on Super User Feb 14, 2011 by Mike • edited Feb 14, 2011 by Mike
0

BSOD error 0x0000006B PROCESS1_INITIALIZATION_FAILED on boot

windows-7
windows
bsod
system-restore

I finally decided to just go with the reformat option.
Thanks for all the help.

answered on Super User Feb 23, 2011 by Teo Klestrup Röijezon
0

How can I get all frames of stack traces in "!htrace -diff" result?

memory-leaks
windbg
handle-leak

This link point to this one Which tells that basically it is hard coded.

The maximum depth of the stack trace is currently hardcoded to 16 (although it's possible it will change in the future). Also, that includes a few entries for the kernel-mode portion of the stack trace. Those stack trace entries can be displayed by kernel or driver developers by using !htrace in a kernel debugger. So getting around 11 user-mode entries for each of your traces sounds accurate.

answered on Stack Overflow Dec 9, 2014 by Boris
0

How can I get all frames of stack traces in "!htrace -diff" result?

memory-leaks
windbg
handle-leak

Unfortunately you can't.

Assuming that you have symbols set up correctly, I see the following possibility

Some of the traces reported by !htrace may be from a different process context. In this case, the return addresses may not resolve properly in the current process context, or may resolve to the wrong symbols.

Source: WinDbg help (.hh !htrace)

This can happen if a different process injects handles into your process and the addresses correlate to that process. In this case, the process ID listed by !htrace does not match the process you're debugging (type | (pipe) to get the process ID).

In such a case, you can attach to the process (.attach 0x<pid>, 0n is default here) and try to get the remaining callstack from there, but I never did this myself.

answered on Stack Overflow Dec 9, 2014 by Thomas Weller
0

nasm/ld failing to do %include on cygwin

assembly
macros
include
cygwin
nasm

I decided to abandon the I/O scheme from Guide to Assembly Language Programming in Linux and go with that (which works on Cygwin/nasm) of Carter, Paul A. PC assembly language. Raleigh, NC: Lulu Press, 2007(i.e., its driver.c cdecl.h asm_io.inc asm_io.asm files)

answered on Stack Overflow Dec 7, 2014 by boardrider
-1

BSOD error 0x0000006B PROCESS1_INITIALIZATION_FAILED on boot

windows-7
windows
bsod
system-restore

I had the same issue. After 5 and a half hours trying everything, the only end solution was to wipe and reformat the drive and upgrade windows

answered on Super User Jun 17, 2016 by matt

Comments

Leave a comment

(plain text only)

Sources

  1. winerror.h from Windows SDK 10.0.14393.0
  2. https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
  3. https://msdn.microsoft.com/en-us/library/cc231198.aspx

User contributions licensed under CC BY-SA 3.0