Freeze at boot logo despite using UEFISeven

[AlphaNecron]

My specs: Acer Aspire F5-571 34Z0 - i3 5005U - 4GB - Intel HD 5500. I disabled Secure Boot but it's not booting, keep freezing at boot logo. Is there any workaround for this?

[multiwirth]

I´ve experienced the same issue with my Acer Switch 3 sw312-31 After a few minutes, i decided to force power it off. UefiSeven.log

can´t launch the setup.

[mirh]

Same here with an acer nitro 5 AN515-55.

UefiMain: UefiSeven 1.30
InitializeDisplay: Found a GOP display adapter
SwitchVideoMode: Set mode 3 with desired 1024x768 resolution.
PrintVideoInfo: Current mode:
PrintVideoInfo:   HorizontalResolution = 1024
PrintVideoInfo:   VerticalResolution = 768
PrintVideoInfo:   PixelFormat = 1
PrintVideoInfo:   PixelsPerScanLine = 1024
PrintVideoInfo:   FrameBufferBase = 0
PrintVideoInfo:   FrameBufferSize = 3145728
PrintVideoInfo: Available modes (MaxMode = 5):
PrintVideoInfo:   Mode0: 1920x1080
PrintVideoInfo:   Mode1: 640x480
PrintVideoInfo:   Mode2: 800x600
PrintVideoInfo:   Mode3: 1024x768
PrintVideoInfo:   Mode4: 1280x1024
IsInt10hHandlerDefined: Int10h IVT entry points at location (0000:0000) outside VGA ROM memory area (C0000..D0000), rejecting handler
EnsureMemoryLock: Memory at C0000 already unlocked
UefiMain: VESA information filled in, Int10h handler address=C0200 (C000:0200)
EnsureMemoryLock: Success locking memory at C0000 with EfiLegacyRegion2Protocol
UefiMain: Int10h IVT entry modified to point at C000:0200
IsInt10hHandlerDefined: Int10h IVT entry points at location within VGA ROM memory area (C000:0200)
IsInt10hHandlerDefined: First Int10h handler instruction at C000:0200 (3D) valid, accepting handler
UefiMain: Pre-boot Int10h sanity check success
FileExists: Opened file '\EFI\BOOT\BOOTX64.original.efi' for reading
UefiMain: Found Windows Boot Manager at '\EFI\BOOT\BOOTX64.original.efi'
Launch: Loaded 'PciRoot(0x0)/Pci(0x14,0x0)/USB(0x3,0x0)/USB(0x1,0x0)/HD(1,GPT,81B1E1D1-DA63-4B1E-9734-BB54E4FD3308,0x800,0xEFFFDF)/\EFI\BOOT\BOOTX64.original.efi'
Launch: Addresss behind FileImageHandle=83DDE898
CheckBootMgrGuid: Found 9DEA862C-5CDD-4E70-ACC1-F32B344D4795
Launch: File matches an EFI loader signature

(same even if I force fakevesa)

[UsefulVideos]

