BSOD upon first boot after install - Acpi.sys

kreemerz

Member
I created my custom iso using the settings in the attached file.
Install went well, was fast.
But when it came time for first boot, it throws the BSOD referencing acpi.sys?

I googled and googled. hardware? virus? driver?

unsure what happened.

When I did a clean install using Win11 non-modified iso, it booted fine... so I'm not sure what I ticked that could be causing this acpi/bsod error.

Dell Win 11 laptop
 

Attachments

  • KLNexus.xml
    11.3 KB
Last edited:
ACPI.sys is a boot-critical driver for basic power management. BSOD on modern Windows is always triggered by a bad driver.

Why are you including ASUS drivers on a Dell? Yes, PC's have OEM chipsets and drivers are drivers, but use the Dell-supported drivers first before swapping them for non-Dell equivalents.
 
ACPI.sys is a boot-critical driver for basic power management. BSOD on modern Windows is always triggered by a bad driver.

Why are you including ASUS drivers on a Dell? Yes, PC's have OEM chipsets and drivers are drivers, but use the Dell-supported drivers first before swapping them for non-Dell equivalents.
When I'm running the ntlite app, I'm usually running it from my source Asus machine. When I run the 'driver updater' section, I assume it downloads all the updates based on the machine I'm running it from.

I'm not sure how to remedy that issue.
 
Import host feature is intended to help you build a new image which will run on the exact same PC.

If you know the target PC's model, then download and extract all its supported drivers into a separate folder. Now import the extracted driver folder from Drivers.

Sometimes you can get lucky and include extra drivers for two or more different PC's in the same image. But other times, it's possible that Setup matches the wrong drivers from the image and they're not fully compatible. There's a "best fit" algorithm based on HW ID's (vendor strings) and it doesn't always work.
 
Import host feature is intended to help you build a new image which will run on the exact same PC.

If you know the target PC's model, then download and extract all its supported drivers into a separate folder. Now import the extracted driver folder from Drivers.

Sometimes you can get lucky and include extra drivers for two or more different PC's in the same image. But other times, it's possible that Setup matches the wrong drivers from the image and they're not fully compatible. There's a "best fit" algorithm based on HW ID's (vendor strings) and it doesn't always work.
So to run the same preset xml file, do I need to rebuild the entire configuration, or just untick some drivers in the 'drivers' section?
 
You can load the preset, and under Drivers Select all and Remove. Save this preset version, and remake the image from a clean ISO.
 
Back
Top