ASUS P5QPL-AM w/ Coreboot v. Windows 10: STOP 0xa5 BSOD
Hi There :)
I've Been Fiddling Quite a Bit With This Issue, However, None of The Paths I Took Led Me To a Solution. Help, Please ? :)
The Vendor F/W Enables a Windows 10 x64 1909 OS To Boot,
However It's NO Usable For My Purpose - As It Has NO Support for Booting from PCIe/NVMe Drives & I Really Wish To Keep It Simple (This System Is Meant To Be Donated To Those Who Can't Afford Buying a Computer, So No Wizard Should Be Required For a Future OS Re-Installation...).
Coreboot F/W, OTOH, Only Enables a Windows OS - Both Windows 7 x64 pre-SP2 & Windows 10 x64 1909 - To Produce a "STOP 0x000000A5" BSOD on Boot ( Parameter1 = 0x0000000D ; See: https://support.microsoft.com/en-us/help/314830/stop-error-code-0x000000a5-error-when-you-are-installing-windows-xp ).
Hardware Specs. -
Mainboard: ASUS P5QPL-AM
CPU: Intel Xeon L5420
RAM: 4GB (2x2GB)
SSD: Kingston A2000 250GB PCIe/NVMe (on PCIe*16/PEG Port)
Firmware Specs. -
Coreboot: 4.10-455-g44449192ab from 27/08/2019 & 4.11-1706-g34473ea6c9 from 20/03/2020
I Also Have The Means To Externally Re-Flash This Mainboard F/W IC - If Needed.
#2 Updated by Paul Menzel 2 months ago
Please try to transcribe the full error next time – I removed some zeros from the parameters.
0xD, 0xFFFFFA8004753360, 0x000000003353505F,0x0
Here is the error description.
(0x0000000D, Parameter2, Parameter3, Parameter4):
There are many objects that must be defined in the ACPI namespace, and one or more of these was not found. This error generally occurs if either the _HID or _ADR object is missing. An _ADR is used to define the address of a device on its parent bus. The _ADR is a static address that defines slot numbers for devices that reside on any number of bus types, including EISA, floppy, IDE controller, IDE channel, PCI, PCMCIA, and CardBus. The _HID contains objects that supply the operating system with Plug and Play hardware ID for a device. Technically, these objects are optional, but they absolutely must be present to describe any device that is enumerated by an ACPI driver.
Please do the following:
- Please attach
- Please attach the coreboot logs, for example retrieved by
cbmem -1or from the serial console.
- Please start GNU/Linux (some latest version), and attach the Linux kernel console.
- In GNU/Linux, please install FWTS (https://wiki.ubuntu.com/FirmwareTestSuite), and run it, and look out for errors.
PS: Unrelated, it’d be nice if you uploaded the Linux logs to the board status repository. See
- File defconfig.ASUS-P5QPL_AM.debug added
- File console.log added
- File coreboot-ASUS_P5QPL-AM_20200321-1-debug.dmesg.out added
- File coreboot-ASUS_P5QPL-AM_20200321-1-debug.fwts-result.zip added
Dear Paul, 1st & Foremost, I'd Like To Thank You For Taking The Time To Look Into This Issue: a Working Solution Will Enable Me To Release This System, That I Worked Tirelessly To Bring Together, To Some Underprivileged K-12 People :)
The Additional Info. Requested Is Attached (Lacking a USB<>RS-232 Adapter On Hand, I Opted To Use Coreboot's SPI Flash Based Console Logging).
- File fwts-result.GIGABYTE-GA_G41M_ES2L.zip added
- File defconfig.GIGABYTE_GA-G41M-ES2L.debug added
- File coreboot-GIGABYTE_GA-G41M-ES2L-20200321_1_debug.console.log added
- File coreboot-GIGABYTE-GA_G41M_ES2L_20200321-1-debug.dmesg.out added
FWIW, Here's Also The Same Info. - from The Aforementioned Other Mainboard: Gigabyte GA-G41M-ES2L ( w/ Coreboot 4.11-1728-g96cf680c3d from 21/03/2020 ), On Which Windows 10 x64 1909 Successfully Boots.
- File IMG_20200321_174957_HDR-A.jpg added
- File coreboot-ASUS_P5QPL-AM_20200321-1-debug.seabios_debug_8.console.log added
- File .seabiosconfig.defconfig.debug added
[ w.r.t. Mainboard: ASUS P5QPL-AM ]
Updated Coreboot Console Log: SeaBIOS Now Built w/ CONFIG_DEBUG_LEVEL=8 (Earlier It Was Set To '1').
Updated Windows 7 x64 BSoD Details: Stop Error Code=0xA5 (as Before), Parameter1=0xD, Parameter2=0xFFFFFA8004815A00, Parameter3=0x000000003353505F, Parameter4=0x0 .
#6 Updated by Nico Huber 2 months ago
0x3353505F is ASCII and translates to "_PS3". That's a power-state function which seems to be missing for the Super-I/O chip (which is one of the major differences between these boards).
Please try this patch, maybe we are lucky:
- File IMG_20200322_031105_HDR-A.jpg added
Dear Nico, Y'all Have No Idea How Much I Appreciate Your Kind Willingness To Assist Me Bringing a Good Working Computer To One In Need ! :)
& As Per The Proposed Patch, It Resulted In The Same BSoD on Boot, Only With Parameter2=0xFFFFFA8004815A90 .
- File Untitled.jpg added
Dear Nico, It Was, Actually, a Pointer In The Right Direction:
Replacing The File 'src/mainboard/asus/p5qpl-am/acpi/superio.asl' with a Dummy (Merely an Empty File), Did The Trick - Finally ! :)
I'm Currently Still Able & Willing To Test a (Patched) ACPI SuperIO Block, If You're Willing To Try Along.
#13 Updated by Paul Menzel 2 months ago
Great that Nico was able to come up with a fix so quickly.
In the board status archive, I saw, that you select the unneeded
DRIVERS_PS2_KEYBOARD=y in coreboot. GRUB, SeaBIOS and TianoCore have their own drivers for that, so you do not need that.
Additionally, the archive misses the logs from coreboot and Linux. If the fix is in the master branch, it’d be great if you could do another run of