@mirh It's not related to uefiseven, it's probably related to acpi.sys. After I used this acpi.sys on my 8th core laptop along with UefiSeven, it works, here's the link: https://1drv.ms/u/s!AkcyDjKJJ6KwiG-VKTBgc2jzeLDY?e=WoGQXJ acpi.sys needs to be replaced in "\install.wim[index number]\Windows\System32\Drivers\acpi.sys" and "\install.wim[index number]\Windows\System32\DriverStore\FileRepository\acpi.inf_amd64_neutral_aed2e7a487803437\acpi.sys" If you don't also replace the acpi.sys in the file repository, windows 7 oobe will replace the patched acpi.sys with the original acpi.sys, leading to A5 BSOD in the next restart. If you want Windows 7 Recovery Environment to work without A5 BSOD, extract "\install.wim[index number]\Windows\System32\Recovery\winre.wim" from install.wim, open it in 7-zip and replace acpi.sys in from the drivers folder and file repository folder like last lime, and once the files are copied, close winre.wim and copy it again in the same install.wim's path ("\install.wim[index number]\Windows\System32\Recovery") to overwrite the existing winre.wim with the fixed one, copying may take a few minutes, and once it's done, exit install.wim (make sure that it is on the sources folder of the Windows 7 installation folder. You can use oscdimg.exe to make the windows 7 install into an UEFI and Legacy bootable iso.

If it's just the installed Windows 7, just make sure to copy the patched acpi.sys in the "[win7-drive]\windows\system32\drivers\acpi.sys" and "[win7-drive]\windows\DriverStore\FileRepository\acpi.inf_amd64_neutral_aed2e7a487803437\acpi.sys" locations, same on all index numbers of "[win7-drive]\windows\system32\recovery\winre.wim", and you will no longer have the A5 BSOD.

If replacing the acpi.sys fixed the problem, then that's the cause. If it still doesn't work, it probably has 0x000007B BSOD (BOOT INACCESSIBLE DEVICE), make sure that the correct mass storage controller drivers for your device are installed, integrated, or split streamed. Switching to AHCI mode works as long as nvme driver and msahci driver are integrated and enabled on Windows 7 system hive on "SYSTEM\ControlSet001\Services", make sure it is enabled on the default control set "SYSTEM\Select" on the Default Reg DWORD.

On a UEFI class 3 computer without any modifications (VGA emulator, integrated drivers, ACPI patch), windows 7 would freeze and give the A5 BSOD (red bar on top) and then the other 0x000007B BSOD (boot inaccessible device).

[mirh]

Nobody mentioned a BSOD in this issue. It just freezes on the "Starting Windows" screen, before the logo can pop up (if you try safe mode, you'll see loading stops at disk.sys.. but that doesn't really mean anything by itself given that's already normally the last entry of the pre-boot environment)

Anyway I did replace all the acpi.sys in both indexes of boot.wim with yours (also Canonkong's) but nothing changed.

After testing on another pc though I once forgot to add back uefiseven, and then I noticed that when you boot a plain ISO here the behaviour... seems actually the same? Except perhaps a green line on the top of the screen. So I'm actually going out on a limb, and argue this is probably a legitimate bug in uefiseven.

More or less exactly around those instants, some video mode switching is assumedly supposed to happen and there are people with a slightly older laptop than mine (ok, well, it's 2-3 years older but still) that seemed to do well with just slipstreaming the video driver for a GOP-only-like trick.

[ibay770]

@mirh It's not related to uefiseven, it's probably related to acpi.sys. After I used this acpi.sys on my 8th core laptop along with UefiSeven, it works, here's the link: https://1drv.ms/u/s!AkcyDjKJJ6KwiG-VKTBgc2jzeLDY?e=WoGQXJ acpi.sys needs to be replaced in "\install.wim[index number]\Windows\System32\Drivers\acpi.sys" and "\install.wim[index number]\Windows\System32\DriverStore\FileRepository\acpi.inf_amd64_neutral_aed2e7a487803437\acpi.sys" If you don't also replace the acpi.sys in the file repository, windows 7 oobe will replace the patched acpi.sys with the original acpi.sys, leading to A5 BSOD in the next restart. If you want Windows 7 Recovery Environment to work without A5 BSOD, extract "\install.wim[index number]\Windows\System32\Recovery\winre.wim" from install.wim, open it in 7-zip and replace acpi.sys in from the drivers folder and file repository folder like last lime, and once the files are copied, close winre.wim and copy it again in the same install.wim's path ("\install.wim[index number]\Windows\System32\Recovery") to overwrite the existing winre.wim with the fixed one, copying may take a few minutes, and once it's done, exit install.wim (make sure that it is on the sources folder of the Windows 7 installation folder. You can use oscdimg.exe to make the windows 7 install into an UEFI and Legacy bootable iso.

If it's just the installed Windows 7, just make sure to copy the patched acpi.sys in the "[win7-drive]\windows\system32\drivers\acpi.sys" and "[win7-drive]\windows\DriverStore\FileRepository\acpi.inf_amd64_neutral_aed2e7a487803437\acpi.sys" locations, same on all index numbers of "[win7-drive]\windows\system32\recovery\winre.wim", and you will no longer have the A5 BSOD.

If replacing the acpi.sys fixed the problem, then that's the cause. If it still doesn't work, it probably has 0x000007B BSOD (BOOT INACCESSIBLE DEVICE), make sure that the correct mass storage controller drivers for your device are installed, integrated, or split streamed. Switching to AHCI mode works as long as nvme driver and msahci driver are integrated and enabled on Windows 7 system hive on "SYSTEM\ControlSet001\Services", make sure it is enabled on the default control set "SYSTEM\Select" on the Default Reg DWORD.

On a UEFI class 3 computer without any modifications (VGA emulator, integrated drivers, ACPI patch), windows 7 would freeze and give the A5 BSOD (red bar on top) and then the other 0x000007B BSOD (boot inaccessible device).

Thanks for the info. Unless someone wants to put in all that work in replacing said files (unless someone wants to make a patcher that does it automatically) it doesn't seem like it's worth it. You can integrate the drivers with this tool. https://forums.mydigitallife.net/threads/integrate7-script-%E2%80%93-automatically-slipstream-updates-and-drivers-up-to-11-2023.78722/page-42#post-1816388

[FallenChromium]

I have the same issue on the same hardware, but I tried to migrate an existing-and-working installation of Windows to use UEFI-only boot (since I needed dual-boot with Win11). The log says Int10H is initiated succesfully, so I guess there's still some issue in the UefiSeven that doesn't let it to be used with the HD5500 on Acer laptops 🫠

[ibay770]

Truthfully unless someome makes a patcher that auto patches a Win7 iso, I'm not sure if it's worth the hassle. Appreciate the efforts though.