none
process1_initialization_failed

    Question

  • Booted up my laptop today (windows 7), got to the "starting windows" page where the icon does it's little dance, and the i got the BSOD with process1_initialization_failed. My computer has been running flawlessly for about 2 years now, and this is the first BSOD i have ever had.  I am not very tech savy and i'm looking for anything i can do to save my relatively new laptop. Keep in mind that i cannot even get to my desktop to do anything. I used system restore, restored to a month ago, and it fixed nothing. I then tried running startup repair and i got the following message: "Startup Repair cannot repair this computer automatically". I clicked "view problem details" and got the following report:

    Problem signature:

    Problem event name: StartupRepairOffline

    Problem Signature 1: 6.1.7600.16385

    Problem signature 2: 6.1.7600.16385

    Problem Signature 3: unknown

    Problem Signature 4: 21200980

    Problem Signature 5: AutoFailover

    Problem signature 6:  7

    Problem signature 7: Bad Driver

    OS Version: 6.1.7600.2.0.0.256.1

    Locale ID: 1033

     

    Technical information:

    *** STOP: 0x0000006B  (0x0000000000000000, 0x0000000000000000, 0x0000000000000000)

     

    If anyone knows ANYTHING that could help me, it would be appreciated. Thanks

    • Edited by Morgan2327 Friday, June 04, 2010 2:08 AM tech info
    Friday, June 04, 2010 1:58 AM

Answers

  • Bugcheck 0x24 is NTFS_FILE_SYSTEM - "This indicates a problem occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives."  The recent times I've seen this bugcheck, it has been due to or related to memory corruption. Are you at all able to run chkdsk on the drive, as suggested, perhaps from a System Recovery command prompt?

    There's usually a stop code, and four parameters (like you posted with the 0x24 bugcheck).  If each of the four params for the 0x6b bugcheck is 0, then it seems that it will be difficult to know the status code that Windows encountered, and that is responsible for the bugcheck.

    Are you able to ensure that the disk is connected snugly in the laptop? You may need to look at your system manual.  Of course, if you're not comfortable doing so, don't try it.

    Friday, June 04, 2010 11:04 AM

