Forum - Windows 7/Vista/Server 2008 » resolving an A5 BSOD in windows7 using grub2?

Win-Raid Forum (Drivers - Firmware - Modding) � OS related Topics � Windows 7/Vista/Server 2008 � resolving an A5 BSOD in windows7 using grub2?

Page 1 of 6 � Page 1 2 3 4 5 6 Page �

Topic settings

Print view

Jump to forum

General & Forum related Topics News / Announcements Forum-related Questions & Suggestions Off Topic Important Drivers (AHCI/RAID, NVMe, USB etc.) General: Storage Drivers (AHCI/RAID, NVMe and USB) Specific: Intel AHCI/RAID Drivers Specific: NVIDIA nForce Chipset Drivers (incl. AHCI/RAID) Specific: NVMe Drivers Other Drivers System Performance RAID Performance AHCI/NVMe Performance Solid State Drives BIOS Modding BIOS Modding Guides and Problems BIOS modules (PCI ROM, EFI and others) BIOS Modding Requests Reports: BIOS Modding Results Offers: Already modded special BIOSes Special Topics Intel Management Engine CPU Microcodes NVMe Support for old Systems Other Tools (not BIOS modding related) Interesting PC Hardware & Software OS related Topics Windows 11 Windows 8-10/Server 2012-2019 Windows 7/Vista/Server 2008 Windows XP/2000/Server 2003 DOS/Windows 3.X/9X/ME - Retro Gaming Other Operating Systems

#1 | resolving an A5 BSOD in windows7 using grub2? datum

Thu Oct 08, 2020 12:22 pm

@diderius6 @XPLives

I mentioned earlier in the XP on modern hardware thread that I am also getting an A5 BSOD in windows 7 (8.0 too, 8.1 works)

I remember from early last year when experimenting that it was possible to use grub2 to patch the ACPI Tables at boottime and I'm thinking if I can solve the A5 BSOD for windows 7 it might also help to get XP to boot as well.

any interest in experimenting with ACPI Table modding?

reply

#2 | RE: resolving an A5 BSOD in windows7 using grub2? datum

Thu Oct 08, 2020 1:16 pm

@infuscomus
I have interest. I remember talk with @daniel_k how he
modified his DSDT table in Bios so that he can use his normal acpi.sys from XP on his new Gigabyte board.
The problem is to find out in the acpi table, which line gives the BSOD. This line you can comment out or translate it to acpi 1b language, vocabulary.
And I remember from the very first beginning together with @Mov AX, 0xDEAD ,
that it was really hard work but after works with normal acpi.sys.
Move loads up at Git a procedure, how to load up a modified DSDT table during boot.
But this procedure is not so much comfortable ) ..
So, may be just to simplify this procedure for example with a skript which takes all the needed steps for you
Dietmar

reply

#3 | RE: resolving an A5 BSOD in windows7 using grub2? datum

Thu Oct 08, 2020 2:06 pm

@diderius6

my linux install might be giving hints to what the problem might be in its error logs

17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT5D], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT4D], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.WT4D], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT3D], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.WT3D], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT2D], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.WT2D], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT1D], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.WT1D], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.MT5C], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.MT4C], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.WT4C], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.MT3C], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.WT3C], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.MT2C], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.WT2C], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.MT1C], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.WT1C], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.MT5B], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.MT4B], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.WT4B], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.MT3B], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.WT3B], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.MT2B], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.WT2B], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.MT1B], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.WT1B], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.MT5A], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.MT4A], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.WT4A], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.MT3A], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.WT3A], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.MT2A], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.WT2A], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.MT1A], AE_ALREADY_EXISTS (20190816/dswload2-326)
17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.WT1A], AE_ALREADY_EXISTS (20190816/dswload2-326)

So I think I would need to go to my DSDT table, find these duplicate objects and comment them out? (how do I comment in an ACPI table?)

or otherwise those duplicate objects could be completely unrelated to the A5 BSOD.

reply

#4 | RE: resolving an A5 BSOD in windows7 using grub2? datum

Fri Oct 09, 2020 9:14 am

Dump of my TRX40 DESIGNARE ACPI Tables taken from RW-Everything.

Now to start learning how to mod them.

infuscomus has attached files to this post

TRX40_DESIGNARE_ACPI_TABLES.zip

reply

#5 | RE: resolving an A5 BSOD in windows7 using grub2? datum

Tue Oct 13, 2020 7:02 am

@diderius6

what is the GUID for acpi tables in a BIOS image?

I want to extract them with UEFITool and compare them to the output of RW-Everything to see if there are any differences.

reply

#6 | RE: resolving an A5 BSOD in windows7 using grub2? datum

Tue Oct 13, 2020 1:50 pm

@infuscomus

In newer Bios the DSDT table is at C118F50D-391D-45F4-B3D3-11BC931AA56D
But the other Acpi tables are hard to find.
I think @daniel_k knows more about those Guides
Dietmar

PS: I noticed a difference between RW-Everything and the loaded Acpi tables.
As far as I remember RW-Everything looks only in the Acpi tablets in Bios and not, which are really loaded.

reply

#7 | RE: resolving an A5 BSOD in windows7 using grub2? datum

Tue Oct 13, 2020 1:50 pm

iasl from early 2014 shows the AE_ALREADY_EXISTS error when I attempt to disassemble my DSDT

iasl-win-20140114>iasl.exe -d DSDT.bin

Intel ACPI Component Architecture
ASL Optimizing Compiler version 20140114-32 [Jan 14 2014]
Copyright (c) 2000 - 2014 Intel Corporation

