Error stop 0x0000007B Dead screen

Discussion in 'Windows 7' started by alpha45, Jan 21, 2025.

  1. alpha45

    alpha45 MDL Junior Member

    Apr 14, 2014
    88
    8
    0
    Hello,

    I have a problem that I can't solve.

    I have a dual boot system with windows 7 and windows 11 and with the bios everything worked normally.

    Now I have installed a new hardware based on uefi, and at startup windows 7 no longer works, the blue screen appears as described in the subject, while windows 11 works normally.

    I tried to restore the startup with the recovery disk, but it doesn't solve it.

    I don't want or have time to reinstall the OS. It's too complex...

    Do you know and can you help me?

    Thank you
    Immagine WhatsApp 2025-01-21 ore 22.11.21_4b42cd71.jpg
     
  2. kaljukass

    kaljukass MDL Guru

    Nov 26, 2012
    3,468
    1,354
    120
    Just remove Win7 from this machine and you'll be fine. It's that simple.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. pm67310

    pm67310 MDL Guru

    Sep 6, 2011
    3,509
    2,740
    120
    Try modded driver for windows 7 and custom acpi or better convert physical windows 7 to vm ( virtual machine )
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. NewEraCracker

    NewEraCracker MDL Member

    Apr 19, 2011
    196
    236
    10
    #4 NewEraCracker, Jan 22, 2025
    Last edited: Jan 22, 2025
    Patched acpi.sys discussion: forums.mydigitallife.net/threads/uefiseven-easily-boot-windows-7-on-uefi-class-3-devices.82137/page-29#post-1864622

    Latest: winraid.level1techs.com/t/acpi-sys-issue-while-transplanting-win7-from-x570-to-trx40-board/102292/5

    Alternatively, could consider workarounds such as: Using Windows 10 or 11 LTSC (Long-Term Servicing Channel) as the host OS and virtualizing Windows 7 within it, allowing for a more modern and compatible host OS while still running Windows 7 in a virtual environment.

    My two cents.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. Tito

    Tito Admin / Adviser
    Staff Member

    Nov 30, 2009
    18,949
    19,442
    340
  6. alpha45

    alpha45 MDL Junior Member

    Apr 14, 2014
    88
    8
    0
    #6 alpha45, Jan 22, 2025
    Last edited: Jan 22, 2025
    (OP)
    Windows 11 Pro 23H2 Build: 22631 and Windows 7 Ultimate cpu: Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz :Asus Prime B365-Plus ram 32Gb
     

    Attached Files:

  7. alpha45

    alpha45 MDL Junior Member

    Apr 14, 2014
    88
    8
    0
    Windows 11 Pro 23H2 Build: 22631; Windows 7 Ultimate; CPU Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz ram 32Gb
    Grazie
    Immagine 2025-01-22 144651.jpg
     
  8. pm67310

    pm67310 MDL Guru

    Sep 6, 2011
    3,509
    2,740
    120
    I7-8xxx are computer from 2018 - 2019 , computer up to 2020 work fines , past 2020 era more problematic .. for cpu higer than intel 10th gen
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. NewEraCracker

    NewEraCracker MDL Member

    Apr 19, 2011
    196
    236
    10
    The 0x0000007B error can also be caused by a missing or incompatible driver, or a hardware configuration issue, such as the hard drive being connected to the wrong SATA port.

    In particular, the Windows Boot Manager stores the disk signature and partition information of the boot device, including the SATA port number. If the hard drive is moved to a different SATA port, the Boot Manager may not be able to locate the boot device, resulting in the 0x0000007B error.

    I previously encountered this issue and resolved it using Hirens Boot, however, I recognize this may not be an option anymore. Here are some alternative solutions you can try on your Windows 11 system:
    • Bootice: This free tool enables you to manage and repair the BCD store, including the one located at F:. It also features a user-friendly graphical interface.
    • EasyBCD: A widely-used BCD editor that allows for effective management and repair of the BCD store. While I have used it in the past, I haven't utilized it for repairing another partition.
    Always double-check the source of software downloads and avoid clicking on sponsored links, like Google ads, as they can often lead to malware.

    Be cautious when editing the BCD store, as incorrect changes can lead to further boot-related issues. If you're not comfortable making these edits, it's advisable to seek the help of a professional.
    I hope this helps! Good luck, and don't forget to back up your BCD store before making any changes.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. alpha45

    alpha45 MDL Junior Member

    Apr 14, 2014
    88
    8
    0
    EasyBCD is paid and I can't use Bootice
    Thanks
     
  11. pm67310

    pm67310 MDL Guru

    Sep 6, 2011
    3,509
    2,740
    120
    Free for personnal use....
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. NewEraCracker

    NewEraCracker MDL Member

    Apr 19, 2011
    196
    236
    10
    There should be no problem installing it. There is also:

    BCDEdit: A built-in command-line tool in Windows. It supports Windows 11 and can be used to fix boot issues with another partition. When using the BCDEdit command-line tool, you can specify a different store using the /store argument. This allows managing and repairing the boot configuration of a different partition or disk.

    The syntax for using the /store argument is as follows:
    Code:
    bcdedit /store <store_location> <command>
    
    Replace <store_location> with the path to the BCD store to manage, and <command> with the BCDEdit command to execute.

    For example, to manage the BCD store on a different partition, you can use the following command:
    Code:
    bcdedit /store F:\Boot\BCD /enum
    
    This command will enumerate the boot entries in the BCD store located on the F: drive, in the Boot folder.
    Note that the <store_location> path should be in the format of a Windows file path, and should point to the location of the BCD store file (usually named BCD).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. alpha45

    alpha45 MDL Junior Member

    Apr 14, 2014
    88
    8
    0
    #13 alpha45, Jan 23, 2025
    Last edited: Jan 23, 2025
    (OP)
    Thank you very much for the information, but a question before I make a mistake: should this path be executed in the system or in the Windows 7 recovery?

    This is the result executed from windows 11 prompt:
    C:\>bcdedit /store F:\Boot\BCD /enum
    The system cannot open the Boot Configuration Data store.
    The system cannot find the file specified.
     
  14. alpha45

    alpha45 MDL Junior Member

    Apr 14, 2014
    88
    8
    0
  15. NewEraCracker

    NewEraCracker MDL Member

    Apr 19, 2011
    196
    236
    10
    To clarify, my previous instructions assumed that you would select the boot device manually in the BIOS settings.

    Be sure you're running the command as administrator. It could also be that the BCD store is present at a different folder.

    From within Windows 11 according to the partitions you showed, there are two possible locations for the Windows 7 BCD store:
    • F:\Boot\BCD (your separate boot partition)
    • F:\EFI\Microsoft\Boot\BCD (if your separate boot partition is prepared for UEFI)
    How are you currently booting into Windows 7 - through the Windows Boot Manager or by selecting the boot device manually in the BIOS settings?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. NewEraCracker

    NewEraCracker MDL Member

    Apr 19, 2011
    196
    236
    10
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. kebabstorm

    kebabstorm MDL Junior Member

    Aug 3, 2016
    98
    136
    0
    It's always been the conventional wisdom that when you upgrade your computer, especially if you change the motherboard architecture, essentially making it an entirely different machine, you should just back your s**t up and reinstall Windows from scratch. You aren't really meant to use a windows installation made for one machine in another.