windows 7 - BSOD error 0x0000006B PROCESS1_INITIALIZATION_FAILED on boot

08
2014-07
  • Teo Klestrup Röijezon

    I reinstalled League of Legends because the patcher always gave me an error. However, out of complete stupidness I didn't uninstall the old installation first because I thought that it would simply replace the files. However, when the installer bar got to 100% it simply minimized. Then I closed the application from the task manager. I tried uninstalling it after a failed attempt to start it up. The same behavior as when I installed it. Then I tried reinstalling where it simply presented the InstallShield Modify/Repair/Remove menu and I selected repair. Nothing happened.

    Then I tried selecting Modify, then seeing that the only option (called DefaultFeature) was unchecked. Same behaviour as install/uninstall. After seeing that it still failed, I uninstalled again. And after that I deleted C:\Program Files (x86)\League of Legends manually. When I tried installing LoL again it still thought I had it, so I chose repair. This time something actually happened, but it installed the whole game to C:\Windows. Seeing what was going on I clicked cancel and then started it up to try uninstalling it. However, I got an error message about something not being registered and then the minimization to I decided to let it repair completely. Then I uninstalled it and it gave only the minimization.

    However, when I rebooted another application started up complaining about some library being absent. So I decided to do a system restore. After letting it complete I got a BSOD (0x0000006B(0x00000000, 0x00000000, 0x00000000, 0x00000000)) every time I tried starting up Windows normally or in safe mode. However, system recovery mode works, although the system recovery automatic repair does not fix it. After a bit of searching I found a Microsoft KB article about it (981833) and tried following the workaround instructions. Nothing happened.

    I am using Windows 7 Home Premium 64-bit HP OEM and Ubuntu 10.04 LTS 64-bit installed with WUBI.

    • Answers
  • Mike

    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.

  • Teo Klestrup Röijezon

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


    • Related Question

    64 bit - Random BSODs on Windows 7 boot. Can't find a valid reason
  • 0plus1

    I bought and assembled a new PC:

    Asus m4a785td-v EVO
AMD x4 620
OCZ Black Edition 2x 2GB
WD 500GB SATA

    Windows 7 Ultimate 64-bit fresh install BSOD on boot. Formatted, reinstalled, BSOD on install. Ran memtest -> no errors. Ran Windows 7 install in safe mode. Installed, random BSOD on Windows 7 startup, even in safe mode. Updated BIOS. Ran the Windows 7 memtest (no error), booted after some tries and ran Prime95 blend test for 12 hours straight with no errors at all! When the PC has booted, Windows 7 runs as smooth as possible, I've been playing STALKER for 4 hours straight with not a single hiccup.

    Using Blue Screen View I can see that every BSOD involves:

    ntoskrnl.exe

    Here are the dumps

    Ran sfc/scannow as admin:

    Windows Resource Protection found corrupt file but was unable to fix some of them.

    What's going on?


    • Related Answers
  • Richard

    A BSOD is most likely to be either a hardware problem (e.g. unreliable memory) or a driver.

    Submitting a bug report to MS (you should be prompted for this after the reboot) will tell you if it can be matched to a know issue (or unambiguously linked to a specific drive).

    (You can do the same analysis, without the know issues database, with windbg and analyze -v.)

    If that fails you need to divide and conquer, by running hardware diagnostics to eliminate some hardware problems. Also deleting devices with 3rd party drivers (and don't allow Windows to en-enable them might allow you to find a driver issue.