@infuscomus

The Bsod error massage in Win7 means, that the acpi database cant be loaded, means no acpi at all.

Via search string AMD SHAKTOOH 00000001 INTL with Google I found

a webpage with similar ACPI problems.

They make a new DSDT for Macintosh and integrate them during boot. I downloaded their DSDT file named
libiomp5.dylib but I do not know how to work with it.

https://www.macos86.it/topic/3307-trx40-...-better/page/2/

As far what I understand, threadripper can have problems with the connected SSD and the GPU.
Change to normal 2 TB harddisk and try other videocard
Dietmar

@diderius6

So I recompiled all of my ACPI tables - each one with a different date iasl compiler so I could catch which table is causing the A5 BSOD in windows 7 (A5 0x11 parameter4 has the date of the compiler in it)

I've narrowed it down to this specific table - attached

Now I need to figure out what inside this table is causing the BSOD.

@infuscomus
In Linux there is something like acpi debug.
This we need, because until now we do not know at all,
what is going on.
On the website for Macintosh they just look, which device is not loaded
Dietmar

PS: I decompiled your file with -d iasl. But I see no advice there.
And I think, that SSDT is build from DSDT, so we need to fix DSDT.
Just now I look at the Source Code from acpi.sys for XP SP1,
if I can hack "Acpi Database cant be loaded" and build acpi.sys new.

@diderius6

ancient iasl compiler from 2005 shows some errors on reassembly -

@infuscomus

I found a Tutorial how to make your own SSDT

https://dortania.github.io/Getting-Start...path-of-the-gpu

Dietmar

@diderius6

I did not have much time to test today, but I did check whether or not resolving these "Value below valid range " errors in the 2005 compiler would resolve the BSOD - Unfortunately it did not, but the problem is definitely somewhere in this table since the BSOD again had the 20051117 signature.

@infuscomus

Make a try under XP with the new acpi.sys for XP SP1 here
Dietmar

@diderius6

Your new acpi.sys did not work for me - still stuck at "Setup is Starting Windows"

@infuscomus

I take a look, how we solve the BSOD on Ryzen for XP64.
We check one by one all the Acpi Bsods and solve them.
This will work for Threadripper board also, the question is here how to notice the exact Bsods
when nothing is given out. Have you tried XP there without any acpi?
Because the Bsod comes after "Setup is Starting Windows" I still think,
that the compi has a problem with the connected disks.
Make try only with only one harddisk <=2TB connected, put out your graphikcard and disable in Bios as much as possible.
When you succeed to install XP without any acpi, make next try with different acpis
Dietmar

@diderius6

without ACPI it seems to go a little further - mouse and keyboard turn off - but it still gets stuck at "Setup is Starting Windows"

I'll disconnect the disks again.

Threadripper does not have an iGPU, So I need to have something installed in the top pcie slot to get any image output.

@infuscomus

"without ACPI it seems to go a little further - mouse and keyboard turn off - but it still gets stuck at "Setup is Starting Windows"
Then the problem is not only related in acpi. Put an old graphicard in, disable nearly all in Bios
and make try without any acpi (via F5, "Standard PC")
Dietmar

PS: You can make also a try with the old graphikcard in another (!) Pci-e slot.
I remember about the for Macintosh fixed DSDT, that this board has problems with shared lines.
Such a problem with shared lines I have had also with my Baytrail board.

@diderius6

OK, I'll need to go buy an old GPU then - would GTX 700 series be OK?

@infuscomus
yes, any will work
Dietmar

@diderius6

If you have time tomorrow, can I get a copy of each one of your ACPI tables from your AMD Ryzen system? (assuming you still have it?) - I'd like to compare them to see the differences between them.

@infuscomus

Yes I have, but those tables will not help you.
Even between nearly identic compis you cant share DSDT.
You can look at the Macintosh people, what they changed.
And best would be to set up a Windbg connetion.
For this use an XP without any Acpi from an other compi on a harddisk and connect this to your compi
Dietmar