Aspire V3-772G Same BDOS when booting normally or from a bootable flash drive

Alzen
Alzen Member Posts: 2 New User
edited March 2023 in Aspire Laptops

I have had this “Page default in non-paged area” on booting for a few days now, and couldn't fix it using several troobleshooting guides. Other Windows services are affected (DISM and SFC finding but unable to repair corrupted files, Windows update not working, games not lauching, ..).

So I figured I'd clean install Windows using a bootable flash drive, but on boot the same BSOD instantaneously appears after the Acer logo, although it's weirdly zoomed in and pixelated. So my question is, why, and how to fix this ?

To clarify :

  • Model & OS : Aspire V3-772G, fairly old, but running on Windows 10 for years without problems so far. System is x64.
  • Drivers are up to date. No recent hardware added
  • BIOS version is 1.13 (10/2013), last version available on Acer support is 1.15 (04/2014). I'm not confortable updating my BIOS without a good reason to (is it one ?)
  • RAM is fine according to Memtestx86
  • BIOS is UEFI, partitions are GPT, flash drive is FAT32
  • Bootable flash drive created using both Windows MCT and Rufus, with automatic settings for this computer. (I tried repairing Windows using the MCT tool, to no avail).
  • Fast and secure boot are disabled in boot settings and BIOS. F12-boot is enabled ; USB HDD is selected 1st in boot order
  • The issue seems to have appeared since the last Windows updates (KB4023057, KB5012170, KB5022083), installed in a span of 2 days around the time I got the issue. But I couldn't find any related issues regarding my BSOD.

Furthermore, I tried using Legacy mode, and it worked (installation media was launched) until I have to choose on which partition Windows is to be installed : drive being in GPT and BIOS in Legacy, it's not working. But UEFI gives a BSOD so … I sense there's something here, but I'm missing it. Any help ?

PS : I have read these topics here and especially there, but the .png in this last topic is damaged (I don't get what screen I'm supposed to press ShiftF10 on), and I don't seem to be able to access a command prompt before the BSOD appears anyway.

[Edited the thread to add model name]

Answers

  • Puraw
    Puraw ACE, Member Posts: 13,188 Trailblazer

    Personally I would stay with W7 or W8.1, to force a 9 year old sytem to work on Windows10 may results in all sorts of compatibility issues, like updating and booting.😉

  • Alzen
    Alzen Member Posts: 2 New User

    Thanks, but as I've said I've been running W10 for years, I'm not “forcing” it. Plus, Microsoft just stopped supporting W8.1, so it's not a long-term soluton.
    All I want is to be able tu run a bootable flash drive in UEFI without this BSOD. Does anyone have an idea why it works in Legacy but not in UEFI ?