Hi Raul,
The installer behaves differently than the installed Windows OS, so I'd
only try on an already installed OS at first. If you need to do some
in-depth debugging, I'd also recommend using a checked build that has
debug symbols available. Beware that the installed version is very picky
regarding S3/S0ix, so the installation needs to match the target's
configuration.
To decode the bug check values and their parameters, see
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xa5--acpi-bios-error
The third parameter you posted decodes to _UID (that one is 4 char ASCII
stored as little endian number).
Regards,
Felix
_______________________________________________
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org
