Startup Failure - 0x0000007B, even after Clean All & reimage


  1. Posts : 352
    Windows 7 Pro x64 SP1
       #1

    Startup Failure - 0x0000007B, even after Clean All & reimage


    First of all, I read the rules for posting BSOD errors, but I don't think I am able to actually use that "BSOD Dump & System File Collection app," as I cannot get Windows to finish starting up. So I wouldn't think I could download the app to that drive and have it work... If I'm mistaken there, please correct me.

    Second, this is NOT any of my drives as listed below in my specs. The rest of the rig, however, IS the same. I have disconnected my SSD & my HDD. I am working on a friend's drive in one of my hot-swap bays. It is a .

    This just started Wednesday. The BSOD pops up right before the loading screen for Windows finishes.
    Error code: 0x0000007B (0x80786B58, 0xC0000034, 0x00000000, 0x00000000)
    I wiped the entire drive a few times, even did a command prompt "clean all" from the installation disc.
    Windows 7 reinstalled fine and booted normally no problem.
    --But when I reimaged it (from September), the same problem happens.

    That image is perfectly clean and fine. I did test it back then right after I took it. So how come it is causing the same thing to happen? This makes no sense to me.

    I do at least have the "boot log," or something, from when I "Enabled Boot Logging" and tried to let it start, and crashed. I connected my SSD again and am searching for it in the affected drive, but I can't find it. Where is it saved?

    Sorry for not having much info, but I'm not familiar with BSODs that are this hard to deal with... In the mean time I'm going to see if the diagnostics on the Win 7 Installation Disc will tell me anything.
      My Computer


  2. Posts : 352
    Windows 7 Pro x64 SP1
    Thread Starter
       #2

    Startup Repair details:

    Root cause found:
    ------------------
    A recent driver installation or upgrade may be preventing the system from starting.
    Repair action: System files integrity check and repair
    Result: Failed. Error code = 0x490
    Time taken = 709789 ms

    Okay, *now* running memory diagnostics.
      My Computer


  3. Posts : 352
    Windows 7 Pro x64 SP1
    Thread Starter
       #3

    120 views so far but please won't somebody at least help me find where this "boot log" saves to? I've never done this before. =/
      My Computer


  4. Posts : 16,130
    7 X64
       #4

    Look for ntbtlog in the Windows directory
      My Computers


  5. Posts : 352
    Windows 7 Pro x64 SP1
    Thread Starter
       #5

    Thank you! Brb to upload that.
      My Computer


  6. Posts : 352
    Windows 7 Pro x64 SP1
    Thread Starter
       #6

    I just read that I also can only see that file from safe mode, but it also crashes upon trying to boot into safe mode on the affected drive...
      My Computer


  7. Posts : 388
    Windows 7 Home Premium 64 Bit OS
       #7

    SIW2 has given you the location of the file. I have never had to do that
    before either but if that is in fact the location of the file then why not try to
    extract it using a Linux live boot disk.

    Puppy Linux is used in this tutorial:
    Use Puppy Linux Live CD to Recover Your Data - Geeks to Go Forums

    Pretty sure you would be able to accomplish the same result with Knoppix or
    another Linux version which loads to RAM (live boot disk) but try that one - the tutorial looks
    fairly comprehensive and step by step.

    Downside - your gonna need another machine to look at the files.

    Hope this may be of some assistance
    Cheers :)
      My Computer


 

  Related Discussions
Our Sites
Site Links
About 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 13:59.
Find Us