All replies

  • Are you perhaps missing a hex number - there should be 5, and in the case of 0x6b (PROCESS1_INITIALIZATION_FAILED), the first and second ones (the stop code and first param) are the ones of note.

     

    Can you boot into safe mode, or with a Last Known Good Configuration?

    "Any part of the disk subsystem can cause the PROCESS1_INITIALIZATION_FAILED bug check, including bad disks, bad or incorrect cables, mixing different ATA-type devices on the same chain, or drives that are not available becuase of hardware regeneration.

     

    This bug check can also be caused by a missing file from the boot partition or by a driver file that a user accidentally disabled in the Drivers tab."

    Friday, June 04, 2010 2:16 AM
  • Not missing any numbers. The STOP things are all zeros.

    However i just booted my laptop up again, still got a BSOD message, but this time its a very different one. Not even a process1_initialization.

    it says:

    "A problem has been detected and windows has been shut down to prevent damage to your computer.

    If this is the first time you've seen this stop error screen.....

    Disable or uninstall any anti-virus, disk defragmentation or backup utilities (which i cant do because i can't get to the desktop), Check your hard drive configuration and check for any updated drivers. Run chkdsk /f to check for hard drive corruption, and then restart your computer.

    Technical information:

    ***STOP: 0x00000024 (0x0000000000190494, 0xFFFFFA80026A4010, 0xFFFFFFFFC0000102, 0x00000000000000000)"

    Booting in safe mode or using last known good configuration both did not work when i tried (before i got this new BSOD)

    Friday, June 04, 2010 2:47 AM
  • Well i havent got that new one in the past couple tries. Just keep getting the process1_initialization error over and over.
    Friday, June 04, 2010 3:39 AM
  • Bugcheck 0x24 is NTFS_FILE_SYSTEM - "This indicates a problem occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives."  The recent times I've seen this bugcheck, it has been due to or related to memory corruption. Are you at all able to run chkdsk on the drive, as suggested, perhaps from a System Recovery command prompt?

    There's usually a stop code, and four parameters (like you posted with the 0x24 bugcheck).  If each of the four params for the 0x6b bugcheck is 0, then it seems that it will be difficult to know the status code that Windows encountered, and that is responsible for the bugcheck.

    Are you able to ensure that the disk is connected snugly in the laptop? You may need to look at your system manual.  Of course, if you're not comfortable doing so, don't try it.

    Friday, June 04, 2010 11:04 AM
  • I had the exact same issue and I was able to fix it.

    Error STOP: 0x0000006B

     

    The file: Bootcat.cache was corrupted, I am not sure how it happened, I ran spybot and spybot had me rebooot the computer to remove files but I don't think it was from Spybot.

     

    All you have to do is delete the file: bootcat.cache from %SystemRoot%\system32\codeintegrity

     

    I used the instructions from KB981833:

    http://support.microsoft.com/kb/981833

    After I moved the bootcat.cache to another location then computer boot up and no more BSOD and Spybot continued to ran at startup.

    Monday, November 08, 2010 8:55 PM
  • Booted up my laptop today (windows 7), got to the "starting windows" page where the icon does it's little dance, and the i got the BSOD with process1_initialization_failed. My computer has been running flawlessly for about 2 years now, and this is the first BSOD i have ever had.  I am not very tech savy and i'm looking for anything i can do to save my relatively new laptop. Keep in mind that i cannot even get to my desktop to do anything. I used system restore, restored to a month ago, and it fixed nothing. I then tried running startup repair and i got the following message: "Startup Repair cannot repair this computer automatically". I clicked "view problem details" and got the following report:

     

    Problem signature:

    Problem event name: StartupRepairOffline

    Problem Signature 1: 6.1.7600.16385

    Problem signature 2: 6.1.7600.16385

    Problem Signature 3: unknown

    Problem Signature 4: 21200980

    Problem Signature 5: AutoFailover

    Problem signature 6:  7

    Problem signature 7: Bad Driver

    OS Version: 6.1.7600.2.0.0.256.1

    Locale ID: 1033

     

    Technical information:

    *** STOP: 0x0000006B  (0x0000000000000000, 0x0000000000000000, 0x0000000000000000)

     

    If anyone knows ANYTHING that could help me, it would be appreciated. Thanks

    Hi, i've got same problem...tried all kind situations to resolve the problem, but nothing work! I can't get into Safe Mode or to Restore the Computer....i got errors. I don't have SP1, but i tried to remove bootcat.cache but i didn't work, i still got the same BSOD....also i don't have minidump file in windows folder for some reason ( i looked via Ubuntu LiveCD). Atm i try to get bootcat.cache file from my friends computer....

    EDIT 10.12.2011: I replaced the bootcat.cache file from another computer, my computer booted succesfully, but when i installed antivirus program i got same BSOD & after each restart i'm getting same BSOD...

    here is minidump

     

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" /> 
      <EventID Qualifiers="16384">1001</EventID> 
      <Version>0</Version> 
      <Level>2</Level> 
      <Task>0</Task> 
      <Opcode>0</Opcode> 
      <Keywords>0x80000000000000</Keywords> 
      <TimeCreated SystemTime="2011-12-10T15:55:42.000000000Z" /> 
      <EventRecordID>23636</EventRecordID> 
      <Correlation /> 
      <Execution ProcessID="0" ThreadID="0" /> 
      <Channel>System</Channel> 
      <Computer>4uvak91-PC</Computer> 
      <Security /> 
      </System>
    - <EventData>
      <Data Name="param1">0x0000006b (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)</Data> 
      <Data Name="param2">C:\Windows\MEMORY.DMP</Data> 
      <Data Name="param3">121011-45552-01</Data> 
      </EventData>
      </Event>


     



    • Edited by 4uvak91 Sunday, December 11, 2011 10:32 AM
    Saturday, December 10, 2011 1:36 PM
  • any1, please help!?!!
    Tuesday, December 20, 2011 9:45 PM
  • yo any MS tech guy!? cmon!!!!
    Thursday, December 22, 2011 9:59 PM