Loading Acpi table from file DSDT.bin - Length 00062005 (00F235)
Acpi table [DSDT] successfully installed and loaded
Pass 1 parse of [DSDT]
ACPI Warning: Invalid character(s) in name (0x2E5C1501), repaired: [****] (20140114/utstring-713)
ACPI Warning: Invalid character(s) in name (0x2F5C1501), repaired: [****] (20140114/utstring-713)
ACPI Error: ACPI Warning: Invalid character(s) in name (0x2F5C1501), repaired: [****] (20140114/utstring-713)
[****] Namespace lookup failure, AE_ALREADY_EXISTS (20140114/dswload-436)
ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20140114/psobject-304)

I think I will need to fix this to resolve the A5 BSOD in windows 7.

reply

#8 | RE: resolving an A5 BSOD in windows7 using grub2? datum

Tue Oct 13, 2020 2:39 pm

@infuscomus

The error AE_ALREADY_EXISTS happens, when you load the same part of an DSDT file twice.
This means, that you have not find the correct one and only DSDT table.
Also try a newer version of iasl
Dietmar

reply

#9 | RE: resolving an A5 BSOD in windows7 using grub2? datum

Tue Oct 13, 2020 4:34 pm

iasl 20160108 can disassemble my DSDT but can not reassemble.

iasl 20180105 can disassemble and reassemble my DSDT without any errors.

However ideally I would like to be able to compile my DSDT with version 20121114 as the DSDT from my known working AB350 K4 can be compiled using this version.

TL;DR I would like to be able to compile my TRX40 DESIGNARE DSDT table using version 20121114.

reply

#10 | RE: resolving an A5 BSOD in windows7 using grub2? datum

Tue Oct 13, 2020 7:54 pm

I managed to get iasl 20160108 to reassemble my DSDT - I will try a test of it tomorrow

infuscomus has attached files to this post

TRX40_DESIGNARE_DSDT_modded_ATTEMPT1.zip

reply

#11 | RE: resolving an A5 BSOD in windows7 using grub2? datum

Tue Oct 13, 2020 8:01 pm

@infuscomus

Be very careful when you put a new DSDT table to your real Bios.
I "succeed" to get an unbootable compi via this way, no LED blinking, just nothing;))..
Only because I make a working full Bios image with Epromer (I tried 4 different),
I can give life back to this compi
Dietmar

reply

#12 | RE: resolving an A5 BSOD in windows7 using grub2? datum

Tue Oct 13, 2020 8:08 pm

@diderius6

I'm going to attempt to use grub2 to patch the ACPI tables - no risk of a bad BIOS flash.

I will know if the ACPI patching is working when ubuntu no longer has any ACPI errors in the log file.

reply

#13 | RE: resolving an A5 BSOD in windows7 using grub2? datum

Wed Oct 14, 2020 6:32 pm

@diderius6

I can confirm that the modded DSDT Table was loaded using grub2 by checking the log file after I booted into ubuntu

Oct 14 23:19:54 ubuntudde kernel: [ 0.000000] ACPI: DSDT 0x00000000AB21DE50 00E5C3 (v02 AMD A M I 03242016 INTL 20121114)

I still have ACPI errors but at least I know the modded table loaded successfully.

reply

#14 | RE: resolving an A5 BSOD in windows7 using grub2? datum

Wed Oct 14, 2020 8:08 pm (Last edited: Wed Oct 14, 2020 8:14 pm)

@infuscomus

With If (OSYS >= 0x07D6) you can comment lines out for XP in DSDT.
Which lines you have to comment out you can see at the BSOD, that acpi gives.
I think, with the acpi.sys from outerspace ) mostly 64 bit integers can make problems
or even, that acpi.sys is not loaded at all
Dietmar

PS: With my new minixp you can check one by one, which driver gives the BSOD.
But this is crazy hard work. When you have a working XP for your compi (without acpi, just "Standard PC")
I can try to mod this for acpi for you.

Try different boot devices: Storahci, Storport, USB, boot via S4e methode (works always).

reply

#15 | RE: resolving an A5 BSOD in windows7 using grub2? datum

Fri Oct 16, 2020 9:38 am (Last edited: Fri Oct 16, 2020 10:10 am)

@diderius6

Windows 7 A5 0x11 0x8 BSOD referenced a timestamp of 20190509

checking my linux logs I can see this time stamp matches the SSDT tables on my system - with the signatures SHAKTOOH and BIXBY ?

Oct 16 06:25:02 ubuntudde kernel: [ 0.005453] ACPI: SSDT 0x00000000AB22C457 001467 (v01 AMD SHAKTOOH 00000001 INTL 20190509)

Oct 16 06:25:02 ubuntudde kernel: [ 0.005457] ACPI: SSDT 0x00000000AB22DD68 001F44 (v01 AMD SHAKTOOH 00000001 INTL 20190509)

Oct 16 06:25:02 ubuntudde kernel: [ 0.005467] ACPI: SSDT 0x00000000AB23E7CC 000024 (v01 AMD BIXBY 00001000 INTL 20190509)

Oct 16 06:25:02 ubuntudde kernel: [ 0.005474] ACPI: SSDT 0x00000000AB23EB9C 003918 (v01 AMD AMD AOD 00000001 INTL 20190509)

reply

Tower server gone desktop � � driver for nforce3+ATI HD3850 on Windows 7 64 bit

Page 1 of 6 � Page 1 2 3 4 5 6 Page �

Please enter a reason for warning.