Win-Raid forum: Windows XP, 2003 x32 on modern hardware

Part 1 ◄ Part 2 ► Part 3 ► Part 4 ► Part 5

## Page 111

#1651 | XPLAKE8175 | Diderius6's ACPI patch only works on fat32 formatted hdd and no plugged usb devices except format usb (textmode setup recognizes as CD) during textmode setup.
#1652 | XPLAKE8175 | XP mce and 64 bit iso exceeds CD size.

#1653

infuscomus

> Zitat von ⇗ XPLAKE8175 im Beitrag ¶ #1651

> Diderius6's ACPI patch only works on fat32 formatted hdd

not true, it works on NTFS just fine

> Zitat von ⇗ XPLAKE8175 im Beitrag ¶ #1652

> XP mce and 64 bit iso exceeds CD size.

there is a 64bit version of media centre edition? I was not aware of this
just use the normal non-mce 64bit iso.

#1654 | kukonosau | I downloaded original ISO. Also errors. I renamed file acpix64-patched.sys into acpi.sys. Next I write in command line "makecab acpi.sys" and get file acpi.sy_. Put file acpi.sy_ in folder AMD64. I check put acpi.sys in DRIVER.CAB... As a result, the same error "the file acpi.sys is corrupted" or BSOD if put other acpi files.
#1655 | infuscomus | ⇗ @kukonosau try either the checksum-acpix64-patched.sys or the acpi.sy_ I included I tested with en_win_xp_pro_x64_with_sp2_vl_x13-41611.iso
#1656 | kukonosau | I tested all 3 files acpi and different iso image Windows XP, but get errors "the file acpi.sys is corrupted" or BSOD IR_NOT_LESS_OR_EQUAL. May be, BSOD 0x0000000a.
#1657 | XPLAKE8175 | XP MCE 2005 English and XP Professional SP3 Turkish worked very well on NTFS formatted partition with diderius6's acpi.

#1658

infuscomus

> Zitat von ⇗ kukonosau im Beitrag ¶ #1656

> but get errors "the file acpi.sys is corrupted"

I can not reproduce this message on my end

> Zitat von ⇗ kukonosau im Beitrag ¶ #1656

> IR_NOT_LESS_OR_EQUAL. May be, BSOD 0x0000000a.

Thats a driver failure - did it show you the sys file that failed?

#1659 | XPLAKE8175 | ⇗ @kukonosau Maybe you can plug the installation media to usb 2.0 if the PC has USB 2.0 ports. Please don't plug USB devices onto usb 3.0 ports.
#1660 | kukonosau | Sorry, acpi is worked!!! But only with fat32 disks(((
#1661 | kukonosau | No, this is problem ntfs disks!!! ACPI x64 worked only with fat32 disks.
#1662 | infuscomus | ⇗ @kukonosau Glad to hear it worked for you! only working for fat32 is strange - though I have my doubts that it is an ACPI related problem, it's probably a USB or SATA disk problem.
#1663 | kukonosau | Errors 7E, 7B, A5 and so on... FAT32 also doesn't working normally. Install cancel after copy files(
#1664 | infuscomus | ⇗ @kukonosau BSOD after reboot? replace acpi.sys in SP2.CAB or DRIVER.CAB
#1665 | kukonosau | BSOD about viruses hardware, but I integrated drivers Asmedia 106x SATA Controller!!!

## Page 112

#1666 | kukonosau | XP 32-bit working normally with diderius acpi!!!

#1667

canonkong

⇗ @daniel_k ⇗ @diderius6
For AMD X570/3000series USB host 149C, I tested all usb drivers, only Etron usb driver can work very well. Other driver will meet 019 02C 01E BSOD or usb disk cannot work.
And maybe intel usb also can fix if we find the problem out.
Maybe other driver need to find out the breakpoint and use nop to stop it.
Modify like this: https://forum.videohelp.com/threads/390651-Way-to-make-Intel-UHD- 620-graphics-driver-to-works-in-windows-7-(no-crash)

#1668 | daniel_k | ⇗ @canonkong If Etron works, that's OK, it is really hard to fix those errors, specially if one has no hardware to test (I don't have any AMD Ryzen system). Sorry.
#1669 | daniel_k | ⇗ @diderius6 Did you try any of those drivers? One is SCSIPORT, modded and the other one is STORPORT, no mod needed. Unfortunately neither of them works with "real" Intel systems, but works on Virtual Box and supports up to 8 ports. PS: Storport build 402 (included) works, with the older .337 filter driver, please try it as well.
#1670 | diderius6 | ⇗ @daniel_k The ahcix86.sys does not work on AMD board asrock fatal1ty ab350 gaming k4 (DEV_43B7 and DEV_7901) gives code 10 Dietmar

#1671

diderius6

⇗ @daniel_k
But, waaaaaooohh ,
the amd_sata.sys together with newest storport.sys and amd_xata.sys
works generic on AMD board asrock fatal1ty ab350 gaming k4 (DEV_43B7 and DEV_7901)
with Ryzen 3700x cpu.
And the amd_xata.sys gives AmdXataTrimSupport on AMD boards, so TRIM driver is loaded and started!
But still I do not know, how I can test, if TRIM works in XP
Dietmar

#1672

diderius6

⇗ @Mov AX, 0xDEAD
With TxBENCH I can now use the Trim command in XP here for Samsung 860 EVO SSD on the AMD board.
The operation is called "optimation on unused area of the SSD".
It works on ntfs file system.
My question is, how I can test, that TRIM has worked with success on this SSD
Dietmar
EDIT: Using Samsung Magician from win7 for to check TRIM on the Samsung 860 EVO SSD
kills the XP installation there.

#1673 | canonkong | ⇗ @diderius6 Use ADATA SSD ToolBox, it can support other ssd trim on xp.
#1674 | diderius6 | ⇗ @infuscomus "I tested with en_win_xp_pro_x64_with_sp2_vl_x13-41611.iso" I want to check your modded acpi.sys on this XP 64 bit. Do you have a key for it Dietmar
#1675 | infuscomus | ⇗ @diderius6 i PMed you a key

#1676

diderius6

⇗ @infuscomus
First I try to install XP 64 with modded acpi.sys on the AMD board asrock fatal1ty ab350 gaming k4 with 3700x cpu.
Then comes BSOD 0xA IRQL_NOT_LESS_OR_EQUAL. This means, that there is a not working kernel mode driver.
After this I disable really everything in Bios.
On next try I get BSOD 0x7E (xxx, 0xC0000005,yyy) which may be acpi related.
After this, I connect the CD rom drive to the nice EVGA z390 dark board (intel).
There I am just now installing this XP 64 bit and I hope, that I can put this installation after
to the AMD board asrock fatal1ty
Dietmar

#1677

daniel_k

> Zitat von ⇗ diderius6 im Beitrag ¶ #1671

> @daniel_k
> But, waaaaaooohh ,
> the amd_sata.sys together with newest storport.sys and amd_xata.sys
> works generic on AMD board asrock fatal1ty ab350 gaming k4 (DEV_43B7 and DEV_7901)
> with Ryzen 3700x cpu.
> And the amd_xata.sys gives AmdXataTrimSupport on AMD boards, so TRIM driver is loaded and started!
> But still I do not know, how I can test, if TRIM works in XP
> Dietmar

Glad to know it works.
Version 1.2.1.337 is official for Server 2003.
Did you try both amd_sata.sys and amd_xata.sys from the same version?
Then running amd_sata.sys from 1.2.1.402 with amd_xata.sys from 1.2.1.337?
It's important to make sure the older amd_xata.sys didn't kill your XP install.

#1678 | diderius6 | ⇗ @daniel_k Until now I tested only both from the same version 1.2.1.337. I will also test with newer version amd_sata.sys 1.2.1.402 mixed with amd_xata.sys 1.2.1.337 Dietmar
#1679 | daniel_k | ⇗ @diderius6 Ok, please tell me what is the USB3 driver for XP which works properly with your Ryzen board? I'd like to take a look at it.
#1680 | diderius6 | ⇗ @daniel_k For me works only for all USB on AMD boards with Ryzen the USB driver from post 1095, where I changed all the names to usbstor Dietmar

## Page 113

#1681

canonkong

⇗ @diderius6 ⇗ @daniel_k
But the driver will bsod when you uninstall it. And now I don think we find any prefect driver for AMD boards and Ryzen with 149C. VIA will meet 01E BSOD sometimes. Intel/AMD 2.0.0.48 will meet 02C BSOD when install/uninstall sometimes, ASMeidia,TI can not work for U disk.
So I think use windbg to find out the breakpoint and use nop to stop it.
Modify like this: https://forum.videohelp.com/threads/390651-Way-to-make-Intel-UHD-620-graphics-driver-to-works-in-windows-7-(no-crash)

#1682 | daniel_k | ⇗ @canonkong We are talking about Windows XP only.
#1683 | canonkong | ⇗ @daniel_k Xp also have this bsod.

#1684

daniel_k

⇗ @diderius6
Let's clarify some things.

> Zitat

> On 149C the etronxhci7052.sys works at once.
> It is Ryzen 3700x on the nice AMD board asrock fatal1ty ab350 gaming k4

In this case, you mean etronstor.sys works, correct?
No need to rename etronstor.sys to usbstor.sys?

> Zitat

> EDIT: With my modded driver in post 1095 it is other. ALL USB on Ryzen 1700x and Ryzen 3700x works on
> asus prime x570-pro and asrock fatal1ty ab350 gaming k4 board under XP 32 bit.

Is it really stable?
Did you do the same tests you did with my modded Intel USB driver?
Boot from USB, run benchmarks and so on?
I'm asking this because canonkong says it is not stable?

#1685 | canonkong | ⇗ @daniel_k ⇗ @diderius6 These modified drivers have a certain probability of BSOD during instal or uninstal, but once installed success, they will not encounter any problems. Except that the VIA driver appears 01E BSOD in use sometimes.
#1686 | XPLAKE8175 | I installed VESA vbe miniport from ⇗ https://bearwindows.zcm.com.au/vbemp.htm for my laptop. And I tested some 2d tests and half life 1 test. It works pretty well. For Broadwell+ laptops, I recommend this driver.
#1687 | daniel_k | Does anyone have Fresco Logic driver 2.14.0.76? Interesting it included a generic XHCI class code device ID. Unfortunately I can't find it, was made available for Asrock 890GM Pro3 at the time ASRock ran an FTP server. Station-drivers had it as well, but now only 3.x versions are available.

#1688

diderius6

I succeed to install XP 64 on the EVGA z390 dark board with the modded acpi.sys from infuscomus,
with working USB.
Then I set in registry intelppm start=4 and connect
the harddisk to the AMD fatalty board with Ryzen 3700x.
But I get BSOD 0xA even again I enabled / disabled everything in Bios
Dietmar
⇗

#1689 | infuscomus | ⇗ @diderius6 do you think i jumped the wrong function?

#1690

diderius6

⇗ @infuscomus
Your acpi.sys works on the EVGA z390 board.
The acpi.sys from ⇗ @skullteria gives there BSOD 0x7B. They are both from the same nature Longhorn 5048.
I also tried the unmodded 5048 acpi.sys, gives the same BSOD 0xA.
I also make a try, just combinating this both acpi.sys yours and from skullteria,
but results also in BSOD 0x7B.
I integrated with nlite the asm106 driver, which works to 100% (see the EVGA dark board).
I think, it is a problem with some hardware on the AMD board.
Have you installed this XP 64 successfull with ACPI on your compi
Dietmar

#1691

diderius6

⇗ @daniel_k
To be honest, the Intel USB driver I test much more intensive.
But on 2 boards from AMD all was ok with the etronstor.sys driver,
no need to rename. But all USB devices at once where on those 2 AMD boards
only recogniced with the driver from my post 1095
Dietmar
PS: I did not recognice a single BSOD from USB on AMD board. I do not get any "unknown device".

#1692

diderius6

⇗ @daniel_k
Here is the USB driver 2.14.0.76 from Fresco 32 bit
Dietmar
diderius6 has attached files to this post

- ⇗ 0076_32bit_xp.rar

#1693 | infuscomus | ⇗ @diderius6 I also get same BSOD 0xA I thought perhaps I jump the wrong function for ACPI - but it is not A5 BSOD, so just IRQ problem?
#1694 | daniel_k | ⇗ @diderius6 Thanks, do you have the whole package with the x64 driver? Did you ever try it with an AMD system? Or Intel? Will do it later if you don't do it first. Firstly, will fix the Etron driver so it will work on both 149C and 43BB devices.
#1695 | diderius6 | ⇗ @daniel_k No, I never tried. I have also an *.msi installer for 64 bit, but during unpack I notice, that it is still 32 bit, 100% identic to the 32 bit version, so I think, there has never been an XP64 version of it Dietmar

## Page 114

#1696

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #1692

> USB driver 2.14.0.76 from Fresco 32 bit

> Zitat

> [FRESCO.NTx86]
> %FLxHCIc.DRVDESC%= FLxHCIc, PCI\CC_0C0330

fresco is WDF based, this maybe means very slow init of usb devices (like VIA) , but this .inf is funny :)

#1697 | diderius6 | ⇗ @Mov AX, 0xDEAD Yes, very funny. On my Intel PC this crazy Fresco driver думает , что он IEEE 1394 Bus-Hostcontroller Dietmar PS: On the AMD fatalty board, the Fresco driver froze the compi, so no good choice.

#1698

daniel_k

> Zitat von ⇗ diderius6 im Beitrag ¶ #1697

> PS: On the AMD fatalty board, the Fresco driver froze the compi, so no good choice.

That's a lost cause.

#1699 | daniel_k | ⇗ @diderius6 Please try this, specially on the X570 board. I've seen how the drivers behaves in your modded driver. The more important change, is that etronstor.sys must work.
#1700 | daniel_k | ⇗ @Mov AX, 0xDEAD Are you good at assembly? If so, can you help me, please? I'm trying to patch RSTe 4.7, managed to change about 100 instances of an import into another, but I'm puzzled with one instance.
#1701 | diderius6 | ⇗ @daniel_k For the new Etron driver is the same true as before: DEV_149C works, but DEV_43BB (with USB2.0 port also) not, even it is installed Dietmar

#1702

daniel_k

> Zitat von ⇗ diderius6 im Beitrag ¶ #1701

> @daniel_k
> For the new Etron driver is the same true as before:
> DEV_149C works, but DEV_43BB (with USB2.0 port also) not,
> even it is installed
> Dietmar

Thanks.
A new round of test 2, 3 and 4, please try.
One of them should hopefully work.

#1703

daniel_k

The following is easy, almost 99.9% of them:

    .text:00011888                 push    4
    .text:0001188A                 lea     eax, [edi+11h]
    .text:0001188D                 mov     byte ptr [edi+15h], 0
    .text:00011891                 push    eax
    .text:00011892                 movzx   eax, byte ptr [edi+10h]
    .text:00011896                 push    4 -> easily kill by nops
    .text:00011898                 lea     eax, [ebx+eax*4]
    .text:0001189B                 push    eax
    .text:0001189C                 call    ds:memcpy_s -> memcpy

However, this one, I don't know how to patch:

    .text:00067712                 push    eax
    .text:00067713                 mov     eax, [esi]
    .text:00067715                 push    [ebp+arg_0]
    .text:00067718                 call    dword ptr [eax+0Ch]
    .text:0006771B                 movzx   eax, ax
    .text:0006771E                 mov     ecx, esi
    .text:00067720                 push    eax
    .text:00067721                 mov     eax, [esi]
    .text:00067723                 call    dword ptr [eax+8]
    .text:00067726                 push    eax
    .text:00067727                 call    ds:memcpy_s -> memcpy

There are only 2 push'es and memcpy_s requires 4 parameters, what should I kill?
Can a call return value be considered a push <parameter>?
From Microsoft's reference:

    errno_t memcpy_s(
       void *dest,
       size_t destSize, -> this parameter should be killed
       const void *src,
       size_t count
    );

    void *memcpy(
       void *dest,
       const void *src,
       size_t count
    );

Please note that in assembly, the parameter order is reversed:

    push size_t count
    push const void *src,
    push size_t destSize, -> this parameter should be killed
    push void *dest,
    call memcpy_s

#1704 | diderius6 | ⇗ @infuscomus I test your acpi.sys for XP64 also on the x570 board with Ryzen 1700. Nearly exact the same BSOD 0xA happens there Dietmar
#1705 | diderius6 | ⇗ @daniel_k The amd_sata.sys 1.2.1.337 driver does not work, version 1.2.1.402 also not on x570 board Dietmar EDIT: This is a mistake. The driver works also on x570 board.

#1706

diderius6

⇗ @daniel_k
Test 2, 3, 4 do all the same:
The Etron Usb driver recognices DEV_149C
but does not work for DEV_43BB . It installes, but no USB device is then recogniced,
Dietmar
PS: For DEV_149C device is Etron driver good and for DEV_43BB is AMD driver good,
see attached.
diderius6 has attached files to this post

- ⇗ AMD USB 3.1 drivers v1.0.5.3 WHQL.rar

#1707 | canonkong | ⇗ @diderius6 Did you have test uninstal Etron usb driver?

#1708

daniel_k

> Zitat von ⇗ diderius6 im Beitrag ¶ #1705

> @daniel_k
> The amd_sata.sys 1.2.1.337 driver does not work, version 1.2.1.402 also not
> on x570 board
> Dietmar

I believe this one should work.
Unfortunately it is old and surely don't properly support SSD features.
There are SCSIPORT and STORPORT versions, please try both.

#1709

daniel_k

> Zitat von ⇗ diderius6 im Beitrag ¶ #1706

> PS: For DEV_149C device is Etron driver good and for DEV_43BB is AMD driver good,
> see attached.

Hmm, so for X570 AMD's driver works just fine?
So, I'm done with that.
No problems at all? Restarting Windows, shutting down or enabling/disabling the Host controller in Device Manager.

#1710

diderius6

⇗ @canonkong ⇗ @daniel_k
I install, deinstall every USB driver more than 10 times.
Nothing bad happens.
In XP, you have to try this always few times,
but in the end all USB deinstalls if you want
without crash
Dietmar

## Page 115

#1711 | canonkong | ⇗ @diderius6 What about VIA modified driver? On Xp system, I think it is better than Etron.

#1712

diderius6

⇗ @daniel_k
I make a mistake.
I forgot, that I disable everything in Bios
for boot of XP64, and also SATA ports.
Now, when I enable them again, I see,
that the amd_sata.sys 1.2.1.337 driver works and version 1.2.1.402 also
on x570 board
Dietmar

#1713 | daniel_k | ⇗ @diderius6 Glad to know it also works on X570. This just means we're done with drivers. We have drivers for everything, right?

#1714

diderius6

⇗ @daniel_k
I start to understand ⇗ @canonkong .
The USB DEV_149C is on the x570 board
much more unstable than on the AMD fatalty B350 board.
On the x570 board now I see for the first time "unknown device".
The same happens, when I install for DEV_149C the USB driver
from post 1095,
even I think it is on the x570 board the better choice for DEV_149C than the Etron driver
Dietmar

#1715

Mov AX, 0xDEAD

winapi mostly is stdcall(cdecl), so stack not touched by subcalls:

> Zitat von ⇗ daniel_k im Beitrag ¶ #1703

>     .text:00011888                 push    4                  ; 1
>     .text:0001188A                 lea     eax, [edi+11h]
>     .text:0001188D                 mov     byte ptr [edi+15h], 0
>     .text:00011891                 push    eax                         ; 2
>     .text:00011892                 movzx   eax, byte ptr [edi+10h]
>     .text:00011896                 push    4 -> easily kill by nops ; 3
>     .text:00011898                 lea     eax, [ebx+eax*4]
>     .text:0001189B                 push    eax ; 4
>     .text:0001189C                 call    ds:memcpy_s -> memcpy[/code]

>     .text:00067712                 push    eax                  ; 1
>     .text:00067713                 mov     eax, [esi]
>     .text:00067715                 push    [ebp+arg_0]                   ; 2
>     .text:00067718                 call    dword ptr [eax+0Ch] ;  subcall return result in eax
>     .text:0006771B                 movzx   eax, ax ; zeroing high bits of eax
>     .text:0006771E                 mov     ecx, esi
>     .text:00067720                 push    eax                   ; 3
>     .text:00067721                 mov     eax, [esi]          ; reload eax, so we can do anything with eax before this command
>     .text:00067723                 call    dword ptr [eax+8]
>     .text:00067726                 push    eax                   ; 4
>     .text:00067727                 call    ds:memcpy_s -> memcpy

push xx -> nops

#1716 | canonkong | ⇗ @diderius6 So I think VIA will better than Etron on X570 for Xp, even though it will 0x00000019E bsod on win7 sometimes in use.
#1717 | canonkong | ⇗ @Mov AX, 0xDEAD Do you think it's possible to use windbg to find out the breakpoint and use nop to stop it. I think it can solve some usb drivers 02C, 01E bsod, but I don't known how to modify on HxD. Modify like this: ⇗ https://forum.videohelp.com/threads/390651-Way-to-make-Intel-UHD-620-graphics-driver-to-works-in-windows-7-(no-crash)

#1718

diderius6

⇗ @infuscomus
I found,
that the BSOD in XP64 is acpi.sys related.
This error looks very similar to the acpi
BSOD, we have seen on XP 32 bit
Dietmar
PS: First picture is XP64 with unmodded 5048 acpi.sys. Second picture is with acpi.sys 5048 modded by @infuscomus.
⇗
⇗

#1719

daniel_k

⇗ @Mov AX, 0xDEAD
Thank you very much!
I know is stack related, changed this way by looking at other drivers calling memcpy and learned that it should be 0C, is it correct?

    1189C                 call    ds:memcpy_s
    118A2                 add     esp, 10h

to

    1189C                 call    ds:memcpy
    118A2                 add     esp, 0Ch

Sorry for being a noob.
For X64, there is no push, but several mov, sometimes add as well.
How do I know which one is correct for me to NOP?
These are from IDA, do you think the parameters are correct?

    72987                 mov     eax, [rdi+4]
    7298A                 cmp     eax, 40h
    7298D                 jnb     short loc_729AC
    7298F                 mov     [rcx+rsi+8], eax
    72993                 mov     r9d, [rdi+4]    ; size_t
    72997                 add     rcx, 0Ch
    7299B                 add     rcx, rsi        ; void *
    7299E                 mov     r8, r15         ; void *
    729A1                 mov     edx, 40h        ; size_t
    729A6                 call    cs:memcpy_s

    72D50                 xor     r12d, r12d
    72D53                 mov     r8, rdx         ; void *
    72D56                 mov     edi, r9d
    72D59                 mov     edx, 100h       ; size_t
    72D5E                 test    r9d, r9d
    72D61                 jnz     short loc_72D84
    72D63                 mov     rcx, [rsp+48h+arg_38]
    72D6B                 lea     r9d, [rdi+40h]  ; size_t
    72D6F                 mov     dword ptr [rcx], 41696541h
    72D75                 add     rcx, 4          ; void *
    72D79                 call    cs:memcpy_s

This one is missing 2 parameters?!

    72D84                 mov     rbx, [rsp+48h+arg_38]
    72D8C                 mov     eax, [rsp+48h+arg_40]
    72D93                 mov     [rbx+108h], r9d
    72D9A                 lea     rcx, [rbx+4]    ; void *
    72D9E                 mov     r9d, 40h        ; size_t
    72DA4                 mov     dword ptr [rbx], 46696541h
    72DAA                 mov     [rbx+104h], eax
    72DB0                 call    cs:memcpy_s

    72E04                 mov     r8, [r14+rcx*8] ; void *
    72E08                 movzx   eax, dx
    72E0B                 lea     rcx, [rbx+4]    ; void *
    72E0F                 test    r8, r8
    72E12                 jz      short loc_72E22
    72E14                 mov     r9d, eax        ; size_t
    72E17                 movzx   edx, dx         ; size_t
    72E1A                 call    cs:memcpy_s

    72F25                 movzx   edx, word ptr [rdi+0Eh] ; size_t
    72F29                 lea     r8, [rdi+10h]   ; void *
    72F2D                 mov     rcx, rax        ; void *
    72F30                 mov     r9d, edx        ; size_t
    72F33                 call    cs:memcpy_s

    7354C                 lea     rcx, [rbp+37h+var_80] ; void *
    73550                 mov     edx, 40h        ; size_t
    73555                 mov     r9d, [rax+r12+8] ; size_t
    7355A                 lea     r8, [rax+0Ch]
    7355E                 add     r8, r12         ; void *
    73561                 call    cs:memcpy_s

    77F9C                 lea     eax, [rbp+3]
    77F9F                 add     r8, rcx         ; void *
    77FA2                 mov     [rsp+0D8h+var_88], ax
    77FA7                 lea     rax, [rsp+0D8h+var_80]
    77FAC                 lea     rcx, [rsp+0D8h+var_68] ; void *
    77FB1                 mov     r9d, edx        ; size_t
    77FB4                 mov     [rsp+0D8h+var_78], rax
    77FB9                 call    cs:memcpy_s

#1720 | daniel_k | ⇗ @diderius6 Yeah! Thanks to Mov AX, 0xDEAD, I've successfully patched RSTe 4.7.0.1098, the last version compatible with Server 2003 (XP with storport.sys). Please test it, Dietmar.
#1721 | XPLAKE8175 | When I install intel hd the screen flashes once or twice but when I install windows vista the screen doesn't flash and when I restart in vista it restarts at 800x600 instead of 1366x768. I modded intel hd driver on broadwell cpu. Maybe the reg values of XP drivers are wrong.
#1722 | XPLAKE8175 | I'm testing Intel HD graphics on my broadwell laptop. When I successfully installed it, I will mod for Skylake, Kaby Lake and Coffee lake.

#1723

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1719

> to

>     1189C                 call    ds:memcpy
>     118A2                 add     esp, 0Ch

correct

> Zitat von ⇗ daniel_k im Beitrag ¶ #1719

> This one is missing 2 parameters?!

windows x64 calling convention for memcpy_s is:
1 RCX (*dest)
2 RDX (destSize)
3 R8 (*src)
4 R9 (count)
for memcpy:
1 RCX (*dest)
2 RDX (*src)
3 R8 (count)
4 -

#1724

XPLAKE8175

Can someone modify this haswell compatible igxp32 for my intel hd 5500 broadwell laptop? My screen flashes when I install but the driver does not install.
XPLAKE8175 has attached files to this post

- ⇗ IntelHDOriginalInf.zip

#1725 | XPLAKE8175 | I don't want the frustrating Anapa Corp. text before startup.

## Page 116

#1726

XPLAKE8175

ACPI: Solved
Graphics: BSOD after Install/Remove Software for discrete GPU.
Sound: Solved.
Ports: Solved.
Network: Solved.
Thermal Driver: FAIL.,
I modded chipset drivers on Vista and all of them are working properly. Just don't download the installer only package.
NOTE: The only failed drivers are manufactured by Intel. USING BROADWELL LAPTOP.
REQUEST: The most important driver is Intel HD Graphics at #1724

#1727 | diderius6 | I tested Intel RSTe from 2017 on the EVGA z390 dark board. Yesssssaaaa, nice driver !!! Nice work together ⇗ @daniel_k ⇗ @Mov AX, 0xDEAD !!! Dietmar ⇗

#1728

diderius6

iaStorA.sys and iaStorF.sys (TRIM) and newest storport.sys are loaded.
I make a test on the AMD board x570 also. There it gives code 10.
When you replace the asm106 driver with it, it gives BSOD 0xA.
For any Intel chipsets in future, XP will be on board
Dietmar

#1729 | XPLAKE8175 | Please someone answer me?
#1730 | canonkong | ⇗ @diderius6 Can you share the software: PEmaker. I try to find it on the internet, but not found.
#1731 | infuscomus | ⇗ @canonkong pemaker here ⇗ http://blog.livedoor.jp/blackwingcat/archives/1313117.html
#1732 | canonkong | @ infuscomus Thanks, I am trying a new driver sign method, *.sys file not need sign anymore.

#1733

XPLAKE8175

⇗ @diderius6 ⇗ @infuscomus
How can I install Intel HD Graphics for Haswell CPUs on Broadwell (i5 5200u) (Intel HD Graphics 5500). Here is the original igxp32.inf:
XPLAKE8175 has attached files to this post

- ⇗ IntelHDOriginalInf.zip

#1734 | infuscomus | ⇗ @diderius6 I looked at server 2003 x64 checked acpi.sys - I am now 90% certain I jumped the wrong function If I recall correctly, the forced jump should be just after PciInterfacesInstantiated?
#1735 | diderius6 | ⇗ @infuscomus Yes, look in this thread here, you posted a nice picture I remember. By the way, the acpi.sys for XP64 from ⇗ @skullteria contains another important part. This can be put easy together, if you jump the right function Dietmar

#1736

diderius6

⇗ @XPLAKE8175
You can take a look, what DEV_ ID your device has on Broadwell (i5 5200u) cpu
and add this to the *.inf in this section
[IntelGfx.NTx86.5.1]
When this not works, I think it is nearly impossible
to mod the driver for an integrated graphikcard device but you can use external Grafikcard with support for XP
Dietmar

#1737 | XPLAKE8175 | ⇗ @diderius6 My DEV_ID: PCI\VEN_8086&DEV_1616 I added it to strings and got error 10.

#1738

diderius6

⇗ @XPLAKE8175
Here it is, now the card will be recogniced
but if it works is another question
Dietmar
PS: Yes, with code 10 the driver does not start, I think no chance.
diderius6 has attached files to this post

- ⇗ igxp32.rar

#1739 | AddFun | What's the AGESA version on your Ryzen platforms guys? I'm still stuck with 7b BSODs (Gigabyte AX370 Gaming 5) post GUI install. Can't get to desktop proper though. Tried all the different versions of modded .sys files posted here and same result.

#1740

diderius6

I succeed to get the XP64 i210 lan controller to work on the EVGA z390 board.
I remember, that the i210, i211 is very similar (Intel) to the 82579V
and this time it was true
Dietmar
diderius6 has attached files to this post

- ⇗ 82579Vintellanasi210.rar

## Page 117

#1741 | infuscomus | ⇗ @AddFun I am on AMD AGESA to 1.0.0.6. - AB350 Gaming K4 BIOS 5.40

#1742

infuscomus

⇗ @diderius6
I made a 2nd attempt to patch ACPI x64 5048 for ryzen - based off of ⇗ @skullteria earlier version
I'm off to bed, I will test properly tomorrow
infuscomus has attached files to this post

- ⇗ acpi5048 x64 - 2nd patch attempt.zip

#1743

diderius6

When we want UEFI boot for XP
what do you think is best
choice?
XP SP3 32 bit
XP 64 bit SP2
Winserver 2003 32 bit R2
Winserver 2003 64 bit R2
Dietmar

#1744

diderius6

⇗ @Mov AX, 0xDEAD
On XP 64 bit SP2, the crazy clock shows also negativ values on z390 chipset.
Because I have no working tools for 64 bit,
can you please mod my english hal.dll (64 bit) here to use always the old clock
Dietmar
diderius6 has attached files to this post

- ⇗ hal.rar

#1745 | daniel_k | ⇗ @diderius6 Why don't patch the BIOS? Are you running the latest version? I can send the modified module for you to see.

#1746

diderius6

⇗ @daniel_k
I also think first of Bios mod. I have version 0.92 (for XP)
from
⇗ https://forums.evga.com/EVGA-Z390-DARK-O...T-m2930290.aspx
on top of this site there.
I read here, that you can enable the TCO timer in Bios.
But I do not find this timer in any table
Dietmar

#1747

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #1744

> @Mov AX, 0xDEAD
> can you please mod my english hal.dll (64 bit) here to use always the old clock

    8B 0D 56 ED FD FF 8B C2  C1 E8 08 24 01 0F BA E2 0F 73 0C E8 98 03 FC FF  C6 05 91 EC FD FF 01 0F
                                                     0F EB 0C

    8B 05 76 68 FD FF 8B C8  C1 E9 08 41 22 CC 0F BA E0 0F 73 0E 44 88 25 71  09 FD FF 44 88 25 8A 67
                                                        0F EB 0E

this mod for latest version 5.2.3790.4355, but in your old version bytes are same

#1748 | kukonosau | Unfortunately, BSOD(((

#1749

daniel_k

In UEFITool, search for module 16D0A23E-C09C-407D-A14A-AD058FDD0CA1.
Extract body from PE32 image section..
FACP table is built at runtime, with hardcoded flags.
Dark BIOS doesn't have a setting to enable/disable HPET, right?
Change this

    474B: C74070A5C60300         mov          d,[rax][070],00003C6A5

with this

    474B: C74070A5C60300         mov          d,[rax][070],0000346A5

#1750

diderius6

⇗ @Mov AX, 0xDEAD
Thank you, I found this jump and change it to EB,
but on restart XP 64 tells hal.dll is corrupt,
may be of wrong checksum.
I cant correct this checksum or maybe something is wrong with my halmod.dll
Dietmar
EDIT: I change at two places to EB, but still the message appears, that hal.dll is corrupt,
I think because of incorrect checksum. I have no tool for 64 bit, that corrects checksum.
EDIT2: With the tool setcsum.exe I succeed to correct the checksum and now
with correct running clock XP64 looks much more nice than before!
This file is the time correct working acpi hal.dll for XP64
version 5.2.3790.3959 (srv03_sp2_rtm.070216-1710),
Thanks a lot to ⇗ @Mov AX, 0xDEAD and ⇗ @daniel_k
⇗
diderius6 has attached files to this post

- ⇗ halmoddddchecksumm.rar
- ⇗ setcsum.rar

#1751 | kukonosau | How to install XP x64? ACPI is doesn't working on B350 chipset and AMD Ryzen 3 2200G!

#1752

daniel_k

⇗ @Mov AX, 0xDEAD
Thank you very much, managed to patch the x64 version.
However, I can't find any x64 DLL, SYS or EXE with sample code of wcslen and wcsncpy.

    size_t wcsnlen(
       const wchar_t *str, (RCX)
       size_t numberOfElements (RDX)
    );

    size_t wcslen(
       const wchar_t *str (RCX)
    );

    errno_t wcsncpy_s(
       wchar_t *strDest, (RCX)
       size_t numberOfElements, (R9) ???
       const wchar_t *strSource, (R8)
       size_t count (RDX) ???
    );

    wchar_t *wcsncpy(
       wchar_t *strDest, (RCX)
       const wchar_t *strSource, (RDX)
       size_t count (R8) ???
    );

Can you check if my assumptions are correct, please?

#1753

diderius6

⇗ @daniel_k
A5C60300 => A5460300
interesting, there stays the flags of FACP in Bios, here for to disable HPET,
Guid: 16D0A23E-C09C-407D-A14A-AD058FDD0CA1
PE32
before I found this flags from FACP only in real Bios Hex but now I know the place via UEfi tool also
Dietmar

#1754

daniel_k

⇗ @diderius6
Did you ever try Vista on your systems?
There is a well known issue on Haswell and later systems. Services are not initialized properly. It seems sometimes the OS works fine, it's random.
Would it be timer related?
Ivy Bridge is the last architecture known to work properly with Vista.
Would be nice if we could fix it as well.

#1755

diderius6

⇗ @daniel_k
I succeed to install Vista 32 bit and 64 bit on all Intel boards.
But on Ryzen only Vista 64 bit, because of not correct working acpi.sys
Dietmar
PS: The uncorrect timer affects even Win7. Some month ago I took a closer look to this.
For to test, if everything is ok, you can use the timer tool.
Not only the timer does not work correct. intelppm.sys has been fixed by ⇗ @Mov AX, 0xDEAD
which means, that the powermanagment is corrupt on all Intel boards from Skylake above.
diderius6 has attached files to this post

- ⇗ WinTimerTester.rar

## Page 118

#1756

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1752

>     errno_t wcsncpy_s(
>        wchar_t *strDest, (RCX)
>        size_t numberOfElements, (R9) ???
>        const wchar_t *strSource, (R8)
>        size_t count (RDX) ???
>     );

> Can you check if my assumptions are correct, please?

this one is not correct, order of arguments is always fixed if you call "offiicial" MS API, so right is RCX RDX R8 R9, 5th+ args on stack
⇗ https://en.wikipedia.org/wiki/X86_calling_conventions

#1757

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1752

> However, I can't find any x64 DLL, SYS or EXE with sample code of wcslen and wcsncpy.

wcslen - hdaudbus.sys (win7 x64)
wcsncpy - nvlddmkm.sys (nvidia vga driver)
wcsncpy_s - appwiz.cpl (win7 x64)

#1758

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #1755

> the powermanagment is corrupt on all Intel boards from Skylake above.

Now i think some acpi hardware functionality is disabled by bios vendors for some reason (recomendation from intel ?)
This functionality is not used anymore in WIN 7+, so nobody cares

#1759

diderius6

Even I get everything to work in XP 64bit SP2 5.2.3790.3959 on EVGA z390 dark board, 32 Gbyte memory,
Acpi, USB on each port, lan, graphik, sound, ahci, correct clock,
browser basilisk (nice), Moorhuhn, I got the feeling,
that XP SP3 is much more stable
Dietmar
EDIT: For me, I want to try UEFI boot for XP SP3.

#1760

PePilon

Hi, everyone
In other thread ([Guide] How to install Windows XP OS on Modern Hardware), ⇗ @daniel_k just suggested to try:
"USB driver, you must use the one attached to the following post:
Windows XP SP3 32bit and modern PC parts (92) (originally this is an hyperlink, don't know how to paste here)
However, it's unlikely it will work for you because a patched DSDT table (part of ACPI table in BIOS) is needed."
Daniel kindly have personalized a bios for me to test in the motherboard GA-Z170-HD3 (Gigabyte)
After flashing, the driver installs, but it is still not operating. The error code 39 is displayed for VEN_8086&DEV_A12F&SUBSYS_50071458&REV_31 (Intel(R) USB 3.0 eXtensible Host Controller Windows)
Is there still any hope to have USB working on Windows XP?
Thanks in advance.
Paulo
PS: just read this, but will use dual boot: Windows XP and Windows 10. When using Windows 10, I need USB 3.0 working, of course...
⇗ https://www.intel.com/content/www/us/en/...t-software.html

#1761 | daniel_k | ⇗ @PePilon Make sure you have USBD.SYS in the \Windows\System32\Drivers folder. If you don't extract it from the XP install disc or \WINDOWS\Driver Cache\i386\Driver.cab.

#1762

daniel_k

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #1757

> > Zitat von ⇗ daniel_k im Beitrag ¶ #1752

> > However, I can't find any x64 DLL, SYS or EXE with sample code of wcslen and wcsncpy.

> wcslen - hdaudbus.sys (win7 x64)
> wcsncpy - nvlddmkm.sys (nvidia vga driver)
> wcsncpy_s - appwiz.cpl (win7 x64)

I was searching in the XP x64 system folders.
Thanks, much appreciated.

#1763

daniel_k

> Zitat von ⇗ diderius6 im Beitrag ¶ #1755

> I succeed to install Vista 32 bit and 64 bit on all Intel boards.
> But on Ryzen only Vista 64 bit, because of not correct working acpi.sys
> Dietmar
> PS: The uncorrect timer affects even Win7. Some month ago I took a closer look to this.
> For to test, if everything is ok, you can use the timer tool.
> Not only the timer does not work correct. intelppm.sys has been fixed by @Mov AX, 0xDEAD
> which means, that the powermanagment is corrupt on all Intel boards from Skylake above.

I can install Vista after several tries.
About the intelppm.sys, doesn't it have the same effect as setting the XP's power scheme to Portable/Laptop?
I've been doing this for years, that's the only way to make C1E to work on a desktop.

#1764 | PePilon | The file was missing. Then I reinstalled... bingo!!! It worked. But then show up another device in list... and I installed the same drive and... worked!!! See the final results in picture attached. I really owe you one ⇗ @daniel_k !!! PePilon has attached images to this post ⇗ USB.PNG
#1765 | diderius6 | ⇗ @daniel_k Have you been able to install Vista 32 bit on Ryzen board? Did you change something in acpi.sys for to reach this, Dietmar
#1766 | daniel_k | ⇗ @PePilon Glad to know it works. I've got an idea about the missing file. PS: Yes, I'm brazilian and live in Sao Paulo.

#1767

daniel_k

> Zitat von ⇗ diderius6 im Beitrag ¶ #1765

> @daniel_k
> Have you been able to install Vista 32 bit on Ryzen board?
> Did you change something in acpi.sys for to reach this,
> Dietmar

I don't have any AMD board here.
My last AMD system was an Athlon 64 3200+ / nForce 4 SLI.
Moved to Intel because of some strange BSODs while playing games.
Probably a bug in the CPU, chipset or both.
With the Intel system (E6400 + 965P), absolutely no BSODs.

#1768

daniel_k

⇗ @diderius6
Here is the RSTe 4.6.0.1085 x64. UPDATED, found 2 instructions incorrecly patched.
Please test it when possible.
Thanks to Mov AX, 0xDEAD, I've learned how to properly fix the function's arguments.
4.7.0.1098 will take a while, more than 120 changes. [oh2]
PS: Interesting that the RSTe 4.6 and 4.7 driver and the AMD AHCI 1.2.1.402 driver work on VirtualBox supporting 8 ports.

#1769 | infuscomus | ⇗ @diderius6 my 2nd attempt at ACPI x64 patch gives 7E BSOD maybe my 1st attempt is correct and it is something else that is wrong?
#1770 | canonkong | ⇗ @diderius6 ⇗ @infuscomus VIA USB MOD Driver For AMD 149C, you can test it , I test it for two days, not 01E BSOD untill now. Link: ⇗ https://yadi.sk/d/vH7IVuyYPGbCPw I used PEMAKER082 to checksum, but not sucessed. But it can work well. Use new driver Digital Signature.

## Page 119

#1771

diderius6

⇗ @daniel_k
I just test your new driver
RSTe_4.6.0.1085_x64_MOD.rar
on the EVGA z390 dark board with XP 64 bit.
It works:))!!
Have a nice day
Dietmar

#1772 | infuscomus | ⇗ @canonkong MSISupported should be disabled for XP - XP does not support message signaled interrupts.
#1773 | XPLAKE8175 | If diderius6's igxp32 works I will request skylake drivers from diderius6.

#1774

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1763

> About the intelppm.sys, doesn't it have the same effect as setting the XP's power scheme to Portable/Laptop?
> I've been doing this for years, that's the only way to make C1E to work on a desktop.

¶ Windows XP SP3 32bit and modern PC parts (14)
¶ Windows XP SP3 32bit and modern PC parts (19)

#1775 | kukonosau | Can you send me your Intel ACPI x64, please? May be, correctly work in Ryzen?! Modify Hal.dll doesn't help me.

#1776

diderius6

Here is the storahci driver,
which works really everywhere. I just give in the folder AMD64 its *.inf for 64 bit support.
AMD, Intel, 32 bit, 64 bit doesnt matter. Until now I do not find a board, where it does not work,
really generic.
Copy the newest version of storport.sys
to windows\system32\drivers and install. You can also make a txtsetup.oem
and integrate it to your XP installations CD. Dont forget storport.sys!
I tested it for XP 32 bit and XP 64 bit
Dietmar
EDIT: So much thank to ⇗ @skullteria !
diderius6 has attached files to this post

- ⇗ StorahciSkulltrailALL.rar

#1777 | diderius6 | ⇗ @infuscomus ⇗ @skullteria I tested all acpi.sys 64 bit for XP I can found in the forum and also my own new one. No one of them works on Ryzen board until now Dietmar
#1778 | infuscomus | ⇗ @diderius6 maybe ACPI x64 has a different problem from ACPI x86? my 2nd ACPI x64 patch attempt from post #1742 - did you get 7E BSOD?

#1779

diderius6

⇗ @infuscomus
Yes, when all other is ok, it gives
BSOD 0x7E (0xC0000005, xxx, yyy).
My newest acpi.sys for 64 bit gives exact the same BSOD.
Dietmar
PS: My problem is, that I have no good tools for 64 bit. Even the 32 bit acpi.sys for Ryzen was as hard as possible,
for me I have no idea for acpi.sys Ryzen for 64 bit. Editing DSDT does not help for Ryzen until now.
After my experiance with XP 64 bit (sound in Moorhuhn is stottering, lan connection disables itself because it wants to save energy, brrr..)
I am not so very sad about it. I take a look at UEFI boot for XP SP3. I heard, that somebody succeed with Server 2003 RS2 32 bit(!) for UEFI boot,
but real XP SP3 is different.

#1780 | infuscomus | ⇗ @diderius6 here is that helpful thread i found for UEFI boot for XP, in case you forgot ⇗ https://www.betaarchive.com/forum/viewto...=20327&start=29 good luck.

#1781

diderius6

⇗ @canonkong
I just test your modded USB driver from Via for XP SP3.
On the AMD board asrock fatal1ty ab350 gaming k4
with Ryzen 3700x it works absolut stable for DEV_149C.
For DEV_43BB the hub does not work (code 10).
On the asus prime x570-pro AMD board with Ryzen 1700
your driver runs stable for DEV_145C.
For DEV_149C with subsys 148C1022 it is also absolut stable.
For DEV_149C with subsys 87471043 the hub switches on and off
Dietmar

#1782 | canonkong | ⇗ @diderius6 DEV_43BB is belong to ASMedia. AMD 300/400 board chip bought from ASMedia, so they can use AMD 1.0.5.3 USB driver and ASMedia USB driver will better than others.

#1783

daniel_k

> Zitat von ⇗ diderius6 im Beitrag ¶ #1771

> @daniel_k
> I just test your new driver
> RSTe_4.6.0.1085_x64_MOD.rar
> on the EVGA z390 dark board with XP 64 bit.
> It works:))!!
> Have a nice day
> Dietmar

Thanks for the feedback!

#1784

daniel_k

⇗ @Mov AX, 0xDEAD
Thanks for clarifying.
There is really no way to patch the ACPI table so it would work as it should without patching the driver?
Can you please help me with this one?
PE64 also has relocation like PE32, right?
I understand PE32 relocation and know how to patch it without rebuild it all, but I have no idea about PE64.
Opened the .sys file in LordPE, but it gave no clues.
I'm afraid I have no room to properly patch some arguments, like this below.
I guess sometimes arguments can be provided before a call, right?

    75B3B: 4C8D442430                     lea          r8,[rsp][030] -> const void *src
    75B40: 498D8A98020000                 lea          rcx,[r10][000000298]
    75B47: 41B901000000                   mov          r9d,1
    75B4D: E82E360000                     call        79180

    79180: 48895C2410                     mov          [rsp][010],rbx
    79185: 48896C2418                     mov          [rsp][018],rbp
    7918A: 56                             push         rsi
    7918B: 57                             push         rdi
    7918C: 4154                           push         r12
    7918E: 4156                           push         r14
    79190: 4157                           push         r15
    79192: 4883EC20                       sub          rsp,020 ;' '
    79196: 4C8BA1E8980100                 mov          r12,[rcx][0000198E8]
    7919D: 4C8BB1F8980100                 mov          r14,[rcx][0000198F8]
    791A4: 488B9918990100                 mov          rbx,[rcx][000019918]
    791AB: 4C8BF9                         mov          r15,rcx
    791AE: 33C0                           xor          eax,eax
    791B0: 418BE9                         mov          ebp,r9d
    791B3: 8D4820                         lea          ecx,[rax][020]
    791B6: 8D5014                         lea          edx,[rax][014] -> size_t destSize
    791B9: 498BFC                         mov          rdi,r12
    791BC: F3AA                           rep stosb
    791BE: 498BFE                         mov          rdi,r14
    791C1: B900090000                     mov          ecx,000000900
    791C6: F3AA                           rep stosb
    791C8: 498BBFE0980100                 mov          rdi,[r15][0000198E0]
    791CF: B900020000                     mov          ecx,000000200
    791D4: F3AA                           rep stosb
    791D6: 498BCE                         mov          rcx,r14 -> void *dest
    791D9: 448BCA                         mov          r9d,edx -> size_t count
    791DC: 498BF0                         mov          rsi,r8
    791DF: 48895C2450                     mov          [rsp][050],rbx
    791E4: FF15761F0100                   call         memcpy_s

My solution would be:

    75B3B: 4C8D442430                     lea          rdx,[rsp][030] -> const void *src
    75B40: 498D8A98020000                 lea          rcx,[r10][000000298]
    75B47: 41B901000000                   mov          r8d,1
    75B4D: E82E360000                     call        79180

    79180: 48895C2410                     mov          [rsp][010],rbx
    79185: 48896C2418                     mov          [rsp][018],rbp
    7918A: 56                             push         rsi
    7918B: 57                             push         rdi
    7918C: 4154                           push         r12
    7918E: 4156                           push         r14
    79190: 4157                           push         r15
    79192: 4883EC20                       sub          rsp,020 ;' '
    79196: 4C8BA1E8980100                 mov          r12,[rcx][0000198E8]
    7919D: 4C8BB1F8980100                 mov          r14,[rcx][0000198F8]
    791A4: 488B9918990100                 mov          rbx,[rcx][000019918]
    791AB: 4C8BF9                         mov          r15,rcx
    791AE: 33C0                           xor          eax,eax
    791B0: 418BE9                         mov          ebp,r9d
    791B3: 8D4820                         lea          ecx,[rax][020]
    791B6: 448D4014                       lea          r8d,[rax][014] -> size_t count
    791BA: 498BFC                         mov          rdi,r12
    791BD: F3AA                           rep stosb
    791BF: 498BFE                         mov          rdi,r14
    791C2: B900090000                     mov          ecx,000000900
    791C7: F3AA                           rep stosb
    791C9: 498BBFE0980100                 mov          rdi,[r15][0000198E0]
    791D0: B900020000                     mov          ecx,000000200
    791D5: F3AA                           rep stosb
    791D7: 498BCE                         mov          rcx,r14 -> void *dest
    791DA: 498BF0                         mov          rsi,r8
    791DD: 9090                           nop
    791DF: 48895C2450                     mov          [rsp][050],rbx
    791E4: FF15761F0100                   call         memcpy

Can't patch this without moving down some instructions like mov rdi,[r15][0000198E0] which obviously has relocation.

#1785 | daniel_k | ⇗ @diderius6 About the ReactOS' storahci, it's a shame it isn't feature complete.

## Page 120

#1786

daniel_k

⇗ @diderius6
Updated RSTe_4.6.0.1085_x64_MOD, made some mistakes. Now is 100% correct.
¶ Windows XP SP3 32bit and modern PC parts (118)
Tested on VirtualBox.
Please try it again if possible.
By the way, how much RAM available does XP x64 shows in System Properties?
For some reason, here it shows only 15.9GB instead of the full 16.0 GB RAM.

#1787

skullteria

> Zitat von ⇗ daniel_k im Beitrag ¶ #1785

> @diderius6
> About the ReactOS' storahci, it's a shame it isn't feature complete.

Reactos's storahci is incomplete. I adapted Storahci from Win 8 WDK and it work fine. I attached storahci x86 and amd64, and source code is avaliable on One-Core-API repository on github. Yes, i'm the creator of Shorthorn project (⇗ www.shorthornproject.com), One-Core-API and will create a reactos based system.
skullteria has attached files to this post

- ⇗ Storahci.zip

#1788

skullteria

> Zitat von ⇗ daniel_k im Beitrag ¶ #1786

> @diderius6
> Updated RSTe_4.6.0.1085_x64_MOD, made some mistakes. Now is 100% correct.
> ¶ Windows XP SP3 32bit and modern PC parts (118)
> Tested on VirtualBox.
> Please try it again if possible.
> By the way, how much RAM available does XP x64 shows in System Properties?
> For some reason, here it shows only 15.9GB instead of the full 16.0 GB RAM.

It probably is system reserved, completly normal.

#1789 | canonkong | ⇗ @skullteria What about USB XHCI Controller? USB XHCI Driver Based on ReactOS Compiler: ⇗ https://yadi.sk/d/Bo_nQun4ryJXyQ But not work on win7.
#1790 | XPLAKE8175 | How can I use iasl tool? I got an error while creating aml file.
#1791 | XPLAKE8175 | I'm using portable XP with AHCI drivers and I really want dsdt patch.

#1792

diderius6

⇗ @XPLAKE8175
Take the iasl.exe from Mai 2019.
The error can happen, when you forget to set in DSDT.dsl for example "}"
always correct.
It can also happen, when a function is called with no argument.
In some DSDT this is used (bad program code).
You can use the force switch in iasl.exe, to make an *.aml file.
But for to look, if everything is ok,
redisassemble it one more time and compare this produced *.dsl with your original one.
If there is no real error, the code is identic
Dietmar

#1793

diderius6

⇗ @canonkong
The usbxhci.sys has an unmatched import function to ntoskernl in XP SP3
MmAllocatePagesForMdlEx
May be ⇗ @daniel_k ⇗ @Mov AX, 0xDEAD
can fix this.
It is very interesting, if this usbxhci from Reactos
works in XP
Dietmar

#1794 | XPLAKE8175 | I'm creating dsdt and ssdt aml files and got 0 kb file.

#1795

XPLAKE8175

⇗ @diderius6

    Method (_PS0, 0, Serialized)  // _PS0: Power State 0
                {
                    If ((DVID == 0xFFFF))
                    {
                        Return (Zero)
                    }

                    Local2 = MEMB /* \_SB_.PCI0.XHC_.MEMB */
                    Local1 = PDBM /* \_SB_.PCI0.XHC_.PDBM */
                    If (OSYS >= 0x07D6)
                    {
                        PDBM &= 0xFFFFFFFFFFFFFFF9
                    }
                    Local3 = D0D3 /* \_SB_.PCI0.XHC_.D0D3 */
                    D0D3 = Zero
                    MEMB = XWMB /* \XWMB */
                    PDBM = (Local1 | 0x02)
                    OperationRegion (MCA1, SystemMemory, XWMB, 0x9000)
                    Field (MCA1, DWordAcc, Lock, Preserve)
                    {
                        Offset (0x80E0),
                            ,   15,
                        AX15,   1,
                        Offset (0x8154),
                            ,   31,
                        CLK2,   1,
                        Offset (0x816C),
                            ,   2,
                        CLK0,   1,
                            ,   11,
                        CLK1,   1
                    }

                    If ((PCHV () == LPTL))
                    {
                        MB13 = Zero
                        MB14 = Zero
                        CLK0 = Zero
                        CLK1 = Zero
                    }

                    If ((PCHG == One))
                    {
                        CLK2 = One
                    }

                    If (((PCHS == 0x02) && (PCHG == One)))
                    {
                        Local3 = XWMB /* \XWMB */
                        Local3 += 0x0510
                        OperationRegion (PSCA, SystemMemory, Local3, 0x40)
                        Field (PSCA, DWordAcc, Lock, Preserve)
                        {
                            PSC1,   32,
                            Offset (0x10),
                            PSC2,   32,
                            Offset (0x20),
                            PSC3,   32,
                            Offset (0x30),
                            PSC4,   32
                        }

                        While (((((PSC1 & 0x03F8) == 0x02E0) || ((PSC2 &
                            0x03F8) == 0x02E0)) || (((PSC3 & 0x03F8) == 0x02E0) || ((PSC4 &
                            0x03F8) == 0x02E0))))
                        {
                            Stall (0x0A)
                        }

                        Local4 = Zero
                        Local0 = (PSC1 & 0xFFFFFFFFFFFFFFFD)
                        If (((Local0 & 0x000203F9) == 0x02A0))
                        {
                            PSC1 = (Local0 | 0x80000000)
                            Local4 |= One
                        }

                        Local0 = (PSC2 & 0xFFFFFFFFFFFFFFFD)
                        If (((Local0 & 0x000203F9) == 0x02A0))
                        {
                            PSC2 = (Local0 | 0x80000000)
                            Local4 |= 0x02
                        }

                        Local0 = (PSC3 & 0xFFFFFFFFFFFFFFFD)
                        If (((Local0 & 0x000203F9) == 0x02A0))
                        {
                            PSC3 = (Local0 | 0x80000000)
                            Local4 |= 0x04
                        }

                        Local0 = (PSC4 & 0xFFFFFFFFFFFFFFFD)
                        If (((Local0 & 0x000203F9) == 0x02A0))
                        {
                            PSC4 = (Local0 | 0x80000000)
                            Local4 |= 0x08
                        }

                        If (Local4)
                        {
                            Sleep (0x65)
                            If ((Local4 & One))
                            {
                                Local0 = (PSC1 & 0xFFFFFFFFFFFFFFFD)
                                PSC1 = (Local0 | 0x00FE0000)
                            }

                            If ((Local4 & 0x02))
                            {
                                Local0 = (PSC2 & 0xFFFFFFFFFFFFFFFD)
                                PSC2 = (Local0 | 0x00FE0000)
                            }

                            If ((Local4 & 0x04))
                            {
                                Local0 = (PSC3 & 0xFFFFFFFFFFFFFFFD)
                                PSC3 = (Local0 | 0x00FE0000)
                            }

                            If ((Local4 & 0x08))
                            {
                                Local0 = (PSC4 & 0xFFFFFFFFFFFFFFFD)
                                PSC4 = (Local0 | 0x00FE0000)
                            }
                        }

                        AX15 = One
                    }

                    If (((PCHG == One) || ((PCHV () == WPTL) && (PCHP == 0x41))))
                    {
                        SWAI = Zero
                        SAIP = Zero
                    }

                    If (CondRefOf (\_SB.PCI0.XHC.PS0X))
                    {
                        PS0X ()
                    }

                    If (OSYS >= 0x07D6)
                    {
                        PDBM &= 0xFFFFFFFFFFFFFFFD
                    }
                    MEMB = Local2
                    PDBM = Local1
                }

Is it work on my asus k555lb laptop?

#1796 | diderius6 | ⇗ @XPLAKE8175 Please tell me the Bios version of your asus k555lb laptop Dietmar
#1797 | XPLAKE8175 | ⇗ @diderius6 Version 605
#1798 | XPLAKE8175 | ⇗ @diderius6 Did you find my DSDT patch for Asus k555lb (x555lb) version 605?

#1799

diderius6

⇗ @daniel_k ⇗ @infuscomus
Daniel, your new driver works.
Todd, your acpi.sys 64 bit works on the asrock fatal1ty z370 gaming k6 board
as you can see.
By the way, XP64 is on this asrock board absolut stable. All works,
Dietmar
⇗

#1800 | XPLAKE8175 | ⇗ @diderius6 Please answer me did you find my XP compilant DSDT?

## Page 121

#1801 | infuscomus | ⇗ @diderius6 so my ACPI x64 works for intel z370, thanks for letting me know. I will try again to patch for AMD Ryzen.
#1802 | XPLAKE8175 | Now I need asl.exe
#1803 | infuscomus | ⇗ @XPLAKE8175 post #442 or #443 of this thread

#1804

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1784

>     791D6: 498BCE                         mov          rcx,r14 -> void *dest
>     791D9: 448BCA                         mov          r9d,edx -> size_t count
>     791DC: 498BF0                         mov          rsi,r8
>     791DF: 48895C2450                     mov          [rsp][050],rbx
>     791E4: FF15761F0100                   call         memcpy_s

> Can't patch this without moving down some instructions like mov rdi,[r15][0000198E0] which obviously has relocation.

You shift code, this is not i like, in this case i prefer more generic way (but more complex and need some knowledge of mapping segment)
1) extend code segment to max available (max is begin of next segment - 1 byte) in PE header
2) look in reloc table about possible reloc in calling memcpy_s (ff 15 76 1f 01 00 is call qword PTR [rip+0x11f76] , so it is IP relative call and no need reloc)
3a) if no reloc replace CALL memcpy_s to CALL newcode to new code placed at end of segment
or
3b) replace CALL memcpy_s to JMP newcode to new code placed at end of segment
4) add new commands with any lengh (but dont use absolute adressing, otherwise you need patch reloc table)

    newcode:
    XX XX XX             mov rdx, r8 (new *src <- old *src, 64b)
    XX XX XX             mov r8d,r9d (new count <- old count, 32b)
    FF 15 XX XX XX XX    call memcpy (your assembler must calculate offset between current ip and memcpy)
    3a:
    XX XX XX             ret
    3b:
    XX XX XX             jmp 791EA

> Zitat

> memcpy_s
> 2 RDX (destSize)
> 3 R8 (*src)
> 4 R9 (count)
> memcpy:
> 2 RDX (*src)
> 3 R8 (count)

#1805

Andalu

Hi all,
thanks a lot for your great job guys!
I know i'm a bit OT here but i need your help :)
i successfully installed Usb3.0 driver from daniel_k on motherboard Gateway DX4870 (from acer aspire M3985, chipset B75) logically with XPSP3 :) both 'amd usb 3.0 root hub' and 'intel extensible host controller' are visible, but the usb3 ports work like usb2, the benchmark tests speed are too low for a really usb3.
My external disk too uses a blue led only when inserted on the Renesas usb3.0 pci card and always a white led when inserted in any usb2 and usb3 motherboard rear ports.
What's doesn't work correctly?
P.S.: my english is bad..sorry

#1806

diderius6

⇗ @XPLAKE8175
I cant produce a working *.aml from this DSDT from Bios 605,
even I tried the old iasl version from September 2012
and also Bios vers 603
Dietmar
PS: There are other 64 bit constants in this method also,
so I think the DSDT should look like this one for XP.
diderius6 has attached files to this post

- ⇗ DSDT.rar

#1807

skullteria

> Zitat von ⇗ canonkong im Beitrag ¶ #1789

> @skullteria
> What about USB XHCI Controller?
> USB XHCI Driver Based on ReactOS Compiler: ⇗ https://yadi.sk/d/Bo_nQun4ryJXyQ
> But not work on win7.

unfortunately, the source code from Win 10 has some missing functions, is not really easy to compile it...I need more time.
And, reactos xhci is broken, incomplete, can't be used.

#1808 | XPLAKE8175 | ⇗ @diderius6 Another issue your igxp32 driver still gets error code 10

#1809

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1786

> By the way, how much RAM available does XP x64 shows in System Properties?
> For some reason, here it shows only 15.9GB instead of the full 16.0 GB RAM.

check with any e820 tool ram ranges, if is it 15.9 - bios claimed some ram

#1810 | Mov AX, 0xDEAD | Does anyone have a Longhorn x64 windows version <= 4042 ? if yes, please share acpi.sy_
#1811 | XPLAKE8175 | How can I get september 2012 bios for my asus k555lb (x555lb)?
#1812 | diderius6 | ⇗ @XPLAKE8175 I think, it is because of the unknown imports. Take a look with C:\iasl how the other ssdt tables have to be connected to DSDT via the -e switch Dietmar

#1813

infuscomus

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #1810

> Does anyone have a Longhorn x64 windows version <= 4042 ?
> if yes, please share acpi.sy_

⇗ @Mov AX, 0xDEAD
try here
⇗ https://winworldpc.com/product/windows-l...n-vis/pre-reset

#1814 | XPLAKE8175 | I downgraded my bios to version 603 and which dsdt table is true for my 603 version ami?

#1815

diderius6

⇗ @XPLAKE8175
Place all SSDT/DSDT in a single directory (rename them to *.aml as you move them) and use a recent build of iasl to disassemble:
cd "to directory where you placed all SSDT/DSDT"
iasl -da -dl *.aml
Then work with the resulting *.dsl. You'll find you have less errors to deal with
Dietmar
PS: iasl -da -dl -fe refs.txt DSDT.aml SSDT*.aml

## Page 122

#1816 | XPLAKE8175 | Getting syntax error.
#1817 | XPLAKE8175 | My dsdt decreases to 0kb.

#1818

daniel_k

⇗ @skullteria, nice job with the driver!
About the available system RAM, I know the system may reserve some amount.
However, concerning Windows XP x64 and Server 2003 32-bit with PAE enabled, it didn't happen with my H270 board.
It's the first time I've seen such behaviour.
⇗ @diderius6, ⇗ @Mov AX, 0xDEAD
Something has changed between 200 and 300 series chipsets.
Will see if something has changed in the ACPI tables.

#1819

daniel_k

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #1804

> You shift code, this is not i like, in this case i prefer more generic way (but more complex and need some knowledge of mapping segment)
> 1) extend code segment to max available (max is begin of next segment - 1 byte) in PE header
> 2) look in reloc table about possible reloc in calling memcpy_s (ff 15 76 1f 01 00 is call qword PTR [rip+0x11f76] , so it is IP relative call and no need reloc)
> 3a) if no reloc replace CALL memcpy_s to CALL newcode to new code placed at end of segment
> or
> 3b) replace CALL memcpy_s to JMP newcode to new code placed at end of segment
> 4) add new commands with any lengh (but dont use absolute adressing, otherwise you need patch reloc table)

Thanks, I think I understand all your points.
Let me see what I can do.

#1820

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #1805

> Hi all,
> thanks a lot for your great job guys!
> I know i'm a bit OT here but i need your help :)
> i successfully installed Usb3.0 driver from daniel_k on motherboard Gateway DX4870 (from acer aspire M3985, chipset B75) logically with XPSP3 :) both 'amd usb 3.0 root hub' and 'intel extensible host controller' are visible, but the usb3 ports work like usb2, the benchmark tests speed are too low for a really usb3.
> My external disk too uses a blue led only when inserted on the Renesas usb3.0 pci card and always a white led when inserted in any usb2 and usb3 motherboard rear ports.
> What's doesn't work correctly?
> P.S.: my english is bad..sorry

Make sure that the USB3 (XHCI) BIOS settings are properly configured.
Try the driver in this post:
¶ Windows XP SP3 32bit and modern PC parts (89)

#1821 | XPLAKE8175 | ⇗ @diderius6 iasl.exe shows me a syntax error at line 9134, 25964 and 29338.
#1822 | diderius6 | ⇗ @XPLAKE8175 Yes, for me was the same. Make a try with post 1815 Dietmar
#1823 | XPLAKE8175 | ⇗ @diderius6 I got a different error named "compiler aborting due to syntax error(s).

#1824

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1819

> Thanks, I think I understand all your points.

more details:
1) hdaudbus.sys win7 x64
2) original pe header
.text - main code segment/section
.rdata - next segment
3) in memory .rdata will be mapped starting from 13000, .text starting from 1000
max available size of .text is (13000-1000)=12000 in memory
4) size of filled .text in header is 110A4, we get unused mapped gap 0xF5C bytes (12000-110A4)
5) check limitation of our gap inside file:
.text offset 400+ size 11200=11600 is offset of last byte of .text
.rdata offset = 11600, so we have 0 additional free bytes
6) raw size .text is 11200 (size in file), this is max possible size for us
7) change virtual size 110A4=>11200 in pe header, we get unused GAP 0x15C bytes (11200-110A4) in file
8) remember about 110A4 adress, it is last byte of original payload, all after this byte and before start of .rdata is garbage and we will use it !!!
9) place new code starting from 110A4+1 virtual adress (110A4+1 -1000 +400 is offset in file)
unfortunately it may happen that the size of the payload (.text) will be almost equal to the size of raw size, in this case we have only few free bytes and we need find other way to allocate enough amount of bytes

#1825

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #1820

> Make sure that the USB3 (XHCI) BIOS settings are properly configured.
> Try the driver in this post:
> ¶ Windows XP SP3 32bit and modern PC parts (89)

Thank you for reply ;)
there is not XHCI option in bios, the mobo comes from an acer pre-assembled pc and the bios has few options only.
I installed too the "Renesas_FINAL_NEW" and the rear ports are still seen as usb2 but now:
- Intel USB3.1 eXtensible Host Controller and Renesas Electronics Usb 3.0 Host Controller have a new advanced tab where i disabled USB 3.0 power saving features;
- i got the message "this storage device can work faster if connected to a usb 3.0 port" for every device connected to the rear usb3 ports.
Can i try something else?

#1826 | skullteria | Well, i made some tests of USBXHCI from Win8, add functions needed to the kernel. However, this driver has a call to security_cookie_check, only avaiable on Win8 or above (win 8 kernel init security cookie). So, i need from somebody make a fix of this function, removing security_cookie_check call. I will attatch driver on some hours.

#1827

diderius6

⇗ @infuscomus
I make a new try with XP64 on Ryzen.
Always the same BSOD
`0x0000007E (0xFFFFFFFFC0000005, xxx, yyy)
acpi.sys - Address xxx`
Dietmar
PS: 0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred, here by acpi.sys.
EDIT: May be, a reduce the memory to 2 Gbyte during setup will help. But I do not have a 2 GB ram stick.
May be, during setup the allowed memory for XP64 can be reduced to 2 Gbyte.

#1828

Mov AX, 0xDEAD

> Zitat von ⇗ skullteria im Beitrag ¶ #1826

> So, i need from somebody make a fix of this function, removing security_cookie_check call. I will attatch driver on some hours.

    void security_check_cookie(DWORD PTR) {
        return;
    }

#1829

skullteria

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #1828

> > Zitat von ⇗ skullteria im Beitrag ¶ #1826

> > So, i need from somebody make a fix of this function, removing security_cookie_check call. I will attatch driver on some hours.

>     void security_check_cookie(DWORD PTR) {
>         return;
>     }

How add it to driver?

#1830

Mov AX, 0xDEAD

> Zitat von ⇗ skullteria im Beitrag ¶ #1829

> How add it to driver?

binary or source ?
if binary:
1) in import table remove check_cookie_xxx record from list
2) now original record will be not filled by loader, insert in these 4 bytes offset to any ret command
3) add 1 new reloc info with address of record
original call sec_xxx will load adr of subcall from patched record, call to it, return

## Page 123

#1831 | daniel_k | ⇗ @Mov AX, 0xDEAD Unfortunately there are just 5 free bytes, useless. But I've got an idea: in the end of the .text section, there are dozens of strings separated by several CCh. I'll move a couple together, update the address at the referenced code and use the "created" space.

#1832

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #1825

> there is not XHCI option in bios, the mobo comes from an acer pre-assembled pc and the bios has few options only.
> I installed too the "Renesas_FINAL_NEW" and the rear ports are still seen as usb2 but now:
> - Intel USB3.1 eXtensible Host Controller and Renesas Electronics Usb 3.0 Host Controller have a new advanced tab where i disabled USB 3.0 power saving features;
> - i got the message "this storage device can work faster if connected to a usb 3.0 port" for every device connected to the rear usb3 ports.
> Can i try something else?

What is the exact model of your system?
And country of purchase? Some models can only be found in the specific country support site.

#1833

infuscomus

⇗ @daniel_k
PETool 0.0.5 can insert extra space in-between sections, maybe it can help?
originally found here
⇗ https://msfn.org/board/topic/146529-pe-t...eating-patches/
infuscomus has attached files to this post

- ⇗ PE_Tool_0.0.5.zip

#1834 | XPLAKE8175 | I'm now using the rw utility for the XP compilant acpi and I found some strings named OSXP and OSYS. The OSXP string equals 0x10.
#1835 | XPLAKE8175 | ⇗ @diderius6 Getting same errors with SSDTs
#1836 | diderius6 | ⇗ @XPLAKE8175 Can you send me the new builded DSDT.dsl from all the *.aml together Dietmar

#1837

XPLAKE8175

⇗ @diderius6
Here is my zip file with my new DSDT.dsl and all aml files inside:
XPLAKE8175 has attached files to this post

- ⇗ ssdt.zip

#1838

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #1832

> What is the exact model of your system?
> And country of purchase? Some models can only be found in the specific country support site.

My system was an Acer Aspire M3985 and i have kept only the motherboard from it, a IPIMB-AR Rev.1.02A with chipset B75. The country of purchase is Italy.
I also tried to install the driver "AMDXHCI_FINAL" on a Msi CSM-Q87M-E43 mobo but i got always error code 10 even if in bios the XHCI and EHCI options are both or alternatively enabled or disabled. Same results with the driver "Renesas_FINAL_NEW".
So strange, on the older mobo with no XHCI option in bios the drivers are loaded even if the usb3.0 ports work as usb2, on a newer mobo with XHCI/EHCI options in bios, the driver doesn't work.
Edit: the motherboard lga1155 B75 is "IPIMB-AR Rev:1.02A"

#1839 | XPLAKE8175 | ⇗ @diderius6 I sent you an ssdt.zip file please extract it.

#1840

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1831

> @Mov AX, 0xDEAD
> Unfortunately there are just 5 free bytes, useless.

1) in drivers exist section INIT, this is also code section, but after driver initialised this memory is cleaned
to avoid this rename section to .text and make it in header nopageable and nondiscardable
or
2) create new code section, virtual adress must not overlap with existing sectons

#1841 | infuscomus | ⇗ @diderius6 i found debug builds of windows vista ⇗ https://www.getmyos.com/windows-vista-ho...arter-32-64-bit hopefully you can use them to fix the ACPI bug for vista

#1842

diderius6

⇗ @XPLAKE8175
I see, that 19 dependencies are solved
but still 10 are unsolved.
Make a new try with building a refs.txt
as in
⇗ https://hackintoshpro.com/patch-dsdt-hackintosh/
Dietmar

#1843 | diderius6 | ⇗ @infuscomus This is a nice finding :)) Dietmar
#1844 | XPLAKE8175 | ⇗ @diderius6 SSDT files do not create a .dsl file. I think the 10 unsolved dependecies relates to the missing ssdt*.dsl. I created .aml of dsdt and ssdt* by RWeverything.
#1845 | XPLAKE8175 | I tried the more dangerous way: RWEverything.

## Page 124

#1846

Mov AX, 0xDEAD

> Zitat von ⇗ XPLAKE8175 im Beitrag ¶ #1845

> I tried the more dangerous way: RWEverything.

dsdt in bios and on live system is not same !
RWEverything helps to show/extract which ssdts are used

#1847 | XPLAKE8175 | ⇗ @diderius6 ⇗ @Mov AX, 0xDEAD I Extracted All DSDT/SSDTs in AIDA64 Engineer got 8 unresolved dependencies.
#1848 | XPLAKE8175 | ⇗ @diderius6 ⇗ @Mov AX, 0xDEAD All DSDT/SSDTs were Extracted by AIDA64 (Recommended by patchers), got the text in dsdt.dsl, iASL Warning: There were 41 external control methods found during disassembly, but only 33 were resolved (8 unresolved).
#1849 | XPLAKE8175 | ⇗ @diderius6 ⇗ @Mov AX, 0xDEAD How can I find DSDT/SSDTs in my bios with a program? If there is a program available how can I extract all my DSDT/SSDTs?

#1850

diderius6

XPLAKE8175
I have had no Bios before,
where I need other SSDT tables.
Have you build a refs.txt file?
With its help, all unsolved dependencies are gone at once.
Problem in this is only to find the correct numbers.
When you use the iasl.exe from Sept 2012,
a lot of numbers are shown correct.
If I where at your place, i would read about refs.txt
on the hackintosh sites. They have the same problem and solved it for
a lot of Bios
Dietmar

#1851

Mov AX, 0xDEAD

> Zitat von ⇗ XPLAKE8175 im Beitrag ¶ #1848

> @diderius6 @Mov AX, 0xDEAD
> iASL Warning: There were 41 external control methods found during disassembly, but only 33 were resolved (8 unresolved).

iasl -fe external.txt -e ssdt1 ssdt2 ... ssdtx -d dsdt.bin
external.txt (example for h110):

> Zitat

> External (AL6F, MethodObj, 0)
> External (HLVT, MethodObj, 0)
> External (P0L6, MethodObj, 0)
> External (P1L6, MethodObj, 0)
> External (P2L6, MethodObj, 0)
> External (PS0X, MethodObj, 0)
> External (PS2X, MethodObj, 0)
> External (PS3X, MethodObj, 0)
> External (_SB_.PCI0.PAUD.PUAM, MethodObj, 0)
> External (_SB_.PCI0.XHC_.DUAM, MethodObj, 0)
> External (_SB_.PCI0.XHC_.RHUB.INIR, MethodObj, 0)
> External (_SB_.PCI0.SAT0.SDSM, MethodObj, 4)
> External (MDBG, MethodObj, 1)
> External (_SB_.TPM_.PTS_, MethodObj, 1)

if iasl found dependies in ssdt - ignore it, only dsdt is matter

#1852

Mov AX, 0xDEAD

> Zitat von ⇗ XPLAKE8175 im Beitrag ¶ #1849

> @diderius6 @Mov AX, 0xDEAD
> How can I find DSDT/SSDTs in my bios with a program? If there is a program available how can I extract all my DSDT/SSDTs?

UEFIExtract
DSDT file has signature "DSDT" at begin

#1853 | XPLAKE8175 | ⇗ @Mov AX, 0xDEAD How Can I add IT?

#1854

diderius6

⇗ @XPLAKE8175
I found 54 SSDT tables in your Bios 605.
Just use UEFI tool and search with SSDT.
Only from the *.raw files you always extract body and rename them
ssd1.aml until ssd54.aml .
Put them all together in one folder with DSDT.aml
and use the command line directed to that folder from
⇗ @Mov AX, 0xDEAD
Dietmar

#1855 | XPLAKE8175 | How can I find it? And I downgraded my bios to version 603

#1856

diderius6

⇗ @XPLAKE8175
Download the same Bios as yours from website.
Download latest version of Uefi Tool from here.
Put them both in one folder.
Open this downloaded Bios with this Uefi Tool.
Type in header of Uefi Tool search SSDT. Disable mark unicode there.
At the bottom are all the places are shown with found word SSDT.
Click each of them (only those called "raw") and click "extract body", store them one by one in one folder with name ssdt1.aml until ssdt54.aml.
The same for DSDT,
Dietmar

#1857 | XPLAKE8175 | I got non-ascii characters error.

#1858

diderius6

⇗ @XPLAKE8175
Some "raw" files may do not contain a valid SSDT table.
So, first add one, if no message about "non-ascii characters error"
appears the next and so on.
If for one table this message appears, just delete it.
Are you sure, that you chose "extract body" for each "raw" file
Dietmar

#1859 | XPLAKE8175 | I extracted files now I get AE_ALREADY_EXISTS Error.
#1860 | diderius6 | ⇗ @XPLAKE8175 ⇗ https://www.tonymacx86.com/threads/solve...s-error.195653/ Dietmar

## Page 125

#1861 | XPLAKE8175 | I'm Getting same error.

#1862

diderius6

⇗ @XPLAKE8175
You can also use acpidump on this notebook
for to get the loaded tables direct from memory.
This makes sure, that no table is loaded double.
In the comment of this error you find an explanation,
which device is also the same in another SSDT table.
From this comes the error, only 1 SSDT table is allowed for each device,
Dietmar
PS: Make sure, that for each disassemble try you use a new folder with all
the unchanged SSDT.aml and DSDT.aml in it.

#1863

XPLAKE8175

⇗ @diderius6
Is there any duplicate ssdt files in the zip and missing ssdts?
XPLAKE8175 has attached files to this post

- ⇗ ssdtdebug.zip

#1864 | XPLAKE8175 | ⇗ @diderius6 Did you extract my attached ssdt/dsdt files? Did you find my duplicate SSDTs or missing ssdts?

#1865

diderius6

⇗ @XPLAKE8175
Yes, I got it.
1,4,5,6,d,e,f,g,q,r,t,w are double ( I just delete them).
0,2,3,7,8,9,a,b,c,h,i,j,k,l,m,n,o,p,s,u,v,x,y,z are needed.
Dietmar
PS: Disassemble with c:\iasl -e ssdt*.aml -d dsdt.aml
Then you mod dsdt.dsl as I told
and recompile it with c:\iasl dsdt.dsl (your modded dsdt.dsl)
diderius6 has attached files to this post

- ⇗ BiosXrefstxtOri.rar

#1866

XPLAKE8175

⇗ @diderius6
I'm getting the same error but different error named failure creating object LONT. Here is the fully extracted SSDTs:
XPLAKE8175 has attached files to this post

- ⇗ iasl4.zip

#1867 | XPLAKE8175 | ⇗ @diderius6 Please send me the working dsdt.dsl.
#1868 | XPLAKE8175 | ⇗ @diderius6 Have you finished your work for my dsdt.dsl?

#1869

infuscomus

⇗ @XPLAKE8175
well I managed to get it to compile with iasl 20190703
I am inexperienced though, so I'm not sure if I broke anything
edit: also, i have not patched anything, just compiled.
infuscomus has attached files to this post

- ⇗ newdsdt.zip

#1870 | XPLAKE8175 | How can I get stock bios on my asus x555lb version 2012.

#1871

diderius6

⇗ @XPLAKE8175
Here is your modded DSDT.dsl and compiled dsdt.aml
for to awake from USB sleep
Dietmar
diderius6 has attached files to this post

- ⇗ dsdt.rar

#1872 | XPLAKE8175 | ⇗ @diderius6 Getting a5 error 0x00000001 and 0x00000002 again and again. The both acpi errors related with root resources.

#1873

diderius6

⇗ @XPLAKE8175
With asl.exe it does not work (gives A5 BSOD on newer compis for unknown reason).
You have to integrate my modded DSDT to your original Bios with full Acpi support.
Or you use "MPS" for XP hitting F5 during setup, in this case asl.exe works, because no ACPI.
When it is only acpi related,
try my very first acpi.sys from December 2018
Dietmar
diderius6 has attached files to this post

- ⇗ acpi.rar

#1874

diderius6

Today I start with XP SP3 UEFI boot.
I chose for this the board
GA-H110M-S2H
because I can flash Bios there easy, it has a COM port
and a XP friendly Bios, just a board where you can
install everything from XP to Win10.
My first test is, if I can install there any version of UEFI Vista 32 bit.
The first version of Vista, which has efi files is
'Longhorn' 6.0.5112.0) (beta1)
It has NTDETECT.COM, ntldr, bootmgr,
winldfw.efi, winnvram.efi.
The first Vista 32 bit,
which has full UEFI support is
''Longhorn'' 6.0.5219.0) (beta2)
It has bootmgr,
hibrsm32.efi, winldfw.efi, winnvram.efi,
bootmgfw.efi, bootmgr.efi.
The last version of Vista 32,
which has efi files is
''Longhorn'' 6.0.5472.5) (beta2)
It has bootmgr,
winload.efi, bootmgfw.efi, bootmgr.efi
Dietmar
PS: Also I will test, if it is possible,
to use the Win7(grub, bootia32.efi?), win8 32 bit efi files for UEFI boot of Vista, XP SP3.

#1875

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #1874

> GA-H110M-S2H
> ...
> My first test is, if I can install there any version of UEFI Vista 32 bit.

most modern MB is uefi x64, so impossible run anything 32 bit
there is hard way to do this - write uefi translator, in case winxp it will emulate real-mode bios functions, translate to uefi x64 calls, switch cpu from 16-bit real-mode to x64 protected-mode and vice versa. Some like CSM module, but as custom uefi loader on disk

## Page 126

#1876 | diderius6 | ⇗ @Mov AX, 0xDEAD I see on a chinese Website, that they succeed with bootia32.efi Dietmar ⇗ https://translate.google.com/translate?d...700262,15700265
#1877 | infuscomus | ⇗ @Mov AX, 0xDEAD can we maybe work around this by using a linux bootloader like grub2 to start and then load the .efi files?

#1878

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #1876

> I see on a chinese Website, that they succeed with bootia32.efi

fake, uefi x64 can only load \EFI\BOOT\BOOTX64.EFI (maybe linux loaders too with special names like "grubx64.efi")

#1879 | diderius6 | Mov AX, 0xDEAD "Some like CSM module, but as custom uefi loader on disk" Have you ever seen something like a generic CSM module Dietmar
#1880 | infuscomus | ⇗ @Mov AX, 0xDEAD If you boot into grub2 64-bit in EFI mode with grubx64.efi, can you start 32-bit .efi executables from there? like chainloader (hd0,4)/efi/Boot/bootmgfw.efi if bootmgfw.efi is 32-bit?

#1881

diderius6

May be, there is a way:
Is it possible, to flash into every 64 bit UEFI Bios
just the file BootIA32.efi
and start any 32 bit or 64 bit system now via this integrated
BootIA32.efi
Dietmar

#1882

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #1879

> Mov AX, 0xDEAD
> "Some like CSM module, but as custom uefi loader on disk"
> Have you ever seen something like a generic CSM module

i never heard about CSM projects, but anyone can see how it is implemented in real bioses (leaked 2013 sources from ami)
i know only about DUET, but this is emulation "uefi x64 over legacy bios"

#1883

Mov AX, 0xDEAD

> Zitat von ⇗ infuscomus im Beitrag ¶ #1880

> If you boot into grub2 64-bit in EFI mode with grubx64.efi, can you start 32-bit .efi executables from there?
> like
> chainloader (hd0,4)/efi/Boot/bootmgfw.efi
> if bootmgfw.efi is 32-bit?

this is interesting, because centos/fedora x64 ISOs have separate loaders for uefi_x64 and uefi_ia32:

> Zitat

> BOOTIA32.EFI->grubia32.efi->grub.cfg
> BOOTX64.EFI->grubx64.efi->grub.cfg

grub.cfg is same for both loaders and has command to load kernel:

> Zitat

> linuxefi /images/pxeboot/vmlinuz

vmlinuz is x64 kernel
seems exist way to run linux kernel with any uefi, but i dont understand how it works )

#1884 | infuscomus | ⇗ @Mov AX, 0xDEAD XP x64 works in 64-bit UEFI at least - ⇗ https://www.betaarchive.com/forum/viewto...=20327&start=82

#1885

Mov AX, 0xDEAD

> Zitat von ⇗ infuscomus im Beitrag ¶ #1884

> @Mov AX, 0xDEAD
> XP x64 works in 64-bit UEFI at least - ⇗ https://www.betaarchive.com/forum/viewto...=20327&start=82

yes, uefi x64 <-> os x64 and uefi x32 <-> os x32 works
diderius6 want to mix...

#1886 | diderius6 | ⇗ @Mov AX, 0xDEAD ⇗ https://wiki.ubuntuusers.de/Howto/Instal...auf_EFI-System/ Dietmar PS: 64 bit Uefi Bios => runs 32 Bit OS
#1887 | Mov AX, 0xDEAD | chinese guy maked custom loader/grub2x64.efi(??) to run DOS, XP, GRUB4DOS, WIN32, WIN64 ⇗ http://bbs.wuyou.net/forum.php?mod=viewthread&tid=373513 english comments with grub2x64.efi download link to ⇗ https://github.com/a1ive/grub/issues/2 maybe this is what we need or i wrong
#1888 | skullteria | Well, winload.exe on from longhorn 5048 until Vista 5307 won't work on real computer. When try load system, i get BILoadLibry 0x0000017. When i try some version up 5307, get A5 error. Somebody can try solve it , both BI error and A5? It is important use new loader on Xp/2003

#1889

infuscomus

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #1887

> chinese guy maked custom loader/grub2x64.efi(??) to run DOS, XP, GRUB4DOS, WIN32, WIN64
> ⇗ http://bbs.wuyou.net/forum.php?mod=viewthread&tid=373513
> english comments with grub2x64.efi download link to ⇗ https://github.com/a1ive/grub/issues/2
> maybe this is what we need or i wrong

⇗ @Mov AX, 0xDEAD
nice find! Thanks!
I was looking for something that could boot FreeDOS in UEFI mode.

#1890

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #1886

> @Mov AX, 0xDEAD
> ⇗ https://wiki.ubuntuusers.de/Howto/Instal...auf_EFI-System/
> PS: 64 bit Uefi Bios => runs 32 Bit OS

i've searched a little and found how it works - it is KERNEL magic )
if kernel compiled with special setting "CONFIG_EFI_MIXED", it can be runed in uefi_x32/uefi_x64 with special loader
⇗ https://cateee.net/lkddb/web-lkddb/EFI_MIXED.html
loader must have "EFI handover protocol" and grub2 probably implemented it as special command linuxelf in conf
linux-src-4.9\arch\x86\platform\efi\efi_thunk_64.S:

> Zitat

>     /
>      * Support for invoking 32-bit EFI runtime services from a 64-bit
>      * kernel.
>     /

so linux kernel has own emulation layer x32<->x64

## Page 127

#1891

diderius6

⇗ @Mov AX, 0xDEAD ⇗ @infuscomus

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #1887

> chinese guy maked custom loader/grub2x64.efi(??) to run DOS, XP, GRUB4DOS, WIN32, WIN64
> ⇗ http://bbs.wuyou.net/forum.php?mod=viewthread&tid=373513
> english comments with grub2x64.efi download link to ⇗ https://github.com/a1ive/grub/issues/2
> maybe this is what we need or i wrong

When I understand the discussion forum for this general grub2x64.efi correct,
XP SP3 can be just loaded via ntldr on a pur 64bit UEFI without any CSM support?
Only menu.lst with content
root (hd0,0)
chainloader /ntldr
boot
Thats all?
Dietmar
PS: I am not good with syntax for grub. Where has
"If you boot into grub2 64-bit in EFI mode with grubx64.efi, can you start 32-bit .efi executables from there?
like
chainloader (hd0,4)/efi/Boot/bootmgfw.efi
if bootmgfw.efi is 32-bit?"
to stay this special grub2x64.efi ?

#1892 | infuscomus | ⇗ @diderius6 if this grub2x64.efi is able to boot XP ntldr directly then we wont need to use bootmgfw.efi or any other vista beta files.

#1893

Mov AX, 0xDEAD

Presentation from Intel how linux kernel boot in mixed uefi mode
Mov AX, 0xDEAD has attached files to this post

- ⇗ mixing-it-up-with-efi-mixed-mode.pdf

#1894

diderius6

From the Betaarchive
Some Vista builds around Beta 2 actually have experimental UEFI support, and the winload.efi from 5219 x86 can actually boot XP.
So here is how to make it work.
Create two partition on the HDD, a C partition which is FAT for boot files, and a D partition which is NTFS for XP, make both partition as primary partition.
Install XP to D: in BIOS as normal.
Get these files from 5219 x86 ISO:
install.wim\Windows\System32\winload.efi
install.wim\Boot\EFI\Microsoft\BootMgr\bootmgfw.efi
Copy bootmgfw.efi to C:\EFI\Boot\bootia32.efi
and copy winload.efi to D:\Windows\System32
Then edit C:\boot.ini like this, change the path accordingly.
Yes, 5219 is one of the early builds that uses boot.ini in bootmgr instead of BCD.
Code:
[boot loader]
timeout=30
NOBCD
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /NOEXECUTE=OPTIN /FASTDETECT /USENEWLOADER
Then you should boot XP in EFI mode.
EDIT: On the Gigabyte h110m-s2h this Tutorial from betaarchive does not work.
Ok, when now you have a grub2, which can boot from any uefi 32 or Uefi 64bit Bios it should be done
Dietmar

#1895 | Mov AX, 0xDEAD | Another option is patching source code of boot- and os-loader (leaked Windows Shared Source). For loading win_x32 on uefi_x64 we still need translation layer, but much easy to integrate it to existing sources.
#1896 | Mov AX, 0xDEAD | Video CSM Project ⇗ https://github.com/davidcie/VgaShim
#1897 | diderius6 | ⇗ @Mov AX, 0xDEAD Can you compile the source code for win_x32 on uefi for Win server 2003 and XP SP3? This would be a big step forward, Dietmar PS: Have you tried to boot XP from Vista Uefi files?

#1898

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #1897

> @Mov AX, 0xDEAD
> Can you compile the source code for win_x32 on uefi
> for Win server 2003 and XP SP3? This would be a big step forward,

these sources incomplete, need first reverse missing files (many .h and libs)

#1899 | diderius6 | ⇗ @Mov AX, 0xDEAD With Win8 32bit, may be other can help you Dietmar

#1900

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #1899

> @Mov AX, 0xDEAD
> With Win8 32bit, may be other can help you

Sorry, i don't have motivation to do something with "pure" uefi booting since most desktop MBs still have CSM, that's enough for winxp.
only booting from single 3TB+ GPT disk is still an interesting problem

#1901

diderius6

⇗ @daniel_k
I just do the USB mod in DSDT in Bios for full Intel chipset USB3 support on the
gigabyte h110m-s2h
board, works nice :))
Dietmar
⇗

#1902

diderius6

Seems, that there is an UEFI 32 bit Windows just now, which can start on Uefi 64 bit Bios
Dietmar
"WIMBoot is available for client editions of Windows 8.1 with Windows 8.1 Update only (not server versions). All architectures are supported, including amd64, x86, and ARM. Some enterprise deployment tools do not support WIMBoot.
WIMBoot is available only for UEFI-based PCs running in UEFI mode (legacy BIOS-compatibility mode isn't supported)."
"You can install and boot Windows 8 32bit UEFI, but it's not that simple. It involves using command prompt and a Windows PE 32 bit UEFI boot disk (if available) along with a 32 bit Windows WIM file.
The most easy way is to remove the hard disk (or ssd) and get a USB adapter for it and use another workstation to deploy the image. If this option is not available you will need to boot from the Windows PE disk 32 bit UEFI and have the wim image in that disk.
I'll try to keep the instructions as simple as possible. If you don't understand a term, you can google that. There's plenty of information available. If you don't have a wim file available google instructions on how to capture an OS image properly. The beauty of this is that it doesn't have to be UEFI, it can be BIOS, but it has to be 32 bit. I installed mine to a Virtual Machine then captured the wim file.
On CMD type diskpart
Type "list disk" so you know what disk you are going to format, then follow the next commands:
Select disk #
Clean
Convert GPT
Create partition MSR size=128
Create Partition EFI size=100
Format fs=fat32 quick Label="System"
Assign letter=S
Create Partition Primary
Format fs=ntfs quick label="Windows"
Assign letter=W
exit
Now it's time to apply the image using DISM
Dism /apply-image /imagefilae:(directory and filename of your wim file) index:#(the number of the image. If you used a captured image of your own, type 1, otherwise you'll need to know which one is it) /applydir:w:\
example:
dism /apply-image /imnagefile:x:\win832uefi.wim /index:1 /applydir:w:\
Wait until it finished. USB 2.0 can be quite slow.
Finally, this is the crucial part, adding the boot manager with UEFI support
w:\windows\system32\bcdboot w:\windows /f ALL /s S:
Voila! Install the HDD to your device or reboot and remove Windows PE media. You should be able to boot uefi 32 bit now.
Hope this helped. "
"After a bit of tampering with additional ISOs, I've realized that you can just replace the \sources\install.wim file on a Win 8/8.1/10 bootdisk with the one from Win7 to make it work.
Just get a Win8/8.1/10 ISO
Open it using an ISO-explorer (like UltraISO)
Replace \sources\install.wim with that from the Win7 ISO/DVD
Save as a new ISO, and/or burn it into the installation DVD or on a USB/external HDD active Fat32 partition.
The installation UI will be of the bootdisk's Win version, but it will certainly install Windows7."

#1903

daniel_k

> Zitat von ⇗ infuscomus im Beitrag ¶ #1833

> @daniel_k
> PETool 0.0.5 can insert extra space in-between sections, maybe it can help?
> originally found here
> ⇗ https://msfn.org/board/topic/146529-pe-t...eating-patches/

Thanks!

#1904 | daniel_k | ⇗ @Andalu Did you the black USB 2.0 and blue USB 3.0 ports? All ports work? Just saw the service manual, there isn't much to be done if there are no settings available in BIOS Setup.

#1905

daniel_k

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #1840

> > Zitat von ⇗ daniel_k im Beitrag ¶ #1831

> > ⇗ @Mov AX, 0xDEAD
> > Unfortunately there are just 5 free bytes, useless.

> 1) in drivers exist section INIT, this is also code section, but after driver initialised this memory is cleaned
> to avoid this rename section to .text and make it in header nopageable and nondiscardable
> or
> 2) create new code section, virtual adress must not overlap with existing sectons

Thanks for your suggestions, ⇗ @Mov AX, 0xDEAD!
Will try later, way too much work to patch 120+ calls.

## Page 128

#1906 | daniel_k | ⇗ @diderius6, sent you a PM with something interesting for you to try. PS: Nice job with your H110 board! Good luck with your UEFI x86 project!
#1907 | diderius6 | ⇗ @daniel_k Yesssaa, nice:)) Do you have a link for this, is it your project Dietmar

#1908

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #1904

> @Andalu
> Did you the black USB 2.0 and blue USB 3.0 ports?
> All ports work?
> Just saw the service manual, there isn't much to be done if there are no settings available in BIOS Setup.

All ports of my two motherboards, including usb3, work correctly as usb2.
For the Msi CSM-Q87M-E43, although the two options XHCI hand-off and EHCI hand-off are available in the bios the driver don't install anyway and i got errore code 10 for the "Intel USB3.1 extensible host controller"; instead for the older mobo (IPIMB-AR Rev.1.02A from acer aspire M3985) with no XHCI and EHCI options available, the driver loaded correctly but usb3 ports act still as usb2.
The device ID are PCI\VEN_8086&DEV_8C31&CC_0C0330 for Msi CSM-Q87M-E43 and PCI\VEN_8086&DEV_1E31&CC_0C0330 for IPIMB-AR.
Thanks for your attention ;)

#1909

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #1901

> I just do the USB mod in DSDT in Bios for full Intel chipset USB3 support on the

what mod ? 64bit constants ->32 ?

#1910

diderius6

⇗ @Mov AX, 0xDEAD
Yes, some 64bit constants cant live together with XP 32 bit until now in DSDT.
This is minimod for to awake USB on Intel chipset here for the gigabyte h110m-s2h board
Dietmar
diderius6 has attached files to this post

- ⇗ DSDT.rar

#1911 | daniel_k | ⇗ @diderius6, yeah, it's my project. Shh, it's private, for now. Sent you the link. Please give me your feedback by PM.

#1912

daniel_k

⇗ @Andalu, unfortunately, for now, I don't have any other suggestions.
What I can say is that at least it works in USB 2.0 mode in the Acer board. Better than nothing.
About the MSI board, will take a look at its ACPI table to see if there is something suspecting.
Mod the Acer BIOS may be too risky, I wouldn't do that, it's an old board, you may end up spending more money in case something goes wrong.

#1913

diderius6

⇗ @daniel_k
For UEFI boot and I think all other steps of future XP this is a good base.
Very soon XP will be more modern than Win7.
Have you read in post above, that it is possible to
use all the *.efi from win8, 8.1, 10 for Win7 (also efi 32 bit on 64 bit Uefi Bios).
Just change on the installations medium the original install.wim
against your wished one.
I just try to use the x86 *.efi files from Win8 for a direct efi boot of Vista 32 bit
Dietmar

#1914

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #1910

> @Mov AX, 0xDEAD
> Yes, some 64bit constants cant live together with XP 32 bit until now in DSDT.

ok i dont need this because i have this )

#1915 | diderius6 | ⇗ @Mov AX, 0xDEAD Is this QWordConst_check code in your acpi.sys for XP SP3? Have you tested, if this code overcomes the BSOD A5 during use of asl.exe with full acpi support uploading a modded DSDT Dietmar
#1916 | diderius6 | ⇗ @daniel_k I just have integrated the STORAHCI.sys driver from ⇗ @skullteria from post 1020 and install it on the gigabyte h110m-s2h board Dietmar
#1917 | Andalu | ⇗ @daniel_k Thanks for your time ;)

#1918

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #1915

> Have you tested, if this code overcomes the BSOD A5
> during use of asl.exe with full acpi support uploading a modded DSDT

this patch to _ParteIntObj allow use 0x0E opcode(QWORD_OP) in dsdt code, no more A5-C0140001 error for x64 constants.
for full functionality need set "0x0E record" in _OpcodeTable to _atDataObj (_atDataObj is record for integers types).

#1919

daniel_k

⇗ @diderius6 and all
Please use the driver in the archive AMDXHCI_XP_FINAL.rar.
It works just fine on Intel USB 3.x controllers on real machines and on VirtualBox with USB controller in 3.0 (XHCI) mode.
I've used a trick, so USBD.SYS is automatically installed if missing.
Updated with V2 (Dec 19, 2019):
- revised device check patch
- applied small bug fix to 32-bit (x86), as seen on newer 153 and later releases. 64-bit is not affected.

#1920 | daniel_k | ⇗ @diderius6 If I understand correctly and if Mov AX, 0xDEAD gave us all the required steps to add support for qwords, try the acpi.sys (checked/debug version included) or apply the changes to yours

## Page 129

#1921

daniel_k

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #1809

> > Zitat von ⇗ daniel_k im Beitrag ¶ #1786

> > By the way, how much RAM available does XP x64 shows in System Properties?
> > For some reason, here it shows only 15.9GB instead of the full 16.0 GB RAM.

> check with any e820 tool ram ranges, if is it 15.9 - bios claimed some ram

Which tool would you recommend?
Curious to see. Is it possible to tell the device the RAM is reserved to?

#1922

diderius6

⇗ @daniel_k
I just test your mod for qwords on acpi.sys on the Gigabyte board h110m-s2h.
There it gives BSOD 0x7B.
This BSOD belongs to the mod in the acpi.sys,
because with original acpi.sys it starts normal
and also with modded acpi.sys in "MPS" mode, means
without any acpi
Dietmar

#1923

diderius6

⇗ @daniel_k ⇗ @Mov AX, 0xDEAD
During tests with the Gigabyte h110m-s2h board
I start to understand, how the asl.exe tool works.
asl.exe does nothing more, than to copy the wished DSDT.aml file
to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ACPI\parameters.
In december last year I did heavy mod the DSDT table in Bios of h110, so that no need for mod
in acpi.sys was needed.
With this heavy modded Bios I noticed an interesting thing: asl.exe copies as usual the modded dsdt table to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ACPI\parameters.
But now, on next reboot XP uses the original Bios DSDT, means not interested in the modded DSDT at
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ACPI\parameters.
Now it is clear: The mod in Bios with OSYS meets (blocks) a function, that XP needs for to use the DSDT in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ACPI\parameters.
But because this function is blocked via OSYS for XP in Bios, the table cant be loaded
and so the original DSDT from Bios is used.
Conclusion: In this via Osys blocked function happens later the BSOD A5 of (asl.exe used before),
when XP can use it because of no block via OSYS
Dietmar

#1924

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1921

> Which tool would you recommend?
> Curious to see. Is it possible to tell the device the RAM is reserved to?

best is use livecd with DOS + e820.exe/EXTINFO.EXE
worst is rweverything, it show e820 map other way
Mov AX, 0xDEAD has attached files to this post

- ⇗ e820.zip

#1925

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1920

> @diderius6
> If I understand correctly and if Mov AX, 0xDEAD gave us all the required steps to add support for qwords, try the acpi.sys (checked/debug version included) or apply the changes to yours

1 hook _parseintobj in place like "dec esi" (esi - opcode), comparing esi vs 0xe8 (given that the compiler has optimized the CASE statement in C Language and the esi is constantly decreasing), then restore original instruction and jmp back. I chose hook in instruction "sub esi, 0F3h" and replaced it to "jmp _QWordConst_check"
2 allocate free bytes in code section, add processing 0xe8 opcode (result.integer is just "+8")
3 add reloc to 0x2D368(0x1D368 RVA)

#1926 | daniel_k | ⇗ @Mov AX, 0xDEAD, thanks for the E820 tool.

#1927

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1926

> @diderius6, try both these, not sure if I following the logic correctly, so please try both.
> At least it didn't crash here!

still no reloc, after acpi.sys mapped to some adress in high memory, 0x0E record in opcodetable still be "90 D2 02 00", so pointed to 0x0002d290
=> access violation err (

#1928 | daniel_k | ⇗ @Mov AX, 0xDEAD, oops, I was sleepy. so missed that! ⇗ @diderius6, try both these, not sure if I followed the logic correctly, so please try both. At least it didn't crash here!

#1929

daniel_k

⇗ @diderius6, does my XP 2003 properly shows all RAM installed in System Properties?
If so, please run the utilities shared by Mov AX, 0xDEAD, in pure DOS:
¶ Windows XP SP3 32bit and modern PC parts (129)
To save the output, run
E820 > e820.txt
EXTINFO > extinfo.txt
Although I'm sure you know that. :D
I'd like to compare it with the output of my system, as follows:

    E820 Dump Tool - Version 0.1.0 - Copyright(C) Mike Hou 2011
    ----------------------------------------------------------------
            Base Address                Length             Type
    -----------------------+------------------------------+---------
     0: 0x00000000-00000000 (0x00000000-0009C400 ~ 625 KB) 1 (Memory)
     1: 0x00000000-0009C400 (0x00000000-00003C00 ~  15 KB) 2 (Reserved)
     2: 0x00000000-000E0000 (0x00000000-00020000 ~ 128 KB) 2 (Reserved)
     3: 0x00000000-00100000 (0x00000000-3FF00000 ~ 1023 MB) 1 (Memory)
     4: 0x00000000-40000000 (0x00000000-00400000 ~   4 MB) 2 (Reserved)
     5: 0x00000000-40400000 (0x00000000-74F90000 ~   1 GB) 1 (Memory)
     6: 0x00000000-B5390000 (0x00000000-00001000 ~   4 KB) 4 (NVS)
     7: 0x00000000-B5391000 (0x00000000-00001000 ~   4 KB) 2 (Reserved)
     8: 0x00000000-B5392000 (0x00000000-080CC000 ~ 128 MB) 1 (Memory)
     9: 0x00000000-BD45E000 (0x00000000-004FB000 ~   4 MB) 2 (Reserved)
    10: 0x00000000-BD959000 (0x00000000-000B3000 ~ 716 KB) 1 (Memory)
    11: 0x00000000-BDA0C000 (0x00000000-003C3000 ~   3 MB) 4 (NVS)
    12: 0x00000000-BDDCF000 (0x00000000-01230000 ~  18 MB) 2 (Reserved)
    13: 0x00000000-BEFFF000 (0x00000000-00001000 ~   4 KB) 1 (Memory)
    14: 0x00000001-00000000 (0x00000003-3F000000 ~  12 GB) 1 (Memory)
    15: 0x00000000-BF000000 (0x00000000-01000000 ~  16 MB) 2 (Reserved)
    16: 0x00000000-F0000000 (0x00000000-08000000 ~ 128 MB) 2 (Reserved)
    17: 0x00000000-FE000000 (0x00000000-00011000 ~  68 KB) 2 (Reserved)
    18: 0x00000000-FEC00000 (0x00000000-00001000 ~   4 KB) 2 (Reserved)
    19: 0x00000000-FED00000 (0x00000000-00001000 ~   4 KB) 2 (Reserved)
    20: 0x00000000-FEE00000 (0x00000000-00001000 ~   4 KB) 2 (Reserved)
    21: 0x00000000-FF000000 (0x00000000-01000000 ~  16 MB) 2 (Reserved)
    ----------------------------------------------------------------

    Extended Memory:
    INT $15, AH=$88
    Memory above 1M: 0 Kb
    INT $15, AX=$E801
    Free memory between 1M and 16M, in K: 0 Kb
    Free memory above 16M, in 64K blocks: 0 = 0 Kb
    Configured memory between 1M and 16M, in K: 0 Kb
    Configured memory above 16M, in 64K blocks: 0 = 0 Kb
    INT $15, EAX=$0000E820
    0000000000000000 : 000000000009C400 1 (Available)
    000000000009C400 : 0000000000003C00 2 (Reserved)
    00000000000E0000 : 0000000000020000 2 (Reserved)
    0000000000100000 : 000000003FF00000 1 (Available)
    0000000040000000 : 0000000000400000 2 (Reserved)
    0000000040400000 : 0000000074F90000 1 (Available)
    00000000B5390000 : 0000000000001000 4 (ACPI NVS)
    00000000B5391000 : 0000000000001000 2 (Reserved)
    00000000B5392000 : 00000000080CC000 1 (Available)
    00000000BD45E000 : 00000000004FB000 2 (Reserved)
    00000000BD959000 : 00000000000B3000 1 (Available)
    00000000BDA0C000 : 00000000003C3000 4 (ACPI NVS)
    00000000BDDCF000 : 0000000001230000 2 (Reserved)
    00000000BEFFF000 : 0000000000001000 1 (Available)
    0000000100000000 : 000000033F000000 1 (Available)
    00000000BF000000 : 0000000001000000 2 (Reserved)
    00000000F0000000 : 0000000008000000 2 (Reserved)
    00000000FE000000 : 0000000000011000 2 (Reserved)
    00000000FEC00000 : 0000000000001000 2 (Reserved)
    00000000FED00000 : 0000000000001000 2 (Reserved)
    00000000FEE00000 : 0000000000001000 2 (Reserved)
    00000000FF000000 : 0000000001000000 2 (Reserved)

Can't speak of the Z390, but the Z370 (where I ran the tools) is virtually the same as other 200 series chipsets.

#1930

diderius6

⇗ @daniel_k
About the last acpi-test1.sys, acpi-test2.sys
they both show BSOD A5 (0x11,..) without any asl.exe
on asrock fatalty k6 board
and on the EVGA z390 board,
which Bios is XP friendly
Dietmar
PS: Correcting this BSOD A5 (0x11,..) together with mod from other, working acpi.sys,
changes the situation to BSOD A5 (0x7B,..)

#1931 | daniel_k | ⇗ @diderius6, remember that Mov AX, 0xDEAD's patch is for qwords only. It only affects the USB DSDT fix. ToInteger and other opcodes may still crash Windows. Please run E820 and EXTINFO on your H110 board, when possible.

#1932

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1929

> `3: 0x00000000-00100000 (0x00000000-3FF00000 ~ 1023 MB) 1 (Memory)
> 5: 0x00000000-40400000 (0x00000000-74F90000 ~ 1 GB) 1 (Memory)
> 8: 0x00000000-B5392000 (0x00000000-080CC000 ~ 128 MB) 1 (Memory)
> 14: 0x00000001-00000000 (0x00000003-3F000000 ~ 12 GB) 1 (Memory)`
> Can't speak of the Z390, but the Z370 (where I ran the tools) is virtually the same as other 200 series chipsets.

total is 14.1, waste is about 2 gb ?
this bios is not good, it doesnt advertise memory in region 0x8000 0000-0xFFFF FFFF (2G) and no extend this claimed region in high pae ranges (limited to 0x3 3F00 0000)

#1933 | daniel_k | Mov AX, 0xDEAD Does it has something to do with my GTX 980 4GB? Maybe my ACPI table patch is not correct?! Or if there is something wrong in DOS, the same can be seen on Windows?
#1934 | diderius6 | ⇗ @daniel_k ⇗ @Mov AX, 0xDEAD This is via Freedos 1.1 life CD on the gigabyte h110m-s2h board with 32 GByte ram Dietmar ⇗ ⇗
#1935 | daniel_k | ⇗ @diderius6, thanks! In the second picture, #3, there are 3GB (Memory), while on my Z370 there is only 1GB. Can you do the same on the Z370 and Z390, when you have time. Any system with 2x 8GB sticks?

## Page 130

#1936 | diderius6 | ⇗ @daniel_k I have only 1,2*4GB or 1,2,3,4 *16GB Dietmar
#1937 | diderius6 | ⇗ @daniel_k This is from asrock fatal1ty z370 gaming k6 board, also 32 Gb ram Dietmar ⇗ ⇗
#1938 | diderius6 | ⇗ @daniel_k And this is from EVGA Z390 DARK, also 32 Gb ram Dietmar ⇗ ⇗
#1939 | diderius6 | ⇗ @daniel_k On all 3 compis device manager shows 31.9 Gbyte free on your nice XP/ 2003 32 bit project. When I use 4 Gb ram, they all show there 3.9 Gbyte free Dietmar

#1940

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1933

> @Mov AX, 0xDEAD
> Does it has something to do with my GTX 980 4GB?

i dont think so, seems bug in bios or maybe hardware limitation (?)
my h110 4G system:

> Zitat

>     3	0000000000100000  00000000B3D44000  1:Available
>     6	00000000B3E46000  0000000007DF5000  1:Available
>     12	0000000100000000  000000003F400000  1:Available

in low memory available 2877+125 =3002Mb, in high pae 1012Mb, total 4014Mb ~ 4096Mb
in my case bios set some hardware mapping(?) to translate cpu "physical adresses" above first 4G range to "low" ramchip physical lines, because ram is 4G and has relative 0x0-0xFFFF FFFF adressing only

#1941

daniel_k

> Zitat von ⇗ diderius6 im Beitrag ¶ #1939

> @daniel_k
> On all 3 compis device manager shows 31.9 Gbyte free
> on your nice XP/ 2003 32 bit project.
> When I use 4 Gb ram, they all show there 3.9 Gbyte free
> Dietmar

Thank you very much for your tests.
Do any of your graphics cards have 4GB of memory?

#1942 | diderius6 | ⇗ @daniel_k "Do any of your graphics cards have 4GB of memory?" No Dietmar

#1943

daniel_k

⇗ @Mov AX, 0xDEAD, thank you very much for helping us and sharing your knowledge.
Now I understand how ACPI.SYS processes the opcodes and calls a specific function for every opcode.
I was wondering, as I still don't have the knowledge to do it myself, wouldn't it be possible to add support for CreateQWordFieldOp by using the same function that processes CreateDWordFieldOp?
I mean, by adding code to handle the 64-bit address or to "extract" only the lower 32-bit portion of it and later use it as usual. Would it work somehow?

#1944 | daniel_k | ⇗ @diderius6, as my GTX 980 has 4GB of memory, surely it is the culprit.

#1945

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1943

> I was wondering, as I still don't have the knowledge to do it myself, wouldn't it be possible to add support for CreateQWordFieldOp by using the same function that processes CreateDWordFieldOp?

CreateQWordFieldOp is just creating field and no more, yes it is possible add new opcode, but it useless
fields actual used in other procs like _ReadField/_ReadFieldObj/... and need heavy patch it to support 64b fields
after i discovered "vista beta acpi.sys" anyone can add new opcode handlers to classic winxp acpi.sys, but only 32 bit integers betas is compatible with winxp. 1) copy bytes from existing acpi.sys 2) add relocs 3) create missing structs 4) add missing import or replace with internal impelemtation
that's how I made my acpi.sys but took the code from win7 x32 (converted back 64-int logic to 32-int)

#1946

daniel_k

⇗ @Mov AX, 0xDEAD, what I was trying to say is:
The following ACPI "lines" crashes XP:

    If (LEqual (M64L, Zero))
    {
    	CreateQWordField (BUF0, \_SB.PCI0._Y0F._LEN, MSLN)  // _LEN: Length
    	Store (Zero, MSLN) /* \_SB_.PCI0._CRS.MSLN */
    }
    	Else
    {
    	CreateQWordField (BUF0, \_SB.PCI0._Y0F._LEN, M2LN)  // _LEN: Length
    	CreateQWordField (BUF0, \_SB.PCI0._Y0F._MIN, M2MN)  // _MIN: Minimum Base Address
    	CreateQWordField (BUF0, \_SB.PCI0._Y0F._MAX, M2MX)  // _MAX: Maximum Base Address
    	Store (M64L, M2LN) /* \_SB_.PCI0._CRS.M2LN */
    	Store (M64B, M2MN) /* \_SB_.PCI0._CRS.M2MN */
    	Subtract (Add (M2MN, M2LN), One, M2MX) /* \_SB_.PCI0._CRS.M2MX */
    }

- add CreateQWordField, which actually calls CreateDWordField.
- Patch Store so it will ignore higher order address and just copy the lower 32-bit part.
- XP is tricked into thinking we are working with 32-bit addresses.

#1947

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1946

> - add CreateQWordField, which actually calls CreateDWordField.
> - Patch Store so it will ignore higher order address and just copy the lower 32-bit part.
> - XP is tricked into thinking we are working with 32-bit addresses.

This trick will work.
no need touch "store" because in winxp all ints are 32, so M64L/M64B/Zero is 32 too

#1948

daniel_k

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #1947

> > Zitat von ⇗ daniel_k im Beitrag ¶ #1946

> > - add CreateQWordField, which actually calls CreateDWordField.
> > - Patch Store so it will ignore higher order address and just copy the lower 32-bit part.
> > - XP is tricked into thinking we are working with 32-bit addresses.

> This trick will work.
> no need touch "store" because in winxp all ints are 32, so M64L/M64B/Zero is 32 too

From what I understand, that was the reply I expecting.
6F680200-40BA0200-8A
1- Function address
2- Opcode "CreateDwordField" String
3- Opcode
Can I put my new opcode anywhere between two already existing opcodes?

#1949

daniel_k

⇗ @diderius6, are you following the posts?
I've had an idea about a trick and Mov AX, 0xDEAD said it will work.
Wanna give it a try?
It converts CreateQwordField into CreateDwordField.
Basically I've added CreateQwordField opcode pointing to CreateDwordField function.
Maybe this helps with X570?
Do you have a board with stock BIOS?

#1950

diderius6

⇗ @daniel_k
Half year ago, I have had the same idea to change CreateQwordField into CreateDwordField.
But just renaming was not enough and because I am no programmer I do not have the possibility
to make it work.
So I am just happy, when it can be done.
What do you mean with "stock Bios"
Dietmar
PS: Of course I will test. We only make big advantages, when we work together!

## Page 131

#1951

daniel_k

⇗ @diderius6
Whoa, I was not the first then?
I'm asking you to test because currently only have this PC built and with modded BIOS, so I can't keep flashing back and forth because I have some work to do.
Just clarifying I'm not lazy or something.
By stock BIOS I mean unpatched DSDT.
So it would be to test your H110, 'cause the Z370 has the ToInteger opcode, which crashes XP. Remember that patched DSDT I've sent to you?

#1952

diderius6

⇗ @daniel_k
The opcode
Switch (ToInteger (Arg2))
can be changed to
Switch (Arg2)
The compiler then cries, but set it to integer without using the ACPI 2.0 word ToInteger.
So, please tell me, what board should I use for test with which Bios
Dietmar
PS: Yes, I can flash now any Bios on any board forward and back, as much as I like.

#1953 | daniel_k | ⇗ @diderius6, please try on the H110 with the unmodded (original) BIOS. So I'll add ToInteger to ACPI.SYS, which will call Switch. If this works, no more DSDT hacking needed! EDIT: Switch does not exist in ACPI.SYS. Does XP ignores this? Will check ACPI specs.

#1954

diderius6

⇗ @daniel_k
Last acpi-test1.sys gives on original Bios F25
on the gigabyte h110m-s2h board
BSOD 0x000000A5 (0x00000011, 0x00000008, xxx, yyy)
Dietmar
PS: The same BSOD for last acpi-test2.sys.
0x11 : ACPI_SYSTEM_CANNOT_START_ACPI The system could not enter ACPI mode
8 : Failed to load DDB
EDIT: It is the same BSOD, problem, as around the post 217 here. I solved it there with unconditional jmp EB in acpi.sys.

#1955 | daniel_k | ⇗ @diderius6 Need to work some more. Thanks for testing it. I've got an idea about ToInteger, replace with Return. EDIT: Nevermind, I've got an idea, so I can try without messing with BIOS. I'm leaving for now, have a good night, Dietmar!
#1956 | diderius6 | ⇗ @daniel_k "Does DSDT can be modded in VirtualBox? Did you ever try?" I think yes, but the results on real compi may be different Dietmar

#1957

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1948

> 6F680200-40BA0200-8A
> 1- Function address
> 2- Opcode "CreateDwordField" String
> 3- Opcode

Not exactly, record begin with "40BA0200" - offset to string representation
8a - opcode
64BA0200 - offset to "CCN", encoded types of arguments (char,char, int ?)
02 - i dont know
.....
FF680200 - offset to handler, _CreateDWordField
if no need create new implementation, for CreateQWordField enough set 0x8F record same as 0x8A =>"10 CA 02 00"
then opcode 0x8f is equivalent of 0x8a

#1958

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1953

> Switch does not exist in ACPI.SYS. Does XP ignores this? Will check ACPI specs.

switch()+case() is no real commands
switch (Arg0) -> case (0x04) {...} is set of low level command like _T_1 = Arg0, if If (_T_1 == 0x04) then {...}
_T_1 - temp variable

#1959

diderius6

BSOD 0x000000A5 (0x00000011, 0x00000008, xxx, yyy)
has nothing to do with
CreateQWordField.
When you dont patch your DSDT against reserved word from Acpi 2.0
CreateQWordField
you get classical BSOD
A5 (0x3,c0140001,xxx,yyy)
Dietmar

#1960

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #1956

> @daniel_k
> "Does DSDT can be modded in VirtualBox? Did you ever try?"
> I think yes, but the results on real compi may be different

dsdt is hardcoded in Vbox (VBoxDD.dll)
old qemu 1.6 load dsdt from file acpi-dsdt.aml if runed with "-M pc" (but qemu is slow and no gui)

#1961

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #1959

> BSOD 0x000000A5 (0x00000011, 0x00000008, xxx, yyy)
> has nothing to do with
> CreateQWordField.

apply your previous patches, this acpi.sys is classic v5512 from xp sp3

#1962 | daniel_k | ⇗ @Mov AX, 0xDEAD, thanks! ⇗ @diderius6, the "other" qword patch is causing the crashes. This one boots here. Try it on your H110.

#1963

daniel_k

⇗ @Mov AX, 0xDEAD
Can you please confirm this code flow is correct, please?

    2B1D0: 83FE02                         cmp          esi,2
    2B1D3: 740B                           jz          .2B1E0   -> THIS IS CORRECT?
    2B1D5: 81EEF3000000                   sub          esi,0000000F3
    2B1DB: E976D9FFFF                     jmp         .28B56
    2B1E0: 8B31                           mov          esi,[ecx]
    2B1E2: 8B36                           mov          esi,[esi]
    2B1E4: 897208                         mov          [edx][8],esi
    2B1E7: 830108                         add          d,[ecx],8
    2B1EA: E9ADD9FFFF                     jmp         .28B9C

#1964 | diderius6 | ⇗ @daniel_k This acpi.sys gives on the Gigabyte board H110 with original Bios F25 A5 (0x3, xxx, c0140001, yyy) which is the BSOD for unknow words from ACPI 2.0 for XP Dietmar
#1965 | daniel_k | ⇗ @diderius6 I'll take a look at the DSDT. ⇗ @Mov AX, 0xDEAD Did you try this method? What was the outcome?

## Page 132

#1966

daniel_k

⇗ @diderius6, it crashes because of this:

                Device (NVM1)
                {
                    Name (_ADR, 0x00C1FFFF)  // _ADR: Address
                    Method (_INI, 0, NotSerialized)  // _INI: Initialize
                    {
                        NITV = NIT1 /* \NIT1 */
                        NPMV = NPM1 /* \NPM1 */
                        NPCV = NPC1 /* \NPC1 */
                        NL1V = NL11 /* \NL11 */
                        ND2V = ND21 /* \ND21 */
                        ND1V = ND11 /* \ND11 */
                        NLRV = NLR1 /* \NLR1 */
                        NLDV = NLD1 /* \NLD1 */
                        NEAV = NEA1 /* \NEA1 */
                        NEBV = NEB1 /* \NEB1 */
                        NECV = NEC1 /* \NEC1 */
                        NRAV = NRA1 /* \NRA1 */
                        NMBV = NMB1 /* \NMB1 */
                        NMVV = NMV1 /* \NMV1 */
                        NPBV = NPB1 /* \NPB1 */
                        NPVV = NPV1 /* \NPV1 */
                        NRPN = NRP1 /* \NRP1 */
                        NCRN = Zero
                        ARPC (NRPN, RefOf (PWRG), RefOf (RSTG), RefOf (SCLK))  ---> CULPRIT
                    }
    ...

Method ARPC has an ToInteger opcode.
There are 3 instances of that command line (NVM1, NVM2 and NVM3)

#1967

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1963

> @Mov AX, 0xDEAD
> Can you please confirm this code flow is correct, please?

>     2B1D0: 83FE02                         cmp          esi,2
>     2B1D3: 740B                           jz          .2B1E0   -> THIS IS CORRECT?

>     2B1E0: 8B31                           mov          esi,[ecx]

correct, jz if esi == 2 (esi was decreases to -0x0c before)

#1968 | diderius6 | ⇗ @Mov AX, 0xDEAD ⇗ @daniel_k I tried integrate my own mod for acpi.sys. acpi-test1.sys gives with my mod then again the BSOD A5 (0x3, xxx, c0140001, yyy) for unknown words from Acpi 2.0 acpi-test2.sys gives then BSOD 0x7B Dietmar
#1969 | daniel_k | ⇗ @Mov AX, 0xDEAD, thanks! ⇗ @diderius6, try this one, added ToInteger as Return. It is not correct, but the "best" one I could find. With the original BIOS from Gigabyte, did it worked before just with your patches? Please download the file again.
#1970 | diderius6 | ⇗ @daniel_k I have to disable via OSYS also ConcatenateResTemplate Dietmar PS: ToInteger is just ignored from original acpi.sys from XP Sp3.

#1971

diderius6

⇗ @daniel_k
ConcatenateResTemplate
seems to be the reason,
your last acpi.sys gives also
BSOD A5 (0x3, xxx, c0140001, yyy) for unknown words from Acpi 2.0
Dietmar

#1972

daniel_k

⇗ @diderius6, no, ConcatenateResTemplate is not required.
Just disable via OSYS the following:
ARPC (NRPN, RefOf (PWRG), RefOf (RSTG), RefOf (SCLK))
You can see this in BIOS from many manufacturers.
Hmm, ToInteger does crashes Server 2003. Are you sure?
This one also cause crashes:

            Method (HCID, 1, Serialized)
            {
                Name (_T_1, Zero)  // _T_x: Emitted by ASL Compiler
                Name (_T_0, Zero)  // _T_x: Emitted by ASL Compiler
                If (OSYS >= 0x07D6)
                {
                    While (One)
                    {
                        _T_0 = ToInteger (Arg0)
                        If (_T_0 == Zero)
                        {
                            Local0 = L0SM /* \L0SM */
                        }
                        ElseIf (_T_0 == One)
                        {
                            Local0 = L1SM /* \L1SM */
                        }
                        ElseIf (_T_0 == 0x02)
                        {
                            Local0 = L2SM /* \L2SM */
                        }
                        Else
                        {
                            Local0 = L3SM /* \L3SM */
                        }

                        Break
                    }

                    While (One)
                    {
                        _T_1 = ToInteger (Local0)
                        If (_T_1 == Zero)
                        {
                            Return ("INT3471")
                        }
                        ElseIf (_T_1 == One)
                        {
                            Return ("INT33BE")
                        }
                        ElseIf (_T_1 == 0x02)
                        {
                            Return ("INT3476")
                        }
                        ElseIf (_T_1 == 0x03)
                        {
                            Return ("INT3477")
                        }
                        ElseIf (_T_1 == 0x04)
                        {
                            Return ("INT3474")
                        }
                        ElseIf (_T_1 == 0x05)
                        {
                            Return ("INT3473")
                        }
                        ElseIf (_T_1 == 0x06)
                        {
                            Return ("INT3475")
                        }
                        ElseIf (_T_1 == 0x07)
                        {
                            Return ("INT3478")
                        }
                        ElseIf (_T_1 == 0x08)
                        {
                            Return ("INT3479")
                        }
                        ElseIf (_T_1 == 0x09)
                        {
                            Return ("INT347A")
                        }
                        ElseIf (_T_1 == 0x0A)
                        {
                            Return ("INT347B")
                        }
                        ElseIf (_T_1 == 0x0B)
                        {
                            Return ("OVTI2742")
                        }
                        ElseIf (_T_1 == 0x0C)
                        {
                            Return ("OVTI9234")
                        }
                        ElseIf (_T_1 == 0x0D)
                        {
                            Return ("OVTI8856")
                        }
                        ElseIf (_T_1 == 0x0E)
                        {
                            Return ("OVTIF860")
                        }
                        Else
                        {
                            Return (GRID (Arg0))
                        }

                        Break
                    }
                }
                Else
                {
                    Return ("INT3471")
                }
            }

#1973 | daniel_k | ⇗ @diderius6, it isn't that easy, unfortunately. That's enough for today. Good night.

#1974

diderius6

⇗ @daniel_k
I just take a look at my last mod for the Gigabyte board.
In the DSDT table,
I only isolate via OSYS
CreateQWordField
ConcatenateResTemplate (may be no need for isolate)
The same was true for all the other boards for XP SP3,
where I modded DSDT table,
CopyObject (may be no need for to isolate) has to be isolated too, when it appears
Dietmar
PS: This was mod for unknown words from Acpi2.0.
But other errors in DSDT I hacked with my acpi.sys from december 2018.
This one works everywhere, only not for Ryzen boards. This was a really hard job.
EDIT: I forget to tell, that at critical places in DSDT I replace
Switch (ToInteger (Arg0)) => Switch (Arg0)
After this mod of the DSDT table on the Giga board H110, I can use the normal acpi.sys from XP SP3 (without any mod).
See post 138, 139.

#1975

daniel_k

⇗ @diderius6, please try this ACPI.SYS LH Beta 5048.
It was crashing with error 0x3, c0140008.
It boots here just fine (XP and Server 2003), however there is a conflict in PCI bridge, which causes my GPU not being detected, also Intel XHCI also doesn't work, code 10.
Don't know if it is because of my modded DSDT.
Please try it on your H110 with original DSDT.

#1976 | infuscomus | ⇗ @diderius6 ⇗ @daniel_k ⇗ @Mov AX, 0xDEAD what are we doing with acpi.sys? don't we already have a patched acpi.sys from longhorn 5048 that works?

#1977

Mov AX, 0xDEAD

> Zitat von ⇗ infuscomus im Beitrag ¶ #1976

> @diderius6 @daniel_k @Mov AX, 0xDEAD
> what are we doing with acpi.sys? don't we already have a patched acpi.sys from longhorn 5048 that works?

I told how to add ACPI 2.0 opcodes to classic winxp's acpi.sys.
5048 still doesnt support QWordConst opcode, see ¶ Windows XP SP3 32bit and modern PC parts (21) , this opcode used in _ps0 of XHCI

#1978

diderius6

⇗ @daniel_k
I test your acpi.sys 5048 mod.
The gigabyte h110m-s2h board with original BIOS F25 starts with ACPI support.
But there is no graphikcard and on one PCI-to-PCI bridge (yellow exclamation mark) told,
not enough resources. When you look at the IRQ,
they go only up to 19.
The Intel USB does not work (code 10).
And the tool asl.exe copies DSDT to HKLM\CurrentControlSet\services\acpi\parameters
but does not work any longer with this acpi.sys (also no BSOD)
Dietmar

#1979

diderius6

daniel_k
Against BSOD A5(0x03, xxx, C0140008, yyy) in acpi.sys 32 bit 5048 from Longhorn
is easiest hack

    BF080014C0B8  =>  BF00000000B8

Dietmar
PS: But this does not help on the Giga board H110.
DEV_1901 is the PCIe controller (standard PCI-to-PCI bridge with yellow mark)
and because of this no Graphikcard.

#1980 | kukonosau | Do you check acpi for Windows XP x86 or x64 Edition?

## Page 133

#1981 | kukonosau | Thanks for acpi for x86! But what is motherboard resources in device manager? This is normally?
#1982 | diderius6 | ⇗ @kukonosau I have no good tools for 64 bit. So, idea is the same, but just try and error :)) Dietmar
#1983 | kukonosau | But not BSOD A5. Device error. I forgot. Long text in screen. acpi.sys is corrupted.

#1984

diderius6

⇗ @daniel_k
May be, the not working PCIe driver
is, because pci.sys from 5048 has an unfullfilled dependency
to ntoskrnl.exe (it is compatible to winserver 2003 but not XP SP3)
KeIpiGenericCall
Dietmar
EDIT: Exact the same error is with modded acpi.sys 5048 for
XP 64 bit. The device DEV_1901 (PCIe) cant start, because of not enough resources.
So, with unmodded DSDT and modded acpi.sys from 5048, also no graphik card in XP 64bit
on the Gigabyte h110m-s2h board.
⇗ https://docs.microsoft.com/en-us/windows...eipigenericcall
EDIT: The not working device DEV_1901 (PCIe) belongs to acpi.sys 5048,
because in "MPS" mode without any acpi, this device and the graphicard work.

#1985 | infuscomus | ⇗ @diderius6 I recall ⇗ @XPLives saying he encountered this problem aswell during his testing. any possibility for a fix?

#1986

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #1978

> The gigabyte h110m-s2h board with original BIOS F25 starts with ACPI support.
> But there is no graphikcard and on one PCI-to-PCI bridge (yellow exclamation mark) told,
> not enough resources. When you look at the IRQ, they go only up to 19.

check hidden virtual devices "Motherboard resource" in Device Manager
one of these may conflict with pci-vga, in my case it was ACPI\PNP0C02\IOTRAPS and conflict with IO Ports 0xFF00-0xFFFF
so i set resources to zero in dsdt for this acpi device

#1987 | daniel_k | ⇗ @Mov AX, 0xDEAD, interesting that, with XP's ACPI.SYS there is no conflict. ⇗ @diderius6, managed to add QWordConst opcode. It's attached, if you wanna try it. Now USB3 works, unfortunately there still conflict in PCI bridge. What a shame, with this patch 5048 supports ALL opcodes used on my Z370's DSDT.
#1988 | daniel_k | ⇗ @diderius6, can you try the modded ACPI.SYS above on your Ryzen?

#1989

diderius6

⇗ @daniel_k
Yesssaaa, nice job,
on the Giga H110 board now all USB works with unmodded DSDT:))!
Only PCIe DEV_1901 still not works
Dietmar
PS: Now I test your acpi.sys 5048 on Ryzen.

#1990

diderius6

For the not working PCIe (graphikcard)
E/A-Bereich FF00 - FFFE wird verwendet von:
\Driver\VgaSave
PCI Standard-PCI-zu-PCI-Brücke
ACPI\PNP0C02\IOTRAPS
Dietmar

#1991

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1987

> managed to add QWordConst opcode. It's attached, if you wanna try it.

MS did _parseintobj right, but forget add 0x0e to opcodetable, very strange

#1992

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #1990

> For the not working PCIe (graphikcard)
> E/A-Bereich FF00 - FFFE wird verwendet von:
> \Driver\VgaSave
> PCI Standard-PCI-zu-PCI-Brücke
> ACPI\PNP0C02\IOTRAPS

Welcome to Club )
⇗ https://github.com/MovAX0xDEAD/ACPI-Patc...AT/iotr_fix.dif

#1993

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1987

> @Mov AX, 0xDEAD, interesting that, with XP's ACPI.SYS there is no conflict

i dont know how you run original acpi.sys with original _crs of IOTR Device (on intel mb this acpi virtual device generate conflict)
original _crs has ConcatenateResTemplate opcode, so it was commented/patched some way

#1994

diderius6

⇗ @Mov AX, 0xDEAD
I tried to disable ACPI\PNP0C02\IOTRAPS
in registry of XP
and also in devicemanager (motherboard resources)
but without success.
May be, that can be done without modding DSDT
Dietmar

#1995

daniel_k

⇗ @Mov AX, 0xDEAD, that's what I don't get.

            Device (IOTR)
            {
                Name (_HID, EisaId ("PNP0C02") /* PNP Motherboard Resources */)  // _HID: Hardware ID
                Name (_UID, "IoTraps")  // _UID: Unique ID
                Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource Settings
                {
                    Local0 = ResourceTemplate ()
                        {
                        }
                    Name (BUF0, ResourceTemplate ()
                    {
                        IO (Decode16,
                            0x0000,             // Range Minimum
                            0x0000,             // Range Maximum
                            0x01,               // Alignment
                            0xFF,               // Length
                            _Y21)
                    })
                    Name (BUF1, ResourceTemplate ()
                    {
                        IO (Decode16,
                            0x0000,             // Range Minimum
                            0x0000,             // Range Maximum
                            0x01,               // Alignment
                            0xFF,               // Length
                            _Y22)
                    })
                    Name (BUF2, ResourceTemplate ()
                    {
                        IO (Decode16,
                            0x0000,             // Range Minimum
                            0x0000,             // Range Maximum
                            0x01,               // Alignment
                            0xFF,               // Length
                            _Y23)
                    })
                    Name (BUF3, ResourceTemplate ()
                    {
                        IO (Decode16,
                            0x0000,             // Range Minimum
                            0x0000,             // Range Maximum
                            0x01,               // Alignment
                            0xFF,               // Length
                            _Y24)
                    })
                    CreateWordField (BUF0, \_SB.PCI0.IOTR._CRS._Y21._MIN, AMI0)  // _MIN: Minimum Base Address
                    CreateWordField (BUF0, \_SB.PCI0.IOTR._CRS._Y21._MAX, AMA0)  // _MAX: Maximum Base Address
                    CreateWordField (BUF1, \_SB.PCI0.IOTR._CRS._Y22._MIN, AMI1)  // _MIN: Minimum Base Address
                    CreateWordField (BUF1, \_SB.PCI0.IOTR._CRS._Y22._MAX, AMA1)  // _MAX: Maximum Base Address
                    CreateWordField (BUF2, \_SB.PCI0.IOTR._CRS._Y23._MIN, AMI2)  // _MIN: Minimum Base Address
                    CreateWordField (BUF2, \_SB.PCI0.IOTR._CRS._Y23._MAX, AMA2)  // _MAX: Maximum Base Address
                    CreateWordField (BUF3, \_SB.PCI0.IOTR._CRS._Y24._MIN, AMI3)  // _MIN: Minimum Base Address
                    CreateWordField (BUF3, \_SB.PCI0.IOTR._CRS._Y24._MAX, AMA3)  // _MAX: Maximum Base Address
                    AMI0 = ITA0 /* \ITA0 */
                    AMA0 = ITA0 /* \ITA0 */
                    AMI1 = ITA1 /* \ITA1 */
                    AMA1 = ITA1 /* \ITA1 */
                    AMI2 = ITA2 /* \ITA2 */
                    AMA2 = ITA2 /* \ITA2 */
                    AMI3 = ITA3 /* \ITA3 */
                    AMA3 = ITA3 /* \ITA3 */
                    If (ITS0 == One)
                    {
                        ConcatenateResTemplate (Local0, BUF0, Local1)
                        Local0 = Local1
                    }

                    If (ITS1 == One)
                    {
                        ConcatenateResTemplate (Local0, BUF1, Local1)
                        Local0 = Local1
                    }

                    If (ITS2 == One)
                    {
                        ConcatenateResTemplate (Local0, BUF2, Local1)
                        Local0 = Local1
                    }

                    If (ITS3 == One)
                    {
                        ConcatenateResTemplate (Local0, BUF3, Local1)
                        Local0 = Local1
                    }

                    Return (Local0)
                }
            }

## Page 134

#1996

daniel_k

⇗ @Mov AX, 0xDEAD, please take a look at my patched DSDT.
Search for 07D6 for my patches.
daniel_k has attached files to this post

- ⇗ Z370AOG3_F13.rar

#1997

daniel_k

⇗ @Mov AX, 0xDEAD, is there anything special to be done when replacing an API Function call with a Local Function call?
I'm trying to patch Vista beta 4008, which has one missing import, whose code is really simple.
Original:

    3A122: 894610                         mov          [esi][010],eax
    3A125: 0FB6C0                         movzx        eax,al
    3A128: 50                             push         eax
    3A129: E8920FFFFF                     call         HalConvertIdtToIrql
    3A12E: 83661C00                       and          d,[esi][01C],0
    3A132: 884614                         mov          [esi][014],al

My patch:

    3A122: 894610                         mov          [esi][010],eax
    3A125: 0FB6C0                         movzx        eax,al
    3A128: 50                             push         eax
    3A129: E8E2610000                     call        40310
    3A12E: 83661C00                       and          d,[esi][01C],0
    3A132: 884614                         mov          [esi][014],al

    40310: 8B442404                       mov          eax,[esp][4]
    40314: C1E804                         shr          eax,4
    40317: 83C004                         add          eax,4
    4031A: C20400                         retn         4

#1998

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #1994

> I tried to disable ACPI\PNP0C02\IOTRAPS
> in registry of XP
> and also in devicemanager (motherboard resources)
> but without success.
> May be, that can be done without modding DSDT

before patching dsdt i too tried to disable in devmanager with no sucess
seems no way to disable acpi device, windows think that these devices are not PnP, if this device have _DIS method it maybe possible (imho)

#1999

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1995

> @Mov AX, 0xDEAD, that's what I don't get.

>            Device (IOTR)
>                 Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource Settings
>                     If (ITS0 == One)
>                     {
>                         ConcatenateResTemplate (Local0, BUF0, Local1)
>                         Local0 = Local1
>                     }

how you runed this with original acpi.sys ?

#2000 | daniel_k | ⇗ @Mov AX, 0xDEAD, yes, works just fine here with XP SP3 and Server 2003 SP2.
#2001 | Mov AX, 0xDEAD | dancing with IOTRAPS: win7 x64, IO range = Only One adress 0xFF00 winxp 32 orig acpi.sys+acpi2.0 opcodes, IO range = Only One adress 0xFF00: in both OS device manager show different range 0-254:
#2002 | diderius6 | ⇗ @daniel_k Your new acpi.sys 5048 mod does not work with Ryzen BSOD 7E (0xC0000005,..) Dietmar PS: Now I try to implement jmp EB from Infuscomus there also.

#2003

daniel_k

⇗ @Mov AX, 0xDEAD, that's with and Z370.
Even with my older H270, there was no problem at all.
Just remembered something.
I've got this issue when I've modded the Z370 BIOS (ME firmware) and run the board with an i7-7700. Did this while waiting for an i7-8770K.
When the 8770K arrived, flashed original BIOS with usual mods, which you can see in the table above and resource conflict was gone.

#2004 | daniel_k | ⇗ @Mov AX, 0xDEAD, what does this mean (on XP)? On Win7 is exactly the same as yours above.

#2005

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #2004

> @Mov AX, 0xDEAD, what does this mean (on XP)?

this mean device has no resources (_crs failed), but no way to know how it was failed
as you can see in aml code, _crs return ResourceTemplate filled by "start" and "end" ranges

#2006 | daniel_k | ⇗ @Mov AX, 0xDEAD Somehow I was Lucky with that one. Maybe it's the Gigabyte implementation? Can you shine some light here, please? ¶ Windows XP SP3 32bit and modern PC parts (134)

#2007

diderius6

Here comes the nice acpi.sys from ⇗ @daniel_k
which now also works on Ryzen thanks to ⇗ @infuscomus
just tested:)) on 3700x
Dietmar
File acpi.sys for Ryzen see post 2012, works also, I tested.
⇗

#2008

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #1997

> I'm trying to patch Vista beta 4008, which has one missing import, whose code is really simple.
> Original:

>     3A129: E8920FFFFF                     call         HalConvertIdtToIrql

> My patch:

>     3A129: E8E2610000                     call        40310

>     40310: 8B442404                       mov          eax,[esp][4]
>     40314: C1E804                         shr          eax,4
>     40317: 83C004                         add          eax,4
>     4031A: C20400                         retn         4

1) "e8 xx" is relative adressing, its OK. At adress HalConvertIdtToIrql is some like "jmp dword [_imp_HalConvertIdtToIrql]" ?
2) retn 4 - depends on original HalConvertIdtToIrql, if it pop stack back, then this OK

#2009

Mov AX, 0xDEAD

trying to decode what _crs return:
47 - Small resource item , 4=io port type, 7 - lengh
01 - 16-bit adressing
00 FF - Min posible adress
00 FF - Max posible adress
01 - Aligment is 1 byte
FF - Numbers of adresses
79 - End Tag
41 - Checksum
Aida browser was wrong, device claimed 255 adresses

#2010 | daniel_k | ⇗ @Mov AX, 0xDEAD 1) Yes 2) Sorry, don't understand. You mean pop stack back in the original function itself or in the code after the call?

## Page 135

#2011

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #2010

> @Mov AX, 0xDEAD
> 2) Sorry, don't understand. You mean pop stack back in the original function itself or in the code after the call?

in original HalConvertIdtToIrql, if it return with "ret 4" it's ms cdecl convection
if "pop/add esp" somewhere after 3A129 it's stdcall

#2012

daniel_k

⇗ @diderius6
That's great!
Are there any functional changes between this and XP 5512? IRQ ranges?
Please delete your above and use the file I've attached.
There were some unnecessary changes I made.
I've already applied ⇗ @infuscomus fix.

#2013 | diderius6 | ⇗ @daniel_k "Are there any functional changes between this and XP 5512? IRQ ranges" Yes, here Irqs went up to 55 (acpi.sys XP 5512 only up to 19) Dietmar
#2014 | daniel_k | ⇗ @Mov AX, 0xDEAD, thanks, unfortunately it didn't work. I've tried another approach, 4008 seems just incompatible with XP.

#2015

daniel_k

⇗ @Andalu
Here is the fix for USB3 on the Q87.
Rename \WINDOWS\Driver Cache\i386\sp3.cab to something else.
Delete \WINDOWS\system32\DllCache\acpi.sys
Copy and overwrite ACPI.SYS in \WINDOWS\system32\Drivers
Restart and install the USB driver, if not already installed.

#2016 | AddFun | Tried the new ACPI from post #2012 on my WinXP SP3 partition (that I got to the post GUI install stage but never to desktop) but all I got was the usual 7B BSOD 0x0000007B (0xBACC3524, 0x0000034, 0x00000000, 0x00000000) Ryzen 1600X on a Gigabyte AX370 Gaming 5

#2017

AddFun

Alright, nlited a NEW disk with same post #2012 ACPI along with proper AHCI drivers. Got through the entire install only to get dropped onto a blank blue wallpaper screen (Not BSOD). Greeted with this ACPI 7E BSOD upon reboot (safe mode or not, same BSOD). Technically, the WinXP install is complete.

#2018

Andalu

⇗ @daniel_k
After renaming sp3.cab, overwriting acpi.sys and restarting, the microsoft management console process doesn't find any driver for the yellows USB2.0 Hub (Vid_05e3&Pid_0610) and USB3.1 Hub (Vid_05e3&Pid_0612); it continues infinitely to search with no success (no difference on automated, manual and forced driver installation); if i click on 'cancel' or 'back' the process hangs and it needs to be killed manually.
Thanks again for your patience.

#2019 | daniel_k | ⇗ @Andalu, forgot that you need to rename back SP2.CAB. Do those hubs were detected upon reboot after replacing ACPI.SYS? If so, the driver for them is part of the AMDXHCI package.
#2020 | daniel_k | ⇗ @Mov AX, 0xDEAD, wouldn't it be possible to add a string check to Store function in ACPI.SYS so that during processing it would ignore ITA0 and don't do anything? This would solve the PCI bridge conflict.

#2021

skullteria

> Zitat von ⇗ daniel_k im Beitrag ¶ #2012

> @diderius6
> That's great!
> Are there any functional changes between this and XP 5512? IRQ ranges?
> Please delete your above and use the file I've attached.
> There were some unnecessary changes I made.
> I've already applied @infuscomus fix.

Hey ⇗ @daniel_k, it is based on my modded driver? Can you made it to x64?

#2022

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #2020

> @Mov AX, 0xDEAD, wouldn't it be possible to add a string check to Store function in ACPI.SYS so that during processing it would ignore ITA0 and don't do anything?
> This would solve the PCI bridge conflict.

if someone want to patch acpi.sys to zero resources of iotr welcome )
i prefer to investigate pci.sys or some else to find source of conflict

#2023 | daniel_k | ⇗ @skullteria, I did it on my own. Yes, currently porting the changes to x64. ⇗ @Mov AX, 0xDEAD, seeing what most XP compatibility patches are hacks (even official ones), don't see anything wrong with that. Are there any utilities to edit x64 relocation table or we need to change it manually? Something like Relocation Section Editor which I use for 32-bit?
#2024 | Mov AX, 0xDEAD | .del

#2025

skullteria

> Zitat von ⇗ daniel_k im Beitrag ¶ #2023

> @skullteria, I did it on my own. Yes, currently porting the changes to x64.
> @Mov AX, 0xDEAD, seeing what most XP compatibility patches are hacks (even official ones), don't see anything wrong with that.
> Are there any utilities to edit x64 relocation table or we need to change it manually? Something like Relocation Section Editor which I use for 32-bit?

Great! My changes on acpi 5048 are to solve C1400008 BSOD. I feel happy because you solved problem with USB 3.0 too. Windows XP is almost usable on modern computers

## Page 136

#2026

daniel_k

⇗ @diderius6, please try this x64 version of ACPI.SYS 5048.
Figured out the relocation table, luckily there was an empty slot I could use.
Implemented Skylake+ patch, QwordConst and applied Ryzen patch.
By the way, does the previous 32-bit ACPI.SYS 5048 works on your B350?
Maybe it behaves the same as ⇗ @AddFun report?

#2027

diderius6

⇗ @daniel_k
The 32 bit acpi.sys works also on B350 boards, on x370 boards (AMD) and on x570 boards.
At ⇗ https://hwbot.org they tested it also, just works everywhere.
The different BSODs during install of XP 32 bit happens because of DSDT tables,
which are not correct. In this case it only helps, to install on another compi,
and after installation of XP connect to first one.
The other possibilty in BSODs is, that the acpi.sys driver is changed back to
the original acpi.sys after first reboot. In this case, just copy new acpi.sys back to folder
windows\system32\drivers helps.
And I saw a lot of BSODs, because of not correct integrated AHCI drivers.
The STORAHCI from ⇗ @skullteria works on every board, AMD, Intel, old new,
until now I do not have a board, where it does not work. But even there you have to copy
storport.sys by hand and may be after reboot again into windows\system32\drivers
Dietmar
PS: Now I test your new acpi.sys 64 bit.

#2028 | daniel_k | ⇗ @diderius6, reading throughly AddFun now I see the crash occurs after install, so ACPI.SYS is, for sure, restored to original, non-modded version. ⇗ @AddFun, you need to repack SP3.CAB. Unpack SP3.CAB, replace ACPI.SYS and repack it.
#2029 | Andalu | ⇗ @daniel_k yes, the two hubs were created after replacing ACPI.SYS and restart but i can't use the AMDXHCI package because the mmc process hangs again like before, also by renaming back the .cab file into sp2 or sp3

#2030

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #2023

> Are there any utilities to edit x64 relocation table or we need to change it manually? Something like Relocation Section Editor which I use for 32-bit?

is it ⇗ https://github.com/mohic/Relocation-Section-Editor ? do you have download link to release ?

#2031 | daniel_k | ⇗ @Andalu, what a shame. Can you access the XP's drivers folder from another OS? If so, delete amdxhc.sys and boot XP, device won't start because of missing driver and you may be able to test the Renesas driver, which is my suggestion. Maybe the AMD driver doesn't work properly. Unfortunately I don't have any pre-Skylake board to test it.
#2032 | daniel_k | ⇗ @Mov AX, 0xDEAD Can't remember where I got it from, just says its author is gta126 in About box. It's coded in some version of .NET Framework. Works just fine.

#2033

daniel_k

⇗ @Mov AX, 0xDEAD
Interesting that the ACPI.SYS 5048 does an additional check in CreateByteField which leads to a BSOD.
Can you do some analysis, please?
VISTA 5048

    15ED4: BF080014C0                     mov          edi,0C0140008
    15ED9: B8090014C0                     mov          eax,0C0140009
    15EDE: 3B55F8                         cmp          edx,[ebp][-8]
    15EE1: 0F8DE3000000                   jge          000015FCA
    15EE7: 8B5D0C                         mov          ebx,[ebp][00C]
    15EEA: 0FBE141A                       movsx        edx,b,[edx][ebx]
    15EEE: 83FA49                         cmp          edx,049 ;'I'
    15EF1: 7F64                           jg           000015F57
    15EF3: 745C                           jz           000015F51
    15EF5: 83EA41                         sub          edx,041 ;'A'
    15EF8: 7450                           jz           000015F4A
    15EFA: 4A                             dec          edx
    15EFB: 7447                           jz           000015F44
    15EFD: 4A                             dec          edx
    15EFE: 7435                           jz           000015F35
    15F00: 4A                             dec          edx
    15F01: 741F                           jz           000015F22
    15F03: 4A                             dec          edx
    15F04: 4A                             dec          edx
    15F05: 7415                           jz           000015F1C
    15F07: 4A                             dec          edx
    15F08: 4A                             dec          edx
    15F09: 7567                           jnz          000015F72
    15F0B: 6683390F                       cmp          w,[ecx],00F    --> CHECK CAUSES BSOD
    15F0F: 0F84A3000000                   jz           000015FB8
    15F15: 89FF                           mov          esi,edi
    15F17: E99C000000                     jmp          000015FB8
    15F1C: 66833905                       cmp          w,[ecx],5
    15F20: EBED                           jmps         000015F0F

XP 5512:

    13D1F: BF080014C0                     mov          edi,0C0140008 ;'
    13D24: B8090014C0                     mov          eax,0C0140009 ;'
    13D29: 3B5DFC                         cmp          ebx,[ebp][-4]
    13D2C: 0F8DB6000000                   jge          000013DE8
    13D32: 8B550C                         mov          edx,[ebp][00C]
    13D35: 0FBE1413                       movsx        edx,b,[ebx][edx]
    13D39: 83FA49                         cmp          edx,049 ;
    13D3C: 7F51                           jg           000013D8F
    13D3E: 7449                           jz           000013D89
    13D40: 83EA41                         sub          edx,041 ;
    13D43: 743D                           jz           000013D82
    13D45: 4A                             dec          edx
    13D46: 7434                           jz           000013D7C
    13D48: 4A                             dec          edx
    13D49: 7422                           jz           000013D6D
    13D4B: 4A                             dec          edx
    13D4C: 740A                           jz           000013D58
    13D4E: 4A                             dec          edx
    13D4F: 4A                             dec          edx
    13D50: 7553                           jnz          000013DA5
    13D52: 66833905                       cmp          w,[ecx],5
    13D56: EB6F                           jmps         000013DC7

#2034

diderius6

⇗ @daniel_k
The new acpi.sys 5048 for 64 bit gives on a working XP 64 installation on the Giga H110 board
with original DSDT and Bios F25
BSOD A5 (0x03, xxx, 0xC0140008, yyy)
Dietmar
PS: The same BSOD happens on asrock fatal1ty z370 gaming k6.

#2035

AddFun

I already repacked my DRIVER.CAB with that last nlite build. Also, dropped in your file as ACPI.SY_ in the I386 folder. That resulted in what I posted above. There is nothing hooked up to the PC other than RAM/CPU/120GB-SATA drive internally and a PS/2 keyboard externally.
I'm looking at the file structure on the WinXP drive from another PC right now. Looks like XP was installed fully. I tried flashing the AX370 mobo to several different BIOSes (much newer F40, F41, etc) same issue.
Although, the BSOD I'm getting with your ACPI actually lists ACPI.sys, while prior BSODs with other ACPI/AHCI files were puking up totally different 7E, 7B BSODs and not actually referencing ACPI.sys.
Here is one major thing I noticed when using your ACPI.sys from post #2012 ⇗ @daniel_k, there is NO usual error while copying ACPI.sys in "TXT" mode part of the installation, something even latest versions diderius6 provided would cause, even using his custom ISO (thx bud) I would get that error (and couldn't get into GUI part of the install with the latest version on that ISO).

#2036 | daniel_k | ⇗ @diderius6 Please rename and try these files. Pay attention to the number which works, hopefully one should work.
#2037 | daniel_k | ⇗ @AddFun, what I mean is: Did you replace ACPI.SYS inside SP3.CAB? This is a must, otherwise SFC (system file checker) will replace this file with the original, untouched version during last phase of Setup.

#2038

diderius6

⇗ @AddFun
Install XP on another compi,
can be very old one,
integrate extra AHCI driver for your new compi before
and then connect to your new compi.
I am sure, this time it will work,
BSOD is because of faulty DSDT table on new compi
Dietmar

#2039

diderius6

⇗ @daniel_k
acpi_test1.sys acpi_test2.sys acpi_test3.sys fail on
asrock fatal1ty z370 gaming k6 with the same BSOD as before A5 (0x03, xxx, 0xC0140008, yyy).
But acpi_test4.sys works on
asrock fatal1ty z370 gaming k6 :))!
But the error in PCIe device because of IOTR remains.
Now I am testing on the Giga H110 board,
nice work,
Dietmar

#2040 | daniel_k | ⇗ @diderius6, please try all files on H110 too.

## Page 137

#2041

skullteria

> Zitat von ⇗ diderius6 im Beitrag ¶ #2034

> @daniel_k
> The new acpi.sys 5048 for 64 bit gives on a working XP 64 installation on the Giga H110 board
> with original DSDT and Bios F25
> BSOD A5 (0x03, xxx, 0xC0140008, yyy)
> Dietmar
> PS: The same BSOD happens on asrock fatal1ty z370 gaming k6.

0xC0140008 occours on CreateField function. I already fixed on my ACPI version, later i patch daniel_k version tobe compatible too

#2042

diderius6

⇗ @daniel_k
acpi_test2.sys acpi_test3.sys fail on the Giga H110 board
with the same BSOD as before A5 (0x03, xxx, 0xC0140008, yyy).
acpi_test1.sys fails on the Giga H110 board with BSOD 0x7B.
Again acpi_test4.sys works on Giga H110 board.
But the error in PCIe device because of IOTR remains.
Dietmar

#2043 | daniel_k | ⇗ @diderius6, please try it on the Ryzen board. By the way, for now, the IOTR issue can only be solved with DSDT patch. ⇗ @skullteria, thanks, but we already have a working version.
#2044 | Andalu | ⇗ @daniel_k i have dual xp boot so no problem to access to another partition. Unfortunately amdxhc.sys and the Renesas package are missing because the driver installation has never worked (error code 10)
#2045 | diderius6 | ⇗ @daniel_k The modded acpi.sys 64 bit from ⇗ @skullteria does not show IOTR error on the Asrock fatal1ty z370 gaming k6 board Dietmar PS: The very last acpi.sys 64 bit from ⇗ @skullteria I do not have.
#2046 | kukonosau | Acpi_test4.sys is doesn't work on motherboard from Ryzen. My motherboard is ASUS AM4 B350 PRIME B350M-K.

#2047

skullteria

> Zitat von ⇗ diderius6 im Beitrag ¶ #2045

> @daniel_k
> The modded acpi.sys 64 bit from @skullteria
> does not show IOTR error on the Asrock fatal1ty z370 gaming k6 board
> Dietmar
> PS: The very last acpi.sys 64 bit from @skullteria I do not have.

Well, my plan is integrate my changes to solve c14000008 BSOD on daniel_k version.

#2048

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #2033

> @Mov AX, 0xDEAD
> Interesting that the ACPI.SYS 5048 does an additional check in CreateByteField which leads to a BSOD.
> VISTA 5048

>     15ED4: BF080014C0                     mov          edi,0C0140008
>     15ED9: B8090014C0                     mov          eax,0C0140009

This is _ValidateArgTypes, not CreateByteField. I dont see this bytes at 15ED4 in 5048

    15F07: 4A                             dec          edx
    15F08: 4A                             dec          edx
    15F09: 7567                           jnz          000015F72
    15F0B: 6683390F                       cmp          w,[ecx],00F

at ip=15F0B EDX was decremented to 41+1+1+1+2+2=48h="H"
so _ValidateArgTypes was called with 2nd arg = pointer to string with "H" char inside
at winxp_5512 exist C, I, O, A, B, D, .. but not "H"
at vosta_5048 i see two calls with H "LoadTable" & "Unload" opcode, but we dont see this in dsdt, do double check about place of BSOD

#2049

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #2045

> does not show IOTR error on the Asrock fatal1ty z370 gaming k6 board

))
IOTR virtual device exist only on Intel (99% of dsdt created by platform maker)

#2050 | diderius6 | ⇗ @Mov AX, 0xDEAD Asrock fatal1ty z370 gaming k6 board is Intel Dietmar

#2051

diderius6

⇗ @daniel_k
On AMD asrock fatal1ty ab350 gaming k4 with Ryzen 3700x cpu
we get a new BSOD with 64 bit acpi_test4.sys, which is not direct correlated to acpi.sys.
The driver is not listened here, where the BSOD happens
Dietmar
PS: Now I test on other Ryzen board x570.
⇗

#2052 | kukonosau | I have also error!!!

#2053

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #2050

> @Mov AX, 0xDEAD
> Asrock fatal1ty z370 gaming k6 board

Oh, sorry
1) can you check IO resource usage in devmanager ?
2) do call _SB_.PCI0.IOTR._CRS in aida acpi browser ?

#2054

diderius6

⇗ @daniel_k
On the asus prime x570-pro with 64 bit XP and Ryzen 1700
it hangs in an endless loop during start, also in save mode (F8).
This time I think, it is not related to acpi_test4.sys
but to another device on the board.
I have only this XP 64 bit install from the EVGA z390 dark board.
I make a new slip stream CD via nlite for this board
and then I report
Dietmar

#2055

diderius6

⇗ @daniel_k
I cant install XP 64 bit on Ryzen board with acpi_test4.sys
see BSOD on Photo
Dietmar
PS: BSOD happens early on txt setup, I cant get the window with F8.
⇗

## Page 138

#2056 | daniel_k | ⇗ @diderius6, please try these 2 test files. Where is the modded x64 ACPI.SYS from ⇗ @skullteria which fixes IOTR? Was it 5048 or 5512? So, we've got it all after all. We just need to find which patch is resposible for the IOTR fix and apply it on the 32-bit version.
#2057 | diderius6 | ⇗ @daniel_k ⇗ @skullteria makes 5048 acpi.sys 64 Bit. It works on Intel boards with full Acpi support but not on Ryzen Dietmar
#2058 | daniel_k | ⇗ @diderius6, please upload the one you've tested and fixes IOTR.
#2059 | daniel_k | ⇗ @Mov AX, 0xDEAD This is the original untouched ACPI.SYS 5048.

#2060

diderius6

⇗ @daniel_k
On Ryzen new acpi_test1.sys
gives same BSOD 0x7E C0000005
and acpi_test2.sys endless running but
not starting XP 64 bit,
I think it is the same BSOD
Dietmar

#2061 | daniel_k | ⇗ @diderius6, one last try. x64 behaves differently than x86. The patch location is certainly correct the same, but I'm not sure if it can be done. 5 more test files for you. PS: Still waiting for the patched ACPI.SYS which fixes IOTR.

#2062

skullteria

> Zitat von ⇗ daniel_k im Beitrag ¶ #2056

> @diderius6, please try these 2 test files.
> Where is the modded x64 ACPI.SYS from @skullteria which fixes IOTR? Was it 5048 or 5512?
> So, we've got it all after all.
> We just need to find which patch is resposible for the IOTR fix and apply it on the 32-bit version.

My version only fix C1400008 BSOD, later i upload

#2063

diderius6

⇗ @daniel_k
This is the acpi.sys 5048 from ⇗ @skullteria for 64 bit from May 2019
which works on all Intel boards,
with graphikcard also
Dietmar
diderius6 has attached files to this post

- ⇗ acpi.rar

#2064

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #2059

> @Mov AX, 0xDEAD
> This is the original untouched ACPI.SYS 5048.

I've checked adresses, you using "strange" disasm, it ignores Origin adress and virtual adresses of sections (wtf ?)
Now I realized that first column is not adress, it is offset in file

#2065 | diderius6 | ⇗ @daniel_k All 5 acpi.sys test files 64 bit show the same BSOD 0x7E as before on the Ryzen x570 board. This board shows very good real BSODs Dietmar

#2066

diderius6

⇗ @Mov AX, 0xDEAD
I make a mistake:
Only on the EVGA z390 dark board with XP friendly Bios from beginning
the PCIe works and so the graphikcard in XP 64 bit.
I make a check at the Intel asrock fatal1ty z370 gaming k6 board:
PCIe error, no graphikcard in XP 64 bit as you also can see here on post 948.
But with my modded acpi.sys from December 2018
I have without Bios mod for IOTR full graphik
on Intel asrock fatal1ty z370 gaming k6 board
and on Intel Asus Apex X board for XP SP3 32 bit
Dietmar
PS: My mod in acpi.sys was in XP SP3 5112 version.

#2067

daniel_k

⇗ @Mov AX, 0xDEAD
Sorry, was running 2 instances of Hiew in Edit mode when copied the disassembly. Really sorry!
⇗ @diderius6
It's interesting to see how x64 and x86 behaves differently! Same code position, different results.
That's what I've been thinking. Test4 was a quick hack. Just compared with skullteria's and it's exactly the same, no way it would make any difference.
By the way, can you attach your ACPI 5512 mod that fixes IOTR?

#2068

diderius6

⇗ @daniel_k
Here it is,
Dietmar
PS: Now very late here, I go to bed.
diderius6 has attached files to this post

- ⇗ acpi3.rar

#2069 | daniel_k | ⇗ @diderius6 Applied your patches to my 5048, but it probably won't work for you as it didn't here.

#2070

AddFun

⇗ @diderius6 Installed the nlited disk on a AM3 based AMD PC with a Athlon II 640, closest I can get to a Ryzen-yet-not-Ryzen. WinXP installed fine and is desktop bootable. Moved the drive to the Ryzen PC and got this BSOD

> Zitat von ⇗ daniel_k im Beitrag ¶ #2069

> ⇗ @diderius6

## Page 139

#2071 | AddFun | Never mind. Got it to boot!

#2072

diderius6

⇗ @skullteria
This USB files from ⇗ @daniel_k work on all newer boards with Intel chipset and XP SP3 32 bit.
With the acpi.sys 32 bit from post 2069 it installs there without any need
of modding the DSDT table in Bios,
Dietmar
PS: First install xhc.inf and later hub30.inf when asked for new driver.
Dont forget to copy usbd.sys in windows\system32\drivers.
diderius6 has attached files to this post

- ⇗ USB3bestforIntel.rar

#2073

diderius6

⇗ @daniel_k
Your last acpi.sys (post 2069) for XP SP3 32 bit
works on all boards (AMD, Intel, old, new) that I tested.
No need to mod anything in Bios. All USB devices work.
On some Intel boards, the IOTR device claims memory
for the graphikcard (for unknown reason), so this is the last bastion for DSDT mod.
This IOTR problem (only on Intel boards) happens not with my acpi.sys from post 2068,
but for this acpi.sys you have to mod DSDT for XP unfriendly words from acpi 2.0
by hand,
Dietmar

#2074 | infuscomus | ⇗ @diderius6 can you download XP 64bit checked build and see where the problem is? so we can properly fix 64bit acpi.sys 5048 for ryzen?
#2075 | daniel_k | ⇗ @diderius6, fixed the IOTR issue with x86! Will also patch the x64 version and upload both. Then I'll explain what was the issue.

#2076

daniel_k

⇗ @diderius6, here is the x86, I consider this version the final for all Intel chipsets and Ryzen.
What was the issue?
Contrary to what you think, ConcatenateResTemplate is not supported and is ignored by XP 5512.
That's why your modded ACPI 5512 works and doesn't have the IOTR conflict issue, because it is not processed!
So what I did?
Killed the ConcatenateResTemplate from 5048, as it is supported and works, leading to the resource conflict.
Please test on your H110 and Z370 with original DSDT BIOS.
Z390 is XP friendly so test not required.
Ryzen test is also not required because the DSDT doesn't have the ConcatenateResTemplate opcode.

#2077 | daniel_k | ⇗ @diderius6, here is the x64 version, test version. I've uploaded it as 6 test files, because I'd like to know where it crashes. Please test all of them and pay attention to the number. For sure, one of them will work. Ryzen testing is not needed as I did nothing related to it.

#2078

diderius6

⇗ @daniel_k
Yessssssaaaaaaa, full ACPI support in XP SP3 on any compi without any DSDT mod!!!
Your nice acpi.sys from post 2076 works now with the IOTR device.
And to chose the Gigaboard H110 as test board was the right choice
Dietmar
⇗

#2079

Mov AX, 0xDEAD

I played little with length IO range of IOTR at H110 MB (starting adress is always 0xFF00):
0 - OK, device disapear in DevManager
1<->0xA0 - OK
0xA0-0xE0 - Not tested
0xE0-0xFF - Conflict
so hooking of BufferOp is possible, after movsd & movsb we have at EDI struct of bytes:
11 0D 0A 0A 47 01 00 00 00 00 01 FF 79 00

    pseudo-code:
    sub edi, 0xe ; back edi to start of buffer
    cmpl	[edi], 0x11 0D 0A 0A
    jnz nopatch
    cmpl	[edi+4], 0x47 01 00 00
    jnz nopatch
    cmpl	[edi+8], 0x00 00 01 FF
    jnz nopatch
    cmpw [edi+c], 0x79 00
    jnz nopatch
    patch:
    moveb [edi+b], 0x00 ; edi+b=length
    nopatch: jmp _back

im not sure about full bufer, maybe in edi will be only 0A 0A 47 01 00 00 00 00 01 FF 79 00

#2080 | dencorso | Greetz! You all do rock! Awesome collaborative work! Thanks so much. Long live XP!
#2081 | daniel_k | ⇗ @diderius6, finally! ⇗ @Mov AX, 0xDEAD, how do I find the code for a certain opcode? I'm think about replacing a non used opcode. The IOTR stuff is just for you, I'm decades behind your knowledge. ⇗ @dencorso, good to see you here!

#2082

Andalu

> Zitat von ⇗ diderius6 im Beitrag ¶ #2073

> @daniel_k
> Your last acpi.sys (post 2069) for XP SP3 32 bit
> works on all boards (AMD, Intel, old, new) that I tested.
> No need to mod anything in Bios. All USB devices work.

Old how long? In both my Haswell and Ivy boards the USB3 driver doesn't install or work.
Strangely, the usb3 driver installs properly on older Ivy board (even the usb3 ports act as usb2, so no difference) while on the newer haswell board the usb driver doesn't install anyway even the acpi.sys (acpi5048_dietmar md5: 9D1015F5DD2B9EED6CA40579E8574541) is correctly in the windows\system32\drivers after reeboting.
Someone can confirm that? I really hope not, so I can still have a dream :)
In any case, my congratulations to you all for the wonderful work.
Edit: also tried the acpi.sys from daniel_k at #2076 with same results.

#2083

diderius6

⇗ @daniel_k
Until now I tested acpi_test1.sys and acpi_test2.sys (from your 6 acpis (vers. 5048) 64 bit XP )
for Ryzen boot of XP 64 bit.
This is a really hard job, because I need to make sure,
that it is ONLY the fault of acpi.sys, when it crashes. I will continue test for the other acpis.
acpi_test1.sys gives BSOD 0x7E (0xC0000005,..)
acpi_test2.sys hangs during setup (I think, the same BSOD as acpi_test1.sys)
acpi_test3.sys gives BSOD 0x7E (0xC0000005,..)
acpi_test4.sys hangs during setup (I think, the same BSOD as acpi_test1.sys)
acpi_test5.sys hangs during setup (I think, the same BSOD as acpi_test1.sys)
acpi_test6.sys hangs during setup (I think, the same BSOD as acpi_test1.sys)
So, on a longer sight, the idea from ⇗ @infuscomus
to set up a windbg session with checked XP 64 may be the better choice.
⇗ @infuscomus :
I cant download the checked XP 64 from
⇗ https://the-eye.eu/public/MSDN/Windows%20XP/
May be you can try also and send to me this XP checked 64 bit
Dietmar

#2084

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #2081

> @Mov AX, 0xDEAD, how do I find the code for a certain opcode? I'm think about replacing a non used opcode.

FYI:
BufferOpcode start at 0x27407 (winxp_5512) and pointed from _atBuffer structure at 0x2CE10 _atBuffer

    .text:00027407                 mov     edi, edi
    .text:00027409                 push    ebp

in this block we copy bytes from dsdt to memory:

    .text:000274B5                 mov     eax, [ebp+arg_0]
    .text:000274B8                 mov     ecx, esi
    .text:000274BA                 mov     esi, [eax+3Ch]
    .text:000274BD                 mov     eax, [ebx+30h]
    .text:000274C0                 mov     edi, [eax+10h]
    .text:000274C3                 mov     eax, ecx
    .text:000274C5                 shr     ecx, 2
    .text:000274C8                 rep movsd
    .text:000274CA                 mov     ecx, eax
    .text:000274CC                 and     ecx, 3
    .text:000274CF                 rep movsb
    .text:000274D1                 mov     eax, [ebx+14h] <- copying is done at this IP and we can patch
    .text:000274D4                 mov     ecx, [ebp+arg_0]
    .text:000274D7                 mov     [ecx+3Ch], eax
    .text:000274DA                 pop     edi

also possible patching source buffer (where dsdt is loaded) before copying to final destination

#2085 | dencorso | ⇗ @Andalu: what are the VID & PID of the Haswell board's "Intel Chipset Family USB eXtended Host Controller"? Is it present in the .inf? The VID should be 8086 (aka Intel) but the PID can be any value.

## Page 140

#2086

Andalu

⇗ @dencorso
Thank you for reply ;)
The device ID for the "Intel 8 series_C220 series B xHCI HC - 8C31" (with message: "no driver installed for this device") of my CSM-Q87M-E43 board is PCI\VEN_8086&DEV_8C31&CC_0C0330 that is present in the amdxhc.inf of the AMDXHCI package.
When i try to install the driver, i got always error code 10

#2087 | diderius6 | I found WindowsServer2003.WindowsXP-KB914961-SP2-x64-DEBUG-ENU.exe Hope, that I can update XP 64 to SP2 debug version Dietmar

#2088

skullteria

> Zitat von ⇗ diderius6 im Beitrag ¶ #2087

> I found
> WindowsServer2003.WindowsXP-KB914961-SP2-x64-DEBUG-ENU.exe
> Hope, that I can update XP 64 to SP2 debug version
> Dietmar

Only Windows checked can be update to service pack checked (debug)

#2089

dencorso

⇗ @Andalu: just to keep in the same page: are you using precisely the drivers attached below? Those are the latest iteration.
dencorso has attached files to this post

- ⇗ Final_New_daniel_k_v2.rar

#2090 | Andalu | ⇗ @dencorso Yes, it's the same package i have used. I just verified that each file of both packages has the same MD5.

#2091

diderius6

⇗ @skullteria
With little help from nlite 1.4.9.3 64 bit,
I succeed to integrate
WindowsServer2003.WindowsXP-KB914961-SP2-x64-DEBUG-ENU.exe
into my normal XP 64 bit
Dietmar
PS: I also integrated your nice STORAHCI driver there. Now again fun can start:))!
⇗ https://www.askvg.com/windows-xp-sp3-set...service-pack-3/

#2092 | daniel_k | ⇗ @diderius6, those 6 test files, it was supposed to be tested on your Intel boards, not Ryzen. ⇗ @Mov AX, 0xDEAD, thanks! ⇗ @Andalu, if the MMC process hangs, I don't know what to suggest to you. Any chance of doing a clean install on a spare disk then apply the ACPI.SYS and install the driver?
#2093 | diderius6 | ⇗ @daniel_k On Intel boards it is easy for me to test Dietmar
#2094 | daniel_k | ⇗ @diderius6, please do it when you can.

#2095

diderius6

⇗ @daniel_k
Small problem is just now,
that my XP 64 installation does not survive the direct upgrade
to the debug version.
So I have to install it new.
I will make 2 installs,
one with debug XP 64
and another one with normal XP 64.
The versions are identic
Dietmar
PS: That is the debug acpi.sys from XP 64 SP2.
diderius6 has attached files to this post

- ⇗ acpiDEBUGXP64.rar

#2096

diderius6

⇗ @daniel_k
After I installed XP 64 new,
I port it from XP friendly z390 to XP unfriendly (Intel) Asrock fatal1ty z370 gaming k6.
Waaooh, your acpi_test1.sys (out of 6 acpis)
shows for the very first time the graphikcard,
no error about IOTR can be seen
and the USB is recogniced at once, just nice:))
Dietmar
PS: Now I am too tired, go to bed.

#2097 | daniel_k | ⇗ @diderius6, that's great! Please try all files tomorrow.
#2098 | diderius6 | ⇗ @daniel_k Yepp! Dietmar

#2099

diderius6

⇗ @daniel_k
I make 6 identic installations CDs for XP 64 SP2 (nondebug).
On 1. is acpi_test1.sys
On 2. is acpi_test2.sys
On 3. is acpi_test3.sys
On 4. is acpi_test4.sys
On 5. is acpi_test5.sys
On 6. is acpi_test6.sys
With this I try to install XP64 bit direct on XP unfriendly (Intel) Asrock fatal1ty z370 gaming k6 board and on the Giga H110 with original unmodded Bios F25.
Only with CD1 and CD6 this is possible:))!
CD2, CD3, CD4, CD5 show all the same BSOD A5 (0x03,..).
Between them I try again CD1 three times, because sometimes strange things can happen.
Ok, CD1 works always for XP 64 bit install on XP unfriendly compi.
The behavior of the Asrock z370 and the Giga H110 board ist to 100% identic,
Dietmar

#2100 | infuscomus | ⇗ @diderius6 I found XP 64 Debug/Checked ISO here ⇗ https://www.getmyos.com/windows-xp-professional-x64

## Page 141

#2101

skullteria

Well, i installed Windows Vista in my system and USB 3.0 with amd driver modded working fine! However, need be signed to run on x64.
⇗
And in WIndows XP SP3, working fine too! However, after install a hotfix what change kernel, i get code 10, even using acpi modded.
⇗
Now, i need test on Server 2003 and in x64
Well, on Server 2003 installed on Virtual Box, i get Code 10. Later i test on real computer

#2102

dencorso

> Zitat von ⇗ skullteria im Beitrag ¶ #2101

> However, after install a hotfix what change kernel, i get code 10, even using acpi modded.

You've just hit jackpot! That issue was baffling me and ⇗ @Andalu till now! What version were your kernel files before and after the issue showed itself? Just for the record, the latest kernel files are 5.1.2600.7649 (for ntkrnlmp, from KB4486463 of Feb 2019) and 5.1.2600.7811 for the others (including ntkrpamp, from KB4463103 of Oct 2018). Any effective USB 3.x solution must work with those, of course. You just found where does the last bug lurk!!! Congrats! :-)

#2103

skullteria

> Zitat von ⇗ dencorso im Beitrag ¶ #2102

> > Zitat von ⇗ skullteria im Beitrag ¶ #2101

> > However, after install a hotfix what change kernel, i get code 10, even using acpi modded.

> You've just hit jackpot! That issue was baffling me and @Andalu till now! What version were your kernel files before and after the issue showed itself? Just for the record, the latest kernel files are 5.1.2600.7649 (for ntkrnlmp, from KB4486463 of Feb 2019) and 5.1.2600.7811 for the others (including ntkrpamp, from KB4463103 of Oct 2018). Any effective USB 3.x solution must work with those, of course. You just found where does the last bug lurk!!! Congrats! :-)

well, i not used vanilla files in true. I used my kernel files from One-Core-API kernel update (i'm the creator of Shorthorn and one-core-api project: shorthornproject.com). I think something change on DSDT on registry after switch hal. And, i am warried with Server 2003. I need test acpi and usb on real machine. Maybe we have problem if Windows was installed and after packaged on WIM format. Maybe it not change DSDT property.
For kernel test (both Windows XP and Server 2003):
⇗ https://github.com/Skulltrail192/One-Cor...er%20Standalone

#2104

dencorso

Sure! But ist's a pointer, nonetheless, I guess.
Just for the record (and without any intention of preaching at the choir), two references someone may find useful:
⇗ http://www.geoffchappell.com/studies/win...story/index.htm
(about kernel versions) and (about E320 from NT6.*)
⇗ https://www.geoffchappell.com/studies/wi...os/fwmemmap.htm

#2105

Andalu

⇗ @daniel_k ⇗ @dencorso
Some good news from here. I restored on the second partition an XP image saved at first reboot after installation on my haswell board (thanks to daniel_k for the suggestion at #2092), acpi.sys overwritten with the new version form "acpi5048_intel_amd_final" package from my first partition (so the operating system doesn't change it on the restart) and the drivers from "USB3bestforIntel" package are correctly installed now.
But the good news ends here, because the USB 3.0 devices (hard disks and flash drives) are not working at USB 3.0 speed, the performances tested by Crystal Disk Mark are really low and also changing AHCI/EHCI options in bios doesn't help. Someone can confirm that USB3.0 performances of the boards tested are really as USB3?

#2106

diderius6

I tested for some hours the XP 64 SP2 (nondebug) on the Giga H110 board. It is original, unmodded Bios F25.
It is amazing stable. Not a single device is unknown in devicemanager, nothing yellow:)).
I also succeed to find drivers for the SM controller, memory controller, Intel Mei for Skylake cpu, just everything.
And it is real USB 3 as you can see on photo. The USB is recogniced at once, thanks to ⇗ @daniel_k .
For the direct install (nlite) via CD to the Giga H110 board I chose acpi_test6.sys (post 2077), because it contains also the mod from @skullteria.
Also I integrate in CD the STORAHCI driver from ⇗ @skullteria with newest storport.sys (version 64 bit 5.2.3790.4173)
And I use the hal.dll for the crazy timer from ⇗ @Mov AX, 0xDEAD .
Dietmar
PS: Thanks to ⇗ @infuscomus , who makes this XP 64 possible. Now I have also XP 64 SP2 debug version and fun can start via windbg:)).
⇗

#2107

skullteria

> Zitat von ⇗ diderius6 im Beitrag ¶ #2106

> I tested for some hours the XP 64 SP2 (nondebug) on the Giga H110 board. It is original, unmodded Bios F25.
> It is amazing stable. Not a single device is unknown in devicemanager, nothing yellow:)).
> I also succeed to find drivers for the SM controller, memory controller, Intel Mei for Skylake cpu, just everything.
> And it is real USB 3 as you can see on photo. The USB is recogniced at once, thanks to @daniel_k .
> For the direct install (nlite) via CD to the Giga H110 board I chose acpi_test6.sys (post 2077), because it contains also the mod from @skullteria.
> Also I integrate in CD the STORAHCI driver from @skullteria with newest storport.sys (version 64 bit 5.2.3790.4173)
> And I use the hal.dll for the crazy timer from @Mov AX, 0xDEAD .
> Dietmar
> PS: Thanks to @infuscomus , who makes this XP 64 possible. Now I have also XP 64 SP2 debug version and fun can start via windbg:)).
> ⇗

Hey, please test with Server 2003 x86. And, switch kernel too. You don't need really lastest version of storport.sys. I tested Windows XP with Server 2003 SP2 vanilla (5.2.3790.3959)

#2108 | Andalu | ⇗ @diderius6 Thanks for your proof. So it's an issue for me only. Too strange, same problem for two different systems (Haswell and Ivy): drivers correctly installed and devices usb3 recognized but performances too poor.
#2109 | diderius6 | ⇗ @Andalu May be it is a problem from DSDT in Bios: The USB3 is marked as USB2 there. Have you tested on Win7? The driver works there also, Dietmar
#2110 | skullteria | Well, i have a challenge. When i try use winload from Windows Vista on XP/2003 on real machine, i get A5 0x0000002 BSOD. Somebody can help to try fix it? Fixing it, we can use lastest Windows Setup engine based in WIM format ( for now, i only can use 5231 version) and can do a multiversion install for XP/2003/Reactos.
#2111 | infuscomus | ⇗ @skullteria winload from vista beta or RTM?
#2112 | XPLAKE8175 | ⇗ @diderius6 Hello, I still get error 10 on Intel hd 5500.

#2113

skullteria

> Zitat von ⇗ infuscomus im Beitrag ¶ #2111

> @skullteria
> winload from vista beta or RTM?

Both beta and RTM, up build 5307 +, mainly RTM.

#2114 | XPLAKE8175 | ⇗ @diderius6 I will tell you possible issues: - Registry issue - Lack of the .dll and .sys.

#2115

diderius6

⇗ @XPLAKE8175
The Intel hd 5500 is just too new.
I have not seen any driver for XP for it.
⇗ @daniel_k told,
that there is no possibility to mod this driver
from Win7 for XP.
When it is not possible to use the HD 4000 driver
from XP for it,
it will not work
Dietmar
EDIT:
Make a try with
⇗ http://drivers.drp.su/Video_Intel-XP/Int...10.5445-drp.exe

## Page 142

#2116

IntiMD

> Zitat von ⇗ diderius6 im Beitrag ¶ #2115

> @XPLAKE8175
> EDIT:
> Make a try with
> ⇗ http://drivers.drp.su/Video_Intel-XP/Int...10.5445-drp.exe

The redirect seems to not work, here's the actual zipfile for that haswell version: ⇗ http://drivers.drp.su/Video_Intel-XP/Int...10.5445-drp.zip
EDIT: fixed the link, incorrectly pasted the x64 version

#2117

Andalu

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #2109

> May be it is a problem from DSDT in Bios: The USB3 is marked as USB2 there.
> Have you tested on Win7? The driver works there also

I never tried the modded driver on another system that is not XP, i need to use XP only on those systems :) and i'm hoping to have a fully functionally USB3 too.

> Zitat von ⇗ diderius6 im Beitrag ¶ #2106

> I also succeed to find drivers for the SM controller, memory controller, Intel Mei for Skylake cpu, just everything.

Could you give me please the links where downloading these drivers? In the next days i will have an Asrock B250M Pro4 and probably a kaby lake cpu, and, availability of time permitting, i'll also try to install XP on that board.
Thanks in advance ;)

#2118 | diderius6 | ⇗ @Andalu I did an intensive search with the DEV_ numbers of each device and the name "Skylake" on Internet. I found them at different places, tried a lot Dietmar

#2119

IntiMD

> Zitat von ⇗ Andalu im Beitrag ¶ #2117

> Could you give me please the links where downloading these drivers? In the next days i will have an Asrock B250M Pro4 and probably a kaby lake cpu, and, availability of time permitting, i'll also try to install XP on that board.
> Thanks in advance ;)

Not him but for those devices you can use Fernando's AIO pure Intel Chipset Device inf files ⇗ here (Point II). I recommend doing it only for those intel chipset devices in the other drivers section of device manager.

#2120 | Andalu | ⇗ @diderius6 ⇗ @IntiMD thanks for the info, i'll give a try

#2121

Illen

XP x64 works well on ASRock Z170 Pro4S with both acpi_test1 and acpi_test6
I also tried UEFI booting it, but unfortunately it doesn't want to work with BootMGR/Winload from Vista Beta 2 and RC, and the Server 2008 Beta 3 or Vista Beta SP1 ones are pretty much unobtainable.
⇗

#2122 | infuscomus | ⇗ @daniel_k ⇗ @diderius6 just thought I'd try your ACPI driver from post 2076 in virtualbox to see if the virtualized intel USB 3.0 works properly using driver from post 2072 - all working now. nice!

#2123

skullteria

> Zitat von ⇗ Illen im Beitrag ¶ #2121

> XP x64 works well on ASRock Z170 Pro4S with both acpi_test1 and acpi_test6
> I also tried UEFI booting it, but unfortunately it doesn't want to work with BootMGR/Winload from Vista Beta 2 and RC, and the Server 2008 Beta 3 or Vista Beta SP1 ones are pretty much unobtainable.
> ⇗

Some question: Geforce 1060 6GB is installed on XP x64?

#2124

diderius6

⇗ @Illen
Nice work:))!
I am also very interested in UEFI boot.
Did you take a look at
⇗ https://www.betaarchive.com/forum/viewto...2dd71d&start=25
and test with Longhorn 5112 or 5231 AMD64 each
⇗ https://winworldpc.com/product/windows-l...-vis/post-reset
Dietmar

#2125

skullteria

> Zitat von ⇗ diderius6 im Beitrag ¶ #2124

> @Illen
> Nice work:))!
> I am also very interested in UEFI boot.
> Did you take a look at
> ⇗ https://www.betaarchive.com/forum/viewto...2dd71d&start=25
> and test with Longhorn 5112 or 5231 AMD64 each
> ⇗ https://winworldpc.com/product/windows-l...-vis/post-reset
> Dietmar

⇗ @diderius6, be careful, need test on real machine...All winload/bootmgr from Vista 5048 - 5310 tested by me not work on Core based systems. All i get BILibray black screen. And up these builds get A5 BSOD. Virtual Machin not reflect the reality.

#2126

diderius6

On a special wish
I installed XP SP1 32 bit on the Giga H110 board.
The last acpi.sys works there and also all USB, network,
just everything.
1 year ago I noticed, that XP SP1 does not like to work with storport.sys.
Because of this I use the normal AHCI Intel driver from Fernando via nlite
Dietmar

#2127

Illen

> Zitat von ⇗ skullteria im Beitrag ¶ #2123

> Some question: Geforce 1060 6GB is installed on XP x64?

It's a 368.81 driver for XP x64, only 2D acceleration works (GDI, ddraw, etc.). No OpenGL or Direct3D.

> Zitat von ⇗ diderius6 im Beitrag ¶ #2124

> Nice work:))!
> I am also very interested in UEFI boot.
> Did you take a look at
> ⇗ https://www.betaarchive.com/forum/viewto...2dd71d&start=25
> and test with Longhorn 5112 or 5231 AMD64 each
> ⇗ https://winworldpc.com/product/windows-l...-vis/post-reset
> Dietmar

Yep, these early beta builds are known to have 32 bit EFI bootloader, or not have EFI bootloader at all. The later ones (6.0.5384.4 or newer) do have an 64 bit EFI bootloader, although these are still quite buggy and don't work with my Z170. There's one build (Longhorn Server Beta 3 6001.16497) which is known to have a 64 bit UEFI bootloader that works on newer hardware and still can boot NT 5.2 (see: ⇗ https://www.betaarchive.com/forum/viewto...=434233#p434233), but I couldn't find this build (nor any others that are close) anywhere.

#2128 | diderius6 | ⇗ @Illen betaarchive has this OS on its ftp server (''Longhorn Server'' 6.0.6001.16497) (x64 Server beta3).rar but I dont know, how to download it from there Dietmar
#2129 | infuscomus | ⇗ @diderius6 you need to be granted permission to download off the betaarchive FTP server.
#2130 | Andalu | Finally! An old Ivy board (Asrock B75 Pro3-M) with USB3 ports fully functional. Thanks again to all you guys ;) ⇗ But about my haswell board I don't give up :) no other suggestion?

## Page 143

#2131

AddFun

So, what is driver pack I should use to get USB support on a X370/Ryzen platform? I have a PS/2 keyboard so far, but that's about it. Also, what are you guys doing for various PCI devices? My device manager is just yellow question marks galore.
Also, I tried the latest "final" ACPI.sys by Daniel, works perfect as the older one, only difference with the new one the boot time seems to be doubled, but it does get to desktop just fine.

#2132

IntiMD

> Zitat von ⇗ AddFun im Beitrag ¶ #2131

> So, what is driver pack I should use to get USB support on a X370/Ryzen platform? I have a PS/2 keyboard so far, but that's about it. Also, what are you guys doing for various PCI devices? My device manager is just yellow question marks galore.
> Also, I tried the latest "final" ACPI.sys by Daniel, works perfect as the older one, only difference with the new one the boot time seems to be doubled, but it does get to desktop just fine.

The one from post #2089, which is same usb3.0 pack published by daniel_k in post #1919 (AMDXHCI_XP_FINAL.rar). This worked for my friend Illen (although he used the x64 version and x64 acpi mod which acpi_test1.sys and acpi_test6.sys each worked for him)
>Also, what are you guys doing for various PCI devices? My device manager is just yellow question marks galore.
Depends but if they are Intel ones, i'm pretty sure those are chipset devices, so you can use Fernando's AIO pure Intel Chipset Device inf files here (Point II). I recommend doing it only for those intel chipset devices with yellow bang (in other drivers section) of device manager.

#2133 | XPLAKE8175 | Chipset INF files are such a bloatware. If you install them, the performance doesn't increase. The most important missing driver is Intel HD Graphics 5500.
#2134 | XPLAKE8175 | I downloaded it from drpsu and it has two igxp32.inf variants. First is igxp32.inf and second is igxp32_tweak.inf. The Broadwell CPU is Improved version of haswell version.

#2135

IntiMD

> Zitat von ⇗ XPLAKE8175 im Beitrag ¶ #2133

> Chipset INF files are such a bloatware. If you install them, the performance doesn't increase. The most important missing driver is Intel HD Graphics 5500.

They aren't bloatware, maybe if you force the software set to install even though it isn't needed might bloat up the registry and windows/inf, but if you install the pure Intel Chipset Device *.inf files in point II of Fernando's thread regarding Intel Chipset Device "Drivers" only for the intel devices with yellow bang (in "Other devices" section), they won't do any harm

#2136 | XPLAKE8175 | Diderius6's acpi.sys for Ryzen boards works pretty well with ASUS k555lb. Qualcomm AR956x has Windows XP drivers.
#2137 | infuscomus | ⇗ @diderius6 any news on XP x64 debug for ryzen?
#2138 | XPLAKE8175 | ⇗ @diderius6 An unknown person at msfn.org said that drpsu intel hd gpu will work on skylake. The embedded intel hd gpu gets error on haswell U series processors too. I have got broadwell U series Intel HD Gpu. I want to get HDMI audio and internal gpu works on Windows XP. The discrete gpu drivers (Nvidia) doesn't show yellow exclamation mark.
#2139 | dencorso | Super-sized French fries on the side, maybe?

#2140

diderius6

⇗ @infuscomus
I will set up a 64 Bit debug XP on the Giga 110 board,
which I port to the Ryzen board Asrock Fatal1ty AB350 gaming k4.
The next 2 days I have time for this and I hope,
that windbg will show the needed information about BSOD
which helps to overcome it
Dietmar

#2141

diderius6

⇗ @Illen
I got the needed *.efi files for Vista (Longhorn) Server Beta 3 6.0.6001.16497.
Now fun can start for Uefi boot of XP
Dietmar
diderius6 has attached files to this post

- ⇗ xp_efi.rar

#2142

daniel_k

⇗ @Mov AX, 0xDEAD

    If (LGreaterEqual (OSYS, 0x07D6))
    {
    	And (PDBM, 0xFFFFFFFFFFFFFFF9, PDBM) /* \_SB_.PCI0.XHC_.PDBM */
    }

Instead of skipping the code, what do you think of changing the 64-bit value to a 32-bit one as the higher order part is ignored anyway in this operation?

    And (PDBM, 0xFFFFFFF9, PDBM)

I did not try it yet, just want to confirm this is technically correct.
Is there a way to find out the actual address of the PDBM variable to check if the resulting value stays the same when using both 32-bit and 64-bit values, on Windows 7?
EDIT: With AIDA64 Enginner I can query the variable PDBM:

    _SB_.PCI0.XHC_.PDBM: Success
    ---------------------------
    *** Argument #0:  Type = 0, DataLength = 4 ***
    Int. Data = 1024  (0x00000400)
    ---------------------------

That's with the device disabled. If I enable the XHCI controller, data is 0x00000406.
Don't know how to use the arguments.
To make sure the data is the same, aren't we supposed to see the whole 8 bytes data (64-bit) or those 4 bytes are enough?
Sadly the ACPI Browser doesn't work on XP (tree is not populated).

#2143

daniel_k

⇗ @IntiMD, thanks for the report.
I believe we should only patch where required, so acpi_test1.sys is the final release for Intel only systems.
We need to wait for Dietmar to fix Ryzen support so we can have a single file supporting both Intel and AMD systems.
I must stress: this does NOT work on Ryzen systems.

#2144

XPLAKE8175

⇗ @diderius6
Which Section of my dsdt table must be solved to not get ACPI 0x000000A5 error. Detailed error codes and informations are:
0x00000001:
This argument is defined as an ACPI root resources failure. More specifically, ACPI could not find the system control interrupt (SCI) vector in any of the resources that ACPI received at startup. SCI is a special interrupt type that provides a more efficient way to deal with problems that are normally handled by system management interrupts (SMI). If SCIs cannot be initialized, ACPI cannot function. This can occur if no entry for this IRQ is found in the list or if no IRQ resource list was found at all.
0x00000002:
This error is defined as ACPI root PCI resource failure. To discover what current resources are being used by PCI devices, ACPI must be able to query the CRS descriptor in the ACPI namespace. This error occurs if the BIOS lacks a pointer to the list, or if the list is empty, or if the list contains errors or conflicts.
Here is your dsdt table for my Asus k555lb laptop:
XPLAKE8175 has attached files to this post

- ⇗ DSDTK555LB.zip

#2145 | diderius6 | ⇗ @XPLAKE8175 Have you made a try with the acpi.sys from post 2076 for XP SP3? No mod in DSDT is needed, it works on all AMD, Intel boards that I tested, also for USB Dietmar

## Page 144

#2146 | XPLAKE8175 | ⇗ @diderius6 How can I integrate it? Windows 10 or XP mps mode? I tried asl /loadtable dsdt.aml.

#2147

skullteria

> Zitat von ⇗ XPLAKE8175 im Beitrag ¶ #2144

> @diderius6
> Which Section of my dsdt table must be solved to not get ACPI 0x000000A5 error. Detailed error codes and informations are:
> 0x00000001:
> This argument is defined as an ACPI root resources failure. More specifically, ACPI could not find the system control interrupt (SCI) vector in any of the resources that ACPI received at startup. SCI is a special interrupt type that provides a more efficient way to deal with problems that are normally handled by system management interrupts (SMI). If SCIs cannot be initialized, ACPI cannot function. This can occur if no entry for this IRQ is found in the list or if no IRQ resource list was found at all.
> 0x00000002:
> This error is defined as ACPI root PCI resource failure. To discover what current resources are being used by PCI devices, ACPI must be able to query the CRS descriptor in the ACPI namespace. This error occurs if the BIOS lacks a pointer to the list, or if the list is empty, or if the list contains errors or conflicts.
> Here is your dsdt table for my Asus k555lb laptop:

"This can occur if no entry for this IRQ is found in the list or if no IRQ resource list was found at all.
0x00000002:"
This is the error when try load Window Xp with winload from Vista

#2148 | XPLAKE8175 | This error related with IRQs.

#2149

diderius6

⇗ @XPLAKE8175
Copy this acpi.sy_ into your folder i386 on the installations CD of XP 32 bit.
Then use nlite 1.4.9.3 to make bootable CD *.iso
Dietmar
diderius6 has attached files to this post

- ⇗ acpi.rar

#2150

daniel_k

⇗ @Mov AX, 0xDEAD
I've tried really hard to patch existing functions related to opcodes but failed.
Apart from QwordConst which you guided me to add, there are only 2 that need to be added to original XP's ACPI.SYS 5512: CreateQwordField and ToInteger.
I was working on 5512 because don't like the idea of mixing files from a beta OS.
Tried to hook it to a similar function such as Decrement/Increment and added a check for opcode 99 for skipping any operation (+ or -, as expected), right before the 0x75 opcode compare.
XP works just fine, but as soon as I change the DSDT to enable processing of ToInteger, it crashes.

#2151 | XPLAKE8175 | ⇗ @diderius6 I did the method and it succeeded but restarts every time if a new hardware plugged in. How can I load your DSDT.aml?

#2152

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #2142

> @Mov AX, 0xDEAD

>     If (LGreaterEqual (OSYS, 0x07D6))
>     {
>     	And (PDBM, 0xFFFFFFFFFFFFFFF9, PDBM) /* \_SB_.PCI0.XHC_.PDBM */
>     }

> Instead of skipping the code, what do you think of changing the 64-bit value to a 32-bit one as the higher order part is ignored anyway in this operation?

>     And (PDBM, 0xFFFFFFF9, PDBM)

yes, it is right for acpi.sys with 32 integers
p.s my patch of classic 5512 do exactly what you said ¶ Windows XP SP3 32bit and modern PC parts (128) without any changes in dsdt
it load only low 4 bytes (res.int<-esi) then increment ip to next opcode (+8)
5048 dont need this because it already has 64 integers support ¶ Windows XP SP3 32bit and modern PC parts (21)

#2153 | daniel_k | ⇗ @Mov AX, 0xDEAD, what I want to know is if it won't affect functionality newer OSes with support for 64-bit integers. Don't want to screw anything. Will it behave the same as with original code?

#2154

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #2150

> @Mov AX, 0xDEAD
> Apart from QwordConst which you guided me to add, there are only 2 that need to be added to original XP's ACPI.SYS 5512: CreateQwordField and ToInteger.

copy pointer CreateDwordField to CreateQwordField struct. Creating real 64 bit adressing will be more harder.

> Zitat

> XP works just fine, but as soon as I change the DSDT to enable processing of ToInteger, it crashes.

> Zitat

> after i discovered "vista beta acpi.sys" anyone can add new opcode handlers to classic winxp acpi.sys, but only 32 bit integers betas is compatible with winxp. 1) copy bytes from existing acpi.sys 2) add relocs 3) create missing structs 4) add missing import or replace with internal impelemtation
> that's how I made my acpi.sys but took the code from win7 x32 (converted back 64-int logic to 32-int)

#2155

Illen

⇗ @diderius6
Got XP x64 to boot from UEFI on my Z170, using the NVidia 8400GS GPU (instead of GTX 1060) with the Anapa VBE driver installed. This is not pure UEFI yet though (legacy video support is required), because the 8400GS doesn't support UEFI and the NVidia XP native drivers (340.52 for 8400GS and 368.81 for GTX 1060) didn't like UEFI boot. I couldn't get VBE driver to work on GTX 1060 or HD 530 iGPU either.

#2156

diderius6

⇗ @Illen
But this is so nice anyway:))!
Can you please write a short tutorial step by step,
how you reached this,
have a nice evening
Dietmar
PS: Soon I get a lenovo flex 10.
There you have 32 bit UEFI Bios. And the most interesting thing is:
You can update this Bios to 64 bit UEFI. So, you can switch between them
as much as you like .

#2157

diderius6

Until now I do not succeed to install XP64 SP2 debug version on any compi.
I get always the message (using windbg)
An Access Violation occurred in C:\WINDOWS\system32\csrss.exe
Dietmar

>     Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
>     Copyright (c) Microsoft Corporation. All rights reserved.

>     Opened \\.\com1
>     Waiting to reconnect...
>     Connected to Windows Server 2003 3790 x64 target at (Sat Aug 31 00:07:51.421 2019 (UTC + 2:00)), ptr64 TRUE
>     Kernel Debugger connection established.
>     WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
>     Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
>     *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
>     Executable search path is: C:\localsymbols
>     Windows Server 2003 Kernel Version 3790 MP (1 procs) Checked x64
>     Built by: 3790.srv03_sp2_rtm.070216-1710
>     Machine Name:
>     Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`013d1fd0
>     System Uptime: not available
>     AhciHwFindAdapter finishing
>     ==>netdmaInitialize
>     <==__FUNCTION__ Status 0
>     WDF: [DriverEntry] HDAudio Bus Driver - Driver Framework Edition.
>     WDF: [DriverEntry] Built May 26 2005 08:46:10
>     KDTARGET: Refreshing KD connection
>     FromRegistry: Option1 = 0
>     22:08:14.734+9cf0dc20:0000+RDPDYN_Dispatch         +0680+Unhandled PnP IRP with minor 00000018
>     VideoPort: This is an ACPI Machine !
>     HDAudBus: [AzStartDevice] Starting hdaudio bus driver device 0x00000520646AD027
>     HDAudBus: [ReadPciDeviceId] Vendor ID: 10DE, Device ID: E0F, Revision ID: A1
>     HDAudBus: [AzEnumerateBus] Scanning codec on SDI0
>     HDAudBus: [AzEnumerateBus] Scanning function group at node 1
>     HDAudBus: [AzEnumerateBus] SSID 0, trying new control verb.
>     HDAudBus: [AzEnumerateBus] New SSID: 19DA730B.
>     HDAudBus: [AzStartDevice] Starting hdaudio bus driver device 0x0000052064C1A8D7
>     HDAudBus: [ReadPciDeviceId] Vendor ID: 8086, Device ID: A170, Revision ID: 31
>     HDAudBus: [AzEnumerateBus] Scanning codec on SDI0
>     HDAudBus: [AzEnumerateBus] Scanning function group at node 1
>     HDAudBus: [AzEnumerateBus] SSID 0, trying new control verb.
>     HDAudBus: [AzEnumerateBus] New SSID: 1458A182.

>     ***
>      Assertion failed: ((Timer)->Header.Type == TimerNotificationObject)
>     || ((Timer)->Header.Type == TimerSynchronizationObject)
>     ***   Source File: d:\nt\base\ntos\ke\timerobj.c, line 190

>     Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i
>     i
>     ==>NetDmaRegisterClient: ClientContext 0000000000000000
>     <==NetDmaRegisterClient: ClientContext 0000000000000000, ClientHandle FFFFFADF9A966A50, Status 0
>     ==>NetDmaAllocateChannel: ClientHandle FFFFFADF9A966A50
>     <==NetDmaAllocateChannel: ClientHandle FFFFFADF9A966A50, Status c000009a
>     ==>NetDmaAllocateChannel: ClientHandle FFFFFADF9A966A50
>     <==NetDmaAllocateChannel: ClientHandle FFFFFADF9A966A50, Status c000009a
>     ==>NetDmaAllocateChannel: ClientHandle FFFFFADF9A966A50
>     <==NetDmaAllocateChannel: ClientHandle FFFFFADF9A966A50, Status c000009a
>     ==>NetDmaAllocateChannel: ClientHandle FFFFFADF9A966A50
>     <==NetDmaAllocateChannel: ClientHandle FFFFFADF9A966A50, Status c000009a
>     Checking file system on C:
>     The volume is clean.
>     Windows has finished checking the disk.
>     GDI: VerifierInitialization: failed to get info from ntoskrnl

>     (s: 0 0x180.184 smss.exe) USRK-[Wrn] *** win32k: DBCS:[0] IME:[0] MiddleEast:[0] CTFIME:[0]
>     Installed
>     Installed
>     R2BuildNumber

>      *** An Access Violation occurred in C:\WINDOWS\system32\csrss.exe
>     ObjectDirectory=\Windows SharedSection=1024,20480,768 Windows=On
>     SubSystemType=Windows ServerDll=basesrv,1
>     ServerDll=winsrv:UserServerDllInitialization,3
>     ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off
>     MaxRequestThreads=16:

>     The instruction at 0000000077F1E1D1 tried to read from an invalid address, 0000000000000018

>      *** enter .exr 000000000015F370 for the exception record
>      ***  enter .cxr 000000000015EEA0 for the context
>      *** then kb to get the faulting stack

>     Break instruction exception - code 80000003 (first chance)
>     ntdll!DbgBreakPoint:
>     0033:00000000`77f86240 cc              int     3
>     0: kd> !analyze -v
>     Connected to Windows Server 2003 3790 x64 target at (Sat Aug 31 00:10:03.312 2019 (UTC + 2:00)), ptr64 TRUE
>     Loading Kernel Symbols
>     ...............................................................
>     ...................
>     Loading User Symbols
>     ....
>     Loading unloaded module list
>     .......
>     *******************************************************************************
>     *                                                                             *
>     *                        Exception Analysis                                   *
>     *                                                                             *
>     *******************************************************************************

>     *** ERROR: Symbol file could not be found.  Defaulted to export symbols for CSRSRV.dll -
>     *** ERROR: Module load completed but symbols could not be loaded for csrss.exe

>     FAULTING_IP:
>     ntdll!RtlAllocateHeap+51
>     0033:00000000`77f1e1d1 440b6718        or      r12d,dword ptr [rdi+18h]

>     EXCEPTION_RECORD:  000000000015f370 -- (.exr 0x15f370)
>     ExceptionAddress: 0000000077f1e1d1 (ntdll!RtlAllocateHeap+0x0000000000000051)
>        ExceptionCode: c0000005 (Access violation)
>       ExceptionFlags: 00000000
>     NumberParameters: 2
>        Parameter[0]: 0000000000000000
>        Parameter[1]: 0000000000000018
>     Attempt to read from address 0000000000000018

>     ERROR_CODE: (NTSTATUS) 0x80000003 - {AUSNAHME}  Haltepunkt  Im Quellprogramm wurde ein Haltepunkt erreicht.

>     EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - Mindestens ein Argument ist ung ltig.

>     EXCEPTION_PARAMETER1:  0000000000000000

>     MOD_LIST: <ANALYSIS/>

>     NTGLOBALFLAG:  440000

>     APPLICATION_VERIFIER_FLAGS:  0

>     CONTEXT:  000000000015eea0 -- (.cxr 0x15eea0)
>     rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
>     rdx=0000000020040000 rsi=0000000000164bb0 rdi=0000000000000000
>     rip=0000000077f1e1d1 rsp=000000000015f440 rbp=000000000016481f
>      r8=0000000000001ac8  r9=0000000000000000 r10=0065007400730079
>     r11=000000000015f618 r12=0000000020040000 r13=0000000000000000
>     r14=0000000000000080 r15=000007ff7c5b1918
>     iopl=0         nv up ei pl zr na po nc
>     cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
>     ntdll!RtlAllocateHeap+0x51:
>     0033:00000000`77f1e1d1 440b6718        or      r12d,dword ptr [rdi+18h] ds:002b:00000000`00000018=????????
>     Resetting default scope

>     READ_ADDRESS:  0000000000000018

>     FOLLOWUP_IP:
>     basesrv!ServerDllInitialization+0
>     0033:000007ff`7c1e5810 48894c2408      mov     qword ptr [rsp+8],rcx

>     LAST_CONTROL_TRANSFER:  from 000007ff7c1e5b60 to 0000000077f1e1d1

>     FAULTING_THREAD:  ffffffffffffffff

>     ADDITIONAL_DEBUG_TEXT:
>       Followup set based on attribute [Is_ChosenCrashFollowupThread] from
>     Frame:[0] on thread:[PSEUDO_THREAD] ; Enable Pageheap/AutoVerifer

>     DEFAULT_BUCKET_ID:  HEAP_CORRUPTION

>     PRIMARY_PROBLEM_CLASS:  HEAP_CORRUPTION

>     BUGCHECK_STR:  APPLICATION_FAULT_HEAP_CORRUPTION_STATUS_BREAKPOINT

>     STACK_TEXT:
>     00000000`0015f440 00000000`77f1e1d1 ntdll!RtlAllocateHeap+0x51
>     00000000`0015f620 000007ff`7c1e5b60 basesrv!ServerDllInitialization+0x350
>     00000000`0015fc50 000007ff`7c5b3eb8 csrsrv!CsrUnhandledExceptionFilter+0x368
>     00000000`0015fd10 000007ff`7c5b38c0 csrsrv!CsrPopulateDosDevices+0x760
>     00000000`0015fee0 000007ff`7c5b3a10 csrsrv!CsrServerInitialization+0xa0
>     00000000`0015ff10 00000000`4a681121 csrss+0x1121
>     00000000`0015ff18 ffffffff`ffffffff unknown!fillpattern+0x0
>     00000000`0015ff20 00000000`00000005 unknown!unknown+0x0
>     00000000`0015ff28 00000000`00164560 unknown!unknown+0x0
>     00000000`0015ff30 00000000`0000000a unknown!unknown+0x0
>     00000000`0015ff38 00000000`0000000d unknown!unknown+0x0
>     00000000`0015ff40 000007ff`00000000 unknown!unknown+0x0
>     00000000`0015ff48 00000000`00164680 unknown!unknown+0x0
>     00000000`0015ff50 00000000`00164630 unknown!unknown+0x0
>     00000000`0015ff58 00000000`0016478d unknown!unknown+0x0
>     00000000`0015ff60 00000000`4a6815bb csrss+0x15bb
>     00000000`0015ff68 00000000`0015ffa0 unknown!unknown+0x0

>     SYMBOL_NAME:  basesrv!ServerDllInitialization+0

>     FOLLOWUP_NAME:  MachineOwner

>     MODULE_NAME: basesrv

>     IMAGE_NAME:  basesrv.dll

>     DEBUG_FLR_IMAGE_TIMESTAMP:  45d73cba

>     STACK_COMMAND:  .cxr 00164CB0 ; kb ; dds 15f440 ; kb

>     FAILURE_BUCKET_ID:  HEAP_CORRUPTION_80000003_basesrv.dll!ServerDllInitialization

>     BUCKET_ID:  X64_APPLICATION_FAULT_HEAP_CORRUPTION_STATUS_BREAKPOINT_basesrv!ServerDllInitialization+0

>     Followup: MachineOwner
>     ---------

#2158 | diderius6 | Now I make a try with only the acpi.sys from XP64 SP2 debug Dietmar
#2159 | daniel_k | ⇗ @Mov AX, 0xDEAD, thanks. ⇗ @Illen, if the GPU accelerated driver doesn't work, IMHO, it doesn't make sense to use XP in UEFI mode. Thanks for sharing the video, interesting anyway. Where the Anapa driver can be found? ⇗ @diderius6, good luck!

#2160

skullteria

Hello, please test winload and bootmgr to boot Windows XP. It is normal version, not UEFI.
skullteria has attached files to this post

- ⇗ BootFiles.zip

## Page 145

#2161

diderius6

⇗ @daniel_k
First we need to solve via forced jmp (EB) in debug acpi.sys XP64 SP2 all the errors,
which appears on Intel boards also. For me it is not easy, because I have no good tools for XP64. When we have eleminated all
the "normal" acpi errors, windbg will hopefully show us the reason of ACPI BSOD, which happens only on Ryzen boards.
For Ida pro we need the symbols for exact this acpi.sys. I add this debug acpi.sys here.
This is from asus prime x570-pro Ryzen board with Bios version 407
and original DSDT in Bios. This is the very first time, that I get an output which belongs pur to acpi.sys.

>     Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
>     Copyright (c) Microsoft Corporation. All rights reserved.

>     Opened \\.\com1
>     Waiting to reconnect...
>     Connected to Windows Server 2003 3790 x64 target at (Sat Aug 31 01:43:18.109 2019 (UTC + 2:00)), ptr64 TRUE
>     Kernel Debugger connection established.
>     WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
>     Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
>     *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
>     Executable search path is: C:\localsymbols
>     Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64
>     Built by: 3790.srv03_sp2_rtm.070216-1710
>     Machine Name:
>     Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d5100
>     System Uptime: not available
>     ACPIInitializeDDB: AMLILoadDDB failed 0xc0140001

>     *** Assertion failed: ACPIInitializeDDB: AMLILoadDDB failed to load DDB
>     0
>     ***   Source File: d:\nt\base\busdrv\acpi\driver\shared\acpiinit.c, line 515

>     Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i
>     i

>     *** Fatal System Error: 0x000000a5  <---  Hack, which blocks all bugcheck A5 11h in acpi.sys
>                            (0x0000000000000011,0x0000000000000008,0xFFFFFADF9339B1F8,0x0000000020120913)

>     Break instruction exception - code 80000003 (first chance)

>     A fatal system error has occurred.
>     Debugger entered on first try; Bugcheck callbacks have not been invoked.

>     A fatal system error has occurred.

>     Connected to Windows Server 2003 3790 x64 target at (Sat Aug 31 01:43:56.437 2019 (UTC + 2:00)), ptr64 TRUE
>     Loading Kernel Symbols
>     ........................
>     Loading User Symbols

>     *******************************************************************************
>     *                                                                             *
>     *                        Bugcheck Analysis                                    *
>     *                                                                             *
>     *******************************************************************************

>     Use !analyze -v to get detailed debugging information.

>     BugCheck A5, {11, 8, fffffadf9339b1f8, 20120913}

>     *** No owner thread found for resource fffff800011dda40
>     *** No owner thread found for resource fffff800011dda40
>     *** No owner thread found for resource fffff800011dda40
>     Probably caused by : ACPI.sys ( ACPI!ACPIInitializeDDB+127 )

>     Followup: MachineOwner
>     ---------

>     nt!DbgBreakPointWithStatus:
>     fffff800`01026db0 cc              int     3
>     0: kd> !analyze -v
>     *******************************************************************************
>     *                                                                             *
>     *                        Bugcheck Analysis                                    *
>     *                                                                             *
>     *******************************************************************************

>     ACPI_BIOS_ERROR (a5)
>     The ACPI Bios in the system is not fully compliant with the ACPI specification.
>     The first value indicates where the incompatibility lies:
>     This bug check covers a great variety of ACPI problems.  If a kernel debugger
>     is attached, use "!analyze -v".  This command will analyze the precise problem,
>     and display whatever information is most useful for debugging the specific
>     error.
>     Arguments:
>     Arg1: 0000000000000011, ACPI_SYSTEM_CANNOT_START_ACPI
>     	The system could not enter ACPI mode
>     Arg2: 0000000000000008, Failed to load DDB
>     Arg3: fffffadf9339b1f8, Pointer to the table that ACPI failed to load
>     Arg4: 0000000020120913, Creator Revision

>     Debugging Details:
>     ------------------

>     *** No owner thread found for resource fffff800011dda40
>     *** No owner thread found for resource fffff800011dda40
>     *** No owner thread found for resource fffff800011dda40

>     DEFAULT_BUCKET_ID:  DRIVER_FAULT

>     BUGCHECK_STR:  0xA5

>     PROCESS_NAME:  System

>     CURRENT_IRQL:  2

>     LOCK_ADDRESS:  fffff800011ddb40 -- (!locks fffff800011ddb40)

>     Resource @ nt!IopDeviceTreeLock (0xfffff800011ddb40)    Shared 1 owning threads
>          Threads: fffffadf9ee91bf0-01<*>
>     1 total locks, 1 locks currently held

>     PNP_TRIAGE:
>     	Lock address  : 0xfffff800011ddb40
>     	Thread Count  : 1
>     	Thread address: 0xfffffadf9ee91bf0
>     	Thread wait   : 0xa1

>     LAST_CONTROL_TRANSFER:  from fffff800010d673e to fffff80001026db0

>     STACK_TEXT:
>     fffffadf`936076d8
>      fffff800`010d673e : 00000000`00000000 00000000`00000000
>     00000000`00000011 fffff800`0105669e : nt!DbgBreakPointWithStatus
>     fffffadf`936076e0
>      fffff800`010d7d0e : fffff800`00000003 00000000`000000a5
>     00000000`00000011 00000000`00000008 : nt!KiBugCheckDebugBreak+0x1e
>     fffffadf`93607740
>      fffff800`0102ea54 : fffffa80`00000000 fffffadf`92d66250
>     fffffadf`9eac0000 fffffadf`9ead05c8 : nt!KeBugCheck2+0x640
>     fffffadf`93607d80
>      fffffadf`92de0a87 : 00000000`000000a5 00000000`00000011
>     00000000`00000008 fffffadf`9339b1f8 : nt!KeBugCheckEx+0x104
>     fffffadf`93607dc0
>      fffffadf`92de0b3a : fffffa80`00000014 00000000`00000000
>     00000000`00000001 fffffadf`93a9c028 : ACPI!ACPIInitializeDDB+0x127
>     fffffadf`93607e20
>      fffffadf`92de0f1f : fffffadf`00000001 fffffadf`92dea901
>     fffffadf`00000003 00000000`00000000 : ACPI!ACPIInitializeDDBs+0xaa
>     fffffadf`93607e60
>      fffffadf`92d72a4a : fffffadf`9ebd0820 fffffadf`92d680b0
>     fffffadf`93607ee0 fffffadf`92dc3cb0 : ACPI!ACPIInitialize+0x2ff
>     fffffadf`93607eb0
>      fffffadf`92ddd3ba : fffffadf`9ebd0820 fffffa80`0045ac80
>     fffffadf`52706341 fffffadf`9ebd0590 : ACPI!ACPIInitStartACPI+0x8a
>     fffffadf`93607f20
>      fffffadf`92d6c804 : fffffadf`9ebd0820 fffffadf`9ebd1260
>     fffffadf`93607fd8 00000000`00000001 : ACPI!ACPIRootIrpStartDevice+0x1ca
>     fffffadf`93607fa0
>      fffff800`0133ed04 : fffffadf`9ebd0820 fffffadf`9ebd1260
>     fffffadf`9ebd0820 00000000`00000000 : ACPI!ACPIDispatchIrp+0x164
>     fffffadf`93608030
>      fffff800`013364e3 : fffffadf`9eeac870 00000000`00000000
>     fffffadf`9eeac480 fffffadf`9eeac870 : nt!IopSynchronousCall+0x144
>     fffffadf`936080a0
>      fffff800`013359a2 : 00000000`00020019 fffffadf`9eeb6000
>     fffffadf`9eeac870 00000000`00000000 : nt!PipProcessStartPhase1+0x1c7
>     fffffadf`93608140
>      fffff800`010cc809 : fffffadf`9ebda3f0 fffff800`00092470
>     fffffadf`9eeb3910 fffffadf`9ebda3f0 : nt!PipProcessDevNodeTree+0x2aa
>     fffffadf`936084d0
>      fffff800`014329f7 : ffffffff`00000000 fffffadf`9ebda3f0
>     fffff800`00092470 fffffadf`9eeb3940 : nt!PipDeviceActionWorker+0x199
>     fffffadf`93608560
>      fffff800`0142a14d : 00000000`00000000 00000000`0000fffc
>     00000000`00000000 00000000`0000fffc : nt!IopInitializeBootDrivers+0xc57
>     fffffadf`936088c0
>      fffff800`01428144 : fffff800`00091598 fffff800`00091598
>     00000000`00000003 fffffadf`9ee90010 : nt!IoInitSystem+0xf4f
>     fffffadf`93608a50
>      fffff800`0130dc29 : 12d93b24`1e99bf20 fffffadf`9ee91bf0
>     00000000`00000080 fffffadf`9ee91bf0 :
>     nt!Phase1InitializationDiscard+0x111d
>     fffffadf`93608d40
>     fffff800`0124b972 : b6e6174a`baa6174e 8dd685ea`819685ee
>     307b39e5`3c3b39e1 0b4bab45`070baf41 : nt!Phase1Initialization+0x9
>     fffffadf`93608d70
>      fffff800`010202d6 : fffff800`011b1180 fffffadf`9ee91bf0
>     fffff800`011b5500 00000000`da83b888 : nt!PspSystemThreadStartup+0x3e
>     fffffadf`93608dd0
>      00000000`00000000 : 00000000`00000000 00000000`00000000
>     00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

>     STACK_COMMAND:  kb

>     FOLLOWUP_IP:
>     ACPI!ACPIInitializeDDB+127
>     fffffadf`92de0a87 cc              int     3

>     SYMBOL_STACK_INDEX:  4

>     SYMBOL_NAME:  ACPI!ACPIInitializeDDB+127  <---  First hack needed in this acpi.sys

>     FOLLOWUP_NAME:  MachineOwner

>     MODULE_NAME: ACPI

>     IMAGE_NAME:  ACPI.sys

>     DEBUG_FLR_IMAGE_TIMESTAMP:  45d70c6e

>     FAILURE_BUCKET_ID:  X64_0xA5_ACPI!ACPIInitializeDDB+127

>     BUCKET_ID:  X64_0xA5_ACPI!ACPIInitializeDDB+127

>     Followup: MachineOwner
>     ---------

diderius6 has attached files to this post

- ⇗ acpiDEBUGXP64SP2.rar

#2162 | daniel_k | ⇗ @diderius6 I've attached 2 files based on the debug x64 ACPI.SYS. acpi_qword.sys: Added QwordConst and CreateQwordField opcodes. acpi_qword_stop_a5_11.sys: Same as above plus disabled Stop error A5, 11h Sent you a PM with something to help you with x64.

#2163

IntiMD

> Zitat von ⇗ daniel_k im Beitrag ¶ #2159

> if the GPU accelerated driver doesn't work, IMHO, it doesn't make sense to use XP in UEFI mode. Thanks for sharing the video, interesting anyway.
> Where the Anapa driver can be found?

Not him but it can be found here: ⇗ https://www.bearwindows.zcm.com.au/vbemp.htm (for the x64 driver, requires a small fix in this ⇗ link)

#2164

diderius6

⇗ @daniel_k
Now the behavior is exact like the 32 bit acpi.sys on Ryzen boards before. I chose your second acpi.sys against BSOD A5 0x011 also.
Now it shows A5 (0x2001,..) error, fail to enable PIC mode (for ACPI).
This means, that your hack works and now we come to the core of the problem on Ryzen XP 64 bit,
Dietmar

>     Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
>     Copyright (c) Microsoft Corporation. All rights reserved.

>     Opened \\.\com1
>     Waiting to reconnect...
>     Connected to Windows Server 2003 3790 x64 target at (Sat Aug 31 11:32:57.859 2019 (UTC + 2:00)), ptr64 TRUE
>     Kernel Debugger connection established.
>     WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
>     Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
>     *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
>     Executable search path is: C:\localsymbols
>     Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64
>     Built by: 3790.srv03_sp2_rtm.070216-1710
>     Machine Name:
>     Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d5100
>     System Uptime: not available

>     *** Fatal System Error: 0x000000a5
>                            (0x0000000000002001,0x0000000000000001,0xFFFFFFFFC0000034,0xFFFFFADF9EAD3238)

>     Break instruction exception - code 80000003 (first chance)

>     A fatal system error has occurred.
>     Debugger entered on first try; Bugcheck callbacks have not been invoked.

>     A fatal system error has occurred.

>     Connected to Windows Server 2003 3790 x64 target at (Sat Aug 31 11:33:11.187 2019 (UTC + 2:00)), ptr64 TRUE
>     Loading Kernel Symbols
>     ........................
>     Loading User Symbols

>     *******************************************************************************
>     *                                                                             *
>     *                        Bugcheck Analysis                                    *
>     *                                                                             *
>     *******************************************************************************

>     Use !analyze -v to get detailed debugging information.

>     BugCheck A5, {2001, 1, ffffffffc0000034, fffffadf9ead3238}

>     *** No owner thread found for resource fffff800011dda40
>     *** No owner thread found for resource fffff800011dda40
>     *** No owner thread found for resource fffff800011dda40
>     Probably caused by : ACPI.sys ( ACPI!NotifyHalWithMachineStates+582 )

>     Followup: MachineOwner
>     ---------

>     nt!DbgBreakPointWithStatus:
>     fffff800`01026db0 cc              int     3
>     15: kd> !analyze -v
>     *******************************************************************************
>     *                                                                             *
>     *                        Bugcheck Analysis                                    *
>     *                                                                             *
>     *******************************************************************************

>     ACPI_BIOS_ERROR (a5)
>     The ACPI Bios in the system is not fully compliant with the ACPI specification.
>     The first value indicates where the incompatibility lies:
>     This bug check covers a great variety of ACPI problems.  If a kernel debugger
>     is attached, use "!analyze -v".  This command will analyze the precise problem,
>     and display whatever information is most useful for debugging the specific
>     error.
>     Arguments:
>     Arg1: 0000000000002001, ACPI_FAILED_PIC_METHOD
>     	ACPI tried to evaluate the PIC control method but failed
>     Arg2: 0000000000000001, InterruptModel (Integer)
>     Arg3: ffffffffc0000034, return value from interpreter
>     Arg4: fffffadf9ead3238, Pointer to the PIC control method

>     Debugging Details:
>     ------------------

>     *** No owner thread found for resource fffff800011dda40
>     *** No owner thread found for resource fffff800011dda40
>     *** No owner thread found for resource fffff800011dda40

>     DEFAULT_BUCKET_ID:  DRIVER_FAULT

>     BUGCHECK_STR:  0xA5

>     PROCESS_NAME:  System

>     CURRENT_IRQL:  2

>     LOCK_ADDRESS:  fffff800011ddb40 -- (!locks fffff800011ddb40)

>     Resource @ nt!IopDeviceTreeLock (0xfffff800011ddb40)    Shared 1 owning threads
>          Threads: fffffadf9ee91bf0-01<*>
>     1 total locks, 1 locks currently held

>     PNP_TRIAGE:
>     	Lock address  : 0xfffff800011ddb40
>     	Thread Count  : 1
>     	Thread address: 0xfffffadf9ee91bf0
>     	Thread wait   : 0x9f

>     LAST_CONTROL_TRANSFER:  from fffff800010d673e to fffff80001026db0

>     STACK_TEXT:
>     fffffadf`93607698
>      fffff800`010d673e : 00000000`0000000f 00000000`00000000
>     00000000`00002001 fffff800`0105669e : nt!DbgBreakPointWithStatus
>     fffffadf`936076a0
>      fffff800`010d7d0e : fffff800`00000003 00000000`000000a5
>     00000000`00002001 00000000`00000001 : nt!KiBugCheckDebugBreak+0x1e
>     fffffadf`93607700
>      fffff800`0102ea54 : 00000000`00000000 00000000`00000000
>     ffffffff`fffdf3f0 fffffa80`004685e0 : nt!KeBugCheck2+0x640
>     fffffadf`93607d40
>      fffffadf`92dcb6f2 : 00000000`000000a5 00000000`00002001
>     00000000`00000001 ffffffff`c0000034 : nt!KeBugCheckEx+0x104
>     fffffadf`93607d80
>      fffffadf`92d72a8b : 00000000`00000000 fffffadf`00000000
>     fffffadf`93607e00 fffffadf`92dc3c00 :
>     ACPI!NotifyHalWithMachineStates+0x582
>     fffffadf`93607eb0
>     fffffadf`92ddd3ba : fffffadf`9ebd0820 fffffa80`0045ac20
>     fffffadf`52706341 fffffadf`9ebd0590 : ACPI!ACPIInitStartACPI+0xcb
>     fffffadf`93607f20
>      fffffadf`92d6c804 : fffffadf`9ebd0820 fffffadf`9ebd1260
>     fffffadf`93607fd8 00000000`00000001 : ACPI!ACPIRootIrpStartDevice+0x1ca
>     fffffadf`93607fa0
>      fffff800`0133ed04 : fffffadf`9ebd0820 fffffadf`9ebd1260
>     fffffadf`9ebd0820 00000000`00000000 : ACPI!ACPIDispatchIrp+0x164
>     fffffadf`93608030
>      fffff800`013364e3 : fffffadf`9eeac870 00000000`00000000
>     fffffadf`9eeac480 fffffadf`9eeac870 : nt!IopSynchronousCall+0x144
>     fffffadf`936080a0
>      fffff800`013359a2 : 00000000`00020019 fffffadf`9eeb6000
>     fffffadf`9eeac870 00000000`00000000 : nt!PipProcessStartPhase1+0x1c7
>     fffffadf`93608140
>      fffff800`010cc809 : fffffadf`9eeb3870 fffff800`00092528
>     fffffadf`9eeb38c0 fffffadf`9eeb3870 : nt!PipProcessDevNodeTree+0x2aa
>     fffffadf`936084d0
>      fffff800`014329f7 : ffffffff`00000000 fffffadf`9eeb3870
>     fffff800`00092528 fffffadf`9eeb38f0 : nt!PipDeviceActionWorker+0x199
>     fffffadf`93608560
>      fffff800`0142a14d : 00000000`00000000 00000000`0000fffc
>     00000000`00000000 00000000`0000fffc : nt!IopInitializeBootDrivers+0xc57
>     fffffadf`936088c0
>      fffff800`01428144 : fffff800`00091650 fffff800`00091650
>     00000000`00000003 fffffadf`9ee90010 : nt!IoInitSystem+0xf4f
>     fffffadf`93608a50
>      fffff800`0130dc29 : 12d93b24`1e99bf20 fffffadf`9ee91bf0
>     00000000`00000080 fffffadf`9ee91bf0 :
>     nt!Phase1InitializationDiscard+0x111d
>     fffffadf`93608d40
>     fffff800`0124b972 : b6e6174a`baa6174e 8dd685ea`819685ee
>     307b39e5`3c3b19e1 0b4bab45`070baf41 : nt!Phase1Initialization+0x9
>     fffffadf`93608d70
>      fffff800`010202d6 : fffff800`011b1180 fffffadf`9ee91bf0
>     fffff800`011b5500 00000000`da83b678 : nt!PspSystemThreadStartup+0x3e
>     fffffadf`93608dd0
>      00000000`00000000 : 00000000`00000000 00000000`00000000
>     00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

>     STACK_COMMAND:  kb

>     FOLLOWUP_IP:
>     ACPI!NotifyHalWithMachineStates+582
>     fffffadf`92dcb6f2 cc              int     3

>     SYMBOL_STACK_INDEX:  4

>     SYMBOL_NAME:  ACPI!NotifyHalWithMachineStates+582

>     FOLLOWUP_NAME:  MachineOwner

>     MODULE_NAME: ACPI

>     IMAGE_NAME:  ACPI.sys

>     DEBUG_FLR_IMAGE_TIMESTAMP:  45d70c6e

>     FAILURE_BUCKET_ID:  X64_0xA5_ACPI!NotifyHalWithMachineStates+582

>     BUCKET_ID:  X64_0xA5_ACPI!NotifyHalWithMachineStates+582

>     Followup: MachineOwner
>     ---------

#2165

diderius6

Hi,
does anybody know,
where I can get SYMBOLS for
the XP64 DEBUG SP2 version
Dietmar
PS: In this case, acpi.pdb for the debug XP 64 SP2 would be enough.
5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
EDIT:
It is in file
WindowsServer2003-KB933548-v1-x64-symbols-NRL-ENU-DEBUG.exe

#2166

Illen

> Zitat von ⇗ diderius6 im Beitrag ¶ #2156

> But this is so nice anyway:))!
> Can you please write a short tutorial step by step,
> how you reached this,
> have a nice evening
> Dietmar

First, you need to install the latest (2015) VBE driver (and also correct the .inf as mentioned in post ¶ #2163). If you install it and it works, copy the contents of "server_BCD" folder (from the ⇗ xp_efi package) over your Windows XP x64 installation. Your drive with XP x64 install should now appear as UEFI bootable device in the boot device selector of your UEFI. Boot from it and choose the "Disable Driver Signature Enforcement" option, now the XP x64 install should boot from UEFI.
Note: You don't need to convert the the drive to GPT, you can keep the MBR partition table (along the NTLDR bootsector).

> Zitat von ⇗ diderius6 im Beitrag ¶ #2156

> PS: Soon I get a lenovo flex 10.
> There you have 32 bit UEFI Bios. And the most interesting thing is:
> You can update this Bios to 64 bit UEFI. So, you can switch between them
> as much as you like .

Nice one, by the way, I do actually have an 32 bit UEFI Class 3 device (an Atom based tablet), on which I would like to experiment with Windows 2003.

> Zitat von ⇗ daniel_k im Beitrag ¶ #2159

> if the GPU accelerated driver doesn't work, IMHO, it doesn't make sense to use XP in UEFI mode. Thanks for sharing the video, interesting anyway.
> Where the Anapa driver can be found?

Indeed, although this might be the only way to boot XP x64 in future, when CSM is entirely depracated.

#2167

infuscomus

⇗ @diderius6
i have them for server 2003 debug x64
infuscomus has attached files to this post

- ⇗ acpi server2003 x64 debug with pdb.zip

#2168 | kukonosau | ACPI Server 2003 x64 for Ryzen?

#2169

infuscomus

> Zitat von ⇗ kukonosau im Beitrag ¶ #2168

> ACPI Server 2003 x64 for Ryzen?

⇗ @kukonosau
not yet, just symbols for debugging

#2170 | kukonosau | Thanks. But ACPI Server 2003 x64 equal ACPI Windows XP x64?

#2171

diderius6

⇗ @daniel_k
I think, the error is in the InterruptModel.
Take a look at (here original) acpi.sys (Debug XP64 SP2)

    83 3D 18 6C FF FF 00 0F 86 95 00 00 00 =>

    83 3D 18 6C FF FF 00 (force jmp loc_7D6F3)

Dietmar
EDIT:
Arguments:
Arg1: 0000000000002001, ACPI_FAILED_PIC_METHOD
ACPI tried to evaluate the PIC control method but failed
Arg2: 0000000000000001, InterruptModel (Integer) <= failed 0000000000000001 is APIC (0000000000000000 is PIC)
Arg3: ffffffffc0000034, return value from interpreter
Arg4: fffffadf9ead3238, Pointer to the PIC control method
EDIT2: I remember, that the BSOD A5 0x2001 happens, when in FACP was writen InterruptModel 00 (Pic).
This BSOD was gone with modded FACP to InterruptModel 01 (Apic).

#2172 | daniel_k | ⇗ @diderius6, I've applied infuscomus's patch for x86. See if it changes something.
#2173 | daniel_k | ⇗ @diderius6, try these as well. I've forced the checks as if InterruptModel was 1 (APIC, are sure about this?).

#2174

diderius6

⇗ @daniel_k
This was not the right place which was modded
against BSOD A5 (0x2001,..)
because all the acpi.sys show exact the same BSOD as before.
Have you looked at my post, at which place you have to JMP,
for to overcome BSOD A5 (0x2001,..)?
I am quite sure, that this is the right place
Dietmar

#2175

daniel_k

⇗ @diderius6, if you fully understand the code, you'll see it will jump if InterruptModel is 0 (zero).

    7D651                 cmp     cs:InterruptModel, 0
    7D658                 jbe     loc_7D6F3 -> Jump if below or equal 0

I've patched the jump right below to skip the BSOD.
Please try again, the 4 files.

## Page 146

#2176

diderius6

⇗ @daniel_k
I understand the missunderstanding:
The irqs are the problem of Ryzen.
And even it is Interrupt 1,
it fails
Dietmar
PS: Yes to jump always over the BSOD call A5 0x2001 is the right idea.

#2177

diderius6

I just test acpi-test1.sys. The BSOD A5 2001 is gone.
The behavior is exact like from acpi.sys for 32 bit.
Now comes there next also the BSOD A5 0x02
Dietmar

>     Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
>     Copyright (c) Microsoft Corporation. All rights reserved.

>     Opened \\.\com1
>     Waiting to reconnect...
>     Connected to Windows Server 2003 3790 x64 target at (Sat Aug 31 18:17:50.656 2019 (UTC + 2:00)), ptr64 TRUE
>     Kernel Debugger connection established.
>     WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
>     Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
>     *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
>     Executable search path is: C:\localsymbols
>     Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64
>     Built by: 3790.srv03_sp2_rtm.070216-1710
>     Machine Name:
>     Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d5100
>     System Uptime: not available

>     *** Assertion failed: NT_SUCCESS(status)
>     ***   Source File: d:\nt\base\busdrv\acpi\driver\nt\bus.c, line 2682

>     Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i
>     i
>     FFFFFADF9EE95010 ACPI\PNP0A08-0 (0x9ebd94f0): IRP_MN_QUERY_RESOURCE_REQUIREMENTS = 0xc00000bb

>     *** Fatal System Error: 0x000000a5
>                            (0x0000000000000002,0xFFFFFADF9EE95010,0x0000000000000001,0xFFFFFADF9EBD94F0)

>     Break instruction exception - code 80000003 (first chance)

>     A fatal system error has occurred.
>     Debugger entered on first try; Bugcheck callbacks have not been invoked.

>     A fatal system error has occurred.

>     Connected to Windows Server 2003 3790 x64 target at (Sat Aug 31 18:18:19.546 2019 (UTC + 2:00)), ptr64 TRUE
>     Loading Kernel Symbols
>     ........................
>     Loading User Symbols

>     *******************************************************************************
>     *                                                                             *
>     *                        Bugcheck Analysis                                    *
>     *                                                                             *
>     *******************************************************************************

>     Use !analyze -v to get detailed debugging information.

>     BugCheck A5, {2, fffffadf9ee95010, 1, fffffadf9ebd94f0}

>     *** No owner thread found for resource fffff800011dda40
>     *** No owner thread found for resource fffff800011dda40
>     *** No owner thread found for resource fffff800011dda40
>     *** No owner thread found for resource fffff800011dda40
>     Probably caused by : ACPI.sys ( ACPI!ACPIBusIrpQueryResourceRequirements+446 )

>     Followup: MachineOwner
>     ---------

>     nt!DbgBreakPointWithStatus:
>     fffff800`01026db0 cc              int     3
>     15: kd> !analyze -v
>     *******************************************************************************
>     *                                                                             *
>     *                        Bugcheck Analysis                                    *
>     *                                                                             *
>     *******************************************************************************

>     ACPI_BIOS_ERROR (a5)
>     The ACPI Bios in the system is not fully compliant with the ACPI specification.
>     The first value indicates where the incompatibility lies:
>     This bug check covers a great variety of ACPI problems.  If a kernel debugger
>     is attached, use "!analyze -v".  This command will analyze the precise problem,
>     and display whatever information is most useful for debugging the specific
>     error.
>     Arguments:
>     Arg1: 0000000000000002, ACPI_ROOT_PCI_RESOURCE_FAILURE
>     	ACPI could not process the resource list for the PCI root buses
>     Arg2: fffffadf9ee95010, The ACPI Extension for the PCI bus.
>     Arg3: 0000000000000001, ACPI cannot convert the BIOS' resource list into the proper
>     	format. This probably represents a flaw in the BIOS' list
>     	encoding procedure.
>     Arg4: fffffadf9ebd94f0, Pointer to the QUERY_RESOURCE_REQUIREMENTS irp

>     Debugging Details:
>     ------------------

>     *** No owner thread found for resource fffff800011dda40
>     *** No owner thread found for resource fffff800011dda40
>     *** No owner thread found for resource fffff800011dda40
>     *** No owner thread found for resource fffff800011dda40

>     ACPI_EXTENSION:  fffffadf9ee95010 -- (!acpikd.acpiext fffffadf9ee95010)

>     ACPI_RESCONFLICT:  0000000000000001 -- (!acpiresconflict 0000000000000001 fffffadf9ebd94f0)
>     Number of arguments found = 1. 2 arguments expected
>     Usage: acpiresconflict  [DeviceExtension] [IoResList] [e820Info]

>     DEFAULT_BUCKET_ID:  DRIVER_FAULT

>     BUGCHECK_STR:  0xA5

>     PROCESS_NAME:  System

>     CURRENT_IRQL:  2

>     LOCK_ADDRESS:  fffff800011ddb40 -- (!locks fffff800011ddb40)

>     Resource @ nt!IopDeviceTreeLock (0xfffff800011ddb40)    Shared 1 owning threads
>          Threads: fffffadf9ee91bf0-01<*>
>     1 total locks, 1 locks currently held

>     PNP_TRIAGE:
>     	Lock address  : 0xfffff800011ddb40
>     	Thread Count  : 1
>     	Thread address: 0xfffffadf9ee91bf0
>     	Thread wait   : 0xa9

>     LAST_CONTROL_TRANSFER:  from fffff800010d673e to fffff80001026db0

>     STACK_TEXT:
>     fffffadf`93607448
>      fffff800`010d673e : 00000000`0000000f 00000000`00000000
>     00000000`00000002 fffff800`0105669e : nt!DbgBreakPointWithStatus
>     fffffadf`93607450
>      fffff800`010d7d0e : fffff800`00000003 00000000`000000a5
>     00000000`00000002 fffffadf`9ee95010 : nt!KiBugCheckDebugBreak+0x1e
>     fffffadf`936074b0
>      fffff800`0102ea54 : fffffadf`92da1040 fffffadf`9ee95010
>     fffffadf`9eeaa210 fffffadf`9eeb1220 : nt!KeBugCheck2+0x640
>     fffffadf`93607af0
>      fffffadf`92dceef6 : 00000000`000000a5 00000000`00000002
>     fffffadf`9ee95010 00000000`00000001 : nt!KeBugCheckEx+0x104
>     fffffadf`93607b30
>      fffffadf`92d6c804 : fffffadf`9ea9d980 fffffadf`9ebd94f0
>     fffffadf`93607c18 fffffadf`92dce2a8 :
>     ACPI!ACPIBusIrpQueryResourceRequirements+0x446
>     fffffadf`93607be0
>     fffff800`0133ed04 : fffffadf`9ea9d980 fffffadf`9ebd94f0
>     fffffadf`9ea9d980 fffffadf`93607d10 : ACPI!ACPIDispatchIrp+0x164
>     fffffadf`93607c70
>      fffff800`01331abb : fffffadf`9eace270 00000000`00000000
>     ffffffff`800001e8 00000000`00000000 : nt!IopSynchronousCall+0x144
>     fffffadf`93607ce0
>      fffff800`01333093 : fffffadf`93607e20 00000000`00000002
>     fffffadf`9eace270 fffffa80`004644f0 :
>     nt!PiQueryResourceRequirements+0x7b
>     fffffadf`93607da0
>     fffff800`0133591b : fffffadf`9eace440 fffffadf`9eace270
>     00000000`00000000 fffffadf`9eace270 : nt!PiProcessNewDeviceNode+0x145e
>     fffffadf`93608140
>      fffff800`010cc809 : fffffadf`9eeb4390 fffff800`00092470
>     fffffadf`9eeb5350 fffffadf`9eeb4390 : nt!PipProcessDevNodeTree+0x223
>     fffffadf`936084d0
>      fffff800`014329f7 : ffffffff`00000000 fffffadf`9eeb4390
>     fffff800`00092470 fffffadf`9eeb5380 : nt!PipDeviceActionWorker+0x199
>     fffffadf`93608560
>      fffff800`0142a14d : 00000000`00000000 00000000`0000fffc
>     00000000`00000000 00000000`0000fffc : nt!IopInitializeBootDrivers+0xc57
>     fffffadf`936088c0
>      fffff800`01428144 : fffff800`00091598 fffff800`00091598
>     00000000`00000003 fffffadf`9ee90010 : nt!IoInitSystem+0xf4f
>     fffffadf`93608a50
>      fffff800`0130dc29 : 12d93b24`1e99bf20 fffffadf`9ee91bf0
>     00000000`00000080 fffffadf`9ee91bf0 :
>     nt!Phase1InitializationDiscard+0x111d
>     fffffadf`93608d40
>     fffff800`0124b972 : b6e6174a`baa6174e 8dd685ea`819685ee
>     307b39e5`3cbb19e1 0b4bab45`070baf41 : nt!Phase1Initialization+0x9
>     fffffadf`93608d70
>      fffff800`010202d6 : fffff800`011b1180 fffffadf`9ee91bf0
>     fffff800`011b5500 00000000`da83b888 : nt!PspSystemThreadStartup+0x3e
>     fffffadf`93608dd0
>      00000000`00000000 : 00000000`00000000 00000000`00000000
>     00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

>     STACK_COMMAND:  kb

>     FOLLOWUP_IP:
>     ACPI!ACPIBusIrpQueryResourceRequirements+446
>     fffffadf`92dceef6 cc              int     3

>     SYMBOL_STACK_INDEX:  4

>     SYMBOL_NAME:  ACPI!ACPIBusIrpQueryResourceRequirements+446

>     FOLLOWUP_NAME:  MachineOwner

>     MODULE_NAME: ACPI

>     IMAGE_NAME:  ACPI.sys

>     DEBUG_FLR_IMAGE_TIMESTAMP:  45d70c6e

>     FAILURE_BUCKET_ID:  X64_0xA5_ACPI!ACPIBusIrpQueryResourceRequirements+446

>     BUCKET_ID:  X64_0xA5_ACPI!ACPIBusIrpQueryResourceRequirements+446

>     Followup: MachineOwner
>     ---------

#2178 | daniel_k | ⇗ @diderius6, please try this, based on 5048 and tell me what happens. I think this is our best bet.
#2179 | diderius6 | ⇗ @daniel_k I just test the 4 acpi.sys from before. They show all the identic BSOD A5 (0x02) Dietmar PS: For acpi.sys for XP SP3 on Ryzen, I just go this hard way, solved one BSOD after the other until to the light:))!

#2180

diderius6

⇗ @daniel_k
With the 5048 acpi.sys on Ryzen board Windbg shows no BSOD,
but the compi hangs in an infinity loop during start,
also in Safe Mode (F8)
Dietmar

>     Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
>     Copyright (c) Microsoft Corporation. All rights reserved.

>     Opened \\.\com1
>     Waiting to reconnect...
>     Connected to Windows Server 2003 3790 x64 target at (Sat Aug 31 18:39:15.984 2019 (UTC + 2:00)), ptr64 TRUE
>     Kernel Debugger connection established.
>     WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
>     Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
>     *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
>     Executable search path is: C:\localsymbols
>     Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64
>     Built by: 3790.srv03_sp2_rtm.070216-1710
>     Machine Name:
>     Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d5100
>     System Uptime: not available
>     AhciHwFindAdapter finishing
>     Break instruction exception - code 80000003 (first chance)
>     *******************************************************************************
>     *                                                                             *
>     *   You are seeing this message because you pressed either                    *
>     *       CTRL+C (if you run kd.exe) or,                                        *
>     *       CTRL+BREAK (if you run WinDBG),                                       *
>     *   on your debugger machine's keyboard.                                      *
>     *                                                                             *
>     *                   THIS IS NOT A BUG OR A SYSTEM CRASH                       *
>     *                                                                             *
>     * If you did not intend to break into the debugger, press the "g" key, then   *
>     * press the "Enter" key now.  This message might immediately reappear.  If it *
>     * does, press "g" and "Enter" again.                                          *
>     *                                                                             *
>     *******************************************************************************
>     nt!DbgBreakPointWithStatus:
>     fffff800`01026db0 cc              int     3
>     0: kd> !analyze -v
>     Connected to Windows Server 2003 3790 x64 target at (Sat Aug 31 18:42:09.015 2019 (UTC + 2:00)), ptr64 TRUE
>     Loading Kernel Symbols
>     ........................
>     Loading User Symbols

>     *******************************************************************************
>     *                                                                             *
>     *                        Bugcheck Analysis                                    *
>     *                                                                             *
>     *******************************************************************************

>     Unknown bugcheck code (0)
>     Unknown bugcheck description
>     Arguments:
>     Arg1: 0000000000000000
>     Arg2: 0000000000000000
>     Arg3: 0000000000000000
>     Arg4: 0000000000000000

>     Debugging Details:
>     ------------------

>     PROCESS_NAME:  Idle

>     FAULTING_IP:
>     nt!DbgBreakPointWithStatus+0
>     fffff800`01026db0 cc              int     3

>     EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
>     ExceptionAddress: fffff80001026db0 (nt!DbgBreakPointWithStatus)
>        ExceptionCode: 80000003 (Break instruction exception)
>       ExceptionFlags: 00000000
>     NumberParameters: 1
>        Parameter[0]: 0000000000000000

>     ERROR_CODE: (NTSTATUS) 0x80000003 - {AUSNAHME}  Haltepunkt  Im Quellprogramm wurde ein Haltepunkt erreicht.

>     EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - Mindestens ein Argument ist ung ltig.

>     EXCEPTION_PARAMETER1:  0000000000000000

>     DEFAULT_BUCKET_ID:  DRIVER_FAULT

>     BUGCHECK_STR:  0x0

>     CURRENT_IRQL:  d

>     STACK_TEXT:
>     fffff800`00069b58
>      fffff800`010791ff : 00000000`00000062 fffff800`010273ae
>     00000000`00000000 00000000`00000000 : nt!DbgBreakPointWithStatus
>     fffff800`00069b60
>      fffff800`010299fb : 00000000`000001d6 00000000`0005ffd4
>     fffff800`011b1180 fffff800`0083f480 : nt!KdCheckForDebugBreak+0xb5
>     fffff800`00069ba0
>      fffff800`010296a0 : 00000000`00004000 00000000`00000000
>     00000000`0002625a fffff800`0083f480 : nt!KeUpdateRunTime+0x19e
>     fffff800`00069bd0
>      fffff800`00814241 : fffff800`011b1180 fffff800`00069cb0
>     fffff800`0083f480 fffff800`0083f480 : nt!KeUpdateSystemTime+0xf0
>     fffff800`00069c00
>      fffff800`0102ff59 : fffff800`011b5dc0 fffff800`0102ff59
>     fffff800`011b1180 fffffadf`9ee91460 : hal!HalpClockInterrupt+0xb1
>     fffff800`00069c30
>      fffff800`0081dbe2 : fffff800`01067cde fffff800`011b1180
>     fffff800`011b1180 fffff800`011b5500 : nt!KiInterruptDispatchNoLock+0x119
>     fffff800`00069dc8
>      fffff800`01067cde : fffff800`011b1180 fffff800`011b1180
>     fffff800`011b5500 fffffadf`9ee91460 : hal!HalProcessorIdle+0x2
>     fffff800`00069dd0
>      fffff800`014151d1 : 00000000`00000000 00000000`00000000
>     00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x1e
>     fffff800`00069e00
>      00000000`fffff800 : 00000000`00000000 00000000`00000000
>     00000000`00000000 00000000`00000000 : nt!KiSystemStartup+0x1bf
>     fffff800`000630b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00680000`00000000 : 0xfffff800

>     STACK_COMMAND:  kb

>     FOLLOWUP_IP:
>     nt!DbgBreakPointWithStatus+0
>     fffff800`01026db0 cc              int     3

>     SYMBOL_STACK_INDEX:  0

>     SYMBOL_NAME:  nt!DbgBreakPointWithStatus+0

>     FOLLOWUP_NAME:  MachineOwner

>     MODULE_NAME: nt

>     IMAGE_NAME:  ntkrnlmp.exe

>     DEBUG_FLR_IMAGE_TIMESTAMP:  45d69ab4

>     BUCKET_ID:  MANUAL_BREAKIN

>     Followup: MachineOwner
>     ---------

>     0: kd> lm
>     start             end                 module name
>     fffff800`00800000
>      fffff800`0085e000   hal        (pdb symbols)
>     c:\symbols\hal.pdb\786A0CD8B0CB4761BA7DC79BD10C215C1\hal.pdb
>     fffff800`01000000
>      fffff800`01490000   nt         (pdb symbols)
>     c:\symbols\ntkrnlmp.pdb\03185083233249D9BB747EA777B80C982\ntkrnlmp.pdb
>     fffffadf`929b2000 fffffadf`929e6000   Mup        (deferred)
>     fffffadf`929e6000 fffffadf`92a4c000   NDIS       (deferred)
>     fffffadf`92a4c000 fffffadf`92b51000   Ntfs       (deferred)
>     fffffadf`92b51000 fffffadf`92b85000   KSecDD     (deferred)
>     fffffadf`92b85000 fffffadf`92ba8000   sr         (deferred)
>     fffffadf`92ba8000 fffffadf`92be6000   fltMgr     (deferred)
>     fffffadf`92be6000 fffffadf`92c03000   CLASSPNP   (deferred)
>     fffffadf`92c03000 fffffadf`92c18000   disk       (deferred)
>     fffffadf`92c18000 fffffadf`92c7b000   storport   (deferred)
>     fffffadf`92c7b000 fffffadf`92cc6000   volsnap    (deferred)
>     fffffadf`92cc6000 fffffadf`92d0d000   dmio       (deferred)
>     fffffadf`92d0d000 fffffadf`92d4d000   ftdisk     (deferred)
>     fffffadf`92d4d000 fffffadf`92d63000   MountMgr   (deferred)
>     fffffadf`92d63000 fffffadf`92d84000   pci        (deferred)
>     fffffadf`92d84000 fffffadf`92df2000   ACPI       (deferred)
>     fffffadf`931fb000 fffffadf`93205000   kdcom      (deferred)
>     fffffadf`9320b000 fffffadf`93214000   BOOTVID    (deferred)
>     fffffadf`9321b000 fffffadf`93224000   WMILIB     (deferred)
>     fffffadf`9322b000 fffffadf`93234000   isapnp     (deferred)
>     fffffadf`9323b000 fffffadf`9324b000   PartMgr    (deferred)
>     fffffadf`9324b000 fffffadf`93259000   storahci   (deferred)
>     fffffadf`9325b000 fffffadf`93266000   crcdisk    (deferred)
>     fffffadf`935fb000 fffffadf`93602000   dmload     (deferred)
>     0: kd> !Devnode 0 1
>     Dumping IopRootDeviceNode (= 0xfffffadf9ebd9620)
>     DevNode 0xfffffadf9ebd9620 for PDO 0xfffffadf9eeb4490
>       InstancePath is "HTREE\ROOT\0"
>       State = DeviceNodeStarted (0x308)
>       Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb3720 for PDO 0xfffffadf9eeb3940
>         InstancePath is "Root\ACPI_HAL\0000"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>         DevNode 0xfffffadf9ebd2490 for PDO 0xfffffadf9eeac060
>           InstancePath is "ACPI_HAL\PNP0C08\0"
>           ServiceName is "ACPI"
>           State = DeviceNodeStarted (0x308)
>           Previous State = DeviceNodeEnumerateCompletion (0x30d)
>           DevNode 0xfffffadf9eab6dd0 for PDO 0xfffffadf9eaca1b0
>             InstancePath is "ACPI\PNP0C14\AWW"
>             ServiceName is "WmiAcpi"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>           DevNode 0xfffffadf9e5150a0 for PDO 0xfffffadf9eabc1b0
>             InstancePath is "ACPI\PNP0A08\0"
>             ServiceName is "pci"
>             State = DeviceNodeStarted (0x308)
>             Previous State = DeviceNodeEnumerateCompletion (0x30d)
>             DevNode 0xfffffadf9eea9840 for PDO 0xfffffadf9dfccd40
>               InstancePath is "PCI\VEN_1022&DEV_1450&SUBSYS_00000000&REV_00\3&11583659&0&00"
>               State = DeviceNodeStarted (0x308)
>               Previous State = DeviceNodeEnumerateCompletion (0x30d)
>             DevNode 0xfffffadf9eea9670 for PDO 0xfffffadf9dfcca20
>               InstancePath is "PCI\VEN_1022&DEV_1451&SUBSYS_87471043&REV_00\3&11583659&0&02"
>               State = DeviceNodeInitialized (0x302)
>               Previous State = DeviceNodeUninitialized (0x301)
>               Problem = CM_PROB_NOT_CONFIGURED
>             DevNode 0xfffffadf9eea94a0 for PDO 0xfffffadf9dfcc700
>               InstancePath is "PCI\VEN_1022&DEV_1452&SUBSYS_00000000&REV_00\3&11583659&0&08"
>               State = DeviceNodeStarted (0x308)
>               Previous State = DeviceNodeEnumerateCompletion (0x30d)
>             DevNode 0xfffffadf9eea92d0 for PDO 0xfffffadf9dfcc3e0
>               InstancePath is "PCI\VEN_1022&DEV_1453&SUBSYS_00000000&REV_00\3&11583659&0&0A"
>               ServiceName is "pci"
>               State = DeviceNodeStarted (0x308)
>               Previous State = DeviceNodeEnumerateCompletion (0x30d)
>               DevNode 0xfffffadf9e3d2530 for PDO 0xfffffadf9eab4720
>                 InstancePath is "PCI\VEN_1022&DEV_57AD&SUBSYS_00000000&REV_00\4&d487977&0&000A"
>                 ServiceName is "pci"
>                 State = DeviceNodeStarted (0x308)
>                 Previous State = DeviceNodeEnumerateCompletion (0x30d)
>                 DevNode 0xfffffadf9e0cae40 for PDO 0xfffffadf9e0ca860
>                   InstancePath is "PCI\VEN_1022&DEV_57A3&SUBSYS_00000000&REV_00\5&1f331b67&0&28000A"
>                   ServiceName is "pci"
>                   State = DeviceNodeStarted (0x308)
>                   Previous State = DeviceNodeEnumerateCompletion (0x30d)
>                   DevNode 0xfffffadf9dfcbaa0 for PDO 0xfffffadf9e2c2a30
>                     InstancePath is "PCI\VEN_8086&DEV_1539&SUBSYS_85F01043&REV_03\6&12f3bd8&0&0028000A"
>                     State = DeviceNodeInitialized (0x302)
>                     Previous State = DeviceNodeUninitialized (0x301)
>                     Problem = CM_PROB_NOT_CONFIGURED
>                 DevNode 0xfffffadf9dfcb010 for PDO 0xfffffadf9e0ca540
>                   InstancePath is "PCI\VEN_1022&DEV_57A4&SUBSYS_00000000&REV_00\5&1f331b67&0&40000A"
>                   ServiceName is "pci"
>                   State = DeviceNodeStarted (0x308)
>                   Previous State = DeviceNodeEnumerateCompletion (0x30d)
>                   DevNode 0xfffffadf9eab5e40 for PDO 0xfffffadf9e1bdd40
>                     InstancePath is "PCI\VEN_1022&DEV_1485&SUBSYS_87471043&REV_00\6&28ecf81d&0&0040000A"
>                     State = DeviceNodeInitialized (0x302)
>                     Previous State = DeviceNodeUninitialized (0x301)
>                     Problem = CM_PROB_NOT_CONFIGURED
>                   DevNode 0xfffffadf9eab5c70 for PDO 0xfffffadf9e1bd820
>                     InstancePath is "PCI\VEN_1022&DEV_149C&SUBSYS_87471043&REV_00\6&28ecf81d&0&0140000A"
>                     State = DeviceNodeInitialized (0x302)
>                     Previous State = DeviceNodeUninitialized (0x301)
>                     Problem = CM_PROB_NOT_CONFIGURED
>                   DevNode 0xfffffadf9eab5aa0 for PDO 0xfffffadf9df2b700
>                     InstancePath is "PCI\VEN_1022&DEV_149C&SUBSYS_148C1022&REV_00\6&28ecf81d&0&0340000A"
>                     State = DeviceNodeInitialized (0x302)
>                     Previous State = DeviceNodeUninitialized (0x301)
>                     Problem = CM_PROB_NOT_CONFIGURED
>                 DevNode 0xfffffadf9dfcbe40 for PDO 0xfffffadf9df2b060
>                   InstancePath is "PCI\VEN_1022&DEV_57A4&SUBSYS_00000000&REV_00\5&1f331b67&0&48000A"
>                   ServiceName is "pci"
>                   State = DeviceNodeStarted (0x308)
>                   Previous State = DeviceNodeEnumerateCompletion (0x30d)
>                   DevNode 0xfffffadf9df2c9a0 for PDO 0xfffffadf9df2cd40
>                     InstancePath is "PCI\VEN_1022&DEV_7901&SUBSYS_79011022&REV_51\6&39625884&0&0048000A"
>                     ServiceName is "storahci"
>                     State = DeviceNodeStarted (0x308)
>                     Previous State = DeviceNodeStartPostWork (0x307)
>                 DevNode 0xfffffadf9dfcbc70 for PDO 0xfffffadf9df2bd40
>                   InstancePath is "PCI\VEN_1022&DEV_57A4&SUBSYS_00000000&REV_00\5&1f331b67&0&50000A"
>                   ServiceName is "pci"
>                   State = DeviceNodeStarted (0x308)
>                   Previous State = DeviceNodeEnumerateCompletion (0x30d)
>                   DevNode 0xfffffadf9df2c330 for PDO 0xfffffadf9df2c6d0
>                     InstancePath is "PCI\VEN_1022&DEV_7901&SUBSYS_79011022&REV_51\6&15d2f925&0&0050000A"
>                     ServiceName is "storahci"
>                     State = DeviceNodeDriversAdded (0x303)
>                     Previous State = DeviceNodeInitialized (0x302)
>             DevNode 0xfffffadf9efea010 for PDO 0xfffffadf9e2c3060
>               InstancePath is "PCI\VEN_1022&DEV_1452&SUBSYS_00000000&REV_00\3&11583659&0&10"
>               State = DeviceNodeStarted (0x308)
>               Previous State = DeviceNodeEnumerateCompletion (0x30d)
>             DevNode 0xfffffadf9efeae40 for PDO 0xfffffadf9e2c3d40
>               InstancePath is "PCI\VEN_1022&DEV_1452&SUBSYS_00000000&REV_00\3&11583659&0&18"
>               State = DeviceNodeStarted (0x308)
>               Previous State = DeviceNodeEnumerateCompletion (0x30d)
>             DevNode 0xfffffadf9efeac70 for PDO 0xfffffadf9e2c3a20
>               InstancePath is "PCI\VEN_1022&DEV_1453&SUBSYS_00000000&REV_00\3&11583659&0&19"
>               ServiceName is "pci"
>               State = DeviceNodeStarted (0x308)
>               Previous State = DeviceNodeEnumerateCompletion (0x30d)
>               DevNode 0xfffffadf9e513620 for PDO 0xfffffadf9e513060
>                 InstancePath is "PCI\VEN_10DE&DEV_1287&SUBSYS_730B19DA&REV_A1\4&2c517c28&0&0019"
>                 State = DeviceNodeInitialized (0x302)
>                 Previous State = DeviceNodeUninitialized (0x301)
>                 Problem = CM_PROB_NOT_CONFIGURED
>               DevNode 0xfffffadf9e513450 for PDO 0xfffffadf9e513bc0
>                 InstancePath is "PCI\VEN_10DE&DEV_0E0F&SUBSYS_730B19DA&REV_A1\4&2c517c28&0&0119"
>                 ServiceName is "HDAudBus"
>                 State = DeviceNodeInitialized (0x302)
>                 Previous State = DeviceNodeUninitialized (0x301)
>             DevNode 0xfffffadf9efeaaa0 for PDO 0xfffffadf9e2c3700
>               InstancePath is "PCI\VEN_1022&DEV_1452&SUBSYS_00000000&REV_00\3&11583659&0&20"
>               State = DeviceNodeStarted (0x308)
>               Previous State = DeviceNodeEnumerateCompletion (0x30d)
>             DevNode 0xfffffadf9efea8d0 for PDO 0xfffffadf9e2c33e0
>               InstancePath is "PCI\VEN_1022&DEV_1452&SUBSYS_00000000&REV_00\3&11583659&0&38"
>               State = DeviceNodeStarted (0x308)
>               Previous State = DeviceNodeEnumerateCompletion (0x30d)
>             DevNode 0xfffffadf9efea700 for PDO 0xfffffadf9e514060
>               InstancePath is "PCI\VEN_1022&DEV_1454&SUBSYS_00000000&REV_00\3&11583659&0&39"
>               ServiceName is "pci"
>               State = DeviceNodeDriversAdded (0x303)
>               Previous State = DeviceNodeInitialized (0x302)
>               Problem = CM_PROB_NORMAL_CONFLICT
>             DevNode 0xfffffadf9efea530 for PDO 0xfffffadf9e514d40
>               InstancePath is "PCI\VEN_1022&DEV_1452&SUBSYS_00000000&REV_00\3&11583659&0&40"
>               State = DeviceNodeStarted (0x308)
>               Previous State = DeviceNodeEnumerateCompletion (0x30d)
>             DevNode 0xfffffadf9efea360 for PDO 0xfffffadf9e514a20
>               InstancePath is "PCI\VEN_1022&DEV_1454&SUBSYS_00000000&REV_00\3&11583659&0&41"
>               ServiceName is "pci"
>               State = DeviceNodeDriversAdded (0x303)
>               Previous State = DeviceNodeInitialized (0x302)
>               Problem = CM_PROB_NORMAL_CONFLICT
>             DevNode 0xfffffadf9efd7010 for PDO 0xfffffadf9e514700
>               InstancePath is "PCI\VEN_1022&DEV_790B&SUBSYS_87471043&REV_59\3&11583659&0&A0"
>               State = DeviceNodeInitialized (0x302)
>               Previous State = DeviceNodeUninitialized (0x301)
>               Problem = CM_PROB_NOT_CONFIGURED
>             DevNode 0xfffffadf9efd7e40 for PDO 0xfffffadf9e5143e0
>               InstancePath is "PCI\VEN_1022&DEV_790E&SUBSYS_00000000&REV_51\3&11583659&0&A3"
>               ServiceName is "isapnp"
>               State = DeviceNodeStarted (0x308)
>               Previous State = DeviceNodeEnumerateCompletion (0x30d)
>               DevNode 0xfffffadf9e291c40 for PDO 0xfffffadf9e12be60
>                 InstancePath is "ACPI\PNP0000\4&28d859f2&0"
>                 State = DeviceNodeInitialized (0x302)
>                 Previous State = DeviceNodeUninitialized (0x301)
>                 Problem = CM_PROB_NOT_CONFIGURED
>               DevNode 0xfffffadf9e291a70 for PDO 0xfffffadf9e12bc60
>                 InstancePath is "ACPI\PNP0200\4&28d859f2&0"
>                 State = DeviceNodeInitialized (0x302)
>                 Previous State = DeviceNodeUninitialized (0x301)
>                 Problem = CM_PROB_NOT_CONFIGURED
>               DevNode 0xfffffadf9e2918a0 for PDO 0xfffffadf9e12ba60
>                 InstancePath is "ACPI\PNP0100\4&28d859f2&0"
>                 State = DeviceNodeInitialized (0x302)
>                 Previous State = DeviceNodeUninitialized (0x301)
>                 Problem = CM_PROB_NOT_CONFIGURED
>               DevNode 0xfffffadf9e2916d0 for PDO 0xfffffadf9e12b860
>                 InstancePath is "ACPI\PNP0B00\4&28d859f2&0"
>                 State = DeviceNodeStarted (0x308)
>                 Previous State = DeviceNodeEnumerateCompletion (0x30d)
>               DevNode 0xfffffadf9e291500 for PDO 0xfffffadf9e12b660
>                 InstancePath is "ACPI\PNP0800\4&28d859f2&0"
>                 State = DeviceNodeInitialized (0x302)
>                 Previous State = DeviceNodeUninitialized (0x301)
>                 Problem = CM_PROB_NOT_CONFIGURED
>               DevNode 0xfffffadf9e291330 for PDO 0xfffffadf9e12b460
>                 InstancePath is "ACPI\PNP0C02\0"
>                 State = DeviceNodeInitialized (0x302)
>                 Previous State = DeviceNodeUninitialized (0x301)
>               DevNode 0xfffffadf9e1bc010 for PDO 0xfffffadf9e291060
>                 InstancePath is "ACPI\PNP0303\0"
>                 ServiceName is "i8042prt"
>                 State = DeviceNodeInitialized (0x302)
>                 Previous State = DeviceNodeUninitialized (0x301)
>               DevNode 0xfffffadf9e1bce40 for PDO 0xfffffadf9e291e60
>                 InstancePath is "ACPI\PNP0C09\4&28d859f2&0"
>                 State = DeviceNodeStarted (0x308)
>                 Previous State = DeviceNodeEnumerateCompletion (0x30d)
>             DevNode 0xfffffadf9efd7c70 for PDO 0xfffffadf9e12c060
>               InstancePath is "PCI\VEN_1022&DEV_1460&SUBSYS_00000000&REV_00\3&11583659&0&C0"
>               State = DeviceNodeStarted (0x308)
>               Previous State = DeviceNodeEnumerateCompletion (0x30d)
>             DevNode 0xfffffadf9efd7aa0 for PDO 0xfffffadf9e12cd40
>               InstancePath is "PCI\VEN_1022&DEV_1461&SUBSYS_00000000&REV_00\3&11583659&0&C1"
>               State = DeviceNodeStarted (0x308)
>               Previous State = DeviceNodeEnumerateCompletion (0x30d)
>             DevNode 0xfffffadf9efd78d0 for PDO 0xfffffadf9e12ca20
>               InstancePath is "PCI\VEN_1022&DEV_1462&SUBSYS_00000000&REV_00\3&11583659&0&C2"
>               State = DeviceNodeStarted (0x308)
>               Previous State = DeviceNodeEnumerateCompletion (0x30d)
>             DevNode 0xfffffadf9efd7700 for PDO 0xfffffadf9e12c700
>               InstancePath is "PCI\VEN_1022&DEV_1463&SUBSYS_00000000&REV_00\3&11583659&0&C3"
>               State = DeviceNodeStarted (0x308)
>               Previous State = DeviceNodeEnumerateCompletion (0x30d)
>             DevNode 0xfffffadf9efd7530 for PDO 0xfffffadf9e12c3e0
>               InstancePath is "PCI\VEN_1022&DEV_1464&SUBSYS_00000000&REV_00\3&11583659&0&C4"
>               State = DeviceNodeStarted (0x308)
>               Previous State = DeviceNodeEnumerateCompletion (0x30d)
>             DevNode 0xfffffadf9efd7360 for PDO 0xfffffadf9e292060
>               InstancePath is "PCI\VEN_1022&DEV_1465&SUBSYS_00000000&REV_00\3&11583659&0&C5"
>               State = DeviceNodeStarted (0x308)
>               Previous State = DeviceNodeEnumerateCompletion (0x30d)
>             DevNode 0xfffffadf9e3d2010 for PDO 0xfffffadf9e292d40
>               InstancePath is "PCI\VEN_1022&DEV_1466&SUBSYS_00000000&REV_00\3&11583659&0&C6"
>               State = DeviceNodeStarted (0x308)
>               Previous State = DeviceNodeEnumerateCompletion (0x30d)
>             DevNode 0xfffffadf9e3d2e40 for PDO 0xfffffadf9e292a20
>               InstancePath is "PCI\VEN_1022&DEV_1467&SUBSYS_00000000&REV_00\3&11583659&0&C7"
>               State = DeviceNodeStarted (0x308)
>               Previous State = DeviceNodeEnumerateCompletion (0x30d)
>             DevNode 0xfffffadf9e3d2c70 for PDO 0xfffffadf9e292820
>               InstancePath is "ACPI\PNP0C01\c8"
>               State = DeviceNodeInitialized (0x302)
>               Previous State = DeviceNodeUninitialized (0x301)
>               Problem = CM_PROB_NOT_CONFIGURED
>             DevNode 0xfffffadf9e3d2aa0 for PDO 0xfffffadf9e292620
>               InstancePath is "ACPI\PNP0C02\15"
>               State = DeviceNodeInitialized (0x302)
>               Previous State = DeviceNodeUninitialized (0x301)
>               Problem = CM_PROB_NOT_CONFIGURED
>             DevNode 0xfffffadf9e3d28d0 for PDO 0xfffffadf9e292420
>               InstancePath is "ACPI\PNP0C02\700"
>               State = DeviceNodeInitialized (0x302)
>               Previous State = DeviceNodeUninitialized (0x301)
>               Problem = CM_PROB_NOT_CONFIGURED
>             DevNode 0xfffffadf9e3d2700 for PDO 0xfffffadf9e1bd060
>               InstancePath is "ACPI\PNP0C14\MXM2"
>               ServiceName is "WmiAcpi"
>               State = DeviceNodeInitialized (0x302)
>               Previous State = DeviceNodeUninitialized (0x301)
>           DevNode 0xfffffadf9eeb3e40 for PDO 0xfffffadf9ee991b0
>             InstancePath is "ACPI\PNP0C0C\aa"
>             State = DeviceNodeStarted (0x308)
>             Previous State = DeviceNodeEnumerateCompletion (0x30d)
>           DevNode 0xfffffadf9eac0190 for PDO 0xfffffadf9e2a3620
>             InstancePath is "ACPI\PNP0103\2&daba3ff&0"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9eac5190 for PDO 0xfffffadf9ebd1460
>             InstancePath is "ACPI\AMDI0030\0"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9e12d750 for PDO 0xfffffadf9ebd99f0
>             InstancePath is "ACPI\PNP0C14\ASUSWMI"
>             ServiceName is "WmiAcpi"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>           DevNode 0xfffffadf9eaba340 for PDO 0xfffffadf9eeab560
>             InstancePath is "ACPI\FixedButton\2&daba3ff&0"
>             State = DeviceNodeStarted (0x308)
>             Previous State = DeviceNodeEnumerateCompletion (0x30d)
>           DevNode 0xfffffadf9e1be700 for PDO 0xfffffadf9e515e60
>             InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_0"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9ebd1680 for PDO 0xfffffadf9e1bf620
>             InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_1"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9e1be0e0 for PDO 0xfffffadf9e1bf420
>             InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_2"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9efd9e40 for PDO 0xfffffadf9e12d450
>             InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_3"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9efd9c70 for PDO 0xfffffadf9e12d250
>             InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_4"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9efd9aa0 for PDO 0xfffffadf9ebd1e60
>             InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_5"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9efd98d0 for PDO 0xfffffadf9ebd1c60
>             InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_6"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9efd9700 for PDO 0xfffffadf9ebd1a60
>             InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_7"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9efd9530 for PDO 0xfffffadf9eab7620
>             InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_8"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9efd9360 for PDO 0xfffffadf9eab7420
>             InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_9"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9efda010 for PDO 0xfffffadf9eab7220
>             InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\10"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9efdae40 for PDO 0xfffffadf9e3d4e60
>             InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\11"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9efdac70 for PDO 0xfffffadf9e3d4c60
>             InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\12"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9efdaaa0 for PDO 0xfffffadf9e3d4a60
>             InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\13"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9efda8d0 for PDO 0xfffffadf9e3d4860
>             InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\14"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9efda700 for PDO 0xfffffadf9e3d4660
>             InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\15"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9efda530 for PDO 0xfffffadf9e3d4460
>             InstancePath is "ACPI\PNP0C02\90"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9efda360 for PDO 0xfffffadf9e3d4260
>             InstancePath is "ACPI\PNP0C02\91"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9efd8010 for PDO 0xfffffadf9efd9060
>             InstancePath is "ACPI\PNP0C14\AOD"
>             ServiceName is "WmiAcpi"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd8e40 for PDO 0xfffffadf9ebd8060
>         InstancePath is "Root\dmio\0000"
>         ServiceName is "dmio"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd8a60 for PDO 0xfffffadf9ebd8c80
>         InstancePath is "Root\ftdisk\0000"
>         ServiceName is "ftdisk"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd8680 for PDO 0xfffffadf9ebd88a0
>         InstancePath is "Root\LEGACY_AFD\0000"
>         ServiceName is "AFD"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd82a0 for PDO 0xfffffadf9ebd84c0
>         InstancePath is "Root\LEGACY_AMPA\0000"
>         ServiceName is "ampa"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb2e40 for PDO 0xfffffadf9eeb2060
>         InstancePath is "Root\LEGACY_BEEP\0000"
>         ServiceName is "Beep"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb2a60 for PDO 0xfffffadf9eeb2c80
>         InstancePath is "Root\LEGACY_CDAC15BA\0000"
>         ServiceName is "CdaC15BA"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb2680 for PDO 0xfffffadf9eeb28a0
>         InstancePath is "Root\LEGACY_CDAD10BA\0000"
>         ServiceName is "CdaD10BA"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb22a0 for PDO 0xfffffadf9eeb24c0
>         InstancePath is "Root\LEGACY_CRCDISK\0000"
>         ServiceName is "crcdisk"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd7e40 for PDO 0xfffffadf9ebd7060
>         InstancePath is "Root\LEGACY_DMBOOT\0000"
>         ServiceName is "dmboot"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd7a60 for PDO 0xfffffadf9ebd7c80
>         InstancePath is "Root\LEGACY_DMLOAD\0000"
>         ServiceName is "dmload"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd7680 for PDO 0xfffffadf9ebd78a0
>         InstancePath is "Root\LEGACY_FIPS\0000"
>         ServiceName is "Fips"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd72a0 for PDO 0xfffffadf9ebd74c0
>         InstancePath is "Root\LEGACY_GPC\0000"
>         ServiceName is "Gpc"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb1e40 for PDO 0xfffffadf9eeb1060
>         InstancePath is "Root\LEGACY_HTTP\0000"
>         ServiceName is "HTTP"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb1a60 for PDO 0xfffffadf9eeb1c80
>         InstancePath is "Root\LEGACY_IPNAT\0000"
>         ServiceName is "IpNat"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb1680 for PDO 0xfffffadf9eeb18a0
>         InstancePath is "Root\LEGACY_IPSEC\0000"
>         ServiceName is "IPSec"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb12a0 for PDO 0xfffffadf9eeb14c0
>         InstancePath is "Root\LEGACY_KSECDD\0000"
>         ServiceName is "ksecdd"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd6e40 for PDO 0xfffffadf9ebd6060
>         InstancePath is "Root\LEGACY_MNMDD\0000"
>         ServiceName is "mnmdd"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd6a60 for PDO 0xfffffadf9ebd6c80
>         InstancePath is "Root\LEGACY_MOUNTMGR\0000"
>         ServiceName is "mountmgr"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd6680 for PDO 0xfffffadf9ebd68a0
>         InstancePath is "Root\LEGACY_NDIS\0000"
>         ServiceName is "NDIS"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd62a0 for PDO 0xfffffadf9ebd64c0
>         InstancePath is "Root\LEGACY_NDISTAPI\0000"
>         ServiceName is "NdisTapi"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb0e40 for PDO 0xfffffadf9eeb0060
>         InstancePath is "Root\LEGACY_NDISUIO\0000"
>         ServiceName is "Ndisuio"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb0a60 for PDO 0xfffffadf9eeb0c80
>         InstancePath is "Root\LEGACY_NDPROXY\0000"
>         ServiceName is "NDProxy"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb0680 for PDO 0xfffffadf9eeb08a0
>         InstancePath is "Root\LEGACY_NETBT\0000"
>         ServiceName is "NetBT"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb02a0 for PDO 0xfffffadf9eeb04c0
>         InstancePath is "Root\LEGACY_NULL\0000"
>         ServiceName is "Null"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd5e40 for PDO 0xfffffadf9ebd5060
>         InstancePath is "Root\LEGACY_PARTMGR\0000"
>         ServiceName is "PartMgr"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd5a60 for PDO 0xfffffadf9ebd5c80
>         InstancePath is "Root\LEGACY_RASACD\0000"
>         ServiceName is "RasAcd"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd5680 for PDO 0xfffffadf9ebd58a0
>         InstancePath is "Root\LEGACY_RDPCDD\0000"
>         ServiceName is "RDPCDD"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd52a0 for PDO 0xfffffadf9ebd54c0
>         InstancePath is "Root\LEGACY_SECDRV\0000"
>         ServiceName is "Secdrv"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeafe40 for PDO 0xfffffadf9eeaf060
>         InstancePath is "Root\LEGACY_TCPIP\0000"
>         ServiceName is "Tcpip"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeafa60 for PDO 0xfffffadf9eeafc80
>         InstancePath is "Root\LEGACY_VGASAVE\0000"
>         ServiceName is "VgaSave"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeaf680 for PDO 0xfffffadf9eeaf8a0
>         InstancePath is "Root\LEGACY_VOLSNAP\0000"
>         ServiceName is "VolSnap"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeaf2a0 for PDO 0xfffffadf9eeaf4c0
>         InstancePath is "Root\LEGACY_WANARP\0000"
>         ServiceName is "Wanarp"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd4e40 for PDO 0xfffffadf9ebd4060
>         InstancePath is "Root\MEDIA\MS_MMACM"
>         ServiceName is "audstub"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd4a60 for PDO 0xfffffadf9ebd4c80
>         InstancePath is "Root\MEDIA\MS_MMDRV"
>         ServiceName is "audstub"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd4680 for PDO 0xfffffadf9ebd48a0
>         InstancePath is "Root\MEDIA\MS_MMMCI"
>         ServiceName is "audstub"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd42a0 for PDO 0xfffffadf9ebd44c0
>         InstancePath is "Root\MEDIA\MS_MMVCD"
>         ServiceName is "audstub"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9eeaee40 for PDO 0xfffffadf9eeae060
>         InstancePath is "Root\MEDIA\MS_MMVID"
>         ServiceName is "audstub"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9eeaea60 for PDO 0xfffffadf9eeaec80
>         InstancePath is "Root\MS_L2TPMINIPORT\0000"
>         ServiceName is "Rasl2tp"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9eeae680 for PDO 0xfffffadf9eeae8a0
>         InstancePath is "Root\MS_NDISWANIP\0000"
>         ServiceName is "NdisWan"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9eeae2a0 for PDO 0xfffffadf9eeae4c0
>         InstancePath is "Root\MS_PPPOEMINIPORT\0000"
>         ServiceName is "RasPppoe"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd3e40 for PDO 0xfffffadf9ebd3060
>         InstancePath is "Root\MS_PPTPMINIPORT\0000"
>         ServiceName is "PptpMiniport"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd3a60 for PDO 0xfffffadf9ebd3c80
>         InstancePath is "Root\MS_PSCHEDMP\0000"
>         ServiceName is "PSched"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd3680 for PDO 0xfffffadf9ebd38a0
>         InstancePath is "Root\MS_PSCHEDMP\0001"
>         ServiceName is "PSched"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd32a0 for PDO 0xfffffadf9ebd34c0
>         InstancePath is "Root\MS_PTIMINIPORT\0000"
>         ServiceName is "Raspti"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9eeade40 for PDO 0xfffffadf9eead060
>         InstancePath is "Root\RDPDR\0000"
>         ServiceName is "rdpdr"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9eeada60 for PDO 0xfffffadf9eeadc80
>         InstancePath is "Root\RDP_KBD\0000"
>         ServiceName is "TermDD"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9eead680 for PDO 0xfffffadf9eead8a0
>         InstancePath is "Root\RDP_MOU\0000"
>         ServiceName is "TermDD"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9eead2a0 for PDO 0xfffffadf9eead4c0
>         InstancePath is "Root\SYSTEM\0000"
>         ServiceName is "swenum"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd2e40 for PDO 0xfffffadf9ebd2060
>         InstancePath is "Root\SYSTEM\0001"
>         ServiceName is "update"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd2a60 for PDO 0xfffffadf9ebd2c80
>         InstancePath is "Root\SYSTEM\0002"
>         ServiceName is "mssmbios"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)

#2181 | daniel_k | ⇗ @diderius6, from the debugger output, we're almost there! Try these 3 test files.

#2182

diderius6

daniel_k
acpi_test1.sys
The pointer which points to low memory is very similar to the behavior of acpi.sys from XP SP3
Dietmar

>     Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
>     Copyright (c) Microsoft Corporation. All rights reserved.

>     Opened \\.\com1
>     Waiting to reconnect...
>     Connected to Windows Server 2003 3790 x64 target at (Sat Aug 31 20:47:12.921 2019 (UTC + 2:00)), ptr64 TRUE
>     Kernel Debugger connection established.
>     WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
>     Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
>     *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
>     Executable search path is: C:\localsymbols
>     Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64
>     Built by: 3790.srv03_sp2_rtm.070216-1710
>     Machine Name:
>     Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d5100
>     System Uptime: not available

>     *** Fatal System Error: 0x0000007e
>                            (0xFFFFFFFFC0000005,0xFFFFFADF92D9D923,0xFFFFFADF93607540,0xFFFFFADF93606F50)

>     Break instruction exception - code 80000003 (first chance)

>     A fatal system error has occurred.
>     Debugger entered on first try; Bugcheck callbacks have not been invoked.

>     A fatal system error has occurred.

>     Connected to Windows Server 2003 3790 x64 target at (Sat Aug 31 20:47:25.703 2019 (UTC + 2:00)), ptr64 TRUE
>     Loading Kernel Symbols
>     ........................
>     Loading User Symbols

>     *******************************************************************************
>     *                                                                             *
>     *                        Bugcheck Analysis                                    *
>     *                                                                             *
>     *******************************************************************************

>     Use !analyze -v to get detailed debugging information.

>     BugCheck 7E, {ffffffffc0000005, fffffadf92d9d923, fffffadf93607540, fffffadf93606f50}

>     *** ERROR: Module load completed but symbols could not be loaded for ACPI.sys
>     *** No owner thread found for resource fffff800011dda40
>     *** No owner thread found for resource fffff800011dda40
>     *** No owner thread found for resource fffff800011dda40
>     *** No owner thread found for resource fffff800011dda40
>     Probably caused by : ACPI.sys ( ACPI+19923 )

>     Followup: MachineOwner
>     ---------

>     nt!DbgBreakPointWithStatus:
>     fffff800`01026db0 cc              int     3
>     15: kd> !analyze -v
>     *******************************************************************************
>     *                                                                             *
>     *                        Bugcheck Analysis                                    *
>     *                                                                             *
>     *******************************************************************************

>     SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
>     This is a very common bugcheck.  Usually the exception address pinpoints
>     the driver/function that caused the problem.  Always note this address
>     as well as the link date of the driver/image that contains this address.
>     Arguments:
>     Arg1: ffffffffc0000005, The exception code that was not handled
>     Arg2: fffffadf92d9d923, The address that the exception occurred at
>     Arg3: fffffadf93607540, Exception Record Address
>     Arg4: fffffadf93606f50, Context Record Address

>     Debugging Details:
>     ------------------

>     *** No owner thread found for resource fffff800011dda40
>     *** No owner thread found for resource fffff800011dda40
>     *** No owner thread found for resource fffff800011dda40
>     *** No owner thread found for resource fffff800011dda40

>     EXCEPTION_CODE:
>      (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher
>     bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x"
>     nicht in den Arbeitsspeicher  bertragen.

>     FAULTING_IP:
>     ACPI+19923
>     fffffadf`92d9d923 41ff5620        call    qword ptr [r14+20h]

>     EXCEPTION_RECORD:  fffffadf93607540 -- (.exr 0xfffffadf93607540)
>     ExceptionAddress: fffffadf92d9d923 (ACPI+0x0000000000019923)
>        ExceptionCode: c0000005 (Access violation)
>       ExceptionFlags: 00000000
>     NumberParameters: 2
>        Parameter[0]: 0000000000000000
>        Parameter[1]: 0000000000000020
>     Attempt to read from address 0000000000000020

>     CONTEXT:  fffffadf93606f50 -- (.cxr 0xfffffadf93606f50)
>     rax=fffffadf936077b0 rbx=fffffadf92dd3b40 rcx=fffffadf9eabd1b0
>     rdx=fffffadf936077d0 rsi=0000000000000000 rdi=0000000000000000
>     rip=fffffadf92d9d923 rsp=fffffadf93607760 rbp=fffffadf9eabd1b0
>      r8=fffffadf936077b4  r9=fffffadf936077b3 r10=0000000000000001
>     r11=fffffadf936079a8 r12=fffffadf936079f0 r13=fffffadf92dd3b00
>     r14=0000000000000000 r15=fffffadf936079f8
>     iopl=0         nv up ei pl zr na po nc
>     cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
>     ACPI+0x19923:
>     fffffadf`92d9d923 41ff5620        call    qword ptr [r14+20h] ds:002b:00000000`00000020=????????????????
>     Resetting default scope

>     PROCESS_NAME:  System

>     CURRENT_IRQL:  2

>     ERROR_CODE:
>      (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher
>     bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x"
>     nicht in den Arbeitsspeicher  bertragen.

>     EXCEPTION_PARAMETER1:  0000000000000000

>     EXCEPTION_PARAMETER2:  0000000000000020

>     READ_ADDRESS:  0000000000000020

>     FOLLOWUP_IP:
>     ACPI+19923
>     fffffadf`92d9d923 41ff5620        call    qword ptr [r14+20h]

>     BUGCHECK_STR:  0x7E

>     DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

>     LOCK_ADDRESS:  fffff800011ddb40 -- (!locks fffff800011ddb40)

>     Resource @ nt!IopDeviceTreeLock (0xfffff800011ddb40)    Shared 1 owning threads
>          Threads: fffffadf9ee91bf0-01<*>
>     1 total locks, 1 locks currently held

>     PNP_TRIAGE:
>     	Lock address  : 0xfffff800011ddb40
>     	Thread Count  : 1
>     	Thread address: 0xfffffadf9ee91bf0
>     	Thread wait   : 0xab

>     LAST_CONTROL_TRANSFER:  from fffff800010d673e to fffff80001026db0

>     STACK_TEXT:
>     fffffadf`93607760 fffffadf`92ddec12 : 00000000`00000001 fffff800`0137de62 fffffadf`00000101 fffff800`0137eb82 : ACPI+0x19923
>     fffffadf`936079b0 fffffadf`92de8136 : fffffadf`92dd3b40 fffffadf`93607bb0 fffffa80`00421708 fffffadf`93607bb0 : ACPI+0x5ac12
>     fffffadf`93607a30 fffffadf`92ddf2b2 : fffffadf`92dd3b40 fffffa80`00478370 00000000`00000009 fffffadf`93607bb0 : ACPI+0x64136
>     fffffadf`93607b10 fffffadf`92de826f : 00000000`00000000 fffffa80`00478370 00000000`00000009 00000000`00000000 : ACPI+0x5b2b2
>     fffffadf`93607b40 fffff800`01330d16 : fffffa80`004216e0 fffffa80`00473378 fffffa80`00473350 fffffadf`93607ba0 : ACPI+0x6426f
>     fffffadf`93607b80
>      fffff800`01330b03 : 00000000`00000000 fffffa80`00478370
>     fffffa80`00421680 fffffadf`9e1be130 : nt!IopBootAllocation+0x14b
>     fffffadf`93607be0
>      fffff800`01330a07 : fffffa80`004701e0 fffffadf`9eabd1b0
>     00000000`00000004 fffffadf`9eabd1b0 :
>     nt!IopAllocateBootResourcesInternal+0x93
>     fffffadf`93607c70
>     fffff800`014303ab : 00000000`00000010 fffffadf`9e1be130
>     fffffa80`004701e0 00000000`00000004 : nt!IopAllocateBootResources+0x57
>     fffffadf`93607cb0
>      fffff800`013319e6 : 00000000`00000000 ffffffff`800001d8
>     fffffadf`9e1be130 fffffa80`004701e0 : nt!IopReportBootResources+0xc1
>     fffffadf`93607ce0
>      fffff800`01333334 : ffffffff`800001e4 fffffadf`9e1be1f0
>     fffffadf`9e1be130 ffffffff`800001e4 :
>     nt!PiQueryAndAllocateBootResources+0x276
>     fffffadf`93607da0
>     fffff800`0133591b : fffffadf`9eacb190 fffffadf`9e1be130
>     00000000`00000000 fffffadf`9e1be130 : nt!PiProcessNewDeviceNode+0x16ff
>     fffffadf`93608140
>      fffff800`010cc809 : fffffadf`9eeb4370 fffff800`00092528
>     fffffadf`9eeb4460 fffffadf`9eeb4370 : nt!PipProcessDevNodeTree+0x223
>     fffffadf`936084d0
>      fffff800`014329f7 : ffffffff`00000000 fffffadf`9eeb4370
>     fffff800`00092528 fffffadf`9eeb4490 : nt!PipDeviceActionWorker+0x199
>     fffffadf`93608560
>      fffff800`0142a14d : 00000000`00000000 00000000`0000fffc
>     00000000`00000000 00000000`0000fffc : nt!IopInitializeBootDrivers+0xc57
>     fffffadf`936088c0
>      fffff800`01428144 : fffff800`00091650 fffff800`00091650
>     00000000`00000003 fffffadf`9ee90010 : nt!IoInitSystem+0xf4f
>     fffffadf`93608a50
>      fffff800`0130dc29 : 12f93b24`1e99bf20 fffffadf`9ee91bf0
>     00000000`00000080 fffffadf`9ee91bf0 :
>     nt!Phase1InitializationDiscard+0x111d
>     fffffadf`93608d40
>     fffff800`0124b972 : b6e6174a`baa6174e 8dd685ea`819685ee
>     307b39e5`3cbb19e1 0b4bab45`070baf41 : nt!Phase1Initialization+0x9
>     fffffadf`93608d70
>      fffff800`010202d6 : fffff800`011b1180 fffffadf`9ee91bf0
>     fffff800`011b5500 00000000`da83b678 : nt!PspSystemThreadStartup+0x3e
>     fffffadf`93608dd0
>      00000000`00000000 : 00000000`00000000 00000000`00000000
>     00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

>     SYMBOL_STACK_INDEX:  0

>     SYMBOL_NAME:  ACPI+19923

>     FOLLOWUP_NAME:  MachineOwner

>     MODULE_NAME: ACPI

>     IMAGE_NAME:  ACPI.sys

>     DEBUG_FLR_IMAGE_TIMESTAMP:  424d79aa

>     STACK_COMMAND:  .cxr 0xfffffadf93606f50 ; kb

>     FAILURE_BUCKET_ID:  X64_0x7E_ACPI+19923

>     BUCKET_ID:  X64_0x7E_ACPI+19923

>     Followup: MachineOwner
>     ---------

>     15: kd> !devnode 0 1
>     Dumping IopRootDeviceNode (= 0xfffffadf9ebd9620)
>     DevNode 0xfffffadf9ebd9620 for PDO 0xfffffadf9eeb4490
>       InstancePath is "HTREE\ROOT\0"
>       State = DeviceNodeStarted (0x308)
>       Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb3720 for PDO 0xfffffadf9eeb3940
>         InstancePath is "Root\ACPI_HAL\0000"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>         DevNode 0xfffffadf9ebd2490 for PDO 0xfffffadf9eeac060
>           InstancePath is "ACPI_HAL\PNP0C08\0"
>           ServiceName is "ACPI"
>           State = DeviceNodeStarted (0x308)
>           Previous State = DeviceNodeEnumerateCompletion (0x30d)
>           DevNode 0xfffffadf9eac5190 for PDO 0xfffffadf9e525120
>             InstancePath is "ACPI\PNP0C14\AWW"
>             ServiceName is "WmiAcpi"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>           DevNode 0xfffffadf9ebd19c0 for PDO 0xfffffadf9eac01b0
>             InstancePath is "ACPI\PNP0A08\0"
>             ServiceName is "pci"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>           DevNode 0xfffffadf9eacb190 for PDO 0xfffffadf9eaca1b0
>             InstancePath is "ACPI\PNP0C0C\aa"
>             State = DeviceNodeDriversAdded (0x303)
>             Previous State = DeviceNodeInitialized (0x302)
>           DevNode 0xfffffadf9e1be130 for PDO 0xfffffadf9eabd1b0
>             InstancePath is "ACPI\PNP0103\2&daba3ff&0"
>             State = DeviceNodeInitialized (0x302)
>             Previous State = DeviceNodeUninitialized (0x301)
>             Problem = CM_PROB_NOT_CONFIGURED
>           DevNode 0xfffffadf9e1c0340 for PDO 0xfffffadf9e2a3620
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9e323840 for PDO 0xfffffadf9ebd99a0
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9e323670 for PDO 0xfffffadf9e1bf480
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9e3234a0 for PDO 0xfffffadf9e1bf280
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9e3232d0 for PDO 0xfffffadf9eab7590
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9e323100 for PDO 0xfffffadf9eab7390
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9e3e4e40 for PDO 0xfffffadf9ebd17b0
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9e3e4c70 for PDO 0xfffffadf9ebd15b0
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9e3e4aa0 for PDO 0xfffffadf9e12d060
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9e3e48d0 for PDO 0xfffffadf9e12d8e0
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9e3e4700 for PDO 0xfffffadf9e12d6e0
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9e3e4530 for PDO 0xfffffadf9e12d4e0
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9e3e4360 for PDO 0xfffffadf9e12d2e0
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9e3e4190 for PDO 0xfffffadf9eeabe60
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9efea010 for PDO 0xfffffadf9eeabc60
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9efeae40 for PDO 0xfffffadf9eeaba60
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9efeac70 for PDO 0xfffffadf9eeab860
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9efeaaa0 for PDO 0xfffffadf9eeab660
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9efea8d0 for PDO 0xfffffadf9eeab460
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9efea700 for PDO 0xfffffadf9e323e60
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9efea530 for PDO 0xfffffadf9e323c60
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>           DevNode 0xfffffadf9efea360 for PDO 0xfffffadf9e323a60
>             State = DeviceNodeUninitialized (0x301)
>             Previous State = Unknown State (0x0)
>       DevNode 0xfffffadf9ebd8e40 for PDO 0xfffffadf9ebd8060
>         InstancePath is "Root\dmio\0000"
>         ServiceName is "dmio"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd8a60 for PDO 0xfffffadf9ebd8c80
>         InstancePath is "Root\ftdisk\0000"
>         ServiceName is "ftdisk"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd8680 for PDO 0xfffffadf9ebd88a0
>         InstancePath is "Root\LEGACY_AFD\0000"
>         ServiceName is "AFD"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd82a0 for PDO 0xfffffadf9ebd84c0
>         InstancePath is "Root\LEGACY_AMPA\0000"
>         ServiceName is "ampa"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb2e40 for PDO 0xfffffadf9eeb2060
>         InstancePath is "Root\LEGACY_BEEP\0000"
>         ServiceName is "Beep"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb2a60 for PDO 0xfffffadf9eeb2c80
>         InstancePath is "Root\LEGACY_CDAC15BA\0000"
>         ServiceName is "CdaC15BA"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb2680 for PDO 0xfffffadf9eeb28a0
>         InstancePath is "Root\LEGACY_CDAD10BA\0000"
>         ServiceName is "CdaD10BA"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb22a0 for PDO 0xfffffadf9eeb24c0
>         InstancePath is "Root\LEGACY_CRCDISK\0000"
>         ServiceName is "crcdisk"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd7e40 for PDO 0xfffffadf9ebd7060
>         InstancePath is "Root\LEGACY_DMBOOT\0000"
>         ServiceName is "dmboot"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd7a60 for PDO 0xfffffadf9ebd7c80
>         InstancePath is "Root\LEGACY_DMLOAD\0000"
>         ServiceName is "dmload"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd7680 for PDO 0xfffffadf9ebd78a0
>         InstancePath is "Root\LEGACY_FIPS\0000"
>         ServiceName is "Fips"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd72a0 for PDO 0xfffffadf9ebd74c0
>         InstancePath is "Root\LEGACY_GPC\0000"
>         ServiceName is "Gpc"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb1e40 for PDO 0xfffffadf9eeb1060
>         InstancePath is "Root\LEGACY_HTTP\0000"
>         ServiceName is "HTTP"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb1a60 for PDO 0xfffffadf9eeb1c80
>         InstancePath is "Root\LEGACY_IPNAT\0000"
>         ServiceName is "IpNat"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb1680 for PDO 0xfffffadf9eeb18a0
>         InstancePath is "Root\LEGACY_IPSEC\0000"
>         ServiceName is "IPSec"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb12a0 for PDO 0xfffffadf9eeb14c0
>         InstancePath is "Root\LEGACY_KSECDD\0000"
>         ServiceName is "ksecdd"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd6e40 for PDO 0xfffffadf9ebd6060
>         InstancePath is "Root\LEGACY_MNMDD\0000"
>         ServiceName is "mnmdd"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd6a60 for PDO 0xfffffadf9ebd6c80
>         InstancePath is "Root\LEGACY_MOUNTMGR\0000"
>         ServiceName is "mountmgr"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd6680 for PDO 0xfffffadf9ebd68a0
>         InstancePath is "Root\LEGACY_NDIS\0000"
>         ServiceName is "NDIS"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd62a0 for PDO 0xfffffadf9ebd64c0
>         InstancePath is "Root\LEGACY_NDISTAPI\0000"
>         ServiceName is "NdisTapi"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb0e40 for PDO 0xfffffadf9eeb0060
>         InstancePath is "Root\LEGACY_NDISUIO\0000"
>         ServiceName is "Ndisuio"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb0a60 for PDO 0xfffffadf9eeb0c80
>         InstancePath is "Root\LEGACY_NDPROXY\0000"
>         ServiceName is "NDProxy"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb0680 for PDO 0xfffffadf9eeb08a0
>         InstancePath is "Root\LEGACY_NETBT\0000"
>         ServiceName is "NetBT"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeb02a0 for PDO 0xfffffadf9eeb04c0
>         InstancePath is "Root\LEGACY_NULL\0000"
>         ServiceName is "Null"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd5e40 for PDO 0xfffffadf9ebd5060
>         InstancePath is "Root\LEGACY_PARTMGR\0000"
>         ServiceName is "PartMgr"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd5a60 for PDO 0xfffffadf9ebd5c80
>         InstancePath is "Root\LEGACY_RASACD\0000"
>         ServiceName is "RasAcd"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd5680 for PDO 0xfffffadf9ebd58a0
>         InstancePath is "Root\LEGACY_RDPCDD\0000"
>         ServiceName is "RDPCDD"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd52a0 for PDO 0xfffffadf9ebd54c0
>         InstancePath is "Root\LEGACY_SECDRV\0000"
>         ServiceName is "Secdrv"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeafe40 for PDO 0xfffffadf9eeaf060
>         InstancePath is "Root\LEGACY_TCPIP\0000"
>         ServiceName is "Tcpip"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeafa60 for PDO 0xfffffadf9eeafc80
>         InstancePath is "Root\LEGACY_VGASAVE\0000"
>         ServiceName is "VgaSave"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeaf680 for PDO 0xfffffadf9eeaf8a0
>         InstancePath is "Root\LEGACY_VOLSNAP\0000"
>         ServiceName is "VolSnap"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9eeaf2a0 for PDO 0xfffffadf9eeaf4c0
>         InstancePath is "Root\LEGACY_WANARP\0000"
>         ServiceName is "Wanarp"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0xfffffadf9ebd4e40 for PDO 0xfffffadf9ebd4060
>         InstancePath is "Root\MEDIA\MS_MMACM"
>         ServiceName is "audstub"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd4a60 for PDO 0xfffffadf9ebd4c80
>         InstancePath is "Root\MEDIA\MS_MMDRV"
>         ServiceName is "audstub"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd4680 for PDO 0xfffffadf9ebd48a0
>         InstancePath is "Root\MEDIA\MS_MMMCI"
>         ServiceName is "audstub"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd42a0 for PDO 0xfffffadf9ebd44c0
>         InstancePath is "Root\MEDIA\MS_MMVCD"
>         ServiceName is "audstub"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9eeaee40 for PDO 0xfffffadf9eeae060
>         InstancePath is "Root\MEDIA\MS_MMVID"
>         ServiceName is "audstub"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9eeaea60 for PDO 0xfffffadf9eeaec80
>         InstancePath is "Root\MS_L2TPMINIPORT\0000"
>         ServiceName is "Rasl2tp"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9eeae680 for PDO 0xfffffadf9eeae8a0
>         InstancePath is "Root\MS_NDISWANIP\0000"
>         ServiceName is "NdisWan"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9eeae2a0 for PDO 0xfffffadf9eeae4c0
>         InstancePath is "Root\MS_PPPOEMINIPORT\0000"
>         ServiceName is "RasPppoe"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd3e40 for PDO 0xfffffadf9ebd3060
>         InstancePath is "Root\MS_PPTPMINIPORT\0000"
>         ServiceName is "PptpMiniport"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd3a60 for PDO 0xfffffadf9ebd3c80
>         InstancePath is "Root\MS_PSCHEDMP\0000"
>         ServiceName is "PSched"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd3680 for PDO 0xfffffadf9ebd38a0
>         InstancePath is "Root\MS_PSCHEDMP\0001"
>         ServiceName is "PSched"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd32a0 for PDO 0xfffffadf9ebd34c0
>         InstancePath is "Root\MS_PTIMINIPORT\0000"
>         ServiceName is "Raspti"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9eeade40 for PDO 0xfffffadf9eead060
>         InstancePath is "Root\RDPDR\0000"
>         ServiceName is "rdpdr"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9eeada60 for PDO 0xfffffadf9eeadc80
>         InstancePath is "Root\RDP_KBD\0000"
>         ServiceName is "TermDD"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9eead680 for PDO 0xfffffadf9eead8a0
>         InstancePath is "Root\RDP_MOU\0000"
>         ServiceName is "TermDD"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9eead2a0 for PDO 0xfffffadf9eead4c0
>         InstancePath is "Root\SYSTEM\0000"
>         ServiceName is "swenum"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd2e40 for PDO 0xfffffadf9ebd2060
>         InstancePath is "Root\SYSTEM\0001"
>         ServiceName is "update"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>       DevNode 0xfffffadf9ebd2a60 for PDO 0xfffffadf9ebd2c80
>         InstancePath is "Root\SYSTEM\0002"
>         ServiceName is "mssmbios"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)

#2183 | daniel_k | ⇗ @diderius6, did you already try test2? Analysing the code, test2 should work, otherwise there is something else with x64.
#2184 | diderius6 | ⇗ @daniel_k acpi_test2.sys gives endless loop, no BSOD. But the windebug crashes during start, no output later on Dietmar
#2185 | daniel_k | Unfortunately I'm out of ideas for now.

#2186

diderius6

⇗ @daniel_k
acpi_test3.sys gives also endless loop, no BSOD.
And the windbg crashes also during start,
so no output later on
Dietmar
PS: The 5512 XP debug XP 64 has the advantage, that it shows a lot of information.
So, just kill the BSOD A5 0x02 for it and we will be at the core of the problem.
From the results of last 5048 acpi.sys, I would try to implement the hack from infuscomus
to this pointer in last acpi_test1.sys, which shows exact as the classical Nullpointer for the XP SP3 to low memory.
You can find this way here in the forum,
read from post 757 ff.

#2187 | daniel_k | ⇗ @diderius6, applied the hacks from post 757. Please try it.

#2188

diderius6

⇗ @daniel_k
Yes,
but you forget to jmp always over BSOD
BugCheck A5, {2001, 1, ffffffffc0000034, fffffadf9df52238}.
I also copied ntoskrnl.exe and hal.dll from the XP 64 SP2 DEBUG
version.
I noticed, that the output from windbg is better with them
and it crashes less
Dietmar
PS: Until now, the behavior of XP 64 on Ryzen is absolut identic with XP SP3 32 bit.

#2189 | daniel_k | Ops, I've applied only the hacks from post 757. Here it is.

#2190

diderius6

⇗ @daniel_k
Now is the same BSOD A5 (0x02,..) as before. May be, it is only one step away from working!
But I think, it is the right way, because this way works before also.
Tomorrow I flash the DSDT in Bios new,
killing the device ACPI\PNP0A08-0,
because in Debug XP 64 acpi.sys I do not find the bugcheck place,
where BSOD A5 (0x02,..) happens
Dietmar

>     Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
>     Copyright (c) Microsoft Corporation. All rights reserved.

>     Opened \\.\com1
>     Waiting to reconnect...
>     Connected to Windows Server 2003 3790 x64 target at (Sun Sep  1 01:40:00.281 2019 (UTC + 2:00)), ptr64 TRUE
>     Kernel Debugger connection established.
>     WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
>     Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
>     *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
>     Executable search path is: C:\localsymbols
>     Windows Server 2003 Kernel Version 3790 MP (1 procs) Checked x64
>     Built by: 3790.srv03_sp2_rtm.070216-1710
>     Machine Name:
>     Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`013d1fd0
>     System Uptime: not available

>     *** Assertion failed: NT_SUCCESS(status)
>     ***   Source File: d:\nt\base\busdrv\acpi\driver\nt\bus.c, line 2682

>     Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i
>     i
>     FFFFFADF9E325430 ACPI\PNP0A08-0 (0x9e333710): IRP_MN_QUERY_RESOURCE_REQUIREMENTS = 0xc00000bb

>     *** Fatal System Error: 0x000000a5
>                            (0x0000000000000002,0xFFFFFADF9E325430,0x0000000000000001,0xFFFFFADF9E333710)

>     Break instruction exception - code 80000003 (first chance)

>     A fatal system error has occurred.
>     Debugger entered on first try; Bugcheck callbacks have not been invoked.

>     A fatal system error has occurred.

>     Connected to Windows Server 2003 3790 x64 target at (Sun Sep  1 01:40:34.031 2019 (UTC + 2:00)), ptr64 TRUE
>     Loading Kernel Symbols
>     ........................
>     Loading User Symbols

>     *******************************************************************************
>     *                                                                             *
>     *                        Bugcheck Analysis                                    *
>     *                                                                             *
>     *******************************************************************************

>     Use !analyze -v to get detailed debugging information.

>     BugCheck A5, {2, fffffadf9e325430, 1, fffffadf9e333710}

>     *** No owner thread found for resource fffff800013eab00
>     *** No owner thread found for resource fffff800013eab00
>     *** No owner thread found for resource fffff800013eab00
>     *** No owner thread found for resource fffff800013eab00
>     Probably caused by : ACPI.sys ( ACPI!ACPIBusIrpQueryResourceRequirements+446 )

>     Followup: MachineOwner
>     ---------

>     nt!RtlpBreakWithStatusInstruction:
>     fffff800`011a02e0 cc              int     3
>     15: kd> !analyze -v
>     *******************************************************************************
>     *                                                                             *
>     *                        Bugcheck Analysis                                    *
>     *                                                                             *
>     *******************************************************************************

>     ACPI_BIOS_ERROR (a5)
>     The ACPI Bios in the system is not fully compliant with the ACPI specification.
>     The first value indicates where the incompatibility lies:
>     This bug check covers a great variety of ACPI problems.  If a kernel debugger
>     is attached, use "!analyze -v".  This command will analyze the precise problem,
>     and display whatever information is most useful for debugging the specific
>     error.
>     Arguments:
>     Arg1: 0000000000000002, ACPI_ROOT_PCI_RESOURCE_FAILURE
>     	ACPI could not process the resource list for the PCI root buses
>     Arg2: fffffadf9e325430, The ACPI Extension for the PCI bus.
>     Arg3: 0000000000000001, ACPI cannot convert the BIOS' resource list into the proper
>     	format. This probably represents a flaw in the BIOS' list
>     	encoding procedure.
>     Arg4: fffffadf9e333710, Pointer to the QUERY_RESOURCE_REQUIREMENTS irp

>     Debugging Details:
>     ------------------

>     *** No owner thread found for resource fffff800013eab00
>     *** No owner thread found for resource fffff800013eab00
>     *** No owner thread found for resource fffff800013eab00
>     *** No owner thread found for resource fffff800013eab00

>     ACPI_EXTENSION:  fffffadf9e325430 -- (!acpikd.acpiext fffffadf9e325430)

>     ACPI_RESCONFLICT:  0000000000000001 -- (!acpiresconflict 0000000000000001 fffffadf9e333710)
>     Number of arguments found = 1. 2 arguments expected
>     Usage: acpiresconflict  [DeviceExtension] [IoResList] [e820Info]

>     DEFAULT_BUCKET_ID:  DRIVER_FAULT

>     BUGCHECK_STR:  0xA5

>     PROCESS_NAME:  System

>     CURRENT_IRQL:  2

>     LOCK_ADDRESS:  fffff800013eac00 -- (!locks fffff800013eac00)
>     The state of the ACPI locks is:
>       - Build Queue Lock is not owned
>       - Button Lock is not owned
>       - Device Tree Lock is not owned
>       - Fatal Lock is not owned
>       - Power Lock is not owned
>       - Get Lock is not owned
>       - Power Queue Lock is not owned
>       - Thermal Lock is not owned
>       - Update Flags Lock is not owned
>       - Worker Lock is not owned

>     PNP_TRIAGE:
>     	Lock address  : 0xfffff800013eac00
>     	Thread Count  : 1
>     	Thread address: 0xfffffadf9e3117d0
>     	Thread wait   : 0x105eca8c

>     LAST_CONTROL_TRANSFER:  from fffff8000105d707 to fffff800011a02e0

>     STACK_TEXT:
>     fffffadf`93a06968
>      fffff800`0105d707 : 00000000`000000a5 00000000`000000a5
>     00000000`0000000f 00000000`00000000 : nt!RtlpBreakWithStatusInstruction
>     fffffadf`93a06970
>      fffff800`0105e9a0 : fffff800`00000003 00000000`000000a5
>     00000000`00000002 fffffadf`9e325430 : nt!KiBugCheckDebugBreak+0x17
>     fffffadf`93a069e0
>      fffff800`01197144 : fffffadf`000000a5 00000000`00000002
>     fffffadf`9e325430 00000000`00000001 : nt!KeBugCheck2+0x630
>     fffffadf`93a07020
>      fffffadf`931ceef6 : 00000000`000000a5 00000000`00000002
>     fffffadf`9e325430 00000000`00000001 : nt!KeBugCheckEx+0x104
>     fffffadf`93a07060
>      fffffadf`9316c804 : fffffadf`9df3de60 fffffadf`9e333710
>     fffffadf`93a07148 fffffadf`9e333710 :
>     ACPI!ACPIBusIrpQueryResourceRequirements+0x446
>     fffffadf`93a07110
>     fffff800`014ec01c : fffffadf`9df3de60 fffffadf`9e333710
>     00000000`00000000 00000000`00000000 : ACPI!ACPIDispatchIrp+0x164
>     fffffadf`93a071a0
>      fffff800`014dac61 : fffffadf`9df3de60 fffffadf`93a07288
>     fffffadf`93a07270 00000000`00000000 : nt!IopSynchronousCall+0x29c
>     fffffadf`93a07240
>      fffff800`014dc966 : fffffadf`9dde8a40 ffffffff`8000012c
>     fffffadf`93a073a8 fffffa80`000f003f :
>     nt!PiQueryResourceRequirements+0x111
>     fffffadf`93a07310
>     fffff800`014dff21 : fffffadf`9dde8a40 fffffadf`9e32ca00
>     fffffadf`93a079b4 fffffadf`9e32cf70 : nt!PiProcessNewDeviceNode+0x1ab6
>     fffffadf`93a07660
>      fffff800`0104e1b6 : fffffadf`9e333920 fffffadf`00000000
>     00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x281
>     fffffadf`93a07970
>      fffff800`016e2bf7 : 00000000`00000000 00000000`00000038
>     fffffadf`6e657050 fffff800`00091701 : nt!PipDeviceActionWorker+0x2f6
>     fffffadf`93a07a10
>      fffff800`016d8839 : fffff800`00091448 fffffadf`93a08160
>     fffffadf`9e30e1a0 fffff800`00000000 : nt!IopInitializeBootDrivers+0xb47
>     fffffadf`93a080e0
>      fffff800`016d6483 : fffff800`00091448 fffff800`01724340
>     fffffadf`93a08b68 00000000`00000000 : nt!IoInitSystem+0x1119
>     fffffadf`93a08a40
>      fffff800`0149d643 : fffff800`00091448 29e9a186`25a9bd80
>     2a610eb2`22a11ea3 10d18c06`1d918c22 :
>     nt!Phase1InitializationDiscard+0x11b3
>     fffffadf`93a08d40
>     fffff800`015762de : fffff800`00091448 8dd685ea`819685ee
>     307b39e5`3cbb19e1 0b4bab45`070baf41 : nt!Phase1Initialization+0x13
>     fffffadf`93a08d70
>      fffff800`0119fe96 : fffff800`0149d630 fffff800`00091448
>     fffff800`015762a0 8f4ca6e9`830ea2ed : nt!PspSystemThreadStartup+0x3e
>     fffffadf`93a08dd0
>      00000000`00000000 : 00000000`00000000 00000000`00000000
>     00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

>     STACK_COMMAND:  kb

>     FOLLOWUP_IP:
>     ACPI!ACPIBusIrpQueryResourceRequirements+446
>     fffffadf`931ceef6 cc              int     3

>     SYMBOL_STACK_INDEX:  4

>     SYMBOL_NAME:  ACPI!ACPIBusIrpQueryResourceRequirements+446

>     FOLLOWUP_NAME:  MachineOwner

>     MODULE_NAME: ACPI

>     IMAGE_NAME:  ACPI.sys

>     DEBUG_FLR_IMAGE_TIMESTAMP:  45d70c6e

>     FAILURE_BUCKET_ID:  X64_0xA5_ACPI!ACPIBusIrpQueryResourceRequirements+446

>     BUCKET_ID:  X64_0xA5_ACPI!ACPIBusIrpQueryResourceRequirements+446

>     Followup: MachineOwner
>     ---------

## Page 147

#2191 | daniel_k | ⇗ @diderius6, found where to patch it.

#2192

diderius6

⇗ @daniel_k
Still the same BSOD of the same Device

    FFFFFADF9E325430 ACPI\PNP0A08-0 (0x9e333710): IRP_MN_QUERY_RESOURCE_REQUIREMENTS = 0xc00000bb

    *** Fatal System Error: 0x000000a5
                           (0x0000000000000002,0xFFFFFADF9E325430,0x0000000000000001,0xFFFFFADF9E333710)

On XP SP3 acpi.sys I found 8 different pathes, which leads to Bsod A5 (0x02).
So I think, the same is true here
Dietmar
PS: Now I go to bed. When you find the other possibilities which lead to this BSOD,
you can hack them. If not, tomorrow I build new DSDT without this crazy device,
it is exact the same as for XP SP3, has something to do with the PCIe bus.

#2193 | daniel_k | ⇗ @diderius6, patched all BSOD A5 (0x02) I could find. Give it a try.
#2194 | Mov AX, 0xDEAD | diderius6, please hide WinDBG reports to "spoiler" tag for much better reading this topic )

#2195

diderius6

⇗ @daniel_k
Hi,
This is BSOD A5 (0x02, ..)
of another device from the PCI list.
But Windbg this time does not show, which one.
So, the only possibility now is to look again in acpi.sys
for another path, which is not blocked until now
to A5 (0x02,..)
Dietmar
PS: ⇗ @Mov AX, 0xDEAD
Do you have an idea, how to overcome BSOD A5 (0x02,..) on the acpi.sys from XP 64 SP2?

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Opened \\.\com1
    Waiting to reconnect...
    Connected to Windows Server 2003 3790 x64 target at (Sun Sep  1 10:48:18.890 2019 (UTC + 2:00)), ptr64 TRUE
    Kernel Debugger connection established.
    WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
    Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
    *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
    Executable search path is: C:\localsymbols
    Windows Server 2003 Kernel Version 3790 MP (1 procs) Checked x64
    Built by: 3790.srv03_sp2_rtm.070216-1710
    Machine Name:
    Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`013d1fd0
    System Uptime: not available

    *** Fatal System Error: 0x000000a5
                           (0x0000000000000002,0xFFFFFADF9E325430,0x0000000000000000,0xFFFFFADF9E333710)

    Break instruction exception - code 80000003 (first chance)

    A fatal system error has occurred.
    Debugger entered on first try; Bugcheck callbacks have not been invoked.

    A fatal system error has occurred.

    Connected to Windows Server 2003 3790 x64 target at (Sun Sep  1 10:48:32.687 2019 (UTC + 2:00)), ptr64 TRUE
    Loading Kernel Symbols
    ........................
    Loading User Symbols

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A5, {2, fffffadf9e325430, 0, fffffadf9e333710}

    *** No owner thread found for resource fffff800013eab00
    *** No owner thread found for resource fffff800013eab00
    *** No owner thread found for resource fffff800013eab00
    *** No owner thread found for resource fffff800013eab00
    Probably caused by : ACPI.sys ( ACPI!ACPIBusIrpQueryResources+2b8 )

    Followup: MachineOwner
    ---------

    nt!RtlpBreakWithStatusInstruction:
    fffff800`011a02e0 cc              int     3
    15: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    ACPI_BIOS_ERROR (a5)
    The ACPI Bios in the system is not fully compliant with the ACPI specification.
    The first value indicates where the incompatibility lies:
    This bug check covers a great variety of ACPI problems.  If a kernel debugger
    is attached, use "!analyze -v".  This command will analyze the precise problem,
    and display whatever information is most useful for debugging the specific
    error.
    Arguments:
    Arg1: 0000000000000002, ACPI_ROOT_PCI_RESOURCE_FAILURE
    	ACPI could not process the resource list for the PCI root buses
    Arg2: fffffadf9e325430, The ACPI Extension for the PCI bus.
    Arg3: 0000000000000000, ACPI cannot convert the BIOS' resource list into the proper
    	format. This probably represents a flaw in the BIOS' list
    	encoding procedure.
    Arg4: fffffadf9e333710, Pointer to the QUERY_RESOURCES irp

    Debugging Details:
    ------------------

    *** No owner thread found for resource fffff800013eab00
    *** No owner thread found for resource fffff800013eab00
    *** No owner thread found for resource fffff800013eab00
    *** No owner thread found for resource fffff800013eab00

    ACPI_EXTENSION:  fffffadf9e325430 -- (!acpikd.acpiext fffffadf9e325430)

    ACPI_RESCONFLICT:  0000000000000000 -- (!acpiresconflict 0000000000000000 fffffadf9e333710)
    Number of arguments found = 1. 2 arguments expected
    Usage: acpiresconflict  [DeviceExtension] [IoResList] [e820Info]

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0xA5

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    LOCK_ADDRESS:  fffff800013eac00 -- (!locks fffff800013eac00)
    The state of the ACPI locks is:
      - Build Queue Lock is not owned
      - Button Lock is not owned
      - Device Tree Lock is not owned
      - Fatal Lock is not owned
      - Power Lock is not owned
      - Get Lock is not owned
      - Power Queue Lock is not owned
      - Thermal Lock is not owned
      - Update Flags Lock is not owned
      - Worker Lock is not owned

    PNP_TRIAGE:
    	Lock address  : 0xfffff800013eac00
    	Thread Count  : 1
    	Thread address: 0xfffffadf9e3117d0
    	Thread wait   : 0x105eca8c

    LAST_CONTROL_TRANSFER:  from fffff8000105d707 to fffff800011a02e0

    STACK_TEXT:
    fffffadf`93a06968
     fffff800`0105d707 : 00000000`000000a5 00000000`000000a5
    00000000`0000000f 00000000`00000000 : nt!RtlpBreakWithStatusInstruction
    fffffadf`93a06970
     fffff800`0105e9a0 : fffff800`00000003 00000000`000000a5
    00000000`00000002 fffffadf`9e325430 : nt!KiBugCheckDebugBreak+0x17
    fffffadf`93a069e0
     fffff800`01197144 : 00000000`000000a5 00000000`00000002
    fffffadf`9e325430 00000000`00000000 : nt!KeBugCheck2+0x630
    fffffadf`93a07020
     fffffadf`931cea38 : 00000000`000000a5 00000000`00000002
    fffffadf`9e325430 00000000`00000000 : nt!KeBugCheckEx+0x104
    fffffadf`93a07060
     fffffadf`9316c804 : fffffadf`9df3c7d0 fffffadf`9e333710
    fffffadf`93a07138 00000000`00000050 :
    ACPI!ACPIBusIrpQueryResources+0x2b8
    fffffadf`93a07100
    fffff800`014ec01c : fffffadf`9df3c7d0 fffffadf`9e333710
    00000000`00000000 fffffadf`9de87b00 : ACPI!ACPIDispatchIrp+0x164
    fffffadf`93a07190
     fffff800`014da8bb : fffffadf`9df3c7d0 fffffadf`93a07280
    fffffadf`93a07268 fffff800`014e73dc : nt!IopSynchronousCall+0x29c
    fffffadf`93a07230
     fffff800`014dcd69 : fffffadf`9de87a40 ffffffff`8000012c
    00000000`00000001 00000000`00000007 :
    nt!PiQueryAndAllocateBootResources+0x19b
    fffffadf`93a07310
    fffff800`014dff21 : fffffadf`9de87a40 fffffadf`9e32ca00
    fffffadf`93a079b4 fffffadf`9e32cf70 : nt!PiProcessNewDeviceNode+0x1eb9
    fffffadf`93a07660
     fffff800`0104e1b6 : fffffadf`9e333920 fffffadf`00000000
    00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x281
    fffffadf`93a07970
     fffff800`016e2bf7 : 00000000`00000000 00000000`00000038
    fffffadf`6e657050 fffff800`00091701 : nt!PipDeviceActionWorker+0x2f6
    fffffadf`93a07a10
     fffff800`016d8839 : fffff800`00091448 fffffadf`93a08160
    fffffadf`9e30e1a0 fffff800`00000000 : nt!IopInitializeBootDrivers+0xb47
    fffffadf`93a080e0
     fffff800`016d6483 : fffff800`00091448 fffff800`01724340
    fffffadf`93a08b68 00000000`00000000 : nt!IoInitSystem+0x1119
    fffffadf`93a08a40
     fffff800`0149d643 : fffff800`00091448 29e9a984`25a9a980
    2ae11ea6`26a11ea2 10d18c06`1d918c02 :
    nt!Phase1InitializationDiscard+0x11b3
    fffffadf`93a08d40
    fffff800`015762de : fffff800`00091448 8dd685ea`819685ee
    307b39e5`3c3b39e1 0b4bab45`070bab41 : nt!Phase1Initialization+0x13
    fffffadf`93a08d70
     fffff800`0119fe96 : fffff800`0149d630 fffff800`00091448
    fffff800`015762a0 8f4ca2e9`830ca2ed : nt!PspSystemThreadStartup+0x3e
    fffffadf`93a08dd0
     00000000`00000000 : 00000000`00000000 00000000`00000000
    00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    ACPI!ACPIBusIrpQueryResources+2b8
    fffffadf`931cea38 cc              int     3

    SYMBOL_STACK_INDEX:  4

    SYMBOL_NAME:  ACPI!ACPIBusIrpQueryResources+2b8

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: ACPI

    IMAGE_NAME:  ACPI.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  45d70c6e

    FAILURE_BUCKET_ID:  X64_0xA5_ACPI!ACPIBusIrpQueryResources+2b8

    BUCKET_ID:  X64_0xA5_ACPI!ACPIBusIrpQueryResources+2b8

    Followup: MachineOwner
    ---------

    15: kd> !devnode 0 1
    Dumping IopRootDeviceNode (= 0xfffffadf9e333920)
    DevNode 0xfffffadf9e333920 for PDO 0xfffffadf9e336040
      InstancePath is "HTREE\ROOT\0"
      State = DeviceNodeStarted (0x308)
      Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e333530 for PDO 0xfffffadf9e058070
        InstancePath is "Root\ACPI_HAL\0000"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
        DevNode 0xfffffadf9e32ce30 for PDO 0xfffffadf9e32ca40
          InstancePath is "ACPI_HAL\PNP0C08\0"
          ServiceName is "ACPI"
          State = DeviceNodeStarted (0x308)
          Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9de87c20 for PDO 0xfffffadf9df3c110
            InstancePath is "ACPI\PNP0C14\AWW"
            ServiceName is "WmiAcpi"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
          DevNode 0xfffffadf9de87a40 for PDO 0xfffffadf9df3c7d0
            InstancePath is "ACPI\PNP0A08\0"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
          DevNode 0xfffffadf9de87860 for PDO 0xfffffadf9df3d210
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9de87680 for PDO 0xfffffadf9df3db90
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9de874a0 for PDO 0xfffffadf9de88710
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9de872c0 for PDO 0xfffffadf9de88500
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9df1e010 for PDO 0xfffffadf9ddf8070
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9df1ee30 for PDO 0xfffffadf9ddf8e60
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9df1ec50 for PDO 0xfffffadf9ddf8c50
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9df1ea70 for PDO 0xfffffadf9ddf8a40
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9df1e890 for PDO 0xfffffadf9ddf8830
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9df1e6b0 for PDO 0xfffffadf9ddf8620
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9df1e4d0 for PDO 0xfffffadf9ddf8410
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9df1e2f0 for PDO 0xfffffadf9df3b070
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9df4e010 for PDO 0xfffffadf9df3be60
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9df4ee30 for PDO 0xfffffadf9df3bc50
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9df4ec50 for PDO 0xfffffadf9df3ba40
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9df4ea70 for PDO 0xfffffadf9df3b830
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9df4e890 for PDO 0xfffffadf9df3b620
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9df4e6b0 for PDO 0xfffffadf9df3b410
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9df4e4d0 for PDO 0xfffffadf9de87070
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9df4e2f0 for PDO 0xfffffadf9de87e60
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
      DevNode 0xfffffadf9e058a50 for PDO 0xfffffadf9e058c90
        InstancePath is "Root\dmio\0000"
        ServiceName is "dmio"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9e058650 for PDO 0xfffffadf9e058890
        InstancePath is "Root\ftdisk\0000"
        ServiceName is "ftdisk"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9e332010 for PDO 0xfffffadf9e058450
        InstancePath is "Root\LEGACY_AFD\0000"
        ServiceName is "AFD"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e332c10 for PDO 0xfffffadf9e332e50
        InstancePath is "Root\LEGACY_AMPA\0000"
        ServiceName is "ampa"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e332810 for PDO 0xfffffadf9e332a50
        InstancePath is "Root\LEGACY_BEEP\0000"
        ServiceName is "Beep"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e332410 for PDO 0xfffffadf9e332650
        InstancePath is "Root\LEGACY_CDAC15BA\0000"
        ServiceName is "CdaC15BA"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e057010 for PDO 0xfffffadf9e332250
        InstancePath is "Root\LEGACY_CDAD10BA\0000"
        ServiceName is "CdaD10BA"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e057c10 for PDO 0xfffffadf9e057e50
        InstancePath is "Root\LEGACY_CRCDISK\0000"
        ServiceName is "crcdisk"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e057810 for PDO 0xfffffadf9e057a50
        InstancePath is "Root\LEGACY_DMBOOT\0000"
        ServiceName is "dmboot"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e057410 for PDO 0xfffffadf9e057650
        InstancePath is "Root\LEGACY_DMLOAD\0000"
        ServiceName is "dmload"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e331010 for PDO 0xfffffadf9e057250
        InstancePath is "Root\LEGACY_FIPS\0000"
        ServiceName is "Fips"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e331c10 for PDO 0xfffffadf9e331e50
        InstancePath is "Root\LEGACY_GPC\0000"
        ServiceName is "Gpc"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e331810 for PDO 0xfffffadf9e331a50
        InstancePath is "Root\LEGACY_HTTP\0000"
        ServiceName is "HTTP"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e331410 for PDO 0xfffffadf9e331650
        InstancePath is "Root\LEGACY_IPNAT\0000"
        ServiceName is "IpNat"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e056010 for PDO 0xfffffadf9e331250
        InstancePath is "Root\LEGACY_IPSEC\0000"
        ServiceName is "IPSec"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e056c10 for PDO 0xfffffadf9e056e50
        InstancePath is "Root\LEGACY_KSECDD\0000"
        ServiceName is "ksecdd"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e056810 for PDO 0xfffffadf9e056a50
        InstancePath is "Root\LEGACY_MNMDD\0000"
        ServiceName is "mnmdd"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e056410 for PDO 0xfffffadf9e056650
        InstancePath is "Root\LEGACY_MOUNTMGR\0000"
        ServiceName is "mountmgr"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e330010 for PDO 0xfffffadf9e056250
        InstancePath is "Root\LEGACY_NDIS\0000"
        ServiceName is "NDIS"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e330c10 for PDO 0xfffffadf9e330e50
        InstancePath is "Root\LEGACY_NDISTAPI\0000"
        ServiceName is "NdisTapi"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e330810 for PDO 0xfffffadf9e330a50
        InstancePath is "Root\LEGACY_NDISUIO\0000"
        ServiceName is "Ndisuio"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e330410 for PDO 0xfffffadf9e330650
        InstancePath is "Root\LEGACY_NDPROXY\0000"
        ServiceName is "NDProxy"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e055010 for PDO 0xfffffadf9e330250
        InstancePath is "Root\LEGACY_NETBT\0000"
        ServiceName is "NetBT"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e055c10 for PDO 0xfffffadf9e055e50
        InstancePath is "Root\LEGACY_NULL\0000"
        ServiceName is "Null"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e055810 for PDO 0xfffffadf9e055a50
        InstancePath is "Root\LEGACY_PARTMGR\0000"
        ServiceName is "PartMgr"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e055410 for PDO 0xfffffadf9e055650
        InstancePath is "Root\LEGACY_RASACD\0000"
        ServiceName is "RasAcd"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e32f010 for PDO 0xfffffadf9e055250
        InstancePath is "Root\LEGACY_RDPCDD\0000"
        ServiceName is "RDPCDD"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e32fc10 for PDO 0xfffffadf9e32fe50
        InstancePath is "Root\LEGACY_SECDRV\0000"
        ServiceName is "Secdrv"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e32f810 for PDO 0xfffffadf9e32fa50
        InstancePath is "Root\LEGACY_TCPIP\0000"
        ServiceName is "Tcpip"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e32f410 for PDO 0xfffffadf9e32f650
        InstancePath is "Root\LEGACY_VGASAVE\0000"
        ServiceName is "VgaSave"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e054010 for PDO 0xfffffadf9e32f250
        InstancePath is "Root\LEGACY_VOLSNAP\0000"
        ServiceName is "VolSnap"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e054c10 for PDO 0xfffffadf9e054e50
        InstancePath is "Root\LEGACY_WANARP\0000"
        ServiceName is "Wanarp"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e054810 for PDO 0xfffffadf9e054a50
        InstancePath is "Root\MEDIA\MS_MMACM"
        ServiceName is "audstub"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9e054410 for PDO 0xfffffadf9e054650
        InstancePath is "Root\MEDIA\MS_MMDRV"
        ServiceName is "audstub"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9e32e010 for PDO 0xfffffadf9e054250
        InstancePath is "Root\MEDIA\MS_MMMCI"
        ServiceName is "audstub"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9e32ec10 for PDO 0xfffffadf9e32ee50
        InstancePath is "Root\MEDIA\MS_MMVCD"
        ServiceName is "audstub"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9e32e810 for PDO 0xfffffadf9e32ea50
        InstancePath is "Root\MEDIA\MS_MMVID"
        ServiceName is "audstub"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9e32e410 for PDO 0xfffffadf9e32e650
        InstancePath is "Root\MS_L2TPMINIPORT\0000"
        ServiceName is "Rasl2tp"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9e053010 for PDO 0xfffffadf9e32e250
        InstancePath is "Root\MS_NDISWANIP\0000"
        ServiceName is "NdisWan"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9e053c10 for PDO 0xfffffadf9e053e50
        InstancePath is "Root\MS_PPPOEMINIPORT\0000"
        ServiceName is "RasPppoe"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9e053810 for PDO 0xfffffadf9e053a50
        InstancePath is "Root\MS_PPTPMINIPORT\0000"
        ServiceName is "PptpMiniport"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9e053410 for PDO 0xfffffadf9e053650
        InstancePath is "Root\MS_PSCHEDMP\0000"
        ServiceName is "PSched"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9e32d010 for PDO 0xfffffadf9e053250
        InstancePath is "Root\MS_PSCHEDMP\0001"
        ServiceName is "PSched"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9e32dc10 for PDO 0xfffffadf9e32de50
        InstancePath is "Root\MS_PTIMINIPORT\0000"
        ServiceName is "Raspti"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9e32d810 for PDO 0xfffffadf9e32da50
        InstancePath is "Root\RDPDR\0000"
        ServiceName is "rdpdr"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9e32d410 for PDO 0xfffffadf9e32d650
        InstancePath is "Root\RDP_KBD\0000"
        ServiceName is "TermDD"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9e052010 for PDO 0xfffffadf9e32d250
        InstancePath is "Root\RDP_MOU\0000"
        ServiceName is "TermDD"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9e052c10 for PDO 0xfffffadf9e052e50
        InstancePath is "Root\SYSTEM\0000"
        ServiceName is "swenum"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9e052810 for PDO 0xfffffadf9e052a50
        InstancePath is "Root\SYSTEM\0001"
        ServiceName is "update"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9e052410 for PDO 0xfffffadf9e052650
        InstancePath is "Root\SYSTEM\0002"
        ServiceName is "mssmbios"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)

#2196

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #2195

> PS: @Mov AX, 0xDEAD
> Do you have an idea, how to overcome BSOD A5 (0x02,..) on the acpi.sys from XP 64 SP2?

no, i dont know why winxp cannot accept some device resources
maybe this is same problem with IRQ on amd

#2197

diderius6

⇗ @daniel_k
I succeed to read out the BSODs via Windbg with 5048 acpi.sys from yesterday
which give infinity loop.
There I noticed something interesting:
With the DEBUG version of ntoskrnl.exe and hal.dll
the BSOD was the same as now with the 5512 acpi.sys
A5 (0x02,..).
But with the nondebug version of ntoskrnl.exe and hal.dll
the BSOD looks other, now it is going to pci.sys
But I think, the DEBUG versions of ntoskrnl.exe and hal.dll are better, show the problem more precise,
Dietmar
PS: The second spoiler is from todays acpi.sys of 5512 base. This time also with nondebug Ntoskrnl.exe and hal.dll

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Opened \\.\com1
    Waiting to reconnect...
    Connected to Windows Server 2003 3790 x64 target at (Sun Sep  1 13:17:48.125 2019 (UTC + 2:00)), ptr64 TRUE
    Kernel Debugger connection established.
    WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
    Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
    *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
    Executable search path is: C:\localsymbols
    Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64
    Built by: 3790.srv03_sp2_rtm.070216-1710
    Machine Name:
    Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d5100
    System Uptime: not available

    *** Fatal System Error: 0x0000000a
                           (0x0000000000000080,0x000000000000000C,0x0000000000000001,0xFFFFF80001079600)

    Break instruction exception - code 80000003 (first chance)

    A fatal system error has occurred.
    Debugger entered on first try; Bugcheck callbacks have not been invoked.

    A fatal system error has occurred.

    Connected to Windows Server 2003 3790 x64 target at (Sun Sep  1 13:18:01.359 2019 (UTC + 2:00)), ptr64 TRUE
    Loading Kernel Symbols
    ........................
    Loading User Symbols

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {80, c, 1, fffff80001079600}

    *** ERROR: Module load completed but symbols could not be loaded for ACPI.sys
    *** No owner thread found for resource fffff800011dda40
    *** No owner thread found for resource fffff800011dda40
    Probably caused by : pci.sys ( pci!PciDispatchIrp+1a0 )

    Followup: MachineOwner
    ---------

    nt!DbgBreakPointWithStatus:
    fffff800`01026db0 cc              int     3
    15: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000000000080, memory referenced
    Arg2: 000000000000000c, IRQL
    Arg3: 0000000000000001, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80001079600, address which referenced memory

    Debugging Details:
    ------------------

    *** No owner thread found for resource fffff800011dda40
    *** No owner thread found for resource fffff800011dda40

    WRITE_ADDRESS:  0000000000000080

    CURRENT_IRQL:  c

    FAULTING_IP:
    nt!IopCompleteRequest+68f
    fffff800`01079600 4981888000000000010000 or qword ptr [r8+80h],100h

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0xA

    PROCESS_NAME:  System

    IRP_ADDRESS:  ffffffffffffff88

    TRAP_FRAME:  fffffadf936076b0 -- (.trap 0xfffffadf936076b0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffadf9ebda350 rbx=0000000000000000 rcx=fffffadf9334b7f0
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80001079600 rsp=fffffadf93607840 rbp=fffffadf93607980
     r8=0000000000000000  r9=fffffadf93607918 r10=fffffadf9ebd0288
    r11=fffff80001032de0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    nt!IopCompleteRequest+0x68f:
    fffff800`01079600 4981888000000000010000 or qword ptr [r8+80h],100h ds:00000000`00000080=????????????????
    Resetting default scope

    LOCK_ADDRESS:  fffff800011ddb40 -- (!locks fffff800011ddb40)
    The state of the ACPI locks is:
    ACPI: Could not read acpi!AcpiBuildQueueLock
    ACPI: Could not read acpi!AcpiButtonLock
    ACPI: Could not read acpi!AcpiDeviceTreeLock
    ACPI: Could not read acpi!AcpiFatalLock
    ACPI: Could not read acpi!AcpiPowerLock
    ACPI: Could not read acpi!AcpiGetLock
    ACPI: Could not read acpi!AcpiPowerQueueLock
    ACPI: Could not read acpi!AcpiThermalLock
    ACPI: Could not read acpi!AcpiUpdateFlagsLock
    ACPI: Could not read acpi!AcpiWorkerSpinLock

    PNP_TRIAGE:
    	Lock address  : 0xfffff800011ddb40
    	Thread Count  : 1
    	Thread address: 0xfffffadf9ee91bf0
    	Thread wait   : 0xad

    LAST_CONTROL_TRANSFER:  from fffff800010d673e to fffff80001026db0

    STACK_TEXT:
    fffffadf`93606e48
     fffff800`010d673e : 00000000`0000000f 00000000`00000000
    00000000`00000080 fffff800`0105669e : nt!DbgBreakPointWithStatus
    fffffadf`93606e50
     fffff800`010d7d0e : fffff800`00000003 00000000`0000000a
    00000000`00000080 00000000`0000000c : nt!KiBugCheckDebugBreak+0x1e
    fffffadf`93606eb0
     fffff800`0102ea54 : 00000000`00000001 fffffadf`92dc3290
    00000000`00000000 0000fadf`92dcf100 : nt!KeBugCheck2+0x640
    fffffadf`936074f0
     fffff800`0102e674 : 00000000`0000000a 00000000`00000080
    00000000`0000000c 00000000`00000001 : nt!KeBugCheckEx+0x104
    fffffadf`93607530
     fffff800`0102d607 : 00000000`00000000 00000000`5244415f
    00000000`00000000 fffffadf`92dadeb2 : nt!KiBugCheckDispatch+0x74
    fffffadf`936076b0
     fffff800`01079600 : fffffadf`93607c80 00000000`00000009
    00000000`00000000 00000000`00000000 : nt!KiPageFault+0x207
    fffffadf`93607840
     fffff800`01027f81 : 00000000`00000000 00000000`00000000
    00000000`00000000 fffffadf`9ebd0210 : nt!IopCompleteRequest+0x68f
    fffffadf`936078e0
     fffff800`01027b8d : 00000000`00000008 00000000`00000000
    00000000`00000000 fffffadf`9334b180 : nt!KiDeliverApc+0x215
    fffffadf`93607980
     fffff800`0102737b : fffffadf`93607ba0 fffff800`01030d7d
    00000000`00000010 00000000`00000246 : nt!KiApcInterrupt+0xdd
    fffffadf`93607b10
     fffff800`01030e05 : 00000000`00000000 00000000`00000000
    00000001`00000000 fffffadf`9ebda350 : nt!KiExitDispatcher+0x1d3
    fffffadf`93607b40
     fffff800`010252f9 : 00000000`00000000 00000000`00000000
    00000000`a0000003 fffffadf`9ebda350 : nt!KeInsertQueueApc+0xd4
    fffffadf`93607b90
     fffffadf`92d65a00 : 00000000`00000000 fffffadf`92d76f00
    00000000`00000000 fffffadf`93607d20 : nt!IopfCompleteRequest+0xa26
    fffffadf`93607c00
     fffffadf`92dddbf8 : fffffadf`9e0dca30 fffffadf`93607d20
    fffffadf`9e0dca30 fffffadf`93607cd0 : pci!PciDispatchIrp+0x1a0
    fffffadf`93607c30 fffffadf`92de02ea : fffffadf`9e0dca30 fffffadf`9eeb3d58 00000000`00010005 fffffadf`93607de0 : ACPI+0x59bf8
    fffffadf`93607cb0 fffffadf`92ddc218 : fffffadf`00000200 fffffadf`00000004 fffffadf`00000000 fffffadf`9eea7010 : ACPI+0x5c2ea
    fffffadf`93607d90 fffffadf`92d8eb9e : 00000000`00000000 fffffadf`9eea87d0 fffffadf`00000000 00000000`00000000 : ACPI+0x58218
    fffffadf`93607ec0 fffffadf`92ddad76 : 00000000`00000000 fffffadf`9eabb1b0 fffffadf`9eeb3d20 fffffadf`9ebd1260 : ACPI+0xab9e
    fffffadf`93607f70 fffffadf`92d941ae : fffffadf`92ddac40 fffffadf`9ebd1378 fffffadf`9eea8010 fffffadf`9ebd1260 : ACPI+0x56d76
    fffffadf`93607fb0 fffffadf`92d659e0 : 00000000`00000000 fffffadf`936080d0 fffffadf`9e0dce80 fffffadf`9ebd1260 : ACPI+0x101ae
    fffffadf`93608010
     fffff800`0133ed04 : fffffadf`9ebd1260 fffffadf`936080d0
    fffffadf`9e0dcd30 fffffadf`9eea12d0 : pci!PciDispatchIrp+0x180
    fffffadf`93608040
     fffff800`010d0891 : 00000000`00000000 00000000`00000000
    00000000`00000000 fffffadf`9eea1190 : nt!IopSynchronousCall+0x144
    fffffadf`936080b0
     fffff800`01335a3a : fffffadf`9eea9240 fffffadf`9eea1190
    fffffadf`9eea1190 00000000`00000000 : nt!IopQueryDeviceRelations+0x71
    fffffadf`93608140
     fffff800`010cc809 : fffffadf`9eab6660 fffff800`000924d0
    fffffadf`9eeb38c0 fffffadf`9eab6660 : nt!PipProcessDevNodeTree+0x342
    fffffadf`936084d0
     fffff800`014329f7 : ffffffff`00000000 fffffadf`9eab6660
    fffff800`000924d0 fffffadf`9eeb38f0 : nt!PipDeviceActionWorker+0x199
    fffffadf`93608560
     fffff800`0142a14d : 00000000`00000000 00000000`0000fffc
    00000000`00000000 00000000`0000fffc : nt!IopInitializeBootDrivers+0xc57
    fffffadf`936088c0
     fffff800`01428144 : fffff800`00091598 fffff800`00091598
    00000000`00000003 fffffadf`9ee90010 : nt!IoInitSystem+0xf4f
    fffffadf`93608a50
     fffff800`0130dc29 : 12d93b24`1e99bf20 fffffadf`9ee91bf0
    00000000`00000080 fffffadf`9ee91bf0 :
    nt!Phase1InitializationDiscard+0x111d
    fffffadf`93608d40
    fffff800`0124b972 : b6e6174a`baa6174e 8dd685ea`819685ee
    307b39e5`3c3b19e1 0b4bab45`070baf41 : nt!Phase1Initialization+0x9
    fffffadf`93608d70
     fffff800`010202d6 : fffff800`011b1180 fffffadf`9ee91bf0
    fffff800`011b5500 00000000`da83b888 : nt!PspSystemThreadStartup+0x3e
    fffffadf`93608dd0
     00000000`00000000 : 00000000`00000000 00000000`00000000
    00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    pci!PciDispatchIrp+1a0
    fffffadf`92d65a00 8bc3            mov     eax,ebx

    SYMBOL_STACK_INDEX:  c

    SYMBOL_NAME:  pci!PciDispatchIrp+1a0

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: pci

    IMAGE_NAME:  pci.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  45d694c3

    FAILURE_BUCKET_ID:  X64_0xA_pci!PciDispatchIrp+1a0

    BUCKET_ID:  X64_0xA_pci!PciDispatchIrp+1a0

    Followup: MachineOwner
    ---------

    15: kd> !devnode 0 1
    Dumping IopRootDeviceNode (= 0xfffffadf9eeb47c0)
    DevNode 0xfffffadf9eeb47c0 for PDO 0xfffffadf9eeb38f0
      InstancePath is "HTREE\ROOT\0"
      State = DeviceNodeStarted (0x308)
      Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd9c30 for PDO 0xfffffadf9ebd9e50
        InstancePath is "Root\ACPI_HAL\0000"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
        DevNode 0xfffffadf9eeac870 for PDO 0xfffffadf9eeac480
          InstancePath is "ACPI_HAL\PNP0C08\0"
          ServiceName is "ACPI"
          State = DeviceNodeStarted (0x308)
          Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9eea9240 for PDO 0xfffffadf9eab4320
            InstancePath is "ACPI\PNP0C14\AWW"
            ServiceName is "WmiAcpi"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
          DevNode 0xfffffadf9eea1190 for PDO 0xfffffadf9eabb1b0
            InstancePath is "ACPI\PNP0A08\0"
            ServiceName is "pci"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeStartPostWork (0x307)
          DevNode 0xfffffadf9eeb3220 for PDO 0xfffffadf9e0dd410
            InstancePath is "ACPI\PNP0C0C\aa"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9eab1330 for PDO 0xfffffadf9ee96e60
            InstancePath is "ACPI\PNP0103\2&daba3ff&0"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9e1be900 for PDO 0xfffffadf9eeb3e60
            InstancePath is "ACPI\AMDI0030\0"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9e1be730 for PDO 0xfffffadf9e1bf390
            InstancePath is "ACPI\PNP0C14\ASUSWMI"
            ServiceName is "WmiAcpi"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
          DevNode 0xfffffadf9e1be560 for PDO 0xfffffadf9e1bf190
            InstancePath is "ACPI\FixedButton\2&daba3ff&0"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9e1be390 for PDO 0xfffffadf9e1bee20
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_0"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9ee97ad0 for PDO 0xfffffadf9e1bec20
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_1"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9ee97900 for PDO 0xfffffadf9ee965c0
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_2"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9ee97730 for PDO 0xfffffadf9ee963c0
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_3"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9ee97560 for PDO 0xfffffadf9ebd9060
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_4"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9ee97390 for PDO 0xfffffadf9ebd9370
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_5"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9ee971c0 for PDO 0xfffffadf9e1bfba0
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_6"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9efda010 for PDO 0xfffffadf9e1bf9a0
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_7"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9efdae40 for PDO 0xfffffadf9ee95e60
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_8"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9efdac70 for PDO 0xfffffadf9ee95c60
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_9"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9efdaaa0 for PDO 0xfffffadf9eeb3060
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\10"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9efda8d0 for PDO 0xfffffadf9eeb3440
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\11"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9efda700 for PDO 0xfffffadf9e1c0740
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\12"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9efda530 for PDO 0xfffffadf9e1c0540
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\13"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9efda360 for PDO 0xfffffadf9e1c0340
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\14"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9dffc010 for PDO 0xfffffadf9ebd2a60
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\15"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9dffce40 for PDO 0xfffffadf9ebd2860
            InstancePath is "ACPI\PNP0C02\90"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9dffcc70 for PDO 0xfffffadf9ebd2660
            InstancePath is "ACPI\PNP0C02\91"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9dffcaa0 for PDO 0xfffffadf9ebd2460
            InstancePath is "ACPI\PNP0C14\AOD"
            ServiceName is "WmiAcpi"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9ebd9720 for PDO 0xfffffadf9ebd9940
        InstancePath is "Root\dmio\0000"
        ServiceName is "dmio"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9ebd9550 for PDO 0xfffffadf9eeb2060
        InstancePath is "Root\ftdisk\0000"
        ServiceName is "ftdisk"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9eeb2be0 for PDO 0xfffffadf9eeb2e00
        InstancePath is "Root\LEGACY_AFD\0000"
        ServiceName is "AFD"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb2800 for PDO 0xfffffadf9eeb2a20
        InstancePath is "Root\LEGACY_AMPA\0000"
        ServiceName is "ampa"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb2420 for PDO 0xfffffadf9eeb2640
        InstancePath is "Root\LEGACY_BEEP\0000"
        ServiceName is "Beep"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb2250 for PDO 0xfffffadf9ebd8060
        InstancePath is "Root\LEGACY_CDAC15BA\0000"
        ServiceName is "CdaC15BA"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd8c30 for PDO 0xfffffadf9ebd8e50
        InstancePath is "Root\LEGACY_CDAD10BA\0000"
        ServiceName is "CdaD10BA"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd8750 for PDO 0xfffffadf9ebd8970
        InstancePath is "Root\LEGACY_CRCDISK\0000"
        ServiceName is "crcdisk"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd8370 for PDO 0xfffffadf9ebd8590
        InstancePath is "Root\LEGACY_DMBOOT\0000"
        ServiceName is "dmboot"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb1e40 for PDO 0xfffffadf9eeb1060
        InstancePath is "Root\LEGACY_DMLOAD\0000"
        ServiceName is "dmload"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb1a60 for PDO 0xfffffadf9eeb1c80
        InstancePath is "Root\LEGACY_FIPS\0000"
        ServiceName is "Fips"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb1680 for PDO 0xfffffadf9eeb18a0
        InstancePath is "Root\LEGACY_GPC\0000"
        ServiceName is "Gpc"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb12a0 for PDO 0xfffffadf9eeb14c0
        InstancePath is "Root\LEGACY_HTTP\0000"
        ServiceName is "HTTP"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd7e40 for PDO 0xfffffadf9ebd7060
        InstancePath is "Root\LEGACY_IPNAT\0000"
        ServiceName is "IpNat"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd7a60 for PDO 0xfffffadf9ebd7c80
        InstancePath is "Root\LEGACY_IPSEC\0000"
        ServiceName is "IPSec"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd7680 for PDO 0xfffffadf9ebd78a0
        InstancePath is "Root\LEGACY_KSECDD\0000"
        ServiceName is "ksecdd"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd72a0 for PDO 0xfffffadf9ebd74c0
        InstancePath is "Root\LEGACY_MNMDD\0000"
        ServiceName is "mnmdd"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb0e40 for PDO 0xfffffadf9eeb0060
        InstancePath is "Root\LEGACY_MOUNTMGR\0000"
        ServiceName is "mountmgr"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb0a60 for PDO 0xfffffadf9eeb0c80
        InstancePath is "Root\LEGACY_NDIS\0000"
        ServiceName is "NDIS"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb0680 for PDO 0xfffffadf9eeb08a0
        InstancePath is "Root\LEGACY_NDISTAPI\0000"
        ServiceName is "NdisTapi"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb02a0 for PDO 0xfffffadf9eeb04c0
        InstancePath is "Root\LEGACY_NDISUIO\0000"
        ServiceName is "Ndisuio"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd6e40 for PDO 0xfffffadf9ebd6060
        InstancePath is "Root\LEGACY_NDPROXY\0000"
        ServiceName is "NDProxy"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd6a60 for PDO 0xfffffadf9ebd6c80
        InstancePath is "Root\LEGACY_NETBT\0000"
        ServiceName is "NetBT"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd6680 for PDO 0xfffffadf9ebd68a0
        InstancePath is "Root\LEGACY_NULL\0000"
        ServiceName is "Null"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd62a0 for PDO 0xfffffadf9ebd64c0
        InstancePath is "Root\LEGACY_PARTMGR\0000"
        ServiceName is "PartMgr"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeafe40 for PDO 0xfffffadf9eeaf060
        InstancePath is "Root\LEGACY_RASACD\0000"
        ServiceName is "RasAcd"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeafa60 for PDO 0xfffffadf9eeafc80
        InstancePath is "Root\LEGACY_RDPCDD\0000"
        ServiceName is "RDPCDD"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeaf680 for PDO 0xfffffadf9eeaf8a0
        InstancePath is "Root\LEGACY_SECDRV\0000"
        ServiceName is "Secdrv"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeaf2a0 for PDO 0xfffffadf9eeaf4c0
        InstancePath is "Root\LEGACY_TCPIP\0000"
        ServiceName is "Tcpip"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd5e40 for PDO 0xfffffadf9ebd5060
        InstancePath is "Root\LEGACY_VGASAVE\0000"
        ServiceName is "VgaSave"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd5a60 for PDO 0xfffffadf9ebd5c80
        InstancePath is "Root\LEGACY_VOLSNAP\0000"
        ServiceName is "VolSnap"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd5680 for PDO 0xfffffadf9ebd58a0
        InstancePath is "Root\LEGACY_WANARP\0000"
        ServiceName is "Wanarp"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd52a0 for PDO 0xfffffadf9ebd54c0
        InstancePath is "Root\MEDIA\MS_MMACM"
        ServiceName is "audstub"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9eeaee40 for PDO 0xfffffadf9eeae060
        InstancePath is "Root\MEDIA\MS_MMDRV"
        ServiceName is "audstub"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9eeaea60 for PDO 0xfffffadf9eeaec80
        InstancePath is "Root\MEDIA\MS_MMMCI"
        ServiceName is "audstub"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9eeae680 for PDO 0xfffffadf9eeae8a0
        InstancePath is "Root\MEDIA\MS_MMVCD"
        ServiceName is "audstub"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9eeae2a0 for PDO 0xfffffadf9eeae4c0
        InstancePath is "Root\MEDIA\MS_MMVID"
        ServiceName is "audstub"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9ebd4e40 for PDO 0xfffffadf9ebd4060
        InstancePath is "Root\MS_L2TPMINIPORT\0000"
        ServiceName is "Rasl2tp"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9ebd4a60 for PDO 0xfffffadf9ebd4c80
        InstancePath is "Root\MS_NDISWANIP\0000"
        ServiceName is "NdisWan"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9ebd4680 for PDO 0xfffffadf9ebd48a0
        InstancePath is "Root\MS_PPPOEMINIPORT\0000"
        ServiceName is "RasPppoe"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9ebd42a0 for PDO 0xfffffadf9ebd44c0
        InstancePath is "Root\MS_PPTPMINIPORT\0000"
        ServiceName is "PptpMiniport"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9eeade40 for PDO 0xfffffadf9eead060
        InstancePath is "Root\MS_PSCHEDMP\0000"
        ServiceName is "PSched"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9eeada60 for PDO 0xfffffadf9eeadc80
        InstancePath is "Root\MS_PSCHEDMP\0001"
        ServiceName is "PSched"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9eead680 for PDO 0xfffffadf9eead8a0
        InstancePath is "Root\MS_PTIMINIPORT\0000"
        ServiceName is "Raspti"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9eead2a0 for PDO 0xfffffadf9eead4c0
        InstancePath is "Root\RDPDR\0000"
        ServiceName is "rdpdr"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9ebd3e40 for PDO 0xfffffadf9ebd3060
        InstancePath is "Root\RDP_KBD\0000"
        ServiceName is "TermDD"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9ebd3a60 for PDO 0xfffffadf9ebd3c80
        InstancePath is "Root\RDP_MOU\0000"
        ServiceName is "TermDD"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9ebd3680 for PDO 0xfffffadf9ebd38a0
        InstancePath is "Root\SYSTEM\0000"
        ServiceName is "swenum"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9ebd32a0 for PDO 0xfffffadf9ebd34c0
        InstancePath is "Root\SYSTEM\0001"
        ServiceName is "update"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9eeace40 for PDO 0xfffffadf9eeac060
        InstancePath is "Root\SYSTEM\0002"
        ServiceName is "mssmbios"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
    15: kd> !PCItree
    Bus 0x0 (FDO Ext fffffadf9e0dce80)
      0600 14501022 (d=0,  f=0) devext fffffadf9efd91b0 Bridge/HOST to PCI
      0806 14511022 (d=0,  f=2) devext fffffadf9efd9570 Base System Device/Unknown Sub Class
      0600 14521022 (d=1,  f=0) devext fffffadf9dffbe90 Bridge/HOST to PCI
      0604 14531022 (d=1,  f=2) devext fffffadf9dffbb70 Bridge/PCI to PCI
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: pci!PCI_FDO_EXTENSION                         ***
    ***                                                                   ***

    *************************************************************************
      Bus 0x0 (FDO Ext 00000000)
      No devices have been enumerated on this bus.
      0600 14521022 (d=2,  f=0) devext fffffadf9dffb850 Bridge/HOST to PCI
      0600 14521022 (d=3,  f=0) devext fffffadf9e0dc1b0 Bridge/HOST to PCI
      0604 14531022 (d=3,  f=1) devext fffffadf9e0dcb80 Bridge/PCI to PCI
    *************************************************************************

    ***************
      Bus 0x0 (FDO Ext 00000000)
      No devices have been enumerated on this bus.
      0600 14521022 (d=4,  f=0) devext fffffadf9e0dc860 Bridge/HOST to PCI
      0600 14521022 (d=7,  f=0) devext fffffadf9e0dc540 Bridge/HOST to PCI
      0604 14541022 (d=7,  f=1) devext fffffadf9e8a01b0 Bridge/PCI to PCI
    *************************************************************************

    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: pci!FDO_EXTENSION                             ***
    ***                                                                   ***
    *************************************************************************

    *************************************************************************
      Bus 0x0 (FDO Ext 00000000)
      No devices have been enumerated on this bus.
      0600 14521022 (d=8,  f=0) devext fffffadf9e8a0e90 Bridge/HOST to PCI
      0604 14541022 (d=8,  f=1) devext fffffadf9e8a0b70 Bridge/PCI to PCI
    *************************************************************************

    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: pci!FDO_EXTENSION                             ***
    ***                                                                   ***
    *************************************************************************

      Bus 0x0 (FDO Ext 00000000)
      No devices have been enumerated on this bus.
      0c05 790b1022 (d=14, f=0) devext fffffadf9e8a0850 Serial Bus Controller/Unknown Sub Class
      0601 790e1022 (d=14, f=3) devext fffffadf9e8a0530 Bridge/PCI to ISA
      0600 14601022 (d=18, f=0) devext fffffadf9eacf1b0 Bridge/HOST to PCI
      0600 14611022 (d=18, f=1) devext fffffadf9eacfe90 Bridge/HOST to PCI
      0600 14621022 (d=18, f=2) devext fffffadf9eacfb70 Bridge/HOST to PCI
      0600 14631022 (d=18, f=3) devext fffffadf9eacf850 Bridge/HOST to PCI
      0600 14641022 (d=18, f=4) devext fffffadf9eacf530 Bridge/HOST to PCI
      0600 14651022 (d=18, f=5) devext fffffadf9efd81b0 Bridge/HOST to PCI
      0600 14661022 (d=18, f=6) devext fffffadf9efd8e90 Bridge/HOST to PCI
      0600 14671022 (d=18, f=7) devext fffffadf9efd8b70 Bridge/HOST to PCI
    Total PCI Root busses processed = 1
    15: kd> !PCI
    PCI Segment 0 Bus 0
    00:0  1022:1450.00  Cmd[0000:......]  Sts[0000:.....]  AMD Host Bridge  SubID:1043:8747
    00:2  1022:1451.00  Cmd[0004:..b...]  Sts[0010:c....]  AMD Class:8:6:0  SubID:1043:8747
    01:0  1022:1452.00  Cmd[0000:......]  Sts[0000:.....]  AMD Host Bridge
    01:2  1022:1453.00  Cmd[0007:imb...]  Sts[0010:c....]  AMD PCI-PCI Bridge 0->0x1-0x6
    02:0  1022:1452.00  Cmd[0000:......]  Sts[0000:.....]  AMD Host Bridge
    03:0  1022:1452.00  Cmd[0000:......]  Sts[0000:.....]  AMD Host Bridge
    03:1  1022:1453.00  Cmd[0007:imb...]  Sts[0010:c....]  AMD PCI-PCI Bridge 0->0x7-0x7
    04:0  1022:1452.00  Cmd[0000:......]  Sts[0000:.....]  AMD Host Bridge
    07:0  1022:1452.00  Cmd[0000:......]  Sts[0000:.....]  AMD Host Bridge
    07:1  1022:1454.00  Cmd[0007:imb...]  Sts[0010:c....]  AMD PCI-PCI Bridge 0->0x8-0x8
    08:0  1022:1452.00  Cmd[0000:......]  Sts[0000:.....]  AMD Host Bridge
    08:1  1022:1454.00  Cmd[0007:imb...]  Sts[0010:c....]  AMD PCI-PCI Bridge 0->0x9-0x9
    14:0  1022:790b.59  Cmd[0403:im....]  Sts[0220:.6...]  AMD SMBus Controller  SubID:1043:8747
    14:3  1022:790e.51  Cmd[000f:imb...]  Sts[0220:.6...]  AMD ISA Bridge  SubID:1043:8747
    18:0  1022:1460.00  Cmd[0000:......]  Sts[0000:.....]  AMD Host Bridge
    18:1  1022:1461.00  Cmd[0000:......]  Sts[0000:.....]  AMD Host Bridge
    18:2  1022:1462.00  Cmd[0000:......]  Sts[0000:.....]  AMD Host Bridge
    18:3  1022:1463.00  Cmd[0000:......]  Sts[0000:.....]  AMD Host Bridge
    18:4  1022:1464.00  Cmd[0000:......]  Sts[0000:.....]  AMD Host Bridge
    18:5  1022:1465.00  Cmd[0000:......]  Sts[0000:.....]  AMD Host Bridge
    18:6  1022:1466.00  Cmd[0000:......]  Sts[0000:.....]  AMD Host Bridge
    18:7  1022:1467.00  Cmd[0000:......]  Sts[0000:.....]  AMD Host Bridge
    1f

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Opened \\.\com1
    Waiting to reconnect...
    Connected to Windows Server 2003 3790 x64 target at (Sun Sep  1 13:39:29.250 2019 (UTC + 2:00)), ptr64 TRUE
    Kernel Debugger connection established.
    WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
    Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
    *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
    Executable search path is: C:\localsymbols
    Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64
    Built by: 3790.srv03_sp2_rtm.070216-1710
    Machine Name:
    Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d5100
    System Uptime: not available

    *** Fatal System Error: 0x0000000a
                           (0x0000000000000010,0x000000000000000C,0x0000000000000000,0xFFFFF8000107984D)

    Break instruction exception - code 80000003 (first chance)

    A fatal system error has occurred.
    Debugger entered on first try; Bugcheck callbacks have not been invoked.

    A fatal system error has occurred.

    Connected to Windows Server 2003 3790 x64 target at (Sun Sep  1 13:39:41.703 2019 (UTC + 2:00)), ptr64 TRUE
    Loading Kernel Symbols
    ........................
    Loading User Symbols

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {10, c, 0, fffff8000107984d}

    *** No owner thread found for resource fffff800011dda40
    *** No owner thread found for resource fffff800011dda40
    *** No owner thread found for resource fffff800011dda40
    *** No owner thread found for resource fffff800011dda40
    *** No owner thread found for resource fffff800011dda40
    *** No owner thread found for resource fffff800011dda40
    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+207 )

    Followup: MachineOwner
    ---------

    nt!DbgBreakPointWithStatus:
    fffff800`01026db0 cc              int     3
    15: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000000000010, memory referenced
    Arg2: 000000000000000c, IRQL
    Arg3: 0000000000000000, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff8000107984d, address which referenced memory

    Debugging Details:
    ------------------

    *** No owner thread found for resource fffff800011dda40
    *** No owner thread found for resource fffff800011dda40
    *** No owner thread found for resource fffff800011dda40
    *** No owner thread found for resource fffff800011dda40
    *** No owner thread found for resource fffff800011dda40
    *** No owner thread found for resource fffff800011dda40

    READ_ADDRESS:  0000000000000010

    CURRENT_IRQL:  c

    FAULTING_IP:
    nt!IopCompleteRequest+8e0
    fffff800`0107984d 4c8b4810        mov     r9,qword ptr [rax+10h]

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0xA

    PROCESS_NAME:  System

    IRP_ADDRESS:  ffffffffffffff88

    TRAP_FRAME:  fffffadf93607310 -- (.trap 0xfffffadf93607310)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffadf9334b7f0
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8000107984d rsp=fffffadf936074a0 rbp=fffffadf936075e0
     r8=0000000000000000  r9=fffffadf93607578 r10=fffff800011dcd28
    r11=fffff80001032de0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!IopCompleteRequest+0x8e0:
    fffff800`0107984d 4c8b4810        mov     r9,qword ptr [rax+10h] ds:6080:0010=????????????????
    Resetting default scope

    LOCK_ADDRESS:  fffff800011ddb40 -- (!locks fffff800011ddb40)
    The state of the ACPI locks is:
      - Build Queue Lock is not owned
      - Button Lock is not owned
      - Device Tree Lock is not owned
      - Fatal Lock is not owned
      - Power Lock is not owned
      - Get Lock is not owned
      - Power Queue Lock is not owned
      - Thermal Lock is not owned
      - Update Flags Lock is not owned
      - Worker Lock is not owned

    PNP_TRIAGE:
    	Lock address  : 0xfffff800011ddb40
    	Thread Count  : 1
    	Thread address: 0xfffffadf9ee91bf0
    	Thread wait   : 0x9d

    LAST_CONTROL_TRANSFER:  from fffff800010d673e to fffff80001026db0

    STACK_TEXT:
    fffffadf`93606aa8
     fffff800`010d673e : 00000000`0000000f 00000000`00000000
    00000000`00000010 fffff800`0105669e : nt!DbgBreakPointWithStatus
    fffffadf`93606ab0
     fffff800`010d7d0e : fffff800`00000003 00000000`0000000a
    00000000`00000010 00000000`0000000c : nt!KiBugCheckDebugBreak+0x1e
    fffffadf`93606b10
     fffff800`0102ea54 : fffffadf`93607180 00000000`00000180
    00000006`00000000 fffffa80`0045c4b0 : nt!KeBugCheck2+0x640
    fffffadf`93607150
     fffff800`0102e674 : 00000000`0000000a 00000000`00000010
    00000000`0000000c 00000000`00000000 : nt!KeBugCheckEx+0x104
    fffffadf`93607190
     fffff800`0102d607 : 00000000`00000000 fffffadf`93607420
    fffffadf`93607300 fffffadf`00000240 : nt!KiBugCheckDispatch+0x74
    fffffadf`93607310
     fffff800`0107984d : 00000000`00000000 fffffadf`9ee91bf0
    fffffadf`93607728 fffffa80`0045e150 : nt!KiPageFault+0x207
    fffffadf`936074a0
     fffff800`01027f81 : 00000000`00000000 fffff800`012966ee
    00020019`0047e401 fffffadf`9ebd9b00 : nt!IopCompleteRequest+0x8e0
    fffffadf`93607540
     fffff800`01027b8d : 00000000`00000000 00000000`00000000
    00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x215
    fffffadf`936075e0
     fffff800`012857c3 : 00000000`00020019 fffffadf`9eeb6080
    fffffa80`0045e150 00000000`00000000 : nt!KiApcInterrupt+0xdd
    fffffadf`93607770
     fffff800`0129b22b : fffffadf`0008e888 fffffadf`93607d30
    fffffadf`93607988 fffff800`011aa8fd : nt!ObOpenObjectByName+0xac
    fffffadf`93607960
     fffff800`0102e3fd : fffffadf`93607c40 fffff800`00020019
    fffffadf`93607c58 fffffadf`9ee91bf0 : nt!NtOpenKey+0x277
    fffffadf`93607a60
     fffff800`0102e8c0 : fffff800`0133dbe6 fffffadf`93607c58
    ffffffff`80000194 00000000`00000014 : nt!KiSystemServiceCopyEnd+0x3
    fffffadf`93607bf8
     fffff800`0133dbe6 : fffffadf`93607c58 ffffffff`80000194
    00000000`00000014 ffffffff`80000194 : nt!KiServiceLinkage
    fffffadf`93607c00
     fffff800`0133db61 : fffffadf`9eeaea60 fffffadf`93608068
    fffffadf`93608048 fffffadf`9eeaea60 : nt!PpSaveDeviceCapabilities+0x66
    fffffadf`93607ca0
     fffff800`0134cd61 : 00000000`00000000 fffffadf`93608068
    fffffadf`93608048 fffffadf`9eeaea60 :
    nt!IopQueryAndSaveDeviceNodeCapabilities+0xc0
    fffffadf`93607d60
    fffff800`01339aae : ffffffff`80000194 fffffadf`9ebda420
    00000000`00000000 00000000`00000000 :
    nt!IopInitializeDeviceInstanceKey+0x62f
    fffffadf`93607e20
    fffff800`0134c6fd : 00000000`00000000 00000000`00000020
    00000000`00000010 00000000`00000086 : nt!PipApplyFunctionToSubKeys+0x151
    fffffadf`93607ef0
     fffff800`01339aae : 00000000`00000000 00000000`0000006a
    00000000`00000001 fffffa80`00484360 : nt!IopInitializeDeviceKey+0x9d
    fffffadf`93607f30
     fffff800`0134c50a : 00000000`00000000 00000000`0000001a
    fffffadf`9eeb38f0 00000000`00000000 : nt!PipApplyFunctionToSubKeys+0x151
    fffffadf`93608000
     fffff800`0134bbf8 : fffffadf`9ebda350 00000000`00000000
    fffffadf`9eeb38f0 00000000`00000000 : nt!IopGetRootDevices+0x18a
    fffffadf`936080d0
     fffff800`0133ed04 : fffffadf`9ebda350 fffffadf`936081d0
    fffffadf`9eeb38f0 fffffadf`9eeb4900 : nt!IopPnPDispatch+0xc8
    fffffadf`93608140
     fffff800`010d0891 : 00000000`00000000 00000000`00000002
    00000000`00000000 fffffadf`9eeb47c0 : nt!IopSynchronousCall+0x144
    fffffadf`936081b0
     fffff800`01335a3a : fffffa80`0046d170 fffffa80`000a7500
    fffffadf`93608290 00000000`00000000 : nt!IopQueryDeviceRelations+0x71
    fffffadf`93608240
     fffff800`013376e5 : 00000000`00000000 fffffadf`9eeb4880
    00000000`00000002 fffffadf`9eeb3ab0 : nt!PipProcessDevNodeTree+0x342
    fffffadf`936085d0
     fffff800`010cc9d8 : fffffadf`00000003 00000000`00000000
    fffffadf`9eeb38f0 00000000`00000000 : nt!PiProcessReenumeration+0x85
    fffffadf`93608620
     fffff800`010cc63b : 00000000`00000000 fffffadf`9eeb3ab0
    fffff800`0134a4f0 fffffadf`9eeb38f0 : nt!PipDeviceActionWorker+0x368
    fffffadf`936086b0
     fffff800`01431545 : fffffadf`00000001 00000000`00000000
    00000000`00000000 fffffadf`9eeb38f0 : nt!PipRequestDeviceAction+0x1ab
    fffffadf`93608710
     fffff800`0142a040 : 00000000`00000000 00000000`0000fffc
    fffff800`00091448 fffff800`0146a68e :
    nt!IopInitializePlugPlayServices+0xd80
    fffffadf`936088c0
    fffff800`01428144 : fffff800`00091598 fffff800`00091598
    00000000`00000003 fffffadf`9ee90010 : nt!IoInitSystem+0xe41
    fffffadf`93608a50
     fffff800`0130dc29 : 12d93b24`1e99bf20 fffffadf`9ee91bf0
    00000000`00000080 fffffadf`9ee91bf0 :
    nt!Phase1InitializationDiscard+0x111d
    fffffadf`93608d40
    fffff800`0124b972 : b6e6174a`baa6174e 8dd685ea`819685ee
    307b39e5`3cbb19e1 0b4bab45`070baf41 : nt!Phase1Initialization+0x9
    fffffadf`93608d70
     fffff800`010202d6 : fffff800`011b1180 fffffadf`9ee91bf0
    fffff800`011b5500 00000000`da83b888 : nt!PspSystemThreadStartup+0x3e
    fffffadf`93608dd0
     00000000`00000000 : 00000000`00000000 00000000`00000000
    00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!KiPageFault+207
    fffff800`0102d607 488d0572300000  lea     rax,[nt!ExpInterlockedPopEntrySList (fffff800`01030680)]

    SYMBOL_STACK_INDEX:  5

    SYMBOL_NAME:  nt!KiPageFault+207

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  45d69ab4

    FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+207

    BUCKET_ID:  X64_0xA_nt!KiPageFault+207

    Followup: MachineOwner
    ---------

#2198 | infuscomus | ⇗ @diderius6 does windows XP x64 install properly with Standard PC or MPS?
#2199 | diderius6 | ⇗ @infuscomus There is nothing like this in XP 64 and so it is more difficult Dietmar

#2200

diderius6

⇗ @daniel_k
Here is the Windbg output from
5048 acpi_test1.sys from yesterday (first from 3)
with nondebug Ntoskrnl.exe and Hal.dll
Dietmar

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Opened \\.\com1
    Waiting to reconnect...
    Connected to Windows Server 2003 3790 x64 target at (Sun Sep  1 14:02:36.906 2019 (UTC + 2:00)), ptr64 TRUE
    Kernel Debugger connection established.
    WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
    Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
    *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
    Executable search path is: C:\localsymbols
    Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64
    Built by: 3790.srv03_sp2_rtm.070216-1710
    Machine Name:
    Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d5100
    System Uptime: not available

    *** Fatal System Error: 0x0000007e
                           (0xFFFFFFFFC0000005,0xFFFFFADF92D9D923,0xFFFFFADF93607540,0xFFFFFADF93606F50)

    Break instruction exception - code 80000003 (first chance)

    A fatal system error has occurred.
    Debugger entered on first try; Bugcheck callbacks have not been invoked.

    A fatal system error has occurred.

    Connected to Windows Server 2003 3790 x64 target at (Sun Sep  1 14:02:49.671 2019 (UTC + 2:00)), ptr64 TRUE
    Loading Kernel Symbols
    ........................
    Loading User Symbols

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7E, {ffffffffc0000005, fffffadf92d9d923, fffffadf93607540, fffffadf93606f50}

    *** ERROR: Module load completed but symbols could not be loaded for ACPI.sys
    *** No owner thread found for resource fffff800011dda40
    *** No owner thread found for resource fffff800011dda40
    *** No owner thread found for resource fffff800011dda40
    *** No owner thread found for resource fffff800011dda40
    Probably caused by : ACPI.sys ( ACPI+19923 )

    Followup: MachineOwner
    ---------

    nt!DbgBreakPointWithStatus:
    fffff800`01026db0 cc              int     3
    15: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffffadf92d9d923, The address that the exception occurred at
    Arg3: fffffadf93607540, Exception Record Address
    Arg4: fffffadf93606f50, Context Record Address

    Debugging Details:
    ------------------

    *** No owner thread found for resource fffff800011dda40
    *** No owner thread found for resource fffff800011dda40
    *** No owner thread found for resource fffff800011dda40
    *** No owner thread found for resource fffff800011dda40

    EXCEPTION_CODE:
     (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher
    bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x"
    nicht in den Arbeitsspeicher  bertragen.

    FAULTING_IP:
    ACPI+19923
    fffffadf`92d9d923 41ff5620        call    qword ptr [r14+20h]

    EXCEPTION_RECORD:  fffffadf93607540 -- (.exr 0xfffffadf93607540)
    ExceptionAddress: fffffadf92d9d923 (ACPI+0x0000000000019923)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000020
    Attempt to read from address 0000000000000020

    CONTEXT:  fffffadf93606f50 -- (.cxr 0xfffffadf93606f50)
    rax=fffffadf936077b0 rbx=fffffadf92dd3b40 rcx=fffffadf9ee97290
    rdx=fffffadf936077d0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffffadf92d9d923 rsp=fffffadf93607760 rbp=fffffadf9ee97290
     r8=fffffadf936077b4  r9=fffffadf936077b3 r10=0000000000000001
    r11=fffffadf936079a8 r12=fffffadf936079f0 r13=fffffadf92dd3b00
    r14=0000000000000000 r15=fffffadf936079f8
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    ACPI+0x19923:
    fffffadf`92d9d923 41ff5620        call    qword ptr [r14+20h] ds:002b:00000000`00000020=????????????????
    Resetting default scope

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    ERROR_CODE:
     (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher
    bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x"
    nicht in den Arbeitsspeicher  bertragen.

    EXCEPTION_PARAMETER1:  0000000000000000

    EXCEPTION_PARAMETER2:  0000000000000020

    READ_ADDRESS:  0000000000000020

    FOLLOWUP_IP:
    ACPI+19923
    fffffadf`92d9d923 41ff5620        call    qword ptr [r14+20h]

    BUGCHECK_STR:  0x7E

    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

    LOCK_ADDRESS:  fffff800011ddb40 -- (!locks fffff800011ddb40)
    The state of the ACPI locks is:
    ACPI: Could not read acpi!AcpiBuildQueueLock
    ACPI: Could not read acpi!AcpiButtonLock
    ACPI: Could not read acpi!AcpiDeviceTreeLock
    ACPI: Could not read acpi!AcpiFatalLock
    ACPI: Could not read acpi!AcpiPowerLock
    ACPI: Could not read acpi!AcpiGetLock
    ACPI: Could not read acpi!AcpiPowerQueueLock
    ACPI: Could not read acpi!AcpiThermalLock
    ACPI: Could not read acpi!AcpiUpdateFlagsLock
    ACPI: Could not read acpi!AcpiWorkerSpinLock

    PNP_TRIAGE:
    	Lock address  : 0xfffff800011ddb40
    	Thread Count  : 1
    	Thread address: 0xfffffadf9ee91bf0
    	Thread wait   : 0xab

    LAST_CONTROL_TRANSFER:  from fffff800010d673e to fffff80001026db0

    STACK_TEXT:
    fffffadf`93607760 fffffadf`92ddec12 : 00000000`00000001 fffff800`0137de62 fffffadf`00000101 fffff800`0137eb82 : ACPI+0x19923
    fffffadf`936079b0 fffffadf`92de8136 : fffffadf`92dd3b40 fffffadf`93607bb0 fffffa80`0044a4e8 fffffadf`93607bb0 : ACPI+0x5ac12
    fffffadf`93607a30 fffffadf`92ddf2b2 : fffffadf`92dd3b40 fffffa80`00459f30 00000000`00000009 fffffadf`93607bb0 : ACPI+0x64136
    fffffadf`93607b10 fffffadf`92de826f : 00000000`00000000 fffffa80`00459f30 00000000`00000009 00000000`00000000 : ACPI+0x5b2b2
    fffffadf`93607b40 fffff800`01330d16 : fffffa80`0044a4c0 fffffa80`0045abe8 fffffa80`0045abc0 fffffadf`93607ba0 : ACPI+0x6426f
    fffffadf`93607b80
     fffff800`01330b03 : 00000000`00000000 fffffa80`00459f30
    fffffa80`0044a460 fffffadf`9e1c0360 : nt!IopBootAllocation+0x14b
    fffffadf`93607be0
     fffff800`01330a07 : fffffa80`004695d0 fffffadf`9ee97290
    00000000`00000004 fffffadf`9ee97290 :
    nt!IopAllocateBootResourcesInternal+0x93
    fffffadf`93607c70
    fffff800`014303ab : 00000000`00000010 fffffadf`9e1c0360
    fffffa80`004695d0 00000000`00000004 : nt!IopAllocateBootResources+0x57
    fffffadf`93607cb0
     fffff800`013319e6 : 00000000`00000000 ffffffff`800001d8
    fffffadf`9e1c0360 fffffa80`004695d0 : nt!IopReportBootResources+0xc1
    fffffadf`93607ce0
     fffff800`01333334 : ffffffff`800001e4 fffffadf`9e1c0420
    fffffadf`9e1c0360 ffffffff`800001e4 :
    nt!PiQueryAndAllocateBootResources+0x276
    fffffadf`93607da0
    fffff800`0133591b : fffffadf`9eab9190 fffffadf`9e1c0360
    00000000`00000000 fffffadf`9e1c0360 : nt!PiProcessNewDeviceNode+0x16ff
    fffffadf`93608140
     fffff800`010cc809 : fffffadf`9eeb3870 fffff800`00092470
    fffffadf`9eeb38c0 fffffadf`9eeb3870 : nt!PipProcessDevNodeTree+0x223
    fffffadf`936084d0
     fffff800`014329f7 : ffffffff`00000000 fffffadf`9eeb3870
    fffff800`00092470 fffffadf`9eeb38f0 : nt!PipDeviceActionWorker+0x199
    fffffadf`93608560
     fffff800`0142a14d : 00000000`00000000 00000000`0000fffc
    00000000`00000000 00000000`0000fffc : nt!IopInitializeBootDrivers+0xc57
    fffffadf`936088c0
     fffff800`01428144 : fffff800`00091598 fffff800`00091598
    00000000`00000003 fffffadf`9ee90010 : nt!IoInitSystem+0xf4f
    fffffadf`93608a50
     fffff800`0130dc29 : 12d93b24`1e99bf20 fffffadf`9ee91bf0
    00000000`00000080 fffffadf`9ee91bf0 :
    nt!Phase1InitializationDiscard+0x111d
    fffffadf`93608d40
    fffff800`0124b972 : b6e6174a`baa6174e 8dd685ea`819685ee
    307b39e5`3cbb19e1 0b4bab45`070baf41 : nt!Phase1Initialization+0x9
    fffffadf`93608d70
     fffff800`010202d6 : fffff800`011b1180 fffffadf`9ee91bf0
    fffff800`011b5500 00000000`da83b888 : nt!PspSystemThreadStartup+0x3e
    fffffadf`93608dd0
     00000000`00000000 : 00000000`00000000 00000000`00000000
    00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  ACPI+19923

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: ACPI

    IMAGE_NAME:  ACPI.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  424d79aa

    STACK_COMMAND:  .cxr 0xfffffadf93606f50 ; kb

    FAILURE_BUCKET_ID:  X64_0x7E_ACPI+19923

    BUCKET_ID:  X64_0x7E_ACPI+19923

    Followup: MachineOwner
    ---------

    15: kd> !devnode 0 1
    Dumping IopRootDeviceNode (= 0xfffffadf9eeb47c0)
    DevNode 0xfffffadf9eeb47c0 for PDO 0xfffffadf9eeb38f0
      InstancePath is "HTREE\ROOT\0"
      State = DeviceNodeStarted (0x308)
      Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd9c30 for PDO 0xfffffadf9ebd9e50
        InstancePath is "Root\ACPI_HAL\0000"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
        DevNode 0xfffffadf9eeac870 for PDO 0xfffffadf9eeac480
          InstancePath is "ACPI_HAL\PNP0C08\0"
          ServiceName is "ACPI"
          State = DeviceNodeStarted (0x308)
          Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9ee96e40 for PDO 0xfffffadf9eabe1b0
            InstancePath is "ACPI\PNP0C14\AWW"
            ServiceName is "WmiAcpi"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
          DevNode 0xfffffadf9eea4190 for PDO 0xfffffadf9eeb3600
            InstancePath is "ACPI\PNP0A08\0"
            ServiceName is "pci"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
          DevNode 0xfffffadf9eab9190 for PDO 0xfffffadf9eeb3e20
            InstancePath is "ACPI\PNP0C0C\aa"
            State = DeviceNodeDriversAdded (0x303)
            Previous State = DeviceNodeInitialized (0x302)
          DevNode 0xfffffadf9e1c0360 for PDO 0xfffffadf9ee97290
            InstancePath is "ACPI\PNP0103\2&daba3ff&0"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_NOT_CONFIGURED
          DevNode 0xfffffadf9eeb3100 for PDO 0xfffffadf9ebd2a60
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9ee95a40 for PDO 0xfffffadf9e1beab0
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9e1bfb10 for PDO 0xfffffadf9eeb3320
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9e1bf940 for PDO 0xfffffadf9ebd26e0
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9e1bf770 for PDO 0xfffffadf9ebd24e0
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9e1bf5a0 for PDO 0xfffffadf9e0cd060
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9e1bf3d0 for PDO 0xfffffadf9e0cd410
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9e1bf200 for PDO 0xfffffadf9e1c0780
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9e8d0010 for PDO 0xfffffadf9e1c0580
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9e8d0c90 for PDO 0xfffffadf9ee95e60
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9e8d0ac0 for PDO 0xfffffadf9ee95c60
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9e8d08f0 for PDO 0xfffffadf9e1be720
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9e8d0720 for PDO 0xfffffadf9e1be520
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9e8d0550 for PDO 0xfffffadf9e1be320
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9e8d0380 for PDO 0xfffffadf9ee96600
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9e1bd010 for PDO 0xfffffadf9ee96400
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9e1bde40 for PDO 0xfffffadf9ee96200
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9e1bdc70 for PDO 0xfffffadf9ee97dc0
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9e1bdaa0 for PDO 0xfffffadf9ee97bc0
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9e1bd8d0 for PDO 0xfffffadf9ee979c0
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9e1bd700 for PDO 0xfffffadf9ee977c0
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
          DevNode 0xfffffadf9e1bd530 for PDO 0xfffffadf9ee975c0
            State = DeviceNodeUninitialized (0x301)
            Previous State = Unknown State (0x0)
      DevNode 0xfffffadf9ebd9720 for PDO 0xfffffadf9ebd9940
        InstancePath is "Root\dmio\0000"
        ServiceName is "dmio"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9ebd9550 for PDO 0xfffffadf9eeb2060
        InstancePath is "Root\ftdisk\0000"
        ServiceName is "ftdisk"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9eeb2be0 for PDO 0xfffffadf9eeb2e00
        InstancePath is "Root\LEGACY_AFD\0000"
        ServiceName is "AFD"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb2800 for PDO 0xfffffadf9eeb2a20
        InstancePath is "Root\LEGACY_AMPA\0000"
        ServiceName is "ampa"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb2420 for PDO 0xfffffadf9eeb2640
        InstancePath is "Root\LEGACY_BEEP\0000"
        ServiceName is "Beep"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb2250 for PDO 0xfffffadf9ebd8060
        InstancePath is "Root\LEGACY_CDAC15BA\0000"
        ServiceName is "CdaC15BA"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd8c30 for PDO 0xfffffadf9ebd8e50
        InstancePath is "Root\LEGACY_CDAD10BA\0000"
        ServiceName is "CdaD10BA"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd8750 for PDO 0xfffffadf9ebd8970
        InstancePath is "Root\LEGACY_CRCDISK\0000"
        ServiceName is "crcdisk"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd8370 for PDO 0xfffffadf9ebd8590
        InstancePath is "Root\LEGACY_DMBOOT\0000"
        ServiceName is "dmboot"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb1e40 for PDO 0xfffffadf9eeb1060
        InstancePath is "Root\LEGACY_DMLOAD\0000"
        ServiceName is "dmload"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb1a60 for PDO 0xfffffadf9eeb1c80
        InstancePath is "Root\LEGACY_FIPS\0000"
        ServiceName is "Fips"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb1680 for PDO 0xfffffadf9eeb18a0
        InstancePath is "Root\LEGACY_GPC\0000"
        ServiceName is "Gpc"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb12a0 for PDO 0xfffffadf9eeb14c0
        InstancePath is "Root\LEGACY_HTTP\0000"
        ServiceName is "HTTP"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd7e40 for PDO 0xfffffadf9ebd7060
        InstancePath is "Root\LEGACY_IPNAT\0000"
        ServiceName is "IpNat"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd7a60 for PDO 0xfffffadf9ebd7c80
        InstancePath is "Root\LEGACY_IPSEC\0000"
        ServiceName is "IPSec"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd7680 for PDO 0xfffffadf9ebd78a0
        InstancePath is "Root\LEGACY_KSECDD\0000"
        ServiceName is "ksecdd"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd72a0 for PDO 0xfffffadf9ebd74c0
        InstancePath is "Root\LEGACY_MNMDD\0000"
        ServiceName is "mnmdd"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb0e40 for PDO 0xfffffadf9eeb0060
        InstancePath is "Root\LEGACY_MOUNTMGR\0000"
        ServiceName is "mountmgr"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb0a60 for PDO 0xfffffadf9eeb0c80
        InstancePath is "Root\LEGACY_NDIS\0000"
        ServiceName is "NDIS"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb0680 for PDO 0xfffffadf9eeb08a0
        InstancePath is "Root\LEGACY_NDISTAPI\0000"
        ServiceName is "NdisTapi"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeb02a0 for PDO 0xfffffadf9eeb04c0
        InstancePath is "Root\LEGACY_NDISUIO\0000"
        ServiceName is "Ndisuio"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd6e40 for PDO 0xfffffadf9ebd6060
        InstancePath is "Root\LEGACY_NDPROXY\0000"
        ServiceName is "NDProxy"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd6a60 for PDO 0xfffffadf9ebd6c80
        InstancePath is "Root\LEGACY_NETBT\0000"
        ServiceName is "NetBT"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd6680 for PDO 0xfffffadf9ebd68a0
        InstancePath is "Root\LEGACY_NULL\0000"
        ServiceName is "Null"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd62a0 for PDO 0xfffffadf9ebd64c0
        InstancePath is "Root\LEGACY_PARTMGR\0000"
        ServiceName is "PartMgr"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeafe40 for PDO 0xfffffadf9eeaf060
        InstancePath is "Root\LEGACY_RASACD\0000"
        ServiceName is "RasAcd"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeafa60 for PDO 0xfffffadf9eeafc80
        InstancePath is "Root\LEGACY_RDPCDD\0000"
        ServiceName is "RDPCDD"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeaf680 for PDO 0xfffffadf9eeaf8a0
        InstancePath is "Root\LEGACY_SECDRV\0000"
        ServiceName is "Secdrv"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9eeaf2a0 for PDO 0xfffffadf9eeaf4c0
        InstancePath is "Root\LEGACY_TCPIP\0000"
        ServiceName is "Tcpip"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd5e40 for PDO 0xfffffadf9ebd5060
        InstancePath is "Root\LEGACY_VGASAVE\0000"
        ServiceName is "VgaSave"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd5a60 for PDO 0xfffffadf9ebd5c80
        InstancePath is "Root\LEGACY_VOLSNAP\0000"
        ServiceName is "VolSnap"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd5680 for PDO 0xfffffadf9ebd58a0
        InstancePath is "Root\LEGACY_WANARP\0000"
        ServiceName is "Wanarp"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9ebd52a0 for PDO 0xfffffadf9ebd54c0
        InstancePath is "Root\MEDIA\MS_MMACM"
        ServiceName is "audstub"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9eeaee40 for PDO 0xfffffadf9eeae060
        InstancePath is "Root\MEDIA\MS_MMDRV"
        ServiceName is "audstub"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9eeaea60 for PDO 0xfffffadf9eeaec80
        InstancePath is "Root\MEDIA\MS_MMMCI"
        ServiceName is "audstub"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9eeae680 for PDO 0xfffffadf9eeae8a0
        InstancePath is "Root\MEDIA\MS_MMVCD"
        ServiceName is "audstub"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9eeae2a0 for PDO 0xfffffadf9eeae4c0
        InstancePath is "Root\MEDIA\MS_MMVID"
        ServiceName is "audstub"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9ebd4e40 for PDO 0xfffffadf9ebd4060
        InstancePath is "Root\MS_L2TPMINIPORT\0000"
        ServiceName is "Rasl2tp"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9ebd4a60 for PDO 0xfffffadf9ebd4c80
        InstancePath is "Root\MS_NDISWANIP\0000"
        ServiceName is "NdisWan"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9ebd4680 for PDO 0xfffffadf9ebd48a0
        InstancePath is "Root\MS_PPPOEMINIPORT\0000"
        ServiceName is "RasPppoe"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9ebd42a0 for PDO 0xfffffadf9ebd44c0
        InstancePath is "Root\MS_PPTPMINIPORT\0000"
        ServiceName is "PptpMiniport"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9eeade40 for PDO 0xfffffadf9eead060
        InstancePath is "Root\MS_PSCHEDMP\0000"
        ServiceName is "PSched"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9eeada60 for PDO 0xfffffadf9eeadc80
        InstancePath is "Root\MS_PSCHEDMP\0001"
        ServiceName is "PSched"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9eead680 for PDO 0xfffffadf9eead8a0
        InstancePath is "Root\MS_PTIMINIPORT\0000"
        ServiceName is "Raspti"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9eead2a0 for PDO 0xfffffadf9eead4c0
        InstancePath is "Root\RDPDR\0000"
        ServiceName is "rdpdr"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9ebd3e40 for PDO 0xfffffadf9ebd3060
        InstancePath is "Root\RDP_KBD\0000"
        ServiceName is "TermDD"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9ebd3a60 for PDO 0xfffffadf9ebd3c80
        InstancePath is "Root\RDP_MOU\0000"
        ServiceName is "TermDD"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9ebd3680 for PDO 0xfffffadf9ebd38a0
        InstancePath is "Root\SYSTEM\0000"
        ServiceName is "swenum"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9ebd32a0 for PDO 0xfffffadf9ebd34c0
        InstancePath is "Root\SYSTEM\0001"
        ServiceName is "update"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)
      DevNode 0xfffffadf9eeace40 for PDO 0xfffffadf9eeac060
        InstancePath is "Root\SYSTEM\0002"
        ServiceName is "mssmbios"
        State = DeviceNodeInitialized (0x302)
        Previous State = DeviceNodeUninitialized (0x301)

#2201 | diderius6 | ⇗ @daniel_k and here with DEBUG Ntoskrnl.exe and Hal.dll 5048 acpi_test1.sys from yesterday (first from 3). It is identic to post before Dietmar

#2202

diderius6

⇗ @daniel_k
Yessssssssssssssssssssaaaaaaaaaaaaaaaaaaaaa we got it!!!!!!!!!!!!!!!!!!!!!!!!
Dietmar
diderius6 has attached files to this post

- ⇗ acpiXP64Ryzen.rar

#2203

kukonosau

> Zitat von ⇗ diderius6 im Beitrag ¶ #2202

> @daniel_k
> Yessssssssssssssssssssaaaaaaaaaaaaaaaaaaaaaaaa we got it!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> Dietmar

T tell me about ACPI and hal.dll, please. How to start Windows XP x64 with modify ACPI and hal.dll? Where is two files modify?

#2204

kukonosau

> Zitat von ⇗ diderius6 im Beitrag ¶ #2202

> @daniel_k
> Yessssssssssssssssssssaaaaaaaaaaaaaaaaaaaaa we got it!!!!!!!!!!!!!!!!!!!!!!!!
> Dietmar

Jh, sorry, I am not to see file! I refreshed pages! I will check this file now.

#2205 | infuscomus | ⇗ @diderius6 I am curious to know - what was the problem? where was the fix needed?

## Page 148

#2206 | kukonosau | BSOD 0A(((

#2207

diderius6

⇗ @infuscomus
The problem was, that only one of the 3 STORAHCI devices on the asrock fatal1ty ab350 gaming k4 board was recogniced.
I noticed this strange behavior because of different BSODs with HD in different SATA slots yesterday.
After this I installed STORAHCI from ⇗ @skullteria via hand in registry of XP 64 again before each new try.
The endless loop is gone.
Here is the output from Windbg with DEBUG ntoskrnl.exe and Hal.dll
Dietmar
PS: The only difference between first acpi.sys 5048 from yesterday and from working is
18C97: 00 => 17

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Opened \\.\com1
    Waiting to reconnect...
    Connected to Windows Server 2003 3790 x64 target at (Sun Sep  1 14:42:44.468 2019 (UTC + 2:00)), ptr64 TRUE
    Kernel Debugger connection established.
    WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
    Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
    *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
    Executable search path is: C:\localsymbols
    Windows Server 2003 Kernel Version 3790 MP (1 procs) Checked x64
    Built by: 3790.srv03_sp2_rtm.070216-1710
    Machine Name:
    Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`013d1fd0
    System Uptime: not available
    AhciHwFindAdapter finishing
    AhciHwFindAdapter finishing
    AhciHwFindAdapter finishing
    KDTARGET: Refreshing KD connection
    HAL: RTC interrupt flag is not cleared by first read.
    RTC Status Register C = 0xc0
    HAL: RTC interrupt flag is not cleared by first read.
    RTC Status Register C = 0xc0

    HAL: RTC interrupt flag is not cleared by first read.
    RTC Status Register C = 0xd0
    Port lock was not acquired!
    AFD: AfdPprThreshold value queried from transport: 2960
    ERROR: DavReadRegistryValues/RegQueryValueExW(6). WStatus = 1309
    HAL: RTC interrupt flag is not cleared by first read.
    RTC Status Register C = 0xc0
    PipCallDriverAddDevice:			Unable to reference driver \Driver\amdxhc (c000026c)
    PipCallDriverAddDevice:			Unable to reference driver \Driver\amdxhc (c000026c)
    PipCallDriverAddDevice:			Unable to reference driver \Driver\amdxhc (c000026c)
    PipCallDriverAddDevice:			Unable to reference driver \Driver\amdxhc (c000026c)
    PipCallDriverAddDevice:			Unable to reference driver \Driver\amdxhc (c000026c)
    PipCallDriverAddDevice:			Unable to reference driver \Driver\amdxhc (c000026c)
    AhciHwFindAdapter finishing
    AhciHwFindAdapter finishing
    LPC[ 380.8a4 ]: Refusing connection from 380.3cc
    Port lock was not acquired!
    LPC[ 934.944 ]: Refusing connection from 934.938
    Break instruction exception - code 80000003 (first chance)
    *******************************************************************************
    *                                                                             *
    *   You are seeing this message because you pressed either                    *
    *       CTRL+C (if you run kd.exe) or,                                        *
    *       CTRL+BREAK (if you run WinDBG),                                       *
    *   on your debugger machine's keyboard.                                      *
    *                                                                             *
    *                   THIS IS NOT A BUG OR A SYSTEM CRASH                       *
    *                                                                             *
    * If you did not intend to break into the debugger, press the "g" key, then   *
    * press the "Enter" key now.  This message might immediately reappear.  If it *
    * does, press "g" and "Enter" again.                                          *
    *                                                                             *
    *******************************************************************************
    nt!RtlpBreakWithStatusInstruction:
    fffff800`011a02e0 cc              int     3

    4: kd> !devnode 0 1
    Dumping IopRootDeviceNode (= 0xfffffadf9e3338e0)
    DevNode 0xfffffadf9e3338e0 for PDO 0xfffffadf9e336d30
      InstancePath is "HTREE\ROOT\0"
      State = DeviceNodeStarted (0x308)
      Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e058c10 for PDO 0xfffffadf9e058e50
        InstancePath is "Root\ACPI_HAL\0000"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
        DevNode 0xfffffadf9e32cc10 for PDO 0xfffffadf9e32c820
          InstancePath is "ACPI_HAL\PNP0C08\0"
          ServiceName is "ACPI"
          State = DeviceNodeStarted (0x308)
          Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9e31ce30 for PDO 0xfffffadf9e050620
            InstancePath is "ACPI\PNP0C14\AWW"
            ServiceName is "WmiAcpi"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9f1e5180 for PDO 0xfffffadf9f1e08e0
            InstancePath is "ACPI\PNP0A08\0"
            ServiceName is "pci"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadf9dd11a10 for PDO 0xfffffadf9df03950
              InstancePath is "PCI\VEN_1022&DEV_1450&SUBSYS_00000000&REV_00\3&11583659&0&00"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadf9dd11830 for PDO 0xfffffadf9df03620
              InstancePath is "PCI\VEN_1022&DEV_1451&SUBSYS_87471043&REV_00\3&11583659&0&02"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
              Problem = CM_PROB_FAILED_INSTALL
            DevNode 0xfffffadf9dd11650 for PDO 0xfffffadf9df1d070
              InstancePath is "PCI\VEN_1022&DEV_1452&SUBSYS_00000000&REV_00\3&11583659&0&08"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadf9dd11470 for PDO 0xfffffadf9df1dd40
              InstancePath is "PCI\VEN_1022&DEV_1453&SUBSYS_00000000&REV_00\3&11583659&0&0A"
              ServiceName is "pci"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0xfffffadf9df01010 for PDO 0xfffffadf9f1d9720
                InstancePath is "PCI\VEN_1022&DEV_57AD&SUBSYS_00000000&REV_00\4&d487977&0&000A"
                ServiceName is "pci"
                State = DeviceNodeStarted (0x308)
                Previous State = DeviceNodeEnumerateCompletion (0x30d)
                DevNode 0xfffffadf9df1be30 for PDO 0xfffffadf9df01a30
                  InstancePath is "PCI\VEN_1022&DEV_57A3&SUBSYS_00000000&REV_00\5&1f331b67&0&28000A"
                  ServiceName is "pci"
                  State = DeviceNodeStarted (0x308)
                  Previous State = DeviceNodeEnumerateCompletion (0x30d)
                  DevNode 0xfffffadf9e317e30 for PDO 0xfffffadf9dc51720
                    InstancePath is "PCI\VEN_8086&DEV_1539&SUBSYS_85F01043&REV_03\6&12f3bd8&0&0028000A"
                    State = DeviceNodeInitialized (0x302)
                    Previous State = DeviceNodeUninitialized (0x301)
                    Problem = CM_PROB_FAILED_INSTALL
                DevNode 0xfffffadf9df1bc50 for PDO 0xfffffadf9df01580
                  InstancePath is "PCI\VEN_1022&DEV_57A4&SUBSYS_00000000&REV_00\5&1f331b67&0&40000A"
                  ServiceName is "pci"
                  State = DeviceNodeStarted (0x308)
                  Previous State = DeviceNodeEnumerateCompletion (0x30d)
                  DevNode 0xfffffadf9dc542e0 for PDO 0xfffffadf9f1db420
                    InstancePath is "PCI\VEN_1022&DEV_1485&SUBSYS_87471043&REV_00\6&28ecf81d&0&0040000A"
                    State = DeviceNodeInitialized (0x302)
                    Previous State = DeviceNodeUninitialized (0x301)
                    Problem = CM_PROB_NOT_CONFIGURED
                  DevNode 0xfffffadf9e317930 for PDO 0xfffffadf9df03d40
                    InstancePath is "PCI\VEN_1022&DEV_149C&SUBSYS_87471043&REV_00\6&28ecf81d&0&0140000A"
                    ServiceName is "amdxhc"
                    State = DeviceNodeInitialized (0x302)
                    Previous State = DeviceNodeUninitialized (0x301)
                    Problem = CM_PROB_DRIVER_FAILED_LOAD
                  DevNode 0xfffffadf9e317750 for PDO 0xfffffadf9df1b070
                    InstancePath is "PCI\VEN_1022&DEV_149C&SUBSYS_148C1022&REV_00\6&28ecf81d&0&0340000A"
                    ServiceName is "amdxhc"
                    State = DeviceNodeInitialized (0x302)
                    Previous State = DeviceNodeUninitialized (0x301)
                    Problem = CM_PROB_DRIVER_FAILED_LOAD
                DevNode 0xfffffadf9df1ba70 for PDO 0xfffffadf9dd10070
                  InstancePath is "PCI\VEN_1022&DEV_57A4&SUBSYS_00000000&REV_00\5&1f331b67&0&48000A"
                  ServiceName is "pci"
                  State = DeviceNodeStarted (0x308)
                  Previous State = DeviceNodeEnumerateCompletion (0x30d)
                  DevNode 0xfffffadf9e317250 for PDO 0xfffffadf9f1d8d40
                    InstancePath is "PCI\VEN_1022&DEV_7901&SUBSYS_79011022&REV_51\6&39625884&0&0048000A"
                    ServiceName is "storahci"
                    State = DeviceNodeStarted (0x308)
                    Previous State = DeviceNodeEnumerateCompletion (0x30d)
                DevNode 0xfffffadf9df1b890 for PDO 0xfffffadf9dd10d40
                  InstancePath is "PCI\VEN_1022&DEV_57A4&SUBSYS_00000000&REV_00\5&1f331b67&0&50000A"
                  ServiceName is "pci"
                  State = DeviceNodeStarted (0x308)
                  Previous State = DeviceNodeEnumerateCompletion (0x30d)
                  DevNode 0xfffffadf9f1d8650 for PDO 0xfffffadf9f1d8a10
                    InstancePath is "PCI\VEN_1022&DEV_7901&SUBSYS_79011022&REV_51\6&15d2f925&0&0050000A"
                    ServiceName is "storahci"
                    State = DeviceNodeStarted (0x308)
                    Previous State = DeviceNodeEnumerateCompletion (0x30d)
                    DevNode 0xfffffadf9deffe30 for PDO 0xfffffadf9daa3070
                      InstancePath is "SCSI\Disk&Ven_WDC&Prod_WD2003FZEX-00SRL&Rev_01.0\7&85444d0&0&000000"
                      ServiceName is "disk"
                      State = DeviceNodeStarted (0x308)
                      Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadf9dd11290 for PDO 0xfffffadf9df1da10
              InstancePath is "PCI\VEN_1022&DEV_1452&SUBSYS_00000000&REV_00\3&11583659&0&10"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadf9df1c010 for PDO 0xfffffadf9df1d6e0
              InstancePath is "PCI\VEN_1022&DEV_1452&SUBSYS_00000000&REV_00\3&11583659&0&18"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadf9df1ce30 for PDO 0xfffffadf9df1d3b0
              InstancePath is "PCI\VEN_1022&DEV_1453&SUBSYS_00000000&REV_00\3&11583659&0&19"
              ServiceName is "pci"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0xfffffadf9df008f0 for PDO 0xfffffadf9df00070
                InstancePath is "PCI\VEN_10DE&DEV_1287&SUBSYS_730B19DA&REV_A1\4&2c517c28&0&0019"
                ServiceName is "vga"
                State = DeviceNodeRemoved (0x312)
                Previous State = DeviceNodeStartCompletion (0x306)
                Problem = CM_PROB_FAILED_START
                Failure Status 0000000000

              DevNode 0xfffffadf9df00710 for PDO 0xfffffadf9df00d40
                InstancePath is "PCI\VEN_10DE&DEV_0E0F&SUBSYS_730B19DA&REV_A1\4&2c517c28&0&0119"
                ServiceName is "HDAudBus"
                State = DeviceNodeStarted (0x308)
                Previous State = DeviceNodeEnumerateCompletion (0x30d)
                DevNode 0xfffffadf9d76be30 for PDO 0xfffffadf9cdd7850

                  InstancePath is
    "HDAUDIO\FUNC_01&VEN_10DE&DEV_0051&SUBSYS_19DA730B&REV_1001\5&2e590a66&0&0001"
                  ServiceName is "NVHDA"
                  State = DeviceNodeStarted (0x308)
                  Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadf9df1cc50 for PDO 0xfffffadf9dc53070
              InstancePath is "PCI\VEN_1022&DEV_1452&SUBSYS_00000000&REV_00\3&11583659&0&20"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadf9df1ca70 for PDO 0xfffffadf9dc53d40
              InstancePath is "PCI\VEN_1022&DEV_1452&SUBSYS_00000000&REV_00\3&11583659&0&38"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadf9df1c890 for PDO 0xfffffadf9dc53a10
              InstancePath is "PCI\VEN_1022&DEV_1454&SUBSYS_00000000&REV_00\3&11583659&0&39"
              ServiceName is "pci"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0xfffffadf9dd0f230 for PDO 0xfffffadf9df00440
                InstancePath is "PCI\VEN_1022&DEV_145A&SUBSYS_87471043&REV_00\4&323ac8bb&0&0039"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_FAILED_INSTALL
              DevNode 0xfffffadf9df1a010 for PDO 0xfffffadf9dd0fd40
                InstancePath is "PCI\VEN_1022&DEV_1456&SUBSYS_87471043&REV_00\4&323ac8bb&0&0239"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_FAILED_INSTALL
              DevNode 0xfffffadf9df1ae30 for PDO 0xfffffadf9dd0fa10
                InstancePath is "PCI\VEN_1022&DEV_145C&SUBSYS_87471043&REV_00\4&323ac8bb&0&0339"
                ServiceName is "amdxhc"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_DRIVER_FAILED_LOAD
              DevNode 0xfffffadf9df1ac50 for PDO 0xfffffadf9dd0f680
                InstancePath is "ACPI\PNP0C02\4&323ac8bb&0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
            DevNode 0xfffffadf9df1c6b0 for PDO 0xfffffadf9dc536e0
              InstancePath is "PCI\VEN_1022&DEV_1452&SUBSYS_00000000&REV_00\3&11583659&0&40"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadf9df1c4d0 for PDO 0xfffffadf9dc533b0
              InstancePath is "PCI\VEN_1022&DEV_1454&SUBSYS_00000000&REV_00\3&11583659&0&41"
              ServiceName is "pci"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0xfffffadf9dc50a10 for PDO 0xfffffadf9df1a980
                InstancePath is "PCI\VEN_1022&DEV_1455&SUBSYS_87471043&REV_00\4&3786a086&0&0041"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_FAILED_INSTALL
              DevNode 0xfffffadf9dc50830 for PDO 0xfffffadf9df1a4d0
                InstancePath is "PCI\VEN_1022&DEV_7901&SUBSYS_87471043&REV_51\4&3786a086&0&0241"
                ServiceName is "storahci"
                State = DeviceNodeStarted (0x308)
                Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0xfffffadf9dc50650 for PDO 0xfffffadf9dc50070
                InstancePath is "PCI\VEN_1022&DEV_1457&SUBSYS_87331043&REV_00\4&3786a086&0&0341"
                ServiceName is "HDAudBus"
                State = DeviceNodeStarted (0x308)
                Previous State = DeviceNodeEnumerateCompletion (0x30d)
                DevNode 0xfffffadf9d943e30 for PDO 0xfffffadf9d8c3c60

                  InstancePath is
    "HDAUDIO\FUNC_01&VEN_10EC&DEV_1168&SUBSYS_10438733&REV_1001\5&1bd841a1&0&0001"
                  State = DeviceNodeInitialized (0x302)
                  Previous State = DeviceNodeUninitialized (0x301)
                  Problem = CM_PROB_FAILED_INSTALL
            DevNode 0xfffffadf9df1c2f0 for PDO 0xfffffadf9e319070
              InstancePath is "PCI\VEN_1022&DEV_790B&SUBSYS_87471043&REV_59\3&11583659&0&A0"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
              Problem = CM_PROB_FAILED_INSTALL
            DevNode 0xfffffadf9dc52010 for PDO 0xfffffadf9e319d40
              InstancePath is "PCI\VEN_1022&DEV_790E&SUBSYS_00000000&REV_51\3&11583659&0&A3"
              ServiceName is "isapnp"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0xfffffadf9e315c20 for PDO 0xfffffadf9e316e60
                InstancePath is "ACPI\PNP0000\4&28d859f2&0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
              DevNode 0xfffffadf9e315a40 for PDO 0xfffffadf9e316c50
                InstancePath is "ACPI\PNP0200\4&28d859f2&0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
              DevNode 0xfffffadf9e315860 for PDO 0xfffffadf9e316a40
                InstancePath is "ACPI\PNP0100\4&28d859f2&0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
              DevNode 0xfffffadf9e315680 for PDO 0xfffffadf9e316830
                InstancePath is "ACPI\PNP0B00\4&28d859f2&0"
                State = DeviceNodeStarted (0x308)
                Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0xfffffadf9e3154a0 for PDO 0xfffffadf9e316620
                InstancePath is "ACPI\PNP0800\4&28d859f2&0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
              DevNode 0xfffffadf9e3152c0 for PDO 0xfffffadf9e316410
                InstancePath is "ACPI\PNP0C02\0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
              DevNode 0xfffffadf9e314010 for PDO 0xfffffadf9e315070
                InstancePath is "ACPI\PNP0303\0"
                ServiceName is "i8042prt"
                TargetDeviceNotify List - f 0xfffffa80006b89b0  b 0xfffffa80006b89b0
                State = DeviceNodeStarted (0x308)
                Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0xfffffadf9e314e30 for PDO 0xfffffadf9e315e60
                InstancePath is "ACPI\PNP0C09\4&28d859f2&0"
                ServiceName is "ACPIEC"
                State = DeviceNodeRemoved (0x312)
                Previous State = DeviceNodeStartCompletion (0x306)
                Problem = CM_PROB_FAILED_START
                Failure Status 0000000000

            DevNode 0xfffffadf9dc52e30 for PDO 0xfffffadf9e319a10
              InstancePath is "PCI\VEN_1022&DEV_1460&SUBSYS_00000000&REV_00\3&11583659&0&C0"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadf9dc52c50 for PDO 0xfffffadf9e3196e0
              InstancePath is "PCI\VEN_1022&DEV_1461&SUBSYS_00000000&REV_00\3&11583659&0&C1"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadf9dc52a70 for PDO 0xfffffadf9e3193b0
              InstancePath is "PCI\VEN_1022&DEV_1462&SUBSYS_00000000&REV_00\3&11583659&0&C2"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadf9dc52890 for PDO 0xfffffadf9f1da070
              InstancePath is "PCI\VEN_1022&DEV_1463&SUBSYS_00000000&REV_00\3&11583659&0&C3"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadf9dc526b0 for PDO 0xfffffadf9f1dad40
              InstancePath is "PCI\VEN_1022&DEV_1464&SUBSYS_00000000&REV_00\3&11583659&0&C4"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadf9dc524d0 for PDO 0xfffffadf9f1daa10
              InstancePath is "PCI\VEN_1022&DEV_1465&SUBSYS_00000000&REV_00\3&11583659&0&C5"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadf9dc522f0 for PDO 0xfffffadf9f1da6e0
              InstancePath is "PCI\VEN_1022&DEV_1466&SUBSYS_00000000&REV_00\3&11583659&0&C6"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadf9e318010 for PDO 0xfffffadf9f1da3b0
              InstancePath is "PCI\VEN_1022&DEV_1467&SUBSYS_00000000&REV_00\3&11583659&0&C7"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadf9e318e30 for PDO 0xfffffadf9f1dbaa0
              InstancePath is "ACPI\PNP0C01\c8"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
            DevNode 0xfffffadf9e318c50 for PDO 0xfffffadf9df03410
              InstancePath is "ACPI\PNP0C02\15"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
            DevNode 0xfffffadf9e318a70 for PDO 0xfffffadf9df02070
              InstancePath is "ACPI\PNP0C02\700"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
            DevNode 0xfffffadf9e318890 for PDO 0xfffffadf9df02e60
              InstancePath is "ACPI\PNP0C14\MXM2"
              ServiceName is "WmiAcpi"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9df08130 for PDO 0xfffffadf9f1e2360
            InstancePath is "ACPI\PNP0C0C\aa"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9df04c20 for PDO 0xfffffadf9f1dd360
            InstancePath is "ACPI\PNP0103\2&daba3ff&0"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
          DevNode 0xfffffadf9df04a40 for PDO 0xfffffadf9e333ba0
            InstancePath is "ACPI\AMDI0030\0"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
            Problem = CM_PROB_FAILED_INSTALL
          DevNode 0xfffffadf9df04860 for PDO 0xfffffadf9df07420
            InstancePath is "ACPI\PNP0C14\ASUSWMI"
            ServiceName is "WmiAcpi"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9df04680 for PDO 0xfffffadf9f1dea40
            InstancePath is "ACPI\FixedButton\2&daba3ff&0"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9df044a0 for PDO 0xfffffadf9f1de830
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_0"
            ServiceName is "Processor"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9df042c0 for PDO 0xfffffadf9f1de620
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_1"
            ServiceName is "Processor"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9dd14010 for PDO 0xfffffadf9f1de410
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_2"
            ServiceName is "Processor"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9dd14e30 for PDO 0xfffffadf9e31b070
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_3"
            ServiceName is "Processor"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9dd14c50 for PDO 0xfffffadf9e31be60
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_4"
            ServiceName is "Processor"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9dd14a70 for PDO 0xfffffadf9e31bc50
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_5"
            ServiceName is "Processor"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9dd14890 for PDO 0xfffffadf9e31ba40
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_6"
            ServiceName is "Processor"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9dd146b0 for PDO 0xfffffadf9e31b830
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_7"
            ServiceName is "Processor"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9dd144d0 for PDO 0xfffffadf9e31b620
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_8"
            ServiceName is "Processor"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9dd142f0 for PDO 0xfffffadf9e31b410
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\_9"
            ServiceName is "Processor"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9df1e010 for PDO 0xfffffadf9f1dc070
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\10"
            ServiceName is "Processor"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9df1ee30 for PDO 0xfffffadf9f1dce60
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\11"
            ServiceName is "Processor"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9df1ec50 for PDO 0xfffffadf9f1dcc50
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\12"
            ServiceName is "Processor"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9df1ea70 for PDO 0xfffffadf9f1dca40
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\13"
            ServiceName is "Processor"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9df1e890 for PDO 0xfffffadf9f1dc830
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\14"
            ServiceName is "Processor"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9df1e6b0 for PDO 0xfffffadf9f1dc620
            InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_1\15"
            ServiceName is "Processor"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadf9df1e4d0 for PDO 0xfffffadf9f1dc410
            InstancePath is "ACPI\PNP0C02\90"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
          DevNode 0xfffffadf9df1e2f0 for PDO 0xfffffadf9df04070
            InstancePath is "ACPI\PNP0C02\91"
            State = DeviceNodeInitialized (0x302)
            Previous State = DeviceNodeUninitialized (0x301)
          DevNode 0xfffffadf9dc54010 for PDO 0xfffffadf9df04e60
            InstancePath is "ACPI\PNP0C14\AOD"
            ServiceName is "WmiAcpi"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e0586e0 for PDO 0xfffffadf9e058920
        InstancePath is "Root\dmio\0000"
        ServiceName is "dmio"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e0582e0 for PDO 0xfffffadf9e058520
        InstancePath is "Root\ftdisk\0000"
        ServiceName is "ftdisk"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
        DevNode 0xfffffadf9e3142d0 for PDO 0xfffffadf9d2c7860
          InstancePath is "STORAGE\Volume\1&30a96598&0&Signature646587B9Offset100000Length1D1C04C7E00"
          ServiceName is "volsnap"
          TargetDeviceNotify List - f 0xfffffa80004899b0  b 0xfffffa8000af05a0
          State = DeviceNodeStarted (0x308)
          Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e332e30 for PDO 0xfffffadf9e332070
        InstancePath is "Root\LEGACY_AFD\0000"
        ServiceName is "AFD"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e332a30 for PDO 0xfffffadf9e332c70
        InstancePath is "Root\LEGACY_AMPA\0000"
        ServiceName is "ampa"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e332630 for PDO 0xfffffadf9e332870
        InstancePath is "Root\LEGACY_BEEP\0000"
        ServiceName is "Beep"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e332230 for PDO 0xfffffadf9e332470
        InstancePath is "Root\LEGACY_CDAC15BA\0000"
        ServiceName is "CdaC15BA"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e057e30 for PDO 0xfffffadf9e057070
        InstancePath is "Root\LEGACY_CDAD10BA\0000"
        ServiceName is "CdaD10BA"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e057a30 for PDO 0xfffffadf9e057c70
        InstancePath is "Root\LEGACY_CRCDISK\0000"
        ServiceName is "crcdisk"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e057630 for PDO 0xfffffadf9e057870
        InstancePath is "Root\LEGACY_DMBOOT\0000"
        ServiceName is "dmboot"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e057230 for PDO 0xfffffadf9e057470
        InstancePath is "Root\LEGACY_DMLOAD\0000"
        ServiceName is "dmload"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e331e30 for PDO 0xfffffadf9e331070
        InstancePath is "Root\LEGACY_FIPS\0000"
        ServiceName is "Fips"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e331a30 for PDO 0xfffffadf9e331c70
        InstancePath is "Root\LEGACY_GPC\0000"
        ServiceName is "Gpc"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e331630 for PDO 0xfffffadf9e331870
        InstancePath is "Root\LEGACY_HTTP\0000"
        ServiceName is "HTTP"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e331230 for PDO 0xfffffadf9e331470
        InstancePath is "Root\LEGACY_IPNAT\0000"
        ServiceName is "IpNat"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e056e30 for PDO 0xfffffadf9e056070
        InstancePath is "Root\LEGACY_IPSEC\0000"
        ServiceName is "IPSec"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e056a30 for PDO 0xfffffadf9e056c70
        InstancePath is "Root\LEGACY_KSECDD\0000"
        ServiceName is "ksecdd"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e056630 for PDO 0xfffffadf9e056870
        InstancePath is "Root\LEGACY_MNMDD\0000"
        ServiceName is "mnmdd"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e056230 for PDO 0xfffffadf9e056470
        InstancePath is "Root\LEGACY_MOUNTMGR\0000"
        ServiceName is "mountmgr"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e330e30 for PDO 0xfffffadf9e330070
        InstancePath is "Root\LEGACY_NDIS\0000"
        ServiceName is "NDIS"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e330a30 for PDO 0xfffffadf9e330c70
        InstancePath is "Root\LEGACY_NDISTAPI\0000"
        ServiceName is "NdisTapi"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e330630 for PDO 0xfffffadf9e330870
        InstancePath is "Root\LEGACY_NDISUIO\0000"
        ServiceName is "Ndisuio"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e330230 for PDO 0xfffffadf9e330470
        InstancePath is "Root\LEGACY_NDPROXY\0000"
        ServiceName is "NDProxy"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e055e30 for PDO 0xfffffadf9e055070
        InstancePath is "Root\LEGACY_NETBT\0000"
        ServiceName is "NetBT"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e055a30 for PDO 0xfffffadf9e055c70
        InstancePath is "Root\LEGACY_NULL\0000"
        ServiceName is "Null"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e055630 for PDO 0xfffffadf9e055870
        InstancePath is "Root\LEGACY_PARTMGR\0000"
        ServiceName is "PartMgr"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e055230 for PDO 0xfffffadf9e055470
        InstancePath is "Root\LEGACY_RASACD\0000"
        ServiceName is "RasAcd"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e32fe30 for PDO 0xfffffadf9e32f070
        InstancePath is "Root\LEGACY_RDPCDD\0000"
        ServiceName is "RDPCDD"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e32fa30 for PDO 0xfffffadf9e32fc70
        InstancePath is "Root\LEGACY_SECDRV\0000"
        ServiceName is "Secdrv"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e32f630 for PDO 0xfffffadf9e32f870
        InstancePath is "Root\LEGACY_TCPIP\0000"
        ServiceName is "Tcpip"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e32f230 for PDO 0xfffffadf9e32f470
        InstancePath is "Root\LEGACY_VGASAVE\0000"
        ServiceName is "VgaSave"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e054e30 for PDO 0xfffffadf9e054070
        InstancePath is "Root\LEGACY_VOLSNAP\0000"
        ServiceName is "VolSnap"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e054a30 for PDO 0xfffffadf9e054c70
        InstancePath is "Root\LEGACY_WANARP\0000"
        ServiceName is "Wanarp"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e054630 for PDO 0xfffffadf9e054870
        InstancePath is "Root\MEDIA\MS_MMACM"
        ServiceName is "audstub"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e054230 for PDO 0xfffffadf9e054470
        InstancePath is "Root\MEDIA\MS_MMDRV"
        ServiceName is "audstub"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e32ee30 for PDO 0xfffffadf9e32e070
        InstancePath is "Root\MEDIA\MS_MMMCI"
        ServiceName is "audstub"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e32ea30 for PDO 0xfffffadf9e32ec70
        InstancePath is "Root\MEDIA\MS_MMVCD"
        ServiceName is "audstub"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e32e630 for PDO 0xfffffadf9e32e870
        InstancePath is "Root\MEDIA\MS_MMVID"
        ServiceName is "audstub"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e32e230 for PDO 0xfffffadf9e32e470
        InstancePath is "Root\MS_L2TPMINIPORT\0000"
        ServiceName is "Rasl2tp"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e053e30 for PDO 0xfffffadf9e053070
        InstancePath is "Root\MS_NDISWANIP\0000"
        ServiceName is "NdisWan"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e053a30 for PDO 0xfffffadf9e053c70
        InstancePath is "Root\MS_PPPOEMINIPORT\0000"
        ServiceName is "RasPppoe"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e053630 for PDO 0xfffffadf9e053870
        InstancePath is "Root\MS_PPTPMINIPORT\0000"
        ServiceName is "PptpMiniport"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e053230 for PDO 0xfffffadf9e053470
        InstancePath is "Root\MS_PSCHEDMP\0000"
        ServiceName is "PSched"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e32de30 for PDO 0xfffffadf9e32d070
        InstancePath is "Root\MS_PSCHEDMP\0001"
        ServiceName is "PSched"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e32da30 for PDO 0xfffffadf9e32dc70
        InstancePath is "Root\MS_PTIMINIPORT\0000"
        ServiceName is "Raspti"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e32d630 for PDO 0xfffffadf9e32d870
        InstancePath is "Root\RDPDR\0000"
        ServiceName is "rdpdr"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e32d230 for PDO 0xfffffadf9e32d470
        InstancePath is "Root\RDP_KBD\0000"
        ServiceName is "TermDD"
        TargetDeviceNotify List - f 0xfffffa80006a9730  b 0xfffffa80006a9730
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e052e30 for PDO 0xfffffadf9e052070
        InstancePath is "Root\RDP_MOU\0000"
        ServiceName is "TermDD"
        TargetDeviceNotify List - f 0xfffffa80006d4d50  b 0xfffffa80006d4d50
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e052a30 for PDO 0xfffffadf9e052c70
        InstancePath is "Root\SYSTEM\0000"
        ServiceName is "swenum"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e052630 for PDO 0xfffffadf9e052870
        InstancePath is "Root\SYSTEM\0001"
        ServiceName is "update"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadf9e052230 for PDO 0xfffffadf9e052470
        InstancePath is "Root\SYSTEM\0002"
        ServiceName is "mssmbios"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)

#2208

daniel_k

⇗ @diderius6
The file on post 2202 works or it needs this patch?

    18C97: 00 => 17

In the end, my assumption was correct and the behavior of x86 and x64 is the same.
Your working ACPI.SYS is the same as the test2 of this post:
¶ Windows XP SP3 32bit and modern PC parts (146)

#2209

diderius6

⇗ @daniel_k
This is your ) patch 18C97: 00 => 17
I also think, because of the to 100% identic BSODS, that XP SP3 and XP 64 behave like the same.
But what was the important difference to the 5048 XP 64 acpi.sys from ⇗ @infuscomus ?
I know, that you integrate QwordConst and CreateQwordfield,
but this can be reached also via mod of DSDT.
So, something must be other than in mod of 5048 acpi.sys for XP SP3
Dietmar

#2210

sqpp

So I have used the linked ⇗ @diderius6 's file acpiXP64Ryzen.rar in my 64 Bit Windows XP. I have used the guide of ⇗ @infuscomus in ⇗ Installing Windows XP on Newer Laptop (Coffee Lake S)
and apparently it still fails for me. Possibly maybe I do something wrong, but I don't think. Everything is done as he wrote to do. The new acpi.sys and acpi.sy_ is in the correct cab/directory.
Now after everything is going, it fails with the same BSOD A5 error like earlier.
Not sure if the patch would work on my i5-8350u processor though, as I said, I might do something incorrect.

#2211 | daniel_k | Please try test2 from ¶ Windows XP SP3 32bit and modern PC parts (146) Just to confirm?
#2212 | sqpp | Will do now, it will take a few. Be right back :)

#2213

diderius6

⇗ @daniel_k
I retested from this morning all your acpi.sys for XP 64 bit,
this time with checked (debug) version of hal.dll and ntoskrnl.
And I installed for each try the registry entries for the STORAHCI driver by hand new.
Yes, from 1 of three was your acpi_test2.sys 5048 version the one that
works
Dietmar

#2214 | sqpp | I am also not sure if my Sata drivers working correctly, since upon pressing the F6/F7 key, it mentions that I have no mass storage in the computer. I guess that's not a good sign?
#2215 | daniel_k | ⇗ @sqpp, sorry I was talking to diderius6 ⇗ @diderius6, so we don't need to patch offset 18C97. The code is exactly the same as @infuscomus.
#2216 | infuscomus | ⇗ @sqpp If you have BSOD 7B when you press F7 then you do need to get a storage driver you can try Fernando modded intel driver or otherwise there is a generic storahci driver to try
#2217 | sqpp | ⇗ @infuscomus It asks me to press F6 actually for the Sata drivers. No F7 mentioned, just read that somewhere, but I don't get BSOD in case, just for the ACPI. I am still not sure if I am using the right drivers.
#2218 | infuscomus | ⇗ @sqpp try this driver - use nlite to integrate ¶ Windows XP SP3 32bit and modern PC parts (119)
#2219 | daniel_k | ⇗ @diderius6 Please try this later. It's based on original XP SP2 3959 x64 for Ryzen only, supports QwordConst and CreateQwordField. PS: Please confirm that we don't need to patch offset 18C97 of acpi_test2.sys, so we can declare it as the final version.
#2220 | sqpp | This is what happens upon installing. Then whatever I do. Soon after this, I got the ACPI BSOD

## Page 149

#2221 | infuscomus | ⇗ @sqpp try not pressing F6, but press F7 instead, what BSOD do you get then?
#2222 | diderius6 | ⇗ @daniel_k This picture is based on the acpi.sys 5048 for XP 64 SP2 on Ryzen from post 2202 Dietmar ⇗

#2223

diderius6

⇗ @daniel_k
The acpi.sys driver from post 2219 does not work,
it gives BSOD 0x7B,
even I update the registry entries by hand for the STORAHCI driver
2 times.
Until now, only the acpi.sys from post 2202
works for XP 64 SP2 and Ryzen
Dietmar

#2224 | kukonosau | ⇗ @diderius6 ACPI from post 2202 does not work, it gives different BSOD. Many restarting. Don't copy several files in our installation.

#2225

daniel_k

⇗ @diderius6, ⇗ @kukonosau
Thanks for trying.
So, to make things clear, here are the final versions of ACPI.SYS based on Vista beta 5048.
For Windows XP SP2 x64 and Server 2003 SP2 x64 use acpi5048_x64_intel_amd_final.rar
For Windows XP SP3 x86 and Server 2003 SP2 x86 use acpi5048_x86_intel_amd_final.rar
Supports:
- Intel Skylake, Coffee Lake and later
- AMD Ryzen
No BIOS modding required.
XHCI USB 3.0/3.1 driver for all Intel chipsets use AMDXHCI_XP_FINAL.rar for x86 and x64
PS: Updated with proper support for Z390 chipsets (including H370 and other 300 series).

daniel_k has attached files to this post

- ⇗ AMDXHCI_XP_FINAL.rar
- ⇗ acpi5048_intel_amd_final.rar
- ⇗ acpi5048_x64_intel_only_final.rar

#2226 | kukonosau | Different BSOD((( I check ACPI with Asmedia 106X Controller and chipset controller.
#2227 | sqpp | Whats the best SATA driver for Coffee Lake based laptops for XP? Can't get any of them working :(
#2228 | sqpp | In my case 0x000000A5, 0x00000000000000003 (or something like that), 0xFFFFFADF40B4C9948,... Not sure if that helps. Using the final version linked above acpi5048_x64_intel_amd_final.rar

#2229

diderius6

⇗ @skullteria
After debug of XP SP3 via Vista boot,
I see, that the problem was in the E820 list.
And voila, I am getting better,
here is the acpi.sys of XP SP3
which can boot XP SP3 via BCD via Vista files with full ACPI support
Dietmar
EDIT: Yessa, I make the nail test, renaming ntldr to ntttldr, XP SP3 boots only using
files of Vista:)) and it is absolut stable with everything works on the nice Giga H110 board.
diderius6 has attached files to this post

- ⇗ acpi11Checksum.rar

#2230

skullteria

> Zitat von ⇗ diderius6 im Beitrag ¶ #2229

> @skullteria
> After debug of XP SP3 via Vista boot,
> I see, that the problem was in the E820 list.
> And voila, I am getting better,
> here is the acpi.sys of XP SP3
> which can boot XP SP3 via BCD via Vista files with full ACPI support
> Dietmar
> EDIT: Yessa, I make the nail test, renaming ntldr to ntttldr, XP SP3 boots only using
> files of Vista:)) and it is absolut stable with everything works on the nice Giga H110 board.

Awasome! THank you so much! One only question: can you do it on acpi 5048 from danie_K and for x64?
EDIT: When i installed Intel HD Graphics, the system restart...No time to BSOD.

#2231

diderius6

⇗ @skullteria
I will make some more tests.
About programming I have nearly no idea.
So I hope, that I get help for to put the most important parts
of acpi11.sys to the 5048 version.
But now we know, that it can be done,
have a nice day
Dietmar
PS: I am just writing this from this compi H110, XP SP3 booted via Vista files:))!

#2232 | infuscomus | ⇗ @diderius6 nice! in CSM mode or UEFI mode?
#2233 | infuscomus | ⇗ @sqpp there is a modded intel storage driver you can try and see if it works for you ¶ Windows XP SP3 32bit and modern PC parts (118) ⇗ @daniel_k made it

#2234

Gelip

> Zitat von ⇗ diderius6 im Beitrag ¶ #1776

> Here is the storahci driver,
> which works really everywhere. I just give in the folder AMD64 its *.inf for 64 bit support.
> AMD, Intel, 32 bit, 64 bit doesnt matter. Until now I do not find a board, where it does not work,
> really generic.
> Copy the newest version of storport.sys
> to windows\system32\drivers and install. You can also make a txtsetup.oem
> and integrate it to your XP installations CD. Dont forget storport.sys!
> I tested it for XP 32 bit and XP 64 bit
> Dietmar
> EDIT: So much thank to @skullteria !

Where to download the storport.sys file because there is no one in the StorahciSkulltrailALL.rar archive?

#2235

sqpp

> Zitat von ⇗ infuscomus im Beitrag ¶ #2233

> @sqpp
> there is a modded intel storage driver you can try and see if it works for you
> ¶ Windows XP SP3 32bit and modern PC parts (118)
> @daniel_k made it

Thanks a ton, still I need to wait for the acpi fix

## Page 150

#2236 | infuscomus | ⇗ @sqpp can you upload your ACPI.SY_ and DRIVER.CAB ? just want to double check for correct integration
#2237 | sqpp | ⇗ @infuscomus I would upload it here but .sy_ was not allowed filetype, so just used Mega. ⇗ acpi_sy_, driver.cab

#2238

infuscomus

⇗ @sqpp
looks to me like you integrated properly
what laptop did you have again?
⇗ @diderius6 ⇗ @daniel_k
we might have some additional ACPI BSODs to fix?
sqpp ran into a BSOD - post 2228

#2239 | sqpp | ⇗ @infuscomus Lenovo Thinkpad T480 (i5-8350u)
#2240 | diderius6 | ⇗ @sqpp Please write here the complete BSOD A5 field with all its other numbers. We need this for a first check, what went wrong Dietmar
#2241 | sqpp | ⇗ @diderius6 I was worried, I might type the numbers incorrectly, so just took a photo instead.

#2242

diderius6

⇗ @Gelip
Here comes storport for XP SP3 32 and for XP64 bit,
as far as I know the last versions
Dietmar
diderius6 has attached files to this post

- ⇗ STORPORT.rar

#2243

Andalu

I'm still looking for a solution to get a full functionality of the USB3.0 ports for my CSM-Q87M-E43 board. Only using the "acpi5048_x86_intel_amd_final" and "AMDXHCI_XP_FINAL" is not enough. As diderius6 suggested, i need probably a DSDT table mod.
Keeping in mind my limited knowledge about bios modding, can someone suggest where to start in order to modify the DSDT table, please?

#2244

diderius6

⇗ @sqpp
A5 (0x03
The ACPI object that was being run
The return value from the interpreter C0140010 (I have only seen in Vista until now, but I think it can be done a Hack)
STATUS_ACPI_INVALID_REGION. An invalid region for the target was specified.
The name of the control method (in ULONG format)
ACPI tried to run a control method while creating device extensions to represent the ACPI namespace, but this control method failed.
Dietmar

#2245 | sqpp | ⇗ @diderius6 Thats a bit difficult for me actually. So it some sort of unique problem?

#2246

diderius6

⇗ @Andalu
It is an Intel USB3 device with the HC switch methode.
So I think, the device is just switched to USB2
but I dont know the place in Bios, where this happens
Dietmar
EDIT: Take a look in your Bios. Maybe there is something like "compatible" enabled for USB3, this means USB2.
⇗ https://superuser.com/questions/719079/u...el-usb-3-0-xhci

#2247

Gelip

> Zitat von ⇗ diderius6 im Beitrag ¶ #2242

> @Gelip
> Here comes storport for XP SP3 32 and for XP64 bit,
> as far as I know the last versions
> Dietmar

The x64 version you have included is 5.2.3790.4173 but this is not the latest version. I found even newer files on ⇗ http://thehotfixshare.net
Probably this is latest: ⇗ WindowsServer2003.WindowsXP-KB957910-x64-ENU.exe - ver. 5.2.3790.4485 same as 32-bit version.

#2248 | daniel_k | ⇗ @diderius6 Does the NVIDIA GPU driver works?
#2249 | daniel_k | ⇗ @sqpp Dump the DSDT table of your Thinkpad with this: ⇗ http://rweverything.com/ Click on ACPI Tables button, click on DSDT and save it as binary. Then ZIP or RAR it and attach it for us.

#2250

sqpp

⇗ @daniel_k Here you go :)
sqpp has attached files to this post

- ⇗ ACPI (1).zip

## Page 151

#2251 | daniel_k | ⇗ @sqpp It's DSDT.
#2252 | sqpp | Yes, I have corrected it, uploaded the correct one. Excuse me for the mistake.

#2253

Andalu

⇗ @diderius6
I checked again the entire bios and no options like "usb compatible" or "switching usb" are present, only the classics "XHCI hand-off" and "EHCI hand-off" but enabling or disabling one or both of them has no effects. Maybe the msi bios doesn't work properly?
Really useful link, thanks. About it, my "PCI bus" device (id ACPI\PNP0A08\0) has not "iusb3hcs" value in "device lower filters" and effectively this .sys file is missing on my system. I tried to install the 32bit DPInst Set with Intel USB 3.0+3.1 Drivers v5.0.4.43 mod+signed by Fernando package containing "iusb3hcs.inf" but it clearly doesn't work even if the iusb3hcs.sys is copied to windows\system32\drivers folder.

#2254

diderius6

⇗ @daniel_k
"Does the NVIDIA GPU driver works?"
Yesssssssssssss, I am just running 3Dmark2001 on it and the boottime is ultrafast,
about 2 sec to full desktop of XP SP3 compared with around
30 sec for booting XP via ntldr
Dietmar

#2255 | daniel_k | ⇗ @diderius6 What an achievement! Please give us an step-by-step guide.

#2256

diderius6

⇗ @daniel_k
The same I ask yesterday ⇗ @skullteria and he helped me a little.
I dont know, how far he is now,
Dietmar
PS: It is not ready. I do some more tests. I would be very happy,
when you can integrate some hacks into the acpi.sys 5048 version for XP SP3.
Which hacks are really needed, I try to find out today.

#2257 | daniel_k | ⇗ @diderius6, by guide I mean to setup the UEFI boot. Which file system is needed? Or we just copy the .efi boot files to the NTFS XP boot partition and create an entry in boot loader? About the hacks, just restore the bytes one by one and test if it still boots.

#2258

diderius6

⇗ @daniel_k
"⇗ @diderius6, by guide I mean to setup the UEFI boot."
Until now, it is not UEFI boot.
I try UEFI boot, because the steps are nearly identic.
But we have to ask ⇗ @skullteria if he allows, that I
open all his files and his nice Tutorial
Dietmar

#2259

diderius6

From Wikipedia
BIOS
Im Fall von BIOS liest dieses den MBR der Festplatte oder eines anderen Speichermediums ein und führt ihn aus. Durch den dort befindlichen Code wird dann der Bootsektor der als aktiv markierten Partition geladen und ausgeführt. Der Code aus dem Bootsektor einer Partition, auf der eine entsprechende Windows-Installation installiert wurde, ist nun fähig, die Datei bootmgr im Wurzelverzeichnis eines NTFS-Dateisystems zu finden und auszuführen. Das Programm bootmgr liest die Datei \Boot\BCD ein und zeigt ein Bootmenü zur Auswahl des zu startenden Betriebssystems an. Zudem überprüft der BOOTMGR die Disk-Signatur (Bytes 440443 im MBR) mit seinen gespeicherten Booteinträgen aus der Boot Configuration Data. Wurde die Disk-Signatur verändert, verweigert Windows den Start mit einem winload error.[1]
EFI
Liegt EFI vor, so sind die ersten beiden Teile aus dem MBR und VBR überflüssig. Der Boot Manager ist in der Datei \efi\BOOT\bootia32.efi bzw. \efi\BOOT\bootx64.efi in der EFI-System-Partition gespeichert und wird von EFI direkt geladen und ausgeführt. Ansonsten ist die Funktionalität identisch zum bootmgr.
Als Nächstes startet BOOTMGR winload.exe, sofern Windows geladen werden soll. Es lädt in der Folge genau wie NTLDR den HAL, den Kernel und seine Bibliotheken und Gerätetreiber. Zudem lädt er die Windows-Registrierungsdatenbank. Danach übergibt winload.exe die Kontrolle dem Kernel, der sich initialisiert und weitere System-Dienste lädt.
Boot-Einstellungen
Alle Einstellungen für den Bootloader sind bei BIOS-Systemen in der Datei \Boot\BCD, bei EFI-Systemen in der Datei \EFI\Microsoft\Boot\BCD in der EFI-Systempartition abgelegt.[2] Die Boot Configuration Data ist in eine Binärdatei abgelegt und vom Aufbau her ein Hive der Windows-Registrierungsdatenbank. Microsoft bietet das Kommandozeilen-Tool bcdedit.exe an, um Bootparameter zu ändern. Es ist auch möglich beim Booten von der Windows-CD über den Punkt Computer reparieren/Systemwiederherstellungsoptionen das Tool bootrec.exe aufzurufen. Alternativ kann das Programm EasyBCD 1.7.2 needs Net Framework 2.0. , um die BOOTMGR-Einstellungen zu ändern.

#2260

daniel_k

⇗ @sqpp
It's a Phoenix BIOS, which is known to have compatibility issues, much like Insyde's.
It seems to me, that the issue lies here (just an example, there are many instances of this XP incompatible coding):

    Scope (\_SB.PCI0)
    {
        Device (XHC)
        {
            Method (_INI, 0, NotSerialized)  // _INI: Initialize
            {
                If (CondRefOf (\_SB.PCI0.XHC.RHUB.INIR))
                {
                    \_SB.PCI0.XHC.RHUB.INIR () ---> WRONG
                }
            }
        }
    }

    Scope (_SB.PCI0)
    {
        Device (XHC)
        {
            Method (_INI, 0, NotSerialized)  // _INI: Initialize
            {
                If (CondRefOf (\_SB.PCI0.XHC.RHUB.INIR))
                {
                    ^RHUB.INIR () ---> CORRECT
                }
            }
        }
    }

However, I don't know if it can be fixed by patching ACPI.SYS.

#2261 | sqpp | Ah hell no :( I most likely need an another thinkpad then.

#2262

daniel_k

> Zitat von ⇗ sqpp im Beitrag ¶ #2261

> Ah hell no :( I most likely need an another thinkpad then.

There is this:

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #1638

> I feel that it is time to remind about my util called "acpi patcher" )
> it is dsdt/ssdt table manipulation tool before OS loading, even for winxp textmode setup

He explains how to use it here:
⇗ http://reboot.pro/topic/22051-acpi-patcher-at-boot-time/
If you learn how to use it, let me know and I can help you to fix the table.

#2263

diderius6

⇗ @daniel_k
Daniel, please can you add this 3 hacks
to the acpi.sys 5048 for XP SP3?
This is german versions of original acpi.sys 5512,
but this is not important
Dietmar
diderius6 has attached files to this post

- ⇗ ACPIforShorthorn.rar

#2264 | daniel_k | ⇗ @diderius6, for x86 it was easy.
#2265 | diderius6 | ⇗ @daniel_k Waaaoh, this is in record time ), I am going to test Dietmar

## Page 152

#2266 | diderius6 | ⇗ @daniel_k Yesssaaaaa:)))), thanks a lot, works on Shorthorn files to boot XP SP3 this makes also ⇗ @skullteria happy, I know for sure Dietmar

#2267

Doc.Brown

Awesome work you're doing here guys
I'm trying to have a working XP SP3 with Maximus XI Gene and CoffeLake CPU based on a 5512 build XP,tryed many of your ACPI.sys modded file with AHCI drivers from Fernando and the new from Daniel_k.
In the best case install work with F7 to ignore ACPi but it seems that CPU isn't recognize in OS and also TurboV software doesn't work.
Do you think there's a way to have it working well ? I'm sure I did something wrong cause I don't understand anything about coding or hacking file so that's why I prefer asking help for expert.
I want it for overclocking and benchmarking not for H24 use.
Thanks for your help.

#2268

skullteria

> Zitat von ⇗ diderius6 im Beitrag ¶ #2266

> @daniel_k
> Yesssaaaaa:)))), thanks a lot, works on Shorthorn files to boot XP SP3
> this makes also @skullteria happy, I know for sure
> Dietmar

Please man, test with integrated GPU (intel HD graphics).
I made some patch on winload to disable permanently signature check. On X64 too, however, need add a option on boot entry or patch bootmgr too.

#2269 | diderius6 | ⇗ @skullteria I do not have a modern CPU, which has working Intel HD graphics for XP. I do not know, if there is any Dietmar

#2270

diderius6

⇗ @Doc.Brown
The Maximus XI Gene has an Intel® Z390 Chipset.
I succeed to install XP SP3 on the EVGA z390 dark board,
so it should work there also.
Integrate the last acpi.sys from ⇗ @daniel_k and also the STORAHCI driver via nlite
together with storport.sys from ⇗ @skullteria
Dietmar

#2271

skullteria

> Zitat von ⇗ diderius6 im Beitrag ¶ #2269

> @skullteria
> I do not have a modern CPU,
> which has working Intel HD graphics for XP.
> I do not know, if there is any .
> Dietmar

My system what i tested is 2nd generation...HD 3000. I will try get the error.Well, i'm very thankful and happy. Only x64 needed now. I will test UEFI too.

> Zitat von ⇗ daniel_k im Beitrag ¶ #2264

> @diderius6, for x86 it was easy.

Please Daniel_k, made it to x64 too

#2272

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #2270

> @Doc.Brown
> The Maximus XI Gene has an Intel® Z390 Chipset.
> I succeed to install XP SP3 on the EVGA z390 dark board,
> so it should work there also.
> Integrate the last acpi.sys from ⇗ @daniel_k and also the STORAHCI driver via nlite
> together with storport.sys from @skullteria
> Dietmar

⇗ @diderius6
Yes cause the Dark has the full bios compatibility with XP like older Asus Apex IX and X had with specific overclocking bios but the new XI products doesn't have this support.
I "ll test your methodology,by STORAHCI you mean AMDXHCI_XP_FINAL by ⇗ @daniel_k or another else ? and also I don't know where to put the 2 Storeport.sys files,they aren't in i386 folder it seems ?
Thanks

#2273 | diderius6 | ⇗ @Doc.Brown No, it is the STORAHCI driver from ⇗ @skullteria together with storport.sys see all in post 1020 here Dietmar PS: The storport.sys driver needs to be put by hand into i386 installationfolder for CD.

#2274

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #2273

> @Doc.Brown
> No, it is the STORAHCI driver from @skullteria together with storport.sys see all in
> post 1020 here
> Dietmar
> PS: The storport.sys driver needs to be put by hand into i386 installationfolder for CD.

⇗ @diderius6
hum ok,found it but I put the 2 files in original STORAHCI folder before integrate driver with nlite ?
there's no need of AHCI driver at all ?
Thanks for your help :)
Edit: just saw your edit after posting so I put the 2 STORPORTin the original folder racine of STORAHCI and then copy into i386 if I understand well ...sorry i'm french,nobody is perfect xD
Edit 2: I put 2x STOREPORT files into i386 XP folder and integrate STORAHCI with nlite,change the ACPI file also and after create the iso,hope i'm right ^^

#2275 | skullteria | Well, a interestering thing: until build 5231, winload works on XP x64 without problem, don't need nogui. Starting build 5270, has some issue with BootVid VidResetDisplay. Maybe changing winload we can laod XP x64
#2276 | daniel_k | If you're going to share info and files, I'll help. Otherwise, I won't help to fix something that is copyrighted or open source just for private use.
#2277 | skullteria | I can share the files...For now, i shared only info. Well, can you fix acpi fro x64 to load winload?
#2278 | diderius6 | _

#2279

Doc.Brown

> Zitat von ⇗ Doc.Brown im Beitrag ¶ #2274

> > Zitat von ⇗ diderius6 im Beitrag ¶ #2273

> > @Doc.Brown
> > No, it is the STORAHCI driver from @skullteria together with storport.sys see all in
> > post 1020 here
> > Dietmar
> > PS: The storport.sys driver needs to be put by hand into i386 installationfolder for CD.

> ⇗ @diderius6
> hum ok,found it but I put the 2 files in original STORAHCI folder before integrate driver with nlite ?
> there's no need of AHCI driver at all ?
> Thanks for your help :)
> Edit: just saw your edit after posting so I put the 2 STORPORTin the original folder racine of STORAHCI and then copy into i386 if I understand well ...sorry i'm french,nobody is perfect xD
> Edit 2: I put 2x STOREPORT files into i386 XP folder and integrate STORAHCI with nlite,change the ACPI file also and after create the iso,hope i'm right ^^

⇗ @diderius6
Sadly it results on another BSOD :
⇗ https://cdn.discordapp.com/attachments/3...54/IMG_2096.JPG
Disk are well recognized,this BSOD came after when the real XP set up start,installation launched without pressing F7 ...
Thanks :)

#2280

diderius6

⇗ @Doc.Brown
In this case, the only thing that helps is,
to set XP up on another, more XP friendly compi
and later connect this XP to first one.
It can be done with the STORAHCI driver,
because it is really generic,
Dietmar

## Page 153

#2281

cedar

⇗ @diderius6, ⇗ @daniel_k
Keep up the good works!
I made a fresh bootable storahci XP64 Window with only default vga driver on my old Ivy system.
Then add the latest acpi64 driver from Daniel_K and swapp the hard disk to the Asus Prime B350 Ryzen board.
Regular boot always get BSOD, I can boot into safe mode,
so I installed AMD chipset and usb 3.1 driver within Safe mode. Usb 3.1 worked. Nvidia GS8400 also installed.
I installed my motherboard's Amdpcidev.sys on both PCI entries PCI\VEN_1022&DEV_1455 and PCI\VEN_1022&DEV_145A both failed with yellow bangs.
I also tried Canonkong's Amdpcidev.sys from x570 board, it didn't work either.
After some drivers installations and reboots to test, sometime I can get back to safe mode using last good configuration
,but could not boot regular mode. I think it might be PCI issue.
Eventually I got.
irql_not_less_or_equal error BSOD as
0X0000000A (0X0000000000000014, 0X000000000000000C,0X0000000000000000,
0XFFFFF80000107984D)
After this I can't get back to XP64 safe mode even using last good configuration.
Could you please look into that?
However, 2003 x64 seems to work, but need further tests on my board to see
how it goes.

#2282 | Doc.Brown | ⇗ @diderius6 Ok it will be test,thanks for your quick reply ;)
#2283 | infuscomus | ⇗ @sqpp ⇗ @Doc.Brown can you test with XP ACPI 32bit instead of 64bit? - you might have better luck getting 32bit to work
#2284 | Doc.Brown | ⇗ @infuscomus It is already an 32 bit XP used with latest ACPI from ⇗ @daniel_k

#2285

cedar

⇗ @infuscomus
Good works!. Your 1st attempt ACPI 64 version can boot 2003 too, but not on XP, 2nd attempt version, BSOD.
I need to create 3 or more hard ware profiles after install drivers to test on both Daniel_K latest 64 bit
and your 1st version ,on both XP and 2003.
Some profiles will boot, other profiles will BSOD on 2003.

#2286

Gelip

> Zitat von ⇗ diderius6 im Beitrag ¶ #2165

> Hi,
> does anybody know,
> where I can get SYMBOLS for
> the XP64 DEBUG SP2 version
> Dietmar
> PS: In this case, acpi.pdb for the debug XP 64 SP2 would be enough.
> 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
> EDIT:
> It is in file
> WindowsServer2003-KB933548-v1-x64-symbols-NRL-ENU-DEBUG.exe

Direct links to symbol files in post number #6 on the ⇗ arabhardware.net forum. You can also enter the site's ⇗ archive and see the full .exe file names :-)
Now in Firefox, press Ctrl + F, paste the searched file name, e.g. WindowsServer2003-KB933548-v1-x64-symbols-NRL-ENU-DEBUG.exe, mark the link on the page and select Save target as... from the context menu:
⇗
I attach all links in txt file:
Gelip has attached files to this post

- ⇗ symbol_links.txt

#2287 | diderius6 | ⇗ @Gelip I see the download link for the symbols. But they seem to link to the Microsoft page and download from there does not work Dietmar
#2288 | skullteria | I have symbols packages from XP until Win8, want place here or pm?

#2289

Gelip

> Zitat von ⇗ skullteria im Beitrag ¶ #2288

> I have symbols packages from XP until Win8, want place here or pm?

Yes, please for WinXP 32 and 64 bit. Thx

#2290

skullteria

> Zitat von ⇗ Gelip im Beitrag ¶ #2289

> > Zitat von ⇗ skullteria im Beitrag ¶ #2288

> > I have symbols packages from XP until Win8, want place here or pm?

> Yes, please for WinXP 32 and 64 bit. Thx

Here:
Windows XP x64:
⇗ https://www.adrive.com/public/Kk44M8/Win...ols-NRL-ENU.exe
Windows XP SP3:
⇗ https://www.adrive.com/public/K8GKd5/Win...-update-ENU.exe

#2291

infuscomus

> Zitat von ⇗ skullteria im Beitrag ¶ #2275

> Well, a interestering thing: until build 5231, winload works on XP x64 without problem, don't need nogui. Starting build 5270, has some issue with BootVid VidResetDisplay. Maybe changing winload we can laod XP x64

⇗ @skullteria
can we use bootvid from vista beta to solve this?

#2292

skullteria

> Zitat von ⇗ infuscomus im Beitrag ¶ #2291

> > Zitat von ⇗ skullteria im Beitrag ¶ #2275

> > Well, a interestering thing: until build 5231, winload works on XP x64 without problem, don't need nogui. Starting build 5270, has some issue with BootVid VidResetDisplay. Maybe changing winload we can laod XP x64

> @skullteria
> can we use bootvid from vista beta to solve this?

Unfortunately, the problem is not in bootvid. I tried Vista RTM bootvid, however, get same error. The real problem is in HalResetDisplay, or HalpResetDisplay. In x64, it is Int10 emulated, and in vista has some change.

#2293

Gelip

In VMware Workstation 8.0.2 build-591240 WinXP x86 or x64 works without problems in EFI32 and EFI64 on the graphics driver VMware Tools (VMware SVGA II) with EFI files from beta Longhorn Vista x86 6.0.5219.0 and beta Longhorn Server 6.0.6001.16497 x64, beta Longhorn Vista 6.0.5384.4 x64. The VMware graphics card has no GOP firmware:
⇗
On real hardware WinXP x64 work only with VBEMP (AnaPa).

#2294

diderius6

I just try UEFI boot for XP64 on the Giga H110 board. The XP64 sits as C:\ on a MBR with ntfs formatted harddisk
and is amazing stable, nothing yellow in device manager.
Just to copy the 64 bit EFI folder on C:\ and winload.efi into windows\system32 does not work.
The harddisk is still shown as CSM harddisk, no possibility to chose UEFI for the harddisk via F12 (chose Bootdevice).
When I force in Bios disable CSM,
the harddisk entry via F12 is gone,
Dietmar
PS: When I put the EFI folder on an USB stick, formatted with FAT32,
I can chose UEFI boot, even with complete disabled CSM in Bios.
But then comes the message, that winload.efi was not found
in windows\system32, even it is there.
This may be, because via USB stick UEFI does not find the way to the ntfs formatted harddisk
with MBR. So, a lot of more work has to be done.

#2295 | infuscomus | ⇗ @diderius6 try creating a small 100mb primary active fat32 partition at the start of the drive and put the \BOOT\EFI files in there I think thats what windows 8 and 10 use

## Page 154

#2296

diderius6

⇗ @infuscomus
I just put an extra 7 Gbyte Fat32 partition (primary partition, visable) on the same harddisk.
Now I can chose UEFI boot.
Ok, again I was told, that winload.efi was not there.
I copy an extra folder windows\system32\ there on the Fat32 partition with winload.efi in it.
Now I get message, that windows\system32\config is missed.
Aha, I understand, UEFI looks ONLY on that Fat32 partition.
So, in next step I copy the whole Windows folder on it,
and we will see
Dietmar
PS: May be, that can be controlled via the BCD file on the FAT32 partition.
But I dont know, how I have to change the settings in BCD, so that on next time
it uses the ntfs partition.
But who knows, maybe the whole XP64 can be started from Fat32.
EDIT: May be, the BIOS of the Giga H110 board has no UEFI driver for the ntfs file system.
EDIT2: Now I get screen with "Starting Windows Vista" but hangs there.
EDIT3: I enlarge the Fat32 partition to 28 Gbyte. There I copy the whole XP64 installation from ntfs partition.
Oho, there are a lot of new possibilities. Just copy the UEFI nvme driver to Bios and start from old Compi UEFI via nvme:))!

#2297 | infuscomus | ⇗ @diderius6 BootICE can edit BCD settings for you

#2298

Gelip

> Zitat von ⇗ diderius6 im Beitrag ¶ #2294

> I just try UEFI boot for XP64 on the Giga H110 board. The XP64 sits as C:\ on a MBR with ntfs formatted harddisk
> and is amazing stable, nothing yellow in device manager.
> Just to copy the 64 bit EFI folder on C:\ and winload.efi into windows\system32 does not work.
> The harddisk is still shown as CSM harddisk, no possibility to chose UEFI for the harddisk via F12 (chose Bootdevice).
> When I force in Bios disable CSM,
> the harddisk entry via F12 is gone,
> Dietmar
> PS: When I put the EFI folder on an USB stick, formatted with FAT32,
> I can chose UEFI boot, even with complete disabled CSM in Bios.
> But then comes the message, that winload.efi was not found
> in windows\system32, even it is there.
> This may be, because via USB stick UEFI does not find the way to the ntfs formatted harddisk
> with MBR. So, a lot of more work has to be done.

Please read this my topic carefully and the links in the subject: ⇗ https://www.betaarchive.com/forum/viewto...=444391#p444391

#2299 | Gelip | Read this: ⇗ https://www.betaarchive.com/forum/viewto...=435277#p435277
#2300 | Gelip | Yes, my file BCD need edit in BOOTICE (Professional mode) - select partition NTFS in ApplicationDevice and OSDevice

#2301

diderius6

⇗ @Gelip
I try direct UEFI boot from Fat32 partition,
using
xxcopy /k /r /e /i /s /c /h Q:\ R:\
where Q is the working XP64 ntfs partition with all UEFI files on it
and R empty FAT32 partition
Dietmar

#2302 | Gelip | No, no, no - read PM
#2303 | infuscomus | ⇗ @daniel_k do you still have your modified AMD generic AHCI drivers?
#2304 | kukonosau | ⇗ @cedar How to start Windows XP x64 on ASUS AM4 B350 PRIME B350M-K? Where is daniel_k acpi.sys and storage drivers skullteria?
#2305 | daniel_k | ⇗ @infuscomus, can be found in the following posts: ¶ Windows XP SP3 32bit and modern PC parts (112) ¶ Windows XP SP3 32bit and modern PC parts (114)

#2306

cedar

⇗ @kukonosau
XP64 only boot in safe mode by luck. 2003 can boot normally
, but both are not stable either.
I installed them in another computer and moved the hard disk to Ryzen
system. Burning discs boot directly on Ryzen didn't work that well for me.
Make sure to create lot of hardware profiles in XP or 03. By luck, some can boot,
others may not. USB3.0 does not work consistently on my board on XP32,
but 64bit USB3.0 works on mouse and thumb drives.
64 ACPI drivers tested were from post #2202 or infuscomus first attemp.
Even Mplayer classic playing mkv files can instantly reboot Win2003.
So it is not too stable, although .mpg and avi can play in Mplayer.
I still need to test it if it can be fixed.

#2307 | infuscomus | ⇗ @daniel_k thanks very much. ⇗ @cedar what stability issues have you come across?

#2308

Illen

> Zitat von ⇗ diderius6 im Beitrag ¶ #2296

> EDIT: May be, the BIOS of the Giga H110 board has no UEFI driver for the ntfs file system.

Yep, forgot to mention that some UEFI firmwares might not be able to read from NTFS. In such cases, you either want to create a small FAT32 partition with EFI folder in it, and keep the Windows install with winload.efi on NTFS partition (and modify the BCD as mentioned in ¶ post#2300) , or keep the whole install on FAT32 partition and boot from there.

> Zitat von ⇗ diderius6 im Beitrag ¶ #2296

> EDIT2: Now I get screen with "Starting Windows Vista" but hangs there.

Did you install the Anapa VBE driver, and are you sure it works?

#2309

cedar

⇗ @infuscomus
0n Win 2003, even if i can boot a certain hardware profile several time
in a row, it can reboot instantly the next time. With 5 or 6 profiles, so
far, I can boot with luck by choosing a different hardware profile.
sometime I have to choose 3 profiles, and 1 will boot. others will
instantly reboot the machine.
Those hardware profiles are created after installing USB, Network, sound
, XP friendly GForce 8400GS and ATI HDTV Wonder.
These hardwares are very stable on XP32.
On 64 bit 2003. USB 2 to 3.1 all work.
Network not work yet.
Beyond TV (may reboot machine) and SichBoPVR not work yet.
it could be DirectX problems. its past all DirectX tests, but on next reboot,
some components of DirectX are not enabled anymore.
Mplayer Classic reboot machine on .mkv and .mp4. maybe LAV splitter
problems.
All programs above work well under XP32 on Ryzen, as well
as under XP64 on Ivy board.
Some of the problems are video related, may be fixable with
different software versions. while others are probably harder
to fix.

#2310 | kukonosau | ⇗ @diderius6 Thanks! I started Windows XP X64 with ACPI from post 2202, but with some times. A lot of different BSOD, for example 7E, 0A, 7B, irql not less or equal and so on!!! I install XP in VirtualBox, create reserve copy with Acronis 2014. Send copy from virtual XP in Windows 10. Installed copy in hardware with Acronis Universal Restore. I deleted all drivers and add storport drivers from skullteria. But, unfortunately, after 2nd sucessfully loading I get BSOD again(((

## Page 155

#2311

Gelip

> Zitat von ⇗ kukonosau im Beitrag ¶ #2310

> @diderius6
> Thanks! I started Windows XP X64 with ACPI from post 2202, but with some times. A lot of different BSOD, for example 7E, 0A, 7B, irql not less or equal and so on!!! I install XP in VirtualBox, create reserve copy with Acronis 2014. Send copy from virtual XP in Windows 10. Installed copy in hardware with Acronis Universal Restore. I deleted all drivers and add storport drivers from skullteria. But, unfortunately, after 2nd sucessfully loading I get BSOD again(((

Try deploy WinXP x64 in this way ⇗ How to deploy WinXP 64-bit on a UEFI >⇗ read this< and start under UEFI:

> Zitat

> The VGA controller can be turned off in a running system after make Reseal - just select the Quit option in Sysprep. Now delete display.inf and vga & VgaSave services from registry in CurrentControlSet key.

#2312 | infuscomus | I think the windows partition should be separate from the UEFI partition. That way the windows partition can still be formatted as NTFS with EFI as fat32 and just point the UEFI bootloader to the NTFS partition from there.

#2313

Gelip

> Zitat von ⇗ infuscomus im Beitrag ¶ #2312

> I think the windows partition should be separate from the UEFI partition.
> That way the windows partition can still be formatted as NTFS with EFI as fat32 and just point the UEFI bootloader to the NTFS partition from there.

I think, I think
Yes 100MB FAT32 for bootx64.efi and BCD files and NTFS for Windows with winload.efi file. It has been checked a long time ago - please read the links it provides or the whole topic on betaarchive ⇗ https://www.betaarchive.com/forum/viewtopic.php?f=61&t=20327 in which I performed the most tests with start WinXP on UEFI.
P.S. If the BIOS has an NTFS driver then only one NTFS partition can be used.
You can also boot the system from a FAT32 pendrive, but the most convenient is the FAT32 + NTFS partition just like in newer Windows starting from Win7 x64 on UEFI.

#2314

Gelip

> Zitat von ⇗ diderius6 im Beitrag ¶ #1145

> May be we need WDFLDR.SYS (from Vista-Longhorn5048, Vista, Win7) all 32 bit
> for XP for Intel USB
> Dietmar
> PS:Intel USB 3 drivers need WDFLDR.SYS (Kernel Mode Driver Framework LOADER) which doesn't exist on XP.
> XP drivers require coinstaller WdfCoInstaller01009.dll (included with driver, it installs wdfldr.sys and wdf01000.sys) and separate usbd.sys.
> I install the Microsoft Kernel Mode Driver Framework runtime 'Microsoft Kernel-Mode Driver Framework Install-v1.9-Win2k-WinXP-Win2k3.exe' extracted from WdfCoinstaller01009.dll which is the co-installer for KMDF 1.9.
> This drivers here have all only dependecies for XP!
> EDIT: This brings me to the idea, to install the very first USB driver from NEC on Longhorn 5048 for Intel chipset USB3.0.

I need driver 1.9 for WinXP x64 (⇗ https://support.microsoft.com/pl-pl/help...sta-and-for-win)

#2315

diderius6

I have XP64 on Fat32 partition (only first, one partition on HD).
And I installed the ANAPA driver for XP64, set start=4 to vga and vgasave in registry,
but still the compi hangs after Vista bootscreen on the Giga H110 board
Dietmar
PS: No difference between 16497 version and 5384.4.
Now I try to set up a debug session.
With the 5384.4 version this is not possible, even it has boot.ini.
So I hope for BCD, set debug option there via EasyBCD.
No debug at all possible.

#2316 | infuscomus | ⇗ @diderius6 are you able to remote desktop into it?

#2317

Gelip

> Zitat von ⇗ diderius6 im Beitrag ¶ #2315

> I have XP64 on Fat32 partition (only first, one partition on HD).
> And I installed the ANAPA driver for XP64, set start=4 to vga and vgasave in registry,
> but still the compi hangs after Vista bootscreen on the Giga H110 board
> Dietmar
> PS: No difference between 16497 version and 5384.4.
> Now I try to set up a debug session.
> With the 5384.4 version this is not possible, even it has boot.ini.
> So I hope for BCD, set debug option there via EasyBCD.
> No debug at all possible.

What graphics card are you using? If the card has GOP (UEFI) firmware and WinXP x64 drivers then install the driver, disable CSM and try to run WinXP in UEFI - here I wrote what idea I have to implement: ⇗ My new idea to try boot WinXP x64 on UEFI

#2318

Gelip

First in legacy bios mode, install all device drivers and AnaPa and check if the system works properly in legacy bios mode !!! Only after you check that the system works OK in legacy bios mode can you try to run under UEFI.
Remote Desktop will of course be useful but only if you have installed the network card drivers.
Maybe you use wrong AnaPa driver? You need use driver exactly from vbempk\VBE30\XPAMD64\PNP with my >⇗ fix<.

#2319 | diderius6 | ⇗ @Gelip I tried all this, XP64 hangs during boot Dietmar

#2320

Gelip

If you use Anapa, you do not need to disable services in the registry.
Try without any graphics driver (install all other drivers including Ethernet), enable Remote Desktop and remove two vga and vgasave services from CurrentControlSet from the registry. Run WinXP in uefi and check from another computer if you have access via a remote desktop.
P.S. If the sound drivers are installed, you should hear the Windows startup sound when Starting Windows Vista is on the screen.

#2321 | Gelip | If you had the manufacturer's graphics driver installed before, you must uninstall it and remove the oemx.inf file from the WINDOWS/Inf directory (created by the driver installer), otherwise the system will automatically reinstall the graphics card driver after restart.
#2322 | Gelip | If use AnaPa you need install VBE Miniport (manufacturer) (for GeForce card VBE Miniport (nVidia) ) driver not VBE Miniport - Standard PCI Graphics Adapter (VGA)

#2323

Gelip

On the ThinkPad X220 WinXP SP2 x64 it runs 100% OK in UEFI on the AnaPa driver - attached.
Gelip has attached files to this post

- ⇗ vbemp_x64_fix.zip

#2324

diderius6

⇗ @Gelip
I use your driver,
install it new,
set Bios to default settings,
does not help.
Only via MBR XP64 starts to desktop,
via UEFI it hangs during boot,
screen shows all the time "Starting Windows Vista"
Dietmar

#2325

Gelip

> Zitat von ⇗ diderius6 im Beitrag ¶ #2324

> @Gelip
> I use your driver,
> install it new,
> set Bios to default settings,
> does not help.
> Only via MBR XP64 starts to desktop,
> via UEFI it hangs during boot,
> screen shows all the time "Starting Windows Vista"
> Dietmar

I just tested on ASUS P8H61-M LE R2 with the latest bios 1408 and unfortunately WinXP also does not start with the AnaPa driver or without any graphics driver + removed vga and VgaSave services. It looks like it doesn't work on some motherboards
But it still works for others e.g. ASrock Z170 Pro4S:

## Page 156

#2326

diderius6

⇗ @Gelip
I just set up a brand new XP64 on the Asrock fatal1ty z370 gaming k6 board with Fat32.
Then I install there the Anapa driver.
But it boots only via MBR,
hangs during UEFI boot
Dietmar

#2327 | diderius6 | ⇗ @Gelip Can you please enable in BCD from folder server_BCD (64 bit Uefi) the debug option for me Dietmar

#2328

Gelip

> Zitat von ⇗ diderius6 im Beitrag ¶ #2327

> @Gelip
> Can you please enable in BCD from folder server_BCD (64 bit Uefi)
> the debug option for me
> Dietmar

The best tool for editing a BCD file and more is BOOTICE v1.3.2 x64 or x86 by Pauly - attached. This tool works on WinXP To enable debugging on COM1, edit the file like this:
⇗
Gelip has attached files to this post

- ⇗ booticex86_v1.321.rar
- ⇗ booticex64_v1.321.rar

#2329

Gelip

I connected WinDbg to ASUS and it turns out that the problem is caused by the VIDEOPRT.SYS file and/or the AHCI driver regardless of whether we use the AnaPa driver or boot the system without any graphics driver (vga and VgaSave services removed):

    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.

    Opened \\.\com1
    Waiting to reconnect...
    Connected to Windows Server 2003 3790 x64 target at (Sun Sep  8 09:14:38.008 2019 (GMT+2)), ptr64 TRUE
    Kernel Debugger connection established.
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
    Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64
    Built by: 3790.srv03_sp2_rtm.070216-1710
    Machine Name:
    Kernel base = 0xfffff800`01800000 PsLoadedModuleList = 0xfffff800`019d5100
    System Uptime: not available

    Intel Storage Driver Ver: 11.2.0.1006

    KDTARGET: Refreshing KD connection

    *** Fatal System Error: 0x00000050
                           (0xFFFFFADFCB40202A,0x0000000000000000,0xFFFFF800018E2CAE,0x0000000000000000)

    Break instruction exception - code 80000003 (first chance)

    A fatal system error has occurred.
    Debugger entered on first try; Bugcheck callbacks have not been invoked.

    A fatal system error has occurred.

    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {fffffadfcb40202a, 0, fffff800018e2cae, 0}

    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntdll.dll -
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for VIDEOPRT.SYS -
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys -
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Probably caused by : VIDEOPRT.SYS ( VIDEOPRT!VideoPortSetTrappedEmulatorPorts+5e )

    Followup: MachineOwner
    ---------

    nt!DbgBreakPointWithStatus:
    fffff800`01826db0 cc              int     3

#2330

Gelip

You may need to patch the VIDEOPRT.SYS and/or VGA.SYS file to not traps ports of the graphic board. Such a patch exists but only for WinXP 32-bit:

- ⇗ Installation note 5: My driver does not provide any support for running fullscreen DOS applications in VESA graphics modes. VGA.SYS controls it and in most cases it traps i/o ports and prevents VESA-based programs to run correctly. There are third-party patches - WinXPFix Utility (nomissoft.com/service.html#as2downloads) and 'Videoport driver patch for VESA in NTVDM' (volny.cz/martin.sulak/, direct download videoprt.zip) that fixes VGA.SYS behaviour. Try them if you need to run DOS programs in Windows. I am not affiliate with author(s) of these programs.
- ⇗ patch for WinXP/2000 monitor issues

@diderius
Maybe you can do it?

#2331

Mov AX, 0xDEAD

> Zitat

> Probably caused by : VIDEOPRT.SYS ( VIDEOPRT!VideoPortSetTrappedEmulatorPorts+5e

> Zitat von ⇗ Gelip im Beitrag ¶ #2330

> You may need to patch the VIDEOPRT.SYS and/or VGA.SYS file to not traps ports of the graphic board

VideoPortSetTrappedEmulatorPorts of VIDEOPRT.SYS on win2003 x64 FRE is only two asm commands:

    mov     eax, 57h
    retn

probably error in next proc, pVideoPortInitializeInt10
but if you using CHK version of VIDEOPRT.SYS it may be diff proc

#2332

diderius6

⇗ @Gelip
Thanks a lot for bootice:))!
I noticed on the Asrock k6 the same error using windbg
belonging to videoprt.sys
Dietmar

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Opened \\.\com1
    Waiting to reconnect...
    Connected to Windows Server 2003 3790 x64 target at (Sun Sep  8 10:34:00.281 2019 (UTC + 2:00)), ptr64 TRUE
    Kernel Debugger connection established.
    WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
    Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
    *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
    Executable search path is: C:\localsymbols
    Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64
    Built by: 3790.srv03_sp2_rtm.070216-1710
    Machine Name:
    Kernel base = 0xfffff800`00c00000 PsLoadedModuleList = 0xfffff800`00dd5100
    System Uptime: not available
    AhciHwFindAdapter finishing
    AhciHwFindAdapter finishing
    KDTARGET: Refreshing KD connection

    *** Fatal System Error: 0x00000050
                                                 (0xFFFFFADCC100202A,0x0000000000000000,0xFFFFF80000CE2CAE,0x0000000000000000)

    Break instruction exception - code 80000003 (first chance)

    A fatal system error has occurred.
    Debugger entered on first try; Bugcheck callbacks have not been invoked.

    A fatal system error has occurred.

    Connected to Windows Server 2003 3790 x64 target at (Sun Sep  8 10:35:24.250 2019 (UTC + 2:00)), ptr64 TRUE
    Loading Kernel Symbols
    ...............................................................
    ................
    Loading User Symbols
    ........
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {fffffadcc100202a, 0, fffff80000ce2cae, 0}

    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for CSRSRV.dll -
    Probably caused by : VIDEOPRT.SYS ( VIDEOPRT!pVideoPortInitializeInt10+4e )

    Followup: MachineOwner
    ---------

    nt!DbgBreakPointWithStatus:
    fffff800`00c26db0 cc              int     3
    8: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffffadcc100202a, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80000ce2cae, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000000, (reserved)

    Debugging Details:
    ------------------

    READ_ADDRESS:  fffffadcc100202a

    FAULTING_IP:
    nt!MmMapIoSpace+489
    fffff800`00ce2cae 668b4e1a        mov     cx,word ptr [rsi+1Ah]

    MM_INTERNAL_CODE:  0

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  csrss.exe

    CURRENT_IRQL:  2

    TRAP_FRAME:  fffffadcc0376900 -- (.trap 0xfffffadcc0376900)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff6fd6e5ec0f0 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffffadcc070b101 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80000ce2cae rsp=fffffadcc0376a90 rbp=0000000000000000
     r8=000000fffffff000  r9=0000000000000002 r10=0000000000000eff
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    nt!MmMapIoSpace+0x489:
    fffff800`00ce2cae 668b4e1a        mov     cx,word ptr [rsi+1Ah] ds:b180:001a=????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff80000cd673e to fffff80000c26db0

    STACK_TEXT:
    fffffadc`c0376148
     fffff800`00cd673e : 00000000`00000008 fffffadc`c0376900
    fffffadc`c100202a fffff800`00c5669e : nt!DbgBreakPointWithStatus
    fffffadc`c0376150
     fffff800`00cd7d0e : fffff800`00000003 00000000`00000050
    fffffadc`c100202a 00000000`00000000 : nt!KiBugCheckDebugBreak+0x1e
    fffffadc`c03761b0
     fffff800`00c2ea54 : fffffadc`c0376830 fffffadc`00000004
    fffffadc`c0376c64 fffffadc`c0376c10 : nt!KeBugCheck2+0x640
    fffffadc`c03767f0
     fffff800`00ca58f2 : 00000000`00000050 fffffadc`c100202a
    00000000`00000000 fffffadc`c0376900 : nt!KeBugCheckEx+0x104
    fffffadc`c0376830
     fffff800`00c2d519 : 00000000`00000011 fffff800`00e9534b
    fffffadc`c0376900 fffffadc`c03769d0 : nt!MmAccessFault+0xa1f
    fffffadc`c0376900
     fffff800`00ce2cae : 00000000`0000087b 00000000`00000000
    fffffadc`c1000000 00000000`00000000 : nt!KiPageFault+0x119
    fffffadc`c0376a90
     fffffadc`be4a813e : fffffadc`00000001 00000000`00100000
    fffffadc`00000000 fffffa80`00677000 : nt!MmMapIoSpace+0x489
    fffffadc`c0376b60
     fffffadc`be4b28b3 : 00000000`00000000 00000000`00000000
    00000000`00000000 00000000`00000000 :
    VIDEOPRT!pVideoPortInitializeInt10+0x4e
    fffffadc`c0376ba0
    fffff800`00e837c9 : fffffadc`e0511070 fffffadc`e03e69d0
    fffffadc`e0511070 fffff800`00e83170 : VIDEOPRT!pVideoPortDispatch+0xca3
    fffffadc`c0376cc0
     fffff800`00e81164 : fffffadc`e0511070 fffffadc`e0511020
    fffffadc`c0376ff0 00000000`00000000 : nt!IopParseDevice+0x1088
    fffffadc`c0376e70
     fffff800`00e85887 : 00000000`00000000 fffffadc`c0376fe0
    00000000`00000240 00000000`00000000 : nt!ObpLookupObjectName+0x931
    fffffadc`c0376f80
     fffff800`00e92e4d : 00000000`00000001 fffffadc`c03774e0
    00000000`00000001 fffff800`00c241ce : nt!ObOpenObjectByName+0x180
    fffffadc`c0377170
     fffff800`00e99ef7 : fffffa80`0066e4d0 fffff800`00c3c37e
    fffffa80`0066e4a0 00000000`00000500 : nt!IopCreateFile+0x630
    fffffadc`c0377300
     fffff800`00e958f9 : 00000000`00000000 fffffa80`00001c80
    fffffadc`dff1ac20 fffffadc`e0556750 : nt!IoCreateFile+0x12f
    fffffadc`c03773e0
     fffff800`00c2e3fd : fffffadc`e0556750 fffffadc`c03774e0
    00000000`00000000 00000000`00000000 : nt!NtOpenFile+0x49
    fffffadc`c0377460
     fffff800`00c2e8c0 : fffff800`00e7ec67 00000000`00000000
    000007ff`7c5c9620 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
    fffffadc`c0377668
     fffff800`00e7ec67 : 00000000`00000000 000007ff`7c5c9620
    00000000`00000000 00000000`00000001 : nt!KiServiceLinkage
    fffffadc`c0377670
     fffff97f`ff008587 : 00000000`00000000 00000000`00000000
    00000000`00000001 00000000`00000000 : nt!IoGetDeviceObjectPointer+0x57
    fffffadc`c0377700
     fffff97f`ff00334d : 00000000`00000001 00000000`00000000
    00000000`00000003 00000000`00000001 :
    win32k!DrvUpdateGraphicsDeviceList+0x4ba
    fffffadc`c0377900
    fffff97f`ff008d8c : fffffadc`c0377a38 00000000`00000000
    00000000`01bc8000 00000000`00000000 : win32k!DrvInitConsole+0xd5
    fffffadc`c0377970
     fffff97f`ff00bb28 : 00000000`01bc8000 00000000`00000000
    00000000`00000003 00000000`00000000 : win32k!InitVideo+0xb
    fffffadc`c03779e0
     fffff97f`ff00b646 : 00000000`00000060 fffffadc`c0377cf0
    00000000`00000003 00000000`0000005c : win32k!UserInitialize+0x63c
    fffffadc`c0377c20
     fffff800`00c2e3fd : fffffadc`000001e0 00000000`00000001
    fffffadc`e0556750 00000000`00000020 : win32k!NtUserInitialize+0x15f
    fffffadc`c0377c70
     000007ff`7c7de86a : 000007ff`7c7deaa9 00000000`001657f0
    00000000`001657f0 00000000`00000003 : nt!KiSystemServiceCopyEnd+0x3
    00000000`0015fbc8
     000007ff`7c7deaa9 : 00000000`001657f0 00000000`001657f0
    00000000`00000003 00000000`00000000 : winsrv!NtUserInitialize+0xa
    00000000`0015fbd0
     000007ff`7c5b3eb8 : 00000000`00000000 00000000`00000001
    00000000`001657f0 00000000`00000000 :
    winsrv!UserServerDllInitialization+0x229
    00000000`0015fc50
    00000000`00000000 : 00000000`00000001 00000000`001657f0
    00000000`00000000 00000000`00100000 :
    CSRSRV!CsrUnhandledExceptionFilter+0x368

    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    VIDEOPRT!pVideoPortInitializeInt10+4e
    fffffadc`be4a813e 4c8bcb          mov     r9,rbx

    SYMBOL_STACK_INDEX:  7

    SYMBOL_NAME:  VIDEOPRT!pVideoPortInitializeInt10+4e

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: VIDEOPRT

    IMAGE_NAME:  VIDEOPRT.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP:  45d69799

    FAILURE_BUCKET_ID:  X64_0x50_VIDEOPRT!pVideoPortInitializeInt10+4e

    BUCKET_ID:  X64_0x50_VIDEOPRT!pVideoPortInitializeInt10+4e

    Followup: MachineOwner
    ---------

    8: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffffadcc100202a, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80000ce2cae, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000000, (reserved)

    Debugging Details:
    ------------------

    READ_ADDRESS:  fffffadcc100202a

    FAULTING_IP:
    nt!MmMapIoSpace+489
    fffff800`00ce2cae 668b4e1a        mov     cx,word ptr [rsi+1Ah]

    MM_INTERNAL_CODE:  0

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  csrss.exe

    CURRENT_IRQL:  2

    TRAP_FRAME:  fffffadcc0376900 -- (.trap 0xfffffadcc0376900)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff6fd6e5ec0f0 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffffadcc070b101 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80000ce2cae rsp=fffffadcc0376a90 rbp=0000000000000000
     r8=000000fffffff000  r9=0000000000000002 r10=0000000000000eff
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    nt!MmMapIoSpace+0x489:
    fffff800`00ce2cae 668b4e1a        mov     cx,word ptr [rsi+1Ah] ds:b180:001a=????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff80000cd673e to fffff80000c26db0

    STACK_TEXT:
    fffffadc`c0376148
     fffff800`00cd673e : 00000000`00000008 fffffadc`c0376900
    fffffadc`c100202a fffff800`00c5669e : nt!DbgBreakPointWithStatus
    fffffadc`c0376150
     fffff800`00cd7d0e : fffff800`00000003 00000000`00000050
    fffffadc`c100202a 00000000`00000000 : nt!KiBugCheckDebugBreak+0x1e
    fffffadc`c03761b0
     fffff800`00c2ea54 : fffffadc`c0376830 fffffadc`00000004
    fffffadc`c0376c64 fffffadc`c0376c10 : nt!KeBugCheck2+0x640
    fffffadc`c03767f0
     fffff800`00ca58f2 : 00000000`00000050 fffffadc`c100202a
    00000000`00000000 fffffadc`c0376900 : nt!KeBugCheckEx+0x104
    fffffadc`c0376830
     fffff800`00c2d519 : 00000000`00000011 fffff800`00e9534b
    fffffadc`c0376900 fffffadc`c03769d0 : nt!MmAccessFault+0xa1f
    fffffadc`c0376900
     fffff800`00ce2cae : 00000000`0000087b 00000000`00000000
    fffffadc`c1000000 00000000`00000000 : nt!KiPageFault+0x119
    fffffadc`c0376a90
     fffffadc`be4a813e : fffffadc`00000001 00000000`00100000
    fffffadc`00000000 fffffa80`00677000 : nt!MmMapIoSpace+0x489
    fffffadc`c0376b60
     fffffadc`be4b28b3 : 00000000`00000000 00000000`00000000
    00000000`00000000 00000000`00000000 :
    VIDEOPRT!pVideoPortInitializeInt10+0x4e
    fffffadc`c0376ba0
    fffff800`00e837c9 : fffffadc`e0511070 fffffadc`e03e69d0
    fffffadc`e0511070 fffff800`00e83170 : VIDEOPRT!pVideoPortDispatch+0xca3
    fffffadc`c0376cc0
     fffff800`00e81164 : fffffadc`e0511070 fffffadc`e0511020
    fffffadc`c0376ff0 00000000`00000000 : nt!IopParseDevice+0x1088
    fffffadc`c0376e70
     fffff800`00e85887 : 00000000`00000000 fffffadc`c0376fe0
    00000000`00000240 00000000`00000000 : nt!ObpLookupObjectName+0x931
    fffffadc`c0376f80
     fffff800`00e92e4d : 00000000`00000001 fffffadc`c03774e0
    00000000`00000001 fffff800`00c241ce : nt!ObOpenObjectByName+0x180
    fffffadc`c0377170
     fffff800`00e99ef7 : fffffa80`0066e4d0 fffff800`00c3c37e
    fffffa80`0066e4a0 00000000`00000500 : nt!IopCreateFile+0x630
    fffffadc`c0377300
     fffff800`00e958f9 : 00000000`00000000 fffffa80`00001c80
    fffffadc`dff1ac20 fffffadc`e0556750 : nt!IoCreateFile+0x12f
    fffffadc`c03773e0
     fffff800`00c2e3fd : fffffadc`e0556750 fffffadc`c03774e0
    00000000`00000000 00000000`00000000 : nt!NtOpenFile+0x49
    fffffadc`c0377460
     fffff800`00c2e8c0 : fffff800`00e7ec67 00000000`00000000
    000007ff`7c5c9620 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
    fffffadc`c0377668
     fffff800`00e7ec67 : 00000000`00000000 000007ff`7c5c9620
    00000000`00000000 00000000`00000001 : nt!KiServiceLinkage
    fffffadc`c0377670
     fffff97f`ff008587 : 00000000`00000000 00000000`00000000
    00000000`00000001 00000000`00000000 : nt!IoGetDeviceObjectPointer+0x57
    fffffadc`c0377700
     fffff97f`ff00334d : 00000000`00000001 00000000`00000000
    00000000`00000003 00000000`00000001 :
    win32k!DrvUpdateGraphicsDeviceList+0x4ba
    fffffadc`c0377900
    fffff97f`ff008d8c : fffffadc`c0377a38 00000000`00000000
    00000000`01bc8000 00000000`00000000 : win32k!DrvInitConsole+0xd5
    fffffadc`c0377970
     fffff97f`ff00bb28 : 00000000`01bc8000 00000000`00000000
    00000000`00000003 00000000`00000000 : win32k!InitVideo+0xb
    fffffadc`c03779e0
     fffff97f`ff00b646 : 00000000`00000060 fffffadc`c0377cf0
    00000000`00000003 00000000`0000005c : win32k!UserInitialize+0x63c
    fffffadc`c0377c20
     fffff800`00c2e3fd : fffffadc`000001e0 00000000`00000001
    fffffadc`e0556750 00000000`00000020 : win32k!NtUserInitialize+0x15f
    fffffadc`c0377c70
     000007ff`7c7de86a : 000007ff`7c7deaa9 00000000`001657f0
    00000000`001657f0 00000000`00000003 : nt!KiSystemServiceCopyEnd+0x3
    00000000`0015fbc8
     000007ff`7c7deaa9 : 00000000`001657f0 00000000`001657f0
    00000000`00000003 00000000`00000000 : winsrv!NtUserInitialize+0xa
    00000000`0015fbd0
     000007ff`7c5b3eb8 : 00000000`00000000 00000000`00000001
    00000000`001657f0 00000000`00000000 :
    winsrv!UserServerDllInitialization+0x229
    00000000`0015fc50
    00000000`00000000 : 00000000`00000001 00000000`001657f0
    00000000`00000000 00000000`00100000 :
    CSRSRV!CsrUnhandledExceptionFilter+0x368

    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    VIDEOPRT!pVideoPortInitializeInt10+4e
    fffffadc`be4a813e 4c8bcb          mov     r9,rbx

    SYMBOL_STACK_INDEX:  7

    SYMBOL_NAME:  VIDEOPRT!pVideoPortInitializeInt10+4e

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: VIDEOPRT

    IMAGE_NAME:  VIDEOPRT.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP:  45d69799

    FAILURE_BUCKET_ID:  X64_0x50_VIDEOPRT!pVideoPortInitializeInt10+4e

    BUCKET_ID:  X64_0x50_VIDEOPRT!pVideoPortInitializeInt10+4e

    Followup: MachineOwner
    ---------

    8: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffffadcc100202a, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80000ce2cae, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000000, (reserved)

    Debugging Details:
    ------------------

    READ_ADDRESS:  fffffadcc100202a

    FAULTING_IP:
    nt!MmMapIoSpace+489
    fffff800`00ce2cae 668b4e1a        mov     cx,word ptr [rsi+1Ah]

    MM_INTERNAL_CODE:  0

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  csrss.exe

    CURRENT_IRQL:  2

    TRAP_FRAME:  fffffadcc0376900 -- (.trap 0xfffffadcc0376900)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff6fd6e5ec0f0 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffffadcc070b101 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80000ce2cae rsp=fffffadcc0376a90 rbp=0000000000000000
     r8=000000fffffff000  r9=0000000000000002 r10=0000000000000eff
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    nt!MmMapIoSpace+0x489:
    fffff800`00ce2cae 668b4e1a        mov     cx,word ptr [rsi+1Ah] ds:b180:001a=????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff80000cd673e to fffff80000c26db0

    STACK_TEXT:
    fffffadc`c0376148
     fffff800`00cd673e : 00000000`00000008 fffffadc`c0376900
    fffffadc`c100202a fffff800`00c5669e : nt!DbgBreakPointWithStatus
    fffffadc`c0376150
     fffff800`00cd7d0e : fffff800`00000003 00000000`00000050
    fffffadc`c100202a 00000000`00000000 : nt!KiBugCheckDebugBreak+0x1e
    fffffadc`c03761b0
     fffff800`00c2ea54 : fffffadc`c0376830 fffffadc`00000004
    fffffadc`c0376c64 fffffadc`c0376c10 : nt!KeBugCheck2+0x640
    fffffadc`c03767f0
     fffff800`00ca58f2 : 00000000`00000050 fffffadc`c100202a
    00000000`00000000 fffffadc`c0376900 : nt!KeBugCheckEx+0x104
    fffffadc`c0376830
     fffff800`00c2d519 : 00000000`00000011 fffff800`00e9534b
    fffffadc`c0376900 fffffadc`c03769d0 : nt!MmAccessFault+0xa1f
    fffffadc`c0376900
     fffff800`00ce2cae : 00000000`0000087b 00000000`00000000
    fffffadc`c1000000 00000000`00000000 : nt!KiPageFault+0x119
    fffffadc`c0376a90
     fffffadc`be4a813e : fffffadc`00000001 00000000`00100000
    fffffadc`00000000 fffffa80`00677000 : nt!MmMapIoSpace+0x489
    fffffadc`c0376b60
     fffffadc`be4b28b3 : 00000000`00000000 00000000`00000000
    00000000`00000000 00000000`00000000 :
    VIDEOPRT!pVideoPortInitializeInt10+0x4e
    fffffadc`c0376ba0
    fffff800`00e837c9 : fffffadc`e0511070 fffffadc`e03e69d0
    fffffadc`e0511070 fffff800`00e83170 : VIDEOPRT!pVideoPortDispatch+0xca3
    fffffadc`c0376cc0
     fffff800`00e81164 : fffffadc`e0511070 fffffadc`e0511020
    fffffadc`c0376ff0 00000000`00000000 : nt!IopParseDevice+0x1088
    fffffadc`c0376e70
     fffff800`00e85887 : 00000000`00000000 fffffadc`c0376fe0
    00000000`00000240 00000000`00000000 : nt!ObpLookupObjectName+0x931
    fffffadc`c0376f80
     fffff800`00e92e4d : 00000000`00000001 fffffadc`c03774e0
    00000000`00000001 fffff800`00c241ce : nt!ObOpenObjectByName+0x180
    fffffadc`c0377170
     fffff800`00e99ef7 : fffffa80`0066e4d0 fffff800`00c3c37e
    fffffa80`0066e4a0 00000000`00000500 : nt!IopCreateFile+0x630
    fffffadc`c0377300
     fffff800`00e958f9 : 00000000`00000000 fffffa80`00001c80
    fffffadc`dff1ac20 fffffadc`e0556750 : nt!IoCreateFile+0x12f
    fffffadc`c03773e0
     fffff800`00c2e3fd : fffffadc`e0556750 fffffadc`c03774e0
    00000000`00000000 00000000`00000000 : nt!NtOpenFile+0x49
    fffffadc`c0377460
     fffff800`00c2e8c0 : fffff800`00e7ec67 00000000`00000000
    000007ff`7c5c9620 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
    fffffadc`c0377668
     fffff800`00e7ec67 : 00000000`00000000 000007ff`7c5c9620
    00000000`00000000 00000000`00000001 : nt!KiServiceLinkage
    fffffadc`c0377670
     fffff97f`ff008587 : 00000000`00000000 00000000`00000000
    00000000`00000001 00000000`00000000 : nt!IoGetDeviceObjectPointer+0x57
    fffffadc`c0377700
     fffff97f`ff00334d : 00000000`00000001 00000000`00000000
    00000000`00000003 00000000`00000001 :
    win32k!DrvUpdateGraphicsDeviceList+0x4ba
    fffffadc`c0377900
    fffff97f`ff008d8c : fffffadc`c0377a38 00000000`00000000
    00000000`01bc8000 00000000`00000000 : win32k!DrvInitConsole+0xd5
    fffffadc`c0377970
     fffff97f`ff00bb28 : 00000000`01bc8000 00000000`00000000
    00000000`00000003 00000000`00000000 : win32k!InitVideo+0xb
    fffffadc`c03779e0
     fffff97f`ff00b646 : 00000000`00000060 fffffadc`c0377cf0
    00000000`00000003 00000000`0000005c : win32k!UserInitialize+0x63c
    fffffadc`c0377c20
     fffff800`00c2e3fd : fffffadc`000001e0 00000000`00000001
    fffffadc`e0556750 00000000`00000020 : win32k!NtUserInitialize+0x15f
    fffffadc`c0377c70
     000007ff`7c7de86a : 000007ff`7c7deaa9 00000000`001657f0
    00000000`001657f0 00000000`00000003 : nt!KiSystemServiceCopyEnd+0x3
    00000000`0015fbc8
     000007ff`7c7deaa9 : 00000000`001657f0 00000000`001657f0
    00000000`00000003 00000000`00000000 : winsrv!NtUserInitialize+0xa
    00000000`0015fbd0
     000007ff`7c5b3eb8 : 00000000`00000000 00000000`00000001
    00000000`001657f0 00000000`00000000 :
    winsrv!UserServerDllInitialization+0x229
    00000000`0015fc50
    00000000`00000000 : 00000000`00000001 00000000`001657f0
    00000000`00000000 00000000`00100000 :
    CSRSRV!CsrUnhandledExceptionFilter+0x368

    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    VIDEOPRT!pVideoPortInitializeInt10+4e
    fffffadc`be4a813e 4c8bcb          mov     r9,rbx

    SYMBOL_STACK_INDEX:  7

    SYMBOL_NAME:  VIDEOPRT!pVideoPortInitializeInt10+4e

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: VIDEOPRT

    IMAGE_NAME:  VIDEOPRT.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP:  45d69799

    FAILURE_BUCKET_ID:  X64_0x50_VIDEOPRT!pVideoPortInitializeInt10+4e

    BUCKET_ID:  X64_0x50_VIDEOPRT!pVideoPortInitializeInt10+4e

    Followup: MachineOwner
    ---------

    8: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffffadcc100202a, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80000ce2cae, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000000, (reserved)

    Debugging Details:
    ------------------

    READ_ADDRESS:  fffffadcc100202a

    FAULTING_IP:
    nt!MmMapIoSpace+489
    fffff800`00ce2cae 668b4e1a        mov     cx,word ptr [rsi+1Ah]

    MM_INTERNAL_CODE:  0

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  csrss.exe

    CURRENT_IRQL:  2

    TRAP_FRAME:  fffffadcc0376900 -- (.trap 0xfffffadcc0376900)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff6fd6e5ec0f0 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffffadcc070b101 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80000ce2cae rsp=fffffadcc0376a90 rbp=0000000000000000
     r8=000000fffffff000  r9=0000000000000002 r10=0000000000000eff
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    nt!MmMapIoSpace+0x489:
    fffff800`00ce2cae 668b4e1a        mov     cx,word ptr [rsi+1Ah] ds:b180:001a=????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff80000cd673e to fffff80000c26db0

    STACK_TEXT:
    fffffadc`c0376148
     fffff800`00cd673e : 00000000`00000008 fffffadc`c0376900
    fffffadc`c100202a fffff800`00c5669e : nt!DbgBreakPointWithStatus
    fffffadc`c0376150
     fffff800`00cd7d0e : fffff800`00000003 00000000`00000050
    fffffadc`c100202a 00000000`00000000 : nt!KiBugCheckDebugBreak+0x1e
    fffffadc`c03761b0
     fffff800`00c2ea54 : fffffadc`c0376830 fffffadc`00000004
    fffffadc`c0376c64 fffffadc`c0376c10 : nt!KeBugCheck2+0x640
    fffffadc`c03767f0
     fffff800`00ca58f2 : 00000000`00000050 fffffadc`c100202a
    00000000`00000000 fffffadc`c0376900 : nt!KeBugCheckEx+0x104
    fffffadc`c0376830
     fffff800`00c2d519 : 00000000`00000011 fffff800`00e9534b
    fffffadc`c0376900 fffffadc`c03769d0 : nt!MmAccessFault+0xa1f
    fffffadc`c0376900
     fffff800`00ce2cae : 00000000`0000087b 00000000`00000000
    fffffadc`c1000000 00000000`00000000 : nt!KiPageFault+0x119
    fffffadc`c0376a90
     fffffadc`be4a813e : fffffadc`00000001 00000000`00100000
    fffffadc`00000000 fffffa80`00677000 : nt!MmMapIoSpace+0x489
    fffffadc`c0376b60
     fffffadc`be4b28b3 : 00000000`00000000 00000000`00000000
    00000000`00000000 00000000`00000000 :
    VIDEOPRT!pVideoPortInitializeInt10+0x4e
    fffffadc`c0376ba0
    fffff800`00e837c9 : fffffadc`e0511070 fffffadc`e03e69d0
    fffffadc`e0511070 fffff800`00e83170 : VIDEOPRT!pVideoPortDispatch+0xca3
    fffffadc`c0376cc0
     fffff800`00e81164 : fffffadc`e0511070 fffffadc`e0511020
    fffffadc`c0376ff0 00000000`00000000 : nt!IopParseDevice+0x1088
    fffffadc`c0376e70
     fffff800`00e85887 : 00000000`00000000 fffffadc`c0376fe0
    00000000`00000240 00000000`00000000 : nt!ObpLookupObjectName+0x931
    fffffadc`c0376f80
     fffff800`00e92e4d : 00000000`00000001 fffffadc`c03774e0
    00000000`00000001 fffff800`00c241ce : nt!ObOpenObjectByName+0x180
    fffffadc`c0377170
     fffff800`00e99ef7 : fffffa80`0066e4d0 fffff800`00c3c37e
    fffffa80`0066e4a0 00000000`00000500 : nt!IopCreateFile+0x630
    fffffadc`c0377300
     fffff800`00e958f9 : 00000000`00000000 fffffa80`00001c80
    fffffadc`dff1ac20 fffffadc`e0556750 : nt!IoCreateFile+0x12f
    fffffadc`c03773e0
     fffff800`00c2e3fd : fffffadc`e0556750 fffffadc`c03774e0
    00000000`00000000 00000000`00000000 : nt!NtOpenFile+0x49
    fffffadc`c0377460
     fffff800`00c2e8c0 : fffff800`00e7ec67 00000000`00000000
    000007ff`7c5c9620 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
    fffffadc`c0377668
     fffff800`00e7ec67 : 00000000`00000000 000007ff`7c5c9620
    00000000`00000000 00000000`00000001 : nt!KiServiceLinkage
    fffffadc`c0377670
     fffff97f`ff008587 : 00000000`00000000 00000000`00000000
    00000000`00000001 00000000`00000000 : nt!IoGetDeviceObjectPointer+0x57
    fffffadc`c0377700
     fffff97f`ff00334d : 00000000`00000001 00000000`00000000
    00000000`00000003 00000000`00000001 :
    win32k!DrvUpdateGraphicsDeviceList+0x4ba
    fffffadc`c0377900
    fffff97f`ff008d8c : fffffadc`c0377a38 00000000`00000000
    00000000`01bc8000 00000000`00000000 : win32k!DrvInitConsole+0xd5
    fffffadc`c0377970
     fffff97f`ff00bb28 : 00000000`01bc8000 00000000`00000000
    00000000`00000003 00000000`00000000 : win32k!InitVideo+0xb
    fffffadc`c03779e0
     fffff97f`ff00b646 : 00000000`00000060 fffffadc`c0377cf0
    00000000`00000003 00000000`0000005c : win32k!UserInitialize+0x63c
    fffffadc`c0377c20
     fffff800`00c2e3fd : fffffadc`000001e0 00000000`00000001
    fffffadc`e0556750 00000000`00000020 : win32k!NtUserInitialize+0x15f
    fffffadc`c0377c70
     000007ff`7c7de86a : 000007ff`7c7deaa9 00000000`001657f0
    00000000`001657f0 00000000`00000003 : nt!KiSystemServiceCopyEnd+0x3
    00000000`0015fbc8
     000007ff`7c7deaa9 : 00000000`001657f0 00000000`001657f0
    00000000`00000003 00000000`00000000 : winsrv!NtUserInitialize+0xa
    00000000`0015fbd0
     000007ff`7c5b3eb8 : 00000000`00000000 00000000`00000001
    00000000`001657f0 00000000`00000000 :
    winsrv!UserServerDllInitialization+0x229
    00000000`0015fc50
    00000000`00000000 : 00000000`00000001 00000000`001657f0
    00000000`00000000 00000000`00100000 :
    CSRSRV!CsrUnhandledExceptionFilter+0x368

    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    VIDEOPRT!pVideoPortInitializeInt10+4e
    fffffadc`be4a813e 4c8bcb          mov     r9,rbx

    SYMBOL_STACK_INDEX:  7

    SYMBOL_NAME:  VIDEOPRT!pVideoPortInitializeInt10+4e

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: VIDEOPRT

    IMAGE_NAME:  VIDEOPRT.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP:  45d69799

    FAILURE_BUCKET_ID:  X64_0x50_VIDEOPRT!pVideoPortInitializeInt10+4e

    BUCKET_ID:  X64_0x50_VIDEOPRT!pVideoPortInitializeInt10+4e

    Followup: MachineOwner
    ---------

    8: kd> lm
    start             end                 module name
    00000000`4a680000 00000000`4a686000   csrss      (deferred)
    00000000`77c20000 00000000`77d2c000   USER32     (deferred)
    00000000`77d40000
     00000000`77eb3000   KERNEL32   (pdb symbols)
    c:\symbols\kernel32.pdb\8600FA0E2CE1463C8CDD0CBC26A8D84C2\kernel32.pdb
    00000000`77ec0000
     00000000`77ff9000   ntdll      (pdb symbols)
    c:\symbols\ntdll.pdb\95DDB8CA2A5D4C0EBF9924339F14E4862\ntdll.pdb
    000007ff`7c5b0000 000007ff`7c5cd000   CSRSRV     (export symbols)       CSRSRV.dll
    000007ff`7c7b0000 000007ff`7c7c6000   basesrv    (deferred)
    000007ff`7c7d0000
     000007ff`7c851000   winsrv     (pdb symbols)
    c:\symbols\winsrv.pdb\3579A339B79745F482A2CD61E9A594CF2\winsrv.pdb
    000007ff`7fc90000 000007ff`7fd2b000   GDI32      (deferred)
    fffff800`00c00000
     fffff800`01090000   nt         (pdb symbols)
    c:\symbols\ntkrnlmp.pdb\03185083233249D9BB747EA777B80C982\ntkrnlmp.pdb
    fffff800`01090000 fffff800`010ee000   hal        (deferred)
    fffff97f`fd000000 fffff97f`fd028000   dxg        (deferred)
    fffff97f`ff000000
     fffff97f`ff45f000   win32k     (pdb symbols)
    c:\symbols\win32k.pdb\3E94FFC5B7B84E3999B1CB92A9B3B2372\win32k.pdb
    fffffadc`bd8b9000 fffffadc`bd986000   mrxsmb     (deferred)
    fffffadc`bd986000 fffffadc`bd9d7000   rdbss      (deferred)
    fffffadc`bd9d7000 fffffadc`bda24000   afd        (deferred)
    fffffadc`bda24000 fffffadc`bda7e000   netbt      (deferred)
    fffffadc`bda7e000 fffffadc`bdabc000   ipnat      (deferred)
    fffffadc`bdabc000 fffffadc`bdbb1000   tcpip      (deferred)
    fffffadc`bdbb1000 fffffadc`bdbdc000   ipsec      (deferred)
    fffffadc`bdbdc000 fffffadc`bdbf0000   Npfs       (deferred)
    fffffadc`bdd16000 fffffadc`bdd56000   portcls    (deferred)
    fffffadc`bdd56000 fffffadc`bdd80000   nvhda64    (deferred)
    fffffadc`bddc6000 fffffadc`bddda000   NDProxy    (deferred)
    fffffadc`be260000 fffffadc`be27b000   update     (deferred)
    fffffadc`be27b000 fffffadc`be291000   termdd     (deferred)
    fffffadc`be291000 fffffadc`be2e8000   rdpdr      (deferred)
    fffffadc`be2e8000 fffffadc`be2fe000   msgpc      (deferred)
    fffffadc`be2fe000 fffffadc`be31e000   psched     (deferred)
    fffffadc`be31e000 fffffadc`be341000   raspptp    (deferred)
    fffffadc`be341000 fffffadc`be355000   raspppoe   (deferred)
    fffffadc`be355000 fffffadc`be381000   ndiswan    (deferred)
    fffffadc`be381000 fffffadc`be3a7000   rasl2tp    (deferred)
    fffffadc`be3a7000 fffffadc`be3f0000   ks         (deferred)
    fffffadc`be3f0000 fffffadc`be40d000   i8042prt   (deferred)
    fffffadc`be40d000 fffffadc`be45e000   e1r51x64   (deferred)
    fffffadc`be45e000 fffffadc`be49c000   HDAudBus   (deferred)
    fffffadc`be49c000
     fffffadc`be4bf000   VIDEOPRT   (pdb symbols)
    c:\symbols\videoprt.pdb\A735567342A448C683C9DB1C8BEB2BEE1\videoprt.pdb
    fffffadc`be4bf000 fffffadc`befd4e00   nv4_mini   (deferred)
    fffffadc`bf7d5000 fffffadc`bf7e3000   kbdclass   (deferred)
    fffffadc`bf7e5000 fffffadc`bf7ee000   wmiacpi    (deferred)
    fffffadc`bf7f5000 fffffadc`bf803000   vga        (deferred)
    fffffadc`bf805000 fffffadc`bf80f000   RDPCDD     (deferred)
    fffffadc`bf815000 fffffadc`bf822000   mouclass   (deferred)
    fffffadc`bf855000 fffffadc`bf863000   dump_STORAHCI   (deferred)
    fffffadc`bfe76000 fffffadc`bfeaa000   Mup        (deferred)
    fffffadc`bfeaa000 fffffadc`bff10000   NDIS       (deferred)
    fffffadc`bff10000 fffffadc`bff44000   KSecDD     (deferred)
    fffffadc`bff44000 fffffadc`bff85000   Fastfat    (deferred)
    fffffadc`bff85000 fffffadc`bffa8000   sr         (deferred)
    fffffadc`bffa8000 fffffadc`bffe6000   fltMgr     (deferred)
    fffffadc`bffe6000 fffffadc`c0003000   CLASSPNP   (deferred)
    fffffadc`c0003000 fffffadc`c0018000   disk       (deferred)
    fffffadc`c0018000 fffffadc`c007b000   storport   (deferred)
    fffffadc`c007b000 fffffadc`c00c6000   volsnap    (deferred)
    fffffadc`c00c6000 fffffadc`c010d000   dmio       (deferred)
    fffffadc`c010d000 fffffadc`c014d000   ftdisk     (deferred)
    fffffadc`c014d000 fffffadc`c0163000   MountMgr   (deferred)
    fffffadc`c0163000 fffffadc`c0184000   pci        (deferred)
    fffffadc`c0184000 fffffadc`c01f2000   ACPI       (deferred)
    fffffadc`c02f3000 fffffadc`c0305000   intelppm   (deferred)
    fffffadc`c0306000 fffffadc`c0318000   wanarp     (deferred)
    fffffadc`c0319000 fffffadc`c032b000   netbios    (deferred)
    fffffadc`c032c000 fffffadc`c033e000   Fips       (deferred)
    fffffadc`c05fb000 fffffadc`c0605000   kdcom      (deferred)
    fffffadc`c060b000 fffffadc`c0614000   BOOTVID    (deferred)
    fffffadc`c061b000 fffffadc`c0624000   WMILIB     (deferred)
    fffffadc`c062b000 fffffadc`c0634000   isapnp     (deferred)
    fffffadc`c063b000 fffffadc`c064b000   PartMgr    (deferred)
    fffffadc`c064b000 fffffadc`c0659000   storahci   (deferred)
    fffffadc`c065b000 fffffadc`c0666000   crcdisk    (deferred)
    fffffadc`c073b000 fffffadc`c0745000   Fs_Rec     (deferred)
    fffffadc`c074b000 fffffadc`c0758000   Msfs       (deferred)
    fffffadc`c079b000 fffffadc`c07a5000   rasacd     (deferred)
    fffffadc`c07ab000 fffffadc`c07b6000   raspti     (deferred)
    fffffadc`c07bb000 fffffadc`c07c5000   mnmdd      (deferred)
    fffffadc`c07cb000 fffffadc`c07d7000   dump_diskdump   (deferred)
    fffffadc`c07eb000 fffffadc`c07f8000   ptilink    (deferred)
    fffffadc`c07fb000 fffffadc`c080a000   TDI        (deferred)
    fffffadc`c080b000 fffffadc`c0814000   watchdog   (deferred)
    fffffadc`c081b000 fffffadc`c0827000   Dxapi      (deferred)
    fffffadc`c084b000
     fffffadc`c0858000   mssmbios   (pdb symbols)
    c:\symbols\mssmbios.pdb\ECAD413A7E6C4AFEB52606D7E237C5411\mssmbios.pdb
    fffffadc`c085b000 fffffadc`c0865000   ndistapi   (deferred)
    fffffadc`c0873000 fffffadc`c087b000   audstub    (deferred)
    fffffadc`c087b000 fffffadc`c0883000   Null       (deferred)
    fffffadc`c09fb000 fffffadc`c0a02000   dmload     (deferred)
    fffffadc`c0b6e000 fffffadc`c0b73e80   ksthunk    (deferred)
    fffffadc`c0c32000 fffffadc`c0c39000   Beep       (deferred)
    fffffadc`c0db3000 fffffadc`c0db4400   swenum     (deferred)

    Unloaded modules:
    fffffadc`bd8a2000 fffffadc`bd8b9000   imapi.sys
    fffffadc`bd9c1000 fffffadc`bd9d7000   redbook.sys
    fffffadc`bd9b4000 fffffadc`bd9d7000   serial.sys
    fffffadc`bdc3b000 fffffadc`bdc56000   cdrom.sys
    fffffadc`c075b000 fffffadc`c0764000   Sfloppy.SYS
    fffffadc`c082b000 fffffadc`c0837000   Flpydisk.SYS
    fffffadc`c071b000 fffffadc`c0729000   Fdc.SYS

#2333

Andalu

The USB3.0 drivers modded work correctly on asrock B250M Pro4 with i5 6600 skylake and XP32 (including the USB 3.0 type-C port).
But I can obtain only a 'multiprocessor mps' system, so no ACPI and no multi-core. All the alternative options chosen during XP installation (by pressing F5 or F7 keys) are without ACPI mode or give me BSOD A5. In the updated bios, all the related options seem to be properly configured.
Can I try something else?

#2334 | infuscomus | ⇗ @Andalu have you tried the patched ACPI driver? ¶ Windows XP SP3 32bit and modern PC parts (149)

#2335

diderius6

I just renamed videoport.sys to videoOriport.sys.
But now it seems, that something is missing
Dietmar

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Opened \\.\com1
    Waiting to reconnect...
    Connected to Windows Server 2003 3790 x64 target at (Sun Sep  8 11:03:40.531 2019 (UTC + 2:00)), ptr64 TRUE
    Kernel Debugger connection established.
    WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
    Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
    *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
    Executable search path is: C:\localsymbols
    Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64
    Built by: 3790.srv03_sp2_rtm.070216-1710
    Machine Name:
    Kernel base = 0xfffff800`00c00000 PsLoadedModuleList = 0xfffff800`00dd5100
    System Uptime: not available
    AhciHwFindAdapter finishing
    AhciHwFindAdapter finishing
    KDTARGET: Refreshing KD connection

    *** Fatal System Error: 0xc000021a
                                                 (0xFFFFFA80008CE2E0,0x00000000C0000034,0x0000000000000000,0x0000000000000000)

    STOP: c000021a {Fatal System Error}
    The Session Manager Initialization system process terminated unexpectedly with a status of 0xc0000034 (0x00000000 0x00000000).
    The system has been shut down.
    Break instruction exception - code 80000003 (first chance)

    A fatal system error has occurred.
    Debugger entered on first try; Bugcheck callbacks have not been invoked.

    A fatal system error has occurred.

    Connected to Windows Server 2003 3790 x64 target at (Sun Sep  8 11:04:37.093 2019 (UTC + 2:00)), ptr64 TRUE
    Loading Kernel Symbols
    ...............................................................
    .....
    Loading User Symbols

    Loading unloaded module list
    .........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck C000021A, {fffffa80008ce2e0, c0000034, 0, 0}

    unable to get nt!KiCurrentEtwBufferOffset
    unable to get nt!KiCurrentEtwBufferBase
    Probably caused by : ntkrnlmp.exe ( nt!NtSetSystemPowerState+826 )

    Followup: MachineOwner
    ---------

    nt!DbgBreakPointWithStatus:
    fffff800`00c26db0 cc              int     3
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    WINLOGON_FATAL_ERROR (c000021a)
    The Winlogon process terminated unexpectedly.
    Arguments:
    Arg1: fffffa80008ce2e0, String that identifies the problem.
    Arg2: 00000000c0000034, Error Code.
    Arg3: 0000000000000000
    Arg4: 0000000000000000

    Debugging Details:
    ------------------

    unable to get nt!KiCurrentEtwBufferOffset
    unable to get nt!KiCurrentEtwBufferBase

    ERROR_CODE:
     (NTSTATUS) 0xc000021a - {Daten wurden nicht akzeptiert}  Der TDI-Client
     konnte die empfangenen Daten nicht verarbeiten.

    EXCEPTION_CODE:
    (NTSTATUS) 0xc000021a - {Daten wurden nicht akzeptiert}  Der TDI-Client
    konnte die empfangenen Daten nicht verarbeiten.

    EXCEPTION_PARAMETER1:  fffffa80008ce2e0

    EXCEPTION_PARAMETER2:  00000000c0000034

    EXCEPTION_PARAMETER3:  0000000000000000

    EXCEPTION_PARAMETER4: 0

    ADDITIONAL_DEBUG_TEXT:  Session Manager Initialization

    BUGCHECK_STR:  0xc000021a_smss.exe_c0000034

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    LAST_CONTROL_TRANSFER:  from fffff80000cd673e to fffff80000c26db0

    STACK_TEXT:
    fffffadc`c0ae8148
     fffff800`00cd673e : 00000000`00000002 00000000`00000000
    00000000`00000001 fffff800`00c5669e : nt!DbgBreakPointWithStatus
    fffffadc`c0ae8150
     fffff800`00cd7d0e : fffffadc`00000003 00000000`ffff0025
    00000000`ffffffff 00000000`00000000 : nt!KiBugCheckDebugBreak+0x1e
    fffffadc`c0ae81b0
     fffff800`00c2ea54 : fffffadc`e0453408 fffff800`00fcac4a
    00000001`00060000 fffffadc`e06c7080 : nt!KeBugCheck2+0x640
    fffffadc`c0ae87f0
     fffff800`00fd5a8b : 00000000`0000004c 00000000`c000021a
    fffffadc`c0bf2608 fffffadc`e051f640 : nt!KeBugCheckEx+0x104
    fffffadc`c0ae8830
     fffff800`00fd96b1 : ffffffff`8000005c ffffffff`8000005c
    00000000`00000000 00000000`00000002 : nt!PopGracefulShutdown+0x32b
    fffffadc`c0ae88b0
     fffff800`00c2e3fd : fffffadc`00000004 fffff800`00000004
    fffffadc`e033e700 fffffadc`e20e77a0 : nt!NtSetSystemPowerState+0x826
    fffffadc`c0ae8a60
     fffff800`00c2e8c0 : fffff800`00f6c105 fffffadc`e20e77a0
    00000000`00000004 fffffadc`e20e7701 : nt!KiSystemServiceCopyEnd+0x3
    fffffadc`c0ae8bf8
     fffff800`00f6c105 : fffffadc`e20e77a0 00000000`00000004
    fffffadc`e20e7701 00000000`e0000004 : nt!KiServiceLinkage
    fffffadc`c0ae8c00
     fffff800`00f6be6e : 00000000`00000004 fffff800`00d19a90
    fffffadc`e20e77a0 00000000`00000002 : nt!PopIssueActionRequest+0x85
    fffffadc`c0ae8c60
     fffff800`00d19b48 : fffffadc`e0632020 fffff800`00fc2d20
    ffffffff`ff676980 00000000`00000002 : nt!PopPolicyWorkerAction+0x6e
    fffffadc`c0ae8ca0
     fffff800`00c3768a : 00000000`00000000 d14de0c1`83d94500
    fffff800`00dd2720 fffff800`00dce9d8 : nt!PopPolicyWorkerThread+0xb9
    fffffadc`c0ae8d00
     fffff800`00e4b972 : fffffadc`e20e77a0 00000000`00000080
    fffffadc`e20e77a0 fffffadc`c0683680 : nt!ExpWorkerThread+0x13b
    fffffadc`c0ae8d70
     fffff800`00c202d6 : fffffadc`c067b180 fffffadc`e20e77a0
    fffffadc`c0683680 00000000`00000000 : nt!PspSystemThreadStartup+0x3e
    fffffadc`c0ae8dd0
     00000000`00000000 : 00000000`00000000 00000000`00000000
    00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!NtSetSystemPowerState+826
    fffff800`00fd96b1 cc              int     3

    SYMBOL_STACK_INDEX:  5

    SYMBOL_NAME:  nt!NtSetSystemPowerState+826

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  45d69ab4

    FAILURE_BUCKET_ID:  X64_0xc000021a_smss.exe_c0000034_nt!NtSetSystemPowerState+826

    BUCKET_ID:  X64_0xc000021a_smss.exe_c0000034_nt!NtSetSystemPowerState+826

    Followup: MachineOwner
    ---------

    2: kd> lm
    start             end                 module name
    fffff800`00c00000
     fffff800`01090000   nt         (pdb symbols)
    c:\symbols\ntkrnlmp.pdb\03185083233249D9BB747EA777B80C982\ntkrnlmp.pdb
    fffff800`01090000 fffff800`010ee000   hal        (deferred)
    fffffadc`b9b44000 fffffadc`b9c11000   mrxsmb     (deferred)
    fffffadc`b9c11000 fffffadc`b9c62000   rdbss      (deferred)
    fffffadc`b9c62000 fffffadc`b9caf000   afd        (deferred)
    fffffadc`b9caf000 fffffadc`b9d09000   netbt      (deferred)
    fffffadc`b9d09000 fffffadc`b9d47000   ipnat      (deferred)
    fffffadc`b9d47000 fffffadc`b9e3c000   tcpip      (deferred)
    fffffadc`b9e3c000 fffffadc`b9e67000   ipsec      (deferred)
    fffffadc`b9e67000 fffffadc`b9e7b000   Npfs       (deferred)
    fffffadc`bd6ef000 fffffadc`bd703000   NDProxy    (deferred)
    fffffadc`bd703000 fffffadc`bd743000   portcls    (deferred)
    fffffadc`bd743000 fffffadc`bd76d000   nvhda64    (deferred)
    fffffadc`be283000 fffffadc`be29e000   update     (deferred)
    fffffadc`be29e000 fffffadc`be2b4000   termdd     (deferred)
    fffffadc`be2b4000 fffffadc`be30b000   rdpdr      (deferred)
    fffffadc`be30b000 fffffadc`be321000   msgpc      (deferred)
    fffffadc`be321000 fffffadc`be341000   psched     (deferred)
    fffffadc`be341000 fffffadc`be364000   raspptp    (deferred)
    fffffadc`be364000 fffffadc`be378000   raspppoe   (deferred)
    fffffadc`be378000 fffffadc`be3a4000   ndiswan    (deferred)
    fffffadc`be3a4000 fffffadc`be3ca000   rasl2tp    (deferred)
    fffffadc`be3ca000 fffffadc`be413000   ks         (deferred)
    fffffadc`be413000 fffffadc`be430000   i8042prt   (deferred)
    fffffadc`be430000 fffffadc`be481000   e1r51x64   (deferred)
    fffffadc`be481000 fffffadc`be4bf000   HDAudBus   (deferred)
    fffffadc`bf7d5000 fffffadc`bf7df000   rasacd     (deferred)
    fffffadc`bf805000
     fffffadc`bf812000   mssmbios   (pdb symbols)
    c:\symbols\mssmbios.pdb\ECAD413A7E6C4AFEB52606D7E237C5411\mssmbios.pdb
    fffffadc`bf845000 fffffadc`bf84e000   wmiacpi    (deferred)
    fffffadc`bfe76000 fffffadc`bfeaa000   Mup        (deferred)
    fffffadc`bfeaa000 fffffadc`bff10000   NDIS       (deferred)
    fffffadc`bff10000 fffffadc`bff44000   KSecDD     (deferred)
    fffffadc`bff44000 fffffadc`bff85000   Fastfat    (deferred)
    fffffadc`bff85000 fffffadc`bffa8000   sr         (deferred)
    fffffadc`bffa8000 fffffadc`bffe6000   fltMgr     (deferred)
    fffffadc`bffe6000 fffffadc`c0003000   CLASSPNP   (deferred)
    fffffadc`c0003000 fffffadc`c0018000   disk       (deferred)
    fffffadc`c0018000 fffffadc`c007b000   storport   (deferred)
    fffffadc`c007b000 fffffadc`c00c6000   volsnap    (deferred)
    fffffadc`c00c6000 fffffadc`c010d000   dmio       (deferred)
    fffffadc`c010d000 fffffadc`c014d000   ftdisk     (deferred)
    fffffadc`c014d000 fffffadc`c0163000   MountMgr   (deferred)
    fffffadc`c0163000 fffffadc`c0184000   pci        (deferred)
    fffffadc`c0184000 fffffadc`c01f2000   ACPI       (deferred)
    fffffadc`c02f3000 fffffadc`c0305000   intelppm   (deferred)
    fffffadc`c0306000 fffffadc`c0318000   wanarp     (deferred)
    fffffadc`c0319000 fffffadc`c032b000   netbios    (deferred)
    fffffadc`c032c000 fffffadc`c033e000   Fips       (deferred)
    fffffadc`c05fb000 fffffadc`c0605000   kdcom      (deferred)
    fffffadc`c060b000 fffffadc`c0614000   BOOTVID    (deferred)
    fffffadc`c061b000 fffffadc`c0624000   WMILIB     (deferred)
    fffffadc`c062b000 fffffadc`c0634000   isapnp     (deferred)
    fffffadc`c063b000 fffffadc`c064b000   PartMgr    (deferred)
    fffffadc`c064b000 fffffadc`c0659000   storahci   (deferred)
    fffffadc`c065b000 fffffadc`c0666000   crcdisk    (deferred)
    fffffadc`c074b000 fffffadc`c0755000   ndistapi   (deferred)
    fffffadc`c076b000 fffffadc`c077a000   TDI        (deferred)
    fffffadc`c078b000 fffffadc`c0799000   kbdclass   (deferred)
    fffffadc`c07bb000 fffffadc`c07c6000   raspti     (deferred)
    fffffadc`c07db000 fffffadc`c07e8000   ptilink    (deferred)
    fffffadc`c082b000 fffffadc`c0838000   Msfs       (deferred)
    fffffadc`c083b000 fffffadc`c0845000   Fs_Rec     (deferred)
    fffffadc`c084b000 fffffadc`c0858000   mouclass   (deferred)
    fffffadc`c087b000 fffffadc`c0883000   audstub    (deferred)
    fffffadc`c0883000 fffffadc`c088b000   Null       (deferred)
    fffffadc`c09fb000 fffffadc`c0a02000   dmload     (deferred)
    fffffadc`c0b6e000 fffffadc`c0b73e80   ksthunk    (deferred)
    fffffadc`c0bd7000 fffffadc`c0bde000   Beep       (deferred)
    fffffadc`c0db3000 fffffadc`c0db4400   swenum     (deferred)

    Unloaded modules:
    fffffadc`c073b000 fffffadc`c0747000   dump_storport.sys
    fffffadc`bf835000 fffffadc`bf843000   dump_STORAHCI.sys
    fffffadc`b9b2d000 fffffadc`b9b44000   imapi.sys
    fffffadc`b9c4c000 fffffadc`b9c62000   redbook.sys
    fffffadc`b9c3f000 fffffadc`b9c62000   serial.sys
    fffffadc`b9f00000 fffffadc`b9f1b000   cdrom.sys
    fffffadc`c071b000 fffffadc`c0724000   Sfloppy.SYS
    fffffadc`bf855000 fffffadc`bf861000   Flpydisk.SYS
    fffffadc`bf7f5000 fffffadc`bf803000   Fdc.SYS

#2336 | Andalu | ⇗ @infuscomus Sure, I attached the HDD on another machine to copy ACPI.sys in the system32\drivers folder.

#2337

diderius6

Now I changed ntoskrnl.exe, hal.dll, videoport.sys against their DEBUG version.
So, this is the best output, what windbg gives you.
The problem is at the same part in videoport.sys
Dietmar
PS: I have no idea how to hack this. May be it can be done )!

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Opened \\.\com1
    Waiting to reconnect...
    Connected to Windows Server 2003 3790 x64 target at (Sun Sep  8 11:24:22.968 2019 (UTC + 2:00)), ptr64 TRUE
    Kernel Debugger connection established.
    WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
    Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
    *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
    Executable search path is: C:\localsymbols
    Windows Server 2003 Kernel Version 3790 MP (1 procs) Checked x64
    Built by: 3790.srv03_sp2_rtm.070216-1710
    Machine Name:
    Kernel base = 0xfffff800`00c00000 PsLoadedModuleList = 0xfffff800`00fd1fd0
    System Uptime: not available
    AhciHwFindAdapter finishing
    AhciHwFindAdapter finishing
    KDTARGET: Refreshing KD connection
    VideoPort: This is an ACPI Machine !

    *** Assertion failed: (Pfn1->u3.e2.ReferenceCount != 0) || ((Pfn1->u3.e1.Rom == 1) && (CacheType == MmCached))
    ***   Source File: d:\nt\base\ntos\mm\iosup.c, line 9066

    Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i
    i

    *** Assertion failed: (Pfn1->u3.e2.ReferenceCount != 0) || ((Pfn1->u3.e1.Rom == 1) && (CacheType == MmCached))
    ***   Source File: d:\nt\base\ntos\mm\iosup.c, line 9066

    Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i
    i

    *** Assertion failed: (Pfn1->u3.e2.ReferenceCount != 0) || ((Pfn1->u3.e1.Rom == 1) && (CacheType == MmCached))
    ***   Source File: d:\nt\base\ntos\mm\iosup.c, line 9066

    Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i
    i

    *** Assertion failed: (Pfn1->u3.e2.ReferenceCount != 0) || ((Pfn1->u3.e1.Rom == 1) && (CacheType == MmCached))
    ***   Source File: d:\nt\base\ntos\mm\iosup.c, line 9066

    Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i
    i
    HAL: RTC interrupt flag is not cleared by first read.

    *** Assertion failed: (Pfn1->u3.e2.ReferenceCount != 0) || ((Pfn1->u3.e1.Rom == 1) && (CacheType == MmCached))
    ***   Source File: d:\nt\base\ntos\mm\iosup.c, line 9066

    Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i
    i
    RTC Status Register C = 0xc0

    *** Assertion failed: (Pfn1->u3.e2.ReferenceCount != 0) || ((Pfn1->u3.e1.Rom == 1) && (CacheType == MmCached))
    ***   Source File: d:\nt\base\ntos\mm\iosup.c, line 9066

    Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i
    i

    *** Assertion failed: (Pfn1->u3.e2.ReferenceCount != 0) || ((Pfn1->u3.e1.Rom == 1) && (CacheType == MmCached))
    ***   Source File: d:\nt\base\ntos\mm\iosup.c, line 9066

    Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i
    i

    *** Assertion failed: (Pfn1->u3.e2.ReferenceCount != 0) || ((Pfn1->u3.e1.Rom == 1) && (CacheType == MmCached))
    ***   Source File: d:\nt\base\ntos\mm\iosup.c, line 9066

    Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i
    i
    HAL: RTC interrupt flag is not cleared by first read.

    *** Assertion failed: (Pfn1->u3.e2.ReferenceCount != 0) || ((Pfn1->u3.e1.Rom == 1) && (CacheType == MmCached))
    ***   Source File: d:\nt\base\ntos\mm\iosup.c, line 9066

    Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i
    i
    RTC Status Register C = 0xd0

    *** Assertion failed: (Pfn1->u3.e2.ReferenceCount != 0) || ((Pfn1->u3.e1.Rom == 1) && (CacheType == MmCached))
    ***   Source File: d:\nt\base\ntos\mm\iosup.c, line 9066

    Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i
    i

    *** Assertion failed: (Pfn1->u3.e2.ReferenceCount != 0) || ((Pfn1->u3.e1.Rom == 1) && (CacheType == MmCached))
    ***   Source File: d:\nt\base\ntos\mm\iosup.c, line 9066

    Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i
    i

    *** Assertion failed: (Pfn1->u3.e2.ReferenceCount != 0) || ((Pfn1->u3.e1.Rom == 1) && (CacheType == MmCached))
    ***   Source File: d:\nt\base\ntos\mm\iosup.c, line 9066

    Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i
    i
    HAL: RTC interrupt flag is not cleared by first read.

    *** Assertion failed: (Pfn1->u3.e2.ReferenceCount != 0) || ((Pfn1->u3.e1.Rom == 1) && (CacheType == MmCached))
    ***   Source File: d:\nt\base\ntos\mm\iosup.c, line 9066

    Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i
    i
    RTC Status Register C = 0xc0

    *** Fatal System Error: 0x00000050
                                                 (0xFFFFFADCC1002028,0x0000000000000000,0xFFFFF80000C90624,0x0000000000000000)

    Break instruction exception - code 80000003 (first chance)

    A fatal system error has occurred.
    Debugger entered on first try; Bugcheck callbacks have not been invoked.

    A fatal system error has occurred.

    Connected to Windows Server 2003 3790 x64 target at (Sun Sep  8 11:26:03.078 2019 (UTC + 2:00)), ptr64 TRUE
    Loading Kernel Symbols
    ...............................................................
    ................
    Loading User Symbols
    ........
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {fffffadcc1002028, 0, fffff80000c90624, 0}

    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for CSRSRV.dll -
    Probably caused by : VIDEOPRT.SYS ( VIDEOPRT!pVideoPortInitializeInt10+52 )

    Followup: MachineOwner
    ---------

    nt!RtlpBreakWithStatusInstruction:
    fffff800`00da02e0 cc              int     3
    8: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffffadcc1002028, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80000c90624, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000000, (reserved)

    Debugging Details:
    ------------------

    READ_ADDRESS:  fffffadcc1002028

    FAULTING_IP:
    nt!MmMapIoSpace+564
    fffff800`00c90624 6641837d1800    cmp     word ptr [r13+18h],0

    MM_INTERNAL_CODE:  0

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  CSRSS.EXE

    CURRENT_IRQL:  2

    TRAP_FRAME:  fffffadcc03768f0 -- (.trap 0xfffffadcc03768f0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffadcc0370007 rbx=0000000000000000 rcx=fffff8000109ec2c
    rdx=0000000000000006 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80000c90624 rsp=fffffadcc0376a80 rbp=0000000000000000
     r8=0000000000000007  r9=0000000081c031b5 r10=fffff80000f5e948
    r11=0000000000000008 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    nt!MmMapIoSpace+0x564:
    fffff800`00c90624 6641837d1800    cmp     word ptr [r13+18h],0 ds:000f:0018=????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff80000c5d707 to fffff80000da02e0

    STACK_TEXT:
    fffffadc`c0376108
     fffff800`00c5d707 : 00000000`40000082 00000000`00000050
    00000000`00000008 fffffadc`c03768f0 : nt!RtlpBreakWithStatusInstruction
    fffffadc`c0376110
     fffff800`00c5e9a0 : fffff800`00000003 00000000`00000050
    fffffadc`c1002028 00000000`00000000 : nt!KiBugCheckDebugBreak+0x17
    fffffadc`c0376180
     fffff800`00d97144 : 00000000`00000050 fffffadc`c1002028
    00000000`00000000 fffffadc`c03768f0 : nt!KeBugCheck2+0x630
    fffffadc`c03767c0
     fffff800`00d3982d : 00000000`00000050 fffffadc`c1002028
    00000000`00000000 fffffadc`c03768f0 : nt!KeBugCheckEx+0x104
    fffffadc`c0376800
     fffff800`00da5059 : 00000000`00000000 fffffadc`c1002028
    00000000`00000100 fffffadc`c03768f0 : nt!MmAccessFault+0x162d
    fffffadc`c03768f0
     fffff800`00c90624 : fffff800`00000000 fffff800`00000007
    fffff800`00f5e948 fffffadc`c0376ae0 : nt!KiPageFault+0x119
    fffffadc`c0376a80
     fffffadc`be3ad212 : 00000000`00000000 00000000`00100000
    fffffadc`00000000 fffffadc`be3a2950 : nt!MmMapIoSpace+0x564
    fffffadc`c0376b70
     fffffadc`be3bbc42 : fffffadc`def751d0 fffffadc`be3c7460
    00000000`00000000 fffff780`00000008 :
    VIDEOPRT!pVideoPortInitializeInt10+0x52
    fffffadc`c0376bc0
    fffff800`010bb08a : fffffadc`def75080 fffffadc`dfc72cf0
    fffffadc`c0376e00 fffff800`00000000 : VIDEOPRT!pVideoPortDispatch+0xf32
    fffffadc`c0376cf0
     fffff800`0114d53b : fffffadc`def75080 00000000`00000000
    fffffadc`c0377010 fffffa80`009d8f00 : nt!IopParseDevice+0x13ca
    fffffadc`c0376e70
     fffff800`01153e47 : 00000000`00000000 fffffadc`c0377000
    fffffadc`00000200 00000000`00000000 : nt!ObpLookupObjectName+0xacb
    fffffadc`c0376f90
     fffff800`0109f329 : fffffadc`c03776c0 00000000`00000000
    fffff800`010a0400 00000000`00000000 : nt!ObOpenObjectByName+0x257
    fffffadc`c0377190
     fffff800`0109ec2c : fffffadc`c03776a0 fffffa80`00000000
    fffffadc`c03776c0 fffffadc`c03776b0 : nt!IopCreateFile+0x599
    fffffadc`c0377300
     fffff800`010ab16f : fffffadc`c03776a0 fffff800`00000000
    fffffadc`c03776c0 fffffadc`c03776b0 : nt!IoCreateFile+0x1bc
    fffffadc`c03773e0
     fffff800`00da5f43 : fffffadc`c03776a0 fffff800`00000000
    fffffadc`c03776c0 fffffadc`c03776b0 : nt!NtOpenFile+0xaf
    fffffadc`c0377460
     fffff800`00da63c0 : fffff800`010a0577 fffffadc`c03776a0
    00000000`00000000 fffffadc`c03776c0 : nt!KiSystemServiceCopyEnd+0x3
    fffffadc`c0377668
     fffff800`010a0577 : fffffadc`c03776a0 00000000`00000000
    fffffadc`c03776c0 fffffadc`c03776b0 : nt!KiServiceLinkage
    fffffadc`c0377670
     fffff97f`ff008587 : fffffadc`c0377850 fffffadc`00000000
    fffffadc`c0377780 fffffadc`c0377770 : nt!IoGetDeviceObjectPointer+0xa7
    fffffadc`c0377700
     fffff97f`ff00334d : 00000000`00000001 00000000`00000000
    00000000`00000003 00000000`00000001 :
    win32k!DrvUpdateGraphicsDeviceList+0x4ba
    fffffadc`c0377900
    fffff97f`ff008d8c : fffffadc`df44b9e0 00000000`00000000
    00000000`01bc8000 00000000`00000000 : win32k!DrvInitConsole+0xd5
    fffffadc`c0377970
     fffff97f`ff00bb28 : fffffa80`008b0e10 fffff97f`fcff0b80
    fffffadc`c0377a38 fffffadc`c0377a78 : win32k!InitVideo+0xb
    fffffadc`c03779e0
     fffff97f`ff00b646 : 00000000`00000154 fffffadc`c0377cf0
    00000000`00000003 00000000`00000150 : win32k!UserInitialize+0x63c
    fffffadc`c0377c20
     fffff800`00da5f43 : 00000000`00000001 00000000`0015fa40
    fffffadc`df0e65f0 00000000`00000020 : win32k!NtUserInitialize+0x15f
    fffffadc`c0377c70
     000007ff`7c7de86a : 000007ff`7c7deaa9 00000000`001657f0
    00000000`001657f0 00000000`00000003 : nt!KiSystemServiceCopyEnd+0x3
    00000000`0015fbc8
     000007ff`7c7deaa9 : 00000000`001657f0 00000000`001657f0
    00000000`00000003 00000000`00000000 : winsrv!NtUserInitialize+0xa
    00000000`0015fbd0
     000007ff`7c5b3eb8 : 00000000`00000000 00000000`00000001
    00000000`001657f0 00000000`00000000 :
    winsrv!UserServerDllInitialization+0x229
    00000000`0015fc50
    00000000`00000000 : 00000000`00000001 00000000`001657f0
    00000000`00000000 00000000`00100000 :
    CSRSRV!CsrUnhandledExceptionFilter+0x368

    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    VIDEOPRT!pVideoPortInitializeInt10+52
    fffffadc`be3ad212 4885c0          test    rax,rax

    SYMBOL_STACK_INDEX:  7

    SYMBOL_NAME:  VIDEOPRT!pVideoPortInitializeInt10+52

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: VIDEOPRT

    IMAGE_NAME:  VIDEOPRT.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP:  45d70045

    FAILURE_BUCKET_ID:  X64_0x50_VIDEOPRT!pVideoPortInitializeInt10+52

    BUCKET_ID:  X64_0x50_VIDEOPRT!pVideoPortInitializeInt10+52

    Followup: MachineOwner
    ---------

    8: kd> lm
    start             end                 module name
    00000000`4a680000 00000000`4a686000   csrss      (deferred)
    00000000`77c20000 00000000`77d2c000   USER32     (deferred)
    00000000`77d40000
     00000000`77eb3000   KERNEL32   (pdb symbols)
    c:\symbols\kernel32.pdb\8600FA0E2CE1463C8CDD0CBC26A8D84C2\kernel32.pdb
    00000000`77ec0000
     00000000`77ff9000   ntdll      (pdb symbols)
    c:\symbols\ntdll.pdb\95DDB8CA2A5D4C0EBF9924339F14E4862\ntdll.pdb
    000007ff`7c5b0000 000007ff`7c5cd000   CSRSRV     (export symbols)       CSRSRV.dll
    000007ff`7c7b0000 000007ff`7c7c6000   basesrv    (deferred)
    000007ff`7c7d0000
     000007ff`7c851000   winsrv     (pdb symbols)
    c:\symbols\winsrv.pdb\3579A339B79745F482A2CD61E9A594CF2\winsrv.pdb
    000007ff`7fc90000 000007ff`7fd2b000   GDI32      (deferred)
    fffff800`00c00000
     fffff800`01354000   nt         (pdb symbols)
    c:\symbols\ntkrnlmp.pdb\61159976B2E549B2B431DC7329C4B4B51\ntkrnlmp.pdb
    fffff800`01354000 fffff800`013ba000   hal        (deferred)
    fffff97f`fd000000 fffff97f`fd028000   dxg        (deferred)
    fffff97f`ff000000
     fffff97f`ff45f000   win32k     (pdb symbols)
    c:\symbols\win32k.pdb\3E94FFC5B7B84E3999B1CB92A9B3B2372\win32k.pdb
    fffffadc`bd8a0000 fffffadc`bd96d000   mrxsmb     (deferred)
    fffffadc`bd96d000 fffffadc`bd9be000   rdbss      (deferred)
    fffffadc`bd9be000 fffffadc`bda0b000   afd        (deferred)
    fffffadc`bda0b000 fffffadc`bda65000   netbt      (deferred)
    fffffadc`bda65000 fffffadc`bdaa3000   ipnat      (deferred)
    fffffadc`bdaa3000 fffffadc`bdb98000   tcpip      (deferred)
    fffffadc`bdb98000 fffffadc`bdbc3000   ipsec      (deferred)
    fffffadc`bdbc3000 fffffadc`bdbd7000   Npfs       (deferred)
    fffffadc`bdc5d000 fffffadc`bdc9d000   portcls    (deferred)
    fffffadc`bdc9d000 fffffadc`bdcc7000   nvhda64    (deferred)
    fffffadc`bdcc7000 fffffadc`bdcdb000   NDProxy    (deferred)
    fffffadc`be161000 fffffadc`be17c000   update     (deferred)
    fffffadc`be17c000 fffffadc`be192000   termdd     (deferred)
    fffffadc`be192000 fffffadc`be1e9000   rdpdr      (deferred)
    fffffadc`be1e9000 fffffadc`be1ff000   msgpc      (deferred)
    fffffadc`be1ff000 fffffadc`be21f000   psched     (deferred)
    fffffadc`be21f000 fffffadc`be242000   raspptp    (deferred)
    fffffadc`be242000 fffffadc`be256000   raspppoe   (deferred)
    fffffadc`be256000 fffffadc`be282000   ndiswan    (deferred)
    fffffadc`be282000 fffffadc`be2a8000   rasl2tp    (deferred)
    fffffadc`be2a8000 fffffadc`be2f1000   ks         (deferred)
    fffffadc`be2f1000 fffffadc`be30e000   i8042prt   (deferred)
    fffffadc`be30e000 fffffadc`be35f000   e1r51x64   (deferred)
    fffffadc`be35f000 fffffadc`be39d000   HDAudBus   (deferred)
    fffffadc`be39d000
     fffffadc`be3cf000   VIDEOPRT   (pdb symbols)
    c:\symbols\videoprt.pdb\49E376C44D0944CF8DA5E04E57F0BE071\videoprt.pdb
    fffffadc`be447000 fffffadc`bef5ce00   nv4_mini   (deferred)
    fffffadc`bef5d000 fffffadc`bef66000   watchdog   (deferred)
    fffffadc`bef6d000 fffffadc`bef79000   Dxapi      (deferred)
    fffffadc`bef9d000 fffffadc`befab000   kbdclass   (deferred)
    fffffadc`befbd000 fffffadc`befc7000   ndistapi   (deferred)
    fffffadc`befcd000 fffffadc`befd6000   wmiacpi    (deferred)
    fffffadc`befed000 fffffadc`beffc000   TDI        (deferred)
    fffffadc`bf76c000 fffffadc`bf77a000   dump_STORAHCI   (deferred)
    fffffadc`bf783000
     fffffadc`bf790000   mssmbios   (pdb symbols)
    c:\symbols\mssmbios.pdb\ECAD413A7E6C4AFEB52606D7E237C5411\mssmbios.pdb
    fffffadc`bf7df000 fffffadc`bf7e9000   Fs_Rec     (deferred)
    fffffadc`bf7ff000 fffffadc`bf80b000   dump_diskdump   (deferred)
    fffffadc`bfe76000 fffffadc`bfeaa000   Mup        (deferred)
    fffffadc`bfeaa000 fffffadc`bff10000   NDIS       (deferred)
    fffffadc`bff10000 fffffadc`bff44000   KSecDD     (deferred)
    fffffadc`bff44000 fffffadc`bff85000   Fastfat    (deferred)
    fffffadc`bff85000 fffffadc`bffa8000   sr         (deferred)
    fffffadc`bffa8000 fffffadc`bffe6000   fltMgr     (deferred)
    fffffadc`bffe6000 fffffadc`c0003000   CLASSPNP   (deferred)
    fffffadc`c0003000 fffffadc`c0018000   disk       (deferred)
    fffffadc`c0018000 fffffadc`c007b000   storport   (deferred)
    fffffadc`c007b000 fffffadc`c00c6000   volsnap    (deferred)
    fffffadc`c00c6000 fffffadc`c010d000   dmio       (deferred)
    fffffadc`c010d000 fffffadc`c014d000   ftdisk     (deferred)
    fffffadc`c014d000 fffffadc`c0163000   MountMgr   (deferred)
    fffffadc`c0163000 fffffadc`c0184000   pci        (deferred)
    fffffadc`c0184000 fffffadc`c01f2000   ACPI       (deferred)
    fffffadc`c02f3000 fffffadc`c0305000   intelppm   (deferred)
    fffffadc`c0306000 fffffadc`c0318000   wanarp     (deferred)
    fffffadc`c0319000 fffffadc`c032b000   netbios    (deferred)
    fffffadc`c032c000 fffffadc`c033e000   Fips       (deferred)
    fffffadc`c05fb000 fffffadc`c0605000   kdcom      (deferred)
    fffffadc`c060b000 fffffadc`c0614000   BOOTVID    (deferred)
    fffffadc`c061b000 fffffadc`c0624000   WMILIB     (deferred)
    fffffadc`c062b000 fffffadc`c0634000   isapnp     (deferred)
    fffffadc`c063b000 fffffadc`c064b000   PartMgr    (deferred)
    fffffadc`c064b000 fffffadc`c0659000   storahci   (deferred)
    fffffadc`c065b000 fffffadc`c0666000   crcdisk    (deferred)
    fffffadc`c071b000 fffffadc`c0725000   mnmdd      (deferred)
    fffffadc`c078b000 fffffadc`c0798000   mouclass   (deferred)
    fffffadc`c079b000 fffffadc`c07a9000   vga        (deferred)
    fffffadc`c07cb000 fffffadc`c07d8000   Msfs       (deferred)
    fffffadc`c081b000 fffffadc`c0825000   RDPCDD     (deferred)
    fffffadc`c082b000 fffffadc`c0836000   raspti     (deferred)
    fffffadc`c084b000 fffffadc`c0855000   rasacd     (deferred)
    fffffadc`c085b000 fffffadc`c0868000   ptilink    (deferred)
    fffffadc`c0873000 fffffadc`c087b000   audstub    (deferred)
    fffffadc`c087b000 fffffadc`c0883000   Null       (deferred)
    fffffadc`c09fb000 fffffadc`c0a02000   dmload     (deferred)
    fffffadc`c0bad000 fffffadc`c0bb2e80   ksthunk    (deferred)
    fffffadc`c0c63000 fffffadc`c0c6a000   Beep       (deferred)
    fffffadc`c0db5000 fffffadc`c0db6400   swenum     (deferred)

    Unloaded modules:
    fffffadc`bd889000 fffffadc`bd8a0000   imapi.sys
    fffffadc`bd9a8000 fffffadc`bd9be000   redbook.sys
    fffffadc`bd99b000 fffffadc`bd9be000   serial.sys
    fffffadc`bdbdc000 fffffadc`bdbf7000   cdrom.sys
    fffffadc`c076b000 fffffadc`c0774000   Sfloppy.SYS
    fffffadc`c075b000 fffffadc`c0767000   Flpydisk.SYS
    fffffadc`c07eb000 fffffadc`c07f9000   Fdc.SYS

#2338

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #2337

> PS: I have no idea how to hack this. May be it can be done )!

    mov     dword ptr [rsp+38h+PhysicalAddress], 0
    ....
    xor     eax, eax
    mov     dword ptr [rsp+38h+PhysicalAddress+4], eax
    mov     rcx, qword ptr [rsp+38h+PhysicalAddress] ; PhysicalAddress
    mov     edx, 100000h    ; NumberOfBytes
    call    cs:__imp_MmMapIoSpace <-  ERROR !

it try to map memory at PHYSICAL adress at 0x0000000 with length = 1Megabyte (low DOS memory range) to be accessable to kernel
if csm is ON this error shouldn't be

#2339

Gelip

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #2331

> probably error in next proc, pVideoPortInitializeInt10

Probably yes because on VMware in 6021 (EFI bios) binres in VGA rom module DC9E5943-0EB5-42C6-8F43-B081A91DF78E there is some INT10 routine that is not in the memory under C000 in WinXP:
⇗

#2340

Gelip

I test ASUS. If in bios set VGA priority to PCI (i have not PCI card in slot PCI only iGPU integrated in CPU i3) and disable CSM then no error VIDEOPORT.SYS in WinDbg while boot WinXP x64 but instead, the OS auto restarts and bios display info:
The VGA card is not supported by UEFI driver.

## Page 157

#2341 | Gelip | @diderius Are you testing with graphics cards that have GOP firmware?
#2342 | diderius6 | ⇗ @Gelip Yes, but yesterday I tested on the Giga H110 board also without the nvidia card GT 730 hangs also Dietmar
#2343 | Gelip | @diderius Have you tested running WinXP x64 under UEFI with a GOP card and with the NVIDIA drivers installed for WinXP x64 ???
#2344 | diderius6 | ⇗ @Gelip yes ) Dietmar
#2345 | Gelip | @diderius This means that the GOP card will not help :-( In that case, I will not buy a card that has GOP firmware.

#2346

infuscomus

⇗ @diderius6
videoprt.sys from vista beta 5048 x86 and x64 again matches imports from XP - can you test if it works OK with XP?
EDIT:
oops! watchdog.sys has several missing imports
watchdog.sys 5048 missing 1 import - KdRefreshDebuggerNotPresent (can this import be removed without breaking it?)
EDIT2:
I was dumb and was looking at x86 versions, not x64
x64 versions seem to not have any missing imports

#2347

diderius6

⇗ @infuscomus
I just copy the videoprt.sys from 5048 64 bit to the harddsik Windows\system32\drivers
But now comes the same error as if no videoprt.sys is there and it is also not listed under the loaded modules
Dietmar

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Opened \\.\com1
    Waiting to reconnect...
    Connected to Windows Server 2003 3790 x64 target at (Sun Sep  8 13:59:20.250 2019 (UTC + 2:00)), ptr64 TRUE
    Kernel Debugger connection established.
    WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
    Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
    *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
    Executable search path is: C:\localsymbols
    Windows Server 2003 Kernel Version 3790 MP (1 procs) Checked x64
    Built by: 3790.srv03_sp2_rtm.070216-1710
    Machine Name:
    Kernel base = 0xfffff800`00c00000 PsLoadedModuleList = 0xfffff800`00fd1fd0
    System Uptime: not available
    AhciHwFindAdapter finishing
    AhciHwFindAdapter finishing
    PipCallDriverAddDevice:			Ignoring driver load failure (status = c000026c) until user-mode PnPMgr comes online
    KDTARGET: Refreshing KD connection
    PipCallDriverAddDevice:			Ignoring driver load failure (status = c000026c) until user-mode PnPMgr comes online
    PipCallDriverAddDevice:			Ignoring driver load failure (status = c000026c) until user-mode PnPMgr comes online
    PipCallDriverAddDevice:			Ignoring driver load failure (status = c000026c) until user-mode PnPMgr comes online
    PipCallDriverAddDevice:			Ignoring driver load failure (status = c000026c) until user-mode PnPMgr comes online
    PipCallDriverAddDevice:			Ignoring driver load failure (status = c000026c) until user-mode PnPMgr comes online
    PipCallDriverAddDevice:			Ignoring driver load failure (status = c000026c) until user-mode PnPMgr comes online
    PipCallDriverAddDevice:			Ignoring driver load failure (status = c000026c) until user-mode PnPMgr comes online
    HALACPI:  The BIOS wants the OS to preserve 3ae000 bytes

    *** Fatal System Error: 0xc000021a
                                                 (0xFFFFFA80007096B0,0x00000000C0000263,0x0000000000000000,0x0000000000000000)

    STOP: c000021a {Fatal System Error}
    The Session Manager Initialization system process terminated unexpectedly with a status of 0xc0000263 (0x00000000 0x00000000).
    The system has been shut down.
    Break instruction exception - code 80000003 (first chance)

    A fatal system error has occurred.
    Debugger entered on first try; Bugcheck callbacks have not been invoked.

    A fatal system error has occurred.

    Connected to Windows Server 2003 3790 x64 target at (Sun Sep  8 14:00:54.906 2019 (UTC + 2:00)), ptr64 TRUE
    Loading Kernel Symbols
    ...............................................................
    ......
    Loading User Symbols

    Loading unloaded module list
    .........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck C000021A, {fffffa80007096b0, c0000263, 0, 0}

    unable to get nt!KiCurrentEtwBufferOffset
    unable to get nt!KiCurrentEtwBufferBase
    Probably caused by : ntkrnlmp.exe ( nt!NtSetSystemPowerState+958 )

    Followup: MachineOwner
    ---------

    nt!RtlpBreakWithStatusInstruction:
    fffff800`00da02e0 cc              int     3
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    WINLOGON_FATAL_ERROR (c000021a)
    The Winlogon process terminated unexpectedly.
    Arguments:
    Arg1: fffffa80007096b0, String that identifies the problem.
    Arg2: 00000000c0000263, Error Code.
    Arg3: 0000000000000000
    Arg4: 0000000000000000

    Debugging Details:
    ------------------

    unable to get nt!KiCurrentEtwBufferOffset
    unable to get nt!KiCurrentEtwBufferBase

    ERROR_CODE:
     (NTSTATUS) 0xc000021a - {Daten wurden nicht akzeptiert}  Der TDI-Client
     konnte die empfangenen Daten nicht verarbeiten.

    EXCEPTION_CODE:
    (NTSTATUS) 0xc000021a - {Daten wurden nicht akzeptiert}  Der TDI-Client
    konnte die empfangenen Daten nicht verarbeiten.

    EXCEPTION_PARAMETER1:  fffffa80007096b0

    EXCEPTION_PARAMETER2:  00000000c0000263

    EXCEPTION_PARAMETER3:  0000000000000000

    EXCEPTION_PARAMETER4: 0

    ADDITIONAL_DEBUG_TEXT:  Session Manager Initialization

    BUGCHECK_STR:  0xc000021a_smss.exe_c0000263

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    LAST_CONTROL_TRANSFER:  from fffff80000c5d707 to fffff80000da02e0

    STACK_TEXT:
    fffffadc`c0ae8108
     fffff800`00c5d707 : 00000000`40000082 00000000`0000004c
    00000000`00000002 00000000`00000000 : nt!RtlpBreakWithStatusInstruction
    fffffadc`c0ae8110
     fffff800`00c5e9a0 : fffffadc`00000003 00000000`ffff0025
    00000000`ffffffff 00000000`00000000 : nt!KiBugCheckDebugBreak+0x17
    fffffadc`c0ae8180
     fffff800`00d97144 : 00000000`0000004c 00000000`c000021a
    fffffadc`c0c1c600 fffffadc`df5293c0 : nt!KeBugCheck2+0x630
    fffffadc`c0ae87c0
     fffff800`0126883c : 00000000`0000004c 00000000`c000021a
    fffffadc`c0c1c600 fffffadc`df5293c0 : nt!KeBugCheckEx+0x104
    fffffadc`c0ae8800
     fffff800`0126c4d8 : 00000000`00000000 fffffadc`00000000
    fffff800`00000005 fffffadc`c0ae88a8 : nt!PopGracefulShutdown+0x48c
    fffffadc`c0ae8860
     fffff800`00da5f43 : 00000000`00000004 fffffadc`00000004
    00000000`e0000004 00000000`00000200 : nt!NtSetSystemPowerState+0x958
    fffffadc`c0ae8a00
     fffff800`00da63c0 : fffff800`0116210b 00000000`00000004
    00000000`00000004 00000000`e0000004 : nt!KiSystemServiceCopyEnd+0x3
    fffffadc`c0ae8b98
     fffff800`0116210b : 00000000`00000004 00000000`00000004
    00000000`e0000004 00000000`c0000004 : nt!KiServiceLinkage
    fffffadc`c0ae8ba0
     fffff800`01161d35 : fffffadc`c067b700 fffffadc`00000004
    00000000`00000004 fffff800`c0000004 : nt!PopIssueActionRequest+0x8b
    fffffadc`c0ae8c20
     fffff800`00d69725 : 00000000`00000000 00000000`00000000
    00000000`00000000 fffffadc`df14d2c0 : nt!PopPolicyWorkerAction+0x45
    fffffadc`c0ae8c70
     fffff800`00d8a634 : 00000000`80000000 0deb47b9`d31cfa01
    00000000`00000000 4dfb07a9`930cba46 : nt!PopPolicyWorkerThread+0x185
    fffffadc`c0ae8ce0
     fffff800`011762de : 00000000`00000001 f2af5786`1df48971
    5856ccd3`e5b9b72d 7854ecf1`c5bb972f : nt!ExpWorkerThread+0x194
    fffffadc`c0ae8d70
     fffff800`00d9fe96 : fffff800`00d8a4a0 00000000`00000001
    fffff800`011762a0 8ae10682`5e442fc8 : nt!PspSystemThreadStartup+0x3e
    fffffadc`c0ae8dd0
     00000000`00000000 : 00000000`00000000 00000000`00000000
    00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!NtSetSystemPowerState+958
    fffff800`0126c4d8 cc              int     3

    SYMBOL_STACK_INDEX:  5

    SYMBOL_NAME:  nt!NtSetSystemPowerState+958

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  45d70b7b

    FAILURE_BUCKET_ID:  X64_0xc000021a_smss.exe_c0000263_nt!NtSetSystemPowerState+958

    BUCKET_ID:  X64_0xc000021a_smss.exe_c0000263_nt!NtSetSystemPowerState+958

    Followup: MachineOwner
    ---------

    2: kd> lm
    start             end                 module name
    fffff800`00c00000
     fffff800`01354000   nt         (pdb symbols)
    c:\symbols\ntkrnlmp.pdb\61159976B2E549B2B431DC7329C4B4B51\ntkrnlmp.pdb
    fffff800`01354000 fffff800`013ba000   hal        (deferred)
    fffffadc`b9946000 fffffadc`b9a13000   mrxsmb     (deferred)
    fffffadc`b9a13000 fffffadc`b9a64000   rdbss      (deferred)
    fffffadc`b9a64000 fffffadc`b9ab1000   afd        (deferred)
    fffffadc`b9ab1000 fffffadc`b9b0b000   netbt      (deferred)
    fffffadc`b9b0b000 fffffadc`b9b49000   ipnat      (deferred)
    fffffadc`b9b49000 fffffadc`b9c3e000   tcpip      (deferred)
    fffffadc`b9c3e000 fffffadc`b9c69000   ipsec      (deferred)
    fffffadc`b9c69000 fffffadc`b9c7d000   Npfs       (deferred)
    fffffadc`bd5a9000 fffffadc`bd5bd000   NDProxy    (deferred)
    fffffadc`bd5bd000 fffffadc`bd5fd000   portcls    (deferred)
    fffffadc`bd5fd000 fffffadc`bd627000   nvhda64    (deferred)
    fffffadc`be168000 fffffadc`be183000   update     (deferred)
    fffffadc`be183000 fffffadc`be199000   termdd     (deferred)
    fffffadc`be1df000 fffffadc`be236000   rdpdr      (deferred)
    fffffadc`be236000 fffffadc`be24c000   msgpc      (deferred)
    fffffadc`be24c000 fffffadc`be26c000   psched     (deferred)
    fffffadc`be26c000 fffffadc`be28f000   raspptp    (deferred)
    fffffadc`be28f000 fffffadc`be2a3000   raspppoe   (deferred)
    fffffadc`be2a3000 fffffadc`be2cf000   ndiswan    (deferred)
    fffffadc`be2cf000 fffffadc`be2f5000   rasl2tp    (deferred)
    fffffadc`be2f5000 fffffadc`be33e000   ks         (deferred)
    fffffadc`be33e000 fffffadc`be35b000   i8042prt   (deferred)
    fffffadc`be35b000 fffffadc`be3ac000   e1r51x64   (deferred)
    fffffadc`be3ac000 fffffadc`be3ea000   HDAudBus   (deferred)
    fffffadc`bf79f000 fffffadc`bf7a8000   wmiacpi    (deferred)
    fffffadc`bf7bf000 fffffadc`bf7c9000   Fs_Rec     (deferred)
    fffffadc`bf80f000 fffffadc`bf81e000   TDI        (deferred)
    fffffadc`bfe76000 fffffadc`bfeaa000   Mup        (deferred)
    fffffadc`bfeaa000 fffffadc`bff10000   NDIS       (deferred)
    fffffadc`bff10000 fffffadc`bff44000   KSecDD     (deferred)
    fffffadc`bff44000 fffffadc`bff85000   Fastfat    (deferred)
    fffffadc`bff85000 fffffadc`bffa8000   sr         (deferred)
    fffffadc`bffa8000 fffffadc`bffe6000   fltMgr     (deferred)
    fffffadc`bffe6000 fffffadc`c0003000   CLASSPNP   (deferred)
    fffffadc`c0003000 fffffadc`c0018000   disk       (deferred)
    fffffadc`c0018000 fffffadc`c007b000   storport   (deferred)
    fffffadc`c007b000 fffffadc`c00c6000   volsnap    (deferred)
    fffffadc`c00c6000 fffffadc`c010d000   dmio       (deferred)
    fffffadc`c010d000 fffffadc`c014d000   ftdisk     (deferred)
    fffffadc`c014d000 fffffadc`c0163000   MountMgr   (deferred)
    fffffadc`c0163000 fffffadc`c0184000   pci        (deferred)
    fffffadc`c0184000 fffffadc`c01f2000   ACPI       (deferred)
    fffffadc`c02f3000 fffffadc`c0305000   intelppm   (deferred)
    fffffadc`c0306000 fffffadc`c0318000   wanarp     (deferred)
    fffffadc`c0319000 fffffadc`c032b000   netbios    (deferred)
    fffffadc`c032c000 fffffadc`c033e000   Fips       (deferred)
    fffffadc`c05fb000 fffffadc`c0605000   kdcom      (deferred)
    fffffadc`c060b000 fffffadc`c0614000   BOOTVID    (deferred)
    fffffadc`c061b000 fffffadc`c0624000   WMILIB     (deferred)
    fffffadc`c062b000 fffffadc`c0634000   isapnp     (deferred)
    fffffadc`c063b000 fffffadc`c064b000   PartMgr    (deferred)
    fffffadc`c064b000 fffffadc`c0659000   storahci   (deferred)
    fffffadc`c065b000 fffffadc`c0666000   crcdisk    (deferred)
    fffffadc`c073b000
     fffffadc`c0748000   mssmbios   (pdb symbols)
    c:\symbols\mssmbios.pdb\ECAD413A7E6C4AFEB52606D7E237C5411\mssmbios.pdb
    fffffadc`c076b000 fffffadc`c0774000   watchdog   (deferred)
    fffffadc`c07ab000 fffffadc`c07b9000   kbdclass   (deferred)
    fffffadc`c07cb000 fffffadc`c07d5000   ndistapi   (deferred)
    fffffadc`c07db000 fffffadc`c07e8000   mouclass   (deferred)
    fffffadc`c080b000 fffffadc`c0818000   ptilink    (deferred)
    fffffadc`c081b000 fffffadc`c0825000   rasacd     (deferred)
    fffffadc`c084b000 fffffadc`c0858000   Msfs       (deferred)
    fffffadc`c085b000 fffffadc`c0866000   raspti     (deferred)
    fffffadc`c086b000 fffffadc`c0873000   audstub    (deferred)
    fffffadc`c0873000 fffffadc`c087b000   Null       (deferred)
    fffffadc`c09fb000 fffffadc`c0a02000   dmload     (deferred)
    fffffadc`c0b98000 fffffadc`c0b9de80   ksthunk    (deferred)
    fffffadc`c0bfa000 fffffadc`c0c01000   Beep       (deferred)
    fffffadc`c0db5000 fffffadc`c0db6400   swenum     (deferred)

    Unloaded modules:
    fffffadc`c075b000 fffffadc`c0767000   dump_storport.sys
    fffffadc`c071b000 fffffadc`c0729000   dump_STORAHCI.sys
    fffffadc`b992f000 fffffadc`b9946000   imapi.sys
    fffffadc`b9a4e000 fffffadc`b9a64000   redbook.sys
    fffffadc`b9a41000 fffffadc`b9a64000   serial.sys
    fffffadc`b9ce3000 fffffadc`b9cfe000   cdrom.sys
    fffffadc`bf7af000 fffffadc`bf7b8000   Sfloppy.SYS
    fffffadc`befbd000 fffffadc`befc9000   Flpydisk.SYS
    fffffadc`c074b000 fffffadc`c0759000   Fdc.SYS

#2348

infuscomus

⇗ @diderius6
watchdog.sys 5048 is also needed
My guess is it does not work right now because of missing imports
EDIT:
I was dumb and was looking at x86 versions, not x64
x64 versions seem to not have any missing imports

#2349

diderius6

⇗ @infuscomus
Here are the 2 files from 5048 64 bit
unmodded
Dietmar
diderius6 has attached files to this post

- ⇗ Videoprt64Watchdog5048.rar

#2350 | infuscomus | ⇗ @diderius6 no missing imports for these - earlier I was looking at x86 versions by mistake which does have missing imports can you try and boot XP x64 in CSM mode with these drivers?
#2351 | diderius6 | ⇗ @infuscomus Later in the evening, because now I hurry to family meeting Dietmar

#2352

Gelip

My ASUS has GOP firmware for iGPU graphics card in motherboard bios but to be available in the system the computer and operating system must be running without CSM. I just installed Win10 without CSM and GPU-Z shows that GOP is present. As confirmation, I checked the bios 1408.bin in UBU (UEFI BIOS Updater):
⇗ ⇗ ⇗ ⇗
If CSM is enabled then legacy OROM VBIOS SNB-IVB 2143 is used instead.
P.S. I don't have to buy a PCIe graphics card with GOP for WinXP x64 testing :-)

#2353

Gelip

I installed the IntelHD driver and now WinDbg shows that it is his error and not videoprt.sys:

    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.

    Opened \\.\com1
    Waiting to reconnect...
    Connected to Windows Server 2003 3790 x64 target at (Sun Sep  8 13:39:57.774 2019 (GMT+2)), ptr64 TRUE
    Kernel Debugger connection established.
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
    Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64
    Built by: 3790.srv03_sp2_rtm.070216-1710
    Machine Name:
    Kernel base = 0xfffff800`01800000 PsLoadedModuleList = 0xfffff800`019d5100
    System Uptime: not available

    Intel Storage Driver Ver: 11.2.0.1006

    KDTARGET: Refreshing KD connection

    *** Fatal System Error: 0x00000050
                                                 (0xFFFFF80000090000,0x0000000000000000,0xFFFFF80001CA664D,0x0000000000000000)

    Break instruction exception - code 80000003 (first chance)

    A fatal system error has occurred.
    Debugger entered on first try; Bugcheck callbacks have not been invoked.

    A fatal system error has occurred.

    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {fffff80000090000, 0, fffff80001ca664d, 0}

    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntdll.dll -
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for hal.dll -
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for VIDEOPRT.SYS -
    *** ERROR: Module load completed but symbols could not be loaded for igxpmp64.sys
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys -
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for igxpdv64.DLL -
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for igxpgd64.dll -
    *** ERROR: Module load completed but symbols could not be loaded for igxprd64.dll
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Probably caused by : igxpmp64.sys ( igxpmp64_fffffadfc85a4000+26a3e )

    Followup: MachineOwner
    ---------

    nt!DbgBreakPointWithStatus:
    fffff800`01826db0 cc              int     3

#2354

skullteria

> Zitat von ⇗ Gelip im Beitrag ¶ #2329

> I connected WinDbg to ASUS and it turns out that the problem is caused by the VIDEOPRT.SYS file and/or the AHCI driver regardless of whether we use the AnaPa driver or boot the system without any graphics driver (vga and VgaSave services removed):

>     Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
>     Copyright (c) Microsoft Corporation. All rights reserved.

>     Opened \\.\com1
>     Waiting to reconnect...
>     Connected to Windows Server 2003 3790 x64 target at (Sun Sep  8 09:14:38.008 2019 (GMT+2)), ptr64 TRUE
>     Kernel Debugger connection established.
>     Symbol search path is: *** Invalid ***
>     ****************************************************************************
>     * Symbol loading may be unreliable without a symbol search path.           *
>     * Use .symfix to have the debugger choose a symbol path.                   *
>     * After setting your symbol path, use .reload to refresh symbol locations. *
>     ****************************************************************************
>     Executable search path is:
>     *********************************************************************
>     * Symbols can not be loaded because symbol path is not initialized. *
>     *                                                                   *
>     * The Symbol Path can be set by:                                    *
>     *   using the _NT_SYMBOL_PATH environment variable.                 *
>     *   using the -y <symbol_path> argument when starting the debugger. *
>     *   using .sympath and .sympath+                                    *
>     *********************************************************************
>     *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
>     Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64
>     Built by: 3790.srv03_sp2_rtm.070216-1710
>     Machine Name:
>     Kernel base = 0xfffff800`01800000 PsLoadedModuleList = 0xfffff800`019d5100
>     System Uptime: not available

>     Intel Storage Driver Ver: 11.2.0.1006

>     KDTARGET: Refreshing KD connection

>     *** Fatal System Error: 0x00000050
>                                                  (0xFFFFFADFCB40202A,0x0000000000000000,0xFFFFF800018E2CAE,0x0000000000000000)

>     Break instruction exception - code 80000003 (first chance)

>     A fatal system error has occurred.
>     Debugger entered on first try; Bugcheck callbacks have not been invoked.

>     A fatal system error has occurred.

>     *********************************************************************
>     * Symbols can not be loaded because symbol path is not initialized. *
>     *                                                                   *
>     * The Symbol Path can be set by:                                    *
>     *   using the _NT_SYMBOL_PATH environment variable.                 *
>     *   using the -y <symbol_path> argument when starting the debugger. *
>     *   using .sympath and .sympath+                                    *
>     *********************************************************************
>     *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
>     *******************************************************************************
>     *                                                                             *
>     *                        Bugcheck Analysis                                    *
>     *                                                                             *
>     *******************************************************************************

>     Use !analyze -v to get detailed debugging information.

>     BugCheck 50, {fffffadfcb40202a, 0, fffff800018e2cae, 0}

>     *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntdll.dll -
>     ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

>     *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
>     *************************************************************************
>     ***                                                                   ***
>     ***                                                                   ***
>     ***    Your debugger is not using the correct symbols                 ***
>     ***                                                                   ***
>     ***    In order for this command to work properly, your symbol path   ***
>     ***    must point to .pdb files that have full type information.      ***
>     ***                                                                   ***
>     ***    Certain .pdb files (such as the public OS symbols) do not      ***
>     ***    contain the required information.  Contact the group that      ***
>     ***    provided you with these symbols if you need this command to    ***
>     ***    work.                                                          ***
>     ***                                                                   ***
>     ***    Type referenced: nt!_KPRCB                                     ***
>     ***                                                                   ***
>     *************************************************************************
>     *** ERROR: Symbol file could not be found.  Defaulted to export symbols for VIDEOPRT.SYS -
>     *** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys -
>     *************************************************************************
>     ***                                                                   ***
>     ***                                                                   ***
>     ***    Your debugger is not using the correct symbols                 ***
>     ***                                                                   ***
>     ***    In order for this command to work properly, your symbol path   ***
>     ***    must point to .pdb files that have full type information.      ***
>     ***                                                                   ***
>     ***    Certain .pdb files (such as the public OS symbols) do not      ***
>     ***    contain the required information.  Contact the group that      ***
>     ***    provided you with these symbols if you need this command to    ***
>     ***    work.                                                          ***
>     ***                                                                   ***
>     ***    Type referenced: nt!_KPRCB                                     ***
>     ***                                                                   ***
>     *************************************************************************
>     *************************************************************************
>     ***                                                                   ***
>     ***                                                                   ***
>     ***    Your debugger is not using the correct symbols                 ***
>     ***                                                                   ***
>     ***    In order for this command to work properly, your symbol path   ***
>     ***    must point to .pdb files that have full type information.      ***
>     ***                                                                   ***
>     ***    Certain .pdb files (such as the public OS symbols) do not      ***
>     ***    contain the required information.  Contact the group that      ***
>     ***    provided you with these symbols if you need this command to    ***
>     ***    work.                                                          ***
>     ***                                                                   ***
>     ***    Type referenced: nt!_KPRCB                                     ***
>     ***                                                                   ***
>     *************************************************************************
>     *********************************************************************
>     * Symbols can not be loaded because symbol path is not initialized. *
>     *                                                                   *
>     * The Symbol Path can be set by:                                    *
>     *   using the _NT_SYMBOL_PATH environment variable.                 *
>     *   using the -y <symbol_path> argument when starting the debugger. *
>     *   using .sympath and .sympath+                                    *
>     *********************************************************************
>     *********************************************************************
>     * Symbols can not be loaded because symbol path is not initialized. *
>     *                                                                   *
>     * The Symbol Path can be set by:                                    *
>     *   using the _NT_SYMBOL_PATH environment variable.                 *
>     *   using the -y <symbol_path> argument when starting the debugger. *
>     *   using .sympath and .sympath+                                    *
>     *********************************************************************
>     Probably caused by : VIDEOPRT.SYS ( VIDEOPRT!VideoPortSetTrappedEmulatorPorts+5e )

>     Followup: MachineOwner
>     ---------

>     nt!DbgBreakPointWithStatus:
>     fffff800`01826db0 cc              int     3

VGA and VGASAVE are fallback if no video driver are installed. It these drivers are not present or removed from registry, windows not show interface

#2355

Gelip

> Zitat von ⇗ skullteria im Beitrag ¶ #2354

> VGA and VGASAVE are fallback if no video driver are installed. It these drivers are not present or removed from registry, windows not show interface

Yes I know about it. After removing these services from the registry, you can start WinXP x64 without a graphics driver under UEFI having, for example, access via Remote Desktop.
It looks like not on every UEFI computer - just like with the AnaPa driver.

## Page 158

#2356

Gelip

I confirm what WinDbg shows when IntelHD drivers are installed:

- if CSM is enable then videoprt.sys error
- if CSM is disabled then igxpmp64.sys error

#2357 | diderius6 | ⇗ @infuscomus "can you try and boot XP x64 in CSM mode with these drivers?" I just try and I get the same BSOD as with videoprt.sys 5048 alone Dietmar

#2358

skullteria

> Zitat von ⇗ diderius6 im Beitrag ¶ #2357

> @infuscomus
> "can you try and boot XP x64 in CSM mode with these drivers?"
> I just try and I get the same BSOD as with videoprt.sys 5048 alone
> Dietmar

Well, i think we will don't have support for any XDDM based driver. Videoprt use int10 instruction. On AMD64, int10 instruction (used to video support, on BIOS) is emulated. However, only dxgkrnl support driver without int10, on WDDM model

#2359

Gelip

Maybe files from some version of ReactOS will help because they are constantly making patches: ⇗ reactos/win32ss/drivers/videoprt
or
files from beta Longhorn Server 2008 or beta Longhorn Vista like efi files?
Why does WinXP x64 boot from UEFI on some computers and not on others e.g working on ThinkPad X220, ASRock Z170 Pro4S ???
Why WinXP boot from UEFI on VMware Workstation even with a graphics driver (VMware Tools) ???
Instead of patching system files, maybe it is better to patch the motherboard or graphics card BIOS?
⇗ @Illen
From >¶ this< post it follows that it depends on the graphics card and therefore its firmware VBIOS ROM.

#2360 | infuscomus | ⇗ @Gelip ⇗ @diderius6 Does Vista RTM boot properly in UEFI mode on boards that have trouble booting XP x64?

#2361

diderius6

⇗ @infuscomus
I have not tried yet.
Just now I make another try:
May be it can be done with winload.efi
from win8
have a nice day
Dietmar
EDIT: bootx64.efi from win8 works as good as the one from Longhorn.

#2362 | skullteria | Well, winload can't load Windows XP/2003 since Windows. Always Computer restart...I think winload from win8 works is almost impossible
#2363 | diderius6 | ⇗ @skullteria Yes, winload.efi from win8 64 bit first asks for apisetschema.dll. I give it, but then always restart, debug not possible. What is your latest version from Vista, Win7, that can start XP via its winload Dietmar

#2364

skullteria

> Zitat von ⇗ diderius6 im Beitrag ¶ #2363

> @skullteria
> Yes, winload.efi from win8 64 bit first asks for apisetschema.dll.
> I give it, but then always restart, debug not possible.
> What is your latest version from Vista, Win7, that can start XP via its winload
> Dietmar

Vista, lastest version. Windows 7 any version doesn't works. Please, confirm to me, winload.exe can start Windows XP x64 (not UEFI)?

#2365

Andalu

> Zitat von ⇗ Andalu im Beitrag ¶ #2333

> The USB3.0 drivers modded work correctly on asrock B250M Pro4 with i5 6600 skylake and XP32 (including the USB 3.0 type-C port).
> But I can obtain only a 'multiprocessor mps' system, so no ACPI and no multi-core. All the alternative options chosen during XP installation (by pressing F5 or F7 keys) are without ACPI mode or give me BSOD A5. In the updated bios, all the related options seem to be properly configured.
> Can I try something else?

I found a workaround for the problem I quoted above and so I post it here, maybe it can be useful for other owners of this motherboard. I will try to explain the procedure step by step in the hope that my poor english can be at least clear a bit.
1. I downgraded the bios from the latest version installed to the first released (1.00) - also tried intermediate versions without success - (thanks to member Mov AX, 0xDEAD for ¶ this tip);
2. At next reboot, I loaded default bios settings leaving the 'XHCI hand-off' option on disable;
3. I started the XP installation using the method described ⇗ here by the member Hardwarejiri (thanks to him too);
4. I pressed the usual F5 key and I chosen the 'ACPI Multiprocessor PC' from the list and the installation goes on with no BSOD A5 for the first time in my attempts;
5. The XP installation continues in the normal mode until it blocks on a 'asms' file request;
6. At this point, I turned it off manually, extracted the pendrive and inserted the XP installation disc in the internal optical disc drive and I restarted the machine;
7. At next boot, the installation continues from the disc and it goes on until the classic azure screen appears (no BSOD here :)) but the manual restart is needed again;
8. Now, finally, XP starts as usual. In the device manager the 'ACPI Multiprocessor PC' now appears in addition to cpu's cores previously not visible.
I then successfully installed the USB3.0 drivers modded and, for last, i updated the bios to the latest version (2.50) et voila, no change has occurred, everything seems to work as before even if the 'XHCI hand-off' option is now enabled by default.
During the XP installation the usb mouse did not work even if the ps2 emulation was enabled in the bios.
I have tried again to install XP on the upgraded bios but i still got the BSOD A5.
One last thingh I have not a solution: while the shutdown works correctly, the restart won't, it always hangs.
I will attempt for a solution...... any suggest is appreciated.
⇗

#2366 | diderius6 | ⇗ @skullteria I am on FAT32 with XP64 and it seems not to be possible via EasyBCD 1.7.2 to install the bootmgr with Vista MBR there Dietmar

#2367

skullteria

> Zitat von ⇗ diderius6 im Beitrag ¶ #2366

> @skullteria
> I am on FAT32 with XP64
> and it seems not to be possible via EasyBCD 1.7.2 to install the bootmgr with Vista MBR there
> Dietmar

Well, maybe because Windows Vista only support NTFS as system file system.

#2368

Gelip

> Zitat von ⇗ skullteria im Beitrag ¶ #2364

> > Zitat von ⇗ diderius6 im Beitrag ¶ #2363

> > @skullteria
> > Yes, winload.efi from win8 64 bit first asks for apisetschema.dll.
> > I give it, but then always restart, debug not possible.
> > What is your latest version from Vista, Win7, that can start XP via its winload
> > Dietmar

> Vista, lastest version. Windows 7 any version doesn't works. Please, confirm to me, winload.exe can start Windows XP x64 (not UEFI)?

I checked many versions of bootx64.efi (bootmgfw.efi) and winload.efi from several dozen beta versions of Vista Longhorn, Server 2008, regular Vista, 7, 8, 10
The version of efi files older than from Server 2008 16497 cannot run WinXP x64 because there is a black screen with a white bar at the top:
⇗
With efi files newer than 16497 WinXP not boot and error 0xc000000f:
⇗
Read this my post: ⇗ https://www.betaarchive.com/forum/viewto...=433499#p433499
winload.exe can start WinXP x64 in legacy (not UEFI) but also from beta server 16497:
⇗
To make possible boot over winload.exe you need:

- format partition from later OS than WinXP e.g. Win7 diskpart because he adds an entry in PBR that looks for the bootmgr file:
  ⇗
  You can fix this in WinPE (Win7) using the bootrec /fixboot command
- folder Boot with BCD file and Fonts folder with wgl4_boot.ttf
- in BCD ApplicationPath to \WINDOWS\system32\winload.exe

But there is the same startup problem as in UEFI mode with the file winload.efi
winload.exe in Legacy mode and winload.efi in UEFI mode cause the same problem, please read my post: ⇗ https://www.betaarchive.com/forum/viewto...=443358#p443358
I really recommend that you read the entire topic ⇗ Does Windows XP have EFI? carefully from beginning to end because there are many things checked and tested.

#2369 | Lost_N_BIOS | You guys post a lot in here, every day this thread is blowing up! Maybe the most active thread here

#2370

Gelip

> Zitat von ⇗ Lost_N_BIOS im Beitrag ¶ #2369

> You guys post a lot in here, every day this thread is blowing up! Maybe the most active thread here

Yeah, please look also at betaarchive how many times the thread ⇗ Does Windows XP have EFI? was viewed
⇗

## Page 159

#2371

Gelip

WinXP x64 (ia64) for Itanium CPU have EFI loader ia64ldr.efi. If you could get the source code and compile for the amd64 architecture this would probably solve the problems
⇗ https://www.betaarchive.com/forum/viewto...=432953#p432953
⇗ IA64ldr.efi
Microsoft --> ⇗ Overview of Boot Options in EFI

#2372 | Gelip | I found an interesting thing: ⇗ In Windows Server 2003, you may not be able to start a computer from a GPT disk when the computer has an Itanium processor It follows that the EFI loader IA64ldr.efi from Itanium Win2003 is not compatible with the Itanium Win2003 SP1 version and vice versa.

#2373

diderius6

⇗ @Gelip
"winload.exe in Legacy mode and winload.efi in UEFI mode cause the same problem"
This is a very important discovery.
It means, that BSOD is NOT the fault because of UEFI
Dietmar
EDIT: Now I think, winload (not important if *.efi or normal) is the reason for BSOD.
videoprt.sys tries to write in low memory and this may be forbidden via winload from Vista.
The situation for XP SP3 and *.efi boot may be other.

#2374 | infuscomus | ⇗ @diderius6 does Vista give same BSOD?

#2375

diderius6

⇗ @infuscomus
Full Vista64 I have not tried until now.
But I see, that the BSOD in videoprt.sys is always exact the same in UEFI boot for XP64 SP2,
error in memory,
not depending if you are enable\disable CSM in Bios
Dietmar

#2376 | diderius6 | May be this can help ⇗ https://www.geoffchappell.com/studies/wi...6bios/index.htm Dietmar
#2377 | infuscomus | ⇗ @diderius6 can you try replacing the bootloader with grub2? from grub2 load winload.efi maybe that might fix the video problem?

#2378

Mov AX, 0xDEAD

Again i've played with IOTR resource conflict, i think source of problem is how vga i/o ports is decoding. Windows get two i/o ranges (3b0-3bb and 3c0-3df) with 10-bit decoding from vga/pci device. These decoding means device may claim not only 3b0-3bb range but all other possible ranges with any high 6 bits in i/o adress e.g. 3b0, 7b0, bb0,..., fbb0, ffb0. IOTR claims ff00-fffe, so ffb0-ffbb & ffc0-ffdf conflicting with vga.
How Windows7+ resolve this problem is still big QUESTION :)
Simple implementation of blocking this device in winxp's v5512 acpi.sys without touching DSDT & ConcatenateResTemplate:
- need patch this code:

> Zitat

>             Name (BUF0, ResourceTemplate ()
>                     {
>                         IO (Decode16,
>                             0x0000,             // Range Minimum  ; Begin I/O range, filled with 0xFF00
>                             0x0000,             // Range Maximum  ; End   I/O range, filled with 0xFF00
>                             0x01,               // Alignment
>                             0xFF,               // Length        ; We will set length to Zero or lower 0xB0
>                             _Y21)
>                     })

same in aml hex code:
`47 01 00 00 00 00 01 FF 79 00`
- patching "_Buffer" proc:

    .text:000274CC                 and     ecx, 3
    .text:000274CF                 rep movsb

    .text:000274D1                 jmp     loc_3BA98 ; replace two "mov xx,yy"
    .text:000274D6 loc_274D6:                        ; with jmp/nop , position depend offset !
    .text:000274D6                 nop               ; dummy for aligning

    .text:000274D7                 mov     [ecx+3Ch], eax
    .text:000274DA                 pop     edi

- allocating some bytes in .TEXT section, for example in enlarged .INIT section at 0x0003BA98:

    .text:0003BA98 loc_3BA98:
    .text:0003BA98                 cmp     eax, 0Ah                       ; check for length==10 bytes
    .text:0003BA9D                 jnz     short loc_3BAC2                ; Skip patching if not
    .text:0003BA9F                 mov     eax, [ebx+30h]
    .text:0003BAA2                 mov     eax, [eax+10h]                 ; Ptr where buffer was copied
    .text:0003BAA5                 cmp     dword ptr [eax],   00000147h   ; "47 01 00 00"
    .text:0003BAAB                 jnz     short loc_3BAC2
    .text:0003BAAD                 cmp     dword ptr [eax+4], FF010000h   ; "00 00 01 FF"
    .text:0003BAB4                 jnz     short loc_3BAC2
    .text:0003BAB6                 cmp     word ptr [eax+8],  0079h       ; "79 00"
    .text:0003BABC                 jnz     short loc_3BAC2

    .text:0003BABE                 mov     byte ptr [eax+7],  00          ; Length FF -> 00 or any lower 0xB0

    .text:0003BAC2 loc_3BAC2:
    .text:0003BAC2                 mov     eax, [ebx+14h]                 ; original 1st mox xx,yy
    .text:0003BAC5                 mov     ecx, [ebp+arg_0]               ; original 2nd mox xx,yy
    .text:0003BAC8                 jmp     loc_274D6                      ; jmp back, position depend offset !

0x0003BA98 in hex:

     3D 0A 00 00 00 75 23 8B  43 30 8B 40 10 81 38 47
     01 00 00 75 15 81 78 04  00 00 01 FF 75 0C 66 81
     78 08 79 00 75 04 C6 40  07 00 8B 43 14 8B 4D 08
     E9 09 ba fe ff

If length = 0 IOTR device report zero i/o range and windows hide/remove it
If length < 0xB0 IOTR device still present but without conflict with vga i/o ports

#2379

diderius6

⇗ @infuscomus
The problem is not direct related to UEFI.
It is how to manage INT10 call.
Some UEFI Bios have an extra INT10 UEFI "driver",
which allows to boot XP there normal, it is called UEFI 2. May be this "driver" just frees or relocates memory <=1 MB.
UEFI 3 has nothing like this. So in Vista I think,
they solved the problem, putting this INT10 code in hal.dll and ntoskrnl.exe.
And now a strange situation happens: The Vista hal.dll and ntoskrnl.exe
with this INT10 simulator crashes together with XP files (in 64 bit. May be not in 32 bit.)
And the XP with INT10 call crashes, when there is no INT10 "driver" in Bios.
⇗ @Mov AX, 0xDEAD wrote, that videoprt.sys has exact this problem
with mapping memory. And you can see exact the place where this happens via Ida Pro.
I think, this INT10 "driver" can be done by hand
Dietmar

#2380 | lsmlcx | Does anyone have a hotfix for scsiport.sys? New version for scsiport.sys
#2381 | infuscomus | ⇗ @lsmlcx the most recent version of scsiport.sys I have is 5.1.2600.6073 I am not sure if it is the newest version
#2382 | lsmlcx | what is the hotfix number?
#2383 | infuscomus | ⇗ @lsmlcx i think it is KB2498072 ⇗ https://support.microsoft.com/en-au/help...iv2-0-for-windo

#2384

diderius6

Even Win7 has this problem with INT10 (Irq from Bios for the grafikcard)
and to boot from typ 3 UEFI Bios:
"Windows 7 Setup hangs at "Starting Windows" on Surface Pro
Applies to: Windows 7 EnterpriseWindows 7 Home PremiumWindows 7 Professional More
Symptoms
If you attempt to install 64-bit version of Windows 7 on a Surface Pro or other UEFI-based computer, the Setup may hang at "Starting Windows" screen and the Setup process may not complete.
Cause
The computer does not support legacy BIOS interrupt 10 (INT 10H).
Resolution
Check the BIOS settings to verify if the computer allows you to enable Compatibility Support Module (CSM) or legacy BIOS Interrupt 10 (INT 10H).
Contact the Original Equipment Manufacture (OEM) or hardware manufacture for additional information.
Note: If your computer does not support above mentioned options then you cannot run Windows 7 on the computer.
More Information
The Surface Pro is a Class 3 UEFI device that does not support legacy BIOS Interrupt 10 (INT 10H) video transitioning and it requires Windows 8 or later operating systems to run.
"
Dietmar
EDIT: Windows 8 works, because it uses GOP for video instead of INT10.
Any idea, how to overcome videoprt.sys and to make at once use of the Nvidia gop driver in XP?

#2385

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #2379

> The problem is not direct related to UEFI.
> It is how to manage INT10 call.
> Some UEFI Bios have an extra INT10 UEFI "driver",
> which allows to boot XP there normal, it is called UEFI 2. May be this "driver" just frees or relocates memory <=1 MB.
> ....
> @Mov AX, 0xDEAD wrote, that videoprt.sys has exact this problem
> with mapping memory. And you can see exact the place where this happens via Ida Pro.
> I think, this INT10 "driver" can be done by hand

Mapping memory is not related to int10 real mode handler.
First 1M RAM is mess of 1) Pure ram 00000-9ffff 2) Video ram a0000-bffff 3) Vga rom c0000-cfffff 4) acpi ram e0000-????? 5) shadow ram (chipset depends) 6) Bios rom f0000-fffff(???) . Videoport_x64 want to map all 1M to kernel space, technicaly this is not problem for CPU, MmMapIoSpace in theory create new GDT/LDT record to translate logical adresses->physical adresses and work is done. Problem starting when someone try to access this translated memory, BSOD inside MmMapIoSpace tell about some check/access to this memory before return to caller, this is strange why memory is accessed immediately after mapping.

## Page 160

#2386 | diderius6 | ⇗ @Mov AX, 0xDEAD "MmMapIoSpace tell about some check/access to this memory before return to caller" Is it possible to force (the user of this memory) to wait, until return is done Dietmar
#2387 | skullteria | Well, i read litle about GOP and Windows 7 seem support it. ⇗ https://www.youtube.com/watch?v=1Yyr1zuFiYk I think it is supported by dxgkrnl, Video Port for WDDM drivers. VideoPrt only support INT10, like bootvid. Because it on Video the boot animation is not displayed.
#2388 | skullteria | Well, we need run. ⇗ https://hothardware.com/news/intel-sunse...or-uefi-class-3 CSM support will end.
#2389 | diderius6 | ⇗ @skullteria May be it is possible, to integrate something like generic CSM in grub2 Dietmar
#2390 | skullteria | Well, i'm working to port WDDM drivers for XP/2003...And, to solve HalResetDisplay, for x64
#2391 | XPLives | Good luck.
#2392 | XPLives | UEFI
#2393 | skullteria | Well, what the isos of i have of Windows Vista, until build 5472, exist EFI files on x86

#2394

Gelip

@diderius

> Zitat von ⇗ diderius6 im Beitrag ¶ #2379

> The problem is not direct related to UEFI.
> It is how to manage INT10 call.
> Some UEFI Bios have an extra INT10 UEFI "driver"

Is this the INT10 driver in VMware? --> ¶ Windows XP SP3 32bit and modern PC parts (156)

> Zitat von ⇗ diderius6 im Beitrag ¶ #2387

> Even Win7 has this problem with INT10 (Irq from Bios for the grafikcard)
> and to boot from typ 3 UEFI Bios:

Yes, read this: ⇗ Install Windows 7 at UEFI Graphics Output Protocol (GOP) hardware
⇗ @infuscomus

> Zitat von ⇗ infuscomus im Beitrag ¶ #2374

> does Vista give same BSOD?

On ThinkPad X220 beta Longhorn Server 2008 6.0.6001.16497 (6.0.6001.16497.longhorn_beta3.070330-1720_amd64fre_server-serverstandard-serverenterprise-serverdatacenter_retail_en-us-KB3SxFRE_EN_DVD.iso) cannot be installed in legacy or UEFI because it is BSOD 7E. On VMware, however, it installs without a problem.

#2395 | infuscomus | ⇗ @Gelip do you know where I can download a copy of 6.0.6001.16497.longhorn_beta3.070330-1720_amd64fre_server-serverstandard-serverenterprise-serverdatacenter_retail_en-us-KB3SxFRE_EN_DVD.iso?
#2396 | infuscomus | just something i found interesting ⇗ https://askubuntu.com/questions/851892/a...to-an-uefi-grub apparently rEFInd boot manager can also boot a non-UEFI OS from UEFI mode
#2397 | Gelip | ⇗ @infuscomus On FTP betaarchive but you must be of the right rank to have access to FTP.
#2398 | infuscomus | ⇗ @Gelip Thanks, unfortunately, I don't have permission to access betaarchive FTP

#2399

diderius6

Does anybody have the version of
videoprt.sys from XP64 without SP2 (meaning I want to test each version of videoprt.sys 64 bit, old new just all)).
I read an interesting articel about stability of XP 64 SP2.
And one of the new files which gives BSODs
is the new videoprt.sys XP64 SP2
Dietmar

#2400

infuscomus

⇗ @diderius6
I might be wrong, but I believe that XP 64-bit only came into existence around the time SP2 came out and was forked from the server 2003 kernel
I think there is a server 2003 SP0 64-bit though.
EDIT:
5.2.3790.1830 - earliest 64bit videoprt.sys I can find.
infuscomus has attached files to this post

- ⇗ VIDEOPORT X64.zip

## Page 161

#2401 | infuscomus | i found useful polish ISO site ⇗ https://winiso.pl/windows-desktop/windows-xp I also found 5.2.3790.0 videoprt.sys but is IA64 architecture so not useful
#2402 | diderius6 | Hi, I am looking for the videoprt.sys from 64 bit beta of XP vers 1069 Dietmar
#2403 | diderius6 | ⇗ @skullteria Take a look at ⇗ http://x86asm.net/articles/calling-bios-...windows-xp-x64/ ⇗ http://www.alex-ionescu.com/publications/Recon/recon2012.pdf Dietmar

#2404

infuscomus

> Zitat von ⇗ diderius6 im Beitrag ¶ #2403

> @skullteria
> Take a look at
> ⇗ http://x86asm.net/articles/calling-bios-...windows-xp-x64/

this mentions VDM (i assume meaning NTVDM)
regarding this, someone made a 64-bit NTVDM on github
⇗ https://github.com/leecher1337/ntvdmx64

#2405 | diderius6 | ⇗ @infuscomus Do you know, how to install this in XP64 Dietmar
#2406 | infuscomus | ⇗ @diderius6 ⇗ https://github.com/leecher1337/ntvdmx64/...ster/readme.txt seems like it takes a few steps to compile OpenNT here ⇗ https://github.com/Paolo-Maffei/OpenNT

#2407

diderius6

Because I noticed, that some problems first time appear with videoprt.sys
from XP64 SP2, I am just making a new FAT32 install with XP64 SP1 5.2.3790.1830.
By the way I noticed, that in this XP version you have to update storport.sys (storport.sys 5.2.3790.4173 works)
or you will get message, that generic STORAHCI from ⇗ @skullteria fails
Dietmar

#2408

diderius6

I change vga.sys, videoprt.sys, ntoskrnl.exe, hal.dll
against XP 64 SP1 DEBUG version.
Now, the BSOD goes to vga.sys
Dietmar

    MODULE_NAME: vga

    FAULTING_MODULE: fffff80000c00000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  42435c56

    READ_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
     fffff800000c1743

    FAULTING_IP:
    hal!x86BiosExecuteInterrupt+95d
    fffff800`0136063d 0fb608          movzx   ecx,byte ptr [rax]

    MM_INTERNAL_CODE:  0

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0x50

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff80000c5c0c7 to fffff80000d9c2c0

    STACK_TEXT:
    fffffadc`c0376318
     fffff800`00c5c0c7 : 00000000`00000050 fffffadc`df66fbd0
    fffff800`000c1743 00000000`00000001 : nt!DbgBreakPointWithStatus
    fffffadc`c0376320
     fffff800`00c5d3d0 : fffff800`00000003 00000000`00000050
    fffff800`000c1743 00000000`00000000 : nt!KeWaitForSingleObject+0xf77
    fffffadc`c0376390
     fffff800`00d93144 : 00000002`00000050 fffff800`000c1743
    00000000`00000000 fffffadc`c0376b00 : nt!KeWaitForSingleObject+0x2280
    fffffadc`c03769d0
     fffff800`00d35fb1 : 00000000`00000050 fffff800`000c1743
    00000000`00000000 fffffadc`c0376b00 : nt!KeBugCheckEx+0x104
    fffffadc`c0376a10
     fffff800`00da1059 : 00000000`00000000 fffff800`000c1743
    fffffadc`df896700 fffffadc`c0376b00 : nt!NtFreeVirtualMemory+0x32ba1
    fffffadc`c0376b00
     fffff800`0136063d : fffffadc`bef4c000 fffffadc`df661743
    0000b86d`de7deaa1 00000000`00000000 : nt!longjmp+0x31f9
    fffffadc`c0376c90
     fffff800`01356b43 : fffff800`01374cd0 fffff800`00d6c000
    00000000`00001743 fffffadc`c0376d00 : hal!x86BiosExecuteInterrupt+0x95d
    fffffadc`c0376ce0
     fffffadc`bef46120 : fffffadc`00000010 fffffadc`c0376e30
    fffffadc`c0376e34 fffffadc`c0376e38 : hal!HalCallBios+0x133
    fffffadc`c0376d60
     fffffadc`bedb6798 : fffffadc`df5da620 fffffadc`c0376e30
    00000000`00000280 00000000`000001e0 : VIDEOPRT!VideoPortInt10+0x110
    fffffadc`c0376e00 fffffadc`bedb8f38 : fffffadc`df5da620 fffffadc`dfb7acb0 00000000`00000004 fffffadc`c0376ec4 : vga+0x5798
    fffffadc`c0376e90 fffffadc`bef542dc : fffffadc`df5da620 fffffadc`c0376fc0 00000000`00000000 00000000`00000000 : vga+0x7f38
    fffffadc`c0376f10
     fffff97f`ff086dee : fffffadc`df5da090 fffffadc`df896700
    fffffa80`0065f928 fffff97f`00000004 :
    VIDEOPRT!VideoPortCreateEvent+0xfec
    fffffadc`c0377040
    fffff97f`ff086cf1 : 00000000`0000019c 00000000`00000000
    00000000`00000000 00000000`00000001 : win32k!EngDeviceIoControl+0x12e
    fffffadc`c0377100
     fffff97f`ff485609 : 00000000`00000000 00000000`00000000
    00000000`0000009c fffff97f`ff0c76a9 : win32k!EngDeviceIoControl+0x31
    fffffadc`c0377150
     fffff97f`ff485304 : 00000000`00000010 00000000`00000000
    00000000`01050033 fffffa80`0065f8e0 : vga_fffff97fff483000+0x2609
    fffffadc`c0377220
     fffff97f`ff006579 : 000001e0`00000280 fffffa80`0067ec50
    00000000`00000000 fffffa80`0065f8e0 : vga_fffff97fff483000+0x2304
    fffffadc`c0377260
     fffff97f`ff0ad017 : fffffadc`c03772b0 fffffa80`006919e0
    fffffa80`0067f000 fffffa80`0067f000 : win32k!EngFreeModule+0x1a09
    fffffadc`c03772a0
     fffff97f`ff0086d1 : fffffa80`0067f000 00000000`000008b8
    fffffa80`002fb830 fffffa80`006919e0 : win32k!EngCreateDeviceSurface+0x57
    fffffadc`c03772f0
     fffff97f`ff0082f0 : fffffa80`0054e3e0 fffffa80`0067b890
    fffffa80`002fb830 00000000`00000001 : win32k!EngFreeModule+0x3b61
    fffffadc`c03773e0
     fffff97f`ff00b1bc : fffffadc`00000002 fffff97f`ff323fc0
    fffffadc`00000000 00000000`00000000 : win32k!EngFreeModule+0x3780
    fffffadc`c0377740
     fffff97f`ff00a01d : fffffadc`ffffffff ffffffff`80000054
    00000000`01bc8000 00000000`00000000 :
    win32k!EngFindImageProcAddress+0x19fc
    fffffadc`c0377970
    fffff97f`ff00ba85 : fffffa80`0059b460 00000000`00000000
    fffffadc`c0377a38 fffffadc`c0377a78 :
    win32k!EngFindImageProcAddress+0x85d
    fffffadc`c03779e0
    fffff97f`ff00b5d6 : 00000000`00000148 fffffadc`c0377cf0
    00000000`00000003 00000000`00000144 :
    win32k!EngFindImageProcAddress+0x22c5
    fffffadc`c0377c20
    fffff800`00da1f33 : 00000000`00000001 00000000`0015fa40
    fffffadc`df66fbd0 00000000`00000010 :
    win32k!EngFindImageProcAddress+0x1e16
    fffffadc`c0377c70
    000007ff`7c5fe85a : 000007ff`7c5fea99 00000000`001657f0
    00000000`001657f0 00000000`00000003 : nt!longjmp+0x40d3
    00000000`0015fbc8 000007ff`7c5fea99 : 00000000`001657f0 00000000`001657f0 00000000`00000003 00000000`00000000 : winsrv+0xe85a
    00000000`0015fbd0
     00000000`001657f0 : 00000000`001657f0 00000000`00000003
    00000000`00000000 00000000`00000000 :
    winsrv!UserServerDllInitialization+0x229
    00000000`0015fbd8 00000000`001657f0 : 00000000`00000003 00000000`00000000 00000000`00000000 00000000`00000003 : 0x1657f0
    00000000`0015fbe0 00000000`00000003 : 00000000`00000000 00000000`00000000 00000000`00000003 00000000`001657f0 : 0x1657f0
    00000000`0015fbe8 00000000`00000000 : 00000000`00000000 00000000`00000003 00000000`001657f0 00000000`78efa9be : 0x3

    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    vga+5798
    fffffadc`bedb6798 85c0            test    eax,eax

    SYMBOL_STACK_INDEX:  9

    SYMBOL_NAME:  vga+5798

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  vga.sys

    BUCKET_ID:  WRONG_SYMBOLS

    Followup: MachineOwner

#2409

diderius6

Next try, this time BSOD goes to bootvid.dll
Dietmar

    MODULE_NAME: BOOTVID

    FAULTING_MODULE: fffff80000c00000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  42438552

    READ_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
     fffff800000c1743

    FAULTING_IP:
    hal!x86BiosExecuteInterrupt+95d
    fffff800`0136063d 0fb608          movzx   ecx,byte ptr [rax]

    MM_INTERNAL_CODE:  0

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0x50

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff80000c5c0c7 to fffff80000d9c2c0

    STACK_TEXT:
    fffffadc`c0a07f68
     fffff800`00c5c0c7 : 00000000`00000050 fffffadc`e136c7b0
    fffff800`000c1743 00000000`00000001 : nt!DbgBreakPointWithStatus
    fffffadc`c0a07f70
     fffff800`00c5d3d0 : fffff800`00000003 00000000`00000050
    fffff800`000c1743 00000000`00000000 : nt!KeWaitForSingleObject+0xf77
    fffffadc`c0a07fe0
     fffff800`00d93144 : 00000000`00000050 fffff800`000c1743
    00000000`00000000 fffffadc`c0a08750 : nt!KeWaitForSingleObject+0x2280
    fffffadc`c0a08620
     fffff800`00d35fb1 : 00000000`00000050 fffff800`000c1743
    00000000`00000000 fffffadc`c0a08750 : nt!KeBugCheckEx+0x104
    fffffadc`c0a08660
     fffff800`00da1059 : 00000000`00000000 fffff800`000c1743
    00000000`00000800 fffffadc`c0a08750 : nt!NtFreeVirtualMemory+0x32ba1
    fffffadc`c0a08750
     fffff800`0136063d : 00000000`0000c000 00000000`00001743
    fffffadc`c5b4ff29 fffff800`0139cfe7 : nt!longjmp+0x31f9
    fffffadc`c0a088e0
     fffff800`013569e7 : fffff800`01374cd0 fffff800`014cc000
    00000000`00001743 fffffadc`c0a08950 : hal!x86BiosExecuteInterrupt+0x95d
    fffffadc`c0a08930
     fffffadc`c060c5ff : 00000000`000a0000 00000000`00020000
    fffffadc`00000000 fffffadc`c0a089c0 : hal!HalReadDmaCounter+0xb27
    fffffadc`c0a08980
     fffff800`012cf251 : fffff800`00437e01 fffff800`013177a0
    00000000`00000000 00002b99`2ddfa232 : BOOTVID!VidInitialize+0x18f
    fffffadc`c0a089f0
     fffff800`012d0756 : fffff800`004184f8 fffff800`00000012
    7ca976fb`74696e49 7ce936ab`a21f8b54 : nt!NlsMbOemCodePageTag+0x19181
    fffffadc`c0a08a40
     fffff800`01097b93 : fffff800`004184f8 f14d9291`54009847
    f1399211`d400d863 f16d9271`5440d823 : nt!NlsMbOemCodePageTag+0x1a686
    fffffadc`c0a08d40
     fffff800`0117059e : fffff800`004184f8 f93d8a25`5594d067
    c6292156`f7a54a4a 00000000`00000080 : nt!IoVerifyPartitionTable+0x33b3
    fffffadc`c0a08d70
     fffff800`00d9be76 : fffff800`01097b80 fffff800`004184f8
    fffff800`01170560 1f197401`ba303053 :
    nt!PsRemoveCreateThreadNotifyRoutine+0x7ae
    fffffadc`c0a08dd0
    00000000`00000000 : 00000000`00000000 00000000`00000000
    00000000`00000000 00000000`00000000 : nt!ZwUnloadKey+0x2ac6

    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    BOOTVID!VidInitialize+18f
    fffffadc`c060c5ff 84c0            test    al,al

    SYMBOL_STACK_INDEX:  8

    SYMBOL_NAME:  BOOTVID!VidInitialize+18f

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  BOOTVID.dll

    BUCKET_ID:  WRONG_SYMBOLS

    Followup: MachineOwner

---------
I succeed to overcome all BSODS, but now I have no screen^^.
This is on pur UEFI, CSM disabled, ultrafast start

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Opened \\.\com1
    Waiting to reconnect...
    Connected to Windows Server 2003 3790 x64 target at (Fri Sep 13 00:31:57.718 2019 (UTC + 2:00)), ptr64 TRUE
    Kernel Debugger connection established.
    WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
    Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
    *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
    Executable search path is: C:\localsymbols
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
    Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64
    Built by: 3790.srv03_sp1_rtm.050324-1447
    Machine Name:
    Kernel base = 0xfffff800`00c00000 PsLoadedModuleList = 0xfffff800`00dad0c0
    System Uptime: not available
    AhciHwFindAdapter finishing
    AhciHwFindAdapter finishing
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status e
    HAL: Interrupt emulation failed, status e
    HAL: Interrupt emulation failed, status e
    HAL: Interrupt emulation failed, status e
    HAL: Interrupt emulation failed, status e
    HAL: Interrupt emulation failed, status e
    ERROR: DavReadRegistryValues/RegQueryValueExW(6). WStatus = 1309
    Break instruction exception - code 80000003 (first chance)
    *******************************************************************************
    *                                                                             *
    *   You are seeing this message because you pressed either                    *
    *       CTRL+C (if you run kd.exe) or,                                        *
    *       CTRL+BREAK (if you run WinDBG),                                       *
    *   on your debugger machine's keyboard.                                      *
    *                                                                             *
    *                   THIS IS NOT A BUG OR A SYSTEM CRASH                       *
    *                                                                             *
    * If you did not intend to break into the debugger, press the "g" key, then   *
    * press the "Enter" key now.  This message might immediately reappear.  If it *
    * does, press "g" and "Enter" again.                                          *
    *                                                                             *
    *******************************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
    nt!DbgBreakPointWithStatus:
    fffff800`00c4b350 cc              int     3
    *** WARNING: Unable to verify timestamp for ntdll.dll
    *** ERROR: Module load completed but symbols could not be loaded for ntdll.dll
    9: kd> lm
    start             end                 module name
    00000000`78ec0000 00000000`78ff9000   ntdll    T (no symbols)
    fffff800`00c00000 fffff800`0106e000   nt         (export symbols)       ntkrnlmp.exe
    fffff800`0106e000 fffff800`010cc000   hal        (deferred)
    fffff97f`ff000000 fffff97f`ff45c000   win32k     (deferred)
    fffff97f`ff45c000 fffff97f`ff483000   dxg        (deferred)
    fffff97f`ff483000 fffff97f`ff48c000   TSDDD      (deferred)
    fffffadc`bdeb0000 fffffadc`bdf7a000   srv        (deferred)
    fffffadc`be092000 fffffadc`be122000   HTTP       (deferred)
    fffffadc`be2b2000 fffffadc`be2fb000   mrxdav     (deferred)
    fffffadc`be7ed000 fffffadc`be8b9000   mrxsmb     (deferred)
    fffffadc`be8b9000 fffffadc`be90a000   rdbss      (deferred)
    fffffadc`be90a000 fffffadc`be958000   afd        (deferred)
    fffffadc`be958000 fffffadc`be9bb000   netbt      (deferred)
    fffffadc`be9bb000 fffffadc`be9f3000   ipnat      (deferred)
    fffffadc`be9f3000 fffffadc`beab4000   tcpip      (deferred)
    fffffadc`beab4000 fffffadc`beadf000   ipsec      (deferred)
    fffffadc`beadf000 fffffadc`beaf3000   Npfs       (deferred)
    fffffadc`beb59000 fffffadc`beb6d000   NDProxy    (deferred)
    fffffadc`bec0d000 fffffadc`bec23000   termdd     (deferred)
    fffffadc`bec23000 fffffadc`bec79000   rdpdr      (deferred)
    fffffadc`bec79000 fffffadc`bec8f000   msgpc      (deferred)
    fffffadc`bec8f000 fffffadc`becaf000   psched     (deferred)
    fffffadc`becaf000 fffffadc`becd2000   raspptp    (deferred)
    fffffadc`becd2000 fffffadc`bece6000   raspppoe   (deferred)
    fffffadc`bece6000 fffffadc`bed12000   ndiswan    (deferred)
    fffffadc`bed12000 fffffadc`bed38000   rasl2tp    (deferred)
    fffffadc`bed38000 fffffadc`bed81000   ks         (deferred)
    fffffadc`bed81000 fffffadc`bed9e000   i8042prt   (deferred)
    fffffadc`bede4000 fffffadc`bee07000   VIDEOPRT   (deferred)
    fffffadc`bf5df000 fffffadc`bf5ec000   mssmbios   (deferred)
    fffffadc`bf5ef000 fffffadc`bf5fc000   mouclass   (deferred)
    fffffadc`bf5ff000 fffffadc`bf609000   ndistapi   (deferred)
    fffffadc`bf60f000 fffffadc`bf618000   watchdog   (deferred)
    fffffadc`bf61f000 fffffadc`bf629000   rasacd     (deferred)
    fffffadc`bf62f000 fffffadc`bf63f000   update     (deferred)
    fffffadc`bf63f000 fffffadc`bf64d000   kbdclass   (deferred)
    fffffadc`bf64f000 fffffadc`bf65c000   Msfs       (deferred)
    fffffadc`bf65f000 fffffadc`bf668000   wmiacpi    (deferred)
    fffffadc`bfc80000 fffffadc`bfcb6000   Mup        (deferred)
    fffffadc`bfcb6000 fffffadc`bfd11000   NDIS       (deferred)
    fffffadc`bfd11000 fffffadc`bfd44000   KSecDD     (deferred)
    fffffadc`bfd44000 fffffadc`bfd85000   Fastfat    (deferred)
    fffffadc`bfd85000 fffffadc`bfda8000   sr         (deferred)
    fffffadc`bfda8000 fffffadc`bfde5000   fltMgr     (deferred)
    fffffadc`bfde5000 fffffadc`bfe04000   CLASSPNP   (deferred)
    fffffadc`bfe04000 fffffadc`bfe19000   disk       (deferred)
    fffffadc`bfe19000 fffffadc`bfe7c000   storport   (deferred)
    fffffadc`bfe7c000 fffffadc`bfec7000   volsnap    (deferred)
    fffffadc`bfec7000 fffffadc`bff0d000   dmio       (deferred)
    fffffadc`bff0d000 fffffadc`bff4d000   ftdisk     (deferred)
    fffffadc`bff4d000 fffffadc`bff63000   MountMgr   (deferred)
    fffffadc`bff63000 fffffadc`bff84000   pci        (deferred)
    fffffadc`bff84000 fffffadc`bfff2000   ACPI       (deferred)
    fffffadc`c00f3000 fffffadc`c0105000   intelppm   (deferred)
    fffffadc`c0106000 fffffadc`c0118000   wanarp     (deferred)
    fffffadc`c0119000 fffffadc`c012b000   netbios    (deferred)
    fffffadc`c012c000 fffffadc`c013e000   Fips       (deferred)
    fffffadc`c03fb000 fffffadc`c0405000   kdcom      (deferred)
    fffffadc`c040b000 fffffadc`c0414000   BOOTVID    (deferred)
    fffffadc`c041b000 fffffadc`c0424000   WMILIB     (deferred)
    fffffadc`c042b000 fffffadc`c0434000   isapnp     (deferred)
    fffffadc`c043b000 fffffadc`c044b000   PartMgr    (deferred)
    fffffadc`c044b000 fffffadc`c0459000   storahci   (deferred)
    fffffadc`c045b000 fffffadc`c0466000   crcdisk    (deferred)
    fffffadc`c055b000 fffffadc`c0569000   vga        (deferred)
    fffffadc`c057b000 fffffadc`c058a000   TDI        (deferred)
    fffffadc`c059b000 fffffadc`c05a5000   mnmdd      (deferred)
    fffffadc`c05ab000 fffffadc`c05b7000   Dxapi      (deferred)
    fffffadc`c05db000 fffffadc`c05e6000   raspti     (deferred)
    fffffadc`c05eb000 fffffadc`c05f8000   ptilink    (deferred)
    fffffadc`c05fb000 fffffadc`c0605000   RDPCDD     (deferred)
    fffffadc`c064b000 fffffadc`c0655000   Fs_Rec     (deferred)
    fffffadc`c065b000 fffffadc`c0666000   ndisuio    (deferred)
    fffffadc`c066b000 fffffadc`c0673000   audstub    (deferred)
    fffffadc`c0673000 fffffadc`c067b000   Null       (deferred)
    fffffadc`c067b000 fffffadc`c0683000   CdaC15BA   (deferred)
    fffffadc`c0683000 fffffadc`c068b000   CdaD10BA   (deferred)
    fffffadc`c068b000 fffffadc`c0693000   secdrv     (deferred)
    fffffadc`c07fb000 fffffadc`c0802000   dmload     (deferred)
    fffffadc`c096e000 fffffadc`c0973e80   ksthunk    (deferred)
    fffffadc`c09ad000 fffffadc`c09b4000   Beep       (deferred)
    fffffadc`c0bb1000 fffffadc`c0bb2400   swenum     (deferred)

    Unloaded modules:
    fffffadc`be4a7000 fffffadc`be4e5000   HDAudBus.sys
    fffffadc`be4a7000 fffffadc`be4e5000   HDAudBus.sys
    fffffadc`c05bb000 fffffadc`c05c7000   dump_storport.sys
    fffffadc`be7af000 fffffadc`be7ed000   HDAudBus.sys
    fffffadc`be7af000 fffffadc`be7ed000   HDAudBus.sys
    fffffadc`be7d6000 fffffadc`be7ed000   imapi.sys
    fffffadc`be8f4000 fffffadc`be90a000   redbook.sys
    fffffadc`be8e7000 fffffadc`be90a000   serial.sys
    fffffadc`beaf8000 fffffadc`beb13000   cdrom.sys
    fffffadc`c054b000 fffffadc`c0554000   Sfloppy.SYS
    fffffadc`c060b000 fffffadc`c0617000   Flpydisk.SYS
    fffffadc`c063b000 fffffadc`c0649000   Fdc.SYS
    fffffadc`bead5000 fffffadc`beb13000   HDAudBus.sys
    fffffadc`bead5000 fffffadc`beb13000   HDAudBus.sys
    fffffadc`bead5000 fffffadc`beb13000   HDAudBus.sys
    fffffadc`bead5000 fffffadc`beb13000   HDAudBus.sys
    fffffadc`beb2f000 fffffadc`beb6d000   HDAudBus.sys
    fffffadc`beb2f000 fffffadc`beb6d000   HDAudBus.sys
    fffffadc`c056b000 fffffadc`c0576000   Vbemp.sys
    fffffadc`bed43000 fffffadc`bed81000   HDAudBus.sys
    fffffadc`bed60000 fffffadc`bed9e000   HDAudBus.sys
    9: kd> !devnode 0 1
    Error retrieving address of IopRootDeviceNode
    9: kd> g

#2410

Gelip

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #2399

> Does anybody have the version of videoprt.sys from XP64 without SP2

⇗ >link<

#2411

infuscomus

> Zitat von ⇗ diderius6 im Beitrag ¶ #2409

> Next try, this time BSOD goes to bootvid.dll
> I succeed to overcome all BSODS, but now I have no screen^^.
> This is on pur UEFI, CSM disabled, ultrafast start

are you able to remote desktop into it? or has it frozen?

#2412

skullteria

> Zitat von ⇗ diderius6 im Beitrag ¶ #2403

> Take a look at
> ⇗ http://x86asm.net/articles/calling-bios-...windows-xp-x64/
> ⇗ http://www.alex-ionescu.com/publications/Recon/recon2012.pdf

Thank you man. Well, i use/made a patch on winload based on PatchPae. Its disable digital signature verification. I think was made to x64 too, however, need make sure. It is importante for EFI too, we need search about it. And, i succeced install and boot Windows XP with Windows 7 setup engine. It need some patch on Windows partition, and patch winsetup.dll from dvd and boot.wim. I will attach here
EDIT by Fernando: Double post deleted and blank lines removed (to save space)

#2413 | skullteria | Well, i was thinking...The problem is of display is not really in UEFI. When you try load Windows XP x64 with Windows Vista winload, you will get a BSOD or computer restart. I think winload don't initialize or reset the display and ntldr made it. So, maybe we need focus on winload or try modifie WRK x64 (Windows Research Kernel) to reset display.

#2414

diderius6

⇗ @infuscomus
I can start XP64 SP1 with full UEFI 64 bit on asrock fatal1ty z370 gaming k6 board.
CSM is disabled, settings to ultrafast boot in Bios.
I hear the startsound from this XP.
But no screen, because hal.dll emulation of INT10 fails
Dietmar
PS: The Anapa driver makes the system hang. So I deleted it.
This boot of XP64 with sound and no screen is without the Anapa driver.

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Opened \\.\com1
    Waiting to reconnect...
    Connected to Windows Server 2003 3790 x64 target at (Fri Sep 13 19:11:51.828 2019 (UTC + 2:00)), ptr64 TRUE
    Kernel Debugger connection established.
    WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
    Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
    *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
    Executable search path is: C:\localsymbols
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
    Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64
    Built by: 3790.srv03_sp1_rtm.050324-1447
    Machine Name:
    Kernel base = 0xfffff800`00c00000 PsLoadedModuleList = 0xfffff800`00dad0c0
    System Uptime: not available
    AhciHwFindAdapter finishing
    AhciHwFindAdapter finishing
    KDTARGET: Refreshing KD connection
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status e
    HAL: Interrupt emulation failed, status e
    HAL: Interrupt emulation failed, status e
    HAL: Interrupt emulation failed, status e
    HAL: Interrupt emulation failed, status e
    HAL: Interrupt emulation failed, status e
    ERROR: DavReadRegistryValues/RegQueryValueExW(6). WStatus = 1309
    [alcwzrd]CheckRegKey = FALSE
    Break instruction exception - code 80000003 (first chance)
    *******************************************************************************
    *                                                                             *
    *   You are seeing this message because you pressed either                    *
    *       CTRL+C (if you run kd.exe) or,                                        *
    *       CTRL+BREAK (if you run WinDBG),                                       *
    *   on your debugger machine's keyboard.                                      *
    *                                                                             *
    *                   THIS IS NOT A BUG OR A SYSTEM CRASH                       *
    *                                                                             *
    * If you did not intend to break into the debugger, press the "g" key, then   *
    * press the "Enter" key now.  This message might immediately reappear.  If it *
    * does, press "g" and "Enter" again.                                          *
    *                                                                             *
    *******************************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
    nt!DbgBreakPointWithStatus:
    fffff800`00c4b350 cc              int     3
    *** WARNING: Unable to verify timestamp for ntdll.dll
    *** ERROR: Module load completed but symbols could not be loaded for ntdll.dll
    5: kd> lm
    start             end                 module name
    00000000`78ec0000 00000000`78ff9000   ntdll    T (no symbols)
    fffff800`00c00000 fffff800`0106e000   nt         (export symbols)       ntkrnlmp.exe
    fffff800`0106e000 fffff800`010cc000   hal        (deferred)
    fffff97f`ff000000 fffff97f`ff45c000   win32k     (deferred)
    fffff97f`ff45c000 fffff97f`ff483000   dxg        (deferred)
    fffff97f`ff483000 fffff97f`ff48c000   TSDDD      (deferred)
    fffffadc`bcb8f000 fffffadc`bcbc7000   kmixer     (deferred)
    fffffadc`bcc16000 fffffadc`bcc41000   sysaudio   (deferred)
    fffffadc`bcc41000 fffffadc`bcc75000   wdmaud     (deferred)
    fffffadc`bcf09000 fffffadc`bcfd3000   srv        (deferred)
    fffffadc`bd27b000 fffffadc`bd30b000   HTTP       (deferred)
    fffffadc`bd397000 fffffadc`bd3e0000   mrxdav     (deferred)
    fffffadc`bd9c2000 fffffadc`bda8e000   mrxsmb     (deferred)
    fffffadc`bda8e000 fffffadc`bdadf000   rdbss      (deferred)
    fffffadc`bdadf000 fffffadc`bdb2d000   afd        (deferred)
    fffffadc`bdb2d000 fffffadc`bdb90000   netbt      (deferred)
    fffffadc`bdb90000 fffffadc`bdbc8000   ipnat      (deferred)
    fffffadc`bdbc8000 fffffadc`bdc89000   tcpip      (deferred)
    fffffadc`bdc89000 fffffadc`bdcb4000   ipsec      (deferred)
    fffffadc`bdcb4000 fffffadc`bdcc8000   Npfs       (deferred)
    fffffadc`bdce8000 fffffadc`bdd0b000   VIDEOPRT   (deferred)
    fffffadc`be3df000 fffffadc`be41f000   portcls    (deferred)
    fffffadc`be41f000 fffffadc`bebac000   RTKHDA64   (deferred)
    fffffadc`bebf2000 fffffadc`bec06000   NDProxy    (deferred)
    fffffadc`bec06000 fffffadc`bec1c000   termdd     (deferred)
    fffffadc`bec1c000 fffffadc`bec72000   rdpdr      (deferred)
    fffffadc`bec72000 fffffadc`bec88000   msgpc      (deferred)
    fffffadc`bec88000 fffffadc`beca8000   psched     (deferred)
    fffffadc`beca8000 fffffadc`beccb000   raspptp    (deferred)
    fffffadc`beccb000 fffffadc`becdf000   raspppoe   (deferred)
    fffffadc`becdf000 fffffadc`bed0b000   ndiswan    (deferred)
    fffffadc`bed0b000 fffffadc`bed31000   rasl2tp    (deferred)
    fffffadc`bed31000 fffffadc`bed7a000   ks         (deferred)
    fffffadc`bedac000 fffffadc`bedc9000   i8042prt   (deferred)
    fffffadc`bedc9000 fffffadc`bee07000   HDAudBus   (deferred)
    fffffadc`bf5df000 fffffadc`bf5ec000   Msfs       (deferred)
    fffffadc`bf5ff000 fffffadc`bf60a000   ndisuio    (deferred)
    fffffadc`bf60f000 fffffadc`bf61b000   Dxapi      (deferred)
    fffffadc`bf62f000 fffffadc`bf63c000   mouclass   (deferred)
    fffffadc`bf65f000 fffffadc`bf669000   Fs_Rec     (deferred)
    fffffadc`bfc80000 fffffadc`bfcb6000   Mup        (deferred)
    fffffadc`bfcb6000 fffffadc`bfd11000   NDIS       (deferred)
    fffffadc`bfd11000 fffffadc`bfd44000   KSecDD     (deferred)
    fffffadc`bfd44000 fffffadc`bfd85000   Fastfat    (deferred)
    fffffadc`bfd85000 fffffadc`bfda8000   sr         (deferred)
    fffffadc`bfda8000 fffffadc`bfde5000   fltMgr     (deferred)
    fffffadc`bfde5000 fffffadc`bfe04000   CLASSPNP   (deferred)
    fffffadc`bfe04000 fffffadc`bfe19000   disk       (deferred)
    fffffadc`bfe19000 fffffadc`bfe7c000   storport   (deferred)
    fffffadc`bfe7c000 fffffadc`bfec7000   volsnap    (deferred)
    fffffadc`bfec7000 fffffadc`bff0d000   dmio       (deferred)
    fffffadc`bff0d000 fffffadc`bff4d000   ftdisk     (deferred)
    fffffadc`bff4d000 fffffadc`bff63000   MountMgr   (deferred)
    fffffadc`bff63000 fffffadc`bff84000   pci        (deferred)
    fffffadc`bff84000 fffffadc`bfff2000   ACPI       (deferred)
    fffffadc`c00f3000 fffffadc`c0105000   intelppm   (deferred)
    fffffadc`c0106000 fffffadc`c0118000   wanarp     (deferred)
    fffffadc`c0119000 fffffadc`c012b000   netbios    (deferred)
    fffffadc`c012c000 fffffadc`c013e000   Fips       (deferred)
    fffffadc`c03fb000 fffffadc`c0405000   kdcom      (deferred)
    fffffadc`c040b000 fffffadc`c0414000   BOOTVID    (deferred)
    fffffadc`c041b000 fffffadc`c0424000   WMILIB     (deferred)
    fffffadc`c042b000 fffffadc`c0434000   isapnp     (deferred)
    fffffadc`c043b000 fffffadc`c044b000   PartMgr    (deferred)
    fffffadc`c044b000 fffffadc`c0459000   storahci   (deferred)
    fffffadc`c045b000 fffffadc`c0466000   crcdisk    (deferred)
    fffffadc`c051b000 fffffadc`c0528000   ptilink    (deferred)
    fffffadc`c055b000 fffffadc`c0565000   rasacd     (deferred)
    fffffadc`c057b000 fffffadc`c0585000   mnmdd      (deferred)
    fffffadc`c059b000 fffffadc`c05a5000   RDPCDD     (deferred)
    fffffadc`c05ab000 fffffadc`c05ba000   TDI        (deferred)
    fffffadc`c05bb000 fffffadc`c05c9000   kbdclass   (deferred)
    fffffadc`c05cb000 fffffadc`c05d8000   mssmbios   (deferred)
    fffffadc`c05db000 fffffadc`c05e6000   raspti     (deferred)
    fffffadc`c060b000 fffffadc`c0615000   ndistapi   (deferred)
    fffffadc`c061b000 fffffadc`c0624000   watchdog   (deferred)
    fffffadc`c062b000 fffffadc`c0634000   wmiacpi    (deferred)
    fffffadc`c063b000 fffffadc`c064b000   update     (deferred)
    fffffadc`c065b000 fffffadc`c0669000   vga        (deferred)
    fffffadc`c066b000 fffffadc`c0673000   audstub    (deferred)
    fffffadc`c0673000 fffffadc`c067b000   Null       (deferred)
    fffffadc`c067b000 fffffadc`c0683000   CdaC15BA   (deferred)
    fffffadc`c0683000 fffffadc`c068b000   CdaD10BA   (deferred)
    fffffadc`c068b000 fffffadc`c0693000   secdrv     (deferred)
    fffffadc`c07fb000 fffffadc`c0802000   dmload     (deferred)
    fffffadc`c096e000 fffffadc`c0973e80   ksthunk    (deferred)
    fffffadc`c09ec000 fffffadc`c09f3000   Beep       (deferred)
    fffffadc`c0b37000 fffffadc`c0b39800   splitter   (deferred)
    fffffadc`c0bb1000 fffffadc`c0bb2400   swenum     (deferred)

    Unloaded modules:
    fffffadc`bcbc7000 fffffadc`bcbe1000   swmidi.sys
    fffffadc`bcbe1000 fffffadc`bcc16000   aec.sys
    fffffadc`c0bd7000 fffffadc`c0bd9000   MSPCLOCK.sys
    fffffadc`c0acf000 fffffadc`c0ad2000   MSKSSRV.sys
    fffffadc`c0bdf000 fffffadc`c0be1000   MSPQM.sys
    fffffadc`c054b000 fffffadc`c0557000   dump_storport.sys
    fffffadc`bd9ab000 fffffadc`bd9c2000   imapi.sys
    fffffadc`bdac9000 fffffadc`bdadf000   redbook.sys
    fffffadc`bdabc000 fffffadc`bdadf000   serial.sys
    fffffadc`bdd36000 fffffadc`bdd51000   cdrom.sys
    fffffadc`c058b000 fffffadc`c0594000   Sfloppy.SYS
    fffffadc`bf64f000 fffffadc`bf65b000   Flpydisk.SYS
    fffffadc`bf61f000 fffffadc`bf62d000   Fdc.SYS

#2415 | infuscomus | ⇗ @diderius6 using a second computer are you able to remote desktop on to it? to bypass the failed display driver.

## Page 162

#2416 | diderius6 | ⇗ @infuscomus I did it on the compi itself, until now I do not test remote boot Dietmar
#2417 | infuscomus | ⇗ @diderius6 it would seem like it is only the display is not working but the rest of the system is fine, that's why I suggested using remote desktop to confirm this is the case.
#2418 | infuscomus | ⇗ @diderius6 if you don't mind, could you make a backup HDD image of your UEFI bootable XP64? I would like to test it for myself. I will PM you my Backup/Recovery media ISO I use.

#2419

diderius6

⇗ @infuscomus
I can also make a pur copy for you
from the harddisk, first partition with MBR.
This you can copy with Hexeditor bit by bit
to an harddisk and it will work
Dietmar

#2420 | infuscomus | ⇗ @diderius6 entire harddisk preferably, so I don't need to reinstall the OS everytime, just restore the image

#2421

diderius6

⇗ @infuscomus
Nice Tool and very fast. But size even with *.rar it is still 2 Gbyte,
I am uploading
Dietmar
PS: It is only one partition FAT32 (for UEFI) with MBR
and with crazy timer hacked hal.dll and sound and Moorhuhn), thanks to ⇗ @Mov AX, 0xDEAD
You can boot this XP64 normal and via UEFI, select via Bootmenu. And for UEFI
you always have to disable driver integry check in boot menu.
I use STORAHCI and last acpi.sys so it should work on any compi.

#2422 | skullteria | Hey diderius6, you could make a test load Windows XP x64 with winload.exe instead winload.efi and see results

#2423

diderius6

⇗ @skullteria
From this version 6.0.6001.16497 I do not have winload.exe.
And I do not know, how I should edit BCD,
that it now uses winload.exe.
I am on a Fat32 partition with MBR
Dietmar
PS: May be, that the problems with INT10 come from winload.exe.
We should test also winload.exe from Win8.

#2424

Gelip

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #2423

> And I do not know, how I should edit BCD,
> that it now uses winload.exe

You edit BCD in BOOTICE in Professional mode - change path winload.efi to winload.exe:
⇗

#2425

skullteria

Hey, to disable Signature check, need patch ImgpValidateImageHash function inside winload.exe. For me, work these lines:
Original: 8B C8 85 C9 89 4D 08 7D
Replace: C7 45 08 00 00 00 00 EB
x64(maybe)
Original: 45 33 db 41 3b c3 8b d8
Replace: C7 45 08 00 00 00 00 EB
Tested on Vista SP2 winload

#2426

Gelip

> Zitat von ⇗ skullteria im Beitrag ¶ #2425

> Hey, to disable Signature check, need patch ImgpValidateImageHash function inside winload.exe. For me, work these lines:
> Original: 8B C8 85 C9 89 4D 08 7D
> Replace: C7 45 08 00 00 00 00 EB
> x64(maybe)
> Original: 45 33 db 41 3b c3 8b d8
> Replace: C7 45 08 00 00 00 00 EB
> Tested on Vista SP2 winload

I checked it in 64-bit winload.efi from beta server 16497. Such a HEX string exists but after changing the value I have a checksum error at system startup:
⇗

#2427 | Gelip | ⇗ @skullteria Maybe it will help:⇗ completely disable all checksum verifications during bootup

#2428

skullteria

> Zitat von ⇗ Gelip im Beitrag ¶ #2426

> > Zitat von ⇗ skullteria im Beitrag ¶ #2425

> > Hey, to disable Signature check, need patch ImgpValidateImageHash function inside winload.exe. For me, work these lines:
> > Original: 8B C8 85 C9 89 4D 08 7D
> > Replace: C7 45 08 00 00 00 00 EB
> > x64(maybe)
> > Original: 45 33 db 41 3b c3 8b d8
> > Replace: C7 45 08 00 00 00 00 EB
> > Tested on Vista SP2 winload

> I checked it in 64-bit winload.efi from beta server 16497. Such a HEX string exists but after changing the value I have a checksum error at system startup:
> ⇗

You need update checksum with pe.exe, with command: pe -c winload.exe
Well, my patch for x64 is not working. This corrupt winload.exe
EDIT: i think i found a way: I read forum about how change Windows 7 boot screen, and in this page: ⇗ https://www.sevenforums.com/customizatio...ows-7-a-12.html
on post number 118, the user thaimin talk about certificates what are verified on boot. So, i copied windows-legacy-whql.cat to WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} and
CodeIntegrity to Windows\System32 and voila: not error with Winload from Vista until Build 6000. I get error with build 6002. Works both x86 and x64. Winload from Vista SP2 (6002) not work on x64 (vmware)
Only thing: kernel component must be signed. Windows are signature on all binaries, even Windows XP;

#2429

Gelip

> Zitat von ⇗ skullteria im Beitrag ¶ #2428

> So, i copied windows-legacy-whql.cat to WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} and
> CodeIntegrity to Windows\System32 and voila: not error with Winload from Vista until Build 6000. I get error with build 6002. Works both x86 and x64. Winload from Vista SP2 (6002) not work on x64 (vmware)

Yeah, I know about it: ⇗ Beta 2 Longhorn Vista 6.0.5384.4 (last Vista Beta2 which support Boot.ini)
In beta Longhorn Server 2008 16497 this not work - ⇗ So I started to test EFI files from versions Windows Server 2008 Longhorn on WinXP x64 on X220 and:
6001.16406 - last version which causes white bar
6001.16497 - first version which causes ntoskrnl.exe 0xc0000428 Windows cannot verify the digital signature for this file

#2430

Gelip

I have idea!
The ThinkPad X220 laptop has VBIOS 2089 SandyBridge-Mobile and on it WinXP x64 boots with the AnaPa driver under UEFI.
ASUS P8H61 M LE R2 (bios 1408) has VBIOS 2143 SandyBridge/IvyBridge-Desktop and on it WinXP x64 does not start from AnaPa.
I came up with the idea to downgrade ASUS VBIOS to 2089 version.
Maybe this will solve the problem with running WinXP x64 under UEFI ???
or
In Intel BMP you can change various VBIOS settings - maybe you need to change something for WinXP x64 to start under UEFI?

## Page 163

#2431

diderius6

With the german version of real Windows 2003 R2 server64 bit 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
now I come exact to the same place as with XP 64 SP1 5.2.3790.1830 (srv03_sp1_rtm.050324-1447) for UEFI boot on
the asrock fatal1ty z370 gaming k6 board.
I can boot full UEFI with CSM disabled.
But because the ANAPA driver hangs (code 10), no screen.
I can hear the sound of this Win Server 2003 R2 after UEFI boot.
Crazy job to find the right time to hit strg alt del and then hit enter with no screen^^.
No BSOD before about videoprt.sys.
I compare videoprt.sys from XP 64 SP2 with this version.
They are different
Dietmar

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Opened \\.\com1
    Waiting to reconnect...
    Connected to Windows Server 2003 3790 x64 target at (Sat Sep 14 20:42:32.671 2019 (UTC + 2:00)), ptr64 TRUE
    Kernel Debugger connection established.
    WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
    Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
    *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
    Executable search path is: C:\localsymbols
    Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64
    Built by: 3790.srv03_sp2_rtm.070216-1710
    Machine Name:
    Kernel base = 0xfffff800`00c00000 PsLoadedModuleList = 0xfffff800`00dd5100
    System Uptime: not available
    HAL: Interrupt emulation failed, status c
    AhciHwFindAdapter finishing
    AhciHwFindAdapter finishing
    KDTARGET: Refreshing KD connection
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    HAL: Interrupt emulation failed, status c
    AFD: AfdPprThreshold value queried from transport: 2960
    Break instruction exception - code 80000003 (first chance)
    *******************************************************************************
    *                                                                             *
    *   You are seeing this message because you pressed either                    *
    *       CTRL+C (if you run kd.exe) or,                                        *
    *       CTRL+BREAK (if you run WinDBG),                                       *
    *   on your debugger machine's keyboard.                                      *
    *                                                                             *
    *                   THIS IS NOT A BUG OR A SYSTEM CRASH                       *
    *                                                                             *
    * If you did not intend to break into the debugger, press the "g" key, then   *
    * press the "Enter" key now.  This message might immediately reappear.  If it *
    * does, press "g" and "Enter" again.                                          *
    *                                                                             *
    *******************************************************************************
    nt!DbgBreakPointWithStatus:
    fffff800`00c26db0 cc              int     3
    11: kd> lm
    start             end                 module name
    00000000`78eb0000
     00000000`78fef000   ntdll      (pdb symbols)
    c:\symbols\ntdll.pdb\B2BE918952834AB8BAA710708C00CC7C2\ntdll.pdb
    fffff800`00c00000
     fffff800`01091000   nt         (pdb symbols)
    c:\symbols\ntkrnlmp.pdb\3B7C35F2F8624C78898D609597BB1C772\ntkrnlmp.pdb
    fffff800`01091000 fffff800`010ef000   hal        (deferred)
    fffff97f`ff000000 fffff97f`ff45f000   win32k     (deferred)
    fffff97f`ff45f000 fffff97f`ff487000   dxg        (deferred)
    fffff97f`ff487000 fffff97f`ff490000   TSDDD      (deferred)
    fffffadc`bc3be000 fffffadc`bc482000   srv        (deferred)
    fffffadc`bcba4000 fffffadc`bcc71000   mrxsmb     (deferred)
    fffffadc`bcc71000 fffffadc`bccc2000   rdbss      (deferred)
    fffffadc`bccc2000 fffffadc`bcd0f000   afd        (deferred)
    fffffadc`bcd0f000 fffffadc`bcd69000   netbt      (deferred)
    fffffadc`bcd69000 fffffadc`bcda7000   ipnat      (deferred)
    fffffadc`bcda7000 fffffadc`bce9c000   tcpip      (deferred)
    fffffadc`bce9c000 fffffadc`bceb2000   msgpc      (deferred)
    fffffadc`bceb2000 fffffadc`bcedd000   ipsec      (deferred)
    fffffadc`bcedd000 fffffadc`bcef1000   Npfs       (deferred)
    fffffadc`bd58b000 fffffadc`bd5cb000   portcls    (deferred)
    fffffadc`bd5cb000 fffffadc`bdd58000   RTKHDA64   (deferred)
    fffffadc`bdd58000 fffffadc`bdd6c000   NDProxy    (deferred)
    fffffadc`bdd6c000 fffffadc`bdd87000   update     (deferred)
    fffffadc`bdd87000 fffffadc`bdd9d000   termdd     (deferred)
    fffffadc`bdde3000 fffffadc`bde3a000   rdpdr      (deferred)
    fffffadc`bde3a000 fffffadc`bde5d000   raspptp    (deferred)
    fffffadc`bde5d000 fffffadc`bde71000   raspppoe   (deferred)
    fffffadc`bde71000 fffffadc`bde9d000   ndiswan    (deferred)
    fffffadc`bde9d000 fffffadc`bdec3000   rasl2tp    (deferred)
    fffffadc`bdec3000 fffffadc`bdf0c000   ks         (deferred)
    fffffadc`bdf34000 fffffadc`bdf51000   i8042prt   (deferred)
    fffffadc`bdf51000 fffffadc`bdf8f000   HDAudBus   (deferred)
    fffffadc`be6c5000 fffffadc`be6cf000   mnmdd      (deferred)
    fffffadc`be6e5000 fffffadc`be6f2000   mouclass   (deferred)
    fffffadc`be7f7000 fffffadc`be800000   wmiacpi    (deferred)
    fffffadc`be837000 fffffadc`be844000   ptilink    (deferred)
    fffffadc`be857000 fffffadc`be862000   raspti     (deferred)
    fffffadc`be887000 fffffadc`be893000   Dxapi      (deferred)
    fffffadc`beea8000 fffffadc`beedc000   Mup        (deferred)
    fffffadc`beedc000 fffffadc`bef42000   NDIS       (deferred)
    fffffadc`bef42000 fffffadc`bef65000   VIDEOPRT   (deferred)
    fffffadc`bef65000 fffffadc`bef99000   KSecDD     (deferred)
    fffffadc`bef99000 fffffadc`befda000   Fastfat    (deferred)
    fffffadc`befda000 fffffadc`bf018000   fltMgr     (deferred)
    fffffadc`bf018000 fffffadc`bf035000   CLASSPNP   (deferred)
    fffffadc`bf035000 fffffadc`bf04a000   disk       (deferred)
    fffffadc`bf04a000 fffffadc`bf07a000   storport   (deferred)
    fffffadc`bf07a000 fffffadc`bf0c6000   volsnap    (deferred)
    fffffadc`bf0c6000 fffffadc`bf10d000   dmio       (deferred)
    fffffadc`bf10d000 fffffadc`bf14d000   ftdisk     (deferred)
    fffffadc`bf14d000 fffffadc`bf163000   MountMgr   (deferred)
    fffffadc`bf163000 fffffadc`bf184000   pci        (deferred)
    fffffadc`bf184000 fffffadc`bf1f2000   ACPI       (deferred)
    fffffadc`bf2f3000 fffffadc`bf304000   Dfs        (deferred)
    fffffadc`bf306000 fffffadc`bf319000   intelppm   (deferred)
    fffffadc`bf319000 fffffadc`bf32b000   wanarp     (deferred)
    fffffadc`bf32c000 fffffadc`bf33e000   netbios    (deferred)
    fffffadc`bf33f000 fffffadc`bf351000   Fips       (deferred)
    fffffadc`bf5fb000 fffffadc`bf605000   kdcom      (deferred)
    fffffadc`bf60b000 fffffadc`bf614000   BOOTVID    (deferred)
    fffffadc`bf61b000 fffffadc`bf624000   WMILIB     (deferred)
    fffffadc`bf62b000 fffffadc`bf634000   isapnp     (deferred)
    fffffadc`bf63b000 fffffadc`bf64b000   PartMgr    (deferred)
    fffffadc`bf64b000 fffffadc`bf659000   storahci   (deferred)
    fffffadc`bf65b000 fffffadc`bf666000   Vbemp      (deferred)
    fffffadc`bf66b000 fffffadc`bf674000   watchdog   (deferred)
    fffffadc`bf67b000 fffffadc`bf686000   crcdisk    (deferred)
    fffffadc`bf73b000 fffffadc`bf74a000   TDI        (deferred)
    fffffadc`bf75b000 fffffadc`bf769000   vga        (deferred)
    fffffadc`bf77b000 fffffadc`bf785000   rasacd     (deferred)
    fffffadc`bf79b000 fffffadc`bf7a8000   mssmbios   (deferred)
    fffffadc`bf7bb000 fffffadc`bf7c5000   RDPCDD     (deferred)
    fffffadc`bf7db000 fffffadc`bf7e7000   ndisuio    (deferred)
    fffffadc`bf7eb000 fffffadc`bf7f5000   Fs_Rec     (deferred)
    fffffadc`bf80b000 fffffadc`bf815000   ndistapi   (deferred)
    fffffadc`bf81b000 fffffadc`bf828000   Msfs       (deferred)
    fffffadc`bf83b000 fffffadc`bf849000   kbdclass   (deferred)
    fffffadc`bf86b000 fffffadc`bf873000   audstub    (deferred)
    fffffadc`bf873000 fffffadc`bf87b000   Null       (deferred)
    fffffadc`bf87b000 fffffadc`bf883000   CdaC15BA   (deferred)
    fffffadc`bf883000 fffffadc`bf88b000   CdaD10BA   (deferred)
    fffffadc`bf88b000 fffffadc`bf893000   secdrv     (deferred)
    fffffadc`bf9fb000 fffffadc`bfa02000   dmload     (deferred)
    fffffadc`bfb98000 fffffadc`bfb9de80   ksthunk    (deferred)
    fffffadc`bfc32000 fffffadc`bfc39000   Beep       (deferred)
    fffffadc`bfdb5000 fffffadc`bfdb6400   swenum     (deferred)

    Unloaded modules:
    fffffadc`be695000 fffffadc`be6a1000   dump_storport.sys
    fffffadc`bcb8d000 fffffadc`bcba4000   imapi.sys
    fffffadc`bccac000 fffffadc`bccc2000   redbook.sys
    fffffadc`bcc9f000 fffffadc`bccc2000   serial.sys
    fffffadc`bcf3c000 fffffadc`bcf57000   cdrom.sys
    fffffadc`be6a5000 fffffadc`be6ae000   Sfloppy.SYS
    fffffadc`bf84b000 fffffadc`bf857000   Flpydisk.SYS
    fffffadc`be867000 fffffadc`be875000   Fdc.SYS
    fffffadc`bf65b000 fffffadc`bf666000   Vbemp.sys

    11: kd> !devnode 0 1
    Dumping IopRootDeviceNode (= 0xfffffadce0a9d7c0)
    DevNode 0xfffffadce0a9d7c0 for PDO 0xfffffadce1f047d0
      InstancePath is "HTREE\ROOT\0"
      State = DeviceNodeStarted (0x308)
      Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a9cc30 for PDO 0xfffffadce0a9ce50
        InstancePath is "Root\ACPI_HAL\0000"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
        DevNode 0xfffffadce0a96490 for PDO 0xfffffadce1efc060
          InstancePath is "ACPI_HAL\PNP0C08\0"
          ServiceName is "ACPI"
          State = DeviceNodeStarted (0x308)
          Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadce084e010 for PDO 0xfffffadce0966060
            InstancePath is "ACPI\PNP0A08\0"
            ServiceName is "pci"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadce23da440 for PDO 0xfffffadcdfa48d40
              InstancePath is "PCI\VEN_8086&DEV_3EC2&SUBSYS_00000000&REV_07\3&11583659&0&00"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadce23da270 for PDO 0xfffffadcdfa48560
              InstancePath is "PCI\VEN_8086&DEV_1901&SUBSYS_00000000&REV_07\3&11583659&0&08"
              ServiceName is "pci"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0xfffffadce07ca800 for PDO 0xfffffadce07ca060
                InstancePath is "PCI\VEN_10DE&DEV_13C0&SUBSYS_13C010DE&REV_A1\4&17bc2637&0&0008"
                ServiceName is "Vbemp"
                State = DeviceNodeRemoved (0x312)
                Previous State = DeviceNodeStartCompletion (0x306)
                Problem = CM_PROB_FAILED_START
                Failure Status 0000000000

              DevNode 0xfffffadce07ca630 for PDO 0xfffffadce07cad40
                InstancePath is "PCI\VEN_10DE&DEV_0FBB&SUBSYS_13C010DE&REV_A1\4&17bc2637&0&0108"
                ServiceName is "HDAudBus"
                State = DeviceNodeStarted (0x308)
                Previous State = DeviceNodeEnumerateCompletion (0x30d)
                DevNode 0xfffffadce0688c50 for PDO 0xfffffadcdf954d20

                  InstancePath is
    "HDAUDIO\FUNC_01&VEN_10DE&DEV_0071&SUBSYS_10DE13C0&REV_1001\5&2222d42c&0&0001"
                  State = DeviceNodeInitialized (0x302)
                  Previous State = DeviceNodeUninitialized (0x301)
                  Problem = CM_PROB_DISABLED
            DevNode 0xfffffadce0962010 for PDO 0xfffffadce0629ad0
              InstancePath is "PCI\VEN_8086&DEV_A2AF&SUBSYS_A2AF1849&REV_00\3&11583659&0&A0"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
              Problem = CM_PROB_DISABLED
            DevNode 0xfffffadce0962e40 for PDO 0xfffffadce0615650
              InstancePath is "PCI\VEN_8086&DEV_A2B1&SUBSYS_A2B11849&REV_00\3&11583659&0&A2"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
              Problem = CM_PROB_DISABLED
            DevNode 0xfffffadce0962c70 for PDO 0xfffffadce0966a80
              InstancePath is "PCI\VEN_8086&DEV_A2BA&SUBSYS_A2BA1849&REV_00\3&11583659&0&B0"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
              Problem = CM_PROB_DISABLED
            DevNode 0xfffffadce0962aa0 for PDO 0xfffffadce0966760
              InstancePath is "PCI\VEN_8086&DEV_A282&SUBSYS_A2821849&REV_00\3&11583659&0&B8"
              ServiceName is "storahci"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0xfffffadce0991360 for PDO 0xfffffadcdfa68a20
                InstancePath is "SCSI\Disk&Ven_WDC&Prod_WD2003FZEX-00SRL&Rev_01.0\4&3543605e&0&010000"
                ServiceName is "disk"
                State = DeviceNodeStarted (0x308)
                Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadce09628d0 for PDO 0xfffffadce0966440
              InstancePath is "PCI\VEN_8086&DEV_A2E7&SUBSYS_00000000&REV_F0\3&11583659&0&D8"
              ServiceName is "pci"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadce0962700 for PDO 0xfffffadce095f060
              InstancePath is "PCI\VEN_8086&DEV_A290&SUBSYS_00000000&REV_F0\3&11583659&0&E0"
              ServiceName is "pci"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadce0962530 for PDO 0xfffffadce095fb70
              InstancePath is "PCI\VEN_8086&DEV_A291&SUBSYS_00000000&REV_F0\3&11583659&0&E1"
              ServiceName is "pci"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0xfffffadce05f8010 for PDO 0xfffffadcdfa37970
                InstancePath is "PCI\VEN_1B21&DEV_0612&SUBSYS_06121849&REV_02\4&12e73dd2&0&00E1"
                ServiceName is "storahci"
                State = DeviceNodeStarted (0x308)
                Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadce0962360 for PDO 0xfffffadce095f850
              InstancePath is "PCI\VEN_8086&DEV_A292&SUBSYS_00000000&REV_F0\3&11583659&0&E2"
              ServiceName is "pci"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0xfffffadcdfa37c40 for PDO 0xfffffadce0709450
                InstancePath is "PCI\VEN_8086&DEV_1539&SUBSYS_15391849&REV_03\4&2880aa1&0&00E2"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_DISABLED
            DevNode 0xfffffadce0963010 for PDO 0xfffffadce095f530
              InstancePath is "PCI\VEN_8086&DEV_A294&SUBSYS_00000000&REV_F0\3&11583659&0&E4"
              ServiceName is "pci"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0xfffffadce0709720 for PDO 0xfffffadce0709060
                InstancePath is "PCI\VEN_1B21&DEV_2142&SUBSYS_21421849&REV_00\4&1fc90664&0&00E4"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
                Problem = CM_PROB_DISABLED
            DevNode 0xfffffadce0963e40 for PDO 0xfffffadce0964d40
              InstancePath is "PCI\VEN_8086&DEV_A298&SUBSYS_00000000&REV_F0\3&11583659&0&E8"
              ServiceName is "pci"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadce0963c70 for PDO 0xfffffadce0964a20
              InstancePath is "PCI\VEN_8086&DEV_A2C9&SUBSYS_00000000&REV_00\3&11583659&0&F8"
              ServiceName is "isapnp"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0xfffffadce05f8200 for PDO 0xfffffadce05f8a20
                InstancePath is "ACPI\PNP0C02\0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
              DevNode 0xfffffadce084b010 for PDO 0xfffffadce05f8820
                InstancePath is "ACPI\PNP0303\0"
                ServiceName is "i8042prt"
                TargetDeviceNotify List - f 0xfffffa8000633370  b 0xfffffa8000633370
                State = DeviceNodeStarted (0x308)
                Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0xfffffadce084be40 for PDO 0xfffffadce05f8620
                InstancePath is "ACPI\PNP0F03\0"
                ServiceName is "i8042prt"
                TargetDeviceNotify List - f 0xfffffa80007ceaf0  b 0xfffffa80007ceaf0
                State = DeviceNodeStarted (0x308)
                Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0xfffffadce084bc70 for PDO 0xfffffadce05f8420
                InstancePath is "ACPI\INT0800\4&e69c0be&0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
              DevNode 0xfffffadce084baa0 for PDO 0xfffffadcdfb88060
                InstancePath is "ACPI\PNP0103\0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
              DevNode 0xfffffadce084b8d0 for PDO 0xfffffadcdfb88e60
                InstancePath is "ACPI\PNP0000\4&e69c0be&0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
              DevNode 0xfffffadce084b700 for PDO 0xfffffadcdfb88c60
                InstancePath is "ACPI\PNP0C04\4&e69c0be&0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
              DevNode 0xfffffadce084b530 for PDO 0xfffffadcdfb88a60
                InstancePath is "ACPI\PNP0C02\2"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
              DevNode 0xfffffadce084b360 for PDO 0xfffffadcdfb88860
                InstancePath is "ACPI\PNP0C02\LPC_DEV"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
              DevNode 0xfffffadce0976010 for PDO 0xfffffadcdfb88660
                InstancePath is "ACPI\PNP0B00\4&e69c0be&0"
                State = DeviceNodeStarted (0x308)
                Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0xfffffadce0976e40 for PDO 0xfffffadcdfb88460
                InstancePath is "ACPI\PNP0100\4&e69c0be&0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
              DevNode 0xfffffadce0976c70 for PDO 0xfffffadcdfb88260
                InstancePath is "ACPI\INT3F0D\4&e69c0be&0"
                State = DeviceNodeInitialized (0x302)
                Previous State = DeviceNodeUninitialized (0x301)
            DevNode 0xfffffadce0963aa0 for PDO 0xfffffadce0964700
              InstancePath is "PCI\VEN_8086&DEV_A2A1&SUBSYS_A2A11849&REV_00\3&11583659&0&FA"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
              Problem = CM_PROB_DISABLED
            DevNode 0xfffffadce09638d0 for PDO 0xfffffadce09643e0
              InstancePath is "PCI\VEN_8086&DEV_A2F0&SUBSYS_12211849&REV_00\3&11583659&0&FB"
              ServiceName is "HDAudBus"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
              DevNode 0xfffffadcdf911010 for PDO 0xfffffadcdfac9560

                InstancePath is
    "HDAUDIO\FUNC_01&VEN_10EC&DEV_1220&SUBSYS_18491221&REV_1000\4&cc7b6aa&0&0001"
                ServiceName is "IntcAzAudAddService"
                State = DeviceNodeStarted (0x308)
                Previous State = DeviceNodeEnumerateCompletion (0x30d)
            DevNode 0xfffffadce0963700 for PDO 0xfffffadce0614060
              InstancePath is "PCI\VEN_8086&DEV_A2A3&SUBSYS_A2A31849&REV_00\3&11583659&0&FC"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
              Problem = CM_PROB_DISABLED
            DevNode 0xfffffadce0963530 for PDO 0xfffffadce0614d40
              InstancePath is "PCI\VEN_8086&DEV_15B8&SUBSYS_15B81849&REV_00\3&11583659&0&FE"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
              Problem = CM_PROB_DISABLED
            DevNode 0xfffffadce0963360 for PDO 0xfffffadce09610c0
              InstancePath is "ACPI\PNP0C02\1"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
            DevNode 0xfffffadce095d010 for PDO 0xfffffadce09641e0
              InstancePath is "ACPI\PNP0C02\PCHRESV"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
            DevNode 0xfffffadce095de40 for PDO 0xfffffadce070a8e0
              InstancePath is "ACPI\PNP0C02\IoTraps"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
            DevNode 0xfffffadce095dc70 for PDO 0xfffffadce0614b40
              InstancePath is "ACPI\PNP0C02\5"
              State = DeviceNodeInitialized (0x302)
              Previous State = DeviceNodeUninitialized (0x301)
            DevNode 0xfffffadce095daa0 for PDO 0xfffffadce0614940
              InstancePath is "ACPI\PNP0C14\MXM2"
              ServiceName is "WmiAcpi"
              State = DeviceNodeStarted (0x308)
              Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadce06152e0 for PDO 0xfffffadce0616060
            InstancePath is "ACPI\GenuineIntel_-_EM64T_Family_6_Model_158\_0"
            ServiceName is "intelppm"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadce097f190 for PDO 0xfffffadce0965060
            InstancePath is "ACPI\GenuineIntel_-_EM64T_Family_6_Model_158\_1"
            ServiceName is "intelppm"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadce0629e40 for PDO 0xfffffadce084c4e0
            InstancePath is "ACPI\GenuineIntel_-_EM64T_Family_6_Model_158\_2"
            ServiceName is "intelppm"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadce1eecb80 for PDO 0xfffffadce084e8e0
            InstancePath is "ACPI\GenuineIntel_-_EM64T_Family_6_Model_158\_3"
            ServiceName is "intelppm"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadce0956340 for PDO 0xfffffadce1ef71b0
            InstancePath is "ACPI\GenuineIntel_-_EM64T_Family_6_Model_158\_4"
            ServiceName is "intelppm"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadce0609670 for PDO 0xfffffadce1ee81b0
            InstancePath is "ACPI\GenuineIntel_-_EM64T_Family_6_Model_158\_5"
            ServiceName is "intelppm"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadce07cb0e0 for PDO 0xfffffadce0617e60
            InstancePath is "ACPI\GenuineIntel_-_EM64T_Family_6_Model_158\_6"
            ServiceName is "intelppm"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadce0617b70 for PDO 0xfffffadce1ef21b0
            InstancePath is "ACPI\GenuineIntel_-_EM64T_Family_6_Model_158\_7"
            ServiceName is "intelppm"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadce0978190 for PDO 0xfffffadce1f033c0
            InstancePath is "ACPI\GenuineIntel_-_EM64T_Family_6_Model_158\_8"
            ServiceName is "intelppm"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadce095fe40 for PDO 0xfffffadce1eed360
            InstancePath is "ACPI\GenuineIntel_-_EM64T_Family_6_Model_158\_9"
            ServiceName is "intelppm"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadce0617480 for PDO 0xfffffadce1ee41b0
            InstancePath is "ACPI\GenuineIntel_-_EM64T_Family_6_Model_158\10"
            ServiceName is "intelppm"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadce06172b0 for PDO 0xfffffadce0609350
            InstancePath is "ACPI\GenuineIntel_-_EM64T_Family_6_Model_158\11"
            ServiceName is "intelppm"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadce06170e0 for PDO 0xfffffadce07cbde0
            InstancePath is "ACPI\PNP0C0E\2&daba3ff&0"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadce0960b80 for PDO 0xfffffadce1eeb590
            InstancePath is "ACPI\PNP0C14\TBFP"
            ServiceName is "WmiAcpi"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadce09609b0 for PDO 0xfffffadce0950440
            InstancePath is "ACPI\PNP0C0C\2&daba3ff&0"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
          DevNode 0xfffffadce09607e0 for PDO 0xfffffadce0609060
            InstancePath is "ACPI\FixedButton\2&daba3ff&0"
            State = DeviceNodeStarted (0x308)
            Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1f02e40 for PDO 0xfffffadce0a9c9e0
        InstancePath is "Root\dmio\0000"
        ServiceName is "dmio"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1f02a60 for PDO 0xfffffadce1f02c80
        InstancePath is "Root\ftdisk\0000"
        ServiceName is "ftdisk"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
        DevNode 0xfffffadce0628010 for PDO 0xfffffadce0974060
          InstancePath is "STORAGE\Volume\1&30a96598&0&Signature661910A0Offset100000Length1D1C05C0000"
          ServiceName is "volsnap"
          TargetDeviceNotify List - f 0xfffffa80003a8290  b 0xfffffa80008061c0
          State = DeviceNodeStarted (0x308)
          Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1f03c30 for PDO 0xfffffadce1f03e50
        InstancePath is "Root\LEGACY_AFD\0000"
        ServiceName is "AFD"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1f03850 for PDO 0xfffffadce1f03a70
        InstancePath is "Root\LEGACY_BEEP\0000"
        ServiceName is "Beep"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a9be40 for PDO 0xfffffadce0a9b060
        InstancePath is "Root\LEGACY_CDAC15BA\0000"
        ServiceName is "CdaC15BA"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a9ba60 for PDO 0xfffffadce0a9bc80
        InstancePath is "Root\LEGACY_CDAD10BA\0000"
        ServiceName is "CdaD10BA"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a9b680 for PDO 0xfffffadce0a9b8a0
        InstancePath is "Root\LEGACY_CRCDISK\0000"
        ServiceName is "crcdisk"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a9b2a0 for PDO 0xfffffadce0a9b4c0
        InstancePath is "Root\LEGACY_DMBOOT\0000"
        ServiceName is "dmboot"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1f01e40 for PDO 0xfffffadce1f01060
        InstancePath is "Root\LEGACY_DMLOAD\0000"
        ServiceName is "dmload"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1f01a60 for PDO 0xfffffadce1f01c80
        InstancePath is "Root\LEGACY_FIPS\0000"
        ServiceName is "Fips"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1f01680 for PDO 0xfffffadce1f018a0
        InstancePath is "Root\LEGACY_GPC\0000"
        ServiceName is "Gpc"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1f012a0 for PDO 0xfffffadce1f014c0
        InstancePath is "Root\LEGACY_IPNAT\0000"
        ServiceName is "IpNat"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a9ae40 for PDO 0xfffffadce0a9a060
        InstancePath is "Root\LEGACY_IPSEC\0000"
        ServiceName is "IPSec"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a9aa60 for PDO 0xfffffadce0a9ac80
        InstancePath is "Root\LEGACY_KSECDD\0000"
        ServiceName is "ksecdd"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a9a680 for PDO 0xfffffadce0a9a8a0
        InstancePath is "Root\LEGACY_MNMDD\0000"
        ServiceName is "mnmdd"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a9a2a0 for PDO 0xfffffadce0a9a4c0
        InstancePath is "Root\LEGACY_MOUNTMGR\0000"
        ServiceName is "mountmgr"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1f00e40 for PDO 0xfffffadce1f00060
        InstancePath is "Root\LEGACY_NDIS\0000"
        ServiceName is "NDIS"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1f00a60 for PDO 0xfffffadce1f00c80
        InstancePath is "Root\LEGACY_NDISTAPI\0000"
        ServiceName is "NdisTapi"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1f00680 for PDO 0xfffffadce1f008a0
        InstancePath is "Root\LEGACY_NDISUIO\0000"
        ServiceName is "Ndisuio"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1f002a0 for PDO 0xfffffadce1f004c0
        InstancePath is "Root\LEGACY_NDPROXY\0000"
        ServiceName is "NDProxy"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a99e40 for PDO 0xfffffadce0a99060
        InstancePath is "Root\LEGACY_NETBT\0000"
        ServiceName is "NetBT"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a99a60 for PDO 0xfffffadce0a99c80
        InstancePath is "Root\LEGACY_NULL\0000"
        ServiceName is "Null"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a99680 for PDO 0xfffffadce0a998a0
        InstancePath is "Root\LEGACY_PARTMGR\0000"
        ServiceName is "PartMgr"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a992a0 for PDO 0xfffffadce0a994c0
        InstancePath is "Root\LEGACY_RASACD\0000"
        ServiceName is "RasAcd"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1effe40 for PDO 0xfffffadce1eff060
        InstancePath is "Root\LEGACY_RDPCDD\0000"
        ServiceName is "RDPCDD"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1effa60 for PDO 0xfffffadce1effc80
        InstancePath is "Root\LEGACY_SECDRV\0000"
        ServiceName is "Secdrv"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1eff680 for PDO 0xfffffadce1eff8a0
        InstancePath is "Root\LEGACY_TCPIP\0000"
        ServiceName is "Tcpip"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1eff2a0 for PDO 0xfffffadce1eff4c0
        InstancePath is "Root\LEGACY_VGASAVE\0000"
        ServiceName is "VgaSave"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a98e40 for PDO 0xfffffadce0a98060
        InstancePath is "Root\LEGACY_VOLSNAP\0000"
        ServiceName is "VolSnap"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a98a60 for PDO 0xfffffadce0a98c80
        InstancePath is "Root\LEGACY_WANARP\0000"
        ServiceName is "Wanarp"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a98680 for PDO 0xfffffadce0a988a0
        InstancePath is "Root\MEDIA\MS_MMACM"
        ServiceName is "audstub"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a982a0 for PDO 0xfffffadce0a984c0
        InstancePath is "Root\MEDIA\MS_MMDRV"
        ServiceName is "audstub"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1efee40 for PDO 0xfffffadce1efe060
        InstancePath is "Root\MEDIA\MS_MMMCI"
        ServiceName is "audstub"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1efea60 for PDO 0xfffffadce1efec80
        InstancePath is "Root\MEDIA\MS_MMVCD"
        ServiceName is "audstub"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1efe680 for PDO 0xfffffadce1efe8a0
        InstancePath is "Root\MEDIA\MS_MMVID"
        ServiceName is "audstub"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1efe2a0 for PDO 0xfffffadce1efe4c0
        InstancePath is "Root\MS_L2TPMINIPORT\0000"
        ServiceName is "Rasl2tp"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a97e40 for PDO 0xfffffadce0a97060
        InstancePath is "Root\MS_NDISWANIP\0000"
        ServiceName is "NdisWan"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a97a60 for PDO 0xfffffadce0a97c80
        InstancePath is "Root\MS_PPPOEMINIPORT\0000"
        ServiceName is "RasPppoe"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a97680 for PDO 0xfffffadce0a978a0
        InstancePath is "Root\MS_PPTPMINIPORT\0000"
        ServiceName is "PptpMiniport"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a972a0 for PDO 0xfffffadce0a974c0
        InstancePath is "Root\MS_PTIMINIPORT\0000"
        ServiceName is "Raspti"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1efde40 for PDO 0xfffffadce1efd060
        InstancePath is "Root\RDPDR\0000"
        ServiceName is "rdpdr"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1efda60 for PDO 0xfffffadce1efdc80
        InstancePath is "Root\RDP_KBD\0000"
        ServiceName is "TermDD"
        TargetDeviceNotify List - f 0xfffffa8000979fa0  b 0xfffffa8000979fa0
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1efd680 for PDO 0xfffffadce1efd8a0
        InstancePath is "Root\RDP_MOU\0000"
        ServiceName is "TermDD"
        TargetDeviceNotify List - f 0xfffffa8000794960  b 0xfffffa8000794960
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce1efd2a0 for PDO 0xfffffadce1efd4c0
        InstancePath is "Root\SYSTEM\0000"
        ServiceName is "swenum"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a96e40 for PDO 0xfffffadce0a96060
        InstancePath is "Root\SYSTEM\0001"
        ServiceName is "update"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
      DevNode 0xfffffadce0a96a60 for PDO 0xfffffadce0a96c80
        InstancePath is "Root\SYSTEM\0002"
        ServiceName is "mssmbios"
        State = DeviceNodeStarted (0x308)
        Previous State = DeviceNodeEnumerateCompletion (0x30d)
    11: kd> g
    [alcwzrd]Driver Version >=5100

Just to change videoprt.sys from WinServer2003 R2 64 bit to XP64 SP2 is not enough.
It still gives BSOD VIDEOPRT.SYS ( VIDEOPRT!pVideoPortInitializeInt10+4e )
on XP64 SP2, this BSOD XP64 SP1 and WinServer2003 R2 64 bit never show.

#2432

Gelip

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #2431

> Just to change videoprt.sys from WinServer2003 R2 64 bit to XP64 SP2 is not enough.
> It still gives BSOD VIDEOPRT.SYS ( VIDEOPRT!pVideoPortInitializeInt10+4e )
> on XP64 SP2, this BSOD XP64 SP1 and WinServer2003 R2 64 bit never show.

There is only one conclusion. Since on some computers WinXP x64 SP2 starts with AnaPa without any problems (X220) and on others it does not have to depend on the motherboard bios.
From this post it follows that booting also depends on the graphics card or its VBIOS:
¶ ASRock Z170 Pro4S + NVidia 8400GS GPU with the Anapa driver

#2433

diderius6

⇗ @Gelip
I just notice, that the grafikcards, which work with the Anapa driver have NO GOP (so no pur UEFI),
means they need always INT10.
Can you confirm this with your grafikcards which work/not work with the Anapa driver on XP64 SP2 for UEFI
Dietmar

#2434

diderius6

⇗ @Mov AX, 0xDEAD ⇗ @daniel_k
Do you have an idea, how to disable the signature check
in winload.efi?
There is a switch in the BCD menu
"Disable Driver Signature Enforcement"
but this switch cannot be set via BootIce for to be permanent.
I noticed, that all the problems, that winload.efi makes via INT10 for grafik
are the same as in winload.exe, so it isnt a problem of UEFI.
Here is the winload.efi 6.0.6001.16497
which may be the only working UEFI OS loader for XP64.
As bootloader you can use also the one from Win8
Dietmar
diderius6 has attached files to this post

- ⇗ server_BCD.rar

#2435

Gelip

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #2433

> I just notice, that the grafikcards, which work with the Anapa driver have NO GOP (so no pur UEFI),
> means they need always INT10.
> Can you confirm this with your grafikcards which work/not work with the Anapa driver on XP64 SP2 for UEFI
> Dietmar

It also depends on the motherboard bios version. X220 with latest bios have no GOP for iGPU and AnaPa working with efi loader from beta server.
ASUS bios 0402 (initial release) and 0405 have no GOP for iGPU but efi loader from server beta crash with error: An unexpected error 0xc0000017 and efi loader from vista beta crash with error: BlInitializeLibrary failed 0xc0000023 The same happens with a PCIe graphics card that does not have a GOP, e.g. GeForce 6200
Only bios version 0610 and newer have GOP for iGPU SNB/IVB and CSM Enable/Disable switch.
Yeeeaahh!
WinXP x64 SP2 boot OK on ASUS P8H61-M-LE-R2 with bios 0610 with PCIe GeForce 6200 LE 64MB VGA (D-sub) with AnaPa (nVidia):
⇗
It is possible because I installed WinXP again:

- one active partition FAT32 5120MB (5GB)
- efi loader from beta server
- no any drivers installed except AnaPa (nVidia) and Gigabit Ethernet
- debugging is set in BCD file and WinDbg work on another PC over serial cable (without symbol path)
- HDD work in IDE Compatible mode (not SATA, AHCI)
- option Fast Boot enabled in bios
- Launch CSM - Auto
- Security Boot - Other legacy & UEFI

⇗ ⇗
Bios 610 not detect HDD as UEFI: but to start WinXP you need use EFI Shell loaded from FAT32 pendrive:

    fs1:\efi\boot\bootx64.efi

or add entry to NVRAM with bcfg command:

    bcfg boot dump

check last value e.g i have 00 - PXE Realtek, 01 - HDD, 02 - UEFI: Kingston then next empty value is 03 so:

    bcfg boot add 3 fs1:\efi\boot\bootx64.efi "WinXP x64 SP2 from UEFI"

⇗
My Geforce 6200 LE no have GOP firmware.

#2436

infuscomus

⇗ @diderius6
I tested you XP64 Image in VMWare Workstation 15.1
in BIOS mode it booted normally, worked fine
in UEFI mode I received this error
⇗
this matches your testing?
edit:
disabling driver signature enforcement appears to make VM freeze (HDD/CD/Network icons in bottom right corner blink constantly and goes nowhere)

#2437 | diderius6 | ⇗ @infuscomus On real hardware I have no problem with disabling driver signature enforcement via BCD. But it can there not be set to permanently Dietmar

#2438

infuscomus

⇗ @Lost_N_BIOS
do you know anything about UEFI programming?
⇗ https://github.com/tianocore/edk2/tree/master/OvmfPkg/Csm
⇗ https://github.com/tianocore/edk2/search...unscoped_q=BIOS
It would be nice to have an EFI executable that could be run from EFI console to create a CSM from scratch to support legacy OS for UEFI class 3 systems in the future that wont have one.
assuming that this is possible

#2439 | lsmlcx | I test final ACPI.sys and xhci for Intel z170. they work well in XP x86, but in 2003 the Intel xhci device cann't start with error 39
#2440 | cringysami | is there any way to make Windows XP run on an ASRock B450M Pro4 motherboard? that's the motherboard that i have and i can't find any sata drivers for xp to work, so i keep getting bluescreens on the xp setup.
#2441 | IntiMD | ⇗ @cringysami ¶ Windows XP SP3 32bit and modern PC parts (119) Here's the link to the generic AHCI driver(storahci) by skullteria. If you can provide, what's the hardware identificator of the mobo's SATA controller?
#2442 | cringysami | How do I provide the hardware identifactor of the SATA controller?
#2443 | infuscomus | ⇗ @cringysami Show what is in Hardware IDs e.g. in Windows 10 -> Control Panel -> Device Manager -> IDE/ATAPI Controllers -> Standard SATA AHCI Controller -> Details -> Hardware IDs -> PCI\VEN_1022&DEV_7901&CC_0106

#2444

IntiMD

⇗ @cringysami
Aight, the first device according to pci.ids (DEV_7901) is "AMD FCH SATA Controller [AHCI mode]", the second one (DEV_43C8) is "AMD 400 Series Chipset SATA Controller" which is actually a virtualised AHCI controller for StoreMI. You shouldn't care about that virtualised device(second one), but the first device instead.
You now have 2 choices: One is to use the generic backported StorAHCI driver (which relies on Storport, which XP doesn't have <only Windows Server 2003>), the second choice is to use the inf-modded AMD AHCI driver by Fernando, which can be found here ⇗ [Guide] Integration of AMD's AHCI/RAID drivers into a WinXP/W2k3 CD
Get >Universal 32bit AMD AHCI driver v6.1.3.35 mod+signed by Fernando<, since the v1.21.321 driver depends on Storport, which XP doesn't have.

#2445 | infuscomus | ⇗ @cringysami there is also a modded driver by daniel_k you can try ¶ Windows XP SP3 32bit and modern PC parts (112)

## Page 164

#2446

infuscomus

Has anyone compiled 64bit reactos? would like to try their 64bit videoprt.sys
edit:
most recent pre-built x64
⇗ https://iso.reactos.org/bootcd/latest-x64-msvc-win-dbg
infuscomus has attached files to this post

- ⇗ reactos-x64-videoprt.zip

#2447

diderius6

⇗ @infuscomus
I tried the videoprt.sys from Reactos for to boot XP64 SP2.
I have no success, not for legacy not for UEFI boot, with
or without the ANAPA driver.
But the BSODS are other than for videoprt.sys from XP64 SP2.
So, may be the Reactos drivers are future for UEFI boot of XP
Dietmar

#2448 | infuscomus | ⇗ @diderius6 I get BSOD 0A with reactos videoprt.sys
#2449 | cringysami | ⇗ @IntiMD I tried using the storAHCI driver but I got the same 0x7B bluescreen. When I messaged didierious6 about it, he told me if I put the storport.sy_ correctly, but on the folder he linked, there was storport.sys and acpi.sys. Was I supposed to rename .sys to .sy_ for the bluescreen to go away. I'll also try the other driver you linked. Thank you for trying to help me solve this problem, I really appreciate it.
#2450 | infuscomus | ⇗ @cringysami you use nlite to integrate the drivers into your XP installation ISO.
#2451 | cringysami | ⇗ @infuscomus I did use nlite to integrate the drivers. It still gave me the same bluescreen. I don't know what I am doing wrong. I tried the universal driver too and it still gave me the bluescreen.
#2452 | infuscomus | ⇗ @cringysami one thing I found through testing - USB CD/DVD drives do not work properly on USB 3.0 for installing XP. you can solve this by using: 1. a SATA CD/DVD or 2. getting a PCI-E USB 2.0 card (uncommon, but they exist) - with USB 2.0 you can use USB CD/DVD drives for installing XP.
#2453 | cringysami | ⇗ @infuscomus Yes, I was using a USB 3.0 to install XP. My computer does not have a CD Drive and all the USB ports on the motherboard are USB 3.0. I guess my only option is to buy a SATA CD/DVD drive. Thank you so much for trying to help me. You, diderious6, and IntiDM have been really helpful and I appreciate it. I was hoping that the installation would work, but it seems that it only would work with a CD drive so I might get one.
#2454 | infuscomus | ⇗ @cringysami you're welcome! P.S alternatively - pcie USB 2.0 card ⇗ https://www.ebay.com/itm/USB-2-0-to-PCI-...lEAAOSwaBZZmNXaThe following contents have been linked to this post:

#2455

skullteria

> Zitat von ⇗ infuscomus im Beitrag ¶ #2448

> @diderius6
> I get BSOD 0A with reactos videoprt.sys

VideoPrt from reactos is incomplete and instable. Need some adaptation to run on XP. Even x86 version not work, on "normal" Bios

#2456

dencorso

> Zitat von ⇗ skullteria im Beitrag ¶ #2455

> VideoPrt from reactos is incomplete and instable. Need some adaptation to run on XP. Even x86 version not work, on "normal" Bios

Ain't it amazing how no interesting module from ReactOS is ever complete or working OK whenever it's needed?

#2457

diderius6

⇗ @dencorso
I make a try to set up the Reactos 64 bit *.iso on a FAT32 partition
from ⇗ @infuscomus post #2446 on the Asrock fatal1ty z370 gaming k6.
But even it looks, as Reactos has all the needed drivers for this board,
it crashes during install with black screen and no comment at all
Dietmar
EDIT: There is also a life CD for Reactos 64 bit
⇗ https://drive.google.com/uc?export=downl...mZwY4l-ndmLzXEb
This one fails with BSOD for bootvid.dll.
May be, that the switch /SOS can help.
EDIT2: Using the /SOS switch and setting up windbg it shows,
that it has a problem with the AHCI driver. So, it may work in IDE compatible mode.

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Opened \\.\com1
    Waiting to reconnect...
    (ntoskrnl\kd64\kdinit.c:74) -----------------------------------------------------
    (ntoskrnl\kd64\kdinit.c:75)
     ReactOS 0.4.13-amd64-dev (Build 20190530-0.4.13-dev-439-g582cbbd)
    (Commit 582cbbd9e082397bc3c7ba62183ab0e19d5adc29)
    (ntoskrnl\kd64\kdinit.c:76) 1 System Processor [1024 MB Memory]
    (ntoskrnl\kd64\kdinit.c:80) Command Line: DEBUG DEBUGPORT=COM1 BAUDRATE=115200 SOS MININT
    (ntoskrnl\kd64\kdinit.c:81) ARC Paths: multi(0)disk(0)cdrom(111) \ multi(0)disk(0)cdrom(111) \reactos\
    Connected to Windows Server 2003 3790 x64 target at (Mon Sep 16 23:15:49.500 2019 (UTC + 2:00)), ptr64 TRUE
    Kernel Debugger connection established.
    WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
    Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
    *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
    Executable search path is: C:\localsymbols
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntoskrnl.exe -
    Windows Server 2003 Kernel Version 3790 UP Checked x64
    Built by: 20190530-0.4.13-dev-439-g582cbbd.MSVC_19.21.27702.2
    Machine Name:
    Kernel base = 0xfffff800`00400000 PsLoadedModuleList = 0xfffff800`0062b830
    System Uptime: not available
    (ntoskrnl\ke\amd64\kiinit.c:445) Pcr = FFFFF80000608180, Gdt = FFFFF800003FC000, Idt = FFFFF80000627A00, Tss = FFFFF8000009B000
    (hal\halx86\acpi\halacpi.c:782) ACPI Timer at: 1808h (EXT: 0)
    (hal\halx86\acpi\halacpi.c:891) ACPI 2.0 Detected. Tables: [RSDT] [FACP] [DBGP]
    (hal\halx86\apic\rtctimer.c:102) Clock initialized
    (ntoskrnl\mm\ARM3\mminit.c:1452) HAL I/O Mapping at FFFFFFFFFFFE0000 is unsafe
    (ntoskrnl\mm\ARM3\mminit.c:1452) HAL I/O Mapping at FFFFFFFFFFFE1000 is unsafe
    (ntoskrnl\mm\ARM3\largepag.c:37) MiInitializeLargePageSupport: PAE/x64 Not Implemented
    (hal\halx86\amd64\x86bios.c:106) memory: F000EEF3F000EEF3, F000EEF3F000E2C3
    ExceptionFilter 1
    ExceptionFilter 2
    Finally
    Target1
    (ntoskrnl\mm\mminit.c:136)           0xFFFFF80000000000 - 0xFFFFF80003000000	Boot Loaded Image
    (ntoskrnl\mm\mminit.c:140)           0xFFFFFA8000000000 - 0xFFFFFA8000E01000	PFN Database
    (ntoskrnl\mm\mminit.c:144)           0xFFFFFA8031038000 - 0xFFFFFA8033050000	ARM3 Non Paged Pool
    (ntoskrnl\mm\mminit.c:148)           0xFFFFF97FED000000 - 0xFFFFF97FF3800000	System View Space
    (ntoskrnl\mm\mminit.c:152)           0xFFFFF97FF3800000 - 0xFFFFF98000000000	Session Space
    (ntoskrnl\mm\mminit.c:155)           0xFFFFF68000000000 - 0xFFFFF6FFFFFFFFFF	Page Tables
    (ntoskrnl\mm\mminit.c:158)           0xFFFFF6FB40000000 - 0xFFFFF6FB7FFFFFFF	Page Directories
    (ntoskrnl\mm\mminit.c:161)           0xFFFFF70000000000 - 0xFFFFF77FFFFFFFFF	Hyperspace
    (ntoskrnl\mm\mminit.c:164)           0xFFFFF98000000000 - 0xFFFFF980FFFFEFFF	System Cache
    (ntoskrnl\mm\mminit.c:168)           0xFFFFF8A000000000 - 0xFFFFF8A002000000	ARM3 Paged Pool
    (ntoskrnl\mm\mminit.c:171)           0xFFFFF88000000000 - 0xFFFFFA8033050000	System PTE Space
    (ntoskrnl\mm\mminit.c:174)           0xFFFFFA8033050000 - 0xFFFFFA8049F44000	Non Paged Pool Expansion PTE Space
    (ntoskrnl\config\cmcheck.c:25) CmCheckRegistry(0xFFFFFA8032FD8000, 2) is UNIMPLEMENTED!
    ACPI Compatible Eisa/Isa HAL Detected
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2CB0, Irp->UserEvent=FFFFF880053DC220, IrpStack=FFFFFA8032FD2DC8
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2CB0, Irp->UserEvent=FFFFF880053DC150, IrpStack=FFFFFA8032FD2DC8
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2CB0, Irp->UserEvent=FFFFF880053DC220, IrpStack=FFFFFA8032FD2DC8
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2CB0, Irp->UserEvent=FFFFF880053DC2A0, IrpStack=FFFFFA8032FD2DC8
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2CB0, Irp->UserEvent=FFFFF880053DC2A0, IrpStack=FFFFFA8032FD2DC8
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2CB0, Irp->UserEvent=FFFFF880053DC380, IrpStack=FFFFFA8032FD2DC8
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2CB0, Irp->UserEvent=FFFFF880053DC380, IrpStack=FFFFFA8032FD2DC8
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2CB0, Irp->UserEvent=FFFFF880053DC380, IrpStack=FFFFFA8032FD2DC8
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2CB0, Irp->UserEvent=FFFFF880053DC380, IrpStack=FFFFFA8032FD2DC8
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2CB0, Irp->UserEvent=FFFFF880053DC380, IrpStack=FFFFFA8032FD2DC8
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2CB0, Irp->UserEvent=FFFFF880053DC420, IrpStack=FFFFFA8032FD2DC8
    (ntoskrnl\ex\work.c:755) Requesting a new thread. CurrentCount: 0. MaxCount: 1
    (sdk\lib\rtl\image.c:172) Invalid base address: 0000000000000000
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC790, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\iomgr\driver.c:1637) '\Driver\SACDRV' initialization failed, status (0xc0000037)
    (ntoskrnl\io\iomgr\driver.c:64) Deleting driver object '\Driver\SACDRV'
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC6D0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC6D0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC6D0, IrpStack=FFFFFA8032FD2340
    (drivers\storage\scsiport\scsiport.c:5859) ZwOpenKey() failed with Status=0xC0000034
    (hal\halx86\legacy\bus\pcibus.c:727) WARNING: PCI Slot Resource Assignment is FOOBAR
    (ntoskrnl\ke\amd64\interrupt.c:94) FIXME: KeConnectInterrupt() with invalid vector 0x0!
    (ntoskrnl\ke\amd64\interrupt.c:136) FIXME: KeConnectInterrupt() with used vector 0x0!
    (hal\halx86\legacy\bus\pcibus.c:727) WARNING: PCI Slot Resource Assignment is FOOBAR
    (ntoskrnl\ke\amd64\interrupt.c:94) FIXME: KeConnectInterrupt() with invalid vector 0x10!
    (ntoskrnl\ke\amd64\interrupt.c:136) FIXME: KeConnectInterrupt() with used vector 0x10!
    (ntoskrnl\io\iomgr\driver.c:1637) '\Driver\UNIATA' initialization failed, status (0xc00000c0)
    (ntoskrnl\io\iomgr\driver.c:64) Deleting driver object '\Driver\UNIATA'
    (ntoskrnl\io\iomgr\driver.c:1637) '\Driver\BUSLOGIC' initialization failed, status (0xc00000c0)
    (ntoskrnl\io\iomgr\driver.c:64) Deleting driver object '\Driver\BUSLOGIC'
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC6D0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC6D0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC6D0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC6D0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC6D0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC6D0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC6D0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC6D0, IrpStack=FFFFFA8032FD2340
    (drivers\ksfilter\swenum\swenum.c:428) SWENUM loaded
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC6D0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2CB0, Irp->UserEvent=FFFFF880053DC8B0, IrpStack=FFFFFA8032FD2DC8
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC4C0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC3F0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC4C0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC540, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC540, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC620, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC620, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC620, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC620, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC620, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2CB0, Irp->UserEvent=FFFFF880053DC3D0, IrpStack=FFFFFA8032FD2DC8
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2CB0, Irp->UserEvent=FFFFF880053DC410, IrpStack=FFFFFA8032FD2DC8
    (ntoskrnl\ke\amd64\interrupt.c:94) FIXME: KeConnectInterrupt() with invalid vector 0x20!
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2CB0, Irp->UserEvent=FFFFF880053DC2C0, IrpStack=FFFFFA8032FD2DC8
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2CB0, Irp->UserEvent=FFFFF880053DC340, IrpStack=FFFFFA8032FD2DC8
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2CB0, Irp->UserEvent=FFFFF880053DC350, IrpStack=FFFFFA8032FD2DC8
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DBF60, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DBE90, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DBF60, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DBFE0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DBFE0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC0C0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC0C0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC0C0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC0C0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC0C0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DC020, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DBF70, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DBFB0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DBE60, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DBEE0, IrpStack=FFFFFA8032FD2340
    (ntoskrnl\io\pnpmgr\pnpmgr.c:670) No service!
    (ntoskrnl\io\pnpmgr\pnpmgr.c:1466) ### Irp=FFFFFA8032FD2270, Irp->UserEvent=FFFFF880053DBEF0, IrpStack=FFFFFA8032FD2340

    *** Fatal System Error: 0x0000007b
                                                 (0xFFFFF880053DCA18,0xFFFFFFFFC0000034,0x0000000000000000,0x0000000000000000)

    Break instruction exception - code 80000003 (first chance)

    A fatal system error has occurred.
    Debugger entered on first try; Bugcheck callbacks have not been invoked.

    A fatal system error has occurred.

    Connected to Windows Server 2003 3790 x64 target at (Mon Sep 16 23:16:02.062 2019 (UTC + 2:00)), ptr64 TRUE
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntoskrnl.exe -
    Loading Kernel Symbols
    .....................
    Loading User Symbols

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7B, {fffff880053dca18, ffffffffc0000034, 0, 0}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : ntoskrnl.exe ( nt!KeRegisterNmiCallback+592 )

    Followup: MachineOwner
    ---------

    nt!DbgBreakPointWithStatus+0x2:
    fffff800`0057f876 cc              int     3
    kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    INACCESSIBLE_BOOT_DEVICE (7b)
    During the initialization of the I/O system, it is possible that the driver
    for the boot device failed to initialize the device that the system is
    attempting to boot from, or it is possible for the file system that is
    supposed to read that device to either fail its initialization or to simply
    not recognize the data on the boot device as a file system structure that
    it recognizes.  In the former case, the argument (#1) is the address of a
    Unicode string data structure that is the ARC name of the device from which
    the boot was being attempted.  In the latter case, the argument (#1) is the
    address of the device object that could not be mounted.
    If this is the initial setup of the system, then this error can occur if
    the system was installed on an unsupported disk or SCSI controller.  Note
    that some controllers are supported only by drivers which are in the Windows
    Driver Library (WDL) which requires the user to do a custom install.  See
    the Windows Driver Library for more information.
    This error can also be caused by the installation of a new SCSI adapter or
    disk controller or repartitioning the disk with the system partition.  If
    this is the case, on x86 systems the boot.ini file must be edited or on ARC
    systems setup must be run.  See the "Advanced Server System Administrator's
    User Guide" for information on changing boot.ini.
    If the argument is a pointer to an ARC name string, then the format of the
    first two (and in this case only) longwords will be:
        USHORT Length;
        USHORT MaximumLength;
        PWSTR Buffer;
    That is, the first longword will contain something like 00800020 where 20
    is the actual length of the Unicode string, and the next longword will
    contain the address of buffer.  This address will be in system space, so
    the high order bit will be set.
    If the argument is a pointer to a device object, then the format of the first
    word will be:
        USHORT Type;
    That is, the first word will contain a 0003, where the Type code will ALWAYS
    be 0003.
    Note that this makes it immediately obvious whether the argument is a pointer
    to an ARC name string or a device object, since a Unicode string can never
    have an odd number of bytes, and a device object will always have a Type
    code of 3.
    Arguments:
    Arg1: fffff880053dca18, Pointer to the device object or Unicode string of ARC name
    Arg2: ffffffffc0000034
    Arg3: 0000000000000000
    Arg4: 0000000000000000

    Debugging Details:
    ------------------

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************

    ADDITIONAL_DEBUG_TEXT:
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    MODULE_NAME: nt

    FAULTING_MODULE: fffff80000400000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  5cf01f6c

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0x7B

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff800004ab0d2 to fffff8000057f876

    STACK_TEXT:
    fffff880`053dc348
     fffff800`004ab0d2 : fffff880`053dc388 fffff880`053dc401
    00000000`00000000 00000000`00000000 : nt!DbgBreakPointWithStatus+0x2
    fffff880`053dc350
     fffff800`004aa282 : fffff800`00000003 00000000`0000007b
    fffff880`053dca18 ffffffff`c0000034 : nt!KeRegisterNmiCallback+0x592
    fffff880`053dc380
     fffff800`004a99f2 : fffff880`0000007b fffff880`053dca18
    ffffffff`c0000034 00000000`00000000 : nt!KeBugCheckEx+0x8d2
    fffff880`053dc990
     fffff800`005b887a : fffff880`0000007b fffff880`053dca18
    ffffffff`c0000034 00000000`00000000 : nt!KeBugCheckEx+0x42
    fffff880`053dc9d0
     fffff800`005b7818 : fffff800`00074000 fffff800`005d29f8
    00000000`0000000a fffff800`006320e0 : nt!InbvEnableBootDriver+0x3a2a
    fffff880`053dcb90
     fffff800`005b2b53 : fffff800`00074000 fffff800`0000004b
    fffff800`00646700 00000000`00000000 : nt!InbvEnableBootDriver+0x29c8
    fffff880`053dcd80 fffff800`00438fe3 : fffff800`00074000 fffffa80`32feebf0 fffff800`00631800 0053002b`002b0010 : nt!wcsspn+0xd063
    fffff880`053dcf60
     fffff800`0053d17e : fffff800`00074000 fffff800`0053d130
    00000000`00000010 00000000`00000246 : nt!HeadlessDispatch+0x223
    fffff880`053dcf90
     fffff800`0040266b : fffff800`00438fd0 fffff800`00074000
    00000000`00000000 fffff800`0053d130 : nt!PsWrapApcWow64Thread+0xdee
    fffff880`053dcfd0
     00000000`00000000 : 00000000`00000000 00000000`00000000
    00000000`00000000 00000000`00000000 : nt!ZwYieldExecution+0xfb

    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!KeRegisterNmiCallback+592
    fffff800`004ab0d2 eb07            jmp     nt!KeRegisterNmiCallback+0x59b (fffff800`004ab0db)

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt!KeRegisterNmiCallback+592

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  ntoskrnl.exe

    BUCKET_ID:  WRONG_SYMBOLS

    Followup: MachineOwner
    ---------

    kd> lm
    start             end                 module name
    fffff800`0022e000 fffff800`00284000   hal        (deferred)
    fffff800`00284000 fffff800`0028b000   kdcom      (deferred)
    fffff800`0028b000 fffff800`00293000   bootvid    (deferred)
    fffff800`00400000 fffff800`00659000   nt         (export symbols)       ntoskrnl.exe
    fffff880`053dd000 fffff880`0540a000   ks         (deferred)
    fffff880`0540a000 fffff880`05411000   swenum     (deferred)
    fffff880`05411000 fffff880`05435000   ndis       (deferred)
    fffff880`05435000 fffff880`05440000   mup        (deferred)
    fffff880`05440000 fffff880`05448000   nmidebug   (deferred)
    fffff880`05448000 fffff880`05466000   ksecdd     (deferred)
    fffff880`05466000 fffff880`05471000   ramdisk    (deferred)
    fffff880`05471000 fffff880`0547f000   disk       (deferred)
    fffff880`0547f000 fffff880`0548e000   class2     (deferred)
    fffff880`0548e000 fffff880`054a0000   cdrom      (deferred)
    fffff880`054a0000 fffff880`054ab000   buslogic   (deferred)
    fffff880`054ab000 fffff880`054c0000   scsiport   (deferred)
    fffff880`054c0000 fffff880`054ff000   uniata     (deferred)
    fffff880`054ff000 fffff880`05518000   mountmgr   (deferred)
    fffff880`05518000 fffff880`05525000   pci        (deferred)
    fffff880`05525000 fffff880`05587000   acpi       (deferred)
    fffff880`05587000 fffff880`055a2000   sacdrv     (deferred)
    fffff880`055a2000 fffff880`055cf000   cdfs       (deferred)
    kd> !devnode 0 1
    Error retrieving address of IopRootDeviceNode

#2458 | IntiMD | IIRC the AMD64 arch version of ReactOS isn't that ready yet (even compared to the project's 32-bit builds), so don't be surprised that it won't work.

#2459

Gelip

I noticed strange thing. I tested different VGA PCIe and PCI cards and now with GeForce 6200 LE WinXP x64 not boot and error:
Probably caused by : VIDEOPRT.SYS ( VIDEOPRT!pVideoPortInitializeInt10+4e )
I programmed again 610 bios with CH341A but it did not help. I think that I have to install the fresh WinXP bacause the registry has a lot of entries from the previous tested VGA PCIe and PCI cards e.g. in:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318}
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters -> VideoInitTime ???
Maybe it changed load order of the drivers in WinXP and is therefore problem videoprt.sys ???
It may have changed device resources such as IRQ, memory adresses and I/O ports ? For now I have like this:

    System Information report written at: 09/16/19 07:23:00
    System Name: EFIFAT
    [Display]

    Item	Value
    Name	VBE Miniport (nVidia)
    PNP Device ID	PCI\VEN_10DE&DEV_0163&SUBSYS_CA33107D&REV_A1\4&8F789FD&0&0008
    Adapter Type	VESA/SVGA, AnaPa Corp compatible
    Adapter Description	VBE Miniport (nVidia)
    Adapter RAM	64,00 MB (67 108 864 bytes)
    Installed Drivers	framebuf.dll,modex.dll
    Driver Version	15.01.0001
    INF File	oem0.inf (Vbemp section)
    Color Planes	1
    Color Table Entries	4294967296
    Resolution	800 x 600 x 56 hertz
    Bits/Pixel	32
    Memory Address	0xF6000000-0xF6FFFFFF
    Memory Address	0xE0000000-0xEFFFFFFF
    Memory Address	0xF5000000-0xF70FFFFF
    I/O Port	0x000003B0-0x000003BB
    I/O Port	0x000003C0-0x000003DF
    Memory Address	0xA0000-0xBFFFF
    Driver	c:\windows\system32\drivers\vbemp.sys (15.01.0001 built by: WinDDK, 23,00 KB (23 552 bytes), 2019-09-15 19:38)

This is very strange. I need install fresh copy WinXP for tests.

#2460

infuscomus

⇗ @Gelip
have you tried the official nvidia driver for Geforce 6000 series? - Surprisingly, Geforce 6000 is supported up to Windows 8 64bit.
XP 64bit
⇗ https://www.geforce.com/drivers/results/57494
Win8 64bit
⇗ https://www.geforce.com/drivers/results/82758

## Page 165

#2461

Andalu

A strange thingh: usb3 no longer works on my asrock B75 Pro3-M as in ¶ #2130. I had put the board aside after checking the correct operation of the mod drivers but today when I picked it up to try a clean XP install on a new hard disk I was no longer able to get the correctly working USB3. And worse, also connecting my previous disk (used with USB3 ports fully functional), the same ports don't work as some days ago.
The modded AHCI.sys is still in C:\WINDOWS\system32\drivers. Tried to reinstall the drivers with no success. The bios options seem be to set as when usb3 worked correctly. In some reboots, I received this message: 'Press <CTRL P> to Enter MEBX Setup Menu - CMOS Date/Time Not Set - Press F2 or Del to Run Setup - Press F1 to Continue'. By pressing F1 key the boot continued normally but windows date and time was incorrect. I already cleared the cmos and changed the battery and that message seems gone but the usb3 ports act as usb2 also with a new clean XP install. What happened and how can i resolve?

#2462

PPeti66x

Hi! Your problem is probably that Intel Inf package installs a null-driver for Gen-3 and older motherboards. You need to kill this driver prior installing a modded one:
1.) You must search in all *.inf in Windows\Inf directory for string "PantUSB3.inf" or "Null driver for Intel(R) USB 3.0", then rename the file extension of both inf and pnf file (the file should be have name "oem*.inf", then rename to "oem*.in_").
2.) Then You must uninstall the "Intel(R) 7 Series/C216 Chipset Family Universal Serial Bus (USB) Controller - 1E31" driver.
3.) Now you can install the modded driver.

#2463 | Andalu | ⇗ @PPeti66x It works!!! Thanks sooo much
#2464 | lama | Hi,.. Can anyone suggest me best new PC and components that is XP and Hackintosh compatible? Thanks in advance

#2465

Gelip

> Zitat von ⇗ lama im Beitrag ¶ #2464

> Hi,..
> Can anyone suggest me best new PC and components that is XP and Hackintosh compatible? Thanks in advance

Not new, but best is ThinkPad X220. It has drivers for WinXP/Vista/7/8/10. Mac OS also sholud work.
or search motherboard from 2010-2014 which has drivers for WinXP.

#2466

infuscomus

⇗ @diderius6 ⇗ @daniel_k ⇗ @skullteria ⇗ @Gelip
So this was something I was attempting to do a couple of years ago using an old version of KernelEx by Xeno86 that used to patch code into PE files - thanks to Dibya over at MSFN forum for finding it.
It was an attempt at patching extra functions into ntoskrnl for XP to support more hardware.
You can see there is extra code at the end of the file after relocations section (this may or may not be a bad idea? not sure)
anyone interested in going further with this? or a waste of time?
infuscomus has attached files to this post

- ⇗ attempt_ntkrnlmp_patch.zip

#2467 | diderius6 | ⇗ @infuscomus This ntkrnlmp.exe has an unfullfilled dependency for Hal.dll HalGetVectorInput Dietmar

#2468

infuscomus

⇗ @diderius6
here is the hal.dll with HalGetVectorInput patched in
infuscomus has attached files to this post

- ⇗ attempt_halmacpi_patch.zip

#2469

Archimedes

Hello Everyone,
first let me thank you for your hard work, you are doing a great job!
I have the same issues that already cedar mentioned with your ACPI 5048 for XP x64 SP2 from Dietmars post #2202. I'm getting random BSODs with IRQ not less or equal 0x0000000A. I uninstalled nearly every Driver but i seems that the patched ACPI must be responsible. The BSODs are more likely to appear when e.g. playing a video file with mediaplayer classic or doing heavy downloads from the intel nic.
I tested with a x370 Crosshair VI Extreme, BIOS 7403 and a Ryzen 3800X.
I also get a yellow exclamation mark at the ACPI Embedded Conroller, which I didnt see in Diderus6 own Screenshots with the patched ACPI. And now comes something more pitty: On a intel x79 with full xp support i also tested for fun the patched ACPI and i am getting the same issues - also the exclamation mark at the ACPI embedded controller. So it can not be an issue with the ACPI tables in the BIOS, it must be a problem with the patched ACPI.
Any Ideas? Im willing to help and test! :) Thank you!
⇗

#2470

Archimedes

> Zitat von ⇗ diderius6 im Beitrag ¶ #2222

> @daniel_k
> This picture is based on the acpi.sys 5048 for XP 64 SP2 on Ryzen from post 2202
> Dietmar
> ⇗

Here in this post Dietmar dont have the exclamation mark at the ACPI embedded controller. Could it be because of the old Ryzen 1700? I used the new 3800x.

#2471

diderius6

⇗ @Archimedes
The embedded Acpi controller is not needed at all.
I make the experience, that XP 64 SP2 is much more instable than XP SP3, 32 bit.
On every compi, where I install XP SP3 it is stable (about 100 different motherboards I tested).
But only on one(!) motherboard, XP64 SP2 was stable, it is the Giga H110 board
Dietmar

#2472

Archimedes

> Zitat von ⇗ diderius6 im Beitrag ¶ #2471

> @Archimedes
> The embedded Acpi controller is not needed at all.
> I make the experience, that XP 64 SP2 is much more instable than XP SP3, 32 bit.
> On every compi, where I install XP SP3 it is stable (about 100 different motherboards I tested).
> But only on one(!) motherboard, XP64 SP2 was stable, it is the Giga H110 board
> Dietmar

Did you/some of you try XP x64 with a modded DSDT instead of a patched ACPI? Was the result more stable?

#2473

diderius6

⇗ @Archimedes
I have not tried. Where is sense to spend a lot of time when results are bad from the beginning?
When you read about your special BSODs from XP64 SP2,
they can be found everywhere from 2007 until now, for lan connections, for sound and so on.
This never happens for any version of XP 32 bit.
It has nothing to do with ACPI.
XP64 SP1 from 2005 was more stable
Dietmar

#2474

skullteria

> Zitat von ⇗ diderius6 im Beitrag ¶ #2473

> @Archimedes
> I have not tried. Where is sense to spend a lot of time when results are bad from the beginning?
> When you read about your special BSODs from XP64 SP2,
> they can be found everywhere from 2007 until now, for lan connections, for sound and so on.
> This never happens for any version of XP 32 bit.
> It has nothing to do with ACPI.
> XP64 SP1 from 2005 was more stable
> Dietmar

However, x64 is the presente and the future, several programs not be more compiled in x86, only x64. Windows XP X64 is the minimum to NT 5.X keep living

#2475

Archimedes

> Zitat von ⇗ diderius6 im Beitrag ¶ #2473

> @Archimedes
> I have not tried. Where is sense to spend a lot of time when results are bad from the beginning?
> When you read about your special BSODs from XP64 SP2,
> they can be found everywhere from 2007 until now, for lan connections, for sound and so on.
> This never happens for any version of XP 32 bit.
> It has nothing to do with ACPI.
> XP64 SP1 from 2005 was more stable
> Dietmar

Dont get me wrong, but I would not agree with that. I am using XP x64 SP2 since 2010 on AMD AM3 and Intel X79 and it is running rock stable - including a 980 TI.
Since the patched ACPI.sys runs flawless without BSODs (excl. the embedded controller) on my x79 build with XP x64, I think there must be still something missing for the ACPI 2.0 compatibility.

## Page 166

#2476

Mov AX, 0xDEAD

Some progress on windbg over NET for Windows XP
- port of kdnet.dll from windows 8.1 x32, support many qualcomm/intel/realtek/broadcom/emulex pci-e chips
- testing on VMware (thanks to embedded GDB server)
- guest OS = WindowsXP x32 PAE SP3 1CPU
- host OS = Windows7 x64
- test card = virtual Intel 8254x(e1000e) Gigabit network card
- currently need little ntoskrnl.exe patch for disabling ram-moving of kdnet.dll+kdstub.dll
- unresolved bug with losting connection windbg<->guestos
windbg log:

    Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Using NET for debugging
    Opened WinSock 2.0
    Waiting to reconnect...
    Connected to target 192.168.4.3 on port 50000 on local IP 192.168.4.1.
    Connected to Windows XP 2600 x86 compatible target at (Sat Sep 21 02:49:35.219 2019 (UTC + 5:00)), ptr64 FALSE
    Kernel Debugger connection established.

    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    OK                                             C:\Windows\Symbols
    Symbol search path is: C:\Windows\Symbols
    Executable search path is:
    Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
    Built by: 2600.xpsp.080413-2111
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    System Uptime: not available
    Break instruction exception - code 80000003 (first chance)
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for halmacpi.dll -
    nt!DbgBreakPoint:
    8052b5d0 cc              int     3
    kd> bu nt!MiReloadBootLoadedDrivers
    kd> g
    Breakpoint 0 hit
    nt!MiReloadBootLoadedDrivers:
    806a6e90 8bff            mov     edi,edi
    kd> p
    nt!MiReloadBootLoadedDrivers+0x2:
    806a6e92 55              push    ebp

#2477

diderius6

⇗ @Mov AX, 0xDEAD
This is a nice result (хорошая работа), because a lot of new compis
can only be debugged for XP via this way.
When you have kdnet.dll for XP,
I want to test
Dietmar
PS: Have you tested, at which point in bootprocess of XP SP3 windbg starts to work?

#2478 | infuscomus | anyone interested in the patcher program to add functions? i have source code if anyone would like to see it.
#2479 | diderius6 | ⇗ @infuscomus I am interested. Do you have a driver, which works now on this new XP 32, using integrated functions Dietmar

#2480

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #2477

> When you have kdnet.dll for XP,
> I want to test

OK, but i dont know when kdnet will be done, on real hardware (realtek and atheros lan chips) it not work yet.
p.s it's realy hard to debug "debug transport" on hardware, maybe i will have mix classic UART/COM transport with lan, so kernel will double output to both transports and will be possible to see on COM what's going with other transport

> Zitat von ⇗ diderius6 im Beitrag ¶ #2477

> PS: Have you tested, at which point in bootprocess of XP SP3 windbg starts to work?

- ntldr load NTOSKRNL(or variation like PAE/MP), then HAL, then bootvid.dll, then KD Transport (default KDCOM ), start NTOSKRNL
- NTOSKRNL load many bootdrivers but not start it
- NTOSKRNL at some init stage (phase0 in sources) start KD transport, init connection to windbg and break instantly if /BREAK option presented in boot.ini

#2481

Gelip

Yes, I confirm - for WinXP x64 SP2 to run under UEFI with the AnaPa driver you need:

- you must install >> !!! fresh !!! << WinXP in legacy mode using a card that will work later when booting in UEFI mode
- after first boot need install AnaPa driver
- copy my EFI files from beta longhorn server

It doesn't matter if you install the system on one FAT32 partition or on 100MB FAT32 + NTFS 5G (my way)
Tested hardware: GeForce 6200 LE PCI EXPRESS LEADTEK LR2A13 PCB REV:C on ASUS P8H61-M LE R2 with bios 0610. SATA disk mode set to IDE in bios:
⇗
P.S. I need make this test one more time but now with nVidia driver

#2482 | Gelip | Just one change of the graphics driver and the system does not boot in UEFI - only fresh WinXP x64 SP2 installation solve the problem.

#2483

diderius6

⇗ @Gelip
This brings me to the idea,
that it is important, which driver starts after which one.
But bootvid.dll and videoprt.sys have no entry in registry.
So I have no idea, how to change the loadorder of them
Dietmar
PS: May be, they have a hidden entry in hive "system".
Can you sent me a whole copy of your working hive "system"
and that one, which fails for UEFI boot and I compare them
via Beyond Compare 2.

#2484

diderius6

Just now I try to set up XP SP3 32 bit for UEFI boot on the Lenovo flex 10 notebook.
Nothing easy in this, because I noticed, that the installed Bios is 64 bit.
There is a 32 bit UEFI Bios for this notebook, but how to flash 64 bit Bios back to 32 bit Bios is another question.
In this moment I make a backup from the installed Win10 on NTFS GPT partition.
Thanks to ⇗ @infuscomus this is easy for me).
Oh my, my i920 compi with XP SP3 for daily use is about 10 times faster^^
Dietmar

#2485

Gelip

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #2483

> So I have no idea, how to change the loadorder of them
> PS: May be, they have a hidden entry in hive "system".
> Can you sent me a whole copy of your working hive "system"
> and that one, which fails for UEFI boot and I compare them
> via Beyond Compare 2.

I attach the system registry files for comparison. Maybe there is something to the Video option in GroupOrderList ???

> Zitat von ⇗ diderius6 im Beitrag ¶ #2484

> Just now I try to set up XP SP3 32 bit for UEFI boot on the Lenovo flex 10 notebook.
> Nothing easy in this, because I noticed, that the installed Bios is 64 bit.
> There is a 32 bit UEFI Bios for this notebook, but how to flash 64 bit Bios back to 32 bit Bios is another question.

You can probably program the old bios with the external programmer and I wrote you what and how on betaarchive: ⇗ https://www.betaarchive.com/forum/viewto...=444342#p444342
⇗
Gelip has attached files to this post

- ⇗ system_not_boot.zip
- ⇗ system_boot.zip

#2486

diderius6

⇗ @Gelip
Until now, I do not succeed to flash back the Lenovo flex 10 notebook from 64 bit to 32 bit Bios.
To extract only the Bios region and use insyde to flash this via win10 64 bit does not work.
The Intel CSME also not works, gives unknown error.
Universal BIOS Backup ToolKit 2.0.exe gives message "Bios cant be identified".
FD44Editor.exe also not works, brrr..
In win10 compi writes that Bios is flashed,
but on reboot appears message Error in flash process.
I can use the external Epromer, but then all information about compi
Uiid and Mac number is gone. With UEFI tool, only the Bios region can be seen,
no ME region etc.
With the external Epromer I can extract the whole 64 bit Bios.
But how to flash it back with Bios 32 bit,
so that Mac etc. is not gone, I dont know
Dietmar

#2487

dencorso

> Zitat

> anyone interested in the patcher program to add functions? i have source code if anyone would like to see it.

⇗ @infuscomus:
Yes, I do. If you can provide both the executable and the source code, even better. Thanks in advance.
Changing subjects: give ⇗ this a look. There you'll find injective code that might be useful for what, IMO, ought to be a properly done kernelex. I think the cleanest way to do that is to inject code at the run time images of kernel32.dll advapi.dll and some other processes, and use that code to redirect requests for missing functions to modules providing them. If that can be done at Ring 0 level, by means of a pseudo-driver, even better, because then hal.dll and krnl*.exe could also be modified without any direct patching of any M$ files. Just my 2¢, of course...
Keep on the great work!

#2488

diderius6

I succeed to read out the whole 64 bit Bios from Lenovo flex 10 notebook with its own
Insyde.exe tool.
For this I set in platform.ini
[BackupROM]
Flag=1
FilePath=
FileName=
This writes the full (?) original Bios to the place, from where it is called.
Can somebody take a look at this file, if UUID, Mac and serial number are correct in this file?
And my question is: When I flash the Bios 32 bit from website
and add there the Me and Gbe region from this 64 bit Bios via UEFI tool before flashing with Epromer,
will this 32 Bit Bios work
Dietmar
diderius6 has attached files to this post

- ⇗ Flex10.rar
- ⇗ Ready32forFlashhh.rar

#2489

diderius6

⇗ @Gelip
I compare both System files.
In System, where it boots,
the monitor is not specified.
And the compi seems to use the original vga.sys instead of the anapa driver
Dietmar
PS: The differences in Registry could be tested one by one, which would be a really hard work.
diderius6 has attached files to this post

- ⇗ rptA7008.rar

#2490

PPeti66x

Hi!
ACPI Embedded controller exclamation can be solved by installing a null-driver (as in original case in Longhorn/Vista)
Here are the modified inf files. Copy the correct inf to the Windows\Inf folder (backup the original file first), then uninstall the Embedded controller, then reinstall it.
PPeti66x has attached files to this post

- ⇗ acpi_inf_for_Longhorn5048.zip

## Page 167

#2491 | infuscomus | ⇗ @diderius6 ⇗ @dencorso I PMed you the kernel patcher program with source code.

#2492

XPLives

⇗ @skullteria

> Zitat von ⇗ skullteria im Beitrag ¶ #2474

> > Zitat von ⇗ diderius6 im Beitrag ¶ #2473

> > @Archimedes
> > I have not tried. Where is sense to spend a lot of time when results are bad from the beginning?
> > When you read about your special BSODs from XP64 SP2,
> > they can be found everywhere from 2007 until now, for lan connections, for sound and so on.
> > This never happens for any version of XP 32 bit.
> > It has nothing to do with ACPI.
> > XP64 SP1 from 2005 was more stable
> > Dietmar

> However, x64 is the presente and the future, several programs not be more compiled in x86, only x64. Windows XP X64 is the minimum to NT 5.X keep living

Actually I have to disagree. There is no need to force XP Pro 64-Bit.
Server 2003 Data Center Edition 32-Bit would be the best NT 5.X version for the future if you want XP 32-Bit compatibility with enhanced memory and GPT support. 2003 Server R2 64-Bit might be the best version if you must push to 64-Bit with the smallest OS foot print as far as total installed size and maximum memory support.
For true 64-Bit I'd use Vista Ultimate only because of Quick Launch and Classic Themes or Windows 7 Enterprise 64-Bit or Server 2012 R2 due to gaming compatibility that XP 64-Bit or 2003 64-Bit just can't play anything DX11+ and restricted to DX9. Why go through all that trouble? Is there some specific XP Pro 64-Bit software that doesn't work in Vista/Windows 7 64-Bit?
2003 Server 32-Bit / 2012 Server R2 64-Bit (These two OS are really all you'll need to run almost 95%) software.

#2493

XPLives

@gelip

> Zitat von ⇗ Gelip im Beitrag ¶ #2481

> Yes, I confirm - for WinXP x64 SP2 to run under UEFI with the AnaPa driver you need:
> - you must install >> !!! fresh !!! << WinXP in legacy mode using a card that will work later when booting in UEFI mode
> - after first boot need install AnaPa driver
> - copy my EFI files from beta longhorn server
> It doesn't matter if you install the system on one FAT32 partition or on 100MB FAT32 + NTFS 5G (my way)
> Tested hardware: GeForce 6200 LE PCI EXPRESS LEADTEK LR2A13 PCB REV:C on ASUS P8H61-M LE R2 with bios 0610. SATA disk mode set to IDE in bios:
> ⇗
> P.S. I need make this test one more time but now with nVidia driver

Gelip since you have access to the beta files archive there can you tell me if you know if it exists?
Is there any beta of Server 2003 64-Bit or XP Pro 64-Bit that had the WINNT.EXE for DOS based installation setup file?
Or even a beta of Vista 32-Bit/64-Bit WINNT.EXE DOS based installation setup file?
Another idea was there any XP x64 Itanium Edition that had a DOS WINNT.EXE installer?

#2494 | infuscomus | ⇗ @XPLives there is an XP x64 Itanium Edition available here ⇗ https://winiso.pl/windows-desktop/windows-xp it is dated 3/27/2003

#2495

diderius6

I make some more tests with the Lenovo Flex 10 notebook.
It is impossible to flash via FPTw, always message error 63, hardware platform not supported.
And Me tool shows Me version 1.0.2.1060 (I think from 2013).
So, only Epromer will do this job.
On the grafik card gpu-z shows empty box for UEFI rom on grafikcard,
so best chances to get XP SP3 to boot via UEFI there.
This Bios has an integrated INT10, which works for the grafikcard also in win10(!)
even when you disable all CSM, "pur" Uefi
Dietmar
PS: 3Dmark2001 gives for Win10 64 bit 5387 points on this notebook.
I think, under XP 32 bit it will be faster, lets test^^.

#2496

XPLives

⇗ @infuscomus c

> Zitat von ⇗ infuscomus im Beitrag ¶ #2494

> @XPLives
> there is an XP x64 Itanium Edition available here
> ⇗ https://winiso.pl/windows-desktop/windows-xp
> it is dated 3/27/2003

I believe that's XP Pro 64 Bit.
Can you confirm that's the IA64 version?
Itanium Edition is dated 2001 around the same time as XP Gold.
I found a info link about it.
⇗ https://msdn.su/downloads/operating-syst.../itanium/ja/iso
Since it was dated 2001 I have a feeling it might have included a 64-Bit DOS installer.

#2497

Gelip

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #2495

> On the grafik card gpu-z shows empty box for UEFI rom on grafikcard,
> so best chances to get XP SP3 to boot via UEFI there.

What version of bios do you have now in Flex10?

#2498

infuscomus

> Zitat von ⇗ XPLives im Beitrag ¶ #2496

> Can you confirm that's the IA64 version?

Yep, downloaded and it's definitely an IA64 version - the rest of them are AMD64 versions

#2499

Mov AX, 0xDEAD

> Zitat von ⇗ Gelip im Beitrag ¶ #2485

> @diderius6

> > Zitat von ⇗ diderius6 im Beitrag ¶ #2483

> > that it is important, which driver starts after which one.
> > But bootvid.dll and videoprt.sys have no entry in registry.
> > So I have no idea, how to change the loadorder of them

> I attach the system registry files for comparison. Maybe there is something to the Video option in GroupOrderList ???

bootvid & videoprt is not boot drivers, they are kernel mode dll and auto-loaded if some other linked to them
ntoskrnl has dependies to bootvid
vga/nt4_mini/rdpcdd/dxapi have dependies to videoprt

#2500 | diderius6 | ⇗ @Gelip Until now it is its original 93CN52WW(V9.2).64bit Soon I change Bios to 32bit 93cn19ww(v5.2&v3.7) Dietmar

#2501

Gelip

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #2495

> On the grafik card gpu-z shows empty box for UEFI rom on grafikcard

GPU-Z shows an empty box in Windows which is launched in Legacy bios mode and uses VBIOS.
A ticked box means that Windows is in UEFI mode with CSM turned off and Secure Boot turned on.
64-bit bios 93CN52WW have VBIOS and GOP firmware but 32-bit bios 93cn19ww have only GOP firmware:
⇗

#2502 | Gelip | Probably this 32-bit bios have no legacy (CSM) support only pure UEFI ??
#2503 | diderius6 | ⇗ @Gelip Hm, this gives me to think, if it would not be better to make some tests before with XP on the 64 bit Bios. Do you know any Bios flash tool, with which you dont have to use Epromer on such a notebook Dietmar

#2504

Gelip

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #2503

> Do you know any Bios flash tool, with which you dont have to use Epromer on such a notebook

I have never programmed a chip in a system PCB without desoldering. Apparently on some devices you can use the test clip SOIC8 e.g. on ThinkPad X220:
⇗ Coreboot on the ThinkPad X220 with a Raspberry Pi
It's possible that you can do it on Flex10. Instead of raspberry you can use e.g. USB CH341A and flashrom for Linux

#2505 | Gelip |

## Page 168

#2506

XPLives

> Zitat von ⇗ Gelip im Beitrag ¶ #2502

> Probably this 32-bit bios have no legacy (CSM) support only pure UEFI ??

What laptops and desktops have only pure 32-Bit UEFI only mode and no CSM?
Are there any desktop UEFI 64-Bit MBs that can be converted to run in pure UEFI 32-Bit for testing?
It will be easier to test using the 32-Bit DOS installer unless WINNT.EXE can be modified to bypass file checking then I might be able to test the 64-Bit version using the same method.

#2507

diderius6

⇗ @Gelip
You are right: No INT10 at all in the 32 bit UEFI Bios for the Flex 10 Lenovo notebook.
But in the 64 bit UEFI Bios there is full CSM support and INT10 can be found in Bios for the graphik *.dxe driver
Dietmar
EDIT: Instead to force all to UEFI, it would be a better idea, to implement something like a generic CSM driver in UEFI Bios.
Now I dont know, how to make this, but when CSM documentation is open source, it could be possibel.

#2508

Andalu

Once again I have read the entire thread from the first page looking for a solution to make USB3 working in all of my motherboards.
Until now, the usb3 works on two boards by installing the modded driver only while on the other it doesn't work. For them, with all probability, I need to modify the DSDT table. I saw the posts ¶ #1445, ¶ #1854, ¶ #1856, ¶ #1858, and ¶ #1865 where ⇗ @diderius6 explain the procedure but I have some difficult to understand some points like: "Extract with UEFI tool your DSDT table. From this raw file make dsdt.dsl with the tool iasl in commandline C:\ iasl dsdt.raw"" and "Do the mod in DSDT as in post 1442".
For example, how to extract the DSDT table with UEFI tool? I tried to extract it from a .rom file but I can't get a .raw file. And how to make the mod in DSDT as in post ¶ #1442 for other boards unlike ASRock Z370?
So, here my request (I think it can be useful for other users too):
is there someone that can explain the method, step by step and in the simplest way, to extract, decompile, modify and recompile the DSDT table, please?
Thanks in advance.

#2509

dencorso

> Zitat von ⇗ Andalu im Beitrag ¶ #2508

> Until now, the usb3 works on two boards by installing the modded driver only while on the other it doesn't work.

Could you please tell which boards/processors the modded driver alone worked for and which it didn't? Moreover, did you try including also the modded acpi.sys for the board/processor the modded usb3 drivers alone were insufficient to make USB3 working? Thanks in advance!

#2510

lsmlcx

> Zitat von ⇗ dencorso im Beitrag ¶ #2509

> > Zitat von ⇗ Andalu im Beitrag ¶ #2508

> > Until now, the usb3 works on two boards by installing the modded driver only while on the other it doesn't work.

> Could you please tell which boards/processors the modded driver alone worked for and which it didn't? Moreover, did you try including also the modded acpi.sys for the board/processor the modded usb3 drivers alone were insufficient to make USB3 working? Thanks in advance!

ASUS z170-k worked with xp sp3 x86 on intel usb3, not 2003 sp2 x86.
ASUS z170-a cann't worked on intel usb3.
The xhci device cann't be started under error code 39 with model acpi.sys and usb3.

#2511

Andalu

⇗ @dencorso
Thanks for your reply. I installed the USB3 modded driver and the acpi system file (5048) for all my boards.
The USB3 works on:
- Asrock B250M Pro4 and i5-6600 Skylake;
- Asrock B75 Pro3-M and i5-3470 Ivy Bridge.
It doesn't work on:
- Msi CSM-Q87M-E43 and i7-4770K Haswell;
- Acer IPIMB-AR Rev 1.02A and i7-3770K Ivy Bridge;
- Asrock B75M-GL R2.0 (so similar to B75 Pro3-M) and i7-3770 Ivy Bridge.
For each board where USB3 fails, I have tried an XPSP3 32bit fresh installation with acpi.sys (5048) packed into i386 folder, driver.cab and SP3.cab. I have also tried an XP installation with Universal 32bit Intel RST AHCI+RAID driver v11.2.0.1006 mod+signed by Fernando only and after I have installed the driver modded and copied acpi.sys in the system32\driver folder from another pc. In both cases the driver has properly installed with no errors but the usb3.0 ports act as USB2.0. In the bios, the options seem to be set correctly. So, I think that the only solution is a modded DSDT table.

#2512 | infuscomus | I recall edit: dencorso mentioned earlier -> here ¶ Windows XP SP3 32bit and modern PC parts (141) in this thread that at some point one of the ntoskrnl updates for XP breaks Intel USB 3.0 and stops it from working. I don't know when exactly it broke, but from my testing I know that up to version 5.1.2600.6748 USB 3.0 still works.
#2513 | Andalu | In my tests i used the same version of ntoskrnl.exe (5.1.2600.5512) for all boards.
#2514 | infuscomus | ⇗ @Andalu which of the USB 3.0 drivers have you tested? there are several versions in this thread
#2515 | Andalu | ⇗ @infuscomus Here I found two version of the modded driver, one is ¶ AMDXHCI_XP_FINAL and another is ¶ USB3bestforIntel. Both with no differences on my boards where USB3 doesn't work. Is there another version?

#2516

infuscomus

⇗ @Andalu
here are a few USB 3.0 drivers to try
amdxhci <- works for me with patched acpi.sys and ntoskrnl 6748
renesas
¶ Windows XP SP3 32bit and modern PC parts (128)
VIA usb 3.0 driver
¶ Windows XP SP3 32bit and modern PC parts (89)
I think there is an Etron driver too somewhere in this thread but I can't remember what page it was on.

#2517 | lsmlcx | ⇗ @infuscomus where is the ntoskrnl 6748?

#2518

infuscomus

⇗ @lsmlcx
here is the multiprocessor version - if you need uniprocessor just ask
you may need to rename them
ntkrnlmp -> ntoskrnl
ntkrpamp -> ntkrnlpa
infuscomus has attached files to this post

- ⇗ ntkrnlmp-6748.zip
- ⇗ ntkrpamp-6748.zip

#2519

Doc.Brown

> Zitat von ⇗ infuscomus im Beitrag ¶ #2518

> @lsmlcx
> here is the multiprocessor version - if you need uniprocessor just ask
> you may need to rename them
> ntkrnlmp -> ntoskrnl
> ntkrpamp -> ntkrnlpa

Do you think thoose files could help with XP SP3 x86 compatibility for my Maximus XI Gene ? I tried lot of things(acpi504,different AHCI drivers) but I'm already stuck with BSOD A5(0x00010006,0x8a275098,0x00000000,0x00000000) or the only solution is to mod the bios to add XP compatibility(impossible for me cause I haven't necessary knowledge) ?
I'm only able to finish OS installation by pressing F5 or F7 for now,USB work well in XP and have 1 core or 6 core if I choose Standard PC or Multiprocessor MPS in F5 option,the big problem is with Asus TurboV that don't install properly(DLL problem).For (extreme) overclocking this software is very usefull unfortunately :/
I also tried to make a ghost after install on X299 Rampage VI Apex but result on this BSOD on Gene too.
Thanks.

#2520

diderius6

⇗ @Doc.Brown
BSOD A5 with
0x10006 : ACPI_LINK_NODE_CANNOT_BE_DISABLED
ACPI found a link node, but cannot disable it. Link nodes must
be disable to allow for reprogramming
2 - Pointer to the link node. This device is missing the _DIS method.
I think, it can be hacked in any acpi.sys
Dietmar

## Page 169

#2521 | infuscomus | ⇗ @Doc.Brown I doubt it will help, but you might as well try anyway. concerning BSOD A5(0x00010006,0x8a275098,0x00000000,0x00000000) ⇗ @diderius6 ⇗ @daniel_k any ideas?
#2522 | Andalu | ⇗ @infuscomus Thanks for your help ;) I tried all the driver suggested and also the ¶ Etron but even if correctly installed the USB3 doesn't work as really USB3. Also using the updated version for ntoskrnl and ntkrnlpa doesn't help. I think that the only way is to modify the DSDT table. I'm still hoping for someone that can explain "how to do".

#2523

diderius6

⇗ @Doc.Brown
Make a try with this acpi.sys,
it is for XP 32 bit,
just small hack
Dietmar
diderius6 has attached files to this post

- ⇗ acpi.rar

#2524 | Doc.Brown | ⇗ @diderius6 My poor knowledge doesn't allow me to understand what it is related to but I guess if it could be hacked it will be wonderful ! I'll test your ACPI file so much thanks ;) ⇗ @infuscomus as USB works for me I think I will not test for now so,thanks for your reply

#2525

PPeti66x

For those, who want make experiments with USB3 kernel compatibility, I collected all kernel updates beginning with 5.1.2600.6748:
⇗ https://drive.google.com/file/d/1Wm7Wvbd...yl6CK_sp1w/view
I can not test it, because both of my computers works correctly with the latest kernel known to be incompatible with some systems.
My USB3 experiences on Windows XP 32-bit:
Computer-1: ASRock Fatal1ty Z77 Professional, I7 3770 (non-k) CPU (Ivy bridge), BIOS v1.70-beta (in v1.90-beta one of my HDDs is not recognized)
USB3 (modded AMD driver) can be installed without changing the ACPI.SYS - but the null-driver must be uninstalled first. But also works with the ACPI 5048 from Longhorn. Everything seems to working OK, USB3 speeds really achieved (120 MiB/s reading, which is the limit of my pendrive).
This mainboard have Etron USB3 - this works on XP with official drivers, but these are unstable - causes BSOD cca. on every 2 weeks when I returning from standby mode, and sometimes in other cases.
Computer-2: Dell Precision M4800, chipset QM87, CPU 4810MQ (Haswell), BIOS A25 (30 okt 2018)
USB3 (modded AMD driver) can be installed only after updating ACPI.SYS to the ACPI 5048 from Longhorn (works with original and patched too). But this notebook have some switching mechanism: if compatible OS detected, ports are switched to USB3 controller, else to USB2 controller. Switching from USB3 to USB 2 requires restarting 2 times, but from USB2 to USB3 is switched instantly. So if I switching from Windows 7 to Windows XP 1st time, the ports will work in USB3 mode (USB3 speeds really achieved - 120MiB/s read speed, limited by pendrive), but if i start XP 2nd time, I will have only USB2.
There are also minor problems with ACPI.SYS 5048:
1. I can not use Fn-keys to set display brightness
2. Switching between internal and external display by Fn key does not work
3. Because of 2 graphics cards (in-CPU and nVidia Quadro), if display is turned off, it can not be turned on by normal way (XP probably switches to in-CPU graphics, which is non-working, because only 1 driver can be loaded at once). The only program which can reenable the display is the MultiMonitorTool by NirSoft with the switch command. But when I returning from standby, the login password must be entered without display (not always, but mostly).
Problems Solved by ACPI.SYS 5048:
1. Possible to install USB3 driver - but switching mechanism is still not resolved
2. Sleep mode works (with the original version it always failed)

#2526

diderius6

⇗ @Doc.Brown
A more elegant way is to put the missing
Method (_DIS, 0, NotSerialized) // _DIS: Disable Device
{
}
in DSDT of Bios from Gene board at the end of the crashing device
Dietmar

#2527

infuscomus

⇗ @PPeti66x
thanks very much for these!
KB3033395(5.1.2600.6748-OK)
KB3134146(5.1.2600.7005-OK) - tested - OK
KB3140410(5.1.2600.7017-?)
KB3153171(5.1.2600.7053-?)
KB3175024(5.1.2600.7121-?)
KB3191256(5.1.2600.7146-?)
KB4011981(5.1.2600.7197-?)
KB4018490(5.1.2600.7259-OK) - tested - OK
KB4056615(5.1.2600.7392-?)
KB4101864(5.1.2600.7459-OK) - tested - OK
KB4230467(5.1.2600.7494-X) - tested - Code 39
KB4463103(5.1.2600.7581-X)
KB4486463(ntkrnlmp.exe only)(5.1.2600.7649-X)

#2528

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #2526

> @Doc.Brown
> A more elegant way is to put the missing

>      Method (_DIS, 0, NotSerialized)  // _DIS: Disable Device
>                  {
>                  }

> in DSDT of Bios from Gene board at the end of the crashing device
> Dietmar

I don't know what is DSDT,I'm totaly noob with that sadly :( I'm open for learn how to do it if you wan't to learn it to me but it will be very long I think cause I start from 0 :/
Just tested the hacked ACPI file and BSOD has changed now as you can see on the pic below :
⇗
And,not sure if it's linked or could help,the Asus TurboV error message after press F5 and choose "MPS multiprocessor" to be able to have complete installation :
⇗
I'm using 0057 bios below : ⇗ M11G-0057
but new 0022 is also good : ⇗ M11G-0022
Thanks.

#2529

diderius6

⇗ @Doc.Brown
Try this acpi.sys.
When it not works,
I am out of ideas just now
Dietmar
diderius6 has attached files to this post

- ⇗ acpi.rar

#2530

XPLives

⇗ @PPeti66x

> Zitat von ⇗ PPeti66x im Beitrag ¶ #2525

> For those, who want make experiments with USB3 kernel compatibility, I collected all kernel updates beginning with 5.1.2600.6748:
> ⇗ https://drive.google.com/file/d/1Wm7Wvbd...yl6CK_sp1w/view
> I can not test it, because both of my computers works correctly with the latest kernel known to be incompatible with some systems.
> My USB3 experiences on Windows XP 32-bit:
> Computer-1: ASRock Fatal1ty Z77 Professional, I7 3770 (non-k) CPU (Ivy bridge), BIOS v1.70-beta (in v1.90-beta one of my HDDs is not recognized)
> USB3 (modded AMD driver) can be installed without changing the ACPI.SYS - but the null-driver must be uninstalled first. But also works with the ACPI 5048 from Longhorn. Everything seems to working OK, USB3 speeds really achieved (120 MiB/s reading, which is the limit of my pendrive).
> This mainboard have Etron USB3 - this works on XP with official drivers, but these are unstable - causes BSOD cca. on every 2 weeks when I returning from standby mode, and sometimes in other cases.
> Computer-2: Dell Precision M4800, chipset QM87, CPU 4810MQ (Haswell), BIOS A25 (30 okt 2018)
> USB3 (modded AMD driver) can be installed only after updating ACPI.SYS to the ACPI 5048 from Longhorn (works with original and patched too). But this notebook have some switching mechanism: if compatible OS detected, ports are switched to USB3 controller, else to USB2 controller. Switching from USB3 to USB 2 requires restarting 2 times, but from USB2 to USB3 is switched instantly. So if I switching from Windows 7 to Windows XP 1st time, the ports will work in USB3 mode (USB3 speeds really achieved - 120MiB/s read speed, limited by pendrive), but if i start XP 2nd time, I will have only USB2.
> There are also minor problems with ACPI.SYS 5048:
> 1. I can not use Fn-keys to set display brightness
> 2. Switching between internal and external display by Fn key does not work
> 3. Because of 2 graphics cards (in-CPU and nVidia Quadro), if display is turned off, it can not be turned on by normal way (XP probably switches to in-CPU graphics, which is non-working, because only 1 driver can be loaded at once). The only program which can reenable the display is the MultiMonitorTool by NirSoft with the switch command. But when I returning from standby, the login password must be entered without display (not always, but mostly).
> Problems Solved by ACPI.SYS 5048:
> 1. Possible to install USB3 driver - but switching mechanism is still not resolved
> 2. Sleep mode works (with the original version it always failed)

Interesting list of kernel updates. Maybe you can add the date of each kernel update next to it so it will be more helpful.
Although I think most people will use mainly the original SP0, SP1, SP2, SP3 versions. Any post SP3 kernel I doubt many will be using but would be interesting to see if all post SP3 updates work at all with the USB modded drivers.
Which specific USB 3.0 modded driver do you test the 120MiB/s read speed on? Can you link the file and I will retest.
This was on your Intel USB 3.0 ports on your Z77?
Try doing a sustained transfer rate reading a Blu-ray movie .m2ts video stream playback and see if it hiccups during the movie playback at any point.
Next try transferring a 100GB file from one USB hard drive to another USB hard drive using both Intel USB 3.0 ports and time the duration.
For your Z77 you should use BIOS v1.00, don't use the BETA. Or use the latest version and repeat the test.
This is a common problem with notebooks using nVidia shared with Intel iGPU. You will not see the discrete graphics card in a notebook and only the Intel iGPU in Windows XP. This is why only Ivy Bridge and earlier chipsets should be used for notebooks and XP if you wish to use it for 3D gaming. Most nVidia with Haswell and later are post XP driver support.
"1. I can not use Fn-keys to set display brightness
2. Switching between internal and external display by Fn key does not work"
These are related to the software that was preinstalled for that notebook to use those Function keys to perform a function. If you installed a clean XP those normally will not function at all without adding the software. Usually this software comes preinstalled with the OS together when you first bought it and sometimes there is no stand alone installer provided by the manufacturer website to do it with a clean XP install. It might be possible to extract the registry entries and the driver files and copy them over to a clean XP installation and make it work but not an easy task.
Also I don't think there should be any need to install the modded ACPI for Haswell or Broadwell. Both should install XP clean without BSOD A5 issues.
"USB3 (modded AMD driver) can be installed only after updating ACPI.SYS to the ACPI 5048 from Longhorn (works with original and patched too)."
What happens do you get an Error Code when installing AMD USB 3.0 modded driver on regular XP ACPI.SYS?

#2531 | kukonosau | Where is chipset drivers for Windows XP x86 and x64 and Windows 7 x86 and x64 for Ryzen? I have sometimes lagging several games in all systems besides Windows 10. This problem with processors or motherboard? Or absents chipset drivers?

#2532

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #2529

> @Doc.Brown
> Try this acpi.sys.
> When it not works,
> I am out of ideas just now
> Dietmar

⇗ @diderius6
Thanks again I will test it as soon as possible(this weekend I think cause I have to buy another pack of CD-R :D )

#2533 | infuscomus | So based on my testing hotfix KB4230467 for ntoskrnl introduces a bug that breaks the generic USB 3.0 driver for XP.

#2534

PPeti66x

⇗ @XPLives
About speed test:
A 3.27 GiB MKV file was copied from Pretec REX 150 64-GB pendrive to HDD, so it was only a fast testing. The copied file was not cached in memory before (it was copied to pendrive weeks earlier).
In both cases test was made on Intel USB3 with AMD modded driver (AMDXHCI_XP_FINAL.rar: ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (128)).
The Etron controller can not achieve even 60 MiB/s with the official drivers. I am not tested AMD driver on the Etron controller.
On both cases on Windows XP was applied all non-SSE2 updates up to May 2019
"Next try transferring a 100GB file from one USB hard drive to another USB hard drive using both Intel USB 3.0 ports and time the duration."
To prove that ports working in USB3 mode, that test was enough. Both the WD VelociRaptor (cca. 140 MiB/s sequential write speed on the selected defragmented partition) and Samsung SSD HDDs had higher speed. Maybe I will do some other tests to check for the data integrity (the transferred MKV file had correct MD5 checksum).
About BIOS version:
In case of the Z77 motherboard, I am using this version many years. Because this motherboard have official Windows XP support, I think, BIOS version not affects the USB3 (by changelog, only DRAM compatibility was improved). The beta BIOS was released in November 2013 (the regular 1.70 in June 2013). I never see the BIOS v1.00, it was 1.3 and some alphabetical subversion.
"These are related to the software that was preinstalled for that notebook to use those Function keys to perform a function."
The mentioned 2 function is provided by the XP ACPI.SYS file (correctly works on SP3, and on x64 SP2). But it was not implemented in longhorn 5048 version, or some dependencies missing from the XP system.
On M4800 was possible to install near everything by extrancting the diver files from the installers. Some of the drivers was hard to find on the manufacrurer site, because packages provided by Dell sometimes lacked the XP driver version. Functioning of the Free Fall Sensor is questionable (Win7 driver was installed), but by the Device Manager it works correctly. Also the Intel management engine is older, than required. The device manager not shows any unknown or non-working hardware.
"What happens do you get an Error Code when installing AMD USB 3.0 modded driver on regular XP ACPI.SYS?"
The device is simply not found by Windows XP (not listed in Device Manager). After replacing the ACPI.SYS with the Longhorn version, a new unknown hardware is found, and is possible to install the device driver. After installing the modded driver and reverting the ACPI.SYS, the device driver not shows, and USB3 is disfunctional (no errors displayed). Longhorn 5048 ACPI.SYS is required only for Gen-4 (Haswell) and later mainboards. Patched version is required by a newer (Gen-6 or Gen-7 and later) mainboards.
Windows XP (32-bit) Kernel update dates (compile date time stamp in ntoskrnl.exe, Y.M.D H:M:S):
KB3033395, 5.1.2600.6748, 2015.02.06 07:14:27
KB3134146, 5.1.2600.7005, 2016.01.21 02:43:40
KB3140410, 5.1.2600.7017, 2016.02.05 16:36:08
KB3153171, 5.1.2600.7053, 2016.03.31 15:35:58
KB3175024, 5.1.2600.7121, 2016.08.16 00:08:27
KB3191256, 5.1.2600.7146, 2016.10.04 07:43:28
KB4011981, 5.1.2600.7197, 2017.02.10 06:39:21
KB4018490, 5.1.2600.7259, 2017.04.28 05:33:39
KB4056615, 5.1.2600.7392, 2017.12.05 19:47:10
KB4101864, 5.1.2600.7459, 2018.04.12 23:32:37
KB4230467, 5.1.2600.7494, 2018.05.20 17:10:49
KB4463103, 5.1.2600.7581, 2018.09.12 17:02:19
KB4486463, 5.1.2600.7649, 2019.01.08 17:48:43 (ntkrnlmp.exe)
⇗ @infuscomus
"So based on my testing hotfix KB4230467 for ntoskrnl introduces a bug that breaks the generic USB 3.0 driver for XP."
This was a great find!

#2535

diderius6

⇗ @Doc.Brown
Make a try with this Bios for the Gene XI board.
It is original Bios from Asus for the Gene XI board, but now not avaible on their website.
In its DSDT table, the _DIS is treated in another way
Dietmar
⇗ https://www.dropbox.com/s/py7qjgousqov3a...S-0057.rar?dl=0

## Page 170

#2536

XPLives

⇗ @PPeti66x

> Zitat von ⇗ PPeti66x im Beitrag ¶ #2534

> @XPLives
> About speed test:
> A 3.27 GiB MKV file was copied from Pretec REX 150 64-GB pendrive to HDD, so it was only a fast testing. The copied file was not cached in memory before (it was copied to pendrive weeks earlier).
> In both cases test was made on Intel USB3 with AMD modded driver (AMDXHCI_XP_FINAL.rar: ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (128)).
> The Etron controller can not achieve even 60 MiB/s with the official drivers. I am not tested AMD driver on the Etron controller.
> On both cases on Windows XP was applied all non-SSE2 updates up to May 2019
> "Next try transferring a 100GB file from one USB hard drive to another USB hard drive using both Intel USB 3.0 ports and time the duration."
> To prove that ports working in USB3 mode, that test was enough. Both the WD VelociRaptor (cca. 140 MiB/s sequential write speed on the selected defragmented partition) and Samsung SSD HDDs had higher speed. Maybe I will do some other tests to check for the data integrity (the transferred MKV file had correct MD5 checksum).
> About BIOS version:
> In case of the Z77 motherboard, I am using this version many years. Because this motherboard have official Windows XP support, I think, BIOS version not affects the USB3 (by changelog, only DRAM compatibility was improved). The beta BIOS was released in November 2013 (the regular 1.70 in June 2013). I never see the BIOS v1.00, it was 1.3 and some alphabetical subversion.
> "These are related to the software that was preinstalled for that notebook to use those Function keys to perform a function."
> The mentioned 2 function is provided by the XP ACPI.SYS file (correctly works on SP3, and on x64 SP2). But it was not implemented in longhorn 5048 version, or some dependencies missing from the XP system.
> On M4800 was possible to install near everything by extrancting the diver files from the installers. Some of the drivers was hard to find on the manufacrurer site, because packages provided by Dell sometimes lacked the XP driver version. Functioning of the Free Fall Sensor is questionable (Win7 driver was installed), but by the Device Manager it works correctly. Also the Intel management engine is older, than required. The device manager not shows any unknown or non-working hardware.
> "What happens do you get an Error Code when installing AMD USB 3.0 modded driver on regular XP ACPI.SYS?"
> The device is simply not found by Windows XP (not listed in Device Manager). After replacing the ACPI.SYS with the Longhorn version, a new unknown hardware is found, and is possible to install the device driver. After installing the modded driver and reverting the ACPI.SYS, the device driver not shows, and USB3 is disfunctional (no errors displayed). Longhorn 5048 ACPI.SYS is required only for Gen-4 (Haswell) and later mainboards. Patched version is required by a newer (Gen-6 or Gen-7 and later) mainboards.
> Windows XP (32-bit) Kernel update dates (compile date time stamp in ntoskrnl.exe, Y.M.D H:M:S):
> KB3033395, 5.1.2600.6748, 2015.02.06 07:14:27
> KB3134146, 5.1.2600.7005, 2016.01.21 02:43:40
> KB3140410, 5.1.2600.7017, 2016.02.05 16:36:08
> KB3153171, 5.1.2600.7053, 2016.03.31 15:35:58
> KB3175024, 5.1.2600.7121, 2016.08.16 00:08:27
> KB3191256, 5.1.2600.7146, 2016.10.04 07:43:28
> KB4011981, 5.1.2600.7197, 2017.02.10 06:39:21
> KB4018490, 5.1.2600.7259, 2017.04.28 05:33:39
> KB4056615, 5.1.2600.7392, 2017.12.05 19:47:10
> KB4101864, 5.1.2600.7459, 2018.04.12 23:32:37
> KB4230467, 5.1.2600.7494, 2018.05.20 17:10:49
> KB4463103, 5.1.2600.7581, 2018.09.12 17:02:19
> KB4486463, 5.1.2600.7649, 2019.01.08 17:48:43 (ntkrnlmp.exe)
> @infuscomus
> "So based on my testing hotfix KB4230467 for ntoskrnl introduces a bug that breaks the generic USB 3.0 driver for XP."
> This was a great find!

Thanks for including the time stamps! Are the version numbers extracted from the ntoskrnl.exe file except the last one?
Now we need to add the version and time stamps for XP SP0, SP1, and SP2 along side these for reference. Other kernels are Server 2003 32-Bit, XP POS 2009 32-Bit for comparison and possible testing. There was also XP Media Center Edition.
This is very fascinating you got 140MB/s speeds on Intel USB 3.0 -> Intel USB 3.0 ports and compared to the Etron much faster?
For your single file 100GB test on Intel USB 3.0 port to Intel USB 3.0 port can you give me the time duration Minutes, Seconds.XX that elapsed?
I haven't tested mine but let's see if we match BIOS versions if this affects.
I will upload my rare v1.00 BIOS to share with you.
You run the program within XP and it will flash it back to genuine v1.00 and once rebooted you will have BIOS v1.00 :)
This was the first BIOS version released for the Fatal1ty splash logo. It's a bit strange seeing it for the time if you've been used to v1.70 Beta all this time.
If you can repeat your tests on BIOS V1.00 to see if any changes are noticed.
One final test is to reinstall XP using F7 or F5 NO ACPI mode which should force it to MPS mode and try all the USB 3.0 modded drivers again with the different kernel versions to see if that affected anything.
If we can isolate which modded drivers work in both modded ACPI and NO ACPI modes this is the best driver choice. Keep note of which kernel version had success.
The reason I mentioned the Function Key issue was software related is even when I install XP clean onto VAIO laptop all Function Keys on top do nothing unless you install the correct software and registry patches. And I think on the VAIO they did not have a stand alone installer for this. It was integrated into the XP install with all the other bloated software when the laptop is brand new or using the recovery disc images.
XPLives has attached files to this post

- ⇗ Z77FAT10.ZIP

⇗ u10321_XPLives.html

#2537

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #2535

> @Doc.Brown
> Make a try with this Bios for the Gene XI board.
> It is original Bios from Asus for the Gene XI board, but now not avaible on their website.
> In its DSDT table, the _DIS is treated in another way
> Dietmar
> ⇗ https://www.dropbox.com/s/py7qjgousqov3a...S-0057.rar?dl=0

wow awesome ! I'll test it tonight and your last ACPI file too,thank you ^^

#2538 | kukonosau | ⇗ @diderius6 Where is chipset drivers for Windows XP x86 and x64 and Windows 7 x86 and x64 for Ryzen? I have sometimes lagging several games in all systems besides Windows 10. This problem with processors or motherboard? Or absents chipset drivers?
#2539 | diderius6 | ⇗ @kukonosau No chipset driver for AMD Ryzen and XP. But a lot of drivers for XP can be found via VEN_&DEV_ number Dietmar

#2540

IntiMD

⇗ @kukonosau
For Windows 7: ⇗ https://www.amd.com/en/support/chipsets/amd-socket-am4/b350 --> Windows 7 - 64-Bit Edition
For Windows XP there's different situation, although I can try helping you when it comes to missing drivers. Get Snappy Driver Installer Origin (only drivertool that has integrity - no bundled shit, open-source) from ⇗ here. Get "Application Only", unpack the archive and load the program. Choose "Download indexes only". After it downloads and shows list of drivers, quit the program and copy latest .snp log file from "logs". Upload it to say zippyshare or anonfile, or you can make a forum attachment if it fits the size. I'll take a look and tell you which drivers you should install.
(Sidenote of SDIO, even though it's most genuine, i recommend not letting the app installing the drivers itself, rather mouse over the device to check driver info such as localisation of driver in the driverpack, which version is it, all that. Download the driverpack and navigate to the folder, if it has an installer AND is not bloated, use the installer. if it doesn't have an installer or it's bloated, install it manually through devmgmt.msc.)
But like I said, get the latest .SNP log and upload it.

#2541 | Doc.Brown | ⇗ @diderius6 Same BSOD A5 with the other 0057 bios I try with last ACPI file after making a fresh ISO ;)
#2542 | kukonosau | ⇗ @diderius6 This is opportunity without SDI (Snappy Driver Installer)? I have lagging in all system in several games besides Windows 10!!! Unfortunately, Windows 7 has lagging also!!! May be, this from processor Ryzen 3 2200G with integrated graphics card? May be, for example, Ryzen 5 2600 is stability work in Windows 7 or Windows XP? Or I must find chipset drivers?

#2543

PPeti66x

⇗ @XPLives
"Are the version numbers extracted from the ntoskrnl.exe file except the last one?"
Yes, but should be same for all files in the package.
"This is very fascinating you got 140MB/s speeds on Intel USB 3.0"
140 MiB/s was not achieved via USB, it was reading from SATA HDD to memory - I needed to know, which device is slower. I have not fast enough device to test the maximal speed of the USB3.
XP kernel versions:
Date time stamps are extracted from ntoskrnl.exe file.
XP SP SP3 32-bit english (untouched CD image)
XP POSReady 2009 (untouched CD image)
(SP3 and POSReady 2009 file CRC32 is same.)
SP3.CAB\ ntkrnlmp.exe, ntkrnlpa.exe, ntkrpamp.exe, ntoskrnl.exe: 5.1.2600.5512 2008.04.13 19:27:39
SP3.CAB\ acpi.sys: 5.1.2600.5512 2008.04.13 18:36:33
XP SP2 32-bit + Media Center 2005 (unofficial CD image, but seems to be correct, not updated)
SP3.CAB\ ntkrnlmp.exe, ntkrnlpa.exe, ntkrpamp.exe, ntoskrnl.exe: 5.1.2600.2180 2004.08.04 06:19:48
SP3.CAB\ acpi.sys: 5.1.2600.2180 2004.08.04 06:07:35
XP SP1a 32-bit (untouched CD image)
SP3.CAB\ ntkrnlmp.exe, ntkrnlpa.exe, ntkrpamp.exe, ntoskrnl.exe: 5.1.2600.1106 2002.08.29 09:03:24
SP3.CAB\ acpi.sys: 5.1.2600.1106 2002.08.29 08:09:03
XP SP2 x64 (untouched CD image)
SP2.CAB\ ntkrnlmp.exe: 5.2.3790.3959 2007.02.17 07:03:32
SP2.CAB\ ntoskrnl.exe: 5.2.3790.3959 2007.02.17 07:01:10
SP2.CAB\ acpi.sys: 5.2.3790.3959 2007.02.17 06:37:56
I have no XP SP0 version and Server versions.
"The reason I mentioned the Function Key issue..."
Windows XP SP3 ACPI.SYS incorporates some Fn functions. I had no Dell software installed for this, because these was only for Windows 7, and disfunctional on XP. Only Device Drivers was installed, but I not found any specific device for this.
New speed test:
Source HDD: ADATA HV620S
Target HDD: Seagate Barracuda 7200.12 via StarTech USB to IDE/SATA adapter
Mainboard: ASRock Fatal1ty Z77 Professional
BIOS: 1.00, 1.70b (1.90b not tested, is incompatible with one of my HDDs)
XP kernel: ntoskrnl.exe 5.1.2600.7649, ntkrnlpa.exe 5.1.2600.7581
Controller: Intel C216 (PCI\VEN_8086&DEV_1E31)
Controller: Etron EJ188H
Video file: single AVI file, 161384651246 bytes, 153.908 GiB
(Speed was practically limited by the HDDs - I do not have faster high capacity media.
Speed constantly slowed from cca. 122000 kbytes/s to cca. 70000 kbytes/s)
Intel controller with BIOS v1.70b, microcode 306A9/15
27min 53sec = 1673 sec, 91.995 MiB/s
Etron Controller with BIOS v1.70b, microcode 306A9/15 (device driver v0.0.0.119)
27min 55sec = 1675 sec, 91.886 MiB/s
Intel controller with BIOS v1.00, microcode 306A9/C
27min 43sec = 1663 sec, 92.549 MiB/s
Etron controller with BIOS v1.00, microcode 306A9/C (device driver v0.0.0.119)
28min 14sec = 1694 sec, 90.855 MiB/s
On Windows 7 the speed is similiar.
It was amazing to see the old Fatal1ty logo in the 1.00 BIOS. In the original 1.3? BIOS was same or similiar. But the reaction on the F2/Del key was strange.
IMPORTANT NOTE: By backdating the BIOS the microcode updates was not backdated! The microcode update 306A9 comes from BIOS 1.90beta, which was not used, because of incompatibility with my 2TB WD Green HDD (not listed in BIOS, not seen by Windows).
When I was unable to achieve 60 MiB/s on Etron controller (around Q4/2014) the driver version was older (probably 0.0.0.118, or may be 0.0.0.115beta), and BIOS was 1.60 or 1.70 (non-beta). The speed was similiar on Win7 x64 and on WinXP 32-bit. And both operating systems was actualized from this time. What caused this big difference is unknown.

#2544

lsmlcx

I had test my z170 like this.
I found something interesting.
used ACPI.sys
then I used AMD xHCI,the error code is 39.
then I used NEC xhci,the device starts OK,and I don't install hub driver,
then I reinstall AMD xhci,and AMD xhci drive can works well.

#2545

skullteria

Error Code 39 is related with missing functions on dependencies files or missing dependencies files. It probably occours because AMD XHCI don't copy USBD.sys and NEC XHCI, copy. On Windows 7, what AMD XHCI is designed, USBD.sys is placed on Drivers folder by default, on XP, with XHCI system, no.
The relevant problem is the error is code 10, because it is related with start device and not really driver.

#2546 | dencorso | XP SP0: ntkrnlmp.exe, ntkrnlpa.exe, ntkrpamp.exe, ntoskrnl.exe: 5.1.2600.0 - Aug 18, 2001
#2547 | Dibya | Does this xhci driver works without bios mod?
#2548 | infuscomus | ⇗ @Dibya based on my testing, yes it does hotfix KB4230467 KB4463103 KB4486463 break the driver ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (169)

#2549

Gelip

I am trying to understand why WinXP x64 starts in VMware with full graphics support. Maybe because VMware has the UGA protocol?
I found interesting tools for UEFI shell:
⇗ ScanGOP_LocateProtocol & ScanUGA_LocateProtocol
⇗ screenmodes.efi (⇗ source code)

> Zitat

> The original EFI (Extensible Firmware Interface) specification and EDK (EFI Development Kit) supported a text output protocol and UGA (Universal Graphic Adapter), a device-independent VGA-derived graphics protocol. In 2005, Intel handed EFI standardization over to an industry consortium, UEFI, and that consortium decided to replace UGA with GOP (Graphics Output Protocol) to remove the remaining VGA hardware dependencies.

VMware has UEFI 2.30 but still has UGA and my ASUS has UEFI 2.31 and only has GOP protocol:
VMware 8 screenmodes.efi:

    No ConsoleControl handle found via HandleProtocol
    Found ConsoleControl handle via LocateProtocol
    Found 1 ConsoleControl handles via LocateHandleBuffer

    No UGA handle found via HandleProtocol
    Found UGA handle via LocateProtocol
    Found 2 UGA handles via LocateHandleBuffer

    No GOP handle found via HandleProtocol
    Found GOP handle via LocateProtocol
    Found 2 GOP handles via LocateHandleBuffer

ASUS screenmodes.efi:

    No ConsoleControl handle found via HandleProtocol
    Found ConsoleControl handle via LocateProtocol
    Found 1 ConsoleControl handles via LocateHandleBuffer

    No UGA handle found via HandleProtocol
    No UGA handle found via LocateProtocol
    No UGA handles found via LocateHandleBuffer

    No GOP handle found via HandleProtocol
    Found GOP handle via LocateProtocol
    Found 1 GOP handles via LocateHandleBuffer

#2550

lsmlcx

> Zitat von ⇗ skullteria im Beitrag ¶ #2545

> Error Code 39 is related with missing functions on dependencies files or missing dependencies files. It probably occours because AMD XHCI don't copy USBD.sys and NEC XHCI, copy. On Windows 7, what AMD XHCI is designed, USBD.sys is placed on Drivers folder by default, on XP, with XHCI system, no.
> The relevant problem is the error is code 10, because it is related with start device and not really driver.

⇗ @skullteria
thank you very much.
It works.

## Page 171

#2551

diderius6

On the Lenovo Flex 10 notebook with Bay Trail N2806 cpu and 64 bit legacy Bios
I get acpi.sys BSOD A5 (0x11, 0x08,..)
on XP SP3 and also on Win7 32 bit.
This remembers me a lot about the reversions number r2
in the DSDT table. Soon I change DSDT via iasl into version r1 (for 32 bit)
and flash with Epromer Revelprog IS
Dietmar

#2552

dencorso

> Zitat von ⇗ infuscomus im Beitrag ¶ #2548

> hotfix KB4230467 KB4463103 KB4486463 break the driver
> ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (169)

⇗ @daniel_k: would you kindly take a look at the newer kernel versions and see whether it's possible to fix the modded AMD drivers so that they can be used with the latest kernel version? Sorry to bother and thanks in advance!

#2553

lsmlcx

> Zitat von ⇗ skullteria im Beitrag ¶ #2545

> Error Code 39 is related with missing functions on dependencies files or missing dependencies files. It probably occours because AMD XHCI don't copy USBD.sys and NEC XHCI, copy. On Windows 7, what AMD XHCI is designed, USBD.sys is placed on Drivers folder by default, on XP, with XHCI system, no.
> The relevant problem is the error is code 10, because it is related with start device and not really driver.

⇗ @skullteria
I got a new problem.
When I put usbd.sys on Driver folder (\Windows\system32\drivers\), And install the modded AMD XHCI drivers.
It works well.
But when I restart the PC, After the scrollbar the PC got Black screen, I cann't see the desktop, But it doesn't Crash.
I donn't know why, It seems like the problem still happend with the modded AMD XHCI drivers.
I have tested it many times, every time.

#2554 | infuscomus | ⇗ @lsmlcx strange, I did not run into this problem is usbd.sys located in system32/drivers on a fresh install of XP? does it need to be copied? does the driver work if you dont copy usbd.sys?
#2555 | lsmlcx | ⇗ @infuscomus without copying usbd.sys, the error code is 39. when i copyed usbd.sys, then install driver, OK. but after reboot, I sad that.

#2556

lsmlcx

[[File:amd_new.zip]]
here is the new amd xhci version, DriverVer=12/04/2018, 1.1.0.0276
the xhci seems support xp, but the hub seems not.
maybe you can use old hub driver.
who can try to Crack
lsmlcx has attached files to this post

- ⇗ amd_new.zip

#2557

infuscomus

⇗ @diderius6
I think I may have gotten Intel USB 3.0 ports working in XP textmode setup
in txtsetup.sif edit

    [SourceDisksFiles]

    amdxhc.sys = 100,,,,,,,4,0,0
    amdhub30.sys = 100,,,,,,,4,0,0

    [HardwareIdsDatabase]

    PCI\VEN_8086&CC_0C0330 = "amdxhc"
    AMDUSB30\ROOT_HUB30 = "amdhub30"
    AMDUSB30\CLASS_09&SUBCLASS_00 = "amdhub30"
    AMDUSB30\CLASS_09&SUBCLASS_01 = "amdhub30"

    [InputDevicesSupport.Load]
    usbehci  = usbehci.sys
    usbohci  = usbohci.sys
    usbuhci  = usbuhci.sys
    usbhub   = usbhub.sys
    usbccgp  = usbccgp.sys
    amdxhc   = amdxhc.sys
    amdhub30 = amdhub30.sys
    hidusb   = hidusb.sys
    serial   = serial.sys
    serenum  = serenum.sys
    usbstor  = usbstor.sys

    [files.amdxhc]
    hid.dll,2
    hccoin.dll,2
    hidclass.sys,4
    hidparse.sys,4
    usbd.sys,4
    usbport.sys,4
    amdxhc.sys,4

    [files.amdhub30]
    amdhub30.sys,4

    [InputDevicesSupport]
    usbehci  = "Enhanced Host Controller",files.usbehci,usbehci
    usbohci  = "Open Host Controller",files.usbohci,usbohci
    usbuhci  = "Universal Host Controller",files.usbuhci,usbuhci
    usbhub   = "Generic USB Hub Driver",files.usbhub,usbhub
    hidusb   = "Human Interface Parser",files.hidusb,hidusb
    serial   = "Serial Port Driver",files.none,serial
    serenum  = "Serial Port Enumerator",files.none,serenum
    usbstor  = "USB Storage Class Driver",files.usbstor,usbstor
    usbccgp  = "USB Generic Parent Driver",files.usbccgp,usbccgp
    amdxhc   = "USB xHCI Compliant Host Controller",files.amdxhc,amdxhc
    amdhub30 = "Generic USB 3.0 Hub Driver",files.amdhub30,amdhub30

can you test this on your end?

#2558

diderius6

⇗ @infuscomus
I just edit my txtsetup.sif with your extra values for AMD xhci and make a check, that nothing is missed.
Then I add to installations folder i386 amdxhc.sy_ and amdhub30.sy_ final version for x86 from ⇗ @daniel_k .
All seems ok, but I do not know the behavior of usbd.sys.
Some years ago I make the same for USB ehci boot, but I use F6 method and Nlite for to integrate everything.
In this moment I am installing on the Asrock fatal1ty z370 gaming k6 board
Dietmar
EDIT: On first reboot I got BSOD 0x7B, because I use STORAHCI driver from ⇗ @skullteria and storport.sys is gone.
Now XP continues installing after I add storport.sys again to windows\system32\drivers.
USB mouse does not work during install.
usbd.sys amdxhc.sys amdhub30.sys are in windows\system32\drivers but usbstor.sys is missed there. I add usbstor.sys by hand.
Ok, I get A5 (0x11,..) because crazy XP changed acpi.sys back to original version, I copy modded acpi.sys by hand and continue install.
EDIT2: Install is finished. I see, that for amdxhc.sys and also for amdhub30.sys there is no ImagePath and no Group entry in registry and no entry in registry for usbstor.sys. I think, to integrate the drivers via F6 is more easy.
EDIT3: When I install the final AMD USB driver via hand, the missing entries are put into registry.
No usbstor entry in registry until you connect an USB stick. Then, all USB driver works on the Asrock board.

#2559 | infuscomus | ⇗ @diderius6 Thanks, did USB mouse and keyboard work for you during textmode phase? I was hoping it would work with just a txtsetup.sif mod without any registry hacks, unfortunately nlite wont do the registry hacks automatically to setupreg.hiv and hivesys.inf needed for Intel USB 3.0 to work during XP setup and these will always have to be done manually.
#2560 | diderius6 | ⇗ @infuscomus When you make a txtsetup.oem with all the files from USB, it will work using Nlite Dietmar
#2561 | infuscomus | ⇗ @diderius6 is it possible to specify multiple driver files in a txtsetup.oem? also did USB mouse and keyboard work for you during textmode phase on intel usb 3.0 ports?
#2562 | diderius6 | ⇗ @infuscomus No USB during setup of XP. Yes, I put 7 USB drivers in txtsetup.oem, and named all their *.inf files there Dietmar
#2563 | infuscomus | ⇗ @diderius6 OK, damn, I thought I had managed to get Intel USB 3.0 working in XP textmode setup, but since it does not work for you it means something else must be happening.

#2564

Mov AX, 0xDEAD

Another update ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (12):

> Zitat

> - WinDBG via USB or LAN connection unresolved

to

> Zitat

> WinDBG via LAN connection solved (custom kdnet.dll)

I've fixed all critical bugs in KDNET transport on real hardware and confirm "WinDBG works with NET for Windows XP x32"
Tested on realtek and qualcomm atheros pci-e chips. Now step-debug speed is amazing !
p.s. it need modding hal.dll & ntoskrrnl.exe, i plan to find workaround to not touching these files and release guide on this week...
p.s.s. Diderius6, you will get test files soon...

#2565 | diderius6 | ⇗ @Mov AX, 0xDEAD Niccceee, I want:)))), test on all compis Dietmar

## Page 172

#2566

diderius6

⇗ @Mov AX, 0xDEAD
Interesting, which driver is used for Windbg to connect to other compi via lan.
Is it the Bios lan driver?
If yes, this debug method will even work,
if there is no driver for this lan device under XP
Dietmar
PS:"Tested on realtek and qualcomm atheros pci-e chips. "
This is an interesting detail.
Until now, you cant add an pci-e COM1 card, for to get Windbg working,
because no driver for the pci-e bus is ready before Windbg needs it.
But now, as long as you can add a pci-e lan card, Windbg will work.
Via this way I come to the idea,
that it is even not needed to implement a whole lan driver into windbg,
it would be enough to make use of the the pci-e bus for Windbg and than take a normal COM1 seriell pci-e card.

#2567

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #2566

> @Mov AX, 0xDEAD
> Interesting, which driver is used for Windbg to connect to other compi via lan.
> Is it the Bios lan driver?
> that it is even not needed to implement a whole lan driver into windbg
> it would be enough to make use of the the pci-e bus for Windbg and than take a normal COM1 seriell pci-e card.

These drivers was writed by ms/vendors exclusively for kernel debugging, MS published examples for intel&realtek (see last windbg x64, folder DDK). Also drivers do not use full features of netcard, only minimal for receive&send UDP packets, kdnet.dll include minimal implementation of IP stack (arp/dhcp client/etc)

#2568

diderius6

⇗ @Mov AX, 0xDEAD
Will lan debug work under XP SP3
using there Windbg 6.12.0002.633 ?
This version runs under XP SP3 and can debug Win2000, XP, Server2003, Vista, Win7
each 32 bit and 64 bit architektures
Dietmar

#2569

Doc.Brown

Hi guys :)
After some more testing with bios and ACPI.sys provided by ⇗ @diderius6 unfortunately I'm always stuck with A5 BSOD on the Asus Gene 11 and 8700K,with the last modded ACPI.sys there's more bugged info with the BSOD as you can see on the screen below:
⇗
Started by integrate AHCI driver for A352 device by Fernando,after that tested by adding AMDXHCI and STOREAHCI but nothing help,also tried all ACPI5048 and also the one for 5512 XP build but fail,fail,fail
If you see more things to test I'm open ^^
Thanks for your help

#2570 | diderius6 | ⇗ @Doc.Brown Until now the problem is, that the Gene XI board has no serial COM1 port for debug. But very soon, thanks to ⇗ @Mov AX, 0xDEAD this problem is gone and I can help you Dietmar
#2571 | Doc.Brown | ⇗ @diderius6 That's a good news I'm hurry to see some update so :)
#2572 | infuscomus | ⇗ @diderius6 just asking, there are pci-e serial port cards you can get, does debugging work when using those?

#2573

diderius6

⇗ @infuscomus
When I understand ⇗ @Mov AX, 0xDEAD correct,
Microsoft offers drivers for network cards special for Kernel debug,
even when they are connected via pci-e(!). This would mean, that for example you can debug a compi with Intel i219-v
lan, even there is no XP driver until now for this device. Or you can put your own lan card into pci-e slot and start debugging.
This never works before.
What is not clear until now for me is, if everything can be done (Host and Target compi)
under XP SP3, when you have windbg, which works under XP SP3 and can debug compi with Win7
Dietmar

#2574

diderius6

⇗ @Mov AX, 0xDEAD
Yesssssssssssssssssssssssssssaaaaaaaaaa it works:))))))))))))))!!!!!!!!!!!!!!!!!

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Using NET for debugging
    Opened WinSock 2.0
    Waiting to reconnect...
    Connected to target 192.168.2.108 on port 50000.

Dietmar
PS: Everything under XP SP3(!).

#2575

diderius6

⇗ @Mov AX, 0xDEAD
How can I sent "break" command from host to debugged target compi?
At the window called Port Number from windbg for lan debug is the input
`50000 this.is.secret.key`
correct
Dietmar
PS: "Network debugging uses a 256-bit key that is specified as four 64-bit values, in base 36, separated by periods. Each 64-bit value is specified by using up to 13 characters. Valid characters are the letters a through z and the digits 0 through 9. "
EDIT: Now I think, my connection via XP SP3 as host machine is not complete:

    Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86 is from win 8.1
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86  is my version on XP SP3

#2576

diderius6

Crazy, I cant install the win 8.1 sdk on real Win8.1
The blue map appears for a second and then disappears
Dietmar
EDIT: What a crap is win 8.1..
So, at the moment I dont have windbg Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86 from win 8.1
and I dont know, how to get it even I have original Win 8.1 32 bit installed.

#2577

nektandra

Gentlemen, it is what are you doing tremendous and I understand that I tear off you from a solution of really difficult tasks, but you could render me the small help? I try to install Windows XP х86 on the motherboard with a chipset of B350 and the Ryzen processor. Thanks to the detailed instruction of kindly provided ⇗ @infuscomus I replaced in a distribution kit all copies of the acpi.sys file with the file from acpi5048_x86_intel_amd_final.rar. After that I promoted from the blue screen with error A5 to error 7B. It is obvious that at this stage I should integrate drivers of the SATA controller correctly. Using nlite I tried Universal 32bit AMD AHCI driver v1.2.1.321 mod by Fernando and Universal 32bit AMD AHCI driver v6.1.3.35 mod by Fernando. Also I without results tried to use Scsiport and Storport of the driver the laid-out ⇗ @daniel_k before reached me that for them there are no files of txtsetup.oem. Tell me please,
1 What drivers of the SATA controller of a chipset of AMD 350 are suitable for Windows XP x86 better?
2 If Scsiport or Storport of the driver from ⇗ @daniel_k are the best version of the driver whether then it is necessary to generate manually for them txtsetup.oem?
3 At last if my assumptions are quite misleading, then how it is correct to integrate driver Storport from ⇗ @daniel_k into the Windows XP distribution kit?

#2578 | diderius6 | ⇗ @nektandra Only the STORAHCI driver from ⇗ @skullteria works on AMD Ryzen boards, see this driver in my post #881 Dietmar

#2579

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #2574

> @Mov AX, 0xDEAD
> Using NET for debugging
> Opened WinSock 2.0
> Waiting to reconnect...
> Connected to target 192.168.2.108 on port 50000.
> ....
> PS: Everything under XP SP3(!).

Old windbg for winxp will not work with transport from win8.1 (it doesnt have field for entering password), you wont see anything after "Connected to target 192.168.2.108 on port 50000". If you can find version of windbg for winxp with password support - it probably will work.

#2580

diderius6

⇗ @Mov AX, 0xDEAD
Do you have an idea,
where I can get a newer windbg version which works for lan debug of XP
Dietmar
PS: I cant install SDK 8.1 for unknown reason in Win 8.1 32 bit. This Win 8.1 tells: Incompatible program..
Dietmar

## Page 173

#2581

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #2576

> So, at the moment I dont have windbg Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86 from win 8.1
> and I dont know, how to get it even I have original Win 8.1 32 bit installed.

- start "X86 Debuggers And Tools-x86_en-us.msi" manualy, it will not add menus in Programs, create link to "c:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86\windbg.exe"
or
- extract "X86 Debuggers And Tools-x86_en-us.msi" to any folder, create link

#2582 | diderius6 | ⇗ @Mov AX, 0xDEAD I just found ⇗ https://github.com/kbandla/installers/bl...s-x86_en-us.msi Dietmar

#2583

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #2573

> @infuscomus
> When I understand @Mov AX, 0xDEAD correct,
> Microsoft offers drivers for network cards special for Kernel debug,
> even when they are connected via pci-e(!). This would mean, that for example you can debug a compi with Intel i219-v
> lan, even there is no XP driver until now for this device. Or you can put your own lan card into pci-e slot and start debugging.

- host PC can have any card if owner has driver for windows
- target pc must have card only supported KD NET, ⇗ http://go.microsoft.com/fwlink/p/?linkid=230754
- when boomgr load winload/ntosk/hal it also load kdnet.dll + check for available pci netcard
- if netcard is supported it load proper .dll like kd_02_8086.dll (intel), this dll is special driver for kernel debugging
p.s. windows 8.x also has new BOOT DEBUGGER, all drivers implemented in winload and no need extern dll

#2584

nektandra

> Zitat von diderius6

> Only the STORAHCI driver from @skullteria works on AMD Ryzen boards,
> see this driver in my post #881
> Dietmar

Excellently! Many thanks! I have to apologize for not reading the whole branch of the forum in a row.
After installing with ahci the driver from message 881, I updated the sata driver using the amd_ahci_x86 from message 1669.
Whether correctly I understand that AMDXHCI_XP_FINAL.rar from the message 2225 contains the working driver of the USB controller for AMD B350?

#2585

diderius6

⇗ @Mov AX, 0xDEAD
I get this windbg version to work under win 8.1.
But XP hangs during boot.
May be because of hanging, the "break" or "g" command not works.
Tomorrow I set up new Win7 32 bit.
The connection seems now to be ok
Dietmar

    Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Using NET for debugging
    Opened WinSock 2.0
    Waiting to reconnect...
    Connected to target 192.168.2.108 on port 50000 on local IP 192.168.2.101.
    Connected to Windows XP 2600 x86 compatible target at (Tue Oct  1 01:47:23.109 2019 (UTC + 2:00)), ptr64 FALSE
    Kernel Debugger connection established.
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
    Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
    Built by: 2600.xpsp_sp3_qfe.190108-0655
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
    System Uptime: not available

    Intel Storage Driver Ver: 11.2.0.1006

    AhciHwFindAdapter finishing

#2586

diderius6

Yesssaaaaaaaa, in "Safe Mode" (F8) it works!!!
Dietmar

    Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Using NET for debugging
    Opened WinSock 2.0
    Waiting to reconnect...
    Connected to target 192.168.2.108 on port 50000 on local IP 192.168.2.101.
    Connected to Windows XP 2600 x86 compatible target at (Tue Oct  1 02:10:13.745 2019 (UTC + 2:00)), ptr64 FALSE
    Kernel Debugger connection established.
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
    Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
    Built by: 2600.xpsp_sp3_qfe.190108-0655
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
    System Uptime: not available

    Intel Storage Driver Ver: 11.2.0.1006

    AhciHwFindAdapter finishing
    SAFEBOOT: skipping device = mnmdd.SYS(Video Save)
    SAFEBOOT: skipping device = RDPCDD.SYS(Video Save)
    SAFEBOOT: skipping device = RasAcd.SYS(Streams Drivers)
    SAFEBOOT: skipping device = IPSec.SYS(PNP_TDI)
    SAFEBOOT: skipping device = Tcpip.SYS(PNP_TDI)
    SAFEBOOT: skipping device = NetBT.SYS(PNP_TDI)
    SAFEBOOT: skipping device = AFD.SYS(TDI)
    SAFEBOOT: skipping device = NetBIOS.SYS(NetBIOSGroup)
    SAFEBOOT: skipping device = Serial.SYS(Extended base)
    SAFEBOOT: skipping device = intelppm.SYS(Extended Base)
    SAFEBOOT: skipping device = WS2IFSL.SYS(Group)
    SAFEBOOT: skipping device = Rdbss.SYS(Network)
    SAFEBOOT: skipping device = MRxSmb.SYS(Network)
    SAFEBOOT: skipping device = Fips.SYS(Group)
    SAFEBOOT: skipping device = ElbyCDIO.SYS(Group)
    Break instruction exception - code 80000003 (first chance)
    *******************************************************************************
    *                                                                             *
    *   You are seeing this message because you pressed either                    *
    *       CTRL+C (if you run console kernel debugger) or,                       *
    *       CTRL+BREAK (if you run GUI kernel debugger),                          *
    *   on your debugger machine's keyboard.                                      *
    *                                                                             *
    *                   THIS IS NOT A BUG OR A SYSTEM CRASH                       *
    *                                                                             *
    * If you did not intend to break into the debugger, press the "g" key, then   *
    * press the "Enter" key now.  This message might immediately reappear.  If it *
    * does, press "g" and "Enter" again.                                          *
    *                                                                             *
    *******************************************************************************
    *** WARNING: Unable to verify timestamp for ntdll.dll
    *** ERROR: Module load completed but symbols could not be loaded for ntdll.dll
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
    nt!DbgBreakPointWithStatus+0x4:
    804e29c2 cc              int     3
    0: kd> lm
    start    end        module name
    7f520000 7f5da000   ntdll    T (no symbols)
    80010000 80013000   BOOTVID    (deferred)
    80100000 80140000   KDSTUB     (deferred)
    804d7000 80700000   nt         (export symbols)       ntkrnlmp.exe
    80700000 80720d00   hal        (deferred)
    80721000 80757000   kdcom      (deferred)
    b8019000 b8059000   dump_storport   (deferred)
    b80c9000 b80dcf00   VIDEOPRT   (deferred)
    b80f7000 b80f9900   Dxapi      (deferred)
    b8137000 b8194f00   update     (deferred)
    b8195000 b81b7700   ks         (deferred)
    b81c8000 b81cb000   mouhid     (deferred)
    b81dc000 b81de880   hidusb     (deferred)
    b81e0000 b820fe80   rdpdr      (deferred)
    b8210000 b8227000   amdhub30   (deferred)
    b8227000 b824f000   HDAudBus   (deferred)
    b8393000 b8396c80   mssmbios   (deferred)
    b83c3000 b83dce80   Mup        (deferred)
    b83dd000 b8409980   NDIS       (deferred)
    b840a000 b8496d00   Ntfs       (deferred)
    b8497000 b84a9f00   WudfPf     (deferred)
    b84aa000 b84c0b80   KSecDD     (deferred)
    b84c1000 b84d2f00   sr         (deferred)
    b84d3000 b84f2b00   fltMgr     (deferred)
    b84f3000 b8533000   storport   (deferred)
    b8533000 b854a880   SCSIPORT   (deferred)
    b854b000 b8800000   iaStor     (deferred)
    bd000000 bd011600   dxg        (deferred)
    bf800000 bf9d3780   win32k     (deferred)
    bff70000 bff72480   framebuf   (deferred)
    f7472000 f7497a00   dmio       (deferred)
    f7498000 f74b6d80   ftdisk     (deferred)
    f7517000 f7524000   dump_storahci   (deferred)
    f7527000 f7536900   Cdfs       (deferred)
    f7557000 f7567a80   pci        (deferred)
    f7568000 f75a8000   ACPI       (deferred)
    f75a8000 f75d6000   amdxhc     (deferred)
    f75f7000 f7600300   isapnp     (deferred)
    f7607000 f7611580   MountMgr   (deferred)
    f7617000 f7624200   VolSnap    (deferred)
    f7627000 f7637000   asahci32   (deferred)
    f7637000 f7644000   storahci   (deferred)
    f7647000 f764fe00   disk       (deferred)
    f7657000 f7663180   CLASSPNP   (deferred)
    f76a7000 f76b3f00   i8042prt   (deferred)
    f76b7000 f76c0f00   termdd     (deferred)
    f76c7000 f76d3000   VClone     (deferred)
    f76d7000 f76e6600   cdrom      (deferred)
    f76e7000 f76f5180   redbook    (deferred)
    f76f7000 f7700000   HIDCLASS   (deferred)
    f7707000 f770d780   USBSTOR    (deferred)
    f770f000 f7713d00   PartMgr    (deferred)
    f7747000 f774d280   kbdclass   (deferred)
    f774f000 f7754c00   mouclass   (deferred)
    f7787000 f778d380   HIDPARSE   (deferred)
    f779f000 f77a4200   vga        (deferred)
    f77af000 f77b3b00   Msfs       (deferred)
    f77bf000 f77c6980   Npfs       (deferred)
    f77e7000 f77eb500   watchdog   (deferred)
    f7943000 f7945280   wmiacpi    (deferred)
    f7987000 f7988500   USBD       (deferred)
    f7989000 f798a100   WMILIB     (deferred)
    f798b000 f798c700   dmload     (deferred)
    f7995000 f7996100   swenum     (deferred)
    f799d000 f799ef00   Fs_Rec     (deferred)
    f79a1000 f79a2080   Beep       (deferred)
    f7aa7000 f7aa7d00   dxgthk     (deferred)
    f7ab0000 f7ab0b80   Null       (deferred)

#2587

Andalu

Continuing in my tests about USB3 functionality, something strange happened for my asrock ivy boards.
On the B75 Pro3-M the USB3 works fine after a clean XP install (with inside modded amd drivers and acpi.sys 5048). On each restart, the USB3 continues to work correctly. But if I shutdown the computer and then turn off the power supply unit, on the next boot the USB3 doesn't work anymore until a new XP install or by restoring an XP image with acronis true image boot disk. But even in the last case, at the end of the recover operation:
1) if I choose to restart the computer, on the next boot the USB3 will work fine;
2) if I choose to shutdown, the USB3 will not work anymore.
For the B75M-GL R2.0 almost the same behaviour. The difference is that the USB3 doesn't work on a clean XP install also. The only way to get the USB3 functionality for this board is to restore the image saved from the B75 Pro3-M but never shutdown the computer, only restarts. So, to keep the usb3 functionality, these boards need to be always on. Any ideas?

#2588

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #2585

> @Mov AX, 0xDEAD
> I get this windbg version to work under win 8.1.
> But XP hangs during boot.
> May be because of hanging, the "break" or "g" command not works.
> Tomorrow I set up new Win7 32 bit.
> The connection seems now to be ok

yes, connection now is OK, you dont need win7
maybe XP hangs because you are activated network device in XP ? it must be disabled in DevManager because conflict with debugger driver, also try with /BREAK, it must stop loading windows and you can check G command

#2589 | infuscomus | ⇗ @Andalu for the USB 3.0 controllers listed in device manager, do you see a power management tab?

#2590

Mov AX, 0xDEAD

> Zitat von ⇗ Andalu im Beitrag ¶ #2587

> So, to keep the usb3 functionality, these boards need to be always on. Any ideas?

amd/nec/via/intel usb3 driver save some settings in registry, may this is problem. we dont know what these setting mean but driver can load it after ever reset and override hardware/mode of usb3 controller
example for via:

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\xhcdrv\Parameters]
    "IMODI"=dword:00000001
    "MsDelayAfterAddressBsr0"=dword:00000014
    "RootPortStatusFormat"=dword:00000001
    "HwTriggerMask"=dword:ffffffff
    "MaxRootHubReEnumCount"=dword:00000003
    "UsDelayBetweenSeparateTd"=dword:000003e8
    "UsMinLfsBulkUrbCompletionTime"=dword:000000a0
    "UsMinSsBulkUrbCompletionTime"=dword:00000118
    "UsMinCtrlUrbCompletionTime"=dword:00000000
    "MsDelayAfterModifyIntegratedHubPp"=dword:00000488
    "FrameWindow"=dword:000007ff
    "DmaEnablerAlignmentRequirement"=dword:00000003
    "DisableUpdateFirstTrbCycleBitLast"=dword:00000000
    "DisableSecondaryInterrupters"=dword:00000000
    "DisableSelectiveSuspend"=dword:00000001
    "DisableSimplifiedBulkHandlingOnBOT"=dword:00000000
    "DisableRemoteWakeup"=dword:00000000
    "DisableDynamicRootHubEnum"=dword:00000000

On Notebooks usb3 modes probably controlled by EmbeddedController with help of DSDT (acpi)

#2591 | Andalu | ⇗ @infuscomus here the device manager for the B75Pro3-M board (the same for the B75M-GL R2.0). I always unticked the power saving for all my boards. ⇗

#2592

Andalu

⇗ @Mov AX, 0xDEAD
You are right, it is something related to the registry that changes during XP booting. The strange is: why this change happens for the shutdown only and never for the restart? And regarding the B75 Pro3-M board, why only when the psu is turned off?
I have also tried to load (with asl.exe /loadtable command) a modified DSDT table for the B75M-GL R2.0 board following ⇗ this guide (it is for hackintosh so I have changed the values for OSYS too) but i had no success (I had to use the -f option to force iasl.exe to compile the *.aml file although it had highlighted 3 errors).
So for now, i have only one motherboard out of six where the USB3 is fully functional but I don't know what will happen when I turn on that board :)

#2593

diderius6

⇗ @Mov AX, 0xDEAD
you are right.
I just disable in Device Manager the Realtek network controller on the
nice Giga H110 board and now XP starts normal.
On this compi lan Debug works now like the Debug over COM1,
what a great success
Dietmar

    Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Using NET for debugging
    Opened WinSock 2.0
    Waiting to reconnect...
    Connected to target 192.168.2.108 on port 50000 on local IP 192.168.2.101.
    Connected to Windows XP 2600 x86 compatible target at (Tue Oct  1 17:35:20.084 2019 (UTC + 2:00)), ptr64 FALSE
    Kernel Debugger connection established.
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
    Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
    Built by: 2600.xpsp_sp3_qfe.190108-0655
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
    System Uptime: not available

    Intel Storage Driver Ver: 11.2.0.1006

    AhciHwFindAdapter finishing
    AFD: Read FastSendDatagramThreshold from the registry, value: 0x5dc (default: 0x400))
    AFD: Read DefaultReceiveWindow from the registry, value: 0x40290 (default: 0x2000))
    AFD: Read DefaultSendWindow from the registry, value: 0x1f5e0 (default: 0x2000))
    44: ERROR: UMRxReadDWORDFromTheRegistry/ZwQueryValueKey: NtStatus = c0000034
    ERROR: DavReadRegistryValues/RegQueryValueExW(4). WStatus = 127
    ERROR: DavReadRegistryValues/RegQueryValueExW(5). WStatus = 127
    ERROR: DavReadRegistryValues/RegQueryValueExW(6). WStatus = 127
    Break instruction exception - code 80000003 (first chance)
    *******************************************************************************
    *                                                                             *
    *   You are seeing this message because you pressed either                    *
    *       CTRL+C (if you run console kernel debugger) or,                       *
    *       CTRL+BREAK (if you run GUI kernel debugger),                          *
    *   on your debugger machine's keyboard.                                      *
    *                                                                             *
    *                   THIS IS NOT A BUG OR A SYSTEM CRASH                       *
    *                                                                             *
    * If you did not intend to break into the debugger, press the "g" key, then   *
    * press the "Enter" key now.  This message might immediately reappear.  If it *
    * does, press "g" and "Enter" again.                                          *
    *                                                                             *
    *******************************************************************************
    *** WARNING: Unable to verify timestamp for ntdll.dll
    *** ERROR: Module load completed but symbols could not be loaded for ntdll.dll
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
    nt!DbgBreakPointWithStatus+0x4:
    804e29c2 cc              int     3
    0: kd> lm
    start    end        module name
    7f520000 7f5da000   ntdll    T (no symbols)
    80010000 80013000   BOOTVID    (deferred)
    80100000 80140000   KDSTUB     (deferred)
    804d7000 80700000   nt         (export symbols)       ntkrnlmp.exe
    80700000 80720d00   hal        (deferred)
    80721000 80757000   kdcom      (deferred)
    b2ab7000 b2af7e00   HTTP       (deferred)
    b304a000 b30a1c80   srv        (deferred)
    b31e0000 b31f4480   wdmaud     (deferred)
    b321d000 b3248f80   mrxdav     (deferred)
    b3359000 b3367d80   sysaudio   (deferred)
    b34b5000 b34b8900   ndisuio    (deferred)
    b419c000 b41dc000   dump_storport   (deferred)
    b42a4000 b4313a80   mrxsmb     (deferred)
    b4314000 b433ee80   rdbss      (deferred)
    b433f000 b4360d00   afd        (deferred)
    b4361000 b4386500   ipnat      (deferred)
    b4387000 b43aed80   netbt      (deferred)
    b43d7000 b442f480   tcpip      (deferred)
    b4430000 b4442600   ipsec      (deferred)
    b447f000 b4481900   Dxapi      (deferred)
    b44b3000 b4a7b000   RtkHDAud   (deferred)
    b4aa3000 b4aa6000   mouhid     (deferred)
    b4aab000 b4aad280   rasacd     (deferred)
    b4ab7000 b4ab9880   hidusb     (deferred)
    b4acb000 b4aeea80   portcls    (deferred)
    b4aef000 b4b0c580   nvhda32    (deferred)
    b6d95000 b6df2f00   update     (deferred)
    b6df3000 b6e15700   ks         (deferred)
    b6e16000 b6e45e80   rdpdr      (deferred)
    b6e46000 b6e56e00   psched     (deferred)
    b6e57000 b6e6d680   ndiswan    (deferred)
    b6e89000 b6e89d00   dxgthk     (deferred)
    b6e8c000 b6ea3000   amdhub30   (deferred)
    b6ea3000 b6ecb000   HDAudBus   (deferred)
    b6ecb000 b6edef00   VIDEOPRT   (deferred)
    b6edf000 b7b40bc0   nv4_mini   (deferred)
    b826f000 b8272c80   mssmbios   (deferred)
    b828b000 b8293780   netbios    (deferred)
    b829b000 b82a3700   wanarp     (deferred)
    b82ab000 b82b4000   HIDCLASS   (deferred)
    b82bb000 b82c9180   redbook    (deferred)
    b82cb000 b82da600   cdrom      (deferred)
    b82db000 b82e9b00   drmk       (deferred)
    b82eb000 b82f5000   NDProxy    (deferred)
    b82fb000 b8307000   VClone     (deferred)
    b830b000 b8314f00   termdd     (deferred)
    b831b000 b8323900   msgpc      (deferred)
    b8367000 b8369900   ndistapi   (deferred)
    b836b000 b836d280   wmiacpi    (deferred)
    b836f000 b8372d80   serenum    (deferred)
    b83c3000 b83dce80   Mup        (deferred)
    b83dd000 b8409980   NDIS       (deferred)
    b840a000 b8496d00   Ntfs       (deferred)
    b8497000 b84a9f00   WudfPf     (deferred)
    b84aa000 b84c0b80   KSecDD     (deferred)
    b84c1000 b84d2f00   sr         (deferred)
    b84d3000 b84f2b00   fltMgr     (deferred)
    b84f3000 b8533000   storport   (deferred)
    b8533000 b854a880   SCSIPORT   (deferred)
    b854b000 b8800000   iaStor     (deferred)
    bd000000 bd011600   dxg        (deferred)
    bd012000 bd3ca380   nv4_disp   (deferred)
    bf800000 bf9d3780   win32k     (deferred)
    f7472000 f7497a00   dmio       (deferred)
    f7498000 f74b6d80   ftdisk     (deferred)
    f74b7000 f74c2d00   raspptp    (deferred)
    f74c7000 f74d1200   raspppoe   (deferred)
    f74d7000 f74e3880   rasl2tp    (deferred)
    f74e7000 f74f0e00   intelppm   (deferred)
    f74f7000 f7507000   serial     (deferred)
    f7507000 f7513f00   i8042prt   (deferred)
    f7557000 f7567a80   pci        (deferred)
    f7568000 f75a8000   ACPI       (deferred)
    f75a8000 f75d6000   amdxhc     (deferred)
    f75f7000 f7600300   isapnp     (deferred)
    f7607000 f7611580   MountMgr   (deferred)
    f7617000 f7624200   VolSnap    (deferred)
    f7627000 f7637000   asahci32   (deferred)
    f7637000 f7644000   storahci   (deferred)
    f7647000 f764fe00   disk       (deferred)
    f7657000 f7663180   CLASSPNP   (deferred)
    f7687000 f7691e80   Fips       (deferred)
    f76a7000 f76b1000   ElbyCDIO   (deferred)
    f76c7000 f76d6900   Cdfs       (deferred)
    f76d7000 f76e4000   dump_storahci   (deferred)
    f7707000 f770d780   USBSTOR    (deferred)
    f770f000 f7713d00   PartMgr    (deferred)
    f7767000 f776d280   kbdclass   (deferred)
    f776f000 f7774c00   mouclass   (deferred)
    f7777000 f777ba80   TDI        (deferred)
    f777f000 f7783580   ptilink    (deferred)
    f7787000 f778b080   raspti     (deferred)
    f779f000 f77a5380   HIDPARSE   (deferred)
    f77af000 f77b4200   vga        (deferred)
    f77b7000 f77bbb00   Msfs       (deferred)
    f77bf000 f77c6980   Npfs       (deferred)
    f77c7000 f77cb500   watchdog   (deferred)
    f7987000 f7988500   USBD       (deferred)
    f7989000 f798a100   WMILIB     (deferred)
    f798b000 f798c700   dmload     (deferred)
    f79ab000 f79ac100   swenum     (deferred)
    f79b3000 f79b4f00   Fs_Rec     (deferred)
    f79b5000 f79b6080   Beep       (deferred)
    f79b7000 f79b8080   mnmdd      (deferred)
    f79bb000 f79bc080   RDPCDD     (deferred)
    f7a7b000 f7a7bc00   audstub    (deferred)
    f7aab000 f7aabb80   Null       (deferred)

    Unloaded modules:
    b30f2000 b311d000   kmixer.sys
    b7d04000 b7d05000   drmkaud.sys
    b3531000 b353e000   DMusic.sys
    b3339000 b3347000   swmidi.sys
    b311d000 b3140000   aec.sys
    f79e3000 f79e5000   splitter.sys
    b31e1000 b31f5000   Parport.SYS
    f7677000 f7682000   imapi.sys
    f77a7000 f77ac000   Cdaudio.SYS
    b4ab3000 b4ab6000   Sfloppy.SYS
    f7797000 f779c000   Flpydisk.SYS
    f7627000 f7637000   asahci32.sys
    b854b000 b8800000   iaStor.sys

#2594

diderius6

⇗ @Mov AX, 0xDEAD
I make a new test with a Realtek Slot Pci-e card on the nice Giga H110 board.
In Device Manager I look for its PCI-Bus 4, Gerät 0, Funktion 0 and
make an entry with this numbers in boot.ini with /busparams=4.0.0
so that the debugger knows, which NIC is used.
And voila, it works ). This is the very first time,
that I succeed to connect windbg to an pci-e slot card
and make it work.
This means: Now, as long as the compi has a COM1 port or a supported network card or just 1 free Pci-e slot,
it can be fully debugged under XP SP3
Dietmar

#2595

diderius6

⇗ @Mov AX, 0xDEAD
I test the Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86
under Vista 32 bit (Vista as host, the compi where windbg runs).
It also works from there for debugging XP SP3 over lan. So, there is a chance to make this new debugger version run under XP SP3.
I test Debug over lan on Intel i211 nic on the Asrock fatal1ty z370 gaming k6 board with XP SP3 as target (compi which is debugged).
Works ).
On the NIC i219-v it does not work. The reason is just, i219-v DEV ID 15BX is not supported in Lan Debug of win8.1
Dietmar

    System Requirements

    Kernel
     debugging through Ethernet NICs requires certain low-level platform
    support. Windows requires that these NICs be attached via PCI/PCIe for
    this debugging solution. In most cases, simply plugging in one of these
    supported NICs will allow a robust kernel debugging experience. However,
     there may be cases where BIOS configuration details hinder the Windows
    debug path. The following platform requirement should be considered:

        System firmware should discover and configure the NIC device such
    that its resources do not conflict with any other devices that have been
     BIOS-configured.

    Finding the vendor ID and device ID

    First find the vendor ID and device ID of the network adapter on your target computer.

        On the target computer, open Device Manager (enter devmgmt in a Command Prompt window).
        In Device Manager, locate the network adapter that you want to use for debugging.
        Right click the network adapter node, and choose Properties.
        In the Details tab, under Property, select Hardware Ids.

    The
     vendor and device IDs are shown as VEN_VendorID and DEV_DeviceID. For
    example, if you see PCI\VEN_8086&DEV_104B, the vendor ID is 8086,
    and the device ID is 104B.
    Vendor ID 8086, Intel Corporation

    For vendor ID 8086, these device IDs are supported:

    0438
     043A 043C 0440 1000 1001 1004 1008 1009 100C 100D 100E 100F 1010 1011
    1012 1013 1014 1015 1016 1017 1018 1019 101A 101D 101E 1026 1027 1028
    1049 104A 104B 104C 104D 105E 105F 1060 1075 1076 1077 1078 1079 107A
    107B 107C 107D 107E 107F 108A 108B 108C 1096 1098 1099 109A 10A4 10A5
    10A7 10A9 10B5 10B9 10BA 10BB 10BC 10BD 10BF 10C0 10C2 10C3 10C4 10C5
    10C6 10C7 10C8 10C9 10CB 10CC 10CD 10CE 10D3 10D5 10D6 10D9 10DA 10DB
    10DD 10DE 10DF 10E1 10E5 10E6 10E7 10E8 10EA 10EB 10EC 10EF 10F0 10F1
    10F4 10F5 10F6 10F7 10F8 10F9 10FA 10FB 10FC 1501 1502 1503 1507 150A
    150B 150C 150D 150E 150F 1510 1511 1514 1516 1517 1518 151C 1521 1522
    1523 1524 1525 1526 1527 1528 1529 152A 1533 1534 1535 1536 1537 1538
    1539 153A 153B 1546 154A 154D 1557 1558 1559 155A 1560 157B 157C 1F40
    1F41 1F45 294C
    Vendor ID 10EC, Realtek Semiconductor Corp.

    For vendor ID 10EC, these device IDs are supported:

    8136 8137 8167 8168 8169
    Vendor ID 14E4, Broadcom

    For vendor ID 14E4, these device IDs are supported:

    1600
     1601 1639 163A 163B 163C 1644 1645 1646 1647 1648 164A 164C 164D 1653
    1654 1655 1656 1657 1658 1659 165A 165B 165C 165D 165E 165F 1668 1669
    166A 166B 166D 166E 1672 1673 1674 1676 1677 1678 1679 167A 167B 167C
    167D 167F 1680 1681 1684 1688 1690 1691 1692 1693 1694 1696 1698 1699
    169A 169B 169D 16A0 16A6 16A7 16A8 16AA 16AC 16B0 16B1 16B2 16B4 16B5
    16B6 16C6 16C7 16DD 16F7 16FD 16FE 16FF 170D 170E 170F
    Vendor ID 1969, Atheros Communications

    For vendor ID 1969, these device IDs are supported:

    1062
     1063 1073 1083 1090 1091 10A0 10A1 10B0 10B1 10C0 10C1 10D0 10D1 10E0
    10E1 10F0 10F1 2060 2062 E091 E0A1 E0B1 E0C1 E0D1 E0E1 E0F1
    Vendor ID 19A2, ServerEngines (Emulex)

    For vendor ID 19A2, these device IDs are supported:

    0211 0215 0221 0700 0710
    Vendor ID 10DF, Emulex Corporation

    For vendor ID 10DF, these device IDs are supported:

    0720 E220
    Vendor ID 15B3, Mellanox Technology

    For vendor ID 15B3, these device IDs are supported:

    1000
     1001 1002 1003 1004 1005 1006 1007 1008 1009 100A 100B 100C 100D 100E
    100F 1010 6340 6341 634A 634B 6354 6368 6369 6372 6732 6733 673C 673D
    6746 6750 6751 675A 6764 6765 676E 6778

## Page 174

#2596

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #2595

> On the NIC i219-v it does not work. The reason is just, i219-v DEV ID 15BX is not supported in Lan Debug of win8.1

In theory, if i219-v compatible with some previous model, patched kd_02_8086.dll (ID_XXX=>ID_YYY) solve problem.
Dietmar, learn asm, you can do any things yourself )

#2597

diderius6

⇗ @Mov AX, 0xDEAD
I found with Ida Pro in kd_02_8086.dll the place,
where the check for 8086 (Intel nic) happens.
Also I see the place there

    .text:800119F1                 mov     dword ptr [eax], offset aThisNicIsNotSu

but I dont know, how to add extra Device ID for the i219-v
and a lot of other devices for Atheros (in its kd_02_1969.dll)
even I think the Vendor key is other `VEN_168C&DEV_0036&SUBSYS_061211AD Qualcomm Atheros AR956x Wireless Network Adapter` for the Lenovo Flex 10 netbook
Dietmar

#2598

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #2597

> and a lot of other devices for Atheros (in its kd_02_1969.dll)
> even I think the Vendor key is other
> VEN_168C&DEV_0036&SUBSYS_061211AD Qualcomm Atheros AR956x Wireless Network Adapter for the Lenovo Flex 10 netbook

Vendors can register multiple PCI ID: 1969 for LAN , 168C - wireless, 666- dEvil's electronic toys )

#2599

Mov AX, 0xDEAD

⇗ @diderius6,
Newer Windbg (Win8/Win10) versions has incompatibility bug - Register Window is empty if target is WinXP or Win2003, bug still in place even with original COM debugging. I think MS changed protocol and windbg cannot show required registers.
I use IDA+windbg plugin instead "pure" windbg, this bug is not presented in IDA
p.s. win2003 x32 now supported too

    Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Using NET for debugging
    Opened WinSock 2.0
    Waiting to reconnect...
    Connected to target 192.168.4.3 on port 50000 on local IP 192.168.4.1.
    Connected to Windows Server 2003 3790 x86 compatible target at (Wed Oct  2 23:39:00.684 2019 (UTC + 5:00)), ptr64 FALSE
    Kernel Debugger connection established.

    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\Windows\SYMBOLS*⇗ http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\Windows\SYMBOLS*⇗ http://msdl.microsoft.com/download/symbols
    Executable search path is:
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlpa.exe -
    Windows Server 2003 Kernel Version 3790 UP Free x86 compatible
    Built by: 3790.srv03_sp2_rtm.070216-1710
    Machine Name:
    Kernel base = 0x80800000 PsLoadedModuleList = 0x8089ffa8
    System Uptime: not available
    Break instruction exception - code 80000003 (first chance)
    *******************************************************************************

#2600

diderius6

⇗ @Mov AX, 0xDEAD
"Register Window is empty if target is WinXP or Win2003"
what does this mean for debugging XP via Lan for example with host Win8.1?
Can the Acpi Bsod A5 been fully debugged on XP SP3 via lan
on the Newer Windbg (Win8/Win10)
Dietmar
PS: When this bug cannot be overcome.
How can I integrate the Newer Windbg (Win8/Win10)
into Ida as plugin? I have version 6.1.11.315 (from 2011)
with the possibility to attach windbg.

#2601

diderius6

⇗ @Mov AX, 0xDEAD
I take a look at windbg Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86
why this windbg does not like to run on XP SP3.
Dependency Walker shows as only file with unmatched import functions
msvcrt.dll
__CxxFrameHandler3
_except_handler4_common
wcscpy_s
May be, they can be customized for to work with XP SP3
Dietmar
EDIT: msvcrt.dll from Vista or Longhorn 5048 crashes XP SP3.

#2602

diderius6

⇗ @Mov AX, 0xDEAD
The only strange behavior of using Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86
for lan debugging of XP SP3 on Win8.1 is, that I cant store the Symbol path,
so on each new use of this windbg I have to put the Symbol path there by hand.
All other works for me
Dietmar

#2603 | infuscomus | ⇗ @diderius6 can you not use the older XP debugger over a network?

#2604

diderius6

⇗ @infuscomus
I tried this and I can connect this debugger over lan.
But, because the files from Win8.1 for debug over lan want a password (what a crazy idea^^)
you cant do anything more until now after connecting with the old windbg.
An elegant way would be, to cancel the password question in the files from win8.1.
But until now I am not good enough in assembler to do that.
⇗ @Mov AX, 0xDEAD to me "Dietmar, learn assembler and you can do all this by yourself."
It is just true, this is what I tell pupils every day
Dietmar

#2605

diderius6

I just set up full Acpi XP SP3 on the Lenovo Flex 10 notebook.
All I do is via USB3:)), until now no need to open nice netbook
Dietmar
PS: If I do not succeed to integrate the Ven_&Dev ID from its wireless lan controller,
I try to enable debug via USB3.
⇗

#2606

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #2600

> @Mov AX, 0xDEAD
> "Register Window is empty if target is WinXP or Win2003"
> what does this mean for debugging XP via Lan for example with host Win8.1?

you dont see any registers, only manual "r" works

> Zitat

> How can I integrate the Newer Windbg (Win8/Win10) into Ida as plugin?

1) run windbg, break target PC, close windbg
2) run IDA->attach debugger->windbg debugger
-debug options->set specific-> kernel mode debugging
-connect string: net:port=50000,key=this.is.secret.key
3) select slot (0), wait for connection
In output window you can enter windbg commands, like "lm", "analyze", but often ida hangs, this is ida's bugs (
If module list is empty, try ".reload", sometimes it solve problem

> Zitat von ⇗ diderius6 im Beitrag ¶ #2602

> I cant store the Symbol path

set env variable
_NT_SYMBOL_PATH=SRV*%SYSTEMROOT%\SYMBOLS*⇗ http://msdl.microsoft.com/download/symbols

#2607

Mov AX, 0xDEAD

Status of KDNET for Windows XP x32:
Intel 10G big alloc buffer - ?
No patches to other files - Done
Any HAL - Done
Auto-disable device in pnp manager - Done
Win2003 version - Done
Auto calculate cpufreq option - ?
Windbg 6.3.9600.x under Windows XP - Done
Fixed Register Window - Done
Project - ⇗ https://github.com/MovAX0xDEAD/KDNET

#2608

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #2601

> Dependency Walker shows as only file with unmatched import functions
> msvcrt.dll
> __CxxFrameHandler3
> _except_handler4_common
> wcscpy_s

easy-peasy-japanesey:

    00000140:       06 05
    00000142:       00 01
    00000150:       B9 4D
    00000151:       35 D3
    00000152:       07 06
    0002E3E9:       68 90
    0002E3EA:       00 90
    0002E3EB:       04 90
    0002E3EC:       00 90
    0002E3ED:       00 90
    0002E400:       0C 08
    00033296:       57 90
    000332A0:       0C 08
    000488B4:       5F 00
    000488B5:       73 00
    000489F9:       34 33
    000489FA:       5F 00
    00048D33:       33 00

also need patch winxp/kdexts.dll, but much best:
1) use compatible msvcrt from newer OS, rename to msvcr1.dll, patch exe/dll to use msvcr1 instead msvcrt
2) compile msvcrt.dll from VS2008 sources, rename to msvcr1.dll, patch exe/dll to use msvcr1 instead msvcrt

    000ECEA2:       0B 00

seems works normal, we don't need anymore win7+ for host pc :)

#2609

diderius6

⇗ @Mov AX, 0xDEAD
Waaaoh:)) ,
I just cant believe,
what a nice work
Dietmar
PS: "If there is a Windbg for XP with password field, it may work."
There is no, so we make, I just test under XP SP3, works:))!!

#2610

dencorso

In case you find it useful, a long time ago BlackWingCat created a version of the vista msvcrt.dll which does not cause _except_handler4_common not found error. It's still obtainable from his Japanese language site, in an international version:
⇗ https://translate.google.com.br/translat...%2F1706829.html

## Page 175

#2611

diderius6

⇗ @dencorso
⇗ http://blog.livedoor.jp/blackwingcat/archives/1706829.html
this is the original link to msvcrt.dll from Blackwingcat
thanks:))
Dietmar
diderius6 has attached files to this post

- ⇗ msvcrt.rar

#2612 | Mov AX, 0xDEAD | WinDBG's Register Window fixed, ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (174)

#2613

diderius6

⇗ @Mov AX, 0xDEAD
Thanks a lot, I corrected dbgeng.dll and make checksum new. In the morning I tested the new Windbg under XP SP3 over lan a lot.
ACPI, Pcitree, lm, !analyze-v !devnode 0 1 and so on.
For me I need also the msvcrt.dll from Vista from Blackwingcat. In other case, in !devnode 0 1 Windbg tells, that a *.dll was not found. Windbg over lan is now fast as never before.
Do you have an idea, how to make the grafik on the Bay Trail cpu N2806 work under XP? I tested about 20 drivers, they give all code 10.
I think, Intel put (like into the USB driver) something like a VEN_8086 and DEV check,
so that NO compi from the Baytrail series (2013-2014) can work with XP.
But I only find the 8086 check in igxpmp32.sys driver. May be there is a cpu ID check?
This driver works for HD grafik in XP, but not for the device VEN_8086&DEV_0F31 (Netbook Lenovo Flex 10).
What do you think: Is there a chance to make this work? There are Win7 32 bit, Win8 32 bit drivers for this device but with a lot of unfullfilled dependencies under XP SP3
Dietmar
EDIT: Because all HD3000, HD4000, HD4400, HD5000, ... are treated identic in XP SP3 (see igxp32.inf),
I start to think, that there is no DEV ID check in XP igxpmp32.sys at all. DEV ID check appears in Win7 32 bit for DEV_0F31.
But this would simple mean, that all possible HDXXXX work with this driver in XP. And when it shows code 10,
this driver does just not work for this HD device DEV_0F31 in XP SP3. When I add to igxp32.inf DEV_0F31,
I can use the normal setup program from Intel. But without success after reboot.
And this "why HD not works in XP" depends also on chipset: The same cpu with the same integrated HD works on one chipset and on the other not, brrr...
EDIT2: I just noticed, that on Win7 32 bit, there are extra, other entries to registry for this device 0F31 with name Valleyview,
as for other HDxxxx, here it is named %iVLVGMT0% = iVLV2M_w7, PCI\VEN_8086&DEV_0F31
diderius6 has attached files to this post

- ⇗ igxpmp32.rar

#2614

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #2613

> @Mov AX, 0xDEAD
> But I only find the 8086 check in igxpmp32.sys driver. May be there is a cpu ID check?
> This driver works for HD grafik in XP, but not for the device VEN_8086&DEV_0F31 (Netbook Lenovo Flex 10).

look for dev_id checks around "8086 check", it may be complex like add XX /sub XX, then comparing.
in last drivers intel do check for dev_id, then set config like

    dev_id1:
    mov     dword ptr [edi+298h], 0Bh
    mov     dword ptr [edi+294h], 5
    mov     dword ptr [edi+28Ch], 11h

    dev_id2:
    mov     dword ptr [edi+298h], 3
    mov     dword ptr [edi+294h], 3
    mov     dword ptr [edi+28Ch], 6

so dev_id=>magic numbers

#2615

diderius6

⇗ @Mov AX, 0xDEAD
Thanks a lot,
I just find for example this, direct before Haswell GPU is mentioned

    text:10021BDE

    .text:10021BDE loc_10021BDE: ; CODE XREF: sub_10020DB0+1C0 j
    .text:10021BDE                                         ; sub_10020DB0+203
    j ...
    .text:10021BDE                 mov     edx, [ebp+arg_0]
    .text:10021BE1                 mov     dword ptr [edx+208h], 9
    .text:10021BEB                 mov     eax, [ebp+arg_0]
    .text:10021BEE                 mov     dword ptr [eax+204h], 9
    .text:10021BF8                 mov     ecx, [ebp+arg_0]
    .text:10021BFB                 mov     dword ptr [ecx+1FCh], 0Ch
    .text:10021C05                 mov     edx, [ebp+arg_0]
    .text:10021C08                 mov     eax, [edx+0DCh]
    .text:10021C0E                 or      eax, 80000000h
    .text:10021C13                 mov     ecx, [ebp+arg_0]
    .text:10021C16                 mov     [ecx+0DCh], eax
    .text:10021C1C                 push    offset aIntelRHdGrap_3 ; "Intel(R) HD Graphics Family"
    .text:10021C21                 lea     edx, [ebp+var_208]
    .text:10021C27                 push    edx
    .text:10021C28                 mov     eax, [ebp+arg_0]
    .text:10021C2B                 push    eax
    .text:10021C2C                 call    sub_1002F2D0
    .text:10021C31                 mov     [ebp+var_478], 38h
    .text:10021C3B                 mov     [ebp+var_469], 0
    .text:10021C42                 jmp     loc_10021D24
    .text:10021C47 ; -----

Now question is, how to change values, so that this becomes:)) DEV_0F31
Dietmar
PS: The check for this DEV ID I also found.
It is, where above is jumped from

    A9 loc_10020FA9: ; CODE XREF: sub_10020DB0+1B4 j
    .text:10020FA9                 cmp     [ebp+var_5C4], 166h   <-----  This is VEN_8086&DEV_0166
    .text:10020FB3                 jz      loc_10021BDE
    .text:10020FB9                 cmp     [ebp+var_5C4], 16Ah
    .text:10020FC3                 jz      loc_10021BDE
    .text:10020FC9                 cmp     [ebp+var_5C4], 402h
    .text:10020FD3                 jz      loc_10021C47
    .text:10020FD9                 jmp     loc_10021D15

Do you know anybody, who succeeds with this hack
166h => F31h
EDIT: This IDA extract is from very last XP Embedded for Intel GPU from February 2014.
diderius6 has attached files to this post

- ⇗ igxpmp32.rar

#2616

diderius6

⇗ @Mov AX, 0xDEAD
I just check this magic numbers in Win7 32 bit.
They are identic to XP Embedded.
DEV_0166 => (9 9 0Ch)
So I think, looking at Win7
DEV_0F31 => (9 5 0Fh)
But I have no idea,
what this numbers mean
Dietmar
EDIT: The last magic number seems to be a numerating of the devices:
DEV_0166 => (9 9 0Ch)
DEV_016A => (9 9 0Dh)

#2617

diderius6

⇗ @Mov AX, 0xDEAD
First hack does not work.
May be, that DEV_0F31 has other dependencies also,
for example entries in registry.
I change
DEV_0166 => DEV_0F31 (in igxp32.inf and in igxpmp32.sys)
and also its magic number in igxpmp32.sys from
(9 9 0Ch) => (9 5 0Fh)
as you can see with Ida Pro,
set correct Checksum but I still get code 10
Dietmar
PS: Here I send igxpmp32.sys from Windows Embedded before hack and after.
It is from Intel
⇗ https://downloadcenter.intel.com/de/down...s-Xp32-Embedded
and this one is the same DEV_0F31 Grafik driver for win7, win8, win10
⇗ https://downloadcenter.intel.com/de/down...dows-15-33-?v=t
EDIT: I just notice, that in Win7 32 bit the 0F31h appears also at 3 other places. Oha, this looks like hard work.
But also is interesting, that in this driver nothing changed from win7 to win10.
diderius6 has attached files to this post

- ⇗ IntelValleyView.rar

#2618 | XPWELL64 | ⇗ @diderius6 I benchmarked HL1 with anapa driver on my asus x555lb in windows xp and results are more terrible than windows 95 preinstalled pc. I will mod this igxpmp32.sys with ida pro can you tell me how to do it? My DEVID is: DEV_1616

#2619

Mov AX, 0xDEAD

> Zitat von ⇗ XPWELL64 im Beitrag ¶ #2618

> @diderius6
> I benchmarked HL1 with anapa driver on my asus x555lb in windows xp and results are more terrible than windows 95 preinstalled pc.

Anapa is VBE translator, no any acceleration, only frame buffer, so speed must be relative slow

#2620

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #2617

> @Mov AX, 0xDEAD
> First hack does not work.
> May be, that DEV_0F31 has other dependencies also,
> for example entries in registry.

I cant help with this, sorry, but as i know some guys from this forum overwrite dev_id in skylake+ drivers to work with new HD6xxx for Windows 7
They patched sys + dll

#2621

diderius6

⇗ @Mov AX, 0xDEAD
I make a test with Ida Pro on files from post and arround them.
⇗ Win 7 x64 Coffee Like UHD 630 Video driver (2)
In its *.inf the new Dev Ids are added and also some changes in registry.
I find differences compared via *.lst and Beyond Compare with original igdkmd64.sys and mod.
Original

    .text:0000000140047AE1		       mov     eax, 8086h
    .text:0000000140047AE6		       cmp     [rdx], ax
    .text:0000000140047AE9		      		      		       jz      short loc_140047AF8

Mod

    .text:0000000140047AE1                   mov     ax, 5912h
    .text:0000000140047AE5                  mov     [rdx+2],	ax
    .text:0000000140047AE9                  mov     eax, 8086h
    .text:0000000140047AEE                                                    jmp     short loc_140047AF8

DEV_5912 is a new device id. But other device ids are not added, hm, does it mean only one ID to mod is enough?
May be, that for other Dev Ids *.inf modding is enough.
No *.dll is modded
Dietmar
PS: ⇗ @canonkong please, can you tell me, how do you come to the idea to change this and do you know, how the other DEV_ ids are in igdkmd64.sys?
EDIT: I find my mistake in renaming DEV_0166 => DEV_0F31
Via this way through the logic of the XP Embedded driver it jmp to "Unknown Intel decive". Now fun goes on^^..
Hm, the XP Embedded driver looks also for the chipset..
EDIT2: The famous code 10 is gone. This seems to me, that the driver is started but crashes with
BSOD 0x7E (0xC0000005, 0x00000000,xxx,yyy)
For sure I hacked correct the DEV ID.
Now, Debug on the Lenovo Flex 10 would be nice. May be via USB3.
Now, with my last best^^ version of igxpmp32.sys it installs normal but hangs without visible BSOD at the end of the boot process. I want debugger:))!!
diderius6 has attached files to this post

- ⇗ ValleyViewII.rar

#2622 | Gelip | ⇗ @diderius6 I found how to disable signature checking in winload.efi 6.0.6001.16497 for boot WinXP x64 - read this: ⇗ winload.efi_patch This works ! You do not need the Advanced Menu and the Disable driver signature enforcement option anymore

#2623

diderius6

⇗ @Gelip
This are really nice news:))!! So testing for UEFI boot of XP can go on.
I know for sure, that also ⇗ @skullteria is most happy now.
Today I work all the day on the crazy igxpmp32.sys from XP Embedded
for to make it work with DEV_0F31.
I have the win7 32 bit driver with this DEV, but it is very different from the XP driver.
acpi.sys and usb is easy compared with the graphikdriver, its size is more than 2 Mbyte, brrr
Dietmar

#2624 | Gelip | Probably this patch will also work with winload.exe and winload.efi from any 64-bit version of Vista Beta, Server 2008 beta, Vista RTM
#2625 | diderius6 | ⇗ @Gelip Can the idea for this patch also be put on the 32 bit version of winload.efi (winload.exe) Dietmar

## Page 176

#2626

Gelip

> Zitat von ⇗ diderius6 im Beitrag ¶ #2625

> @Gelip
> Can the idea for this patch also be put on the 32 bit version of winload.efi (winload.exe)
> Dietmar

On 32-bit Windows, there is no signature checking, so you don't have to patch the loader.

#2627 | diderius6 | Waaaoooh, this compi is 1.576.800.000 times faster than the best supercompi today Dietmar ⇗ https://drive.google.com/file/d/19lv8p1f...p082Lc-kdD/view

#2628

infuscomus

⇗ @diderius6
winload 32bit from longhorn server beta 16497
infuscomus has attached files to this post

- ⇗ winload.zip

#2629 | Mov AX, 0xDEAD | Project "Kernel Debugging over LAN cable for WinXP/2003 x32 " published ⇗ https://github.com/MovAX0xDEAD/KDNET comments & bugreports welcome :)

#2630

diderius6

⇗ @Mov AX, 0xDEAD
This is great work:))!!
Today I test. I have a question: Is debugging with USB3 crossed debug cable also possible
with the same files,
have a nice day
Dietmar

#2631 | diderius6 | ⇗ @infuscomus From winload 32bit from longhorn server beta 16497, do you also have the winload.efi 32 bit version Dietmar
#2632 | infuscomus | ⇗ @diderius6 i have the 32bit 16497 ISO and unfortunately it seems that there is no winload.efi for the 32bit version.

#2633

diderius6

⇗ @Mov AX, 0xDEAD
Please add something like this text to your description of your nice project about windbg via lan on XP:
"When you have more than 1 lancard on your motherboard,
look in Device Manager and search there for your used lan card, here for example PCI-Bus 4, Device 0, Function 0 and
make an entry with this numbers in boot.ini with /busparams=4.0.0
so that the debugger knows, which NIC is used."
Dietmar
diderius6 has attached files to this post

- ⇗ WindbgFiles.rar
- ⇗ windbg81.rar
- ⇗ msvcrt.rar

#2634

jonny

hi, guys i need help installing windows xp pro x64 on my machine, im tryng to install it in 2 pc, the first is my laptop, is an ASUS X553MA, if i insert the windows xp 64 bit dvd it give me a BSOD and the error is the classic 0x07B, in the bios i set the hdd to ide mode and the BSOD goes away, but another BSOD appear this time is 0x07E, so i dont know how to fix it im trying all method, i also found a hacked ACPI.SYS in this forum, but when i insert in the win xp cd the setup give me a error, it say ERROR 14, NTKRNLMP.EXE COULD NOT BE LOADED, SETUP CANNOT CONTINUE. PRESS ANY KEY TO EXIT. i was using acpi 5048 from windows longhorn by the way, pls help me guys, thank you.
sorry for my very bad english, im italian.

#2635

diderius6

⇗ @Mov AX, 0xDEAD
Until now I can not debug the BSOD 0x50 made by the modded graphikcard driver igxpmp32.sys on the Lenovo Flex 10.
Is it a lot of work, to enable also USB3 debug for XP? I know, that lan debugging is much more stable.
I found in Win8.1 32 bit the driver kdusb.dll.
The Wlan works under XP SP3 on this Netbook, but the driver from Atheros is not
in the support list from Microsoft,
Dietmar

#2636

diderius6

⇗ @jonny
Make first a try with XP SP3 32 bit.
This is much more easy to install and you can test, if you do everything right with integrating acpi.sy_ (via makecab acpi.sys)
into the installationsfolder. The error "ERROR 14, NTKRNLMP.EXE COULD NOT BE LOADED, SETUP CANNOT CONTINUE. PRESS ANY KEY TO EXIT." can also happen, when a driver has not the correct checksum or the CD is not clean or contains an error
during its burning
Dietmar

#2637 | Andalu | On my asrock B250M-Pro4 the amd USB3 modded drivers seem to be incompatible with the 'chinese patch (XP64G2.1)' applied to support more than 4GB memory: the usb ports 2.0 are with no power and the usb ports 3.0, although powered, don't recognize the devices, mouse included. The shutdown also stops working with. I'm using the patch with no problem on my MSI-Q87 where the usb3 modded drivers unfortunately don't work. Someone is using with success the amd modded drivers and that patch or another method to remove the 4GB RAM limit?
#2638 | infuscomus | ⇗ @Andalu I PMed you an XP ISO to try, please try it.
#2639 | diderius6 | ⇗ @infuscomus Some new results about integrating USB3 drivers into XP SP3 CD? Dietmar
#2640 | Andalu | ⇗ @infuscomus Thank you ;)

## Page 177

#2641 | infuscomus | ⇗ @diderius6 I haven't been able to reproduce the problem you got, I would like to see if ⇗ @Andalu gets the same diderius6 can you test the ISO I PMed you both in VMWare/Virtualbox and real hardware? the Installing drivers part (and the rest of the install) should continue without user input if it is working properly.
#2642 | diderius6 | ⇗ @infuscomus I tried this Iso also on another compi. There it hangs suddently in the middle of txtsetup Dietmar

#2643

Mikedebian

Hello!
I have a Ryzen 1800X on a Biostar X470GTA motherboard, and I've had a bunch of issues. It's a bit tiresome replacing extracting and repacking cab files for a new fix (going through posts), so is there any ISO I can test out ⇗ @infuscomus ?
Please?

#2644 | infuscomus | ⇗ @diderius6 does the ISO work correctly in VMWare/Virtualbox?

#2645

diderius6

⇗ @infuscomus
I have not tested. Where is sense, it needs to run on real hardware.
I use Qemu, but only when nothing other helps.
This I do not understand: You have soso many good ideas, why dont make a good XP SP3 installations CD by yourself? You can..
Tomorrow I try to hack kdstub.dll (qualcom atheros) for lan debug,
because I noticed, that there I can change VEN_&DEV_ number
for my Lenovo Flex 10 notebook
Dietmar
PS: I am getting better in x86 assembler, what a crazy hard lesson in last 3 days.

#2646 | infuscomus | ⇗ @diderius6 just wanted to confirm if it worked correctly for you in VMWare/Virtualbox
#2647 | Mikedebian | Test ISO: Setup is starting windows... IRQ_NOT_LESS_OR_EQUAL 0x0000000A (0X0...0 0x0...2 0x0...1 0x8080F5C0)
#2648 | diderius6 | ⇗ @Mikedebian Switch everything in Bios off (any device, that you dont need for install) Dietmar
#2649 | Mikedebian | ⇗ @diderius6 Sorry, last thing to switch off was XHCI, which in turn disables my sata and usb ports and makes it unable to boot..
#2650 | infuscomus | ⇗ @Mikedebian just to test, if you press F7 to disable ACPI do you still get 0A BSOD?
#2651 | diderius6 | ⇗ @infuscomus ⇗ @Mov AX, 0xDEAD My hack in kdstub.dll (qualcom atheros) for lan debug of Lenovo Flex 10 netbook is ready. Tomorrow I test, if it is possible to do Windbg over Wifi:)) Dietmar PS: ⇗ @infuscomus I just burn CD, now I test it.
#2652 | Mikedebian | I attached picture Edit: Would like to attest that my RAM is fine. No errors since beginning, not OC and have been using it to install Windows 7,10, Vista, Linux, etc. Mikedebian has attached images to this post ⇗ IMG_20191008_010818.jpg

#2653

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #2633

> The Wlan works under XP SP3 on this Netbook, but the driver from Atheros is not
> in the support list from Microsoft

MS wrote drivers only for cable chips, no any wlan

> Zitat von ⇗ diderius6 im Beitrag ¶ #2633

> @Mov AX, 0xDEAD
> Please add something like this text to your description of your nice project about windbg via lan on XP:

Thanks for feedback, fixed
About USB3:
Yes, it possible to enable usb3 in KDNET, but on my hardware it is not works. Maybe cable is very bad or controllers want special pre-initialization, i dont know yet.
You can try, usb3 has special requirement - usb3.0 port on target must support "USB Debugging", can be checked with USBVIEW.exe from windbg install folder. Insert in port any device, check about "Debugging: YES", if NO - check other available ports. You need win8.1+ on HOST )
patch to kdnet.dll (then correct checksum):
C7 05 AE 11 02 80 02 20 C6 05 B0 11 02 80 FF 66
C7 05 AE 11 02 80 0C 03 C6 05 B0 11 02 80 30 66

#2654 | infuscomus | ⇗ @Mikedebian in the txtsetup.sif file - you can try removing all "usbxhc" and "usbhub30" entries, this will remove the USB 3.0 for textmode, but might fix the BSOD

#2655

daniel_k

> Zitat von ⇗ dencorso im Beitrag ¶ #2552

> @daniel_k: would you kindly take a look at the newer kernel versions and see whether it's possible to fix the modded AMD drivers so that they can be used with the latest kernel version? Sorry to bother and thanks in advance!

Hi, ⇗ @dencorso!
I've been finishing updating all my ISOs.
Now I can give a definitive feedback for every testing environment.
OS is always installed from Intel USB 3 ports using my modded driver, additionally I install from ASMedia, just to confirm the same behavior.

## Page 178

#2656 | Mikedebian | ⇗ @infuscomus Now there is no BSOD, but freezes at Setup is starting windows... Just stays there.

#2657

diderius6

⇗ @infuscomus
Compi hangs at exact the same place as before,
after Eula and installing devices,
no reaction, if I hit "next"
compi gets frozen with message "Not Responding".
At your place I would make brandnew CD, where is problem
Dietmar

#2658

daniel_k

BOOTING AND INSTALLING WINDOWS XP SP3 FROM AN USB FLASH DRIVE
System Setup:
- i7-8700K (stock speeds)
- Gigabyte Z370 AORUS Gaming 3
- 16GB RAM (2x8GB) Kingston HyperX FURY 2400MHz
- SSD 240GB KINGSTON V300 (used specifically for testing purposes)
- 16GB USB2.0 Sandidsk Flash Drive (used specifically for testing purposes)
- DVD-RW ASUS DRW-24D3ST
I have many more drives, but I disable all other AHCI ports except one connected to the SSD listed above and the other one connected to the DVD-RW also listed above.
1) Windows XP SP3 with all oficial updates, including POSReady ones, original ACPI.SYS (patched DSDT):
- Only my modded RSTe 4.7.0.1098 driver works. Skullteria's STORAHCI and last official Intel's IASTOR 11.2 cause Setup to suddenly restart during GUI mode before Installing devices.
- AMD USB3 driver works properly through the whole installation, just like ASMedia's. Disabling AMD's driver doesn't help with the above issue.
2) Windows XP SP3 original ISO, no updates, original ACPI.SYS (patched DSDT):
- Same behavior as case above.
3) Windows XP SP3 with all oficial updates, including POSReady ones, patched Vista beta 5048 ACPI.SYS:
- Same behavior as case above.
4) Windows XP SP3 original ISO, no updates, patched Vista beta 5048 ACPI.SYS:
- Same behavior as case above.
CONCLUSION:
As it turned out, this issue lies in the USB install itself.
For some reason only my modded RSTe 4.7.0.1098 driver works and it has nothing to do with the latest kernel update as the original SP3 kernel is also affected by the issue.
Thought it could be a device enumeration issue, but it doesn't make sense at all.
Maybe the issue is specific to 8th generation boards?

#2659 | Mikedebian | It loaded it loaded!!!
#2660 | daniel_k | ⇗ @Mov AX, 0xDEAD, nice job with KDNET and thanks for sharing it publicly! Any plans to work on an x64 version?
#2661 | infuscomus | ⇗ @diderius6 was this in VMWare or Virtualbox or both? Strange, I do not get this behavior even in VMs - also, I do not click next, just wait it continues on its own - maybe clicking next is causing the crash?
#2662 | Mikedebian | Picture Mikedebian has attached images to this post ⇗ IMG_20191008_020437.jpg
#2663 | infuscomus | ⇗ @Mikedebian nice!
#2664 | Mikedebian | Not too supported! Installing the usb driver in XP blue screens the system! Mikedebian has attached images to this post ⇗ 1570494199413573948718909
#2665 | infuscomus | ⇗ @Mikedebian can you get the HWIDs for all the hardware missing drivers? and the USB that BSOD too

#2666

diderius6

⇗ @daniel_k
Why did you change back to original acpi.sys?
Do you think it is possible, to make a generic DSDT for all compis?
May be like translator which translates Acpi 2.0 text to Acpi 1b in DSDT.
I think, the Ryzen hack has to stay in acpi.sys for Ryzen boards
Dietmar

#2667

diderius6

⇗ @infuscomus
On the Lenovo Flex 10 netbook
I can install your XP SP3 via USB CD rom,
no need to tip on "next",
nice:))
Dietmar
PS: I will try direct USB boot install on the other compi too.

#2668 | Mikedebian | Is there a program for windows xp that generates a text file with all the hw ids? Can I use Linux for this? Would the output of lspci -vv be helpful? I am typing this from within windows xp!
#2669 | infuscomus | ⇗ @Mikedebian There are programs that will do this, but we only need the HWIDs missing drivers e.g. Device Manager -> Other Devices -> PCI (USB) controller -> Properties -> Details -> drop down menu - Hardware IDs -> PCI\VEN_1022&DEV_43B9&CC_0C03
#2670 | Mikedebian | Here is for USB Mikedebian has attached images to this post ⇗ 1570495472538213885878745

## Page 179

#2671 | infuscomus | ⇗ @diderius6 Awesome! So it is working for some Intel systems at least, just not all
#2672 | Mikedebian | Second Mikedebian has attached images to this post ⇗ 1570495640417855598997735
#2673 | infuscomus | ⇗ @Mikedebian Try Fernandos driver - ⇗ https://www.win-unattended.de/Benutzer/F....5.3%20WHQL.rar
#2674 | Mikedebian | Hey, now it works! My VEGA 56 is probably never going to be compatible with anything below Windows 7 (never say never!), and I have to download the driver for my sound card, but there are still the sm bus controller, PCI Encryption / Decryption controller, and 4 pci devices marked yellow!
#2675 | infuscomus | ⇗ @Mikedebian grab the HWIDs for the yellow marked devices and we will see if we can get drivers for them.
#2676 | Mikedebian | ⇗ @infuscomus Here is a picture ⇗

#2677

daniel_k

BOOTING AND INSTALLING WINDOWS XP SP3 FROM A DVD DISC
System Setup:
- i7-8700K (stock speeds)
- Gigabyte Z370 AORUS Gaming 3
- 16GB RAM (2x8GB) Kingston HyperX FURY 2400MHz
- SSD 240GB KINGSTON V300 (used specifically for testing purposes)
- DVD-RW ASUS DRW-24D3ST
I have many more drives, but I disable all other AHCI ports except one connected to the SSD listed above and the other one connected to the DVD-RW also listed above.
1) Windows XP SP3 with all oficial updates, including POSReady ones, original ACPI.SYS (patched DSDT):
- All AHCI drivers work (my modded RSTe 4.7.0.1098, Skullteria's STORAHCI and last official Intel's IASTOR 11.2).
- AMD USB3 driver works properly through the whole installation, just like ASMedia's.
2) Windows XP SP3 original ISO, no updates, original ACPI.SYS (patched DSDT):
- Same behavior as case above.
3) Windows XP SP3 with all oficial updates, including POSReady ones, patched Vista beta 5048 ACPI.SYS:
- Same behavior as case above.
4) Windows XP SP3 original ISO, no updates, patched Vista beta 5048 ACPI.SYS:
- Same behavior as case above.
CONCLUSION:
Booting from a DVD disc and installing Windows XP is the easiest way to get the job done.

#2678

daniel_k

Does hibernation work?
Using the patched Vista beta 5048 ACPI.SYS, hibernation does work, as long as you are NOT using Intel USB3 ports.
When system returns from hibernation (after a power on), Intel USB3 controller won't work properly until the system is restarted.
On the other hand, if you use any other USB3 controllers with original drivers (ASMedia and VIA, I tested myself), everything works as it should.
But frankly, with cheap SSD nowadays, I wouldn't use this feature as it takes too much time until Windows is ready for use.

#2679

daniel_k

> Zitat von ⇗ diderius6 im Beitrag ¶ #2666

> @daniel_k
> Why did you change back to original acpi.sys?
> Do you think it is possible, to make a generic DSDT for all compis?
> May be like translator which translates Acpi 2.0 text to Acpi 1b in DSDT.
> I think, the Ryzen hack has to stay in acpi.sys for Ryzen boards
> Dietmar

Just did a final test with original and modded acpi.sys when installing XP from USB or DVD as you can see from my reports.
Personally, I've patched my DSDT table and just use original files.
For current Intel boards, it's easy to patch.
For Ryzen, I don't think we well ever have a DSDT patch as the issue is more complicated.

#2680

infuscomus

> Zitat von ⇗ daniel_k im Beitrag ¶ #2679

> For Ryzen, I don't think we well ever have a DSDT patch as the issue is more complicated.

What is the issue? do we know exactly?

#2681

infuscomus

⇗ @Mikedebian
PCI\VEN_1022&DEV_1451 - AMD IOMMU Device
PCI\VEN_1022&DEV_1455 - AMD PCI
PCI\VEN_1022&DEV_1456 - AMD Family 17h (Models 00h-0fh) Platform Security Processor
PCI\VEN_1022&DEV_145C - AMD USB3 Host Controller drivers / Micro-Star MS-7A34
PCI\VEN_1022&DEV_145A - AMD PCI
PCI\VEN_1022&DEV_790B = AMD SMBus
I think driverpacks solution can cover these - ⇗ https://drp.su/en
PCI\VEN_1987&DEV_5007 - AMD NVME - ⇗ @diderius6 posted a driver for this somewhere in this thread.

#2682

Mikedebian

It wants to install the USB device as AMD usb 3 controller and I point it to the driver pack that you told me about earlier. It finds it and it's all good, but then it wants usbxhc.sys to complete the install, and if I do select usbxhc.sys from the installation medium of windows xp, I get instant blue screen.
Another device that fails is the AMD PSP 3 driver.
Edit:
Also, is there a link to the NVME driver?

#2683 | infuscomus | ⇗ @Mikedebian what BSOD error code did you get? it might be best to leave the USB 3 uninstalled for the moment
#2684 | Mikedebian | Picture Mikedebian has attached images to this post ⇗ 1570525529787575353015910 ⇗ IMG_20191008_110357.jpg
#2685 | infuscomus | ⇗ @Mikedebian what was the HWID of the problem USB device? was it PCI\VEN_1022&DEV_145C ?

## Page 180

#2686 | Mikedebian | ⇗ @infuscomus Yes, that is correct!

#2687

Andalu

⇗ @infuscomus
Installation with pendrive completed. Two manual restarts are needed during the setup.
With the F5 key I can choose only Standard PC with C-Step i486, other options are not present; I pressed the F7 key and I got 'Multiprocessor MPS' so no cpu cores in the device manager (even if 4 cores are visualized in the task manager); acpi.sys is not present so shutdown and restart don't work. USB3 works fine.
An error occurs during the driverpacks installation on searching the "WinXPPx86IE - setup.cmd": file not found.
Applying the 'chinese patch' I got bsod 7B on next boot.

#2688 | infuscomus | ⇗ @Mikedebian some alternate USB drivers to try ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (128) ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (89)
#2689 | infuscomus | ⇗ @Andalu you should be able to see "ACPI multiprocessor PC" if you press the up arrow a few times. does it work without pressing F5/F7 key? does it work unmodified?

#2690

Mikedebian

> Zitat von ⇗ infuscomus im Beitrag ¶ #2688

> @Mikedebian
> some alternate USB drivers to try
> ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (128)
> ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (89)

The second link worked with great success! Now it is only PSP driver lacking.

#2691 | Mikedebian | ⇗ @infuscomus Is it normal that windows xp only sees one core? Process lasso only sees one core too. Edit: It's listed as "Standard PC" in device manager
#2692 | infuscomus | ⇗ @Mikedebian in device manager, under computer do you see "ACPI multiprocessor PC" or something else?
#2693 | Mikedebian | Only "Standard PC" and I can not update the driver to anything else.
#2694 | infuscomus | ⇗ @Mikedebian "Standard PC" is only one core, I think you can update driver to "ACPI multiprocessor PC" manually without reinstalling, but I have not tried this myself.
#2695 | Mikedebian | ⇗ @infuscomus I've seen that ⇗ @diderius6 has that. How did he do it? How would I theoratically update?
#2696 | infuscomus | ⇗ @Mikedebian When updating driver try Install from specific location -> don't search, I will chose which driver to install.
#2697 | Mikedebian | Yes, that is what I have done and it only gives me one option even if I disable the checkbox "Only show compatible hardware"

#2698

diderius6

⇗ @Mikedebian
Update to "ACPI multiprocessor PC" from "StandardPC" does not work.
I make a trick: I installed full "ACPI multiprocessor PC" on another compi.
Then, on this other compi I add hal.dll and ntoskrnl.exe from "StandardPC"
and add an entry for them in boot.ini.
This XP then I copy to first PC,
so I have both
Dietmar

#2699 | infuscomus | ⇗ @Mikedebian when updating try Have Disk.. -> C:\WINDOWS\INF\HAL.INF select "ACPI Multiprocessor PC" diderius6 boot.ini method is probably safer.
#2700 | Mikedebian | Oh so I did it wrong in the beginning? I can't remember an option to select multicpu in install

## Page 181

#2701 | Mikedebian | Oh so I did it wrong in the beginning? I can't remember an option to select multicpu in install

#2702

infuscomus

⇗ @Mikedebian
setup is supposed to detect multiprocessor for you, unless you pressed F5 or F7 and selected "Standard PC"
you can force setup to use multiprocessor by pressing F5 then pressing the up arrow until you get to "ACPI muliprocessor PC" and selecting it.
⇗ @diderius6
do you remember how to modify boot.ini to add an option for ACPI multiprocessor?

#2703

infuscomus

⇗ @Mikedebian
I found an example entry you might be able use in boot.ini
make a 2nd entry e.g.
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP MultiCore" /fastdetect /NoExecute=OptIn /kernel=ntkrnlmp.exe /hal=halmacpi.dll
attached a halmacpi.dll and ntkrnlmp.exe for you - place in C:\WINDOWS\SYSTEM32 of XP
infuscomus has attached files to this post

- ⇗ mikedebian.zip

#2704 | diderius6 | ⇗ @infuscomus I tried this, does not work. Only vice versa from "ACPI Multiprocessor PC" to "Standard PC" is possible Dietmar
#2705 | Mikedebian | I only get options F6 or F2 when booting install
#2706 | infuscomus | ⇗ @Mikedebian the F5 and F7 options exist, setup just doesn't tell you about them. I think at this point it is best to reinstall XP, press F5 during setup (during F6 prompt) and manually force "ACPI Multiprocessor PC"

#2707

Andalu

> Zitat von ⇗ infuscomus im Beitrag ¶ #2689

> you should be able to see "ACPI multiprocessor PC" if you press the up arrow a few times.

You are right, my mistake. I tried just now for multiprocessor acpi but the installation hangs on "setup is detecting and installing devices on your computer"; only the ps/2 keyboard and the pendrive is attached to computer, no usb or ps/2 mouse. The same happens without pressing the F5 or F7 keys. I'll try again.

#2708 | Mikedebian | Only option I get is standard pc with c-step i486 Edit Herp derp lol
#2709 | infuscomus | diderius6 also reported it hangs on "setup is detecting and installing devices on your computer" so your not the only one - try NOT clicking next and just try waiting a bit see if it responds? I have not encountered this issue for myself on my hardware, works fine on ryzen and Z97.
#2710 | Mikedebian | Can I safely install the unofficial XP sp4 June 2019 on this?
#2711 | infuscomus | ⇗ @Mikedebian I'm not sure, I think it should be OK. install it in a VM to test first, just to be safe.
#2712 | Andalu | ⇗ @infuscomus tried again, I waited 10 minutes with no clicking, same behavior.
#2713 | infuscomus | ⇗ @Andalu OK, thanks for the testing. I'll try to make a new xp usb3 iso image with unmodified source.
#2714 | Mikedebian | Waiting works for me. Never tried to click next. Wait about 7 seconds
#2715 | Andalu | ⇗ @infuscomus I tried your iso on my crazy asrock B75 Pro3-M Ivy board: installation completed without errors (except for WinXPPx86IE) but the USB3 doesn't work.

## Page 182

#2716 | infuscomus | ⇗ @Andalu post #2688 i left links to posts containing alternate USB 3 drivers to try.
#2717 | Mikedebian | ⇗ AMD GPIO Controller ACPI\AMDI0030 *AMDI0030 Also, which page is the NVME driver on???

#2718

diderius6

⇗ @Mov AX, 0xDEAD
My Hack in kdstub.dll from Atheros does not work
on the Lenovo Flex 10 card.
The debugger just do not connect. Is there a principial difference between lan NIC and Wifi Nic?
This means, other networkcards do (may?) not work, when they are added to the original Microsoft 8.1 kdstub.dll files
Dietmar
PS: I tested both versions from lan debug: Alpha and the new one.
On cable lan NIC with from Microsoft supported networkcard it works nice and fast.
diderius6 has attached files to this post

- ⇗ kdstubAtheros.rar

#2719 | Andalu | ⇗ @infuscomus I have already tried all the alternative drivers on my crazy B75 Pro3-M with no success. The only one that seems to work (??) is the amd modded driver but I still have the problem reported in ¶ #2587: this board needs to be always on...it's impossible, so it's correct to say: the usb3 doesn't work on this mysterious board... at least for now :)
#2720 | infuscomus | ⇗ @daniel_k do you have any other USB 3 drivers for ⇗ @Andalu to try?

#2721

schreiberstein

Hello!
It is so amazing that you folks over here at win-raid.com were able to get Windows XP / 2003 working on such modern hardware. Unlike other forums where people say "nah, this cannot be done. Just go with the time", you put in the effort to to patch, hack and experiment. I usually expect this kind of stuff from msfn.org, so it is great to see a German forum take the lead in this, (being Germany myself) hehe. Thank you so much to everyone involved in this.
My system:
--------------
Gigabyte Z390 Designare (Cannon Lake PCH)
Intel Core i9 9900K, 32GB RAM
AMD Radeon RX 580 8GB (I am aware this is not XP compatible)
Onboard Network cards: 8086:1539 (I211), 8086:15BC (I219-V)
Onboard AHCI controller: 8086:A352
--> PCI cards work using DELOCK 41341 Riser Card PCI-Express to PCI (tested on Windows 10 with Creative Audigy 2 ZS)
This system is my daily driver on Apple Mac OS X ("Hackintosh"), but I tried to get Windows XP x86 running two or three months ago.
I used good old Winfuture xp-Iso-Builder to integrate Fernando's driver, booted from CD and was able to install XP SP3 (US English) with ACPI disabled, otherwise the installation would crash.
USB keyboard and mouse worked using the integrated legacy support (I have no idea how they implemented that. Magic.), but it is also possible to use a real PS/2 keyboard and mouse using a StarTech KYC1MF PS/2 Y-Adapter.
As far as I remember, all cores were detected properly, but a lesser amount of RAM than the expected 3.25GB were detected. Boot took unusually long. It seems like it was stuck somewhere before the kernel got executed.
I would be happy to volunteer to serve as a guinea pig of some sort, given I have one of the newest systems available.
For now, I would like to refrain from BIOS patching for altering the ACPI table. I am not sure my Mac OS X bootloader could cope with changes in the ACPI table - and I also do not want to brick my board.
(I do not think I can actually choose which BIOS chip to load from. Gigabyte's "DUAL BIOS" will choose it automatically based on failed previous boot attempts, I suppose. If it actually is possible, I might be up for some experiments sometime.)
My questions:
- Is it possible to achieve a mostly working system without modifying the ACPI table on the chip?
- Is there any hope to get any of the integrated Intel ethernet controllers working?
My ideas (as gathered from this long post):
- Create Windows XP SP3 EN_US ISO
- Integrate AHCI driver TXTSETUP
- "Integrate" patched ACPI.SYS using makecab procedure (Which one would be the best version?)
- Install Windows XP with ACPI enabled
- Install modded Intel USB3 driver
- Play 3D Space Cadet Pinball
- Profit
Am I missing any recent findings of you guys, or does this sound like a doable way to get XP running with ACPI and multicore support on this machine?
Just for fun: I also had trouble getting anything DOS or Windows 98/ME related running (EMM386 not installed - incorrect machine type.), even when applying the patches from RLOEW for AHCI and memory. It seems that there is something about this architecture that the MS-DOS memory manager EMM386 just cannot handle. If I inserted a Geforce 7000-series card into one slot, it could theoretically be semi-usable.
Thank you.
Cheers,
Alexander (schreiberstein)

#2722

XPLives

⇗ @schreiberstein
Guten Tag Schreiberstein,
I didn't know the board was in German originally as Fernando did a very good job making it all English. Only the hints are in the editor when you see German words.
From one of my favorite earliest games famous quote, "Halt Stop, Mein Name Ist". Somehow I believe banned in Germany.
Hard to know why the install froze. I would try using CD disc burned method to install from scratch. Use a 128GB drive FAT32 partition and can be split into 32GB each.
What kind of Hackintosh Mac OS do you have setup on your Z370?
What is the oldest MAC OS X version that will work on it? I want to try Tiger 10.4 if that's even possible for legacy support? Would be funny to run Mac OS Tiger on Tiger Lake Intel CPU Chipset in the future.
Can you write a make a new thread and write a guide and steps on how you got your Hackintosh working on your Z370 i9-9900K system. I would be interesting to make an XP/Hackintosh setup. I also use a SB Audigy ZS 2 for my systems though I had to use another model now since the original one fried in an experiment. Which Windows 10 drivers are you using for the sound card? I think the official ones go up to Windows 7.
There might be some tools getting a Hackintosh to work that might benefit XP and UEFI.
What kind of functionality is your Hackintosh?
Does video card and sound card work? What drivers are you using for it?
Does Intel USB 3.0 ports work?
What about network LAN? Do both Intel LAN models ethernet ports work?
To me it sounds like it would be more difficult to get Hackintosh working than XP?
How long did it take you to get the Hackintosh working?
Was this your first Hackintosh build?
The DOS memory issues existed since Sky Lake 100 Series from my own experience. Something to do with how conventional ram is separated is different and might be connected to the iGPU shared memory. Also most PCI sound cards don't work in DOS so only Windows 98SE might be the oldest to work with drivers. Someone with Assembly and BIOS experience might be able to fix the EMM386 issues. AMD doesn't seem to have this issue so maybe comparing the BIOS to see why this occurs.
Do you have any of the DOS/Windows Non XMS Ramdrive software that RLoew created for testing?

#2723

Mikedebian

What is the latest modified storport driver?
"Community NVME 1.3 Storport Miniport by Schtrom"
This device cannot start, code 10
Yellow checkmark.
Also, AMD GPIO driver is checkmarked yellow. I did the snappy driver installer in expert mode and downloaded the pack. Only found windows 7 gpio driver? Anybody else can confirm? ⇗ @diderius6
do you have gpio working?
Those are my last two devices and then my X470GTA is fully supported.
690LC is basically my water cooler to control rgb, not needed.
Video gpu is vega 56, not supported.

#2724

daniel_k

> Zitat von ⇗ infuscomus im Beitrag ¶ #2680

> > Zitat von ⇗ daniel_k im Beitrag ¶ #2679

> > For Ryzen, I don't think we well ever have a DSDT patch as the issue is more complicated.

> What is the issue? do we know exactly?

As the DSDT table is mostly the same as previous AMD platforms and the ACPI.SYS from Vista 5048 beta doesn't work without changes, certainly AMD changed the PIC in a way it isn't compatible with XP.

#2725

daniel_k

⇗ @schreiberstein, sent you a ready to use pack you can use to build your own compatible XP SP3 installation disc.
Make sure you read the instructions in the ReadMe.txt file.
Additionally, you can create a bootable USB flash drive with WinSetupFromUSB. Personally, I've tried with v1.8.
In this case, you don't need to run BUILDCD.BAT, just run WinSetupFromUSB and choose C:\GRTMPFPP_EN\CD as the source folder.

#2726

schreiberstein

⇗ @XPLives
Hello XPLives,
Thank you!
Everything that could be said about my Hackintosh setup can be found in an extraordinary, detailed guide made by an extremely helpful individual over at TonyMacx86:
⇗ https://www.tonymacx86.com/threads/succe...-rx-580.267551/
It is a Z390 system from late 2018 by the way. The parts have been selected to work with macOS Mojave.
I have quite a lot of hackintosh experience (intermediate level, I'd say), but proceeded to use real Macs for years since there were always some quirks involved. And simply because my iMac did all I needed, until it didn't.
This is very different from hackintoshing in the early 2010s. A lot more sophisticated. It is an insane amount of work what people put into patching and modding.
This build works 100%. Never crashed once. No kernel panics. 100% stability. 100% sleep capabilities. 100% wifi, bluetooth, usb3, onboard audio, ThunderBolt 3, iMessage, FileVault boot volume encryption (YES!) etc.
I was initially hesitant to shill out this amount of money on a new system and said to myself "send it back within 14 days if you cannot get it working perfectly"...
What can I say... I built it one Friday night in January, installed Windows and completed my entire macOS installation with everything working by Sunday evening. It pretty much works like a real Mac.
However, there were some things I needed to fix manually to get FileVault encryption working. But the guide is pretty complete. I am uttermost satisfied with this build.
It is insane how well it works.
⇗ https://www.tonymacx86.com/threads/assor...ckintosh.11234/
I built several Hackintoshes over the years (some homeservers, some virtual machines (Linux KVM with PCI-e passthrough and custom patchy kernels back in 2013, very tricky, lovely memories)). My first hackintosh build was in January 2011 (I was 15 at that time) - a Gigabyte GA-H55M-UD2H. It was a huge and cheap upgrade to my MacMini of that time, but the board was very unstable. Even on Windows. Sudden reboots, regardless of RAM or PSU. I then used an iMac 2011 from 2013 onwards. I then switched to a MacBook Pro 2013 in 2018 but really disliked the experience.
I now run this Hackintosh machine with two Apple Cinema HD 30" 16:10 displays connected and a "retro" Apple Extended Keyboard II from the early 1990s. It feels better than any Mac I have ever used in my life. The i9 really is a beast.
My intention was to build a system I would use for the next 5 years that would be Mojave (32 Bit + iTunes intact) compatible and that was somewhat overpowered, yet quiet.
I doubt Tiger would work. It already crashed in a virtual machine on everything higher or equal to Haswell. Something about the CPU. Maybe Snow Leopard. I have way to many "vintage" Macs to justify attempting such a project, lol.
The audio drivers for Windows 10 were : ⇗ http://danielkawakami.blogspot.com/2015/...rt-pack-61.html
There are also drivers for OS X, but mine did not survive sleep and wake. The audio stopped working afterwards. Sleep (ACPI S3, not my body lol) is very important for me. I barely ever turn off my computer.
But there are folks working on that over at the insanelymac forum, if I remember correctly. The kX Audio Driver is open source, after all.
A regular Audigy 2 ZS costs ~20 on German eBay these days. I originally bought it for my Windows 98 Athlon 64 rig, but its FireWire port steals the desired IRQ5 that I can assign in the BIOS. The Live! is better in that regard.
I recently purchased a used EVGA nVidia Geforce GTX 780 (non TI for compatiblity) which should work in both Windows XP and Mac OS X (it is the last supported nVidia GPU generation that is natively supported without "webdrivers" for OS X, which currently are not available for Mojave, as discussed on MacRumors) - However, the Radeon RX 580 feels much smoother on Mac OS X.
The 780 GTX still supports analog VGA out via DVI (for my Sony Trinitron CRT), which the Radeon does not support.
But since this is an ATX board, I could drive both cards. Incompatible GPUs can be made invisible via DSDT patches (also mentioned in the TonyMac guide), as they otherwise mess with sleep. The Geforce 780 wouldn't cause any issues though.
Getting the Hackintosh working will be much easier than XP, given that nearly all of the hardware is incompatible.
I suppose all will be fine if I get ACPI and thus IRQ management working on XP. If you don't mind dozens of add-in cards, I guess you can get nearly any system working.
I do not know why, but I really have an obsession with getting old stuff working on new systems.
--> My installation froze because of "not fully ACPI compliant" - 0x000000A5 . The typical issue discussed on here. Without ACPI, everything went smoothly and the system was stable, but nearly unusable due to severe IRQ conflicts.
Drivers for my Renesas USB3 PCI-E card would not work either. Probably due to the lack of "resources".
It would be really NICE to just get Windows 98 or ME to boot. ME actually went further in the installation. I was able to install it, but it then crashed during the first restart, even after I patched the memory and all that jazz.
No, I do not have any other software from RLOEW. But I purchased both AHCI and Memory patch. Partly because I wanted to support and compliment him for his work. I did not really expect it to work on Z390.
If you have any idea how to work around this issue, I would be very happy to hear about it. I doubt anyone would be able to get universal USB drivers working though. Well... I guess people need some challenges for the 2020s, haha!
If you have any questions regarding your Hackintosh project or about this build, feel free to send me a private message.
Cheers,
schreiberstein

#2727

schreiberstein

⇗ @daniel_k Thanks a lot! That was quick!
I will give that a try! Super helpful.
I won't bother with that USB stuff.
One burned CD-R a day keeps the Greta away.
#TuesdaysForLasers #SaveThePitsAndLands
Cheers,
schreiberstein

#2728 | daniel_k | ⇗ @schreiberstein, you're welcome! Just give me your feedback.
#2729 | XPWELL64 | In MattKC's video,Windows 98 detects internal laptop keyboard and touchpad on Lenovo Thinkpad T480. This is a problem related with vendors that disable XP compilant acpi in dsdt section. This is vendor related thing. Another confusing thing is that Broadwell+ Muxless laptops cannot install GPU drivers. You can't use HDMI you can't use bluetooth you can't play games and you cannot use internal things in Windows XP.

#2730

daniel_k

> Zitat von ⇗ infuscomus im Beitrag ¶ #2720

> @daniel_k
> do you have any other USB 3 drivers for @Andalu to try?

No, all available modded drivers can be found in this topic.

> Zitat von ⇗ Andalu im Beitrag ¶ #2719

> @infuscomus
> I have already tried all the alternative drivers on my crazy B75 Pro3-M with no success. The only one that seems to work (??) is the amd modded driver but I still have the problem reported in ¶ #2587: this board needs to be always on...it's impossible, so it's correct to say: the usb3 doesn't work on this mysterious board... at least for now :)

The USB controller doesn't work at all or it works but is limited to USB2 speeds?

## Page 183

#2731 | POE_UK | The problem is simple, there are very few 32bit drivers for any modern system.

#2732

diderius6

⇗ @Mov AX, 0xDEAD
I make a test to install USB DEBUG 3.0 on the Lenovo Flex 10 under XP SP3.
I get an USB 3.0 Super-Speed A/A Debugging Cable 10ft
⇗ https://www.datapro.net/products/usb-3-0...ging-cable.html
Hm, usbview.exe tells me, that USB debug is not supported on the Lenovo Flex 10 xhci port.
I also take a look at USB2.0 debug, which should work from Vista and above.
The content of my boot.ini for this is (looks very simple, hope not too simple:)) )
[boot loader]
timeout=30
default=C:\WINDOWS
[operating systems]
C:\WINDOWS="Windows XP" /noexecute=optin /fastdetect
C:\WINDOWS="Windows XP QEMU DEBUG" /noexecute=optin /fastdetect /DEBUG /DEBUGPORT=USB /BUSPARAMS=0.14.0 /targetname=otto
When I start XP SP3 with this USB debug settings, it starts at once again with to chose an entry from boot.ini.
Here I mention, that on Vista (for USB2.0 boot) the BUSPARAMS=0.14.0 is a HEX value (from Win7 and above it is only decimal value)
means in Device Manager is shown BUSPARAMS=0.20.0 in decimal for the xhci port.
I do not know, if I should make a test for USB debug with Win8.1, even I have original Win8.1 on the Lenovo Flex 10
Dietmar
PS: Here are my modded files for XP SP3 USB3 debug. I mod only kdnet.dll (the new for lan modded version kdnet.dll with some extra HEX values. There I noticed an write error in the post it has to be
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (177)
C7 05 AE 11 02 80 02 00 C6 05 B0 11 02 80 FF 66 =>
C7 05 AE 11 02 80 0C 03 C6 05 B0 11 02 80 30 66
diderius6 has attached files to this post

- ⇗ USBdebug.rar

#2733

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #2730

> The USB controller doesn't work at all or it works but is limited to USB2 speeds?

Please see my post at ¶ #2587

#2734

diderius6

But it is not me to give up.
I want to make the grafik driver work under XP on the Lenovo Flex 10.
The BSOD 0x50 which is shown I have seen in such situations,
when nearly(!) all was ready. May be, it is a problem of the IRQ configuration,
because under XP SP3 the lan network, sound and the graphikdriver all want IRQ7.
I ordered the very last compi
⇗ https://de.aliexpress.com/item/328158978....1fa24c4d2dAgxo
because it has one of the very rare boards with an N2806 Bay Trail cpu
Dietmar

#2735

tarsonis

Hi there,
hope for getting a direction. I was using XP 32bit dual boot on my Ivy Bridge the last ten years and was stumbled to find out that its a pure hassle to get it running on AM4 unfortunately. Now with my Asus CH6 wifi (latest bios) with 1800x I try to get it running. After I found a user who got it running on this board with links to the files offered in this thread I was happy that there seems to be a chance. I used the latest files from this thread, created a XP cd with nlite but not able to install at all. I tried USB stick method month ago but gave up as I did not succeed at all. Since it works on this board I'm desperate to find out how since month... So any help is much appreciated.
I used the files from this thread:
acpi5048_x86_intel_amd_final.rar = compressed acpi.sys with Cabpack 1.4 and replaced it with the one nLite created in the final iso
AHCI32bit package which should have all drivers posted by diderius6 (inf selection in nlite - textmode - I selected all available in the list)
AMDXHCI_XP_FINAL package posted by diderius6 (inf selection in nlite - textmode)
When I select the processor (F7) I get always 7B error after setup is finished loading files with:
ACPI Multiprocessor
MPS Multiprocessor
Standard PC
If I don't select any Processor at all I get error 5 saying just random advice to check for virus and such. Since there are two important things to get it running (ahci and acpi) I can't figure out which produces the error. Or they maybe both produce the BSOD.
Did I made something wrong with nlite and the files I took from here or I'm just without luck? This board is a nightmare since the day one...
Or do I have to set anything in the bios first (the board is missing a IDE compatible mode obviously)?
Another possibility what I though is. I got my old working XP on hdd which worked on my IVY Bridge. Is it possible, without serious coding skillz, to reconfigure the OS files to be able to boot into it?

#2736

diderius6

⇗ @tarsonis
For me, ONLY the STORAHCI driver from ⇗ @skullteria works on AM4 Ryzen board
Dietmar
PS: ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (59)
Integrate via nlite storahci.sys.
Make storport.sy_
from it via
makecab storport.sys
and put it into installationsfolder i386 from Installations CD.

#2737

diderius6

⇗ @Mov AX, 0xDEAD
On the Asrock fatal1ty z370 gaming k6,
with the same files for USB debug,
compi also reboots at once, so something with the USB debug files or with my boot.ini settings
on the target is not ok for XP SP3
Dietmar
EDIT: No clear statement about USB debug is possible until now for me, because usbview.exe also
on the Asrock fatal1ty z370 gaming k6 board tells: No debug port.
This is for the Intel USB and also for the Asmedia USB there true.

#2738

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #2733

> > Zitat von ⇗ daniel_k im Beitrag ¶ #2730

> > The USB controller doesn't work at all or it works but is limited to USB2 speeds?

> Please see my post at ¶ #2587

Missed that.
What is the error code the XHCI controller reports?
Can you export the following registry tree:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
Of a working and a not working instance?
Curiously, the AMD driver doesn't create any specific registry entries. Really odd.

#2739 | daniel_k | ⇗ @diderius6, any of your boards have the ASM2142 controller? Can you please test the new driver v1.16.59.1 that Fernando just posted? ⇗ USB 3.0/3.1 Drivers (original and modded) For me it isn't working, doesn't detect any devices. vmanuelgm says it's working on his system, which has an ASM3142 controller.

#2740

schreiberstein

⇗ @daniel_k
I created a boot media according to your instructions (VL ISO, the second one from the list, I think).
Unfortunately, the installer crashes after loading the Windows NT Kernel. I could clearly see how it loaded all different sorts of USB drivers and also the Intel Storage stuff.
It then crashed with the same bluescreen about The BIOS in this system is not fully ACPI compliant.
0x0000000A5
I will try to start the installer without ACPI support so I have a semi working system to experiment in, if the AHCI driver is correct.
Do you have an idea what might be the issue? I could see that the modified date of the changed files was correct. I dont think I messed it up.
Cheers,
schreiberstein
EDIT:
Booting off the SATA CD drive also does not work after forcing ACPI off using F7. It gives me another bluescreen: the 0x0000007E - it cant find the boot device, I suppose. I guess the pack did not include the correct AHCI driver for my chipset. An ISO I made myself with a certain driver from Fernando worked without issues previously, albeit without ACPI and USB.
I will list what driver I used in a bit.

#2741

diderius6

⇗ @daniel_k
I just install this new Asmedia driver (see pic) on the Asrock board. It has ASM2142 controller.
ASM3142 does not exist really, it is identic to ASM2142.
For me, Asmedia device with this new driver v1.16.59.1 works normal (I installed xhci and HUB driver).
But I remember some versions ago from this driver, that I have the same problems as you now.
Always crash, device not recogniced and so on.
But now not
Dietmar
⇗

#2742 | daniel_k | ⇗ @schreiberstein, strange. I was sure it would work.

#2743

daniel_k

[quote=diderius6|p2741]
ASM3142 does not exist really, it is identic to ASM2142.[/quote]
That's what I always thought, but why is there a device ID PCI\VEN_1B21&DEV_3142 in the INF?
Is there anything pluged in the ASMedia ports? Can't see from your screenshot.
If not, please connect something.

#2744 | schreiberstein | ⇗ @daniel_k I have just checked my previous download folder. The AHCI driver that should work for my Z390 coffee lake system was "Universal Intel RST Drivers+Software Set v11.2.0.1006 mod+signed by Fernando.rar".
#2745 | diderius6 | ⇗ @daniel_k Look on right side E:\SanDisk (is ultrafast USB stick, about 400 MByte/s) and also in Device Manager, last entry "USB-Massenspeichergerät" Dietmar

## Page 184

#2746 | daniel_k | ⇗ @diderius6, thanks! Just wonder why it doesn't work here? O.o
#2747 | daniel_k | ⇗ @schreiberstein, I've attached the drivers from Fernando. Just unpack in the \GRTMPFPP_EN\CD\I386, overwriting existing files. You may delete the following files in the same folder: iaStorA.inf, iaStorA.sys and iaStorF.sys. Rebuild the ISO.

#2748

schreiberstein

⇗ @daniel_k
Alright! Thank you. I will try that out in a moment.
Unfortunately, this probably means that the Longhorn ACPI hack won't work for me, if it already crashes with a BSOD during setup, right?
That means there won't be a resolution for IRQ resource conflicts.
So, I will install using F7 and see if anything changes.
Cheers,
schreiberstein

#2749 | daniel_k | ⇗ @schreiberstein, by the way, it would be nice if you could post the complete ACPI error message, maybe it gives us some clues about where is the problem. ⇗ @diderius6, you've got an eVGA Z390? If so, it works just fine with the modded ACPI 5048, right?

#2750

schreiberstein

> Zitat von ⇗ daniel_k im Beitrag ¶ #2749

> @schreiberstein, by the way, it would be nice if you could post the complete ACPI error message, maybe it gives us some clues about where is the problem.
> @diderius6, you've got an eVGA Z390? If so, it works just fine with the modded ACPI 5048, right?

I attached a photo of the bluescreen.
Cheers,
schreiberstein
schreiberstein has attached images to this post ⇗ IMG_0688.jpeg

#2751

daniel_k

⇗ @schreiberstein, that's a tough one.
Parameter 1 is kind of incompatibility.
Parameter 2 is the pointer to the link node. (This device is missing the _DIS method.)
⇗ https://docs.microsoft.com/en-us/windows...acpi-bios-error
Parameter 1 is 0x10006, which means that ACPI found a link node, but it cannot disable the node. (Link nodes must be disabled to allow for reprogramming.)
⇗ @diderius6, do you have any experience with this?

#2752

schreiberstein

> Zitat von ⇗ daniel_k im Beitrag ¶ #2751

> @schreiberstein, that's a tough one.

⇗ @daniel_k
Oh, jackpot, I guess... :D
Thanks for your initial assessment of the situation.
Burning the CD-RW of the updated ISO right now...
By the way, can I assist by posting any output from a working Windows/Linux system or DSDT dumps?
I think fixing the problem I encounter should allow users of all other Gigabyte AORUS Z390 boards to run XP, since these boards are very similar, as far as I know.
And these boards are quite popular due to their good VRM design.
Cheers,
schreiberstein

#2753

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #2738

> Missed that.
> What is the error code the XHCI controller reports?
> Can you export the following registry tree:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
> Of a working and a not working instance?
> Curiously, the AMD driver doesn't create any specific registry entries. Really odd.

No yellow exclamation mark for the XHCI controller when the USB3 function fails, simply the usb3 ports act as usb2 after a shutdown.
Sorry, but I'm really noob on this: how can I attached the reg files at my post?

#2754 | daniel_k | ⇗ @schreiberstein, actually I can extract the DSDT table from the BIOS on Gigabyte site. At first sight, it seems to be simple: just missing some _DIS methods.

#2755

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #2753

> No yellow exclamation mark for the XHCI controller when the USB3 function fails, simply the usb3 ports act as usb2 after a shutdown.
> Sorry, but I'm really noob on this: how can I attached the reg files at my post?

When replying, below the "text" box, click on Attach file.
A new box will open, then you can browse your computer for the file, then click on Upload. That's all.
It's a good idea to pack both .reg files together instead of sending them one by one uncompressed.

#2756

schreiberstein

⇗ @daniel_k
That's cool! I am using Firmware F6 by the way, but F7 did not change anything except for the microcode, so...
Btw. The new ISO also fails with a 7E error. Sounds like the AHCI driver does not work. I will try with the ISO I previously created using Winfuture xp-Iso-Builder.
Strange. I removed the files you asked me to remove. and pasted in the content of the archive. It mentioned an Intel Driver being loaded.
Maybe I can get USB to work regardless on a finished system for troubleshooting. Could you point me to the latest "installable" package for the appropriate USB drivers? Installable in the sense of manually assigning the inf files in device manager?
Thank you and cheers,
schreiberstein

#2757 | Mikedebian | ⇗ @infuscomus Is there a reason that ocmsn.dll is not present on the CD / System after install? It is required for things like adding and removing windows components. I got it from an external source, but when trying to add things (like Windows Search 4.0) it complained that other files were missing too (a bmp file for example. It was not present anywhere. Can't remember the name of it.)
#2758 | daniel_k | ⇗ @schreiberstein ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (128) AMDXHCI_XP_FINAL.rar
#2759 | Andalu | ⇗ @daniel_k I have already doing so but on preview the file attached seems to be an image file and not a zip file

#2760

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #2759

> @daniel_k
> I have already doing so but on preview the file attached seems to be an image file and not a zip file

Huh?
Just upload it using ⇗ https://www.mediafire.com/

## Page 185

#2761

Andalu

⇗ @daniel_k
Here the registry trees requested.
Andalu has attached files to this post

- ⇗ HKLM.zip

#2762 | infuscomus | ⇗ @Mikedebian the XP source I used already has it removed I'll PM you my XP source

#2763

diderius6

⇗ @daniel_k
"At first sight, it seems to be simple: just missing some _DIS methods."
Exact the same BSOD happens on the z390 Maximus XI Gene board.
But without having possibility to debug this board,
it is a hard job.
I noticed, that compared with the Asus Apex X board,
they changed _Dis method on a lot of devices.
Patch of DSDT table is possible,
but how
Dietmar
PS: Bsod 0xA5 (0x10006) is not solved until now via acpi 5048 on XP SP3.
It happens on nearly all Z390 boards.
EDIT: May be at the end of every device we can put
Method (_DIS, 0, NotSerialized) // _DIS: Disable Device
{
}
in DSDT.

#2764

daniel_k

⇗ @Andalu, there is only one relevant change in the following tree:

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_0480&Pid_a007\20130504008236F\Device Parameters]

    "ExtPropDescSemaphore"=dword:00000001

Which is only present in 2.HKLM post-shutdown (USB2).reg
Try to delete this entry and restart.
If this doesn't help, probably something related to device programming registers, which is something I can't help you with.

#2765

tarsonis

> Zitat von ⇗ diderius6 im Beitrag ¶ #2736

> @tarsonis
> For me, ONLY the STORAHCI driver from ⇗ @skullteria works on AM4 Ryzen board
> Dietmar
> PS: ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (59)
> Integrate via nlite storahci.sys.
> Make storport.sy_
> from it via
> makecab storport.sys
> and put it into installationsfolder i386 from Installations CD.

Great I will try this one. So just the ⇗ @skullteria driver from your link needed and no iaStor.sys, acpi.sys integration in the iso? Thanks for the link!

#2766 | infuscomus | ⇗ @tarsonis acpi.sys is still needed iastor.sys can be removed

#2767

diderius6

⇗ @tarsonis
Modded acpi.sy_ has to be put in i386 folder as before.
No iaStor.sys is needed.
But you have to integrate the STORAHCI driver as txtmode driver via nlite or F6 method
and add by hand storport.sy_ also in i386 folder
Dietmar

#2768

schreiberstein

⇗ @diderius6
Would it be possible to patch the DSDT without modifying the BIOS, as described in this patcher application ?:
⇗ https://msfn.org/board/topic/179059-acpi...r-at-boot-time/
I have no knowledge about ACPI, but if there is something I can test for you on my Z390 machine, I would love to help - as long as I don't have to attach a JTAG device to my bios chip.
It really is a bummer that these bios programmers removed the support for older ACPI versions. It does not really make sense to me.
Cheers,
schreiberstein

#2769

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #2764

> @Andalu, there is only one relevant change in the following tree:
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_0480&Pid_a007\20130504008236F\Device Parameters]
> "ExtPropDescSemaphore"=dword:00000001
> Which is only present in 2.HKLM post-shutdown (USB2).reg
> Try to delete this entry and restart.
> If this doesn't help, probably something related to device programming registers, which is something I can't help you with.

That entry is re-created after each restart. I'll try tomorrow a way to block it.
Thanks for your time ;)

#2770

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #2769

> That entry is re-created after each restart. I'll try tomorrow a way to block it.
> Thanks for your time ;)

You're welcome.
Question is: Does it make a difference?

#2771 | daniel_k | ⇗ @schreiberstein, please try this. Found the _DIS check which causes the BSOD. Now we need to know what happens later. Just unpack in the \GRTMPFPP_EN\CD\I386, overwriting existing file.
#2772 | diderius6 | ⇗ @daniel_k Do you jmp over 0x10006 Bsod? I tried this also, but does not help Dietmar

#2773

daniel_k

> Zitat von ⇗ diderius6 im Beitrag ¶ #2763

> Bsod 0xA5 (0x10006) is not solved until now via acpi 5048 on XP SP3.
> It happens on nearly all Z390 boards.
> EDIT: May be at the end of every device we can put

>     Method (_DIS, 0, NotSerialized) // _DIS: Disable Device
>     {
>     }

> in DSDT.

Actually, we just need to add that Method to Device (LNKA) to Device (LNKH), which are all have hardware ID PNP0C0F.
Just saw that ACPI.SYS specifically checks all devices with PNP0C0F for a _DIS method.
EDIT: Nevermind them.

#2774

daniel_k

> Zitat von ⇗ diderius6 im Beitrag ¶ #2772

> @daniel_k
> Do you jmp over 0x10006 Bsod?
> I tried this also, but does not help
> Dietmar

What happens then?
⇗ @schreiberstein, please try it anyway, maybe the behavior is different.

#2775

schreiberstein

⇗ @daniel_k
Should I do a quick attempt of what you suggested to see if the 0xA5 BSOD changes to a 0x7E due to the missing AHCI driver? (Thus indicating ACPI works, just no boot media can be found - which I can fix sometime later tomorrow.)
Or should I go to bed and try it tomorrow? :D
Cheers,
schreiberstein

## Page 186

#2776 | daniel_k | ⇗ @schreiberstein, make a quick try.

#2777

diderius6

⇗ @daniel_k
Then happens famous BSOD 0x7E (0xC0000005,..)
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (169)
and from this place I think we need Windbg.
Now all the z390 boards can be debugged via lancard (I use Realtek in Pcie slot) because of nice work for lan debug from ⇗ @Mov AX, 0xDEAD
Dietmar

#2778 | schreiberstein | ⇗ @daniel_k Burning the disc right now... will keep you posted. It's strange that the txtsetup takes soooo long to load on these modern boards with all their bells and whistles. My Athlon 64 939 rushes through it like a starving rat. Cheers, schreiberstein
#2779 | daniel_k | ⇗ @diderius6, can't you try to patch the DSDT? That'd be easier, provided that you can easily flash the BIOS with your tools. Under certain cases I don't think we can simply hack away ACPI.SYS.

#2780

diderius6

⇗ @daniel_k
Of course I can try to patch DSDT. I think with good chances. With lan Windbg you can found the exact place of BSOD.
But I do not have this board. And for other people it is a big risk to flash a faulty DSDT,
even the Gene XI has a Biosflashback port
Dietmar

#2781 | daniel_k | ⇗ @diderius6 I thought you had one Z390 board. Ever thought of getting one?

#2782

diderius6

⇗ @daniel_k
I have the EVGA z390 Dark board. EVGA speaks with people from Asus and they make just as a hobby a Bios,
that works to full with normal XP SP3 and XP 64bit, even with USB3 from scratch.
I compare those 2 Bios for normal and for XP. At once I see, that the _DIS method is treated complete other
and this is also true for Asus Apex X (I patch DSDT, works) and Asus Apex XI, until now no XP Bios
and overclocker worry at hardwarebot a lot about it
Dietmar

#2783 | schreiberstein | Gosh. The disc failed on me. Trying a new one. This was a brand new Verbatim CD-RW. schreiberstein has attached images to this post ⇗ Screen Shot 2019-10-09 at
#2784 | daniel_k | ⇗ @diderius6, forgot about it. EVGA z390 Dark, that's the one that have XP friendly BIOS.
#2785 | daniel_k | ⇗ @schreiberstein, you're in Germany, right? Do it tomorrow, man! It's too late.
#2786 | diderius6 | ⇗ @daniel_k Nono, this EVGA Bios for XP is the key for to understand, what went wrong with _DIS in its normal Bios Dietmar

#2787

daniel_k

⇗ @diderius6, just saw what they did.
Basically, the code of all Device (LNK?) is exactly the same as from Z370 boards.
And they readded this:

        Scope (_SB)
           {
            OperationRegion (ITSS, SystemMemory, 0xFDC43100, 0x0208)
            Field (ITSS, ByteAcc, NoLock, Preserve)
                   {
                PARC,   8,
                PBRC,   8,
                PCRC,   8,
                PDRC,   8,
                PERC,   8,
                PFRC,   8,
                PGRC,   8,
                PHRC,   8,
                Offset (0x200),
                    ,   1,
                    ,   1,
                SCGE,   1
                   }
           }

Piece of cake!

#2788 | daniel_k | ⇗ @schreiberstein, try to learn how to use Mov AX, 0xDEAD's ACPI Patcher, which you've linked previously: ⇗ https://msfn.org/board/topic/179059-acpi...r-at-boot-time/ This way we can help you to test a patched DSDT table.

#2789

schreiberstein

⇗ @daniel_k
Just like Dietmar predicted.
0x7E acpi.sys
I can get familiar with the patcher soon.
Good night,
schreiberstein
schreiberstein has attached images to this post ⇗ 0796B5B1-C15B-4459-8BCB-0

#2790 | daniel_k | ⇗ @schreiberstein Good night! I'm sure we will fix it easily.

## Page 187

#2791

diderius6

⇗ @daniel_k
I think,
the most important part is this in XP DSDT, which is missed 8 times at nonXP DSDT
for Device (LNKA) Device (LNKB) Device (LNKC) Device (LNKD) Device (LNKE) Device (LNKF) Device (LNKG) Device (LNKH)
here as example for Device (LNKA)
Method (_DIS, 0, Serialized) // _DIS: Disable Device
{
PARC |= 0x80
}
Method (_PRS, 0, Serialized) // _PRS: Possible Resource Settings
{
Return (PRSA) /* \_SB_.PRSA */
}
Dietmar
PS: This is from XP friendly Bios 92 of the EVGA DARK z390 board. It is missed in XP unfriendly Bios.

#2792

diderius6

⇗ @daniel_k ⇗ @schreiberstein
I make a new DSDT and flash this into Bios Z390DESI.F7
from original Biosversion F7 from Gigabyte Website
⇗ https://www.gigabyte.com/de/Motherboard/...support-dl-bios
I think, it will not destroy anything to 99% and works for XP. But 1% risk is left.
Dietmar
Download
⇗ https://ufile.io/iwoysdfd
EDIT: If this still gives BSOD A5 (0x10006), we have the possibility to copy in DSDT the whole device
Device (LNKA)
Device (LNKB)
Device (LNKC)
Device (LNKD)
Device (LNKE)
Device (LNKF)
Device (LNKG)
Device (LNKH)
from a Gigabyte z370 gaming 3 DSDT to the gigabyte z390 designare DSDT.
diderius6 has attached files to this post

- ⇗ DSDT.rar

#2793

schreiberstein

⇗ @diderius6
Moin Dietmar,
I will look into the Mov AX, 0xDEAD's ACPI Patcher method first before flashing the BIOS, so thanks a lot for providing the DSDT file as a standalone version. That's really cool.
Right now, I am not familiar with how reliably Gigabyte's dual bios technology works and how easy a recovery would be. I also do not possess a JTAG device or whatever is needed to unflash a bricked BIOS.
I first need to look into how I would in case something goes wrong, before I actually attempt it.
Please understand. :-)
Have a nice day,
schreiberstein

#2794

diderius6

⇗ @schreiberstein
Of course I understand you.
I broke 2 boards with modded Bios, takes me months to make them alive again.
"how reliably Gigabyte's dual bios technology works"
I think, only when the possibility is given, to copy Bios back, this will work.
I "succeed" on Asus Apex board to brake Biosflashback(!)
Dietmar

#2795

diderius6

⇗ @Doc.Brown
To flash Bios is always a risk!
I make also a Bios based on Version 57 for the ROG MAXIMUS XI GENE board.
Flash it via Biosflashback on the gene XI board.
The risk of broken Bios in compi is because of Biosflashback <1%.
The chance, that it works for XP is about 70%, because this solved only BSOD A5 (0x10006)
Dietmar
⇗ https://ufile.io/75zrsuuo
diderius6 has attached files to this post

- ⇗ DSDTgeneXIBios57.rar

#2796 | jonny | ⇗ @diderius6 thanks for your help, pls can you tell me a way to integrate acpi.sy_ correctly into windows xp cd? because i saw that acpi.sys from windows longhorn build 5048 have dependencies with the file that gave me ERROR 14, so if you can help me how to integrate the acpi.sys in a better way pls let me know, (i used CABPACK 1.4 to integrate acpi.sys, then i named the file acpi.sy_) and i installed xp into usb not cd, sorry i typed wrong, have a good day

#2797

diderius6

⇗ @jonny
At commandline type for the modded acpi.sys (path to its folder)
(path to its folder) makecab acpi.sys
This gives you acpi.sy_
This acpi.sy_ you copy to your installationsfolder i386 and burn CD
To change *.cab can be done after installing XP or even never^^^.
Dietmar
PS: Be sure, to have the needed AHCI driver integrated via txtmode driver in nlite.

#2798 | XPWELL64 | ⇗ @diderius6 I bricked my mobo because I integrated your DSDT wrongly.
#2799 | diderius6 | ⇗ @XPWELL64 I cant remember, that I make a Bios for you Dietmar
#2800 | XPWELL64 | ⇗ @diderius6 1- Download my 603 Version of Asus X555LB bios. 2- After extracting things of my bios, please integrate your dsdt.aml into my bios. 3- I will check my bios and injected dsdt.aml by Uefitool.
#2801 | diderius6 | XPWELL64 I remember Asus X555LB notebook. There I solved all 24 unfullfilled dependencies in DSDT Dietmar PS: I still do not know, what you want to change in that Bios.
#2802 | XPWELL64 | ⇗ @diderius6 I want to inject dsdt.aml into bios.
#2803 | diderius6 | ⇗ @XPWELL64 This I understand. But what should be changed in that DSDT Dietmar PS: I have already done with post ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (125)
#2804 | XPWELL64 | ⇗ @diderius6 Nothing.
#2805 | diderius6 | ⇗ @XPWELL64 The problem with long integers 64bit as for example PDBM=0xFFFFFFFFFFFFFFF9 is gone with the last acpi.sys 5048 mod Dietmar

## Page 188

#2806 | XPWELL64 | Problem solved, I will buy sandy bridge desktop.
#2807 | diderius6 | ⇗ @XPWELL64 Witch problem? Dietmar PS: Laptop Asus x555lb seems to stay alive ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (175)

#2808

XPLives

⇗ @schreiberstein

> Zitat von ⇗ schreiberstein im Beitrag ¶ #2726

> @XPLives
> Hello XPLives,
> Thank you!
> Everything that could be said about my Hackintosh setup can be found in an extraordinary, detailed guide made by an extremely helpful individual over at TonyMacx86:
> ⇗ https://www.tonymacx86.com/threads/succe...-rx-580.267551/
> It is a Z390 system from late 2018 by the way. The parts have been selected to work with macOS Mojave.
> I have quite a lot of hackintosh experience (intermediate level, I'd say), but proceeded to use real Macs for years since there were always some quirks involved. And simply because my iMac did all I needed, until it didn't.
> This is very different from hackintoshing in the early 2010s. A lot more sophisticated. It is an insane amount of work what people put into patching and modding.
> This build works 100%. Never crashed once. No kernel panics. 100% stability. 100% sleep capabilities. 100% wifi, bluetooth, usb3, onboard audio, ThunderBolt 3, iMessage, FileVault boot volume encryption (YES!) etc.
> I was initially hesitant to shill out this amount of money on a new system and said to myself "send it back within 14 days if you cannot get it working perfectly"...
> What can I say... I built it one Friday night in January, installed Windows and completed my entire macOS installation with everything working by Sunday evening. It pretty much works like a real Mac.
> However, there were some things I needed to fix manually to get FileVault encryption working. But the guide is pretty complete. I am uttermost satisfied with this build.
> It is insane how well it works.
> ⇗ https://www.tonymacx86.com/threads/assor...ckintosh.11234/
> I built several Hackintoshes over the years (some homeservers, some virtual machines (Linux KVM with PCI-e passthrough and custom patchy kernels back in 2013, very tricky, lovely memories)). My first hackintosh build was in January 2011 (I was 15 at that time) - a Gigabyte GA-H55M-UD2H. It was a huge and cheap upgrade to my MacMini of that time, but the board was very unstable. Even on Windows. Sudden reboots, regardless of RAM or PSU. I then used an iMac 2011 from 2013 onwards. I then switched to a MacBook Pro 2013 in 2018 but really disliked the experience.
> I now run this Hackintosh machine with two Apple Cinema HD 30" 16:10 displays connected and a "retro" Apple Extended Keyboard II from the early 1990s. It feels better than any Mac I have ever used in my life. The i9 really is a beast.
> My intention was to build a system I would use for the next 5 years that would be Mojave (32 Bit + iTunes intact) compatible and that was somewhat overpowered, yet quiet.
> I doubt Tiger would work. It already crashed in a virtual machine on everything higher or equal to Haswell. Something about the CPU. Maybe Snow Leopard. I have way to many "vintage" Macs to justify attempting such a project, lol.
> The audio drivers for Windows 10 were : ⇗ http://danielkawakami.blogspot.com/2015/...rt-pack-61.html
> There are also drivers for OS X, but mine did not survive sleep and wake. The audio stopped working afterwards. Sleep (ACPI S3, not my body lol) is very important for me. I barely ever turn off my computer.
> But there are folks working on that over at the insanelymac forum, if I remember correctly. The kX Audio Driver is open source, after all.
> A regular Audigy 2 ZS costs ~20 on German eBay these days. I originally bought it for my Windows 98 Athlon 64 rig, but its FireWire port steals the desired IRQ5 that I can assign in the BIOS. The Live! is better in that regard.
> I recently purchased a used EVGA nVidia Geforce GTX 780 (non TI for compatiblity) which should work in both Windows XP and Mac OS X (it is the last supported nVidia GPU generation that is natively supported without "webdrivers" for OS X, which currently are not available for Mojave, as discussed on MacRumors) - However, the Radeon RX 580 feels much smoother on Mac OS X.
> The 780 GTX still supports analog VGA out via DVI (for my Sony Trinitron CRT), which the Radeon does not support.
> But since this is an ATX board, I could drive both cards. Incompatible GPUs can be made invisible via DSDT patches (also mentioned in the TonyMac guide), as they otherwise mess with sleep. The Geforce 780 wouldn't cause any issues though.
> Getting the Hackintosh working will be much easier than XP, given that nearly all of the hardware is incompatible.
> I suppose all will be fine if I get ACPI and thus IRQ management working on XP. If you don't mind dozens of add-in cards, I guess you can get nearly any system working.
> I do not know why, but I really have an obsession with getting old stuff working on new systems.
> --> My installation froze because of "not fully ACPI compliant" - 0x000000A5 . The typical issue discussed on here. Without ACPI, everything went smoothly and the system was stable, but nearly unusable due to severe IRQ conflicts.
> Drivers for my Renesas USB3 PCI-E card would not work either. Probably due to the lack of "resources".
> It would be really NICE to just get Windows 98 or ME to boot. ME actually went further in the installation. I was able to install it, but it then crashed during the first restart, even after I patched the memory and all that jazz.
> No, I do not have any other software from RLOEW. But I purchased both AHCI and Memory patch. Partly because I wanted to support and compliment him for his work. I did not really expect it to work on Z390.
> If you have any idea how to work around this issue, I would be very happy to hear about it. I doubt anyone would be able to get universal USB drivers working though. Well... I guess people need some challenges for the 2020s, haha!
> If you have any questions regarding your Hackintosh project or about this build, feel free to send me a private message.
> Cheers,
> schreiberstein

Schreiberstein,
Does your username mean something in German?
For the moment I probably have the most advanced setup at least for XP and Server 2003. I own the i9-9900K and preordered mine and probably the only one to have attempted installing over 64GB memory in XP and Server 2003 for both 32-Bit and 64-Bit testing. I'm using a Z370 that is fully compatible with the i9 Coffee Lake octacore so it is possible whatever I can do can be done the same on the Z390 since the chipsets are nearly identical similar to how the Z68 and Z77 were. The only major changes I believe is just the CPU microcode support for 9th Gen out of the box as the socket remained the same. The Z390 was just a rush job as they were supposed to release a Z470 chipset that supported the 10nm Cannon Lake which now has been delayed or altered so Ice Lake is now the next desktop replacement. This is disappointing as I've read Ice Lake will use a different CPU socket so a new motherboard will have to be purchased. So that is the reason why I am waiting for final news on which Intel Chipset will finally have true DDR5 and PCIe 5.0 support before upgrading again. Worst case is Z470 is still 14nm and 10 core max or capped to 128GB max memory with DDR4 and PCIe 4.0. Best case is Z470 uses the same socket as Z370/Z390 and we get a Z470/Z570 CPU backward compatibility extension with just a BIOS microcode update with the possibility of 10nm CPUs that run cooler so it will work on Z370 since it's doubtful Intel can hit 16 Core / 32 Thread CPUs until 7nm Sapphire Rapids.
Now I typically switch to my cheaper hexacore for most of my experimental OS testing in case I fry it I'm not out a lot of $$$ money. But any testing that works on it should apply to the i9-9900K.
The XP ACPI issues have existed starting with SkyLake 100 Series so without BIOS modding or using a modded ACPI.SYS it is unlikely you can use the system with full ACPI functionality which is why you are getting the infamous BSOD A5 Error.
So without BIOS modding which I also don't want to do either the best method would be either a modded ACPI.sys replacement or choosing to install XP without ACPI. So far in my Z370 any modded ACPI.sys testing the graphics card is missing including the integrated Intel GPU in the Device Manager so if you depend on graphics you may have to be the guinea pig and test out other people's modded ACPI.SYS and hope you hit a winner like the lotto. So unless this is resolved only the NO ACPI install method with MPS Mode on Intel CPUs are the only easy way to get XP working without ACPI or BIOS modding.
The good thing is XP will still work but you are correct since there are less IRQs available you may run into resource issues. I think there is another way to get around this and avoid using all ACPI features by modifying the ACPI.sys to act closer to MPS mode. Without knowing what exactly is being modified in the ACPI.SYS I can't really assist other people and fix it and release my own modded ACPI.SYS for testing. Since no one has taken the time and written any kind of ACPI.SYS modding guide yet on exactly what they are modifying or altering when they release a modded ACPI.SYS for people to guinea pig test it's anyones guess if there can be a universal ACPI.SYS fix for all systems.
But I think the key is partially in converting the ACPI.SYS to be less ACPI friendly and function more in MPS mode so you still get the extra IRQs but no Standy By Mode. You can simulate power efficiency by changing your BIOS CPU Core Ratio down to a fixed number like 8. 800 MHz is the lowest you can go today. I actually hate how the CPU MHz gets throttled as the CPU Voltage isn't constant. By setting a fixed CPU Core Ratio and CPU Core Voltage you can get better efficiency and lower temps. If someone can push it down to 400 MHz -> 66 MHz that would be amazing to see how much lower the CPU Core Voltage can reach. As long as you can Shutdown and Restart the computer I think that would be fine for most people. If the system is running 24/7 this is the perfect universal modded ACPI.SYS. As for Hyperthreading that is something I don't know if it's possible to still function with ACPI disabled because in MPS Mode there is no hyperthreading. If a modified ACPI.SYS can have hyperthreading, all IRQs available, but just no Standy By or Power Saving Modes then this will be the best modded universal ACPI.sys to create combined with my BIOS settings.
The only other way is BIOS modding and simulating only Ivy Bridge ACPI functions and removing all newer ones. If this were possible then maybe you could make a Coffee Lake BIOS operate the same as Ivy Bridge except add newer CPU microcode support. Most of newer lower power features are probably what is causing the ACPI errors. I don't know enough if it's possible to use an Ivy Bridge BIOS template and port it to Coffee Lake BIOS. Only thing is you would have to remove the entire Intel GPU sections as XP drivers won't work on the newer iGPU and I think the iGPU memory sharing is partly responsible for the DOS incompatibility with Himem.sys. Personally I'd just clean out all the iGPU code entirely so it isn't detected or see if the Ivy Bridge iGPU code could work on the Intel Coffee Lake iGPU. I'd be curious if that's all that is preventing the XP drivers from working on newer iGPUs.
I usually don't do too many help responses due to my own limited time but I think yours is the first XP Hackintosh request so I think it may end up being useful for many people. I've been to TonyMacx86 long ago. But at that time it was more of a curiousity and I didn't really need to use a MAC. Every time I used a real one it felt like it wasn't working the way it should. Even internet browsing on one was a bit awkward. But I do have a friend who only uses Macs and another who uses one for Video Editing. So the fact that Intel based Macs are still in production gives Intel another reason to choose them over AMD if you wanted to build a Hackintosh.
I'm not aware of any other members here who are Mac users or they would have chimed in by now. But I think for the moment I might the only one closest to devote my time to try and see if it could happen. So as long as we can help each other out it might be possible.
As for your Hackintosh portion I think if you can create a thread titled "Schreiberstein XP Hackintosh Project" in the Windows XP/2000/Server 2003 Subforum to post your responses regarding it there.
It would be easier to find your messages. As for the ACPI assistance you can keep posting in this thread you are using now and keep guinea pig test till you hit the jackpot.
At one point I was going to build a Hackintosh based on Sandy Bridge and the HD Graphics 3000 back in 2011. Never got around to do it. Maybe half a year ago I almost bought a used Mac Mini for a possible Macintosh XP testing which I assumed would be much easier to do. I have quite a few Macs mainly OS 8-9 era. I think one of the newer ones is a G3 or G4 hand me down that I think has 10.1 or something on it. Never tried it. I'm not sure if it could run Snow Leopard.
Your experience with Hackintosh will be useful to determine if XP can coexist with Mac OS X on the Coffee Lake system. Some questions that need answering that may help determine this.
If you placed that Mojave OS Coffee Lake setup drive you have working now into your older Hackintosh H55 Gigabyte Motherboard and moved the GTX 780 Graphics card over to it does it work without any issues?
Does Mac OS Mojave allow installing onto a FAT32 partition? If not what's the last MAC OS X version to allow installation to a FAT32 partition?
Which earliest MAC OS version started supporting full read/write on NTFS partitions?
Is it possible to boot to different MAC OS X versions each on their own partition?
Does Apple include such a Multi OS bootloader when upgrading to a newer version so you can run your older version in case the new installation fails?
For example Windows allows Windows 2000, XP, and 2003 to coexist in the bootloader and can be chosen instead of stuck on the newest OS.
Does any MAC OS X version you know of allow installing from scratch with ACPI support completely disabled regardless if the BIOS is ACPI compliant?
As for the oldest MAC OS X version that can be installed on your Z390 i9-9900K system can you take some time to test verify if you can get Snow Leopard 10.6 installed on your i9-9900K setup using your current configuration? I have a genuine copy here in case it works you might be able to guide me enough to get it working. Then I might be able to do some sort of hybrid XP / Snow Leopard setup testing that could be a framework used for newer MAC OS testing for Mojave. I have quite a few network cards and USB cards that say they will work with 10.6 so they hopefully are forward compatible with Mojave. I also prefer the older MAC OS versions because they are usually smaller and more compact like XP.
I've collected a lot of hardware, sound cards, video cards, USB cards and I might be able to test both XP and MAC OS X to find the hardware that works natively works in both operating systems to simplify future Hackintosh XP hybrid projects.
Am I correct you are trying to create an XP / Mac OS X setup and not just a stand alone XP system?
What are you planning to use XP for?
Since you confirmed the GTX 780 seems to work natively in Mojave do you have a GT 710 or GTX 750 graphics card to test if these are also compatible? The GT 710 has VGA, DVI, and HDMI full size connectors so is very handy for multi monitor testing without video adapters. I use the VGA port for video output. You can use USB for Audio since it may have native drivers for MAC OS making it much easier to install.
Also what is the last 32-Bit MAC OS X version that can be made to work on a Hackintosh?
The best USB 3.0 PCIe card is still up for debate. I found there is a bug on NEC cards which after the driver is installed it will function but once rebooted it will not and only a driver reinstallation with fix it. So this seems to be the only issue with NEC cards on newer chipsets. VIA seems to work better in all my testing and is cheaper to purchase thanks to eBay.
I got Windows 98SE to work on my Z370 but I used a previous install from a P4 and just moved the SSD over and it was much easier to get working. I haven't tried a direct installation on the Z370 from scratch which may fail because too many changes that not even RLoew patches can solve. My guess is the patches might work only post install.
Universal USB 4.0 drivers could be a possibility in the future. It's unclear if there is sufficient interest and financial backing that I could reach out to a company to help develop them. But a better future solution is using USB 4.0 PCIe cards with proper financial backing to get the OS drivers done that way you could insert them into any motherboard to be used instantly. Even 98SE could get some love if driver support is included since USB 3.0 legacy driver support was entirely skipped all the way to XP. Without any kind of interest and financial backing most likely the USB 4.0 cards are going to only support Windows 7 as the oldest or just Windows 8.X/10 only. You have to remember Windows 7 support pretty much is ending in 2020 for most people. So the likelihood of USB 4.0 Windows 7 drivers for Intel or AMD ports is pretty low. Intel USB 3.0 was already out in 2012 well within XP's extended support time frame before 2014. Windows 7 is nearing its end of it so Intel will not bother that I'm 100% certain.

#2809

XPLives

⇗ @XPWELL64

> Zitat von ⇗ XPWELL64 im Beitrag ¶ #2798

> @diderius6
> I bricked my mobo because I integrated your DSDT wrongly.

Oh you were XPLAKE8175? Did you delete the account because the notebook got bricked after flashing?
Is there some way to flash the notebook BIOS back to life using manufacturer BIOS?
Maybe someone here knows how to do this resurrection. I hate soldered BIOS chips so I don't mess with laptop flashing unless official release and required for some new feature or CPU support.
As for Desktop, you can choose Ivy Bridge for final XP version. Some Sandy Bridge have Asmedia USB 3.0 ports so could be better choice. If for XP only and not Vista OS, then you can try Haswell/Broadwell works even better. Maybe even X99 is the best chipset without modding anything in BIOS.
SkyLake+ prepare for headaches.
But for notebooks the best is Ivy Bridge and nothing newer or no XP Intel graphics driver for iGPU.

#2810

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #2795

> @Doc.Brown
> To flash Bios is always a risk!
> I make also a Bios based on Version 57 for the ROG MAXIMUS XI GENE board.
> Flash it via Biosflashback on the gene XI board.
> The risk of broken Bios in compi is because of Biosflashback <1%.
> The chance, that it works for XP is about 70%, because this solved only BSOD A5 (0x10006)
> Dietmar
> ⇗ https://ufile.io/75zrsuuo

Thank you ⇗ @diderius6 :)
I'll try this friday and also another Xp iso build because by reading last messages here I think I make big error with ACPI and Storport integration,I simply renamed them with .SY_ not used makecab :( Is it a big mistake ?
Also I don't know what to do / how to use the DSDT that you share with M11g modded bios ...

#2811 | Mikedebian | This happens in Vbox, even fully emulated without extensions ⇗

#2812

diderius6

⇗ @Doc.Brown
Just put this Bios on Fat32 formatted USB stick,
connect this stick to Biosflashbackport
and flash Bios.
Nothing bad will happen,
Dietmar

#2813

Doc.Brown

⇗ @diderius6
Don't worry I will,I do extreme things with hardware for overclocking with LN2,dead hardware doesn't fear me since a long time now :D
Just tell me if it's necessary to use makecab cmd with files before integrate them in XP or rename them by changing extension work well to please ?
Thanks.

#2814 | diderius6 | ⇗ @Doc.Brown Better think before than after^^. About files: I think, you can even put them into i386 with full name, but I never tested this, Dietmar
#2815 | Doc.Brown | So true xD Anyway I will try to use this makecab function to be sure to do it right and hope it will work now :finger crossed: Thanks for your help :)
#2816 | Mikedebian | ⇗ @infuscomus I am sorry for to have bothered you. I needed to completely remove VBOX and all leftover files before reinstalling it, and now no blue screen.
#2817 | Andalu | ⇗ @daniel_k the registry key you have identified (ExtPropDescSemaphore) maybe can be the cause for the USB3 function not working on my asrock B75 Pro3-M. The same key related to the same external hard disk appears also in my other system where the USB3 does not work while it is not present where the usb3 works fine (asrock B250M Pro4). I don't think it can be just a coincidence but how to verify it? It's very difficult to prevent this registry key from being created every time the external hard drive is connected to computer.

#2818

tarsonis

> Zitat von ⇗ diderius6 im Beitrag ¶ #2767

> @tarsonis
> Modded acpi.sy_ has to be put in i386 folder as before.
> No iaStor.sys is needed.
> But you have to integrate the STORAHCI driver as txtmode driver via nlite or F6 method
> and add by hand storport.sy_ also in i386 folder
> Dietmar

Puh, I seem to make something wrong creating the nLite iso because I still get the 7B error. With and without selecting the ACPI Multiprocessor typ while setup is loading. Seems to not make a difference here.
Maybe there is mistake. Here are the steps I made.
nlite folder for XP files (untouched XP 32bit SP3)
options -> select driver and bootable iso
select single driver -> storahci.inf
select single driver -> amdhub30.inf
let nlite finalize the setup files
copy(overwrite) ACPI.SY_ I made with cabpck14 into i386 of the nlite working folder
copy(overwrite) storport.sy_ I made with cabpck14 into i386 of the nlite working folder
burn the CD in default settings
I took the storport.sys from the link package, compressed it with cabpack.exe default settings and renamed it afterwards. Is it correct or do the cabpack settings need to be changed?
tarsonis has attached images to this post ⇗ cabpack.JPG

#2819

schreiberstein

⇗ @Mov AX, 0xDEAD
My situation :
I do not have a working XP system to use your ACPI patcher ntldr replacement with.
I have a working DOS system that I would like to use to execute the patch program manually (a.exe),
then attempt to start the installation from the same drive by having the Windows XP i386 folder stored there and then executing the installer via winnt32.exe. I just want to see if the ACPI-related bluescreen goes away, not necessarily install from there.
However, after inspecting your sourcecode, I was unable tell for sure where to place the DSDT related files.
Where does a.exe look for them?
Or is there some other magic involved that stores this information in the RAM temporarily and a.exe reads them from there?
It would be convenient if I could just put them into the same directory as a.exe and execute it.
I am using TerraByte Unlimited's BootIt Bare Metal bootloader to switch between multiple primary partitions.
I could conveniently make it execute the a.exe DOS program and then proceed to load my real Windows OS, without having to change its boot environment.
By the way, it's a pretty terrific idea that you've come up with and how you bootstrap your application using ramdisks, 7zip, etc.
Very impressive.
Would be thankful for an advice.
Cheers,
schreiberstein
EDIT: I had another look at that massive C file. (Wow, where did you learn that?!) It seems that what I would like to achieve should already be possible, as long as the "acpi_pat.cfg" file is in the same directory as the executable file. I will try to compile an adapted version of this binary where the GRUB stuff is commented out and it exits back to the DOS prompt, without having to press shift.

#2820

diderius6

⇗ @tarsonis
Most easy is to use from commandline
makecab acpi.sys
this gives you acpi.sy_
This you put to i386 folder for nlite to make CD XP SP3.
The same for storport.sys.
Then you integrate Txtmode via nlite driver STORAHCI from ⇗ @skullteria .
No need to integrate USB files if you have a PS/2 connector
Dietmar

## Page 189

#2821 | Mikedebian | ⇗ @diderius6 ⇗ @infuscomus Is it important that the AMD GPIO driver works in device manager and is not yellow checkmarked?

#2822

infuscomus

> Zitat von ⇗ Mikedebian im Beitrag ¶ #2816

> @infuscomus I am sorry for to have bothered you. I needed to completely remove VBOX and all leftover files before reinstalling it, and now no blue screen.

no worries, glad to hear you got rid of the blue screen.
edit: I'm not sure what the GPIO is used for, so I can't say for sure.

#2823 | Mikedebian | Anyway I just want to thank you guys for making this possible! It really is unreal! I can only hope that one day win9x will be possible too!

#2824

infuscomus

⇗ @Mikedebian
It is already possible to get win9x working on newer systems - i have confirmed it works for AMD Ryzen.
RAM issues can be limited to 1GB or patched to 4GB.
AHCI can be disabled (if supported by BIOS), patched, or ignored (if you are willing to put up with slower MS-DOS compatibility mode)
USB 2.0 drivers for win9x exist.
ACPI is not as important for win9x as it does not support more than 1 CPU anyway.

#2825 | Mikedebian | Yes I've had it running as well, although no support for my PCI devices even if supported under win98. It is like the device manager is unable to locate, see and use any hardware. That's the issue I have with win98, it is with chipset.
#2826 | infuscomus | ⇗ @Mikedebian I had this issue, I had to disable ACPI during windows 98 setup to get hardware detecting properly. setup /p i disables ACPI if i recall correctly I think i used setup /im /is /p i
#2827 | Mikedebian | Will this carry on over on install? Because It was same issue after install
#2828 | infuscomus | ⇗ @Mikedebian yeah it should carry over, it did for me.
#2829 | Mikedebian | Cool. I shall have to try. I wish the windows XP Vesa driver was carried over too. On windows XP I get 1440p with Vesa driver , but windows 9x with vbe9x doesn't work for me on my Vega 56.

#2830

daniel_k

> Zitat von ⇗ diderius6 im Beitrag ¶ #2745

> @daniel_k
> Look on right side E:\SanDisk (is ultrafast USB stick, about 400 MByte/s)
> and also in Device Manager, last entry "USB-Massenspeichergerät"
> Dietmar

Hi Dietmar,
the issue doesn't affect USB 3.0 devices.
My USB 3.0 portable hard disk works just fine, but keyboard/mouse and USB 2.0 stick don't.
When you have some time, please try one of those devices with the ASMedia ports.

#2831

diderius6

⇗ @daniel_k
Yeppp, you are right. All USB3 devices work, all USB2 devices work not. Mouse works not, brrr..
What a debakel again with drivers from Asmedia!
The 59 version xhci driver does not work for XP.
The 59 Hub driver, mixed with 55 vers xhci works
Dietmar

#2832

IntiMD

⇗ @diderius6
Just wondering about the storport.sys, wouldn't the problem with XP setup not copying it disappear had we added relevant lines in TXTSETUP.SIF and LAYOUT.INF? (not sure if it's obvious for you or if you had done that already)? For example we can do a quick edit and copypaste from the scsiport.sys line (example taken from homebrew XP Integral Edition ISO) :
(TXTSETUP.SIF)

    scsiport.sys = 100,,,,,,4_,4,0,0,,1,4

(LAYOUT.INF)

    scsiport.sys = 100,,96384,,,,4_,4,0,0,,1,4

and when we make a quick addition based on those lines above for x86 storport.sys from KB943545 hotfix (5.2.3790.4173)
(TXTSETUP.SIF)

    storport.sys = 100,,,,,,4_,4,0,0,,1,4

(LAYOUT.INF)

    storport.sys = 100,,108032,,,,4_,4,0,0,,1,4

Of course if this won't work you can tinker with the number codes according to the reference here: ⇗ https://msfn.org/board/topic/127677-txts...&comment=820892

#2833 | XPWELL64 | ⇗ @diderius6 I integrated your dsdt into my bios by UEFItool and now it cannot receive aml information. It BSODs. (Windows 10 BSoDs too)
#2834 | diderius6 | ⇗ @IntiMD See post ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (190) Dietmar

#2835

diderius6

⇗ @XPWELL64
I do not understand your answer.
From post from 6 October 2019
"⇗ @diderius6
I benchmarked HL1 with anapa driver on my asus x555lb in windows xp and results are more terrible than windows 95 preinstalled pc.
I will mod this igxpmp32.sys with ida pro can you tell me how to do it? My DEVID is: DEV_1616"
your Asus notebook seems to work.
And if only some strange thing happen,
flash new with website Bios
Dietmar

## Page 190

#2836

daniel_k

⇗ @IntiMD
Just add this to TXTSETUP.SIF, under storprop.dll

    storport.sys = 1,,,,,,3_,4,0,0,,1,4

This must also be present in DOSNET.INF, in section [FloppyFiles.x] (where x can be 1, 2 or 3) and in section [Files].

    d1,storport.sys

No more files need to be edited.
Got this from Server 2003 and it definitively works.

#2837 | Mov AX, 0xDEAD | Another Update: - Kernel debug with WinDBG/KD over LAN/USB3.0 connection solved, (⇗ https://github.com/MovAX0xDEAD/KDNET) ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (12) Intel onboard usb3.0 H110 - OK VIA External pci-e usb3.0 card - No

#2838

Mov AX, 0xDEAD

⇗ @schreiberstein

> Zitat

> Where does a.exe look for them?
> Or is there some other magic involved that stores this information in the RAM temporarily and a.exe reads them from there?
> It would be convenient if I could just put them into the same directory as a.exe and execute it.
> EDIT: I had another look at that massive C file. (Wow, where did you learn that?!) It seems that what I would like to achieve should already be possible, as long as the "acpi_pat.cfg" file is in the same directory as the executable file.

Hi schreiberstein,
- a.exe reads all files from directory where a.exe started, you can place it in any place at directory tree
- a.exe uses preallocated "virtual floppy" from grub4dos to claim memory for storing acpi tables, to avoid grub4dos tricks need write own int15 e820 handler to exclude some ram from OS

#2839

diderius6

⇗ @Mov AX, 0xDEAD
This are nice news:))!!
I just desoldered my Bios chip from the Lenovo Flex 10 notebook,
flash it with new DSDT via Revelprog IS,
and solder it in again.
Flex 10 survives this operation^^.
What I changed in DSDT is via Iasl -r1 ,
now no 64 bit math is supported. Before I went like crazy with unfullfilled
dependencies (externals) in Iasl and its build *.dsl =>*.aml. Only when I use the original iasl.exe (iasl-win-20130117)
from which this DSDT was originally build, I succeed.
Now I test there debug over USB3
thanks a lot
Dietmar

#2840

schreiberstein

⇗ @Mov AX, 0xDEAD
Hello Mov AX, OxDEAD.
I have tried to adapt your application to my use case today. (I am not a system engineer or embedded developer though)
The grub menu creation as well as attempting to read root.txt part have been removed by me from the main.c, as well as the part that would try to execute GRUB again or waits for SHIFT-KEY.
I compiled the C file using the latest DJGPP environment on DOSBOX. (Was unable to run a 4.x version of GCC for some reason)
The patched DSDT.aml file, as provided by Dietmar, has been compiled manually by me using the respective isl compiler version. I named it "reload.bin".
The MAIN_LOG.txt says "table DSDT replaced, new size= 264991", but then the program complains about the missing GRUB4DOS int13 handler.
Can I load GRUB's interrupt handler, and then continue in a DOS prompt?
It might be a stupid question, but could you briefly explain what it is needed for?
I attached my directory that included my adapted C file, config, LOG and DSDT, in case you are interested.
Thank you.
Cheers,
schreiberstein
schreiberstein has attached files to this post

- ⇗ PATCH.zip

#2841

Mov AX, 0xDEAD

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #2737

> @Mov AX, 0xDEAD
> On the Asrock fatal1ty z370 gaming k6,
> with the same files for USB debug,
> compi also reboots at once

forget about usb3 inside kdnet, this was my mistake )
check kdusb.dll from github, i hope you will find needed original kdusb.dll

#2842

schreiberstein

⇗ @Mov AX, 0xDEAD
Oops, your reply was faster than my new post. Sorry.
So, if I understand correctly, this construction exists for a very specific reason.
The operation system needs to be specifically told that it must use 2 MB of memory less, right?
And that means that there is nothing that can be modified in RAM that would allow another bootloader, oblivious of what has happened, to detect that change, correct?
If that is not possible, then I will think of something else or install XP using a different system, install your patcher and hook it up to my main Z390 system.
Cheers,
schreiberstein
EDIT: My main concern was about booting the installation media on my system to make sure device detection and configuration works out-of-the-box.

#2843

Doc.Brown

⇗ @diderius6
Some update after the test with 0057 modded bios,flash the board and she's still alive :D
Your bios is better than original one cause now there's no BSOD before HDD scan so no need to press F5 or F7 to go forward ! It allow to create partition (one little in FAT and the other in NTFS for XP ), file copy is ok and first reboot also.
After that problem comes in the middle of peripherals installation as you can see on this capture:
⇗
Result on this BSOD 0A :
⇗
After a reset to restart the board a new BSOD A5 comes :
⇗
Another ACPI lock at next level in bios ?
I tested with few XP iso,load fail safe default for IRQL not less or equal BSOD but it's always same errors
Thanks :)

#2844

diderius6

⇗ @Doc.Brown
Waaoh, that means I found exact the place for BSOD 0x10006 in DSDT and repair it there.
So much good news today!!! Now XP will run on ALL x390 boards, Apex XI and so on with this mod.
Last days I compare soso many DSDTs. And they are all the same. Manufacturers deleted important information in DSDT
and because of that XP crashes. XP works very strict in translating DSDT.
The problem with second acpi Bsod is,
that crazy XP just reinstalls its own original acpi.sys in windows\system32^^.
Just copy modded acpi.sys there again.
The other Bsod happens,
because XP does not like a device on the gene XI board.
Sometimes you can overcome this hitting F8 (Safe Mode).
Try to disable as much devices as you can in Bios. Later you can activate them again.
If this does not help,
use an XP install from another compi,
Dietmar
PS: With lan Debug from ⇗ @Mov AX, 0xDEAD we now can find the device, which crashes.

#2845

Mov AX, 0xDEAD

> Zitat von ⇗ schreiberstein im Beitrag ¶ #2840

> @Mov AX, 0xDEAD
> The MAIN_LOG.txt says "table DSDT replaced, new size= 264991", but then the program complains about the missing GRUB4DOS int13 handler.
> Can I load GRUB's interrupt handler, and then continue in a DOS prompt?
> It might be a stupid question, but could you briefly explain what it is needed for?

int13 is place where patcher can find virtual floppy, it searched by magic pattern $INT13SFGRUB4DOS (just like firadisk did)
grub4dos before runing any os:
- allocate memory for empty floppy
- set own int13 handler
- set own int15 e820 handler
- unload self from memory, but floppys and handlers stayed resident
patcher:
- look for $INT13SFGRUB4DOS near to int13
- find where floppy allocated and uses this memory as new store for acpi tables (original store was prepared by bios)
after patcher done own work, int13 no need anymore, grub4dos's int15 still need to exclude memory from OS.
i dont know much about grub4dos.exe, maybe it has some like CLI mode to process menu.cfg & return to dos

#2846

Mov AX, 0xDEAD

> Zitat von ⇗ schreiberstein im Beitrag ¶ #2842

> @Mov AX, 0xDEAD
> If that is not possible, then I will think of something else or install XP using a different system, install your patcher and hook it up to my main Z390 system.
> EDIT: My main concern was about booting the installation media on my system to make sure device detection and configuration works out-of-the-box.

Also possible integrate patcher to boot media (i've not tested), ntldr_patcher rename to SETUPLDR.BIN, original SETUPLDR.BIN to XPLDR
so chain will be almost same, grub4dos is loaded first, then dos, then 2nd grub4dos.exe to run original SETUPLDR.BIN as binary

#2847

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #2844

> @Doc.Brown
> Waaoh, that means I found exact the place for BSOD 0x10006 in DSDT and repair it there.
> So much good news today!!! Now XP will run on ALL x390 boards, Apex XI and so on with this mod.
> Last days I compare soso many DSDTs. And they are all the same. Manufacturers deleted important information in DSDT
> and because of that XP crashes. XP works very strict in translating DSDT.
> The problem with second acpi Bsod is,
> that crazy XP just reinstalls its own original acpi.sys in windows\system32^^.
> Just copy modded acpi.sys there again.
> The other Bsod happens,
> because XP does not like a device on the gene XI board.
> Sometimes you can overcome this hitting F8 (Safe Mode).
> Try to disable as much devices as you can in Bios. Later you can activate them again.
> If this does not help,
> use an XP install from another compi,
> Dietmar
> PS: With lan Debug from @Mov AX, 0xDEAD we now can find the device, which crashes.

Yep it's a really good news being able to go forward in the installation process,you make it happen :)
I already tried F8 for Safe Mode and it also result in BSOD unfortunately
I try to copy ACPI.sys and a fresh install on X299 Rampage Apex(I already have a ghost of previous test) tomorrow ;)

#2848 | diderius6 | ⇗ @Mov AX, 0xDEAD I find small error in description: "On Target (must be Host) PC need Windows 8/10 to be installed with Microsoft drivers for USB3.0 controllers (Vendor's usb3.0 drivers not supported by WinDBG/KD)" Have a nice day Dietmar

#2849

daniel_k

⇗ @schreiberstein, this is my patched DSDT for your board.
This version should work with original XP files, not a single patch needed.
The following files are included:
Z390DESI_F7_original.raw -> original from BIOS
Z390DESI_F7_original.aml -> original compiled
Z390DESI_F7_original.dsl -> original decompiled
Z390DESI_F7_mod.aml -> modded compiled
Z390DESI_F7_mod.dsl -> modded decompiled
Just compare the originals, 99.99% the same as Gigabyte's.
RAW = Gigabyte
AML = Compiled
Just learned that there are code changes when using latest iasl.exe, so use it just to decompile the binary DSDT (aml) file.
Also, we must use -dl parameter when decompiling (emit legacy ASL code), otherwise final code won't match original's.
To compilte the code, use the same version used in the original BIOS (20160527), check the ReadMe.txt included for command line.
daniel_k has attached files to this post

- ⇗ Z390DESIG_F7.rar

#2850 | daniel_k | ⇗ @schreiberstein, don't worry about ACPI patches. I've managed to patch ACPI.SYS for Z390!!! It worked right away on the first try! Just give me some minutes and I'll upload an updated package for you to try.

## Page 191

#2851

diderius6

⇗ @daniel_k ⇗ @schreiberstein
With this nice mod in DSDT from Daniel I think you even dont need modded acpi.
So ⇗ @schreiberstein use DSDT from Daniel.
But we need to be careful with mod:
On newer Gene XI Bios, they treated the _dis method in DSDT other,
so it will come in conflict with our so we have to delete all old use of _dis there and rebuild with our
Dietmar

#2852 | diderius6 | ⇗ @daniel_k "I've managed to patch ACPI.SYS for Z390!!!" I am so curious, how you did this Dietmar
#2853 | daniel_k | ⇗ @diderius6, let me try it properly first. Just tried the patched ACPI.SYS with an already installed XP. Will install from scratch before sharing it.
#2854 | schreiberstein | ⇗ @daniel_k Ready to create a new iso. Wouldn't bother to test it. Sounds promising. :-)

#2855

daniel_k

⇗ @schreiberstein, ⇗ @diderius6
Installation completed successfully!
No errors at all, no ACPI errors in Event Viewer, IRQs assigned properly (*)
(*) Error is related to missing _DIS method in PNP0C0F (PCI Interrupt Link Device. A device that allocates an interrupt connected to a PCI interrupt pin.)
Sending you a PM with package link.

#2856 | schreiberstein | ⇗ @daniel_k Thank you! I am assembling an ISO file in a few minutes. Will get back to you soon. Thank you for your effort. schreiberstein

#2857

daniel_k

⇗ @diderius6
Firsly, I simulate the issue of Z390 boards by renaming the _DIS in ACPI.SYS to _DES, which doesn't exist in the DSDT table of my BIOS.
Jumped the KeBugCheckEx 0x10006 and got the same error as schreiberstein. Same behavior, test is valid!
Analyzing the code, I've realized that all it does is an additional check if device is PNP0C0F, otherwise, it ignores and proceed.
Just patched it so it treats PNP0C0F as an ordinary device and worked.

#2858 | daniel_k | Patched ACPI.SYS files now supporting Z390 boards.

#2859

Andalu

> Zitat von ⇗ Andalu im Beitrag ¶ #2817

> @daniel_k
> the registry key you have identified (ExtPropDescSemaphore) maybe can be the cause for the USB3 function not working on my asrock B75 Pro3-M. The same key related to the same external hard disk appears also in my other system where the USB3 does not work while it is not present where the usb3 works fine (asrock B250M Pro4). I don't think it can be just a coincidence but how to verify it? It's very difficult to prevent this registry key from being created every time the external hard drive is connected to computer.

Bad news from here. Even blocking the creation of the regitry key "ExtPropDescSemaphore=dword:00000001" the usb3 fails anyway. The enigma continues....
I renew my request already made at ¶ #2637 about a way to get XP32 supports more than 4GB memory with amd modded drivers. I'll use the ram over 4GB for ramdisk purpose. I already tried the 'chinese patch' and other methods found on the net with no success.
Is there a way to solve?

#2860 | diderius6 | ⇗ @daniel_k Waaoh, what great success:))!! Wish you nice day and good mood Dietmar

#2861

schreiberstein

⇗ @daniel_k
You bloody madman! You did it!
I created my own ISO from Xp Iso Builder, only enabled the A352 AHCI from Fernando and replaced the acpi.sys file.
The installer boots up. USB isnt working because I did not integrate it. Will boot again with PS2 attached and try to install. But I could hear the CD drive seeking after it said Starting Windows, so everything is fine and it found the AHCI stuff.
Wooooooowwww wooohoooo!
Will keep you posted. So amazing.
Thank you so much!
Cheers,
schreiberstein
schreiberstein has attached images to this post ⇗ F9327103-F8F0-47F8-AE97-B

#2862 | daniel_k | ⇗ @Andalu, sorry but I'm out of ideas. Maybe someone else can help you with those issues.

#2863

schreiberstein

⇗ @daniel_k
It is now in the second stage of the installation process.
PS/2 works.
And the boot process was super fast compared to non-acpi mode. Just as expected from a Core i9... just a few short seconds. :D
schreiberstein
schreiberstein has attached images to this post ⇗ AB348FF1-D962-49B9-9195-0

#2864 | daniel_k | ⇗ @schreiberstein, glad to know it worked! Sure you can do whatever you want, but I've sent you a PM with a ready to use pack including USB drivers. Would be nice if you could test it, as I'm working on a all-in-one ISO which I'll upload somewhere when finished, so everyone can enjoy a compatible and fully updated install of XP SP3.

#2865

schreiberstein

⇗ @daniel_k
I know.
I will try that as well. But your ISOs do not seem to work with the A352 AHCI controller for some reason. At least the first two attempts I tried. And I did not want to mix the two just now.
Maybe some drivers conflict with eachother?
I can choose the A352 in XP Iso Builder and did not have an issue.
I sure can test more ISOs, when it helps! :-)
Cheers,
schreiberstein

## Page 192

#2866 | daniel_k | ⇗ @schreiberstein, you must use my package as it is, with a clean ISO source. Otherwise you'll surely have issues.

#2867

schreiberstein

⇗ @daniel_k
Oh, I am getting a bluescreen after the first start now. A5
Was it not enough to put the acpi.sy_ into the i386 folder?
I suppose the original one got swapped in again.
Right?
Cheers,
schreiberstein
schreiberstein has attached images to this post ⇗ C4829A5B-322E-4565-ACA0-5

#2868 | daniel_k | ⇗ @diderius6, I've updated the files in the following post: ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (149)
#2869 | daniel_k | ⇗ @schreiberstein, that's why I've sent you the package. ACPI.SYS must be replaced in SP3.CAB, otherwise Setup will restore the original version during last installation phase.

#2870

schreiberstein

⇗ @daniel_k
Oh, I am sorry.
I will create a new ISO from your package.
How can I be sure that the 8086:A352 will be loaded properly?
By the way, I suspect reboot might not work properly. During the installation when it attempted to restart, it would just hang the entire machine. Not even the reset button would work. Very strange.
Maybe this is just a side effect.
I will create a new ISO shortly.
Cheers,
schreiberstein

#2871 | Andalu | ⇗ @daniel_k no problem, I just have to say thank you ;) then there will be someone who will use the ram over 4GB for a ramdisk.

#2872

daniel_k

> Zitat von ⇗ schreiberstein im Beitrag ¶ #2870

> How can I be sure that the 8086:A352 will be loaded properly?
> By the way, I suspect reboot might not work properly. During the installation when it attempted to restart, it would just hang the entire machine. Not even the reset button would work. Very strange.
> Maybe this is just a side effect

You'll see your HDD or SSD available as an installation drive.
Yes, it hangs sometimes, I believe that it is related to VGA driver, but only happens during Setup.
Just wait a few seconds and press the reset button, don't need to wait that long.
Here, with the driver for my GTX 980 installed, it has never happened.

#2873

schreiberstein

⇗ @daniel_k
Alright!
I had a look into the iaAHCI.inf file of your package and noticed that this is a different driver.
It does not have the list of device IDs (such as A352) in there and is newer (2017 vs 2012).
Maybe the new iaAHCI driver works if the ID is added somewhere.
Since this driver previously hasnt worked, I replaced it with the 2012 version.
I hope I have done it correctly. Simply overwritten the files.
I am burning the new ISO now from your package.
The AHCI driver I am using is Universal Intel RST Drivers+Software Set v11.2.0.1006mod+signed by Fernando .
It explicitly has the A352 as added by Fernando in the inf file.
Hope this will work.
Cheers and thank you,
schreiberstein

#2874 | daniel_k | ⇗ @schreiberstein, it doesn't have IDs, because it uses a PCI class code: CC_0106 = AHCI CC_0104 = RAID Which means all AHCI or RAID controllers from Intel (VEN_8086). Maybe my driver didn't work before because you were trying to install it in non-ACPI mode or legacy mode.
#2875 | schreiberstein | ⇗ @daniel_k Okay. I understand. :-) My attempt ended in a blank screen after it loaded the kernel. I am now burning an ISO that was created exclusively from your package. schreiberstein

#2876

schreiberstein

⇗ @daniel_k
Same result with the configuration from your package.
The screen goes black. The CDROM makes another noise.
NUM-led cannot be toggled.
No bluescreen, nothing.
Do you have any idea why this is happening?
Just out of curiosity, if I copied your SP3.CAB file into my Winfuture Iso Builder i386 folder, would the acpi.sys get replaced properly?
Or if I simply extracted the CAB, added the file and compressed it again?
I just want to see how much of the system will be usable and if all cores are detected, etc.
Maybe some other driver causes this during the installation.
I am happy to assist for troubleshooting and for improving your installation package. Don't worry. ;-)
Cheers,
schreiberstein :-)

#2877 | daniel_k | ⇗ @schreiberstein, strange, I have no idea. Maybe the USB drivers are causing issues? Anyway, yes, just copy my SP3.CAB and the install will surely proceed as that is where Setup gets the original file from.

#2878

diderius6

⇗ @schreiberstein
Try with a complete XP SP3 install from another compi
Dietmar
PS: For sure it is a device on your motherboard,
that does not like to work with XP. Disable everything in Bios, all what you dont need for install.
It is like training for XP^^.
EDIT: I noticed, that some devices arent any more in DSDT from XP friendly Bios of the nice EVGA dark z390 board.
In XP unfriendly Bios they stay in DSDT.

#2879

schreiberstein

⇗ @daniel_k
I managed to boot into my completed Windows XP installation after replacing the acpi.sys under system32/drivers manually using some psexec.exe magic on Windows 10.
Still black screen -> then I decided to boot with Enable VGA Mode and voila...
All 16 threads detected, only 904MB RAM, USB does not seem to work. No Standard VGA graphics card detected, etc.
Maybe the integrated headless Intel HD graphics confuses it. But I need it enabled for Mac OS X. It is used for rendering JPEGs and acceleration.
But I am so glad this acpi.sys patch did make such a dramatic difference.
Cheers,
schreiberstein
EDIT:
I was able to get the Intel I211 ethernet NIC (8086:1539) running with a driver I found here somewhere.
Connection established, ping works. Amazing. A bit of relief.
schreiberstein has attached images to this post ⇗ 3A830214-F4E5-4E18-A8E0-1 ⇗ 4AB76E2B-887C-460C-BEF7-D

#2880

diderius6

⇗ @Mov AX, 0xDEAD
I just installed Win8.1 32 bit on the Lenovo Flex 10 notebook. My modded Bios there likes now 32 bit a lot.
What crazy long time its need. I make a full XP SP3 install with all updates
and a lot of programs in 1/3 of this time^^.
On the Asrock fatal1ty z370 gaming k6 under Win10 64 bit I make a quick check for USB debug possibility.
There, nearly all ports can do debug via USB3.
On the Lenovo Flex 10 , at this short moment under win8.1, is one(!) port, that supports USB3 debug as viewusb from windbg 8.1 tells there.
But until now I do not succeed with windbg under XP SP3 on the Flex 10 as target, where the modified kdusb.dll stays in windows\system32.
Has the System on the Host (where the programm Windbg starts) also to be under win8.1 32 bit
Dietmar
EDIT: In next try, I look, if the Flex 10 can do USB3 debug at all. For this I try to enable normal USB3 debug with Win8.1 32 bit
on the Flex 10 as target.
EDIT2: In combination Win 8.0 32 bit (Target, compi Flex 10 that should be debugged) via
bcdedit /debug on
bcdedit /dbgsettings usb targetname:otto
and Host Win 10 64 bit (Compi, where Windbg runs) I get using usbview.exe the message "error: Enumeration failed" on both compis.
So I think, even usbview shows that USB Debug is possible on the Flex 10, it is just not true.
Now I update win8 -> win8.1 each 32 bit on the target Flex 10
and I put original English win8.1 32 bit on Host compi.
EDIT3: On the Flex 10 Notebook I have now Win8.1 32 bit german version (as target)
and on Asrock Win8.1 32 bit English original version (from which the new debug files are).
But Debug via USB3 seems not to work for the Flex 10 as target.
Here are the two files from usbview from Flex 10
and from usbview from Asrock board.
EDIT4: When I change Host <-> Target, USB debug works, see spoiler 3 here.

    [Port7] Enumerating

    Is Port User Connectable:         yes
    Is Port Debug Capable:            yes
    Companion Port Number:            1
    Companion Hub Symbolic Link Name: USB#ROOT_HUB30#4&1cecc9c3&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
    Protocols Supported:
     USB 1.1:                         no
     USB 2.0:                         no
     USB 3.0:                         yes

           ---===>Device Information<===---

    ConnectionStatus:                  Enumerating
    Current Config Value:              0x00  -> Device Bus Speed: Low
    Device Address:                    0x00
    Open Pipes:                           0
    *!*ERROR:  No open pipes!

              ===>Device Descriptor<===
    *!*ERROR:  bLength of 0 incorrect, should be 18
    bLength:                           0x00
    bDescriptorType:                   0x00
    bcdUSB:                          0x0000
    bDeviceClass:                      0x00  -> This is an Interface Class Defined Device
    bDeviceSubClass:                   0x00
    bDeviceProtocol:                   0x00
    bMaxPacketSize0:                   0x00 = (0) Bytes
    *!*ERROR:  Low Speed Devices require bMaxPacketSize0 = 8
    idVendor:                        0x0000idProduct:                       0x0000
    bcdDevice:                       0x0000
    iManufacturer:                     0x00
    iProduct:                          0x00
    iSerialNumber:                     0x00
    bNumConfigurations:                0x00
    *!*CAUTION:    Most host controllers will only work with one configuration per speed

    [Port19] Enumerating

    Is Port User Connectable:         yes
    Is Port Debug Capable:            yes
    Companion Port Number:            8
    Companion Hub Symbolic Link Name: USB#ROOT_HUB30#4&556f44c&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
    Protocols Supported:
     USB 1.1:                         no
     USB 2.0:                         no
     USB 3.0:                         yes

           ---===>Device Information<===---

    ConnectionStatus:                  Enumerating
    Current Config Value:              0x00  -> Device Bus Speed: Low
    Device Address:                    0x00
    Open Pipes:                           0
    *!*ERROR:  No open pipes!

              ===>Device Descriptor<===
    *!*ERROR:  bLength of 0 incorrect, should be 18
    bLength:                           0x00
    bDescriptorType:                   0x00
    bcdUSB:                          0x0000
    bDeviceClass:                      0x00  -> This is an Interface Class Defined Device
    bDeviceSubClass:                   0x00
    bDeviceProtocol:                   0x00
    bMaxPacketSize0:                   0x00 = (0) Bytes
    *!*ERROR:  Low Speed Devices require bMaxPacketSize0 = 8
    idVendor:                        0x0000idProduct:                       0x0000
    bcdDevice:                       0x0000
    iManufacturer:                     0x00
    iProduct:                          0x00
    iSerialNumber:                     0x00
    bNumConfigurations:                0x00
    *!*CAUTION:    Most host controllers will only work with one configuration per speed

    Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Using USB for debugging
    Waiting to reconnect...
    USB: Write opened
    Connected to Windows 8 9600 x86 compatible target at (Fri Oct 11 18:31:49.092 2019 (UTC + 2:00)), ptr64 FALSE
    Kernel Debugger connection established.
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe -
    Windows 8 Kernel Version 9600 MP (1 procs) Free x86 compatible
    Built by: 9600.17415.x86fre.winblue_r4.141028-1500
    Machine Name:
    Kernel base = 0x80e76000 PsLoadedModuleList = 0x81075418
    System Uptime: 0 days 0:00:00.804
    KDTARGET: Refreshing KD connection
    nvLDDMkm: Driver Registry Path = '\REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\nvlddmkm'
    nvAdapter:
     Device Registry Path =
    '\REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000'
    nvAdapter:
    nvAdapter:                    ***** CNvLAdapter* 8cfe9000 -> DriverModel is 0x1300 ******
    nvAdapter:
    Break instruction exception - code 80000003 (first chance)
    *******************************************************************************
    *                                                                             *
    *   You are seeing this message because you pressed either                    *
    *       CTRL+C (if you run console kernel debugger) or,                       *
    *       CTRL+BREAK (if you run GUI kernel debugger),                          *
    *   on your debugger machine's keyboard.                                      *
    *                                                                             *
    *                   THIS IS NOT A BUG OR A SYSTEM CRASH                       *
    *                                                                             *
    * If you did not intend to break into the debugger, press the "g" key, then   *
    * press the "Enter" key now.  This message might immediately reappear.  If it *
    * does, press "g" and "Enter" again.                                          *
    *                                                                             *
    *******************************************************************************
    *** ERROR: Module load completed but symbols could not be loaded for ntdll.dll
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe -
    nt!DbgBreakPointWithStatus+0x4:
    80f73014 cc              int     3
    8: kd> lm
    start    end        module name
    77450000 775b9000   ntdll      (no symbols)
    803a4000 803b4000   kdcom      (deferred)
    80e1d000 80e76000   hal        (deferred)
    80e76000 8142a000   nt         (export symbols)       ntkrpamp.exe
    81800000 8180a000   Fs_Rec     (deferred)
    81830000 819d5000   Ntfs       (deferred)
    819d5000 819eb000   ksecdd     (deferred)
    819eb000 819f9000   pcw        (deferred)
    81c23000 81df3000   tcpip      (deferred)
    81e38000 81e80000   fwpkclnt   (deferred)
    81e80000 81e93000   wfplwfs    (deferred)
    81e93000 81f10000   fvevol     (deferred)
    81f10000 81f52000   volsnap    (deferred)
    81f52000 81f87000   rdyboost   (deferred)
    81f87000 81f98000   mup        (deferred)
    81f98000 81fa4000   intelpep   (deferred)
    81faf000 81fc6000   disk       (deferred)
    81fc6000 81ffd000   portcls    (deferred)
    82000000 8204a000   CLASSPNP   (deferred)
    8204a000 8205b000   crashdmp   (deferred)
    82092000 820b5000   cdrom      (deferred)
    820b5000 820bd000   Null       (deferred)
    820bd000 820c4000   Beep       (deferred)
    820c4000 820d0000   BasicRender   (deferred)
    820d0000 8210a000   netbt      (deferred)
    8210a000 82182000   afd        (deferred)
    82182000 821a5000   pacer      (deferred)
    821a5000 821b3000   netbios    (deferred)
    821b3000 821ed000   ks         (deferred)
    85229000 85290000   mcupdate_GenuineIntel   (deferred)
    85290000 8529c000   werkernel   (deferred)
    8529c000 852e6000   CLFS       (deferred)
    852e6000 85301000   tm         (deferred)
    85301000 85314000   PSHED      (deferred)
    85314000 8531d000   BOOTVID    (deferred)
    8531d000 85397000   CI         (deferred)
    85397000 853c8000   msrpc      (deferred)
    853c8000 853ff000   pci        (deferred)
    85425000 85481000   spaceport   (deferred)
    85481000 85492000   volmgr     (deferred)
    85492000 854df000   volmgrx    (deferred)
    854df000 854f5000   mountmgr   (deferred)
    854f5000 8550e000   storahci   (deferred)
    8550e000 8555d000   storport   (deferred)
    8555d000 85573000   EhStorClass   (deferred)
    85573000 855b9000   fltmgr     (deferred)
    855b9000 855cb000   fileinfo   (deferred)
    855cb000 855f0000   Wof        (deferred)
    85600000 85617000   pdc        (deferred)
    85623000 856b9000   Wdf01000   (deferred)
    856b9000 856c7000   WDFLDR     (deferred)
    856c7000 856d8000   acpiex     (deferred)
    856d8000 856e2000   WppRecorder   (deferred)
    856e2000 8574f000   ACPI       (deferred)
    8574f000 85758000   WMILIB     (deferred)
    85758000 857cf000   cng        (deferred)
    857d9000 857e1000   msisadrv   (deferred)
    857e1000 857ec000   vdrvroot   (deferred)
    857ec000 85800000   partmgr    (deferred)
    85831000 8586b000   WdFilter   (deferred)
    8586b000 85945000   ndis       (deferred)
    85945000 8599a000   NETIO      (deferred)
    8599a000 859c1000   ksecpkg    (deferred)
    8d600000 8d61a000   tdx        (deferred)
    8d61e000 8d768000   dxgkrnl    (deferred)
    8d768000 8d777000   watchdog   (deferred)
    8d777000 8d7c9000   dxgmms1    (deferred)
    8d7c9000 8d7d9000   BasicDisplay   (deferred)
    8d7d9000 8d7e9000   Npfs       (deferred)
    8d7e9000 8d7f4000   Msfs       (deferred)
    8d7f4000 8d800000   TDI        (deferred)
    8d800000 8d82c000   nvhda32v   (deferred)
    8d835000 8d88a000   rdbss      (deferred)
    8d88a000 8d8f9000   csc        (deferred)
    8d8f9000 8d905000   nsiproxy   (deferred)
    8d905000 8d910000   npsvctrig   (deferred)
    8d910000 8d91b000   mssmbios   (deferred)
    8d91b000 8d939000   dfsc       (deferred)
    8d948000 8d95c000   ahcache    (deferred)
    8d95c000 8d969000   CompositeBus   (deferred)
    8d969000 8d973000   kdnic      (deferred)
    8d973000 8d982000   umbus      (deferred)
    8d982000 8d9ef000   e1d6232    (deferred)
    8f800000 8f808000   NdisVirtualBus   (deferred)
    8f808000 8f809480   swenum     (deferred)
    8f80a000 8f814000   rdpbus     (deferred)
    8f814000 8f829000   drmk       (deferred)
    8f82b000 90671000   nvlddmkm   (deferred)
    90671000 90686000   HDAudBus   (deferred)
    90686000 906c9000   USBXHCI    (deferred)
    906c9000 906f4000   ucx01000   (deferred)
    906f4000 9071f000   TeeDriverW8   (deferred)
    9071f000 9077f000   e1i6332    (deferred)
    9077f000 90798000   i8042prt   (deferred)
    90798000 907a6000   kbdclass   (deferred)
    907a6000 907b2000   mouclass   (deferred)
    907b2000 907ca000   serial     (deferred)
    907ca000 907d4000   serenum    (deferred)
    907d4000 907dd000   wmiacpi    (deferred)
    907dd000 907f6000   intelppm   (deferred)
    907f6000 907fe000   acpipagr   (deferred)
    90a1a000 90a7b000   UsbHub3    (deferred)
    90a7b000 90a85000   USBD       (deferred)
    90a85000 90ad5000   HdAudio    (deferred)
    90ad5000 90adb980   HIDPARSE   (deferred)
    90adc000 90b20000   udfs       (deferred)
    90b20000 90b2b000   dump_diskdump   (deferred)
    90b2b000 90b44000   dump_storahci   (deferred)
    90b44000 90b57000   dump_dumpfve   (deferred)
    90b57000 90b62000   nvvadarm   (deferred)
    90b62000 90b6d000   monitor    (deferred)
    90b6d000 90b8a000   luafv      (deferred)
    90b8a000 90b9a000   lltdio     (deferred)
    90b9a000 90bae000   rspndr     (deferred)
    91e00000 9217b000   win32k     (deferred)
    921a5000 921ad000   TSDDD      (deferred)
    98e81000 98eb0000   cdd        (deferred)
    9de00000 9de19000   Ndu        (deferred)
    9de19000 9de2b000   mslldp     (deferred)
    9de34000 9deed000   HTTP       (deferred)
    9deed000 9df07000   bowser     (deferred)
    9df07000 9df18000   mpsdrv     (deferred)
    9df18000 9df6f000   mrxsmb     (deferred)
    9df6f000 9df9a000   mrxsmb20   (deferred)
    9dfb2000 9dfee000   mrxsmb10   (deferred)
    9f205000 9f2a6000   peauth     (deferred)
    9f2a6000 9f2b0000   secdrv     (deferred)
    9f2b0000 9f2e3000   srvnet     (deferred)
    9f2e3000 9f2f1000   tcpipreg   (deferred)
    9f2f1000 9f380000   srv2       (deferred)
    9f380000 9f3d6000   srv        (deferred)
    9f3d6000 9f3fb000   tunnel     (deferred)

    Unloaded modules:
    9df9a000 9dfb2000   WdNisDrv.sys
    9df9a000 9dfb2000   parport.sys
    8205b000 82066000   dump_storport.sys
    82066000 8207f000   dump_storahci.sys
    8207f000 82092000   dump_dumpfve.sys
    8d939000 8d948000   dam.sys
    857cf000 857d9000   WdBoot.sys
    81fa4000 81faf000   hwpolicy.sys

## Page 193

#2881 | daniel_k | ⇗ @schreiberstein, I see too many devices. Maybe more than XP can handle. Try to disable some (2 network controllers?!), for testing purposes. That's enough for today. Good night to everyone!
#2882 | diderius6 | ⇗ @schreiberstein I noticed in your Device Manager, that a lot of entries are just double. Disable the fake ones and most is done Dietmar

#2883

schreiberstein

⇗ @diderius6
Which devices do you mean?
I disabled all Other Devices I do not need (NVMe drives, wifi, bluetooth, etc)
Sometimes, USB works. I even got USB sound.
But after a reboot, USB is yellow again...
Is there something I can disable under System devices to free up ressources?
It is strange.
schreiberstein has attached images to this post ⇗ 181752D1-0E28-4F18-B413-7

#2884 | diderius6 | ⇗ @schreiberstein Some devices are double. Take a look at its Irqs in Device Manager (Ansicht->Resourcen nach Typ->Interruptanforderung) Dietmar

#2885

schreiberstein

⇗ @diderius6
Hmm...
It seems like all these devices are unique.
The bridges each have a different location
Number 10 cannot find enough free resources.
I think I have seen something similar in this thread.
Schreiberstein
schreiberstein has attached images to this post ⇗ 6CEDFA41-E15F-4AF5-AFB3-E

#2886

Gelip

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #2880

> My modded Bios there likes now 32 bit a lot.

Is this bios 32-bit UEFI? If so, I am very curious if WinXP 32-bit starts under UEFI with vista beta 6.0.5219.0 32-bit files.

#2887 | infuscomus | ⇗ @Andalu concerning more than 4GB RAM and XP, you can try this Get upto 128GB with PAE in Windows XP 32bit ⇗ https://www.betaarchive.com/forum/viewtopic.php?f=61&t=36597

#2888

Andalu

⇗ @infuscomus
Many thanks for your help ;)
I already knew that patch. I tried it one more time but I got blank screen as always on my B250M Pro4 board.
It will seem incredible but on the crazy B75Pro3M board the 'chinese patch' works fine with the amd modded driver (at least until the pc is not shutdowned and at the same time the power is not turned off for over one minute).
Instead, on my B250M Pro4 board the 'chinese patch' doesn't work when the amd modded drivers are installed. With the acpy.sys 5048 only and no amd modded drivers, the system correctly recognize more than 4GB and I have not the issues reported at ¶ #2637.
I have six motherboards but in no one I can get the USB3 fully functional with the possibility to use more than 4GB of ram without problems.
I'm still looking for the right combination before I go crazy.... :D

#2889

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #2848

> @Mov AX, 0xDEAD
> I find small error in description:

Fixed, thanks!

#2890 | infuscomus | ⇗ @Andalu just a suggestion, try doing a fresh install with the RAM patch? I have had better luck getting the RAM patch to work by nlite-ing it into an ISO and doing a fresh install than trying to patch an existing install.

#2891

schreiberstein

By the way, how does the limit of ~900MB come about? What is reserving so much memory?
I am considering creating a Server 2003 ISO to check if the behavior is similar to XP. Maybe 2003 works better. I always had a high opinion of it.
Is there any chance the acpi.sys is compatible with Windows 2000 SP4 (NT 5.0)?
Cheers,
schreiberstein

#2892

infuscomus

⇗ @schreiberstein
I may be wrong about this, but I believe Microsoft introduced an artificial limit to RAM in SP1 or SP2 because badly programmed device drivers did not handle 4GB of RAM properly.
I think XP SP0 has access to all 4GB of RAM.
Check the hal.dll and ntoskrnl.exe of Windows 2000 SP4 with dependency walker and see if patched acpi 5048 has any missing imported functions, if it's all green and no red then it should work.
edit:
ntoskrnl 2000 missing
InterlockedPopEntrySList
InterlockedPushEntrySList
HeadlessDispatch
ExfInterlockedCompareExchange64
so I doubt it's ever going to work

#2893

tarsonis

> Zitat von ⇗ diderius6 im Beitrag ¶ #2820

> @tarsonis
> Most easy is to use from commandline
> makecab acpi.sys
> this gives you acpi.sy_
> This you put to i386 folder for nlite to make CD XP SP3.
> The same for storport.sys.
> Then you integrate Txtmode via nlite driver STORAHCI from ⇗ @skullteria .
> No need to integrate USB files if you have a PS/2 connector
> Dietmar

So I did it wrong putting the *.sy_ after nlite finalize the setup files? The *.sy_ files need to be put in the XP folder before one selects it as source for nlite?
The storport.sys file that is included in the STORAHCI driver from ⇗ @skullteria is the correct one?
Do I need to select a processor type (F7) for the setup and is "ACPI Multiprocessor" correct for the Ryzen 1800x?
I have no PS/2 connector on the CH6 x370.

#2894

XPLives

> Zitat von ⇗ daniel_k im Beitrag ¶ #2858

> Patched ACPI.SYS files now supporting Z390 boards.

Daniel_K
I've been testing your Z390 ACPI mod for close to half a day.
You've finally fixed the biggest issue that you already fixed in your previous XP / 2003 64-Bit ACPI mod that I mentioned.
The Device Manager now shows the Video Card! Congrats!!! No BIOS Modding required.
First time ever in 32-Bit XP and 2003 it now shows the Video Card with ACPI on Coffee Lake.
Video drivers now install without any issues now that the video card is present. Huge success otherwise XP is handicapped.
From what I can tell your 64-Bit earlier ACPI.sys mod now matches in functionality on the new 32-Bit Z390 Mod.
I will add your MOD to the ACPI Drivers Depot so it is easier to locate for people from almost 3000 messages in this bloated thread.
⇗ Modded ACPI Drivers Depot 2000 XP 2003 2009
[Possible Last ACPI related issues left to fix]
But there still exists problems which only happen under both of your 32-Bit and 64-Bit mods which I cannot explain why.
I think so far ACPI functionality is about 80% fully working and almost 100% soon without any BIOS modding.
I do not know if you are a gamer or not but if you use MAME you can test to verify if it happens on your system.
Test any arcade game in MAME to see if it freezes once any audio begins to play.
So far this is the most consistent problem that hasn't been resolved.
Other problems found in other XP Games too. Crysis 1 Game Demo will freeze with audio stuttering loop so you must end the task in Task Manager.
I tried both PCI and USB Audio devices and this made no difference so it is not a USB related issue.
I also tested HDMI Audio out and the problem still exists in MAME.
Once this is done I think XP is 100% Alive in ACPI. You should be proud of what you accomplished with this recent Z390 Mod.
Maybe this BSOD Error on my Z370 may help solve other ACPI issues.
`0x000000A5 (0X00000011,0X00000008,0XF6F84218,0X20160422)`
Thank you!

#2895

daniel_k

> Zitat von ⇗ schreiberstein im Beitrag ¶ #2891

> By the way, how does the limit of ~900MB come about? What is reserving so much memory?
> I am considering creating a Server 2003 ISO to check if the behavior is similar to XP. Maybe 2003 works better. I always had a high opinion of it.
> Is there any chance the acpi.sys is compatible with Windows 2000 SP4 (NT 5.0)?
> Cheers,
> schreiberstein

Being a premium motherboard, it has too many onboard devices, that explains the "no enough free resources" and just 900MB of available RAM on XP.
Remember that those modern systems are optimized for new OSes, which handle resources differently.
Try Server 2003 Enterprise or Datacenter, as the Standard doesn't support PAE without hacking it, may help with the RAM, but I highly doubt about it helping with the lack of resources.

## Page 194

#2896

diderius6

⇗ @XPLives
The BSOD A5 (0x11,..) can have a lot of different reasons.
This new acpi.sys (see post) solves 50% of them. This is the best acpi.sys for now, that we have for XP SP3 (any compi).
If you get after this acpi.sys BSOD A5 (0x2001,..) it is another serious problem, because then there is a major other reason, why this compi cant enable Acpi mode (and even not MPS Multiprocessor mode without any Acpi)
Dietmar
diderius6 has attached files to this post

- ⇗ acpi.rar

#2897

XPLives

⇗ @infuscomus,⇗ @schreiberstein

> Zitat von ⇗ infuscomus im Beitrag ¶ #2892

> I may be wrong about this, but I believe Microsoft introduced an artificial limit to RAM in SP1 or SP2 because badly programmed device drivers did not handle 4GB of RAM properly.
> I think XP SP0 has access to all 4GB of RAM.
> so I doubt it's ever going to work

4.00GB of RAM for XP SP0/SP1
compared to
3.15GB of RAM on SP2/SP3.

> Zitat von ⇗ infuscomus im Beitrag ¶ #2892

> Check the hal.dll and ntoskrnl.exe of Windows 2000 SP4 with dependency walker and see if patched acpi 5048 has any missing imported functions, if it's all green and no red then it should work.
> edit:
> ntoskrnl 2000 missing
> InterlockedPopEntrySList
> InterlockedPushEntrySList
> HeadlessDispatch
> ExfInterlockedCompareExchange64

Maybe you can find a dependency substitution/workaround?
BlackWingCat team up?

> Zitat von ⇗ schreiberstein im Beitrag ¶ #2891

> By the way, how does the limit of ~900MB come about? What is reserving so much memory?
> I am considering creating a Server 2003 ISO to check if the behavior is similar to XP. Maybe 2003 works better. I always had a high opinion of it.
> Is there any chance the acpi.sys is compatible with Windows 2000 SP4 (NT 5.0)?
> Cheers,
> schreiberstein

900MB free OS Base Memory? Most likely due to integrated Intel HD Graphics Shared Memory Setting hogging it. If it is set to Auto it will use up to 2.5GB in some cases.
Go to your BIOS and look for the option to adjust the Shared Video Memory to the lowest possible. On Ivy Bridge you can go down to 32MB. On Coffee Lake I think they increased it to like 128MB minimum so it hogs more but at least better than 1.5GB->2.5GB default. If I knew how to BIOS Mod and change the Shared Memory setting I would change it to 32MB minimum since there is no XP driver support so any more memory is stolen from XP is completely wasted. You cannot increase the OS base memory > 4.00GB. Only Server 2003 can allow better OS memory utilization. This is why I do not trust those XP memory hacks for 128GB. I do not know what side effects can happen or how they modified and if it is safe. One time I heard someone's USB hard drive got corrupted.
But since you plan on using GTX 780 for GPU for Hackintosh/XP then you should change the Shared Memory setting down to the lowest possible in BIOS to prevent XP from getting robbed of OS Base Memory to use.
Best memory I recorded was XP SP0/SP1 with PAE 4.00GB claimed.
I think even with Intel HD Graphics Shared Memory usage it doesn't affect it because XP can utilize up to 4.00GB so as long as it stays within that range it is not robbed. XP SP2/SP3 stopped that and made it worse. Otherwise even XP probably could use up to 2.0GB -> 4.0GB? max shared memory on Intel HD Graphics 4000 and have 4.00GB free on SP0/SP1 as long as you had 8GB installed then you'd have 4.00GB for OS base memory and 4.00GB for Intel HD Graphics 4000 Shared Memory. Would be the best integrated graphics usage for XP if BIOS Modded option to add up to 4.00GB Shared Memory.
That was one reason I was testing XP SP0 Slim for smaller footprint install size and most OS memory available. This can be as low as 21.25% extra memory which is about 1/5 bonus. (4.00GB vs 3.15GB->3.21GB) typically in SP0/1 vs SP2/SP3.
Only issue is less compatibility with some programs that want SP2/SP3. Otherwise the best option is to jump to Server 2003 instead and utilize all memory up to 64.0GB for 32-Bit. or > 64GB for 64-Bit.
It is unlikely Windows Vista Beta ACPI will work on Windows 2000. I tested before Windows XP SP0 ACPI on Windows 2000 SP4 and it BSOD. So missing dependencies for backward compatibility. Somehow Vista Beta ACPI is probably XP compatible and not changed enough to cause a problem. ACPI.sys is only forward compatible. XP ACPI.sys works on 2003. 2000 ACPI.sys also worked on both XP and 2003. That is why before I asked if anyone knew how to modify Windows 2000 ACPI then it will work for all three Operating systems with full ACPI due to forward compatibility.

#2898

XPLives

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #2896

> @XPLives
> The BSOD A5 (0x11,..) can have a lot of different reasons.
> This new acpi.sys (see post) solves 50% of them. This is the best acpi.sys for now, that we have for XP SP3 (any compi).
> If you get after this acpi.sys BSOD A5 (0x2001,..) it is another serious problem, because then there is a major other reason, why this compi cant enable Acpi mode (and even not MPS Multiprocessor mode without any Acpi)
> Dietmar

That BSOD A5 was using default 32-Bit 2003 ACPI.SYS UnModded on Z370 UnModded BIOS. I thought maybe useful to know if this was different BSOD A5 error than other Z370 or Z390 people tested to compare.
No BSOD so far with recent Daniel_K Z390 ACPI.SYS mod. Seems very stable.
So far Shutdown works normal. Restart always works in ACPI/NO ACPI.
I just now test Stand By Mode for 1 minute and try to wake.
Update:
Ooops... Okay I found out Stand By mode cannot wake up properly.
PS/2 Keyboard - No Effect.
USB Mouse - No Effect.
Power On Button - Turns on but Black Screen and no return to XP Desktop. So I guess this is a FAIL for ACPI feature. But I am glad Shutdown does work however.
Only main issues with Audio playing in MAME games and possibly some DirectX9 titles like Crysis 1 and others like it could happen.
That same issue existed on the earlier Daniel_K Z390 64-Bit (XP/2003) ACPI.SYS mod.
Now DK's recent 32-Bit version matches the 64-Bit version and now I can finally see the Video Card in Device Manager which could not before with earlier ACPI.SYS mods I tested from here.
So it is a huge breakthrough for XP/2003 32-Bit ACPI on 10-10-19.
I think it is very close to getting to 100% without BIOS mod. I say 80% but maybe I am too optimistic.
So far if the Audio problems can be fixed then I can test further any other strange anomalies/bugs to be found.
You should try the Daniel_K Z390 ACPI.SYS MOD with Standard Flashed UnModded Factory BIOS to see if this happens on your Z390 EVGA Dark?
Does EVGA Dark Z390 work fine without any BIOS MOD or ACPI.SYS Mod already from default?
Is your ACPI.SYS attachment different than Daniel_K version? Maybe you can merge both together if yours fixes Stand By and Audio problem?

#2899

skullteria

> Zitat von ⇗ daniel_k im Beitrag ¶ #2858

> Patched ACPI.SYS files now supporting Z390 boards.

Hey my friend, this version of ACPI already is patched to fix winload.exe load Windows XP? Can you test with x64 too?

#2900

XPLives

⇗ @schreiberstein

> Zitat von ⇗ schreiberstein im Beitrag ¶ #2883

> @diderius6
> Which devices do you mean?
> I disabled all Other Devices I do not need (NVMe drives, wifi, bluetooth, etc)
> Sometimes, USB works. I even got USB sound.
> But after a reboot, USB is yellow again...
> Is there something I can disable under System devices to free up ressources?
> It is strange.

Wow you should go into F8 Safe Mode and see if those are still present. Delete the duplicates and reboot back to normal desktop to see if they went away. That should clear them and you will have new pop ups asking for install the driver. You can hold down the ESC key to bypass all the windows and check the Device Manager again any change. Should remove any duplicates.
Hey anyone else see this device in their Device Manager on Z370 or Z390?
"PCI Data Acquisition and Signal Processing Controller"?
Schreiberstein can you go into Details and Get a Text Copy of all the Hardware IDs for each category of that device?
Device Instance ID:
Hardware IDs:
Compatible IDs:
Matching Device ID:
I am curious what this device is as it has never shown before on any Intel system I have.

#2901

tarsonis

Any advice on this?

> Zitat von ⇗ tarsonis im Beitrag ¶ #2893

> > Zitat von ⇗ diderius6 im Beitrag ¶ #2820

> > @tarsonis
> > Most easy is to use from commandline
> > makecab acpi.sys
> > this gives you acpi.sy_
> > This you put to i386 folder for nlite to make CD XP SP3.
> > The same for storport.sys.
> > Then you integrate Txtmode via nlite driver STORAHCI from @skullteria .
> > No need to integrate USB files if you have a PS/2 connector
> > Dietmar

> So I did it wrong putting the *.sy_ after nlite finalize the setup files? The *.sy_ files need to be put in the XP folder before one selects it as source for nlite?
> The storport.sys file that is included in the STORAHCI driver from @skullteria is the correct one?
> Do I need to select a processor type (F7) for the setup and is "ACPI Multiprocessor" correct for the Ryzen 1800x?
> I have no PS/2 connector on the CH6 x370.

#2902

XPLives

⇗ @schreiberstein

> Zitat von ⇗ schreiberstein im Beitrag ¶ #2879

> EDIT:
> I was able to get the Intel I211 ethernet NIC (8086:1539) running with a driver I found here somewhere.
> Connection established, ping works. Amazing. A bit of relief.

Can you upload this Intel I211 ethernet NIC XP driver? I want to test it if you can ping that's amazing and sounds like it is working.

#2903 | diderius6 | ⇗ @skullteria I just make this in acpi.sys from post ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (194) Dietmar

#2904

schreiberstein

⇗ @XPLives
I can sure do that. I am sure I got them from somewhere around here.
I will look for them later today.
Very interesting results regarding missing dependencies for 2000 SP4. Maybe this will be possible someday. I have no experience with Windows Kernel hacking.
Right now, I am creating a Server 2003 i386 Enterprise ISO file for my system, but I am at a loss how to create the SP2.cab file using makecab.exe . :-(
I cannot find an example anywhere on the internet, even though I suppose tools like nLite use them internally.
From what I read, there are certain headers in these files and perhaps the XP setup expects something specific.
It could be possible that 2003 works much better than XP on my system.
Once I am home, I will also install the GeForce 780 in there.
I will keep you all posted.
Cheers,
schreiberstein
EDIT: The driver I used (found somewhere in this thread):
f45t4093p64633n2_tjinwYpq.rar
---> Original link: ⇗ https://files.homepagemodules.de/b602300...n2_tjinwYpq.rar
Contains "i211lan"
The driver works 100%. Gigabit full-duplex negotiated, Internet Explorer 6 worked, ...

#2905

Doc.Brown

> Zitat von ⇗ Doc.Brown im Beitrag ¶ #2847

> > Zitat von ⇗ diderius6 im Beitrag ¶ #2844

> > @Doc.Brown
> > Waaoh, that means I found exact the place for BSOD 0x10006 in DSDT and repair it there.
> > So much good news today!!! Now XP will run on ALL x390 boards, Apex XI and so on with this mod.
> > Last days I compare soso many DSDTs. And they are all the same. Manufacturers deleted important information in DSDT
> > and because of that XP crashes. XP works very strict in translating DSDT.
> > The problem with second acpi Bsod is,
> > that crazy XP just reinstalls its own original acpi.sys in windows\system32^^.
> > Just copy modded acpi.sys there again.
> > The other Bsod happens,
> > because XP does not like a device on the gene XI board.
> > Sometimes you can overcome this hitting F8 (Safe Mode).
> > Try to disable as much devices as you can in Bios. Later you can activate them again.
> > If this does not help,
> > use an XP install from another compi,
> > Dietmar
> > PS: With lan Debug from @Mov AX, 0xDEAD we now can find the device, which crashes.

> Yep it's a really good news being able to go forward in the installation process,you make it happen :)
> I already tried F8 for Safe Mode and it also result in BSOD unfortunately
> I try to copy ACPI.sys and a fresh install on X299 Rampage Apex(I already have a ghost of previous test) tomorrow ;)

⇗ @diderius6
New update from my investigation today:
I copy last Z390 ACPI.sys in System32/drivers after installation error from yesterday but installation restart always at this point(device installation) so bug comes again and again
After that I used a ghost made before on X299 with older acpi5048,changed for last Z390 ACPI.sys in windows directory and was able to boot (only) in Safe Mode,under XP some drivers like USB and AHCI A352 by Fernando pop-up for instal,in the end only one driver doesn't instal properly and it linked with ACPI as you can see on those capture:
⇗
⇗
Don't know if it could help
After that I tried a fresh instal on X299 with last Z390 acpi.sys but when I switch on Gene I've got 7B BSOD this time
⇗
Tried also lot of combination for build the iso but instal process always stop same as yesterday,I think there's something deeper again with this board cause I disabled all useless device in bios(audio,lan ...).
Thanks for your help :)

#2906

diderius6

⇗ @Doc.Brown
This can be solved, I have done.
But you need other compi and from there integrate the *.reg files
for the STORAHCI.sys driver into the registry of your new XP made X299.
Take also a look, if storport.sys is still in windows\system32\drivers
Dietmar
PS: You also can integrate the STORAHCI driver direct on X299 registry.
Copy STORAHCI.sys into windows\system32\drivers on running x299 compi,
storport.sys in windows\system32\drivers
and click just on the storahci.reg file from this post
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (59)

#2907

daniel_k

⇗ @schreiberstein, to build SP2.cab
Unpack original to C:\SP2 and replace desired files.
Extract attached file to the same folder.
Open a command prompt, switch to C:\SP2 and type:

    makecab /f sp2.ddf

Cabinet will be created as C:\SP2\CAB\SP2.CAB
Makecab is available from Vista and later.

#2908

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #2906

> @Doc.Brown
> This can be solved, I have done.
> But you need other compi and from there integrate the *.reg files
> for the STORAHCI.sys driver into the registry of your new XP made X299.
> Take also a look, if storport.sys is still in windows\system32
> Dietmar
> PS: You also can integrate the STORAHCI driver direct on X299 registry.
> Copy STORAHCI.sys into windows\system32\drivers on running x299 compi,
> storport.sys in windows\system32
> and click just on the storahci.reg file from this post
> ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (59)

I already integrate these via Nlite during iso build process but ok I try it from my previous x299 ghost ;)
Thanks

#2909 | diderius6 | ⇗ @Doc.Brown Then I think, storport.sys isnt any more in windows\system32\drivers Dietmar

#2910

Mikedebian

I have a question about GPU. Now that I have XP running I also gave some legacy dos apps that require full screen and cannot be run in a window. If window, it renders fine. If full screen the screen is black. I suspect this might have to do with my GPU in XP having no driver installed (it just works TM). I heard that the latest that was fully supported in XP is the 980Ti. This would solve my desktop being accelerated, but would it also sole full screen legacy apps not working? I tried to replace the videoer.sys, but that just resulted in a blue screen one XP started up and tried to render the login window.
Thank you... I would very very much like help with this.

## Page 195

#2911 | XPWELL64 | I'll hack Windows XP and Windows Vista drivers.
#2912 | XPWELL64 | Other people are hacking Win7 drivers. We will hack Windows Vista Drivers.

#2913

schreiberstein

I wish there were a way to get the Radeon RX 580 working on Windows XP.
But I doubt that the Radeon HD 7xxx drivers can be patched to make it working.
Else, these Linux kernel folks wouldnt have had such a hard time implementing all the changes with every new GPU generation, especially concerning powersaving, firmware blobs, etc.
Maybe I will try a PCI ID transplant sometime.

#2914 | XPWELL64 | I will patch ivy bridge drivers to work Intel HD 5500 on Windows Vista. I will patch igdkmd64.sys to do this.
#2915 | XPWELL64 | I will learn how to use ida pro and I will patch drivers.

#2916

tarsonis

OK, I made a new XP setup iso and tested it again. This time I've overwritten the acpi.sy_ and storport.sy_ before I started the nlite processing..
selecting "Standard PC":
1.Try = "the file STORAHCI.sys" is corrupted."
2.Try= 7B error
selecting "MPS Multiprocessor"
1.Try = Freeze on setup is loading dialog
selecting "AHCI Multiprocessor"
1.Try= 7B error
I have found that one needs to replace those files also in the SP3.cab too is it right? I have no SP3.cab in the setup files. But a driver.cab. Should I replace the acpi.sys and storport.sys in the driver.cab too?

#2917

skullteria

> Zitat von ⇗ tarsonis im Beitrag ¶ #2916

> OK, I made a new XP setup iso and tested it again. This time I've overwritten the acpi.sy_ and storport.sy_ before I started the nlite processing..
> selecting "Standard PC":
> 1.Try = "the file STORAHCI.sys" is corrupted."
> 2.Try= 7B error
> selecting "MPS Multiprocessor"
> 1.Try = Freeze on setup is loading dialog
> selecting "AHCI Multiprocessor"
> 1.Try= 7B error
> I have found that one needs to replace those files also in the SP3.cab too is it right? I have no SP3.cab in the setup files. But a driver.cab. Should I replace the acpi.sys and storport.sys in the driver.cab too?

Its seem or really storachi is corrupted or storport is missing.

#2918

Doc.Brown

⇗ @diderius6
So I tried what you told me under the x299 for Storahci,storport and the reg file,first boot after switching under the Z390 I had to replace the acpi.sys cause I had BSOD for non ACPI compliant bios and after replaced it by the last acpi5048 I had like yesterday :
⇗
This is for normal boot,Safe Boot is OK but always the same Microsoft ACPI Compliant Controller wich Install Manager ask to install,perhaps it's because of the replacement of acpi.sys after installation process don't you think ? If I install XP under X299 with a patched SP3.cab with the good acpi.sys into perhaps I will not have to replace it after switching on Z390 ?
I tried many things again like mode diag,maxmem or pci lock for nothing but this time I saw desktop for 10 secondes before BSOD many times.
Another thing that seems strange is that after switching on z390 and boot in Safe Mode the device manager always have the Intel 7740X listed and not the 8700K ...

#2919 | diderius6 | ⇗ @Doc.Brown Disable in Bios nearly everything. Disable via F8 Safe Mode in Device Manager nearly everything. Then boot with F8 and chose there VGA Dietmar
#2920 | dencorso | ⇗ @schreiberstein: Since you're using a 16-thread processor, you should be running hal.dll v. 5.1.2600.5687... In case you're not, do install 1st ⇗ https://web.archive.org/web/201612291648...en-us/kb/951126 and then ⇗ https://web.archive.org/web/201004240853...t.com/kb/958244 or just the latter. I do have the ENU hotfixes but not the DEU ones, but I'm confident you can find them easily. If not, let me know, and I'll help you locate them.

#2921

Andalu

> Zitat von ⇗ infuscomus im Beitrag ¶ #2890

> @Andalu
> just a suggestion, try doing a fresh install with the RAM patch?
> I have had better luck getting the RAM patch to work by nlite-ing it into an ISO and doing a fresh install than trying to patch an existing install.

So did you apply the patch successfully? Which one did you use?
I didn't have the same luck even with a fresh XP install and the Dibya's patch slipstreamed with nLite. This time the XP boot is completed but as soon as the amd usb3 drivers are installed the mouse attached to usb2 port hangs and the usb3 ports don't recognize the devices. Even the shutdown no longer works.
I don't know what else to try...

#2922 | daniel_k | ⇗ @Doc.Brown, desktop boards usually have very similar DSDT tables. Are you still running diderius6's modded BIOS? I think you should try to flash a stock, original BIOS from ASUS. Sometimes diderius6's changes may conflict with my patched ACPI.SYS.
#2923 | infuscomus | ⇗ @Andalu there are USB drivers included in dibya's archive, try replacing them in c:\windows\system32\drivers with dibya's versions
#2924 | infuscomus | ⇗ @dencorso can i get a copy of that hotfix for hal.dll?

#2925

Andalu

> Zitat von ⇗ infuscomus im Beitrag ¶ #2923

> @Andalu
> there are USB drivers included in dibya's archive, try replacing them in c:\windows\system32\drivers with dibya's versions

I had already replaced those files, no results

## Page 196

#2926

IntiMD

> Zitat von ⇗ infuscomus im Beitrag ¶ #2924

> can i get a copy of that hotfix for hal.dll?

⇗ KB951126
⇗ KB958244

#2927

lsmlcx

I make a new amd modded driver for intel xhci for xp.
It looks like it works better.

lsmlcx has attached files to this post

- ⇗ AMD_XHCI_For_Intel_XP_x86_x64_20191012.zip

#2928 | infuscomus | ⇗ @lsmlcx what changes did you make to it?
#2929 | lsmlcx | ⇗ @infuscomus I saw the previous driver, you changed to Jump 7812, 7814, 7914 on the AMD's 1022 ID, and then no judgment. Total three places. I now jump directly to the 7812, 7814, 7914 where the 1022 detection is detected.

#2930

infuscomus

⇗ @Andalu
try this,
copy ntkr128g.exe and hal128g.dll to c:\windows\system32
make a backup of original boot.ini
replace boot.ini contents with paeboot.ini contents
hopefully this works
infuscomus has attached files to this post

- ⇗ Windows_XP_128GB_double_pae_addon_final_byDibya.7z.zip

#2931

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #2919

> @Doc.Brown
> Disable in Bios nearly everything.
> Disable via F8 Safe Mode in Device Manager nearly everything.
> Then boot with F8 and chose there VGA
> Dietmar

Ok ⇗ @diderius6 I will try this,thanks for the tips ;)

> Zitat von ⇗ daniel_k im Beitrag ¶ #2922

> @Doc.Brown, desktop boards usually have very similar DSDT tables.
> Are you still running diderius6's modded BIOS? I think you should try to flash a stock, original BIOS from ASUS.
> Sometimes diderius6's changes may conflict with my patched ACPI.SYS.

⇗ @daniel_k yep I'm still using modded bios cause for now it's better than stock with your previous acpi5048(remove BSOD before disk scan for install) BUT I didn't try with your last ACPI patched for Z390,I have to test that also ^^
For now I'm trying to adapt your sp2.ddf file to change acpi.sys in my SP3.cab and make the cab,so I compare file names,remove those aren't in SP3.cab and add missing ones.

#2932

diderius6

⇗ @Doc.Brown
I succeed to simulate your BSOD.
About 10 seconds is XP there and then the BSOD with your number.
This I never had before.
It seems to happen, when the Fernando iastor.sys and the Skullteria STORAHCI.sys comes in conflict.
One starts the harddisk and then the other gets loaded also, which gives BSOD
Dietmar
⇗

#2933 | XPWELL64 | Today, I'm modding Intel HD Graphics for Windows XP. I found important string in igxpmp32.sys. I found some infos about Intel HD Graphics for Haswell .sys in IDA Pro.
#2934 | XPWELL64 | There is a "Haswell Mobile Graphics Controller" function in .sys

#2935

schreiberstein

I was busy tinkering with the system yesterday - here are my findings so far:
(I inserted a GeForce GTX 780 to act as a second GPU, selected it to be primary in BIOS. It works properly. The XP nVidia driver picks it up)
--> I created my own installation media for Windows Server 2003 R2 x86 Enterprise
-> Integrated acpi.sys into SP2.cab
-> Integrated AHCI, LAN, USB and USB HUB driver (split the package into two directories so Winfuture Iso Builder would not complain about the directory being 'included twice')
-> Installation went flawlessly
-> Server 2003 has PAE enabled and allows me to use ~31.1 GB (some odd number) of RAM
-> USB never worked once. Not even when I manually installed the INFs from the original package again. It only detects two Intel XHCI 3.1 controllers, not the long list of controllers.
-> Was unable to install nVidia Drivers due to .NetFramework bloat not being able to downloaded automatically by its stupid installer
-> Was able to extract it and installed the nv4_display.inf instead
-> Direct3D did not work, probably something Server 2003 related
-> NTVDM (16 Bit applications such as edit.com) works, also with nVidia drivers enabled
-> Reboot and shutdown always worked
I installed the unoffical SP4 for Windows XP as well to make sure some of this machine's issues is not caused by the lack of Windows updates
However, there are some pretty serious flaws right now:
-> The system just not feels right. Some things hang for a second.
-> NTVDM does not work for some reason - trying to execute edit.com does nothing - just if I had pressed ENTER in the prompt. The 1990s game installers I tried were unable to run because of that - Event viewer showed this:The application, C:\WINDOWS\system32\ntvdm.exe, generated an application error The error occurred on 10/11/2019 @ 17:20:09.312 The exception generated was c0000094 at address 0F01759D (ntvdm!RegisterWOWIdle)
- USB works on every third boot attempt on Windows XP
- No modern web browser works: Chromium 54, Firefox ESR, Palemoon open, I can type something and then the changes to the text will not be visible after a few keystrokes. Sometimes I can see a page, but the UI is broked. The application never crashes or shows an error. I can quit the application any time pressing X. No unresponsiveness. Chromium wrote nothing suspicious into its debug log (started it with special parameters). It seems like the window simply stops redrawing itself. Nothing suspicious in event viewer either.
- "Modern" XP DirectX 9 XP games seem to work, however it feels like the system has some minor micro stuttering, but this might be due to the game, I don't know.
- In case USB was not detected properly, shutdown and reboot will not work. The system simply HALTS there.
- My Athlon 64 939 system from 2005 feels more responsive and "BOOM" for some reason, despite having a quadruple times less "BOOM" when it comes to clock and bus speeds.
- Deactivating devices in Device Manager does not seem to make a difference - I suspect this one, exclamation-marked yellow PCI bridge with "Not enough resources" is to blame.
- Executing AIDA32 system profiler hangs the entire system when it says "Reading MSR" or something like that.
---> I am looking for a tool like HWINFO that allows me to export all the device information so I can share them here
Btw. It seems like only Windows 10 works flawlessly on this machine. (yet)
I installed the modified Intel Z390 USB drivers on my Windows 7 x64 test system and they worked.
The graphics "hang" with the ATI card when it is a bit busy. Like stuttering, Aero effects hanging. And then the mouse (PS/2 and USB) will not be very responsive, like on a system in VESA mode when too many interrupts are fired.
Source: ⇗ [Solution] Win7 drivers for USB 3.0/3.1 Controllers of new Intel chipset systems
At least USB worked on every boot in Windows 7.
Overall, I am very disappointed at Intel/the industry for not caring about backwards compatibility. Not even for Windows 7.
It is bizzare that Apple Mac OS X works better and faster on this system than any version of Microsoft Windows.
Cheers,
schreiberstein

#2936 | diderius6 | ⇗ @Doc.Brown May be, it is the fault of the iastor.sys driver version 11.2.0.1006 for Intel. Ask ⇗ @daniel_k which driver is best for Intel AHCI now Dietmar

#2937

IntiMD

⇗ @Doc.Brown
FYI here are the Intel RSTe driver backports for XP by daniel_k
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (110) - RSTe 4.6.0.1085 x86
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (118) - RSTe 4.6.0.1085 x64
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (115) - RSTe 4.7.0.1098 x86
For x86 NT5.2 systems, you might want to comment out the following entries just like this:

    [SourceDisksFiles.x86]
    iaStorA.sys = 1,,,
    iaStorF.sys = 1,,,
    ; storport.sys = 1,,,
    ;

and

    [iaStorA_inst.ntx86]
    CopyFiles=@iaStorA.sys
    CopyFiles=@iaStorF.sys
    ; CopyFiles=@storport.sys
    ;

PS. forgot to mention, they don't contain the TXTSETUP.OEM file, so you can't slipstream it in first stage text setup.

#2938

diderius6

⇗ @Doc.Brown
I set up a Windbg session for this BSOD.
The BSOD goes to acpi.sys.
A device, which is loaded late in bootprocess is not ACPI compatible.
And because of this, during first install, you get the 10 sec with full ACPI XP,
because this device is not yet installed from XP SP3 from other compi.
When it goes installed, you get this BSOD.
And this device does not start in Safe Mode (F8),
and because of this you do not get BSOD there
Dietmar
PS: It is not iastor.sys, it is not STORAHCI,
just another device, which I do not found until now,
even I disabled in Bios and via Device Manager really ALL.
Here is the debug printout, with its help we will find the reason:))

    nt!IoInvalidateDeviceRelations+9
    80a2b5e1 8b86b0000000 mov eax,dword ptr [esi+0B0h]

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Opened \\.\com1
    Waiting to reconnect...
    Connected to Windows XP 2600 x86 compatible target at (Sat Oct 12 17:10:30.031 2019 (UTC + 2:00)), ptr64 FALSE
    Kernel Debugger connection established.
    WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
    Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
    *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
    Executable search path is: C:\localsymbols
    Windows XP Kernel Version 2600 MP (1 procs) Checked x86 compatible
    Built by: 2600.xpsp.080413-2133
    Machine Name:
    Kernel base = 0x80a02000 PsLoadedModuleList = 0x80af5708
    System Uptime: not available
    WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
    Sat
     Oct 12 17:10:32.296 2019 (UTC + 2:00): MM: Loader/HAL memory block
    indicates large pages cannot be used for 80A02000->80D8DFFF
    Sat Oct 12 17:10:32.296 2019 (UTC + 2:00):
    Sat
     Oct 12 17:10:32.312 2019 (UTC + 2:00): MM: Loader/HAL memory block
    indicates large pages cannot be used for 80100000->8012777F
    Sat Oct 12 17:10:32.312 2019 (UTC + 2:00):
    Sat
     Oct 12 17:10:32.328 2019 (UTC + 2:00): MM: Loader/HAL memory block
    indicates large pages cannot be used for 81D43000->82A93FFF
    Sat Oct 12 17:10:32.328 2019 (UTC + 2:00):
    Sat Oct 12 17:10:32.343 2019 (UTC + 2:00): MM: Disabling large pages for all ranges due to overlap
    Sat Oct 12 17:10:37.656 2019 (UTC + 2:00):

    Intel Storage Driver Ver: 11.2.0.1006

    Sat Oct 12 17:10:48.078 2019 (UTC + 2:00): MM:***PAGE FAULT AT IRQL > 1  Va 000000B0, IRQL 2
    Sat Oct 12 17:10:48.078 2019 (UTC + 2:00):
    Sat Oct 12 17:10:48.109 2019 (UTC + 2:00): MM:***EIP 80A2B5E1, EFL 00010246
    Sat Oct 12 17:10:48.109 2019 (UTC + 2:00):
    Sat Oct 12 17:10:48.125 2019 (UTC + 2:00): MM:***EAX 2000010A, ECX 00806400 EDX 00806400
    Sat Oct 12 17:10:48.125 2019 (UTC + 2:00):
    Sat Oct 12 17:10:48.140 2019 (UTC + 2:00): MM:***EBX F7592840, ESI 00000000 EDI 00000400
    Sat Oct 12 17:10:48.140 2019 (UTC + 2:00):
    Sat Oct 12 17:10:48.171 2019 (UTC + 2:00):
    *** Fatal System Error: 0x0000000a
                                                 (0x000000B0,0x00000002,0x00000000,0x80A2B5E1)

    Sat Oct 12 17:10:48.203 2019 (UTC + 2:00): Break instruction exception - code 80000003 (first chance)

    A fatal system error has occurred.
    Debugger entered on first try; Bugcheck callbacks have not been invoked.

    A fatal system error has occurred.

    Connected to Windows XP 2600 x86 compatible target at (Sat Oct 12 17:10:48.328 2019 (UTC + 2:00)), ptr64 FALSE
    Loading Kernel Symbols
    .........................................
    Loading User Symbols

    Loading unloaded module list
    ..
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {b0, 2, 0, 80a2b5e1}

    *** ERROR: Module load completed but symbols could not be loaded for ACPI.sys
    Probably caused by : ACPI.sys ( ACPI+1142e )

    Followup: MachineOwner
    ---------

    nt!RtlpBreakWithStatusInstruction:
    80ab9138 cc              int     3
    2: kd> lm
    start    end        module name
    80100000 80127780   hal        (deferred)
    80a02000 80d8e000   nt         (pdb symbols)          c:\symbols\ntkrnlmp.pdb\23BD599C4BEE49C0B7E2E3FD595D2ACB1\ntkrnlmp.pdb
    b57d9000 b5836f00   update     (deferred)
    b6922000 b6944700   ks         (deferred)
    b6c89000 b6cb8e80   rdpdr      (deferred)
    b6cb9000 b6ce1000   HDAudBus   (deferred)
    b6ce1000 b6cf4f00   VIDEOPRT   (deferred)
    b6cf5000 b7956bc0   nv4_mini   (deferred)
    b7bff000 b7c02c80   mssmbios   (pdb symbols)          c:\symbols\mssmbios.pdb\9940673F3B9A4BD682DF9D96A12A355C1\mssmbios.pdb
    b83c3000 b83dce80   Mup        (deferred)
    b83dd000 b8409980   NDIS       (deferred)
    b840a000 b8496d00   Ntfs       (deferred)
    b8497000 b84a9f00   WudfPf     (deferred)
    b84aa000 b84c0b80   KSecDD     (deferred)
    b84c1000 b84d2f00   sr         (deferred)
    b84d3000 b84f2b00   fltMgr     (deferred)
    b84f3000 b8533000   storport   (deferred)
    b8533000 b854a880   SCSIPORT   (deferred)
    b854b000 b8800000   iaStor     (deferred)
    f7472000 f7497a00   dmio       (deferred)
    f7498000 f74b6d80   ftdisk     (deferred)
    f74f7000 f7500f00   termdd     (deferred)
    f7507000 f7510e00   intelppm   (deferred)
    f7517000 f7523f00   i8042prt   (deferred)
    f7557000 f7567a80   pci        (deferred)
    f7568000 f75a8000   ACPI       (no symbols)
    f75a8000 f75d6000   amdxhc     (deferred)
    f75f7000 f7600300   isapnp     (deferred)
    f7607000 f7611580   MountMgr   (deferred)
    f7617000 f7624200   VolSnap    (deferred)
    f7647000 f764fe00   disk       (deferred)
    f7657000 f7663180   CLASSPNP   (deferred)
    f7707000 f770d780   USBSTOR    (deferred)
    f770f000 f7713d00   PartMgr    (deferred)
    f77af000 f77b5280   kbdclass   (deferred)
    f77b7000 f77bcc00   mouclass   (deferred)
    f7897000 f789a000   BOOTVID    (deferred)
    f7987000 f7988b80   kdcom      (deferred)
    f7989000 f798a500   USBD       (deferred)
    f798b000 f798c100   WMILIB     (deferred)
    f798d000 f798e700   dmload     (deferred)
    f79bd000 f79be100   swenum     (deferred)

    Unloaded modules:
    f7637000 f7644000   storahci.sys
    f7627000 f7637000   asahci32.sys
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 000000b0, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 80a2b5e1, address which referenced memory

    Debugging Details:
    ------------------

    READ_ADDRESS:  000000b0

    CURRENT_IRQL:  2

    FAULTING_IP:
    nt!IoInvalidateDeviceRelations+9
    80a2b5e1 8b86b0000000    mov     eax,dword ptr [esi+0B0h]

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0xA

    PROCESS_NAME:  System

    TRAP_FRAME:  f78baeb8 -- (.trap 0xfffffffff78baeb8)
    ErrCode = 00000000
    eax=2000010a ebx=f7592840 ecx=00806400 edx=00806400 esi=00000000 edi=00000400
    eip=80a2b5e1 esp=f78baf2c ebp=f78baf30 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    nt!IoInvalidateDeviceRelations+0x9:
    80a2b5e1 8b86b0000000    mov     eax,dword ptr [esi+0B0h] ds:0023:000000b0=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 80a30d41 to 80ab9138

    STACK_TEXT:
    f78baa6c 80a30d41 00000003 f78badc8 00000000 nt!RtlpBreakWithStatusInstruction
    f78baab8 80a319ac 00000003 000000b0 80a2b5e1 nt!KiBugCheckDebugBreak+0x19
    f78bae98 80ad7b50 0000000a 000000b0 00000002 nt!KeBugCheck2+0x574
    f78bae98 80a2b5e1 0000000a 000000b0 00000002 nt!KiTrap0E+0x244
    f78baf30 f757942e 00000000 00000000 00000400 nt!IoInvalidateDeviceRelations+0x9
    WARNING: Stack unwind information not available. Following frames may be wrong.
    f78baf60 f7579541 8aa52d68 8a9fd268 f771f000 ACPI+0x1142e
    f78baf7c f756ed55 8aa52d68 8a994000 00000000 ACPI+0x11541
    f78baf9c f756f134 8a9fd268 f7592800 f78bafe0 ACPI+0x6d55
    f78bafb0 f756f4c2 f78bafc0 f771f9c0 8a9fd268 ACPI+0x7134
    f78bafc8 80ad9899 f75927a0 00000000 00000000 ACPI+0x74c2
    f78baff4 80ad937b f791ac54 00000000 00000000 nt!KiRetireDpcList+0x7e
    f78baff8 f791ac54 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
    80ad937b 00000000 00000009 0081850f bb830000 0xf791ac54

    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    ACPI+1142e
    f757942e eb06            jmp     ACPI+0x11436 (f7579436)

    SYMBOL_STACK_INDEX:  5

    SYMBOL_NAME:  ACPI+1142e

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: ACPI

    IMAGE_NAME:  ACPI.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  424d8208

    FAILURE_BUCKET_ID:  0xA_ACPI+1142e

    BUCKET_ID:  0xA_ACPI+1142e

    Followup: MachineOwner
    ---------

#2939

daniel_k

> Zitat von ⇗ schreiberstein im Beitrag ¶ #2935

> -> USB never worked once. Not even when I manually installed the INFs from the original package again. It only detects two Intel XHCI 3.1 controllers, not the long list of controllers.

What are the device IDs?

> Zitat

> -> Was unable to install nVidia Drivers due to .NetFramework bloat not being able to downloaded automatically by its stupid installer

But you can do a custom install, without GeForce Experience, skipping .NET install.

> Zitat

> -> Direct3D did not work, probably something Server 2003 related

For stability purposes, D3D and Dsound acceleration are disabled by default in all Server editions.
Just run Dxdiag and enable these features.

> Zitat von ⇗ schreiberstein im Beitrag ¶ #2935

> I installed the unoffical SP4 for Windows XP as well to make sure some of this machine's issues is not caused by the lack of Windows updates
> However, there are some pretty serious flaws right now:
> -> The system just not feels right. Some things hang for a second.

You seem to be suffering from the ACPI timer issue.
⇗ @diderius6, please help him.

#2940 | daniel_k | ⇗ @lsmlcx, there is nothing wrong with the driver. And the most important patch has nothing to do with device IDs checks.

## Page 197

#2941 | daniel_k | ⇗ @diderius6, AHCI drivers are only an issue if installing from USB: ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (178) From CD/DVD, no issues with any driver: ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (179)

#2942

diderius6

⇗ @daniel_k ⇗ @schreiberstein
The question is, what Schreiberstein (Alex?)
really wants. To get a working XP or Server 2003 or ..
Only step by step this can be done
Dietmar
PS: Here are the hacked hal.dll and intelppm.sys for XP SP3, which solve the timer problem.
diderius6 has attached files to this post

- ⇗ halplusintelppmXPSP3.rar

#2943 | diderius6 | ⇗ @daniel_k Yes, I see this. This is a brandnew, acpi.sys related error for a special, until now unknown device, BSOD 0x0000000a (0x000000B0,0x00000002,0x00000000, xxx) Dietmar

#2944

diderius6

Because in Safe Mode (F8) this BSOD does not happen,
it must be one of the excluded, following devices, because this are the ones, not loaded in Safe Mode.

    Sat Oct 12 17:35:41.812 2019 (UTC + 2:00): SAFEBOOT: skipping device = Cdrom.SYS(SCSI CDROM Class)
    Sat Oct 12 17:35:43.187 2019 (UTC + 2:00): SAFEBOOT: skipping device = mnmdd.SYS(Video Save)
    Sat Oct 12 17:35:43.187 2019 (UTC + 2:00):
    Sat Oct 12 17:35:43.203 2019 (UTC + 2:00): SAFEBOOT: skipping device = RDPCDD.SYS(Video Save)
    Sat Oct 12 17:35:43.578 2019 (UTC + 2:00): SAFEBOOT: skipping device = RasAcd.SYS(Streams Drivers)
    Sat Oct 12 17:35:43.578 2019 (UTC + 2:00):
    Sat Oct 12 17:35:43.609 2019 (UTC + 2:00): SAFEBOOT: skipping device = IPSec.SYS(PNP_TDI)
    Sat Oct 12 17:35:43.609 2019 (UTC + 2:00):
    Sat Oct 12 17:35:43.625 2019 (UTC + 2:00): SAFEBOOT: skipping device = Tcpip.SYS(PNP_TDI)
    Sat Oct 12 17:35:43.625 2019 (UTC + 2:00):
    Sat Oct 12 17:35:43.640 2019 (UTC + 2:00): SAFEBOOT: skipping device = NetBT.SYS(PNP_TDI)
    Sat Oct 12 17:35:43.640 2019 (UTC + 2:00):
    Sat Oct 12 17:35:43.656 2019 (UTC + 2:00): SAFEBOOT: skipping device = AFD.SYS(TDI)
    Sat Oct 12 17:35:43.656 2019 (UTC + 2:00):
    Sat Oct 12 17:35:43.687 2019 (UTC + 2:00): SAFEBOOT: skipping device = NetBIOS.SYS(NetBIOSGroup)
    Sat Oct 12 17:35:43.687 2019 (UTC + 2:00):
    Sat Oct 12 17:35:43.703 2019 (UTC + 2:00): SAFEBOOT: skipping device = Serial.SYS(Extended base)
    Sat Oct 12 17:35:43.703 2019 (UTC + 2:00):
    Sat Oct 12 17:35:43.718 2019 (UTC + 2:00): SAFEBOOT: skipping device = intelppm.SYS(Extended Base)
    Sat Oct 12 17:35:43.718 2019 (UTC + 2:00):
    Sat Oct 12 17:35:43.750 2019 (UTC + 2:00): SAFEBOOT: skipping device = WmiAcpi.SYS(Extended Base)
    Sat Oct 12 17:35:43.750 2019 (UTC + 2:00):
    Sat Oct 12 17:35:43.796 2019 (UTC + 2:00): SAFEBOOT: skipping device = WS2IFSL.SYS(Group)
    Sat Oct 12 17:35:44.296 2019 (UTC + 2:00): SAFEBOOT: skipping device = Rdbss.SYS(Network)
    Sat Oct 12 17:35:44.296 2019 (UTC + 2:00):
    Sat Oct 12 17:35:44.312 2019 (UTC + 2:00): SAFEBOOT: skipping device = MRxSmb.SYS(Network)
    Sat Oct 12 17:35:44.812 2019 (UTC + 2:00): SAFEBOOT: skipping device = Fips.SYS(Group)
    Sat Oct 12 17:35:44.812 2019 (UTC + 2:00):
    Sat Oct 12 17:35:44.828 2019 (UTC + 2:00): SAFEBOOT: skipping device = ElbyCDIO.SYS(Group)
    Sat Oct 12 17:35:50.046 2019 (UTC + 2:00): MiSessionWideReserveImageAddress: NO Code Sharing
     on \SystemRoot\System32\drivers\dxg.sys, Address 0xbd000000

Dietmar

#2945

schreiberstein

⇗ @daniel_k
⇗ @diderius6
I primarily wanted to try out Windows Server 2003 to check if it works better than Windows XP on this system, and what to expect from PAE mode.
I was able to get USB3 working using the modified AMD drivers.
The problem was... the INF files has NTx86.5.1.1 written all over them... I searched-and-replaced it to NTx86.5 (as Server 2003 is 5.2) and then it picked up all USB controllers properly. USB works more stable than on Windows XP. My mouse and keyboard always worked throughout several reboots, but my USB Audio DAC seems to have issues. Detecting, installing, deactivating, reinstalling itself, etc.
Also, it seems that the USB driver is responsible for killing NTVDM (16 Bit) support. After I installed the driver, edit.com stopped working.
My goal would be to have a working Windows XP system with more than ~900 MB RAM, stable USB and stable applications.
I do not need 2003.
I will try the modded HAL on my XP system shortly.
Direct3D works just fine on Windows Server 2003. I just had to enable it, I found out... and then somebody mentioned it here shortly before I composed this answer.
Thank you all.
Cheers,
Alexander (schreiberstein)

#2946

schreiberstein

⇗ @diderius6
Thank you so much!
I have just installed this patched HAL.dll and intelppm on my XP system and voila...
Guess which system I am using Google Chrome v54 on to post this...
This magically fixed all web browsers and some obscure game demos from 2005 that I attempted to run.
I am using the Geforce GTX 780 to drive my two 2560x1600 displays and it looks gorgeous - extended XP bliss desktop.
Now the main remaining issues for XP are USB, NTVDM crashing and the lack of RAM.
Could I use the aforementioned 128GB RAM patch, or will this cause issues with the (potentially) newer HAL.DLL ?
I will create a new XP installation media and do another clean install soon.
Cheers,
schreiberstein

#2947

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #2932

> @Doc.Brown
> I succeed to simulate your BSOD.
> About 10 seconds is XP there and then the BSOD with your number.
> This I never had before.
> It seems to happen, when the Fernando iastor.sys and the Skullteria STORAHCI.sys comes in conflict.
> One starts the harddisk and then the other gets loaded also, which gives BSOD
> Dietmar
> ⇗

This one(10 second desktop) comes only with XP previously installed with the X299 R6A and I build the iso with Fernando's latest drivers,the Storahci,AMDXHCI and Nvme one but the BSOD also come during device installation process in XP installation from the Z390 Gene.

> Zitat von ⇗ diderius6 im Beitrag ¶ #2936

> @Doc.Brown
> May be, it is the fault of the iastor.sys driver version 11.2.0.1006
> for Intel. Ask @daniel_k which driver is best for Intel AHCI now
> Dietmar

I already tried to build the iso wth only one driver by one and if I remembering well the "worse" case is with only the STORAHCItxtsetup,with it BSOD A5 is coming back

> Zitat von ⇗ diderius6 im Beitrag ¶ #2938

> @Doc.Brown
> I set up a Windbg session for this BSOD.
> The BSOD goes to acpi.sys.
> A device, which is loaded late in bootprocess is not ACPI compatible.
> And because of this, during first install, you get the 10 sec with full ACPI XP,
> because this device is not yet installed from XP SP3 from other compi.
> When it goes installed, you get this BSOD.
> And this device does not start in Safe Mode (F8),
> and because of this you do not get BSOD there
> Dietmar
> PS: It is not iastor.sys, it is not STORAHCI,
> just another device, which I do not found until now,
> even I disabled in Bios and via Device Manager really ALL.
> Here is the debug printout, with its help we will find the reason:))

>     nt!IoInvalidateDeviceRelations+9
>     80a2b5e1 8b86b0000000 mov eax,dword ptr [esi+0B0h]

>     Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
>     Copyright (c) Microsoft Corporation. All rights reserved.

>     Opened \\.\com1
>     Waiting to reconnect...
>     Connected to Windows XP 2600 x86 compatible target at (Sat Oct 12 17:10:30.031 2019 (UTC + 2:00)), ptr64 FALSE
>     Kernel Debugger connection established.
>     WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
>     Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
>     *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
>     Executable search path is: C:\localsymbols
>     Windows XP Kernel Version 2600 MP (1 procs) Checked x86 compatible
>     Built by: 2600.xpsp.080413-2133
>     Machine Name:
>     Kernel base = 0x80a02000 PsLoadedModuleList = 0x80af5708
>     System Uptime: not available
>     WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
>     Sat
>      Oct 12 17:10:32.296 2019 (UTC + 2:00): MM: Loader/HAL memory block
>     indicates large pages cannot be used for 80A02000->80D8DFFF
>     Sat Oct 12 17:10:32.296 2019 (UTC + 2:00):
>     Sat
>      Oct 12 17:10:32.312 2019 (UTC + 2:00): MM: Loader/HAL memory block
>     indicates large pages cannot be used for 80100000->8012777F
>     Sat Oct 12 17:10:32.312 2019 (UTC + 2:00):
>     Sat
>      Oct 12 17:10:32.328 2019 (UTC + 2:00): MM: Loader/HAL memory block
>     indicates large pages cannot be used for 81D43000->82A93FFF
>     Sat Oct 12 17:10:32.328 2019 (UTC + 2:00):
>     Sat Oct 12 17:10:32.343 2019 (UTC + 2:00): MM: Disabling large pages for all ranges due to overlap
>     Sat Oct 12 17:10:37.656 2019 (UTC + 2:00):

>     Intel Storage Driver Ver: 11.2.0.1006

>     Sat Oct 12 17:10:48.078 2019 (UTC + 2:00): MM:***PAGE FAULT AT IRQL > 1  Va 000000B0, IRQL 2
>     Sat Oct 12 17:10:48.078 2019 (UTC + 2:00):
>     Sat Oct 12 17:10:48.109 2019 (UTC + 2:00): MM:***EIP 80A2B5E1, EFL 00010246
>     Sat Oct 12 17:10:48.109 2019 (UTC + 2:00):
>     Sat Oct 12 17:10:48.125 2019 (UTC + 2:00): MM:***EAX 2000010A, ECX 00806400 EDX 00806400
>     Sat Oct 12 17:10:48.125 2019 (UTC + 2:00):
>     Sat Oct 12 17:10:48.140 2019 (UTC + 2:00): MM:***EBX F7592840, ESI 00000000 EDI 00000400
>     Sat Oct 12 17:10:48.140 2019 (UTC + 2:00):
>     Sat Oct 12 17:10:48.171 2019 (UTC + 2:00):
>     *** Fatal System Error: 0x0000000a
>                                                  (0x000000B0,0x00000002,0x00000000,0x80A2B5E1)

>     Sat Oct 12 17:10:48.203 2019 (UTC + 2:00): Break instruction exception - code 80000003 (first chance)

>     A fatal system error has occurred.
>     Debugger entered on first try; Bugcheck callbacks have not been invoked.

>     A fatal system error has occurred.

>     Connected to Windows XP 2600 x86 compatible target at (Sat Oct 12 17:10:48.328 2019 (UTC + 2:00)), ptr64 FALSE
>     Loading Kernel Symbols
>     .........................................
>     Loading User Symbols

>     Loading unloaded module list
>     ..
>     *******************************************************************************
>     *                                                                             *
>     *                        Bugcheck Analysis                                    *
>     *                                                                             *
>     *******************************************************************************

>     Use !analyze -v to get detailed debugging information.

>     BugCheck A, {b0, 2, 0, 80a2b5e1}

>     *** ERROR: Module load completed but symbols could not be loaded for ACPI.sys
>     Probably caused by : ACPI.sys ( ACPI+1142e )

>     Followup: MachineOwner
>     ---------

>     nt!RtlpBreakWithStatusInstruction:
>     80ab9138 cc              int     3
>     2: kd> lm
>     start    end        module name
>     80100000 80127780   hal        (deferred)
>     80a02000 80d8e000   nt         (pdb symbols)          c:\symbols\ntkrnlmp.pdb\23BD599C4BEE49C0B7E2E3FD595D2ACB1\ntkrnlmp.pdb
>     b57d9000 b5836f00   update     (deferred)
>     b6922000 b6944700   ks         (deferred)
>     b6c89000 b6cb8e80   rdpdr      (deferred)
>     b6cb9000 b6ce1000   HDAudBus   (deferred)
>     b6ce1000 b6cf4f00   VIDEOPRT   (deferred)
>     b6cf5000 b7956bc0   nv4_mini   (deferred)
>     b7bff000 b7c02c80   mssmbios   (pdb symbols)          c:\symbols\mssmbios.pdb\9940673F3B9A4BD682DF9D96A12A355C1\mssmbios.pdb
>     b83c3000 b83dce80   Mup        (deferred)
>     b83dd000 b8409980   NDIS       (deferred)
>     b840a000 b8496d00   Ntfs       (deferred)
>     b8497000 b84a9f00   WudfPf     (deferred)
>     b84aa000 b84c0b80   KSecDD     (deferred)
>     b84c1000 b84d2f00   sr         (deferred)
>     b84d3000 b84f2b00   fltMgr     (deferred)
>     b84f3000 b8533000   storport   (deferred)
>     b8533000 b854a880   SCSIPORT   (deferred)
>     b854b000 b8800000   iaStor     (deferred)
>     f7472000 f7497a00   dmio       (deferred)
>     f7498000 f74b6d80   ftdisk     (deferred)
>     f74f7000 f7500f00   termdd     (deferred)
>     f7507000 f7510e00   intelppm   (deferred)
>     f7517000 f7523f00   i8042prt   (deferred)
>     f7557000 f7567a80   pci        (deferred)
>     f7568000 f75a8000   ACPI       (no symbols)
>     f75a8000 f75d6000   amdxhc     (deferred)
>     f75f7000 f7600300   isapnp     (deferred)
>     f7607000 f7611580   MountMgr   (deferred)
>     f7617000 f7624200   VolSnap    (deferred)
>     f7647000 f764fe00   disk       (deferred)
>     f7657000 f7663180   CLASSPNP   (deferred)
>     f7707000 f770d780   USBSTOR    (deferred)
>     f770f000 f7713d00   PartMgr    (deferred)
>     f77af000 f77b5280   kbdclass   (deferred)
>     f77b7000 f77bcc00   mouclass   (deferred)
>     f7897000 f789a000   BOOTVID    (deferred)
>     f7987000 f7988b80   kdcom      (deferred)
>     f7989000 f798a500   USBD       (deferred)
>     f798b000 f798c100   WMILIB     (deferred)
>     f798d000 f798e700   dmload     (deferred)
>     f79bd000 f79be100   swenum     (deferred)

>     Unloaded modules:
>     f7637000 f7644000   storahci.sys
>     f7627000 f7637000   asahci32.sys
>     2: kd> !analyze -v
>     *******************************************************************************
>     *                                                                             *
>     *                        Bugcheck Analysis                                    *
>     *                                                                             *
>     *******************************************************************************

>     IRQL_NOT_LESS_OR_EQUAL (a)
>     An attempt was made to access a pageable (or completely invalid) address at an
>     interrupt request level (IRQL) that is too high.  This is usually
>     caused by drivers using improper addresses.
>     If a kernel debugger is available get the stack backtrace.
>     Arguments:
>     Arg1: 000000b0, memory referenced
>     Arg2: 00000002, IRQL
>     Arg3: 00000000, bitfield :
>     	bit 0 : value 0 = read operation, 1 = write operation
>     	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
>     Arg4: 80a2b5e1, address which referenced memory

>     Debugging Details:
>     ------------------

>     READ_ADDRESS:  000000b0

>     CURRENT_IRQL:  2

>     FAULTING_IP:
>     nt!IoInvalidateDeviceRelations+9
>     80a2b5e1 8b86b0000000    mov     eax,dword ptr [esi+0B0h]

>     DEFAULT_BUCKET_ID:  DRIVER_FAULT

>     BUGCHECK_STR:  0xA

>     PROCESS_NAME:  System

>     TRAP_FRAME:  f78baeb8 -- (.trap 0xfffffffff78baeb8)
>     ErrCode = 00000000
>     eax=2000010a ebx=f7592840 ecx=00806400 edx=00806400 esi=00000000 edi=00000400
>     eip=80a2b5e1 esp=f78baf2c ebp=f78baf30 iopl=0         nv up ei pl zr na pe nc
>     cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
>     nt!IoInvalidateDeviceRelations+0x9:
>     80a2b5e1 8b86b0000000    mov     eax,dword ptr [esi+0B0h] ds:0023:000000b0=????????
>     Resetting default scope

>     LAST_CONTROL_TRANSFER:  from 80a30d41 to 80ab9138

>     STACK_TEXT:
>     f78baa6c 80a30d41 00000003 f78badc8 00000000 nt!RtlpBreakWithStatusInstruction
>     f78baab8 80a319ac 00000003 000000b0 80a2b5e1 nt!KiBugCheckDebugBreak+0x19
>     f78bae98 80ad7b50 0000000a 000000b0 00000002 nt!KeBugCheck2+0x574
>     f78bae98 80a2b5e1 0000000a 000000b0 00000002 nt!KiTrap0E+0x244
>     f78baf30 f757942e 00000000 00000000 00000400 nt!IoInvalidateDeviceRelations+0x9
>     WARNING: Stack unwind information not available. Following frames may be wrong.
>     f78baf60 f7579541 8aa52d68 8a9fd268 f771f000 ACPI+0x1142e
>     f78baf7c f756ed55 8aa52d68 8a994000 00000000 ACPI+0x11541
>     f78baf9c f756f134 8a9fd268 f7592800 f78bafe0 ACPI+0x6d55
>     f78bafb0 f756f4c2 f78bafc0 f771f9c0 8a9fd268 ACPI+0x7134
>     f78bafc8 80ad9899 f75927a0 00000000 00000000 ACPI+0x74c2
>     f78baff4 80ad937b f791ac54 00000000 00000000 nt!KiRetireDpcList+0x7e
>     f78baff8 f791ac54 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
>     80ad937b 00000000 00000009 0081850f bb830000 0xf791ac54

>     STACK_COMMAND:  kb

>     FOLLOWUP_IP:
>     ACPI+1142e
>     f757942e eb06            jmp     ACPI+0x11436 (f7579436)

>     SYMBOL_STACK_INDEX:  5

>     SYMBOL_NAME:  ACPI+1142e

>     FOLLOWUP_NAME:  MachineOwner

>     MODULE_NAME: ACPI

>     IMAGE_NAME:  ACPI.sys

>     DEBUG_FLR_IMAGE_TIMESTAMP:  424d8208

>     FAILURE_BUCKET_ID:  0xA_ACPI+1142e

>     BUCKET_ID:  0xA_ACPI+1142e

>     Followup: MachineOwner
>     ---------

I don't understand all this debug with my limited knowledge but what I can tell is that in Safe Mode the only device who ask to be installed again and again that I never saw before on any compi(I tested a lot since I started overclocking in 2008) it's this "Microsoft ACPI Compliant Embedded Controller",in the other hand device manager also doesn't update the CPU wich is installed cause even under Z390 it keep 7740X instead of 8700K and CPUZ show the good CPU(8700k) ...

#2948

Doc.Brown

> Zitat von ⇗ IntiMD im Beitrag ¶ #2937

> @Doc.Brown
> FYI here are the Intel RSTe driver backports for XP by daniel_k
> ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (110) - RSTe 4.6.0.1085 x86
> ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (118) - RSTe 4.6.0.1085 x64
> ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (115) - RSTe 4.7.0.1098 x86
> For x86 NT5.2 systems, you might want to comment out the following entries just like this:

>     [SourceDisksFiles.x86]
>     iaStorA.sys = 1,,,
>     iaStorF.sys = 1,,,
>     ; storport.sys = 1,,,
>     ;

> and

>     [iaStorA_inst.ntx86]
>     CopyFiles=@iaStorA.sys
>     CopyFiles=@iaStorF.sys
>     ; CopyFiles=@storport.sys
>     ;

> PS. forgot to mention, they don't contain the TXTSETUP.OEM file, so you can't slipstream it in first stage text setup.

Do you mean that I could use this RSTe instead of Fernando's drivers ? by nlite integration ?
Sorry but my knowledge in coding is very bad and I don't understand how to/where to use those code lines,could you explain more please ?
Thank you :)

#2949

diderius6

⇗ @Doc.Brown
With the Fernando iaStore.sys driver 1006 and renaming
dxg.sys ->dxOrig.sys, boot and then back dxOrig.sys ->dxg.sys I succeed to boot normal to full Acpi XP SP3
on the simulating testboard. I use for this the debug version of hal.dll,
debug ntkrnlmp.exe and debug acpi.sys (hacked for Ryzen support).
But I still do not know, which driver causes this BSOD. I think, it has to do with the grafik driver (integrated GPU?)
and with memory above 4 Gbyte. So put in only 4 Gbyte ram, disable the CPU internal GPU and install graphikcard,
I use gtx 980
Dietmar

#2950 | Mikedebian | ⇗ @diderius6 Are you able to have legacy dos graphical applications open in fullscreen? Say, a game that is easy to get, commander keen 4 (shareware) or does it go to black screen? I am asking since you have a Gtx 980.

#2951

IntiMD

> Zitat von ⇗ Doc.Brown im Beitrag ¶ #2948

> > Zitat von ⇗ IntiMD im Beitrag ¶ #2937

> > @Doc.Brown
> > FYI here are the Intel RSTe driver backports for XP by daniel_k
> > ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (110) - RSTe 4.6.0.1085 x86
> > ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (118) - RSTe 4.6.0.1085 x64
> > ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (115) - RSTe 4.7.0.1098 x86
> > For x86 NT5.2 systems, you might want to comment out the following entries just like this:

> >     [SourceDisksFiles.x86]
> >     iaStorA.sys = 1,,,
> >     iaStorF.sys = 1,,,
> >     ; storport.sys = 1,,,
> >     ;

> > and

> >     [iaStorA_inst.ntx86]
> >     CopyFiles=@iaStorA.sys
> >     CopyFiles=@iaStorF.sys
> >     ; CopyFiles=@storport.sys
> >     ;

> > PS. forgot to mention, they don't contain the TXTSETUP.OEM file, so you can't slipstream it in first stage text setup.

> Do you mean that I could use this RSTe instead of Fernando's drivers ? by nlite integration ?
> Sorry but my knowledge in coding is very bad and I don't understand how to/where to use those code lines,could you explain more please ?
> Thank you :)

Like I said, slipstreaming it in first stage setup is impossible due to lack of TXTSETUP.OEM file, Unless somebody creates an appropriate one for the drivers.
You do not need knowledge in coding, since there isn't anything related to coding at all, just a quick INF mod. :D

#2952

IntiMD

> Zitat von ⇗ Doc.Brown im Beitrag ¶ #2947

> I don't understand all this debug with my limited knowledge but what I can tell is that in Safe Mode the only device who ask to be installed again and again that I never saw before on any compi(I tested a lot since I started overclocking in 2008) it's this "Microsoft ACPI Compliant Embedded Controller",in the other hand device manager also doesn't update the CPU wich is installed cause even under Z390 it keep 7740X instead of 8700K and CPUZ show the good CPU(8700k) ...

Maybe this modified LH5048 ACPI INF file courtesy of ⇗ @PPeti66x will handle this problem with that embedded controller? ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (166)

#2953

diderius6

⇗ @Doc.Brown
I noticed a resource conflict.
On Acpi XP SP3 I have no onboard sound (code 10).
On MPS XP SP3 I have sound.
So, it is a design error on the board,
another device shares IRQ and line with the Realtek soundchip
Dietmar
PS: Only this acpi.sys works for me (see post).
It is the DEBUG version of acpi 5512, original for XP SP3 but modded by me for Ryzen support.
On the acpi.sys 5048 (no matter which version), I got BSOD 0x7B, very strange, the new acpi.sys does not
like to work with iastor.sys 1006 on this board.
diderius6 has attached files to this post

- ⇗ acpi.rar

#2954

Gelip

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #2953

> I noticed a resource conflict.
> On Acpi XP SP3 I have no onboard sound (code 10).
> On MPS XP SP3 I have sound.
> So, it is a design error on the board,
> another device shares IRQ and line with the Realtek soundchip

What does the problem say on the Resources tab? Place the screenshot. Does it look exactly like this?
⇗

#2955

Doc.Brown

⇗ @diderius6
iGPU is always disabled,like lan and sound controlers cause it's useless for overclocking perhaps I need to enable sound if ressource is shared with another device as you say.I have a GT 730 and tried with a GTX770 also.I didn't try with less ram just tried to boot with a /maxmem in boot.ini yesterday,we have to limit Bdie RAM capacity on other OS cause 16gb is to much(even with x64 OS) and result on BSOD with tight timings like C12-11 for 4000+ mhz,I have old Edie 4gb stick so I'll test it too ^^
My XP build is a 5512 perhaps this ACPI will be more compatible
I've finished the file to re-build the SP3.cab and it works so I'll try all of this tomorrow I think
Thanks for your great help ;)
⇗ @IntiMD
I already tried this acpi.inf yesterday but doesn't change anything unfortunately
Ok now I understand for RST drivers :)

## Page 198

#2956 | diderius6 | ⇗ @Gelip No, it just tells unknow device ROOT\UNKNOWN\0000 Dietmar

#2957

diderius6

⇗ @Doc.Brown
Because I have had the nearly 100% identic BSOD as you,
now I think about device conflict:
1.) acpi.sys problem (only the for Ryzen Debug modded acpi.sys works for me)
2.) Iastor 1006 problem (with acpi.sys 5048 newest BSOD 0x7B, strange))
3.) Realtek sound (unknown, design error on board, low Irq, same PCI line, brrr).
1.) 2.) I solved, 3.) not
Dietmar

#2958

diderius6

Now I have the nearly perfect clone of my netbook Lenovo Flex 10.
It is the motherboard version Q1900m from Asrock.
Same CPU, same GPU, same chipset, same problems^^ under XP and Win 7 32 bit(!).
But on this board I can do Debug under XP via COM1, Lan, USB, I tested.
By the way, I found out, why USB debug on the Lenovo Flex 10 not works:
Crazy manufacturer cut simple some cables to the USB port. I found this in a report to Microsoft yesterday
for the Celeron series (me is N2806). Other notebook manufacturers do the same.
"This issue occurs because Intel® Atom Processor Z373x and CHT-CR platforms do not provide xHCI debugging support because of pin reduction."
And I found, what I do not want to hear: On those Bay Trail cpus happens a degrade at the USB ports:
Means, after about 20 months you get errors and errors and errors on the USB port, because the Silizium therefore is gone,..
Dietmar
⇗ https://forums.servethehome.com/index.ph...ign-flaw.19402/
EDIT: The DSDT for the Q1900m board does not change from version 1.30, 1.40,...1.90.
So, the problem with sound under Acpi XP SP3 stays forever^^.

#2959

diderius6

⇗ @daniel_k
Do you have an idea, where the Realtek soundcard can be found in this DSDT
from the Q1900m Asrock board? May be an easy hack can bring her back to life:))
Dietmar
diderius6 has attached files to this post

- ⇗ Q1900mdsdt.rar

#2960

Andalu

> Zitat von ⇗ infuscomus im Beitrag ¶ #2930

> @Andalu
> try this,
> copy ntkr128g.exe and hal128g.dll to c:\windows\system32
> make a backup of original boot.ini
> replace boot.ini contents with paeboot.ini contents
> hopefully this works

Thank you for your time and for your help. Unfortunately I could not solve. After applying the patch (I copied all the files into the related directories and I modified the boot.ini file too) and restarting the computer, I can finally get all the amount of the ram correctly recognized and the USB3 that works properly, but only until the computer is turned off. After restarting, the issue reappears: the usb2 ports are not powered (the usb mouse is off) and the devices attached to usb3 ports are not recognized. The same behavior also when I applied the 'chinese patch'.
The USB3 and the patches seem unable to coexist, or it works one or the other but not simultaneously.
Since this board also seems to be crazy as the other two, I start thinking that it may depend on the fact that they are all from Asrock....

#2961 | daniel_k | ⇗ @Mikedebian, with a GTX 980, I'm able to run EDIT.COM in full screen mode.
#2962 | daniel_k | ⇗ @diderius6, I believe it is HDEF. On Haswell and later, it is HDAS.
#2963 | Mikedebian | Hello ⇗ @daniel_k The issue I am having is not with text mode legacy applications, but those that require graphics like EGA, VGA, etc.
#2964 | daniel_k | ⇗ @Mikedebian, give me an example of what to run.
#2965 | Mikedebian | ⇗ @daniel_k Any shareware game would work. Commander Keen 4, Doom, Wolfenstein 3D, etc.

#2966

daniel_k

⇗ @schreiberstein, with a Server 2003 converted to XP, managed to get everything running.
- Intel USB3
- ASMedia USB3
- VIA USB3
- PAE with 15.9GB
- DOS apps working
daniel_k has attached images to this post ⇗ XP2003PAE.JPG

#2967

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #2966

> @schreiberstein, with a Server 2003 converted to XP, managed to get everything running.
> - Intel USB3
> - ASMedia USB3
> - VIA USB3
> - PAE with 15.9GB
> - DOS apps working

how can i have it too?

#2968

schreiberstein

⇗ @daniel_k
Oh, very nice!
Congratulations.
Converted in what sense? I see it says Windows XP.
I usually use this thing: ⇗ http://www.kood.org/win-2003-optimize-tool/
I think I will continue to use Windows XP because of this super cool HAL.dll.
I will see if I can debug ntvdm.exe with some tools and see why it crashes.
It crashes regardless of GPU drivers, I think. It has to do with USB.
Cheers,
schreiberstein

#2969 | daniel_k | ⇗ @Mikedebian, tried Wolf3D shareware. Opens automatically in full screen and hangs Windows.

#2970

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #2967

> how can i have it too?

This one is a private project, unfinished yet.
Try to install Server 2003 Enterprise and Datacenter, which have PAE.
If it works, you can get XP to work with the PAE hack.
I'm just showing a proof that the drivers do support PAE.

## Page 199

#2971 | daniel_k | ⇗ @schreiberstein, from Setup to working Desktop. Installs like XP x64 with no OOBE (asking for user names, activation and so on), default user is Administrator. Only hack is to enable PAE, which is only supported in Server 2003 Enterprise and Datacenter.

#2972

diderius6

ACPI XP SP3 install on Baytrail CPU
I just make a brandnew XP SP3 installations CD for the Asrock Q1900M board (BayTrail).
There I integrate the acpi.sys Debug version 5.1.2600.5512 original from XP SP3 with Hack for Ryzen support.
And I use the STORAHCI driver from ⇗ @skullteria together with new storport.sys,
because I noticed, that all the Iastor driver make problems on Baytrail chipset.
Ok, I just burned CD and now it installs on the Q1900m Asrock miniboard
with Bay Trail chipset and Valley View GPU.
Strange, that for a motherboard from 2014 you need a hacked acpi,
Dietmar
EDIT1: After txtsetup I got BSOD 0x7B.
Ok, storport.sys was gone as usual. But after that I get again BSOD 0x7B.
The registry entries for the STORAHCI I have to do by hand, I have never seen before.
Now install goes on. This is really funny: The model is good: At once I understand, why I never could
install direct to the netbook Lenovo Flex 10 XP SP3 with setup CD.
With this experience I see, that it will be very very difficult to build a generic Install CD for XP SP3,
that workes on all compis.
On next reboot I got again BSOD 0x7B and I have again to put the entries for STORAHCI by hand into registry.
Now I get the same BSOD as ⇗ @Doc.Brown . But not, when I chose save boot.
Crazy, I think nobody succeeds to install full Acpi XP SP3 until now on Baytrail chipset.
Yesssa, with disabling everything in Device Manager I come to the normal desktop with full Acpi XP SP3 on Baytrail chipset.
I think, it is really the very first time that this has been done. For example see this blog
⇗ https://ryanvm.net/forum/viewtopic.php?t=10596
⇗

#2973

schreiberstein

I added the Creative Audigy 2 ZS to my system via a PCI-E to PCI adapter and it works flawlessly.
I removed the AMD/ATI card from the system. Only the GeForce GTX 780 is now in there (aside from the Intel IGPU)
The HAL patch made my system a lot more responsive. Very happy about it.
USB works quite reliably as well. Mouse and Keyboard seem to work after every reboot.
I added "/PAE" to boot.ini, but I don't get more than 904MB RAM (64MB MIN ; 256MB MAX shared RAM for Intel IGPU in BIOS)
⇗ @diderius6
I wonder if there is a way to get more than 4GB (like on Server 2003) with your "halplusintelppmXPSP3.rar" hack bundle?
Like the file "Windows_XP_128GB_double_pae_addon_final_byDibya.7z.zip" from ⇗ @infuscomus suggests - but it has its own patched HAL.
Seems like this is the only way I could access more than 904MB RAM.
I could live with 4GB, but 904MB is quite small. I can feel it swapping when using 4 chrome tabs.
⇗ @XPLives
PCI Data Acquisition and Signal Processing Controller <-- I have only ONE of these devices
PCI bus 0, device 18, function 0
The drivers for this device are not installed. (Code 28)
Device Instance ID: PCI\VEN_8086&DEV_A379&SUBSYS_88881458&REV_10\3&11583659&0&90
Hardware IDs:
PCI\VEN_8086&DEV_A379&SUBSYS_88881458&REV_10
PCI\VEN_8086&DEV_A379&SUBSYS_88881458
PCI\VEN_8086&DEV_A379&CC_118000
PCI\VEN_8086&DEV_A379&CC_1180
Compatible IDs:
PCI\VEN_8086&DEV_A379&REV_10
PCI\VEN_8086&DEV_A379
PCI\VEN_8086&CC_118000
PCI\VEN_8086&CC_1180
PCI\VEN_8086
PCI\CC_118000
PCI\CC_1180
Matching Device ID:
[EMPTY]
I have also started to look into the NTVDM.EXE problem - attached is my output from WinDbg.
It seems that there is something wrong internally that is causing that.
For now, I am surprised at how stable Windows XP is. I once counted more than 5 hours of uptime, benchmarking with several 3DMark versions, playing music on XMPlay
Using the driver from daniel_k.
All important hardware works on Apple Mac OS X 10.14 Mojave, Windows 10, 7, XP and 2003.
The Creative Audigy even works after sleep/standby on Mac OS X using a patched kx Project audio driver kext.
My goal is it to NEVER have to do any preparations before dual booting another OS.
I don't want to plug my devices into different ports, change BIOS settings, etc.
As of now, this has been accomplished. I only have to press F12 at my bootscreen to bring up the boot menu and I am all set.
Now I only need to find a way to place the PCI card in the hard drive bay (right) of my case. All these riser card cables (including the bizarre USB3 type one) are so stiff.
I could put another PCI card into the riser card. It has two slots. #SoManyPossibilities
Cheers,
schreiberstein
schreiberstein has attached files to this post

- ⇗ ntvdm_windbg.txt

schreiberstein has attached images to this post ⇗ FD2C10DB-E523-4DE5-9446-E

#2974 | daniel_k | ⇗ @diderius6, what was the ACPI error on the Asrock Q1900M? I'm curious. A quick look at it and the only strange thing I've found was there are some Methods inside a Method. Never seen this before.

#2975

diderius6

⇗ @daniel_k
This is a really crazy Bios. It is Intel Insyde, brrr.. No tool works extracting Bios or parts of it etc.
The Bsod was before A5 (0x11,..) with original XP acpi.sys.
Later I went through a cascade of BSODs.
I get the same BSOD as ⇗ @Doc.Brown,
get BSOD 0x7E(c0000005,..)
Bsod 0x7B often (unclear reason with last acpi.sys 5048) but the most evel was BSOD A5 (0x2001,..).
This means, that the compi cannot enable Acpi mode for 1 cpu.
This remembers me a lot at the crazy way to the acpi.sys for Ryzen.
And because of this I come to the idea to use that Debug acpi.sys, hacked for Ryzen
and this works
Dietmar
PS: Do edit this DSDT will be hard work, but also fun:))!
EDIT: The work with the debug acpi.sys has one big disadvantage: Always, when it reaches a Breakpoint,
it gives BSOD 0x7E (0x80000003,..) which tells, please connect windbg and hit "i".
But on the Lenovo Flex 10 is no debug possible, so I have to change this acpi.sys back to the last one based on 5048.

#2976

daniel_k

⇗ @schreiberstein, please try this.
Replace both files at the same time, otherwise corruption may occur.
This Hal.dll includes ACPI timer patch from ⇗ @diderius6, plus PAE patch.
Source of original files:
⇗ http://vm1.duckdns.org/Public/Windows_XP...e_PAE_Limit.htm
Didn't try it yet, don't know if you need to set the /PAE command in Boot.ini

#2977 | daniel_k | ⇗ @diderius6, if you had the complete A5 error parameters, that would give us some clue about where it happens, you know, for example, _INI in hex ... But, like I've said before, really strange to have a Method inside another Method.
#2978 | schreiberstein | ⇗ @daniel_k Thank you. I will test that in a minute. By the way, the provided ntoskrnl.exe version is significantly older than the one I use right now: 5.1.2600.6748 vs. 5.1.2600.5512 // This matches the hal.dll version though.
#2979 | daniel_k | ⇗ @schreiberstein, the patched the original SP3, release. If you compare with the original, maybe is easy to patch the new one. Can you do it yourself? If so, remember to fix the PE checksum.

#2980

schreiberstein

⇗ @daniel_k
I replaced both files using another system (the existing one kept reverting the file after each replacement).
However, with or without /PAE there was no change of available memory whatsoever.
And I checked that the correct version was stored in system32.
I am now experimenting with the 128g patch. Just want to see if any of that stuff works for my system.
Cheers
schreiberstein

#2981

schreiberstein

Update:
I used "Windows_XP_128GB_double_pae_addon_final_byDibya.7z.zip" from ⇗ @infuscomus
Put ntkr128g.exe (version 5.1.2600.7146) and hal128g.dll (5.1.2600.5687) into system32,
and added a custom entry to boot.ini.
Now I have 31.8 GB of RAM with PAE enabled.
However, there are obvious problems due to the missing ACPI timer patch.
The patched USB files from the same package do not seem to be needed here. USB works as usual.
schreiberstein

#2982 | daniel_k | Here is the patched version. About the USB drivers, they are NOT needed as you don't have USB2.0 controllers, which are the one affected.

#2983

schreiberstein

⇗ @daniel_k
Yup! This worked! That was quick. Thank you!
31.8 GB - and Chrome works!
USB did not work on the first boot. NTVDM works right now. I can execute edit.com (I suppose that is always the case when USB does not work)
I was also able to finally launch the RAGE Expendable / Millennium Soldier installer (1999 video game)
I will replace the USB related DLLs in system32 with the ones from the 128gb patch shortly.
Cheers,
schreiberstein

#2984 | daniel_k | About the USB drivers, they are NOT needed as you don't have USB2.0 controllers, which are the one affected.
#2985 | schreiberstein | ⇗ @daniel_k Understood! Thank you!

## Page 200

#2986

schreiberstein

⇗ @daniel_k
This PAE 128gb constellation is causing a lot of issues.
USB never works (USB controller devices are not identified) and applications behave strangely.
It seems to mess with file IO. Some games crashed complaining they cannot check if the CD is present or fail to read a certain file. Chrome crashes quite regularly (pages die).
Explorer behaves slowly. There is a noticeable delay when navigating through folders.
So, I guess I will have to stay with Server 2003 if I want to use more than 904MB stably.
Could you try to apply the hal.dll patch to Server 2003 SP2 RTM hal.dll ? Then I could test the system further on 2003.
I really do not know how I could do that myself.
Is it a simple patch via hex editor and I could check via binary diff?
Cheers,
schreiberstein
schreiberstein has attached files to this post

- ⇗ 2003_sp2_i386_hal.rar

#2987

Gelip

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #2953

> @Doc.Brown
> I noticed a resource conflict.
> On Acpi XP SP3 I have no onboard sound (code 10).
> On MPS XP SP3 I have sound.
> So, it is a design error on the board,
> another device shares IRQ and line with the Realtek soundchip

What exactly computer type did you choose during installation - MPS Multiprocessor PC or MPS Uniprocessor PC ???
⇗

#2988 | daniel_k | ⇗ @schreiberstein Here it is, should be correct.
#2989 | diderius6 | ⇗ @Gelip I choose "MPS Multiprocessor PC". "MPS Uniprocessor PC" is without sense, in this case it would be better to choose "Standard PC" Dietmar

#2990

diderius6

⇗ @daniel_k
Hi,
do you have an idea about this DSDT?
It is from the Insyde Bios of the Lenovo Flex 10 notebook (Baytrail). No chance to make windbg work on it. This DSDT stays at other place in Bios, different from all other modern UEFI BIOS.
For any acpi.sys version until now, it gives first BSOD A5 (0x11,..). I think, this is the major problem to solve:
Acpi mode cant be enabled.
When you jump this, at once you come to BSOD A5 (0x2001,..) exact as this has been for the Ryzen cpu.
When you jump this 2001 BSOD, you get famous 0x7E (0xc0000005,..).
The problem in this is, that this netbook Flex 10 cant be debugged
Dietmar
PS: Win 7 32 bit also shows BSOD A5 (0x11,..) on this netbook, crazy.
diderius6 has attached files to this post

- ⇗ DSDTFlex10.rar

#2991

Doc.Brown

Hello all :)
I'm triyng another things like debug ACPI for ryzen (bsod 7e),changing RAM quantity,ahci injection one after other and test,for now I just put RSTe and storahci but nothing works again,i'll will test with USBXhci and Fernando's after
It's seems with New Z390 acpi5048 i don't need modded bios anymore
I'm looking all .log in Windows directory now,do you me to keep some of them for debug like "setupapi" or other else ?

#2992

IntiMD

> Zitat von ⇗ schreiberstein im Beitrag ¶ #2973

> @XPLives

>     PCI Data Acquisition and Signal Processing Controller <-- I have only ONE of these devices

>     PCI bus 0, device 18, function 0
>     The drivers for this device are not installed. (Code 28)

>     Device Instance ID: PCI\VEN_8086&DEV_A379&SUBSYS_88881458&REV_10\3&11583659&0&90

>     Hardware IDs:
>     PCI\VEN_8086&DEV_A379&SUBSYS_88881458&REV_10
>     PCI\VEN_8086&DEV_A379&SUBSYS_88881458
>     PCI\VEN_8086&DEV_A379&CC_118000
>     PCI\VEN_8086&DEV_A379&CC_1180

>     Compatible IDs:
>     PCI\VEN_8086&DEV_A379&REV_10
>     PCI\VEN_8086&DEV_A379
>     PCI\VEN_8086&CC_118000
>     PCI\VEN_8086&CC_1180
>     PCI\VEN_8086
>     PCI\CC_118000
>     PCI\CC_1180

>     Matching Device ID:
>     [EMPTY]

According to pci.ids, the device is called: "Intel Cannon Lake PCH Thermal Controller". You can use Fernando's Intel chipset devices INF AiO package ⇗ {II. Latest "pure" Intel Chipset Device *.INF files for all Intel systems from 6-Series up (for manual installation):}. When updating the device, make sure the path that you direct is "UNPACKED_PACKAGE_ROOT\CannonLake-H\CannonLake-HSystemThermal.inf"

#2993

Gelip

I follow this thread from the very beginning. I see there are problems with ACPI, AHCI and USB because on the motherboards you are testing there is no official support for WinXP. For WinXP, computers from 2010-2013 with UEFI bios are modern hardware. These devices have official WinXP support, i.e. drivers for all devices even for USB 3.0 (e.g. ASmedia). There are no any problems with ACPI or AHCI.
⇗ Windows XP: new Z68/Z77 rig in 2017
⇗ ASRock Z68 Extreme3 Gen3
⇗
I have such hardware on which WinXP 32-bit or 64-bit works very stable and fast - ThinkPad X220 laptop. I tested on it all Windows systems such as WinXP, Vista, 7, 8, 8.1, 10 and what is important - there are drivers for each system for all devices !!!
Linux and even Mac OS also work - ⇗ ThinkPad X220 macOS High Sierra 10.13 Installation Guide
Well, good luck in running WinXP on new hardware
P.S. I also have several computers from 1998-2003 and work very well to this day.
I do not understand why buy modern hardware as we want to use WinXP ???

#2994 | diderius6 | ⇗ @Gelip For fun^^ and XP SP3 is stable, very easy to handle and fast. It runs on 486 processor (i386 I have not tested) and via Qemu on Arm. Take a look at the "search" function at any othe OS. At once you would choose XP Dietmar

#2995

diderius6

⇗ @daniel_k
About the DSDT in Bios (Insyde) from Lenovo Flex 10 netbook.
Can it be, that the manufacturer extra put the DSDT away from its normal place in UEFI Bios GUID
C118F50D-391D-45F4-B3D3-11BC931AA56D
so that XP and Win7 cant find it?
They want to promote Win8.
I always think, that DSDT is an interpreted table, just as a stripe of paper, where acpi.sys runs over.
That OS XP, Vista, Win7 all show the same BSOD A5 (0x11,..)
makes me think, that I might be right.
But if it is so, can its own original DSDT just been copied in Bios itself to place in GUID C118F50D-391D-45F4-B3D3-11BC931AA56D
Dietmar
PS: The GUID C118F50D-391D-45F4-B3D3-11BC931AA56D
is not in this Bios from Insyde.
EDIT: I just upload via asl.exe its own DSDT to the registry of the Lenovo Flex 10 notebook.
So, the DSDT is there for sure. But the BSOD A5 (0x2001,..) stays as before.
So, it is really the fault in its DSDT. Strange, why also Win7 gives BSOD A5 (0x2001,..).
EDIT2: Now comes the most strange thing ever: With the original DSDT from the Lenovo Flex 10 netbook I can start to full Acpi mode on the Asrock Q1900m board. So, the real problem is not in this DSDT but somewhere in the Bios of the Flex 10.

#2996 | XPWELL64 | ⇗ @diderius6 I want to hibernate my PC, with acpi.sys it cannot hibernate. Can you make a DSDT table for me and integrate to my bios? Here is my bios link: ⇗ https://dlcdnets.asus.com/pub/ASUS/nb/X555LB/X555LBAS603.zip
#2997 | diderius6 | ⇗ @XPWELL64 Until now I am not good enough for to enable hibernate in DSDT. But just now I give the asl.exe tool a new chance for to overwrite DSDT Dietmar

#2998

XPLives

> Zitat von ⇗ diderius6 im Beitrag ¶ #2972

> ACPI XP SP3 install on Baytrail CPU
> I just make a brandnew XP SP3 installations CD for the Asrock Q1900M board (BayTrail).
> There I integrate the acpi.sys Debug version 5.1.2600.5512 original from XP SP3 with Hack for Ryzen support.
> And I use the STORAHCI driver from @skullteria together with new storport.sys,
> because I noticed, that all the Iastor driver make problems on Baytrail chipset.
> Ok, I just burned CD and now it installs on the Q1900m Asrock miniboard
> with Bay Trail chipset and Valley View GPU.
> Strange, that for a motherboard from 2014 you need a hacked acpi,
> Dietmar
> EDIT1: After txtsetup I got BSOD 0x7B.
> Ok, storport.sys was gone as usual. But after that I get again BSOD 0x7B.
> The registry entries for the STORAHCI I have to do by hand, I have never seen before.
> Now install goes on. This is really funny: The model is good: At once I understand, why I never could
> install direct to the netbook Lenovo Flex 10 XP SP3 with setup CD.
> With this experience I see, that it will be very very difficult to build a generic Install CD for XP SP3,
> that workes on all compis.
> On next reboot I got again BSOD 0x7B and I have again to put the entries for STORAHCI by hand into registry.
> Now I get the same BSOD as @Doc.Brown . But not, when I chose save boot.
> Crazy, I think nobody succeeds to install full Acpi XP SP3 until now on Baytrail chipset.
> Yesssa, with disabling everything in Device Manager I come to the normal desktop with full Acpi XP SP3 on Baytrail chipset.
> I think, it is really the very first time that this has been done. For example see this blog
> ⇗ https://ryanvm.net/forum/viewtopic.php?t=10596
> ⇗

⇗ @diderius6
Try my Intel Universal SATA driver on XP Pro 64 and test on that Baytrail desktop motherboard Asrock Q1900m.
XP Pro 64-Bit and Server 2003 64-Bit - Universal Intel SATA Controller Driver - XPLIVES64.ZIP
⇗ Windows XP Pro 64-Bit and Server 2003 64-Bit on Modern Hardware
Use a clean XP Pro 64-Bit and do not integrate any other drivers or STORAHCI. Do not even add any USB 3.0 modded drivers. Just keep it clean as possible.
The USB 2.0 ports should work on Baytrail with XP.
Only use my storage driver and DK's acpi.sys for first test and let us know the result.
Just integrate my 64-Bit SATA driver only. And add for acpi.sys use Daniel's recent Z390 acpi. Don't add anything else.
If DK's acpi does not work try yours after.
Also if can you test to see if any Ivy Bridge or Haswell XP Intel iGPU drivers works on that? Try standard one and the embedded one.
XPLives

#2999

diderius6

⇗ @Doc.Brown
I just proved, that the reason in your BSOD 0x0000000a (0x000000B0,0x00000002,0x00000000, xxx)
is only the Iastor driver version 1006
Dietmar
PS: So you have to work with the STORAHCI driver and storport.sys from @skullteria.
This is a hard job.

#3000 | Doc.Brown | I also tried it without Fernando's driver this morning but BSOD first because of the lack of storport and after copy it in system32/drivers the same "IRQL not less or equal" come again ⇗ @diderius6 I try other RSTe linked before,chipset drivers and also nv drivers by nlite but always the same

## Page 201

#3001 | diderius6 | ⇗ @Doc.Brown Nono, you give up too quickly. Build an XP SP3 on another, XP friendly compi ONLY with the STORAHCI driver and storport.sys from ⇗ @skullteria . This XP will start on Gene XI Dietmar

#3002

Gelip

⇗ @Mov AX, 0xDEAD

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #2378

> Again i've played with IOTR resource conflict, i think source of problem is how vga i/o ports is decoding.

Can you patch acpi.sys 5.2.3790.3959 from WinXP x64 please ?
Gelip has attached files to this post

- ⇗ acpi_xp_x64.zip

#3003

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #3001

> @Doc.Brown
> Nono, you give up too quickly. Build an XP SP3 on another, XP friendly compi ONLY with the STORAHCI driver and storport.sys from @skullteria .
> This XP will start on Gene XI
> Dietmar

I don't give up my friend,I'm already at it :p

#3004 | infuscomus | ⇗ @Doc.Brown I have a modified XP ISO with all the patches integrated if you want to try it

#3005

Doc.Brown

> Zitat von ⇗ infuscomus im Beitrag ¶ #3004

> @Doc.Brown
> I have a modified XP ISO with all the patches integrated if you want to try it

Yes I could make a try,thanks ;)
Edit : always the same BSOD at the same moment with only storahci on z390

#3006 | infuscomus | ⇗ @Doc.Brown I sent you a PM
#3007 | Doc.Brown | Thank you :)
#3008 | XPWELL64 | ⇗ @diderius6 I want you to mod my bios. I integrated dsdt.aml with UEFItool but after flashing mod bios, Windows 7 gave a BSoD too. The detailed error codes are: 0xA5 0x11 0x08 (in Windows XP).

#3009

diderius6

⇗ @XPWELL64
This is the "normal" acpi.sys BSOD.
Try the last acpi.sys version from ⇗ @daniel_k
Dietmar
PS: Notebooks are different from normal compis, I just learned:)).
So try different acpi.sys.

#3010 | Doc.Brown | ⇗ @infuscomus Exactly the same BSOD with your XP during devices installation,the truth is deeper with this motherboard it seems
#3011 | XPWELL64 | I found some infos about Intel HD 5500 and UHD 620 graphics on Windows 10 igdkmd64.sys but functions are totally different. (I used IDA Pro.)
#3012 | diderius6 | ⇗ @Doc.Brown It is one device: Iastor.sys vers 1006 Dietmar

#3013

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #3012

> @Doc.Brown
> It is one device: Iastor.sys vers 1006
> Dietmar

Is there something to do against that ⇗ @diderius6 ?
Thanks
Edit: i've got an old adaptec SATA2 pcie card,i try

#3014

diderius6

⇗ @Doc.Brown
Start working XP SP3 on the Gene XI board in Safe Mode (F8).
Copy from the link here storport.sys into windows\system32\drivers.
Copy the extracted folder to your XP c:\.
Via Device Manager go to IDE ATA/ATAPI-Controller
and search for new driver. Direct to the i386 folder of the STORAHCI package
from ⇗ @skullteria and install the driver.
When you restart it will work at once or you have to test different acpi.sys
Dietmar
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (59)

#3015

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #2660

> @Mov AX, 0xDEAD, nice job with KDNET and thanks for sharing it publicly!
> Any plans to work on an x64 version?

> Zitat von ⇗ Gelip im Beitrag ¶ #3002

> @Mov AX, 0xDEAD
> Can you patch acpi.sys 5.2.3790.3959 from WinXP x64 please ?

Sorry, guys, WinXP/2003 x64 is out of my hobbies

## Page 202

#3016

daniel_k

> Zitat von ⇗ diderius6 im Beitrag ¶ #2995

> @daniel_k
> About the DSDT in Bios (Insyde) from Lenovo Flex 10 netbook.
> Can it be, that the manufacturer extra put the DSDT away from its normal place in UEFI Bios GUID
> C118F50D-391D-45F4-B3D3-11BC931AA56D

The GUID probably has nothing to do with it, seems that it isn't a standard GUID after all, as I couldn't find any reference to it in any UEFI docs.

> Zitat

> EDIT2: Now comes the most strange thing ever: With the original DSDT from the Lenovo Flex 10 netbook I can start to full Acpi mode on the Asrock Q1900m board. So, the real problem is not in this DSDT but somewhere in the Bios of the Flex 10.

Yeah, that one is really strange.

    Scope (\_SB)
                Device (LPCB)
                           {
                    Name (_ADR, 0x001F0000)  // _ADR: Address
                    Scope (\_SB) -> This seems to be wrong, inside a Device and inside it's own scope?!
                                   {
                        OperationRegion (ILBR, SystemMemory, IBAS, 0x8C)
                        Field (ILBR, AnyAcc, NoLock, Preserve)
                                           {
                            Offset (0x08),
                            PARC,   8,
                            PBRC,   8,
                            PCRC,   8,
                            PDRC,   8,
                            PERC,   8,
                            PFRC,   8,
                            PGRC,   8,
                            PHRC,   8,
                            Offset (0x88),
                                ,   3,
                            UI3E,   1,
                            UI4E,   1
                                           }

                        Device (LNKA) -> LNKx are critical devices, if the above is wrong, this should be as well
                                           {
                            Name (_HID, EisaId ("PNP0C0F"))  // _HID: Hardware ID
                            Name (_UID, One)  // _UID: Unique ID
                            Method (_DIS, 0, Serialized)  // _DIS: Disable Device
                                                   {
                                Or (PARC, 0x80, PARC)
                                                   }

                            Method (_PRS, 0, Serialized)  // _PRS: Possible Resource Settings
                                                   {
                                Return (PRSA)
                                                   }
    ...

No wonder Insyde BIOS is the worst!
The way the DSDT is written is terrible to read!
I'm sure even the person who wrote can't read it easily.

#3017

diderius6

Hi,
here is a new acpi.sys just from outer space )!
It is based on the original acpi.sys from XP SP3. The advantage against the 5048 version is,
that you get Symbols from the Microsoft Server for debug for it.
By the way I noticed, that even between the original english acpi.sys versions 5512,
there are differences. So we need to give the SHA-1 number each time,
when we speak about a special version
Dietmar
PS: This acpi.sys has SHA-1 number 4115882444A63465079E5D1C27987CD500E8FB9A
diderius6 has attached files to this post

- ⇗ acpi.rar

#3018

daniel_k

Did some load and restart stability tests with XP SP3 x86 fully patched, clean install. All drivers were installed.
1) Disabled automatic restart on system error
2) Created a shortcut in Startup folder of Start Menu, so system restarts continuosly, with the following command line:

    shutdown.exe -t 0 -r

3) Ran the shortcut.
Results:
- Original ACPI.SYS (with patched DSDT):
No issues for 1 hour. Really rare, but I've seen the system hang during shutdown or restart when it was about to power off or reset the display. I don't consider this to be critical.
- Modded ACPI.SYS:
Crashes when loading XP after a dozen restart loops, with a stop error A3 - ACPI_DRIVER_INTERNAL. This is a critical error.
- Original or Modded ACPI.SYS with PAE hack:
Crashes ramdonly during XP loading, with a stop error 0A - IRQL_NOT_LESS_OR_EQUAL.
WDF drivers like VIA USB3 don't work, the XHCI controller shows a yellow bang in Device Manager with error code 10. Seriously, this hack sucks, badly written, one can see that there are many differences between XP's hal and 2003's.
Disabling WDF drivers (including framework), decrease the amount of crashes, but don't stop them.

#3019 | XPWELL64 | ⇗ @diderius6 I believe I can hack Intel HD for Windows XP driver. I found some IDA function strings about Windows 10 UHD Graphics. If I find corresponding function, I can mod it.
#3020 | daniel_k | ⇗ @diderius6, I'd recommend that you do the XP loading/restarting test as I did above.
#3021 | XPWELL64 | Just graph view the string that you addressed me and at the bottom of the graph I saw a haswell included function.
#3022 | Doc.Brown | Bsod A5 with your last acpi.sys even in safe mode ⇗ @diderius6 ;) Nothing works for me,i've tested all the acpi,only boot in safe mode but now with my last ISO the Microsoft ACPI Compliant embedded controler is well installed

#3023

diderius6

⇗ @daniel_k
I want to test, but with which XP version?
The compis themselves are different.
On my compi for daily use with Intel X58 from 2009(!) with i920 cpu
I do not have a single BSOD under XP SP3 in 2 years
Dietmar

#3024 | XPWELL64 | ⇗ @diderius6 Can I use dsdt from Haswell Laptop? Daniel_k used DSDT from Insyde and used in AMI. Which laptop's (or AiO's) dsdt is best for Asus X555LB?
#3025 | diderius6 | ⇗ @Doc.Brown Please, can you write the exact BSOD number A5 for test with acpi.sys from outer space? Dietmar

#3026

diderius6

⇗ @XPWELL64
This was for me the only second time, that a DSDT from another compi works.
In this crazy case also vice versa change DSDT is possible, with better Acpi compatibility than before(!)
Dietmar
PS: The compis, between you can share DSDT needs to be nearly identic.
But an exact criterium, what makes it possible to share successfull DSDT between them, I dont have.
This brings me back to my old idea, to make a very short, generic DSDT for all compis,
which use XP SP3.

#3027 | Doc.Brown | ⇗ @diderius6 of course it's A5 (0x00000003,0x8AA6A6E0,0xC0140008,0x494E495F) ;)
#3028 | XPWELL64 | ⇗ @diderius6 I integrated N56VJ dsdt into x555lb bios.

#3029

Gelip

⇗ @skullteria

> Zitat von ⇗ skullteria im Beitrag ¶ #2425

> Hey, to disable Signature check, need patch ImgpValidateImageHash function inside winload.exe. For me, work these lines:
> Original: 8B C8 85 C9 89 4D 08 7D
> Replace: C7 45 08 00 00 00 00 EB
> x64(maybe)
> Original: 45 33 db 41 3b c3 8b d8
> Replace: C7 45 08 00 00 00 00 EB
> Tested on Vista SP2 winload

I try disable sig check in winload.exe from 64-bit Vista beta 5384.4. HEX 45 33 db 41 3b c3 8b d8 is in the file but after change and rebuild PE checksum loader not work even after added DisableIntegrityChecks in BCD
Fortunately, I was able to turn off signature checking in 64-bit files winload.efi and winload.exe from beta longhorn server 16497 - ⇗ How to switch XP over to winload bootloader?
I need help to disable sig check in 64-bit files winload.efi and winload.exe from Vista beta 5384.4
Gelip has attached files to this post

- ⇗ org_winload_5384.zip

#3030

schreiberstein

⇗ @daniel_k
Thank you for your HAL.DLL patch for Server 2003 x86.
I can report that it is working fine.
The only downside to running Server 2003 seems to be the version incompatibility with user applications which deny you the installation progress based on some version string.
I would like to fake the version string to Windows XP SP3 but I am not quite sure how to do that.
I attempted to change some strings in HKLM\Software\Microsoft\Windows NT\Current Version
ProductName to Windows XP
CSD Version to Service Pack 3.
But nothing changed in the "System Properties" screen, neither were I able to install the nVidia drivers for Windows XP.
Even XP compatibility mode failed.
It either says "GeForce experience requires Windows XP SP3" or (with compatibility mode) complains that nView, GeForce Experience and the driver could not be installed. And I need the whole driver package so mutli-monitor mode can be properly configured.
I am not sure if it is even possible to completely fake "XPness" to user applications.
Both XP and 2003 USB fails every few reboots. Some devices (One AMD USB 2.0 Hub and AMD USB 3.0) have an error code 10.
Cheers,
schreiberstein

## Page 203

#3031

XPLives

> Zitat von ⇗ Gelip im Beitrag ¶ #2993

> I follow this thread from the very beginning.
> I do not understand why buy modern hardware as we want to use WinXP ???

Because it works. Use the K.I.S.S. method.

#3032

Mov AX, 0xDEAD

> Zitat von ⇗ schreiberstein im Beitrag ¶ #3030

> I would like to fake the version string to Windows XP SP3 but I am not quite sure how to do that.
> I attempted to change some strings in HKLM\Software\Microsoft\Windows NT\Current Version
> ProductName to Windows XP
> CSD Version to Service Pack 3.
> But nothing changed in the "System Properties" screen, neither were I able to install the nVidia drivers for Windows XP.
> Even XP compatibility mode failed.
> It either says "GeForce experience requires Windows XP SP3" or (with compatibility mode) complains that nView, GeForce Experience and the driver could not be installed.

you need fake kernel32.dll/GetVersionEx too, it return current OS like numbers, 5.1 / 5.2 / xx

#3033

dencorso

⇗ @daniel_k: Does the hal5687_timer_patch.rar you posted some posts agop just have the timer patch, or does it include the > 4 GiB patch, too?

> Zitat von ⇗ schreiberstein im Beitrag ¶ #3030

> The only downside to running Server 2003 seems to be the version incompatibility with user applications which deny you the installation progress based on some version string.
> I would like to fake the version string to Windows XP SP3 but I am not quite sure how to do that.

Try using fcwin2k.exe for it. I think you can learn how to use it by trial and error, but if you want to read more about it, try this thread at msfn:
⇗ https://msfn.org/board/topic/120936-kdw-fcwin2k/
dencorso has attached files to this post

- ⇗ fcwin2k.rar

#3034

XPLives

> Zitat von ⇗ diderius6 im Beitrag ¶ #2972

> ACPI XP SP3 install on Baytrail CPU
> I just make a brandnew XP SP3 installations CD for the Asrock Q1900M board (BayTrail).
> There I integrate the acpi.sys Debug version 5.1.2600.5512 original from XP SP3 with Hack for Ryzen support.
> And I use the STORAHCI driver from @skullteria together with new storport.sys,
> because I noticed, that all the Iastor driver make problems on Baytrail chipset.
> Ok, I just burned CD and now it installs on the Q1900m Asrock miniboard
> with Bay Trail chipset and Valley View GPU.
> Strange, that for a motherboard from 2014 you need a hacked acpi,
> Dietmar
> EDIT1: After txtsetup I got BSOD 0x7B.
> Ok, storport.sys was gone as usual. But after that I get again BSOD 0x7B.
> The registry entries for the STORAHCI I have to do by hand, I have never seen before.
> Now install goes on. This is really funny: The model is good: At once I understand, why I never could
> install direct to the netbook Lenovo Flex 10 XP SP3 with setup CD.
> With this experience I see, that it will be very very difficult to build a generic Install CD for XP SP3,
> that workes on all compis.
> On next reboot I got again BSOD 0x7B and I have again to put the entries for STORAHCI by hand into registry.
> Now I get the same BSOD as @Doc.Brown . But not, when I chose save boot.
> Crazy, I think nobody succeeds to install full Acpi XP SP3 until now on Baytrail chipset.
> Yesssa, with disabling everything in Device Manager I come to the normal desktop with full Acpi XP SP3 on Baytrail chipset.
> I think, it is really the very first time that this has been done. For example see this blog
> ⇗ https://ryanvm.net/forum/viewtopic.php?t=10596
> ⇗

> Zitat von ⇗ diderius6 im Beitrag ¶ #2972

> ACPI XP SP3 install on Baytrail CPU
> I just make a brandnew XP SP3 installations CD for the Asrock Q1900M board (BayTrail).
> Yesssa, with disabling everything in Device Manager I come to the normal desktop with full Acpi XP SP3 on Baytrail chipset.
> I think, it is really the very first time that this has been done.

I didn't have enough time to add earlier. I remember this motherboard from a few years ago. I think I was using a Z68 but fan cooled at the time.
I saw this BayTrail one and was interested because it was fanless and a very low wattage model.
But one thing bugged me was no XP drivers from the website stated. That and only 1 Dimm slot maxed at 8GB.
So every now and then this motherboard comes up in discussion on forums. So I may have to buy one to test out. It seems to be closest to Sandy Bridge era so curiously I always wondered maybe it was XP compatible but at the time I didn't want to waste a lot of money on it.
You see I found out it uses a special CPU soldered to the motherboard. Then I said #$*!. I wanted to swap the CPU out and test in my socket 1155. So not compatible and you can't swap the CPU for another. Later Haswell Xeon is your best friend and even more lower wattage.
One day... I will test...the Asrock Q1900M for fun.
I found a Baytrail laptop that is fanless from searching a week ago. It is peaking my interest as I think I can get XP working on it for a real cheap security web cam that won't die from fan death from 24/7 operation. And if Intel integrated graphics driver can work than the best XP fanless laptop.

#3035 | dencorso | ⇗ @schreiberstein: I guess you may find this guide useful, too! ⇗ https://web.archive.org/web/200702120345...in2k3.ziras.de/

#3036

XPLives

> Zitat von ⇗ schreiberstein im Beitrag ¶ #2973

> I added the Creative Audigy 2 ZS to my system via a PCI-E to PCI adapter and it works flawlessly.
> I removed the AMD/ATI card from the system. Only the GeForce GTX 780 is now in there (aside from the Intel IGPU)
> The HAL patch made my system a lot more responsive. Very happy about it.
> USB works quite reliably as well. Mouse and Keyboard seem to work after every reboot.
> I added "/PAE" to boot.ini, but I don't get more than 904MB RAM (64MB MIN ; 256MB MAX shared RAM for Intel IGPU in BIOS)
> @diderius6
> I wonder if there is a way to get more than 4GB (like on Server 2003) with your "halplusintelppmXPSP3.rar" hack bundle?
> Like the file "Windows_XP_128GB_double_pae_addon_final_byDibya.7z.zip" from @infuscomus suggests - but it has its own patched HAL.
> Seems like this is the only way I could access more than 904MB RAM.
> I could live with 4GB, but 904MB is quite small. I can feel it swapping when using 4 chrome tabs.
> @XPLives
> PCI Data Acquisition and Signal Processing Controller <-- I have only ONE of these devices
> PCI bus 0, device 18, function 0
> The drivers for this device are not installed. (Code 28)
> Device Instance ID: PCI\VEN_8086&DEV_A379&SUBSYS_88881458&REV_10\3&11583659&0&90
> Hardware IDs:
> PCI\VEN_8086&DEV_A379&SUBSYS_88881458&REV_10
> PCI\VEN_8086&DEV_A379&SUBSYS_88881458
> PCI\VEN_8086&DEV_A379&CC_118000
> PCI\VEN_8086&DEV_A379&CC_1180
> Compatible IDs:
> PCI\VEN_8086&DEV_A379&REV_10
> PCI\VEN_8086&DEV_A379
> PCI\VEN_8086&CC_118000
> PCI\VEN_8086&CC_1180
> PCI\VEN_8086
> PCI\CC_118000
> PCI\CC_1180
> Matching Device ID:
> [EMPTY]
> I have also started to look into the NTVDM.EXE problem - attached is my output from WinDbg.
> It seems that there is something wrong internally that is causing that.
> For now, I am surprised at how stable Windows XP is. I once counted more than 5 hours of uptime, benchmarking with several 3DMark versions, playing music on XMPlay
> Using the driver from daniel_k.
> All important hardware works on Apple Mac OS X 10.14 Mojave, Windows 10, 7, XP and 2003.
> The Creative Audigy even works after sleep/standby on Mac OS X using a patched kx Project audio driver kext.
> My goal is it to NEVER have to do any preparations before dual booting another OS.
> I don't want to plug my devices into different ports, change BIOS settings, etc.
> As of now, this has been accomplished. I only have to press F12 at my bootscreen to bring up the boot menu and I am all set.
> Now I only need to find a way to place the PCI card in the hard drive bay (right) of my case. All these riser card cables (including the bizarre USB3 type one) are so stiff.
> I could put another PCI card into the riser card. It has two slots. #SoManyPossibilities
> Cheers,
> schreiberstein

⇗ @schreiberstein

> Zitat von ⇗ schreiberstein im Beitrag ¶ #2973

> I added "/PAE" to boot.ini, but I don't get more than 904MB RAM (64MB MIN ; 256MB MAX shared RAM for Intel IGPU in BIOS)
> PCI Data Acquisition and Signal Processing Controller

What are the Min and Max settings for the Intel Shared Ram. It can't be 64MB MIN and 256MB MAX.
Make sure you are dynamically sharing the video memory. You should be able to set it to a fixed value.
Usually Minimum I've seen should be 128MB and Max either 1.5GB to 2.5GB range.
Also I would try to disable the iGPU but for testing purposes here's what I recommend you do.
Remove the graphics card and make sure the BIOS default video output for iGPU.
Then test minimum shared video memory and boot into XP and see what the value is for Total Memory.
Then reboot go to BIOS and set to MAX value 1.5GB+ and boot into XP again and see what the value is for Total Memory.
If it changes or not let me know. If not most likely you there is some other option not set correctly.
Also are you planning to completely disable the iGPU when using MAC OS and XP? I would recommend you disable it and force PCIe as primary video card and disable any shared MultiDisplay output options you see.

#3037

schreiberstein

⇗ @dencorso
Oh my goodness!
I have not seen this guide in 10 years! Thank you! So much nostalgia.
Back in 2006, I used this guide to convert my Server 2003 system into a desktop. So much nostalgia.
The "Win2003v146.exe" Win2003 Optimize Tool from kood.org and Winfuture XP Iso Builder get the job done more efficiently, from my experience.
I know the fcwin2k.exe tool from blackwingcat, but thought that it would only work for Win2000 systems.
(I spent a good amount of time in ~2015-2016 with this Windows 2000 modding stuff, hehe)
Thanks for the hint! I will definitely check it out again!
Cheers,
schreiberstein

#3038

schreiberstein

⇗ @XPLives
Thank you.
I will experiment with Intel HD settings as well.
It actually is 64MB MIN and 256MB MAX
I have nearly the exact same BIOS settings as found in this thread:
⇗ https://www.tonymacx86.com/threads/succe...-rx-580.267551/
> Internal Graphics → Enabled
> DVMT Pre-Alloc → 64M (May not be present in BIOS F6 and later.)
> DVMT Total Gfx Mem → 256M (May not be present in BIOS F6 and later.)
--> Except that I have CSM mode activated for obvious reasons.
The Intel iGPU has very significant benefits on Mac OS X. It will be used as rendering accelerator and is required for compatibility on certain emulated machine types (otherwise JPEGs won't be rendered at all)
I have read somewhere that this has to do with some kind of memory hole for "reserved devices".
Given that I can access the entire amount of RAM just fine on Windows Server 2003, there should probably be a way to achieve that on XP as well. Or maybe simply get 2003 to pretend it is XP, hehe.
Cheers,
schreiberstein

#3039

diderius6

Does this Windbg print means, that my for XP SP3 hacked driver igxpmp32.sys is loaded and started?
Dietmar

>     Dumping IopRootDeviceNode (= 0x8a1b3ee8)
>     DevNode 0x8a1b3ee8 for PDO 0x8a1b3020
>       Parent 0000000000   Sibling 0000000000   Child 0x8a1b3a88
>       InstancePath is "HTREE\ROOT\0"
>       State = DeviceNodeStarted (0x308)
>       Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       StateHistory[04] = DeviceNodeEnumerateCompletion (0x30d)
>       StateHistory[03] = DeviceNodeStarted (0x308)
>       StateHistory[02] = DeviceNodeEnumerateCompletion (0x30d)
>       StateHistory[01] = DeviceNodeStarted (0x308)
>       StateHistory[00] = DeviceNodeUninitialized (0x301)
>       StateHistory[19] = Unknown State (0x0)
>       StateHistory[18] = Unknown State (0x0)
>       StateHistory[17] = Unknown State (0x0)
>       StateHistory[16] = Unknown State (0x0)
>       StateHistory[15] = Unknown State (0x0)
>       StateHistory[14] = Unknown State (0x0)
>       StateHistory[13] = Unknown State (0x0)
>       StateHistory[12] = Unknown State (0x0)
>       StateHistory[11] = Unknown State (0x0)
>       StateHistory[10] = Unknown State (0x0)
>       StateHistory[09] = Unknown State (0x0)
>       StateHistory[08] = Unknown State (0x0)
>       StateHistory[07] = Unknown State (0x0)
>       StateHistory[06] = Unknown State (0x0)
>       StateHistory[05] = Unknown State (0x0)
>       Flags (0x00000131)  DNF_MADEUP, DNF_ENUMERATED,
>                           DNF_IDS_QUERIED, DNF_NO_RESOURCE_REQUIRED
>       DisableableDepends = 3 (from children)
>     1: kd> !lmi igxpmp32
>     Loaded Module Info: [igxpmp32]
>              Module: igxpmp32
>        Base Address: b92c5000
>          Image Name: igxpmp32.sys
>        Machine Type: 332 (I386)
>          Time Stamp: 52eae6bc Fri Jan 31 00:56:44 2014
>                Size: 277c00
>            CheckSum: 27acd4
>     Characteristics: 210e
>     Debug Data Dirs: Type  Size     VA  Pointer
>                  CODEVIEW    84, 20be60,  20be60 RSDS - GUID: {F23FF9B8-E2C4-44E8-8D55-1CBFFD969526}

>                    Age: 1, Pdb:
>     d:\ccViews\autobuild1_BR-1401-003D_14.56_Snapshot\gfx_Development\dump32\igfx\xp\gtune\AIM3Lib\igxpmp32.pdb
>          Image Type: MEMORY   - Image read successfully from loaded memory.
>         Symbol Type: NONE     - PDB not found from symbol server.
>         Load Report: no symbols loaded
>     1: kd> .reload igxpmp32.sys
>     1: kd> !devnode 0 1 igxpmp32
>     Dumping IopRootDeviceNode (= 0x8a1b3ee8)

>     Dumping IopRootDeviceNode (= 0x8a1b3ee8)
>     DevNode 0x8a1b3ee8 for PDO 0x8a1b3020
>       InstancePath is "HTREE\ROOT\0"
>       State = DeviceNodeStarted (0x308)
>       Previous State = DeviceNodeEnumerateCompletion (0x30d)

#3040

XPLives

> Zitat von ⇗ schreiberstein im Beitrag ¶ #3038

> @XPLives
> Thank you.
> I will experiment with Intel HD settings as well.
> It actually is 64MB MIN and 256MB MAX
> I have nearly the exact same BIOS settings as found in this thread:
> ⇗ https://www.tonymacx86.com/threads/succe...-rx-580.267551/
> > Internal Graphics → Enabled
> > DVMT Pre-Alloc → 64M (May not be present in BIOS F6 and later.)
> > DVMT Total Gfx Mem → 256M (May not be present in BIOS F6 and later.)
> --> Except that I have CSM mode activated for obvious reasons.
> The Intel iGPU has very significant benefits on Mac OS X. It will be used as rendering accelerator and is required for compatibility on certain emulated machine types (otherwise JPEGs won't be rendered at all)
> I have read somewhere that this has to do with some kind of memory hole for "reserved devices".
> Given that I can access the entire amount of RAM just fine on Windows Server 2003, there should probably be a way to achieve that on XP as well. Or maybe simply get 2003 to pretend it is XP, hehe.
> Cheers,
> schreiberstein

⇗ @schreiberstein
Okay I had my integrated Intel HD Graphics disabled in the BIOS.
Now that I re-enabled them.
Under [Chipset]
Internal Graphics → Enabled
DVMT Pre-Alloc
64MB Default, (Range 32MB-1024MB)
DVMT Total Gfx Mem
256MB Default, (Range 128MB, 256MB, MAX)
The MAX may be some unknown value definitely greater than 256MB. Since my BIOS does not show what the MAX is it must be based on how much installed memory detected and the BIOS probably has a set value I'm guessing. In SkyLake I think it was was 1.5GB. So it's possible the MAX on Coffee Lake increased higher than 1.5GB and possibly 2.0GB to 2.5GB. Since most people will not be installing this on XP they figured most people will be have installed 32GB or 64GB of RAM for most users so I would guess the MAX could be 2.5GB or 3.0GB? Maybe someone here like Lost_N_BIOS could figure out what this value for MAX is for your motherboard?
That is why we are running these tests.
I understand you need the iGPU for MAC. But doesn't the GTX 780 already do a better job of that? Or am I missing something why would an underpowered integrated IGPU be more powerful than your GTX 780? Why wouldn't the GTX 780 be taking over these tasks?
What exactly are you referring to by "emulated machine types"?
Also in another post you said "constellation" what did you mean by this?
You might want to hit ENTER on the DVMT Pre-Alloc and a new Menu list should appear with more values to choose from.
You can probably choose 32MB here which is the lowest on mine.
DVMT Total Mem could be set to 128MB which is the lowest on mine.
You can ask others here who have 300 Series MotherBoard what their settings/ranges are to compare.
[Test #1]
So basically try
32MB - Pre
128MB - Total
Boot into XP check System Properties, General -- Do A Snapshot
Check Task Manager, Performance -- Do A Snapshot
Then Reboot Enter BIOS
[Test #2]
Try again
1024MB - Pre
MAX - Total -- I'm guessing this should use 1024MB or whatever the limit could be given the installed RAM.
Boot into XP check System Properties, General -- Do A Snapshot
Check Task Manager, Performance -- Do A Snapshot
Hopefully these two tests alter the Total Memory shown/reported.
Let's see what happens and of course final comparison test.
[Test #3]
Disable Internal Graphics in BIOS, Power Off
Install GTX 980, Power On
Boot into XP check System Properties, General -- Do A Snapshot
Check Task Manager, Performance -- Do A Snapshot
If you can upload all Snapshots and label each.
Test 1A
Test 1B
Test 2A
Test 2B
Test 3A
Test 3B
You could Test #4 and Enable the Integrated Graphics using Test #2 Settings and with GTX 980 installed.
Test 4A
Test 4B
BTW, I got a MiniMAC coming so maybe this XP Hackintosh Project of yours could be simplified.
Hopefully you got some time to answer some of those previous MAC related questions I sent you prior. The ones you don't know or can't test yet let me know.

#3041

schreiberstein

⇗ @XPLives
I have just attempted booting with the iGPU completely disabled...
Now I had 984MB vs 904MB of RAM.
So no, the iGPU does not take away THAT much RAM.
nVidia cards are not optimized for Apple Mac OS X. That is why Apple uses ATI/AMD exclusively these days.
"emulated machine types" - on a hackintosh, you can choose a Mac hardware model. (such as iMac, MacMini, etc. and you specify their model identifier)
Mac OS X behaves differently on different platform definitions (concerning power management, utilization of dedicated GPUs, even down to the number of available USB ports)
Certain models expect the iGPU to be present as they offload certain tasks onto the iGPU. The iGPU is actually very efficient for something like JPEG rendering and other kinds of acceleration, as far as I have read.
You may find more information on that in the aforementioned tonymacx86 thread concerning the Gigabyte Z390 Designare motherboard.
Especially professional applications like FinalCut Pro X rely on the iGPU.
It would be a waste not to utilize it. Do I need it? I actually tried to disable it and then my system was unable to display JPEGs and to perform other kinds of OS X specific magic like "quick look" previews of movies and images.
And since the problem seems to lie somewhere else, I am not going to hate on the Intel HD graphics component of my system.
It certainly is not using 3GB of RAM, otherwise I would notice that on Server 2003 as well. But there I had 31+GB available.
It seems like Windows XP is unable to cope with something else, some small reserved portion of RAM. And instead of addressing the remaining RAM, it just quits at 904MB and calls it a day. But I have no clue how Windows XP memory mangement and detection works.
With "constellation" I was referring to the 128GB ntoskrnl.exe and hal.dll hack: It had very obvious side effects on the system. Issues with I/O, stuttering, noticeable lag when navigating through explorer.exe, etc. All things that were not present on XP on 904MB and Server 2003 with 32GB PAE.
Once I got either XP or Server 2003 running a bit more reliably, I will write a guide for my motherboard - since it bridges so many gaps. Windows XP support, 7 support, 10 support, Mac OS X support, ...
It is also the last architecture that will be able to run Mac OS X 10.14 Mojave without incompatibilities - hence the last version that runs 32-Bit Mac apps from the mid 2000s natively.
I hope this answers your questions, gentleman. :-)
Cheers,
schreiberstein
EDIT: I will do the testing procedures that you specified. Perhaps the amount of available RAM might still change. Will keep you posted.

#3042

diderius6

I do not find the exact place in igxpmp32.sys (see attached file) where this BSOD happens
Dietmar

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Opened \\.\com1
    Waiting to reconnect...
    Connected to Windows XP 2600 x86 compatible target at (Mon Oct 14 00:57:16.890 2019 (UTC + 2:00)), ptr64 FALSE
    Kernel Debugger connection established.
    WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
    Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
    *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
    Executable search path is: C:\localsymbols
    Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
    Built by: 2600.xpsp.080413-2111
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    System Uptime: not available
    WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
    Mon
     Oct 14 00:57:19.218 2019 (UTC + 2:00): MM: Loader/HAL memory block
    indicates large pages cannot be used for 80D86000->821DEFFF
    Mon Oct 14 00:57:19.218 2019 (UTC + 2:00):
    Mon Oct 14 00:57:19.218 2019 (UTC + 2:00): MM: Disabling large pages for all ranges due to overlap
    Mon Oct 14 00:57:22.906 2019 (UTC + 2:00): AhciHwFindAdapter finishing
    Mon Oct 14 00:57:33.765 2019 (UTC + 2:00):
    *** Fatal System Error: 0x00000050
                                                 (0xB92602C0,0x00000000,0xB92F6548,0x00000000)

    Mon Oct 14 00:57:33.796 2019 (UTC + 2:00): Break instruction exception - code 80000003 (first chance)

    A fatal system error has occurred.
    Debugger entered on first try; Bugcheck callbacks have not been invoked.

    A fatal system error has occurred.

    Connected to Windows XP 2600 x86 compatible target at (Mon Oct 14 00:57:34.031 2019 (UTC + 2:00)), ptr64 FALSE
    Loading Kernel Symbols
    ...................................
    Loading User Symbols

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {b92602c0, 0, b92f6548, 0}

    *** ERROR: Module load completed but symbols could not be loaded for igxpmp32.sys
    *** No owner thread found for resource 8055b4e0
    *** No owner thread found for resource 8055b4e0
    *** No owner thread found for resource 8055b4e0
    *** No owner thread found for resource 8055b4e0
    Probably caused by : igxpmp32.sys ( igxpmp32+31548 )

    Followup: MachineOwner
    ---------

    nt!RtlpBreakWithStatusInstruction:
    8052b5dc cc              int     3
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: b92602c0, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: b92f6548, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 00000000, (reserved)

    Debugging Details:
    ------------------

    *** No owner thread found for resource 8055b4e0
    *** No owner thread found for resource 8055b4e0
    *** No owner thread found for resource 8055b4e0
    *** No owner thread found for resource 8055b4e0

    READ_ADDRESS:  b92602c0

    FAULTING_IP:
    igxpmp32+31548
    b92f6548 8b88c0821000                         mov     ecx,dword ptr [eax+1082C0h]

    MM_INTERNAL_CODE:  0

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  System

    TRAP_FRAME:  b9d13428 -- (.trap 0xffffffffb9d13428)
    ErrCode = 00000000
    eax=b9158000 ebx=e1394b70 ecx=00000001 edx=bb000000 esi=89ce30f0 edi=b9d1367c
    eip=b92f6548 esp=b9d1349c ebp=b9d13530 iopl=0         nv up ei ng nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
    igxpmp32+0x31548:
    b92f6548 8b88c0821000    mov     ecx,dword ptr [eax+1082C0h] ds:0023:b92602c0=????????
    Resetting default scope

    LOCK_ADDRESS:  8055b560 -- (!locks 8055b560)
    NTSDEXTS: Unable to resolve ntdll!RtlCriticalSectionList
    NTSDEXTS: Please check your symbols

    PNP_TRIAGE:
    	Lock address  : 0x8055b560
    	Thread Count  : 1
    	Thread address: 0x8a18f3c8
    	Thread wait   : 0x26b

    LAST_CONTROL_TRANSFER:  from 804f8df9 to 8052b5dc

    STACK_TEXT:
    b9d12f5c 804f8df9 00000003 b92602c0 00000000 nt!RtlpBreakWithStatusInstruction
    b9d12fa8 804f99e4 00000003 00000000 c05c9300 nt!KiBugCheckDebugBreak+0x19
    b9d13388 804f9f33 00000050 b92602c0 00000000 nt!KeBugCheck2+0x574
    b9d133a8 8052036a 00000050 b92602c0 00000000 nt!KeBugCheckEx+0x1b
    b9d13410 80544578 00000000 b92602c0 00000000 nt!MmAccessFault+0x9a8
    b9d13410 b92f6548 00000000 b92602c0 00000000 nt!KiTrap0E+0xd0
    WARNING: Stack unwind information not available. Following frames may be wrong.
    b9d13530 b92f2c6e 89ce3350 e14783b8 290a8000 igxpmp32+0x31548
    b9d13548 b952ce39 89ce3350 8a06dde0 000000dc igxpmp32+0x2dc6e
    b9d1367c b92c89cd 89ce3350 00000000 00000000 igxpmp32+0x267e39
    b9d1369c b92c0318 89ce3350 00000000 00000000 igxpmp32+0x39cd
    b9d138a0 b92c0c9a 89e82a20 89f2bc00 89f2bc08 VIDEOPRT!VideoPortFindAdapter2+0x3ec
    b9d138cc b92bac41 89e82a20 89f2bc00 89f2bc08 VIDEOPRT!VideoPortFindAdapter+0x7c
    b9d13a38 804ef18f 89ce3038 8a0559f0 b9d13ab4 VIDEOPRT!pVideoPortPnpDispatch+0x6ad
    b9d13a48 80592b63 b9d13ab4 8a16f3d8 00000000 nt!IopfCallDriver+0x31
    b9d13a74 80592be1 89ce3038 b9d13a90 00000000 nt!IopSynchronousCall+0xb7
    b9d13ab8 804f61ea 8a16f3d8 89f54960 00000001 nt!IopStartDevice+0x4d
    b9d13ad4 8059229b 8a16f3d8 89f54901 00000000 nt!PipProcessStartPhase1+0x4e
    b9d13d2c 8059276e 8a1b3ee8 00000001 00000000 nt!PipProcessDevNodeTree+0x1db
    b9d13d54 804f6996 00000003 8055b5c0 8056485c nt!PiProcessStartSystemDevices+0x3a
    b9d13d7c 8053876d 00000000 00000000 8a18f3c8 nt!PipDeviceActionWorker+0x170
    b9d13dac 805cff64 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
    b9d13ddc 805460de 8053867e 00000001 00000000 nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    igxpmp32+31548
    b92f6548 8b88c0821000    mov     ecx,dword ptr [eax+1082C0h]

    SYMBOL_STACK_INDEX:  6

    SYMBOL_NAME:  igxpmp32+31548

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: igxpmp32

    IMAGE_NAME:  igxpmp32.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  52eae6bc

    FAILURE_BUCKET_ID:  0x50_igxpmp32+31548

    BUCKET_ID:  0x50_igxpmp32+31548

    Followup: MachineOwner
    ---------

    1: kd> lm
    start    end        module name
    804d7000 806e5000   nt         (pdb symbols)          c:\symbols\ntkrpamp.pdb\7D6290E03E32455BB0E035E38816124F1\ntkrpamp.pdb
    806e5000 80705d00   hal        (deferred)
    b91d8000 b9235f00   update     (deferred)
    b9236000 b9258700   ks         (deferred)
    b9281000 b92b0e80   rdpdr      (deferred)
    b92b1000 b92c4f00   VIDEOPRT   (pdb symbols)          c:\symbols\videoprt.pdb\66CB8EA979A742EABCB14A11545D6EBE1\videoprt.pdb
    b92c5000 b953cc00   igxpmp32   (no symbols)
    b9585000 b959eb80   Mup        (deferred)
    b959f000 b95cb980   NDIS       (deferred)
    b95cc000 b9658600   Ntfs       (deferred)
    b9659000 b966f880   KSecDD     (deferred)
    b9670000 b9681f00   sr         (deferred)
    b9682000 b96a1b00   fltMgr     (deferred)
    b96a2000 b96e2000   storport   (deferred)
    b96e2000 b9707a00   dmio       (deferred)
    b9708000 b9726d80   ftdisk     (deferred)
    b9727000 b9737a80   pci        (deferred)
    b9738000 b97a6480   ACPI       (deferred)
    b98a8000 b98b1300   isapnp     (deferred)
    b98b8000 b98c2580   MountMgr   (deferred)
    b98c8000 b98d5200   VolSnap    (deferred)
    b98d8000 b98e5000   storahci   (deferred)
    b98e8000 b98f0e00   disk       (deferred)
    b98f8000 b9904180   CLASSPNP   (deferred)
    b9948000 b9954f00   i8042prt   (deferred)
    b9958000 b9961e00   intelppm   (deferred)
    b9968000 b9971f00   termdd     (deferred)
    b9b28000 b9b2cd00   PartMgr    (deferred)
    b9b58000 b9b5e280   kbdclass   (deferred)
    b9b60000 b9b65c00   mouclass   (deferred)
    b9cb8000 b9cbb000   BOOTVID    (deferred)
    b9d60000 b9d63c80   mssmbios   (pdb symbols)          c:\symbols\mssmbios.pdb\9940673F3B9A4BD682DF9D96A12A355C1\mssmbios.pdb
    b9da8000 b9da9b80   kdcom      (deferred)
    b9daa000 b9dab100   WMILIB     (deferred)
    b9dac000 b9dad700   dmload     (deferred)
    b9db4000 b9db5100   swenum     (deferred)

diderius6 has attached files to this post

- ⇗ igxpmp32.rar

#3043

XPLives

> Zitat von ⇗ schreiberstein im Beitrag ¶ #3041

> @XPLives
> I have just attempted booting with the iGPU completely disabled...
> Now I had 984MB vs 904MB of RAM.
> So no, the iGPU does not take away THAT much RAM.
> nVidia cards are not optimized for Apple Mac OS X. That is why Apple uses ATI/AMD exclusively these days.
> "emulated machine types" - on a hackintosh, you can choose a Mac hardware model. (such as iMac, MacMini, etc. and you specify their model identifier)
> Mac OS X behaves differently on different platform definitions (concerning power management, utilization of dedicated GPUs, even down to the number of available USB ports)
> Certain models expect the iGPU to be present as they offload certain tasks onto the iGPU. The iGPU is actually very efficient for something like JPEG rendering and other kinds of acceleration, as far as I have read.
> You may find more information on that in the aforementioned tonymacx86 thread concerning the Gigabyte Z390 Designare motherboard.
> Especially professional applications like FinalCut Pro X rely on the iGPU.
> It would be a waste not to utilize it. Do I need it? I actually tried to disable it and then my system was unable to display JPEGs and to perform other kinds of OS X specific magic like "quick look" previews of movies and images.
> And since the problem seems to lie somewhere else, I am not going to hate on the Intel HD graphics component of my system.
> It certainly is not using 3GB of RAM, otherwise I would notice that on Server 2003 as well. But there I had 31+GB available.
> It seems like Windows XP is unable to cope with something else, some small reserved portion of RAM. And instead of addressing the remaining RAM, it just quits at 904MB and calls it a day. But I have no clue how Windows XP memory mangement and detection works.
> With "constellation" I was referring to the 128GB ntoskrnl.exe and hal.dll hack: It had very obvious side effects on the system. Issues with I/O, stuttering, noticeable lag when navigating through explorer.exe, etc. All things that were not present on XP on 904MB and Server 2003 with 32GB PAE.
> Once I got either XP or Server 2003 running a bit more reliably, I will write a guide for my motherboard - since it bridges so many gaps. Windows XP support, 7 support, 10 support, Mac OS X support, ...
> It is also the last architecture that will be able to run Mac OS X 10.14 Mojave without incompatibilities - hence the last version that runs 32-Bit Mac apps from the mid 2000s natively.
> I hope this answers your questions, gentleman. :-)
> Cheers,
> schreiberstein
> EDIT: I will do the testing procedures that you specified. Perhaps the amount of available RAM might still change. Will keep you posted.

⇗ @schreiberstein
I hope you can try those BIOS settings not just DISABLED only.
You should check if your BIOS shows the Shared Video Memory Size RANGE as mine does. Did you try hitting ENTER on that option to see if it provides a window of memory sizes?
I did more testing and I found some interesting results which I had hoped you had done by now.
The most memory I could get using Server 2003 /NOPAE which simulates disabling PAE also reflects a similar enough memory cut off that XP SP2/SP3 does.
Using both my 1GB and 2GB PCIe video cards results in the same maximum OS memory free
3.21GB - I see this on my Ivy Bridge as well so this is consistent. Although my current Ivy Bridge is showing 3.44GB max memory in XP because it is using only 32MB.
[3.16GB] - Intel HD Graphics only - no PCIe card
DVMT Pre
32MB
DVMT Total
128MB
[2.91GB] - Intel HD Graphics only with PCIE card
DVMT Pre
32MB
DVMT Total
128MB
The PCIe card when installed uses up 0.25GB of memory.
[1.94GB] - Intel HD Graphics with PCIE card
DVMT Pre
1024MB
DVMT Total
MAX MB
As you can see 0.97 GB of memory was used setting it to 1024MB on mine.
1.94GB vs your 0.9GB? looks very similar about 1GB difference showing signals to me they might have increased your MAX VIDEO RAM setting to 2048MB which is why you are getting 904MB which looks exactly close to 1.0GB added.
Hopefully you can provide all 8 snapshots for me to compare. You shouldn't give up and skip to the end after disabling the Integrated Graphics. Even on Ivy Bridge the Intel HD Graphics does not disable with just one option I found. Some other options keep it enabled. And in certain causes if you want to use just the video card installed and no iGPU, you have to set the Memory Shared to AUTO and force PCIe slot as Primary video output.
Although I have a theory is either your BIOS is buggy or there is another setting you forgot to disable. Some BIOS have a MultiDisplay setting and without being in front of your computer to examine all the BIOS options it's hard for me to locate this. Also disabling the Intel iGPU you still have to set Primary Video output to a PCIe card remove any MultiDisplay sharing sometimes uses a different name on other motherboards.
Now I know this isn't going be favorable to you to even disable it but since you do require it for the MAC OS graphics emulation. But you never confirmed if it popped up further Memory Size range settings for your integrated graphics like it does on mine. If your BIOS doesn't show you a range from 32MB to 1024MB or 2048MB possibly in your BIOS (my guess). Then you have no other option and should choose to use Server 2003 modded to appear as XP, stick with XP but using a large Ramdrive with your pagefile stored on it, go back to XP SP0/SP1 if your programs work fine on the older versions, trying to flash back to the earliest BIOS version for your motherboard (maybe it uses less max memory or has more options that got removed), contacting your MB manufacturer and filing a bug/complaint case so it can be fixed. Since your is a Z390 it's still the latest and more likely to get support from them to fix it now properly. Or you can try a Z370 motherboard to see if the same thing occurs if you want to stay on the octacore which I assume you paid a lot like me and unlikely to return or sell used for a loss. Maybe the Z390 MB lineup is buggy? I know Intel rushed it to get the i9-9900K out so only you can report the problem to get it fixed by Gigabyte before they close their support window. This memory issue will not be fixed by ACPI modding as it is not related.
Worst but most compatible solution is go back to Sandy Bridge / Ivy Bridge if you want the easiest Hackintosh XP setup. At least everything works for XP and Hackintosh pretty much out of the box it seems. Even Gelip claims he used a laptop with Intel HD Graphics 3000 - Sandy Bridge era and the integrated graphics shared memory can be set to 32MB which is the best I've seen on a desktop. I'm not sure if the Laptop BIOS has this kind of refinement or dynamically allocated shared video memory. I do have a Sandy Bridge laptop somewhere here I might check. But most laptops I've seen have less options than desktops and are usually a fixed setting or dynamically allocated making it harder to gain more OS memory in XP when using integrated graphics. One possible fix I had thought about was modding the BIOS so the memory it used was above the 4.00GB region so XP gets the max memory possible which probably is 3.47->3.50GB on SP2/SP3.
Broadwell Z97 might also be another option but I'm uncertain if the iGPU compatibility for Hackintosh is fully supported. This you probably know or read about and can comment.
The next step up I'd probably suggest for still maintaining ACPI XP Compatibility is the X99 but since you made the comment that your iGPU is required for rendering despite using an internal graphics card and X99 I've just checked and all CPUs do not have any iGPU which in my opinion is a benefit since I usually will go with an internal PCIe card if I can since anything past Ivy Bridge the XP driver support stopped. So this leaves you skipping to SkyLake/Coffee Lake as a possible solution if your Z390 BIOS cannot be patched by Gigabyte or by someone here if you wanted to use the Intel HD 530 Graphics for your Hackintosh which I believe on my SkyLake the Max Video could be set to 1.5GB shared video memory and isn't buggy.
I fell asleep yesterday as I was testing my own Z370 the OS memory reported for my settings and had time to read you gave up your testing after disabling the integrated graphics so I could not compare the actual testing to mine as I wanted to see which would confirm if your BIOS is defective. If you can finish those tests it would be helpful.
Also is there another graphics card from nVidia or AMD that is the most compatible with Mojave or any earlier MAC OS X? I seem to recall some earlier Macs used GeForce 9 series graphics cards wouldn't those work better than the Intel IGPU for rendering?
Don't Give Up.
Chuse.

#3044

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #3042

> I do not find the exact place in igxpmp32.sys (see attached file) where this BSOD happens
> Probably caused by : igxpmp32.sys ( igxpmp32+31548 )
> ...
> FAULTING_IP:
> igxpmp32+31548
> b92f6548 8b88c0821000 mov ecx,dword ptr [eax+1082C0h]
> ....
> b92c5000 b953cc00 igxpmp32 (no symbols)

igxpmp32 PE image maped to b92c5000, fault opcode at b92f6548 => offset 31548
in Disassembler add this offset to image base (take from header) and you get fault adress

#3045

Mov AX, 0xDEAD

    1) If ((M64L == Zero)) / If (LEqual (M64L, Zero)) in _CRS of PCI0
    M64L is declared as external and stored in one of SSDTs as 64-bit field:

        Field (SANV, AnyAcc, Lock, Preserve)
           {
           ...
        M64L,   64,
           ...
           }

v5048 set first argument M64L as Buffer(wtf?) and this is wrong, it has ACPI 1.0 LEqual implementation and can compare only "Integer vs Integer"
2) NMAS = (NHLA + (NHLL - One)) / Add (NHLA, Subtract (NHLL, One), NMAS) in _INI of HDA Audio
Tricky expression, in one operation SUB + ADD on tree args, NHLL = 32b field, NHLA = 64b field, One - 64bit internal Integer
again, v5048 set first arg NHLA as Buffer and then try to sub/add integers, very dumb :)
In both cases we have 64bit field-as-argument and probably acpi.sys has bug with understand this thing

## Page 204

#3046

diderius6

⇗ @Mov AX, 0xDEAD
I found this place via Ida Pro at

    .text:10031548                 mov     ecx, [eax+1082C0h]

But what happens there, is not clear for me.
Windbg tells, that at this adress is

    mov ecx,dword ptr [eax+1082C0h]

this is not the same???
Dietmar
EDIT: May be, that Ida "dword ptr" just cancels. But even then I do not understand, wherin the error is.
What should be moved here to ecx ?
The adress, which is build is `eax+1082C0h = b92602c0`.
This is below the adress, from where the the driver starts. Is this the reason?

#3047 | kukonosau | ⇗ @diderius6 How to install XPx64 with modify acpi.sys? BSOD. XP started with any moments.
#3048 | diderius6 | ⇗ @kukonosau On Ryzen to install XP 64 is hard work and XP 64 is unstable on Ryzen platform Dietmar
#3049 | kukonosau | ⇗ @diderius6 Yes, it is unstable!!! BSOD everywhere: in our starting or in our working! But what is motherboard resources in Windows XP on Ryzen? Hal.dll and so on needed change in modify files?
#3050 | diderius6 | ⇗ @kukonosau Which XP you mean: XP SP3 32bit, or XP 64? Dietmar PS: On Ryzen board, no need to change hal.dll, the timer error happens only on newer Intel boards.
#3051 | kukonosau | ⇗ @diderius6 Motherboard resources in all system Windows XP. BSOD in Windows XP SP2 x64. It is unstable working.

#3052

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #2970

> > Zitat von ⇗ Andalu im Beitrag ¶ #2967

> > how can i have it too?

> This one is a private project, unfinished yet.
> Try to install Server 2003 Enterprise and Datacenter, which have PAE.
> If it works, you can get XP to work with the PAE hack.
> I'm just showing a proof that the drivers do support PAE.

Amount of ram correctly recognized in win2003. What is the next step?
Edit: I was wrong, damned hurry. As soon as the amd modded drivers are installed the mouse hangs immediately, the usb2 ports are power off and the usb3 ports don't recognize the devices. Same behavior as in XP.

#3053

daniel_k

> Zitat von ⇗ dencorso im Beitrag ¶ #3033

> @daniel_k: Does the hal5687_timer_patch.rar you posted some posts agop just have the timer patch, or does it include the > 4 GiB patch, too?

Yes, it includes the PAE patch, based on the one from Dibya.
PAE has serious compatibility issues, specially with modern platforms.
To make things worse, that patch is badly coded, there is a missing check, although it doesn't seem to help with anything.

#3054

daniel_k

Did some tests today, with Server 2003 and found something interesting, which I'll call it Fake PAE
The most interesting thing is that is can be applied to XP with the same results!
Did some preliminar tests and it seems to work just fine.
You can't have more than 4Gb of RAM, but the available RAM is increased dramatically.
Now I have 3.7Gb available, before there was only 2.97 Gb.
The best part of it: no compatibility issues!
daniel_k has attached images to this post ⇗ RAM.JPG

#3055 | infuscomus | ⇗ @daniel_k can dibyas RAM patch be fixed?
#3056 | XPWELL64 | I'm busy but on friday I'll mod igpu drivers.
#3057 | XPWELL64 | XP64: I turned on my asus k555lb with XP64. This PC booted into windows at 11th startup.

#3058

Mov AX, 0xDEAD

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #3046

> The adress, which is build is eax+1082C0h = b92602c0.
> This is below the adress, from where the the driver starts. Is this the reason?

> Zitat

> PAGE_FAULT_IN_NONPAGED_AREA (50)
> Invalid system memory was referenced.

addresses may be in any place in memory because drivers allocate many-many dynamic random memory chunks
in you case problem with eax, i think eax must be pointed to begin of some big buffer (more than 1082C0h bytes) but pointed to wrong memory

#3059

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #3054

> You can't have more than 4Gb of RAM

limitation of badly HalInitSystem or MmInitSystem ?

#3060

dencorso

⇗ @Mov AX, 0xDEAD: I think you'll enjoy reading the pages below:
⇗ http://www.geoffchappell.com/notes/windo...ense/memory.htm
⇗ https://www.remkoweijnen.nl/blog/2009/06...y/#comment-1688
⇗ https://www.remkoweijnen.nl/blog/2008/11...rnals/#more-140
⇗ https://web.archive.org/web/201310041608...al-perspective/

## Page 205

#3061

diderius6

Hi,
has anyone tested the asl.exe Version 5 tool,
if it works under XP?
And if not, can this be changed?
This would be nice for to load DSDT tables to registry.
By the way I noticed, that for to upload a DSDT with asl.exe,
you have to change the revisionsnumber of the DSDT to a higher value, than DSDT in your Bios has.
This can be done with a simple hack in the dsdt.aml it is one Byte at place 08 , there 02 -> 03 (version 2 to version 3 of the DSDT table).
And you have to update your checksum of this dsdt.aml (-1).
This asl.exe version 5 does not crash with newer ACPI
Dietmar
PS: I cant install the WDK 8.1. Can somebody sent me the asl.exe Vers. 5 from there?
It should be in path of the WDK Tools\x86\ACPIVerify
also in WDK 10.
EDIT: Jessa, I got it:))!
I integrate its own DSDT (with versionsnumber of DSDT 2->3) with asl.exe Version 5 on the Q1900m board.
Works.
C:\>asl /loadtable dsdt.aml
Microsoft ACPI Source Language Assembler Version 4.0.0NT [Aug 1 2014, 18:35:18]
Copyright (c) 1996,2009 Microsoft Corporation
Compliant with the ACPI 5.0 Specification
Table overloading succeeded. This will only be active when testsigning is enable
d.
C:\>
I there any testsigning on XP? Or does it work in any case?
EDIT2: The asl.exe version 5 works on XP SP3 for to upload DSDT table.
diderius6 has attached files to this post

- ⇗ asl5.rar

#3062

Mov AX, 0xDEAD

del

Found today bug in PatchPAE3, when it patch hal.dll, it allocate dma-buffers with limit of memory = MAX
in worst case it got memory above 4GB and then try to use it to dma transfers with 32b-only devices.
WinXP's HAL with last SPx doesnt support dma-64, so patch to hal.dll is unnecessary and may crash windows
patch to ntoskrml.exe seem OK, just remove two limitations of phys memory

#3063 | Andalu | I tried again to install Windows 2003 Server R2 SP2 Enterprise and finally I see for the first time in my B250M-Pro4 board both the total amount of ram correctly recognized and the USB3 working fine even after a shutdown. I would like to get the same on XP using the ram that exceeds 4GB as a ramdrive but before buying the memory I need, what can I try?

#3064

dencorso

⇗ @Andalu: the Gavotte Ramdisk is the way to go. the correct version to use (the latest) is attached to my post at reboot.pro which link is below.
⇗ http://reboot.pro/topic/4064-gavottes-rramdisk/?p=52696
⇗ https://msfn.org/board/topic/176356-simp...comment=1147522
However for maximum stability, you should also set HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\DisablePagingExecutive = 1, see:
⇗ https://msfn.org/board/topic/177110-wind...comment=1145279

#3065

Andalu

⇗ @dencorso
Thanks for the links ;) I used Gavotte until two years ago. I need to use more ramdisks than one only. Currently, on my haswell system with 32GB of ram, I'm using 4 or more ramdisks of which three load at boot. My intention is to use 64GB on XP. Moreover, the software license is for two systems, at the moment I'm using only half of it :)
P.S.: the value in the registry is already set to 1 ;)

#3066

daniel_k

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3062

> Found today bug in PatchPAE3, when it patch hal.dll, it allocate dma-buffers with limit of memory = MAX
> in worst case it got memory above 4GB and then try to use it to dma transfers with 32b-only devices.
> WinXP's HAL with last SPx doesnt support dma-64, so patch to hal.dll is unnecessary and may crash windows
> patch to ntoskrml.exe seem OK, just remove two limitations of phys memory

Yeah, I noticed that.
Patching hal.dll does result in random crashes.

#3067 | schreiberstein | ⇗ @daniel_k Any chance youre gonna share some of your FakePAE magic for others to test, or is it too experimental for now? It would be interesting to see if it could make a difference my system, at least in my opinion, haha. Cheers schreiberstein :)

#3068

daniel_k

Let me explain what I've found.
Windows 2003 has many licensing presets (which affects PAE and limits RAM available).
One of them does something interesting: enables PAE, but limits RAM to 4Gb.
The result? RAM is mapped in a more effective way so that more RAM is available.
At the same time, as it is limited to 4Gb, there are absolutely no issues with drivers or specific hardware, which is great for most of us.
I've wrote a small utility to patch all kernel files, should support all languages and all kernel versions 5512 (SP3) and later:
ntkrnlmp.exe - Multiprocessor Kernel
ntoskrnl.exe - Uniprocessor Kernel
ntkrpamp.exe - Multiprocessor PAE Kernel
ntkrnlpa.exe - Uniprocessor PAE Kernel
To use it, copy all kernel files (found in SP3.CAB) and this utility to the same folder.
Usage: winxppae [/4GB | /ALL]
/4GB Enables PAE limiting RAM to 4Gb to avoid stability issues.
/ALL Enables PAE with unlimited RAM, may have stability issues.
You may test the files on a running system by replacing the files from another OS (otherwise File Protection will restore the files).
In this case, pay attention to the filenames, on multiprocessor systems, rename ntkrnlmp.exe to ntoskrnl.exe and ntkrpamp.exe to ntkrnlpa.exe.
Or integrate them on the CD (rebuilding SP3.CAB and repacking ntkrnlmp.ex_ and ntoskrnl.ex_).
No need to include a /PAE switch in boot.ini, as this works just like on Server 2003.
As I've patched the files properly, ntoskrnl.exe automatically chainloads the PAE kernel, ntkrnlpa.exe.
PS: Only supports Windows XP SP3. Another version supporting Server 2003 will be released later.
PS: Updated 1.1 version /4GB and /ALL logic was reversed. Fixed.

daniel_k has attached files to this post

- ⇗ WinXPPAE.rar

#3069

infuscomus

⇗ @daniel_k
thanks!
do we load winxppae in autoexec.bat? or how do we use it?
edit: nevermind, figured it out
edit2: testing in VMWare VM with 8GB RAM assigned to it - applying the /4GB option changes available RAM from 3GB to 8GB - is this expected behavior?
can you add in an option to remove the patch?

#3070 | infuscomus | ⇗ @Andalu are you still having USB trouble with XP?

#3071

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #3066

> Yeah, I noticed that.
> Patching hal.dll does result in random crashes.

I was wrong about bug/dma64 in hal.dll patch, allocating still in <4Gb range, so this place is OK
Another place inside HAL is not match win2003:
winxp sp2+ logic:

     if ScatterGather=1 {
               no_need()
     }

win2003 sp2 logic:

     if ScatterGather=1 {
       if (PhysicalMemoryMayAppearAbove4GB=1 & Dma64BitAddresses=0)
               we_need_mapregisters()
         else
               no_need()
     }

winxp sp2 + "patch" logic:

     we_need_mapregisters() in any case

as I understand forcing mapregisters means dma double-buffering.
MS told this is not problem, just slowdown because additional memory tranfers.

#3072

daniel_k

> Zitat von ⇗ infuscomus im Beitrag ¶ #3069

> edit2: testing in VMWare VM with 8GB RAM assigned to it - applying the /4GB option changes available RAM from 3GB to 8GB - is this expected behavior?
> can you add in an option to remove the patch?

Oops, sorry.
Settings /4GB and ALL were reversed. Fixed.
Please try it again.
Maybe I can add that option, but backing up the files is easier and faster.

#3073 | infuscomus | ⇗ @daniel_k awesome! works correctly now I think it would be a good idea to have the program automatically make backups of the files it modifies, you can't always assume the user has made a backup.
#3074 | daniel_k | Didn't try it before on VirtualBox. Glad it works! From 3.32Gb to 3.83Gb! Let's hope it helps ⇗ @schreiberstein too! daniel_k has attached images to this post ⇗ NOPAE.JPG ⇗ 4GBPAE.JPG

#3075

Mov AX, 0xDEAD

⇗ @daniel_k

> Zitat von ⇗ daniel_k im Beitrag ¶ #3054

> Now I have 3.7Gb available, before there was only 2.97 Gb.
> The best part of it: no compatibility issues!

I think you still have usual "PAE+PhysMem_above_4Gb", check e820 table, recovered 1Gb accessable only at HIGH phys adresses (>4Gb), so if some badly driver alloc this memory and uses for communicating with hardware you'l get same compatibility issues

## Page 206

#3076 | diderius6 | ⇗ @daniel_k Just put only 4 Gbyte ram in, and show again about free ram Dietmar

#3077

diderius6

On the Q1900m board, the Celeron CPU J1900 (soldered on socket all in one chip SoC),
I can install MPS Multiprocessor which shows also (as on acpi) 4 cpu cores, because this chip has 4 cores
and no Hyperthreading. On this Bios is an extra MPS table, on the Lenovo Flex 10 is no MPS table as RW-everything tells.
In MPS the sound works. Interesting, from where the devices get their information on MPS,
because no acpi.sys there, which looks at DSDT table. But the DSDT table is still needed,
compi does not start, when you delete DSDT or give fake empty DSDT.
I will make a speed comparisation ACPI against MPS (all Multiprocessor).
With full ACPI, strange things happen on this board:
Windbg via COM1 runs only correct in Safe Mode (F8) and no sound.
A yellow questionmark is at partmgr in Device Manager. This I do not understand at all,
because without loaded partmgr.sys the compi does not start but it starts
Dietmar
PS: In MPS there are 2 yellow marks at pci-to-Pci bridge, reclaiming not enough free resources
even the IRQs from MPS go up to 128 and noone is double.
This may be a hint, what is really going on in the SoC, may be something is shared there.
All boards with such a SoC cpu have absolut identic devices, because they are all integrated in this SoC chip.
This is very nice, when you compare compis with the same SoC cpu.
I do not like, that I can not change the cpu. But I think, that there is no cheaper and better board today on the market.
It is to 100% silent, passiv cooling and SSD, power consumption around 10 Watt.
Now I just get 155 updates from Posready^^.
EDIT: Now I have also sound on full ACPI Multiprocessor XP SP3 on the Q1900m board. For this I have to disable "Microsoft UAA-Bustreiber für High Definition Audio"
in Device Manager and after this to enable "Microsoft UAA-Bustreiber für High Definition Audio" again, crazy. It has to do with not enough resources. USB2, 3, Lan, sound works now there. The only device is the integrated GPU, which does not work
under XP SP3 even I make hack. Windbg works now also normal, after I deactivated the 2 pci-to-Pci bridges, reclaiming not enough free resources. Now I benchmark full ACPI Multiprocessor against MPS Multiprocessor.
I use for this Nvidia GT 730. The bottleneck is here the CPU J1900.
3DMark2001 Acpi: 17347 Cinebench 11.529: 1.37
3DMark2001 MPS: 15739 Cinebench 11.529: 1.33
So, Acpi is faster than MPS, even I do not know why. 1440 HD Video runs normal.
Commander Keen 4 runs in full screen modus^^. Prime95 and other Benchmarks all together show: XP SP3 runs absolut stable on the Q1900m board in full ACPI Multiprocessor mode.
Hihi:
"Intel ® Bay Trail platform does not support:
Win XP Pro 32bit
Windows Embedded Standard 2009 (XPe SP3) 32bit "
And just for fun: I do pur USB boot on the Q1900m board via USB3 port and the nice driver from ⇗ @daniel_k , so
no more problems with iastor or storahci^^
⇗

#3078

Mov AX, 0xDEAD

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3071

> winxp sp2 + "patch" logic:

>      we_need_mapregisters() in any case

> as I understand forcing mapregisters means dma double-buffering.
> MS told this is not problem, just slowdown because additional memory tranfers.

Edit: VIA USB3 drivers/WDF can't live with forced mapregisters, so WinXP's HAL need exact w2003 logic

#3079

Andalu

> Zitat von ⇗ infuscomus im Beitrag ¶ #3070

> @Andalu
> are you still having USB trouble with XP?

No good news, everything as before. The USB3 function works fine exclusively on my Skylake board but only with no PAE patch installed. Applying any of the them, all the usb ports do not work (both 2.0 and 3.0). Only on win2003 the total amount of ram and the USB3 'coexist peacefully'.

#3080

Mov AX, 0xDEAD

Fixed PAE patch to windows xp halmacpi.dll sp3 (v 5.1.2600.5512 eng)

    Optional:
    1DD03: 6a 10 68 00 00 00 01 53 c7 05 c4 32 02 80 40 00 00 00 be 00 00 01 00 =>
           6a 30 68 FF FF FF FF 53 c7 05 c4 32 02 80 00 40 00 00 be 00 00 03 00

    Optional if you use ISA Devices like onboard Floppy controller :):
    1DD03: 6a 10 68 00 00 00 01 53 c7 05 c4 32 02 80 40 00 00 00 be 00 00 01 00 =>
           6a 30 68 00 00 00 01 53 c7 05 c4 32 02 80 00 40 00 00 be 00 00 03 00

    Critical:
    17815: 80 3D B8 32 02 80 00 75 0A =>
           38 4F 0B 75 12 90 90 90 90

    205B4: 17 38 => 00 00

    + checksum fix

#3081

Andalu

⇗ @daniel_k
I tried your patch on my B250M-Pro4. I did it in the following way:
I extracted the files from SP3.cab (ver. 5.1.2600.5512) of the XP SP3 32bit installation CD, italian version:
ntkrnlmp.exe (SHA1:9A7CD76FAEE28CE009DBE7A367A1CCA6C1532B2E)
ntkrnlpa.exe (SHA1:D35591D175190FDAC795BC0ADDBF3A0D0EB6EDBE)
ntkrpamp.exe (SHA1:437844ED5993F411C32A207781BE463D83122ADE)
ntoskrnl.exe (SHA1:6580C7DDDF31E5E12FBD7EFE87C5FCA36EE68736)
I copied them in the "test" folder with the 'WinXPPAE' exe file ver. 1.1
Then I renamed the files:
from ntkrnlmp.exe to ntoskrnl.exe
from ntkrpamp.exe to ntkrnlpa.exe
But, in my case, that was not necessary because the same versions (with identical SHA1) of the renamed files are already present in the system32 folder:
ntkrnlpa.exe (SHA1:437844ED5993F411C32A207781BE463D83122ADE)
ntoskrnl.exe (SHA1:9A7CD76FAEE28CE009DBE7A367A1CCA6C1532B2E)
The "WinXPPAE.exe /4GB" command launched in a dos window:
⇗
nothing changed on reboot, only 2.44GB recognized as before:
⇗
Even with a fresh XP installation with the renamed and repacked files into sp3.cab, driver.cab and i386 folder the patch doesn't work.
Where did I go wrong?

#3082

infuscomus

⇗ @Andalu
there is a driver package made by ⇗ @lsmlcx -
⇗ [TOOL] Sysceo MassStorage and USB Drivers Installer (with universally usable XP/2003 drivers)
in it there is an intel USB 3.0 driver for XP
in
CeoMSX_20190910\USB\WinXPx86\Intel\SysCeoUsb3.x
try it out, hopefully it works for you

#3083

daniel_k

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3075

> @daniel_k
> I think you still have usual "PAE+PhysMem_above_4Gb", check e820 table, recovered 1Gb accessable only at HIGH phys adresses (>4Gb), so if some badly driver alloc this memory and uses for communicating with hardware you'l get same compatibility issues

Huh, I see.
For now it works just fine.
Will see how far it goes like that.
There was a "conflict" between VGA.SYS and AMDXHC.SYS (Intel modded driver) in PAE mode.
If AMDXHC was loaded, the VGA driver wouldn't work, there was no display in the GUI Setup phase.
If I remove AMDXHC during Setup, installation completes succesfully. Then I install GeForce driver, all OK.
As soon as I install the AMDXHC driver, legacy DOS apps still work, but can't switch to full screen mode, as it gives me an error in NTVDM. Because of the driver "conflict", Windows cannot switch to VGA mode.

#3084 | daniel_k | ⇗ @Mov AX, 0xDEAD, thanks for sharing the patch with us. Will test later. Can this be used in a generic ISO? Does this patch may cause issues on a system which does not need PAE (4Gb or less)?

#3085

daniel_k

> Zitat von ⇗ infuscomus im Beitrag ¶ #3082

> @Andalu
> there is a driver package made by @lsmlcx -
> ⇗ [TOOL] Sysceo MassStorage and USB Drivers Installer (with universally usable XP/2003 drivers)
> in it there is an intel USB 3.0 driver for XP
> in
> CeoMSX_20190910\USB\WinXPx86\Intel\SysCeoUsb3.x
> try it out, hopefully it works for you

Won't help because that is the same driver modded by me.
The guy just changed the resource files, changed the hub device IDs to look like Intel's and signed the files.
Just love those kind of people.

#3086 | infuscomus | ⇗ @daniel_k woah! seriously?! I wasn't aware of this, good to know.
#3087 | infuscomus | ⇗ @Andalu did you put the patched ntoskrnl/ntkrnlpa.exe files into c:\windows\system32 ?

#3088

daniel_k

⇗ @Andalu, just downloaded the Italian XP SP3 ISO, extracted the files and patched them. Absolutely no issues.
ORIGINAL

    ntkrnlmp.exe = 9a7cd76faee28ce009dbe7a367a1cca6c1532b2e
    ntkrnlpa.exe = d35591d175190fdac795bc0addbf3a0d0eb6edbe
    ntkrpamp.exe = 437844ed5993f411c32a207781be463d83122ade
    ntoskrnl.exe = 6580c7dddf31e5e12fbd7efe87c5fca36ee68736

PATCHED

    ntkrnlmp.exe = 742fcf126111532187d4a2861c8b45f882757850
    ntkrnlpa.exe = 7f1865311cb5fac8ee37973d13a0a562d5902164
    ntkrpamp.exe = 39ca749c1988e469ea2b6c46eafd6537734fdcce
    ntoskrnl.exe = 08b39d98400282412979840f0f91eb813ea95ddf

- Create two folders: ORIGINAL and PATCHED
- Extract all kernel files from SP3.CAB to both folders.
- Copy WinXPPAE.exe to the PATCHED folder and run WinXPPAE /4GB
- Compare files from both folders or calculate their hashes.
On a live system, in order to replace protected system files, you need to:
- rename \WINDOWS\Driver Cache\i386\sp3.cab
- delete kernel files from \WINDOWS\system32\DllCache (see list above)
- backup original files \WINDOWS\system32\ntoskrnl.exe and \WINDOWS\system32\ntkrnlpa.exe
- copy patched files, overwriting the originals.
- Windows File Protection will ask you for the XP Disc to restore the files. If you don't receive this message, you did something wrong.
If you don't follow these steps, File Protection will restore the files silently. An event can be found in Event Viewer, though,
You can also replace the files if you have a dual boot setup. For instance, boot Windows 7 and copy the files to the Windows\System32 folder.

#3089 | lsmlcx | ⇗ @daniel_k I got the same problem. But not in PAE mode.

#3090

gordo999

> Zitat von ⇗ daniel_k im Beitrag ¶ #3085

> Won't help because that is the same driver modded by me.

Are you the same daniel_k from Creative driver mod fame? If so, good to see you here and thanks for all your good work in that arena.
Trying to get Win XP going on an 8th generation Asus B360M so I'll be reading through this thread for hints then posting some questions.

## Page 207

#3091

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #3046

>     .text:10031548                 mov     ecx, [eax+1082C0h]

> But what happens there, is not clear for me.
> Windbg tells, that at this adress is

>     mov ecx,dword ptr [eax+1082C0h]

> this is not the same???

@diderius6....I am a bit rusty but as I recall, the [...] brackets represent a pointer. It tells you to load the value at address [eax+1082COh] to ecx. The windbg version is redundant but wdbg has strange ways of representing pointers because it uses the MASM as well as the C++ addressing modes. Gives me a headache.

> Zitat von ⇗ diderius6 im Beitrag ¶ #3046

> What should be moved here to ecx ? The adress, which is build is eax+1082C0h = b92602c0.
> This is below the adress, from where the the driver starts. Is this the reason?

I think the value B92602C0 should be moved to ecx. If that is an address it's a system address and is likely the address of a system module or an address within a system module.
ps. if it's an address, you can tell by following the code a bit to see if a call is made to that address.

#3092 | petter1392 | I'm also getting ⇗ Err_Cache_Miss error after the windows update.

#3093

Pill Monster

PAE is always enabled, however it has no effect by itself after SP2 because MS included a boot time certificate check which disables PAE on "Client Edition".
Unless you pay them lots of money, you don 't see heaven's gate.
M$ & Intel didn't like it when A64 was released and suddenly hello AMD owners could install 8GB of RAM on their NForce3 939 boards with XP installed and use it all.
P.S. ⇗ @daniel_k
Thanks for all the work, I'm still rocking an X-Fi Fatal1ty with your last driver package. :)

#3094

Andalu

> Zitat von ⇗ infuscomus im Beitrag ¶ #3087

> @Andalu
> did you put the patched ntoskrnl/ntkrnlpa.exe files into c:\windows\system32 ?

Your guess is right. I still can't realize how I didn't understand that it was necessary to copy the two kernel files after applying the patch.
Evidently my age is going too fast....
The USB3 AMDXHCI_FINAL by daniel_k drivers work fine even if only on my skylake board. Installing the AMD_XHCI_For_Intel_XP_x86_x64_20191012 by lsmlcx nothing changed but the shutdown stops working, so no good for me.
Now the problem is about the 'coexistence' of usb3 and the recognition of the entire ram. I do not lose hope, probably ⇗ @daniel_k does a magic and pulls a rabbit out of the hat. I believe it ;)

#3095 | Andalu | ⇗ @daniel_k Sorry for my oversight. Once again I have to thank you for your kindness and for the time you have dedicated to my problem. As I reported in my previous post, it was my mistake, your patch installs without problems. Thanks again for your great work ;)
#3096 | diderius6 | ⇗ @Doc.Brown Before you transfer XP SP3 from another working compi to the Gene XI board, disable all USB there Dietmar

#3097

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #3084

> @Mov AX, 0xDEAD, thanks for sharing the patch with us. Will test later.
> Can this be used in a generic ISO?
> Does this patch may cause issues on a system which does not need PAE (4Gb or less)?

this patch need only for systems were 4GB or more RAM + ntoskrnl's pae_licensing_patch was activated. If there is less memory or pae_licensing is original, patch still works, but not optimal, it always think that PC has more 4GB phys adresses and make special actions for dma32-only devices.
for generic iso patch need additional check to match w2003 logic, but there is no space, so need more complex inject like JMP FAR PATCH/..Patch logic../ JMP FAR BACK

#3098

Mov AX, 0xDEAD

I've played with HAL logging of DMA Request on Skylake H110 and IvyBridge notebook (both has 4GB RAM, pae_license_patch activated):
Skylake:
Intel iastor.sys 11.2.0.1006 - only 32bit DMA allowed
VIA USB3.0 xhcdrv.sys 6.1.7600.4402 - 64bit DMA, many requests
AMD USB3.0 hacked amdxhc.sys 1.1.0.145 - 64bit DMA
IvyBridge:
Intel iastor.sys 11.2.0.1006 - only 32bit DMA allowed
MS USB2.0 usbport.sys 5.1.2600.6437 - only 32bit DMA allowed
after installing hal_pae_patch on IvyBridge, it fix "USB 2 Root Hub has no enough power bla-bla" problem

#3099

daniel_k

> Zitat von ⇗ gordo999 im Beitrag ¶ #3090

> > Zitat von ⇗ daniel_k im Beitrag ¶ #3085

> > Won't help because that is the same driver modded by me.

> Are you the same daniel_k from Creative driver mod fame? If so, good to see you here and thanks for all your good work in that arena.
> Trying to get Win XP going on an 8th generation Asus B360M so I'll be reading through this thread for hints then posting some questions.

Yep, that's me! Glad to help!
At this point, we've solved most issues.
Should be easy to get it working, many people contributing here!

#3100

daniel_k

⇗ @Pill Monster
Your nick seems familiar. Which forum are you more active in?
You seem to be everywhere.
Glad to know my packs are still helping you!
Back to the subject, from the compatibility issues we've seen, Microsoft was right to some degree.
Some drivers are poorly written, which may lead to data corruption, something I consider unacceptable.

#3101 | daniel_k | ⇗ @Andalu, don't worry, it happens. But did help you somehow? How many RAM was available before and after the patch?
#3102 | skullteria | Well, my edited kernel of Windows XP has support until 128 GB. Please test in virtual Machine before: ⇗ https://github.com/Skulltrail192/One-Cor...er%20Standalone

#3103

daniel_k

⇗ @Mov AX, 0xDEAD
I see that you've changed this:

    .80027815: 803DB832028000                 cmp          b,[0800232B8],0
    .8002781C: 750A                           jnz         .080027828

into this:

    .80027815: 384F0B                         cmp          [edi][00B],cl
    .80027818: 7512                           jnz         .08002782C

Would it be a generic patch (for system with less/more than 4GB and PAE enabled in kernel) if I manage to include both original and your checks together?
Something like:

    cmp          b,[0800232B8],0
    jnz         .080027828
    cmp          [edi][00B],cl
    jnz         .08002782C

What are you thoughts on this? Would this order of checks be correct or the other way around?

#3104

daniel_k

> Zitat von ⇗ daniel_k im Beitrag ¶ #3083

> There was a "conflict" between VGA.SYS and AMDXHC.SYS (Intel modded driver) in PAE mode.
> If AMDXHC was loaded, the VGA driver wouldn't work, there was no display in the GUI Setup phase.
> If I remove AMDXHC during Setup, installation completes succesfully. Then I install GeForce driver, all OK.
> As soon as I install the AMDXHC driver, legacy DOS apps still work, but can't switch to full screen mode, as it gives me an error in NTVDM. Because of the driver "conflict", Windows cannot switch to VGA mode.

What are you thoughts on this?
As the VGA driver works when the AMDXHC is not installed, would you say the issue is with the later?
If so, any possibilities of fixing the driver?
What did you use to do the HAL logging of DMA Requests? Debugger?

#3105

daniel_k

⇗ @Mov AX, 0xDEAD
The actual code that limits RAM is in the kernel.

    .005D1840: 6A07                push         7
    .005D1842: 8BF0                mov          esi,eax
    .005D1844: 895DFC              mov          [ebp][-4],ebx
    .005D1847: 897DF8              mov          [ebp][-8],edi
    .005D184A: E833FEE8FF          call         ExVerifySuite
    .005D184F: 3C01                cmp          al,1
    .005D1851: 7500                jnz         .0005D1853
    .005D1853: 397E64              cmp          [esi][064],edi
    .005D1856: 7509                jnz         .0005D1861
    .005D1858: C745FC00000001      mov          d,[ebp][-4],001000000 -> Number of 4kb pages
    .005D185F: EB44                jmps        .0005D18A5

0x1000000 x 4 = 0x4000000 = 64Gb
By fine tuning it, managed to get 4.78Gb of RAM with everything working.
Anything above this, DOS apps can't enter full screen (VGA.SYS).
At 5Gb, AMDXHC driver stops working (actually USB devices are recognized as Unknown Devices with zeroed device ids).
Above 5.5Gb, AMDXHC driver works again, but DOS apps can't enter full screen (VGA.SYS) remain, up to 15.9Gb.
Thoughts?
PS: Sorry for so many questions, but you're the only one more technically skilled here.

daniel_k has attached images to this post ⇗ 478GB.JPG

## Page 208

#3106 | daniel_k | ⇗ @schreiberstein Did you manage to try my 4Gb patch? Any improvement?

#3107

schreiberstein

⇗ @daniel_k
Not yet, unfortunately.
I hope I will have some time tonight.
I will let you know the results.
By the way, I think the AMD XHCI driver causes issues on my system as well.
On both XP and 2003. It randomly stops working after reboots.
And then the IDs are also zeroed, as mentioned before.
Is there a way to use a different patched driver for the Z390 platform (like VIA), or is AMD the only option? Whenever the drivers are loaded correctly, the NTVDM does not work at all. No 16 Bit. Not even windowed. No Win16 applications.
I will also conduct the Intel GPU memory adjustment tests to see if it changes my available amount of RAM from 904 to something higher.
Cheers,
schreiberstein

#3108 | daniel_k | ⇗ @schreiberstein Unfortunately, AMD is really the only option. XP with no PAE also has issues? If so, things are more complicated for you.

#3109

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #3101

> @Andalu, don't worry, it happens.
> But did help you somehow? How many RAM was available before and after the patch?

Your /4GB patch works fine. The system recognizes correctly 4GB of ram, before it was 2.2GB.
Applying the /ALL option, the total amount of ram is correctly recognized but I got the identical issues happened with the chinese and the Dibya's patches: on reboot the usb2 and usb3 ports don't recognize anything. Also the usb mouse becomes an unknow device. In details, the usb2 ports don't seem to be powered anymore while the usb3 ports seem to have an altered power as the external hard disk's led is always on. Also the shutdown no longer works.

#3110

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #3105

> @Mov AX, 0xDEAD
> The actual code that limits RAM is in the kernel.

Yes, this is PAE_Licensing check, it trim physical memory adresses to some value, so adresses above limit will be erased even on 4GB RAM, because bios remap ram to two parts - one to 0<->~2.5-3.5Gb and second to 4.0<->4.x, so second part is lost

           //
        // If properly licensed for PAE (ie: DataCenter) and booted without the
        // 3gb switch, then use all available physical memory.
           //

        if (ExVerifySuite(DataCenter) == TRUE) {

                   //
            // Note MmVirtualBias has not yet been initialized at the time of the
            // first call to this routine, so use the LoaderBlock directly.
                   //

            if (LoaderBlock->u.I386.VirtualBias == 0) {   // /3GB stuff

                           //
                // Limit the maximum physical memory to the amount we have
                // actually physically seen in a machine inhouse.
                           //

MaxPage = 8 * 1024 * 1024; // in 2000's max 32GB :)

> Zitat von ⇗ daniel_k im Beitrag ¶ #3105

> Anything above this, DOS apps can't enter full screen (VGA.SYS).
> At 5Gb, AMDXHC driver stops working (actually USB devices are recognized as Unknown Devices with zeroed device ids).
> Above 5.5Gb, AMDXHC driver works again, but DOS apps can't enter full screen (VGA.SYS) remain, up to 15.9Gb.

if you have time, try to force usb3.0 device to be only 32-bit dma in amdxhc.sys, maybe this helps:

    000323E7:
    push    ebx             ; int
    and     dl, 1
    movzx   eax, dl
    push    eax             ; Dma64,  SET IT TO ZERO
    push    esi             ; int
    push    dword ptr [esi+20h] ; PhysicalDeviceObject
    call    sub_3299C
    mov     [ebp+var_1C], eax
    test    eax, eax
    jge     short loc_3240E

#3111

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #3103

> @Mov AX, 0xDEAD
> Would it be a generic patch (for system with less/more than 4GB and PAE enabled in kernel) if I manage to include both original and your checks together?
> Something like:

>     cmp          b,[0800232B8],0
>     jnz         .080027828
>     cmp          [edi][00B],cl
>     jnz         .08002782C

> What are you thoughts on this? Would this order of checks be correct or the other way around?

generic patch like w2003 logic:

    // cmp          b,[0800232B8],0  ; original opcodes

    if _HalpPhysicalMemoryMayAppearAbove4GB==0 go original    //  if <4gb , skip new checks      ; need reloc or PIC tricks
    if  [edi+0B]==0 go loc_8002782C                  // if DeviceDescription.Dma64BitAddresses=0 go to calculating mapbuffers

    original:
    cmp          b,[0800232B8],0                     // obsolete, check low-end system with 16Mb memory only
    check for BUSTYPE=2 or 5
    // now all is OK, we dont need mapbuffers, so set ebx=0 & go next

    loc_8002782C: // calculating mapbuffers
    ..
    next:
    ...

#3112

Mov AX, 0xDEAD

⇗ @daniel_k

> Zitat von ⇗ daniel_k im Beitrag ¶ #3104

> As the VGA driver works when the AMDXHC is not installed, would you say the issue is with the later?
> If so, any possibilities of fixing the driver?
> What did you use to do the HAL logging of DMA Requests? Debugger?

I dont know why usb3 conflict with vga, they dont use same resources (like IOTR bug), but problem with amd because vga driver is simple & well tested. i use amdxhci without any problem with geforce, if i delete nvidia driver, standart video works well, full-screen too, but i have only 4GB ram.
I use remote debugging with windbg, breakpoints to hal is enough for me, with simple lan cables debugging is funny as never before )

#3113 | daniel_k | ⇗ @Andalu To obtain the real amount of RAM available, you need to check Task Manager. Like this: ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (205) Please take a screenshot and attach it here, so we can see the numbers.

#3114

daniel_k

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3110

> if you have time, try to force usb3.0 device to be only 32-bit dma in amdxhc.sys, maybe this helps:
> ...

That did it!
Thank you very much!
I had no idea one could force a driver to use 32-bit DMA! Learning new things everyday!
Does this have any side effects? If not, I'll release it as a "new" final version.
⇗ @schreiberstein, ⇗ @Mov AX, 0xDEAD fixed the issue with AMDXHC!

#3115

Andalu

⇗ @daniel_k
here the screenshots (onboard vga):
⇗ ⇗ ⇗
1.No PAE
2.PAE /4GB
3.PAE /ALL

#3116

daniel_k

⇗ @Andalu
Nice improvement!
Can you try Mov AX, 0xDEAD's fix for AMDXHC.SYS?
Patch kernel files with /ALL command line.
Make sure you replace all files at the same time.
ntkrpamp.exe renamed to ntkrnlpa.exe in \Windows\system32
hal.dll in \Windows\system32 (see attachment)
amdxhc.sys in \Windows\system32\drivers (see attachment)

#3117

Pill Monster

> Zitat von ⇗ daniel_k im Beitrag ¶ #3100

> @Pill Monster
> Your nick seems familiar. Which forum are you more active in?
> You seem to be everywhere.

Haha - once upon a time maybe. :D These days I keep a lower profile - just Win-Raid & another forum you never heard of called GeekZone (mostly NZ IT industry workers).
You would know me from Guru3D, I was active there for ~8yrs.

> Zitat von ⇗ daniel_k im Beitrag ¶ #3100

> Glad to know my packs are still helping you!

I'm sure they're helping many others too.

> Zitat von ⇗ daniel_k im Beitrag ¶ #3100

> Back to the subject, from the compatibility issues we've seen, Microsoft was right to some degree.
> Some drivers are poorly written, which may lead to data corruption, something I consider unacceptable.

I recall a few problems with Nvidia cards running at 8x AGP on nForce2. I can't even remember if that was driver related or not, but selecting 4x AGP n BIOS seem to fix it.
I've not read through this thread so admittedly I don't know the details of any problems users may be having. However I'm going to be honest & say I don't believe Russonivich's claims regarding driver incompatibility.
If there was any incompatibility at I suspect it arose from adding /PAE switch on machines with IA-32/IA-32e CPU's. PAE in the OS context is an acronym for Page Address Extension, not Physical Address Extension.
Physical Address Extension is Intels nomenclature referring to any CPU with more than 32 external bits. IA-32 being 32/32 (registers) doesn't support paging, IA-32e (36/32) does support paging but not remapping.
One can see how that might become a problem when drivers want high addresses.
To the best of my knowledge AMD64 users never had issues - I didn't. The boards supported remapping & address translation I think would be transparent to most drivers, not that it should matter anyway.
⇗ @daniel_k:
When I find the link I'll point you to an article written by developer Geoff Chappell a few years ago on XP/Vista memory limitations & his views of Microsoft.
f

#3118

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #3116

> @Andalu
> Nice improvement!
> Can you try Mov AX, 0xDEAD's fix for AMDXHC.SYS?
> Patch kernel files with /ALL command line.
> Make sure you replace all files at the same time.
> ntkrpamp.exe renamed to ntkrnlpa.exe in \Windows\system32
> hal.dll in \Windows\system32 (see attachment)
> amdxhc.sys in \Windows\system32\drivers (see attachment)

It woooorkssss!! Great!! No issues related to USB ports. The shutdown works as usual.
Also the ramdisk software see the entire ram installed and I can use the memory over 4GB. I already tried to load a ramdrive on boot and it works.
Thanks so much ⇗ @daniel_k and ⇗ @Mov AX, 0xDEAD
⇗

#3119

daniel_k

⇗ @Pill Monster
Yeah, remember you from Guru3D, for sure!
There are some specific drivers that defitively don't support 64-bit addressing.
Some hardware, such as soundcards (Live!, Audigy) also have issues, which were popular by 2008, when XP SP3 was released.
Geoff's article I've already read, thanks.

#3120 | daniel_k | ⇗ @Andalu Glad to know it works! Things just keep getting better!

## Page 209

#3121

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #3114

> > Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3110

> > if you have time, try to force usb3.0 device to be only 32-bit dma in amdxhc.sys, maybe this helps:
> > ...

> That did it!

1) single amdxhc.sys patch or combination with hal.dll patch ?
2) on w2003 did you have problem with amdxhc.sys ?
i think it just beta patch because we dont know where problem, in hal or 3rd driver....

#3122 | Andalu | ⇗ @daniel_k You are right ;) and never to lose the hope. Until two month ago I never imagined being able to install XP on a skylake board and to have the usb3 fully functional. Many thanks to this great forum and its skilled members.

#3123

schreiberstein

⇗ @daniel_k
Hey! I am currently applying your fixed to my system.
Could you adapt the hal_pae_fix.rar to include the ACPI timer fix? Chrome crashes again.
Will let you know my results soon.
Just applied the kernel patch. Rebooting.
Really cool stuff!
Cheers,
schreiberstein

#3124

Ep.Cygni

Hello all and thanks for your effort on enhancing Windows XP.
⇗ @daniel_k
Attached are my results of testing the PAE patch from ¶ post #3068 on a live system. I followed the instructions in ¶ post #3088 but renamed patched kernel files before replacing (as mentioned in #3068 but omitted in #3088).
The PC has a Creative Audigy card installed, and I did a simple driver compatibility check: tried playing midi files on the card's hardware synth.
With /4GB option, some notes were missing and others ended abruptly. However, this issue could be fixed by reloading the soundfont a few times (alternating with other soundfonts seemed to work best).
With /ALL option, the same issues happened but I could not find a way to return the synth to normal operation.
I made several reboots with both patch versions to make sure these results are repeatable.
Also, the Audigy Sw Synth went completely silent with patched kernels and worked again only with the original one.
Thus, it looks like the "fake PAE" approach cannot prevent all possible compatibility issues. It is still more stable than some other PAE-enabling patches I tried before - for example, with "fix128v48" the system would freeze and/or reboot when attempting to play a midi file.
Hope this info will be helpful to people reading the thread.
Ep.Cygni has attached images to this post ⇗ 0 - unpatched.png ⇗ 1 - patched with 4GB opti ⇗ 2 - patched with ALL opti

#3125

daniel_k

⇗ @Mov AX, 0xDEAD

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3121

> 1) single amdxhc.sys patch or combination with hal.dll patch ?
> 2) on w2003 did you have problem with amdxhc.sys ?
> i think it just beta patch because we dont know where problem, in hal or 3rd driver....

1) Combination of both. As you can see some posts above, ⇗ @Andalu reported success as well.
2) Yes.

#3126

schreiberstein

⇗ @daniel_k
I patched "ntkrnlpa.exe" with /4GB and it worked. (See screenshot, running prime95 in the background)
I booted with /pae .
USB did work. I also replaced the "amdxhc.sys" file and hal.dll.
As of now, I cannot judge application stability since the hal.dll causes Chrome and other things to misbehave, due to the lacking ACPI timing patch.
Cheers,
schreiberstein
schreiberstein has attached images to this post ⇗ post_patch.PNG

#3127 | daniel_k | ⇗ @schreiberstein Please use /ALL command line. Here is the patched hal.dll with timer fix. Don't know which one you have, so packed both 5512 and 5687.
#3128 | daniel_k | ⇗ @Ep.Cygni Unfortunately, for XP 32-bit with PAE and XP x64 (which is PAE by design), Audigy cards are a lost cause. Creative didn't bother to fix the driver. Only X-Fi cards (may) work with PAE. PS: Thanks for your reports!

#3129

schreiberstein

⇗ @daniel_k
On /4GB I noticed that it takes longer for explorer.exe to navigate through folders. A noticeable delay.
Same instabilities as with that 128gb patch set occur with /ALL :
RAM gets detected properly, but Chrome pages crash.
Also, boot took much longer than usual.
I have installed the 5687 version of hal.dll .
Cheers,
schreiberstein
schreiberstein has attached images to this post ⇗ patch_all.png

#3130 | daniel_k | ⇗ @schreiberstein Does DOS apps work at all? If so, is possible to change them to full screen? (ALT+Enter) With the modified AMDXHI, just tried Server 2003 and it works just fine. Might worth a try when you have time.

#3131

schreiberstein

⇗ @daniel_k
No. Not at all. Instant crash, as if nothing had been executed.
I will try on 2003 tomorrow.
Thank you for all your work.
Cheers,
schreiberstein

#3132 | infuscomus | ⇗ @daniel_k ⇗ @diderius6 I was experimenting to see if I could install XP onto a KVM VM and I encountered a different A5 BSOD when in KVM. ⇗ bsod A5 14 - I haven't seen this one before. this is with patched ACPI 5048 not urgent to have this fixed, just something of note.

#3133

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #3096

> @Doc.Brown
> Before you transfer XP SP3 from another working compi to the Gene XI board,
> disable all USB there
> Dietmar

⇗ @diderius6 ok I'll try it this afternoon
Do you think USB is in fault for my BSOD problem ?

#3134

roytam1

> Zitat von ⇗ Ep.Cygni im Beitrag ¶ #3124

> The PC has a Creative Audigy card installed, and I did a simple driver compatibility check: tried playing midi files on the card's hardware synth.
> With /4GB option, some notes were missing and others ended abruptly. However, this issue could be fixed by reloading the soundfont a few times (alternating with other soundfonts seemed to work best).
> With /ALL option, the same issues happened but I could not find a way to return the synth to normal operation.

I wonder if kX driver helps? as Creative creates badly written drivers, 3rd party driver seems to be better.

#3135

roytam1

> Zitat von ⇗ daniel_k im Beitrag ¶ #3068

> Let me explain what I've found.
> Windows 2003 has many licensing presets (which affects PAE and limits RAM available).
> One of them does something interesting: enables PAE, but limits RAM to 4Gb.
> The result? RAM is mapped in a more effective way so that more RAM is available.
> At the same time, as it is limited to 4Gb, there are absolutely no issues with drivers or specific hardware, which is great for most of us.
> I've wrote a small utility to patch all kernel files, should support all languages and all kernel versions 5512 (SP3) and later:
> ntkrnlmp.exe - Multiprocessor Kernel
> ntoskrnl.exe - Uniprocessor Kernel
> ntkrpamp.exe - Multiprocessor PAE Kernel
> ntkrnlpa.exe - Uniprocessor PAE Kernel
> To use it, copy all kernel files (found in SP3.CAB) and this utility to the same folder.
> Usage: winxppae [/4GB | /ALL]
> /4GB Enables PAE limiting RAM to 4Gb to avoid stability issues.
> /ALL Enables PAE with unlimited RAM, may have stability issues.
> You may test the files on a running system by replacing the files from another OS (otherwise File Protection will restore the files).
> In this case, pay attention to the filenames, on multiprocessor systems, rename ntkrnlmp.exe to ntoskrnl.exe and ntkrpamp.exe to ntkrnlpa.exe.
> Or integrate them on the CD (rebuilding SP3.CAB and repacking ntkrnlmp.ex_ and ntoskrnl.ex_).
> No need to include a /PAE switch in boot.ini, as this works just like on Server 2003.
> As I've patched the files properly, ntoskrnl.exe automatically chainloads the PAE kernel, ntkrnlpa.exe.
> PS: Only supports Windows XP SP3. Another version supporting Server 2003 will be released later.
> PS: Updated 1.1 version /4GB and /ALL logic was reversed. Fixed.

I wonder if patch can work with latest(last) ntkrnlmp.exe (5.1.2600.7649 from KB4486463) / ntkrnlpa.exe,ntkrpamp.exe,ntoskrnl.exe (5.1.2600.7581 from KB4463103)?

## Page 210

#3136

Ep.Cygni

> Zitat von ⇗ roytam1 im Beitrag ¶ #3134

> I wonder if kX driver helps? as Creative creates badly written drivers, 3rd party driver seems to be better.

Yes, the kX driver is fully compatible with PAE (no issues with any patch).
Also, Creative drivers for early PCI cards based on Ensoniq chip (ES137x) are compatible too; one can install such card to get back the software synth with .ecw sound banks (identical to Live!/Audigy Sw Synth which stops working if PAE is enabled).

#3137

Doc.Brown

> Zitat von ⇗ Doc.Brown im Beitrag ¶ #3133

> > Zitat von ⇗ diderius6 im Beitrag ¶ #3096

> > @Doc.Brown
> > Before you transfer XP SP3 from another working compi to the Gene XI board,
> > disable all USB there
> > Dietmar

> @diderius6 ok I'll try it this afternoon
> Do you think USB is in fault for my BSOD problem ?

Doesn't change anything,I think something is already wrong with acpi.sys

#3138

Mov AX, 0xDEAD

I've maked two experimental hal.dll to test bugs with dma64/dma32 drivers
1) hal_force_high_addr
if driver declare support dma64 and request memory for dma (AllocateCommonBuffer), hal forced to allocate memory only from HIGH adressses. This mean hardware will survive only with adresses >4Gb
Tested:
VIA USB3.0 driver - requests dma64, works fine
AMD USB3.0 hacked driver - requests dma64, not works, dev_0000 if inserted something or nothing happens
Realtek LAN - requests dma32, works fine
NVidia 660GTX - don't use hal, has own dma implementation(?), works fine
Intel integrated VGA on IvyBridge 6.14.10.5437, don't use hal, works fine
Creative X-fi 2.30.0011- requests dma32, not works, hangs or loop somewhere in ring0 space
Creative X-fi 2.30.0011- forced dma64 (hidden option in *.inf), instant reboot
2) hal_force_dma32
any dma64 request forced to dma32, same behavior as patchpae3, but patchpae3 miss limiting allocation <4Gb
VIA USB3.0 driver - driver can't start, Error 10
AMD USB3.0 hacked driver - works fine
Creative X-fi 2.30.0011- not works

#3139

Mov AX, 0xDEAD

> Zitat von ⇗ infuscomus im Beitrag ¶ #3132

> bsod A5 14 - I haven't seen this one before. this is with patched ACPI 5048
> not urgent to have this fixed, just something of note.

¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (21)
BSOD A5(14,...) was discovered in Qemu q35-pcmodel before

#3140

diderius6

⇗ @Doc.Brown
This is acpi.sys from outer space ),
with try to hack against BSOD A5 (0x00000003,xxx,0xC0140008,yyy)
Dietmar
diderius6 has attached files to this post

- ⇗ acpi.rar

#3141 | daniel_k | ⇗ @infuscomus, thanks for reporting the issue. For now, I'm done with ACPI hacking, but saved the info in my notes.
#3142 | daniel_k | ⇗ @roytam1 Yes, personally tested with original SP3 and latest version.

#3143

daniel_k

⇗ @Mov AX, 0xDEAD
Unfortunately forcing 32-bit DMA has issues, at least on my system.
At first, everything works just fine.
But after copying files and specially running disk benchmark on AIDA64, the driver "hangs" the USB drive, even restarting doesn't fix it, need to remove it and plug it again for the drive to be recognized.
As soon as this happens, the issue with NTVDM appears, trying to switch to full screen gives me an error.
When only the XHCI controller is enabled, no problem.
When AMD Hub is enabled, the issue occurs.
Is there anything that can help with this? Memory dumps of before/after issue?

#3144

daniel_k

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3138

> Today i've maked experimental hal.dll to test bugs with dma-64 drivers, if driver declare support dma64, and request memory for dma (AllocateCommonBuffer), hal forced to allocate memory only from HIGH adressses. This mean hardware will survive only with adresses >4Gb.

What about drivers that support only 32-bit DMA?
How does HAL allocate memory?
Can we hack HAL to change its behavior?

#3145

gordo999

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #17

> yes, dsdt binary table stored in uefi...

@Mov AX, 0xDEAD....or anyone interested...
hi...just getting up to speed on this thread reading each post from the beginning. I am curious about what you are saying about ACPI. Here's my problem....
This may be premature, I still have a lot of reading to do in this thread. Right now I am addressing an 0x000000A5 error but I am also mentioning an 0x000000F7 error. Maybe that has been answered later.
I have XP SP3 mounted on a SATA drive. It was working on SATA on an Intel DQ35JOE mobo so I presumed it had at least primitive SATA drivers.
When I plug it into the SATA 4 port on the mobo and try to boot, I get an immediate boot-ini error, claiming it is trying to boot from C:\Windows. I have no such directory, but I am using a small C: partition that held W98 at one time. The boot.ini and XP loaders are on C: but XP is on partition 2. That is indicated in the boot.ini file.
It is shown in a partition manager running in W7 as disk 3. I will address that problem in a later post and focus on the ACPI issue for now.
If I insert the XP install disk, slipstreamed with SP3, I eventually reach a BSOD screen with an 0x000000A5 error...the APCI in BIOS is claimed to be not fully compliant. Is this what you are talking about and does the BIOS have to be modded to get around that?
I got past the BSOD by hitting F7 as directed on the BSOD screen. However, their explanation does not work for me, I must hit F7 immediately when the F6 message appears, to hit F6 if I need to load storage drivers. Then the install disk will proceed to the end. However, when it reached the stage where it is starting Windows, I get an 0x000000F7 error, which is related to the boot.ini error. F7 means it cannot find a bootable OS.
Recently, I read about the unofficial SP4 update for XP. So, I went through the laborious process of slipstreaming the SP4 onto my XP SP3 disk. Lo and behold, with that SP4 disk, the install found my XP OS install and let me select it from a list of partitions.
It appears to me there may be other BIOS issues if the SP4 install can find my XP install but the stock XP SP3 disk can't.

#3146

infuscomus

⇗ @gordo999
I have a modified XP ISO that might potentially solves your BSODs, would you like to try it out?
Bug Check 0xF7: DRIVER_OVERRAN_STACK_BUFFER
are you sure that is the BSOD you get?
Bug Check 0x7B: INACCESSIBLE_BOOT_DEVICE
would seem more likely
can you send screenshots all of the BSODs you get? including the A5 BSOD, F7 BSOD etc... a screenshot of the errors would give more information about them.

#3147

gordo999

> Zitat von ⇗ infuscomus im Beitrag ¶ #3146

> I have a modified XP ISO that might potentially solves your BSODs, would you like to try it out?
> ....Bug Check 0x7B: INACCESSIBLE_BOOT_DEVICE would seem more likely
> can you send screenshots all of the BSODs you get? including the A5 BSOD, F7 BSOD etc... a screenshot of the errors would give more information about them.

@infuscomus...yeah, thanks, the ISO might be helpful to get me going.
I'll follow this reply with an exact description of my problem.
You are right it is error 0x7B. I am getting a bit foggy-minded with all the reading and research I've been doing.
I would be happy to send a screenshot if I could take one. They occur during the boot stage and I have no idea how to take a screenshot then. I could write it out from the screen.

#3148 | infuscomus | ⇗ @gordo999 I PMed you the modded ISO, let me know if it works.

#3149

gordo999

@infuscomus...here's more detail on my problem.
I have XP SP3 installed on it own SATA hard drive. It was working fine on an older Intel DQ35JOE mobo, so I am plugging it into a SATA #4 port on the 8th gen Asus B360M mobo. I think in the past I may have changed the active partition and the primary partition flags so the system would not accidentally boot XP. I have since restored the flags making partition 1 both primary and active and partition 2, with XP, just primary.
BTW...I used the F6 floppy method to install SATA drivers from win-raid. The install went fine. I also have a set of win-raid SATA drivers on the unofficial SP4 update disk. Both recognize the A352 hardware SATA ID on my ASUS mobo.
Partition 1 = (C:) used to be Win98 but I have removed the OS and use the small partition for storage. It was too much of a hassle to convert the partition back to make the XP partition as the boot partition.
Please note that the directory on C: still exists for win98 but it is named WIN98 and not Windows. When I try to boot normally from the drive, I get an error message claiming boot.ini is corrupt and that the system is trying to boot from C:\Windows. No such directory on C: and there are no other drives plugged in while I am booting this drive.
Here is my boot.ini file and please note that it was modified by an attempted repair install with the XP installation disk. I am currently in the middle of that install but when the install tries to reboot, I get stopped by the corrupt boot.ini and another error claiming ''load needed DLLs for kernel". It won't go past that point so I cannot complete the repair install.
[boot loader]
timeout=1 //note...don't know why it's set so low.
default=multi(0)disk(0)rdisk(0)partition(2)/WINXP.2
[operating system]
multi(0)disk(0)rdisk(0)partition(2)/WINXP.2="Microsoft Windows XP Home Edition" /noexecute=optin /fastdetect /noexecute=optout
multi(0)disk(0)rdisk(0)partition(2)/WINXP.2="Microsoft Windows XP Home Edition" /noexecute=optin /fastdetect /noexecute=optout
Please note the following:
-the install program changed the default OS from /WINXP to /WINXP.2. In the XP directory on partition 2, it has also added two new directory, WINXP.0 and WINXP.1, on beside the original WINXP directory.
-you can see they have added another [OS] entry on top of the original, with the /WINXP.2.
-also, they have added a /noexecute=optout to counteract the earlier /noexecute=optin.
Even though the XP is clearly referred to as being in rdisk(0)partition(2) it is looking for the OS in C:\windows. I am wondering if that is somehow wired into the BIOS.
When I look at the setup from a partition manager in W7, the XP drive is referred to as disk 3. Win10 is on disk 1 and W7 is on disk 2. I thought maybe the rdisk value should be changed to reflect that but changing the rdisk value does nothing. I have changed it to 2 but not to 1.
Here's the kicker. I have upgraded my XP SP3 install disk to the unofficial SP4 update. Using that install disk, the install suddenly sees all the partitions on the disk and I am able to select the XP install on partition 2. That means the SP4 install bypasses the 0x7b bsod.

#3150 | gordo999 | @infuscomus....just downloading it now...thank you kindly.

## Page 211

#3151

gordo999

@infuscomus....good news, no 0xA5 or 0X7B BSODS..
Now for the bad news. :-)
When I run an install using the disk, I get no USB at the point where windows is starting. With the unofficial SP4 updated install disk, I do get the USB keyboard. Fortunately I have an OS/2 keyboard plugged in.
I wanted to get to the repair prompt, which I did. I tried diskpart but it must be the XP version and I find it to be useless. I tried bootcfg /scan from inside the WINXP director on partition 2 and it found no operating systems!!!!
Diskpart lists partition 1 as drive C: but it lists partition 2 as drive H???? Go figure.
I would be interested in the mods you used if they are easy to describe for you and not a lot of trouble.

#3152

infuscomus

⇗ @gordo999
The mods are
patched ACPI driver (thanks to daniel_k, diderius6)
generic AHCI driver (thanks to skullteria)
generic USB 3.0 driver (thanks to daniel_k)
I was hoping to have USB 3.0 working for XP setup - shame it did not work, at least you had a PS/2 keyboard.
are you prepared to wipe your hard drive and start from scratch?

#3153

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #3140

> @Doc.Brown
> This is acpi.sys from outer space ),
> with try to hack against BSOD A5 (0x00000003,xxx,0xC0140008,yyy)
> Dietmar

Thanks I don't have this A5 BSOD anymore but I'll try this one today to see if it's resolve mine ;)
I'm always stuck with this one during devices installation in XP set-up or at boot when I instal on another motherboard and put it on the Z390 Gene after :
⇗

#3154

gordo999

> Zitat von ⇗ infuscomus im Beitrag ¶ #3152

> Are you prepared to wipe your hard drive and start from scratch?

@infuscomus...thanks for info re patching OS.
I may have to do a clean install eventually but I don't want to lose the apps I have on the XP partition. I still have some options, like a backup image of both partition 1 and 2. Part of my problem may be that I have more partitions on the disk besides the XP partition and the drive C:\ partition. They are secondary partitions and can be moved elsewhere, so I could load the saved C: and D: partitions on a separate disk to see how that affects the loading.
I booted the W10 repair disk and it can see the XP partition. It just won't repair anything on it. I might try the W7 repair disk.

#3155

gordo999

Can anyone confirm the flag settings on a system with nothing on drive C: (partition 1) and XP on drive D: (partition). I have them both set as primary and only partition 1 set as active.
Drive C: used to be W98 but the OS is no longer working. I had the boot.ini file on C: along with the bootloader for XP. It worked for many years just fine.
I'm sure this has something to do with the newer 8th gen mobo because I had no issues with it on the DQ35JOE mobo which is ICH9 or newer.

#3156

infuscomus

⇗ @gordo999
edit: can you set partition 2 as active? that might work
my guess is the old system used IDE mode which windows98 supports and the new system uses AHCI mode.
windows98 does not support AHCI by default and cannot boot from it without a driver (a driver exists, but it's not free)
so if the windows98 partition is first up to boot, but is in AHCI mode, so it fails.
I think it would be best to backup the drive and start over.
in my setup I have a drive for each OS - I even got windows98 working on AMD Ryzen (with the paid for driver)

#3157 | XPWELL64 | Ahci isn't good for HDD but very good for SSD. FEWER OS SUPPORT and same performance.
#3158 | XPWELL64 | I saw that every site serves the drivers as free.

#3159

diderius6

Hi,
this morning I make the ultimative ACPI test for the EVGA dark z390 board.
First, I make with REVELPROG IS Epromer an update of its whole Bios chip 25Q127CSIG.
3 times I read XP friendly Bios vers. 092 out and compare. Ok, all copies are identic.
Then I flash the brandnew BIOS 107 (September 2019), which is not XP friendly to this z390 board.
Ok, first XP SP3 install gives A5 error and in a strange way also 7B.
After testing and testing I succeed to install full ACPI XP on this board. I do not mod anything in Bios 107.
Everything works: Lan, graphik, all USB.. under XP.
The DSDT table of this Bios 107 is similar to the Bios of the Gene XI board
or the Apex XI board or the z390 boards from Gigabyte.
I have to add the registry entries for the STORAHCI driver by hand (see *.reg here in folder)
Dietmar
EDIT: USB boot of XP SP3 works on all(!) USB ports, nice:)).
EDIT2: I put this XP SP3 on nvme boot device. This is now most fast OS ever seen.
⇗
diderius6 has attached files to this post

- ⇗ XPacpistorportSTORAHCI.rar

#3160 | infuscomus | ⇗ @XPWELL64 AHCI has some improvements for HDDs, NCQ extends the life of a HDD the paid for driver ⇗ http://www.geocities.ws/rloew/catalog2.htm

#3161

gordo999

> Zitat von ⇗ infuscomus im Beitrag ¶ #3156

> so if the windows98 partition is first up to boot, but is in AHCI mode, so it fails

@infuscomus....good point....worth checking out.
I might be able to backup the XP partition, or use my image backup, and install it back to partition 1. I would have to remove both partitions and make one partition.
Would have to figure out a way to make it bootable. Actually, C: currently has the MBR and is bootable. Maybe I could remove partition, expand C:, and recover the XP image to C:.
Too tired to think right now but thanks for ideas. Appreciate it.
BTW...I was using attrib in the cmd window of W7 to look at the C: partition on my XP disk. It still has hidden files going back to the DOS days like drvspace.bin, command.com, and all that good stuff. Better to clean it all out and start with fresh partition.
ps.will set partition 2 active but I think I may have already tried that. No harm in trying.

#3162

IntiMD

> Zitat von ⇗ infuscomus im Beitrag ¶ #3156

> windows98 does not support AHCI by default and cannot boot from it without a driver (a driver exists, but it's not free)

Well, the driver has been released for free due to the author's demise and his son allowing people to freely redistribute it for purposes of continuing his legacy.
For those who don't know what am I talking about, it's about one of Rudolph "rloew" Loew's patches (the AHCI one). ⇗ His driver collection which is user-contributed can be found in the Internet Archive.

#3163

diderius6

⇗ @Doc.Brown
This BSOD comes from the Iastor.sys driver. I have had the same problem.
When you use the STORAHCI driver from my last post,
this BSOD is gone. You have to notice: Everytime when XP wants
to install the Iastor 1006 driver from Fernando, you need to stop this
and set in this place the Standard SATA AHCI Controller (see photo) from ⇗ @skullteria
Dietmar

#3164 | infuscomus | ⇗ @IntiMD Oh dear! I didn't know he had died. Rest in Peace, Rloew.

#3165

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #3144

> > Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3138

> > Today i've maked experimental hal.dll to test bugs with dma-64 drivers, if driver declare support dma64, and request memory for dma (AllocateCommonBuffer), hal forced to allocate memory only from HIGH adressses. This mean hardware will survive only with adresses >4Gb.

> What about drivers that support only 32-bit DMA?
> How does HAL allocate memory?
> Can we hack HAL to change its behavior?

If driver declare only dma32, hal work as w2003 - 1) always allocate mapregisters if we have >4Gb phys adressing) limit allocating buffer memory <4GB.
Hal allocate shared cpu<->dma<->pci memory in HalAllocateCommonBuffer, but not all layers in windows uses hal directly, LAN drivers uses NDIS.sys, Sound drivers use portcls.sys, Video may use videoprt.sys
You can patch to force dma32 for all drivers:
- mov byte ptr [edi+0b], 0 in HalGetAdapter ; Dma64Adressing=0
- HalpGetAdapterMaximumPhysicalAddress return max allowed adress for device in EDX:EAX, for dma32 device is 0:FFFFFFFF, for dma64 device is FFFFFFFF:FFFFFFFF, need to force 0:xxxxx
p.s. i updated post to include new info ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (210)

## Page 212

#3166

daniel_k

⇗ @Mov AX, 0xDEAD
Thanks for the detailed info on how HAL works and several driver testing reports.
Interesting that as I have 16Gb, the hacked AMDXHC driver works just fine, pity it breaks NTVDM.
When forcing DMA32 in AMDXHC, no issues with NTVDM/VGA, but it hangs the flash drive as I've said before.
In your opinion there isn't anything else that can be done with this driver?
I'm trying to hack another driver, but is proving to be difficult.
If a error code 10 is shown, it's reported by the driver, right? Is there a reference list with "error codes" that a driver must report to Windows?
I thought it would be something like 0xC000000A (A would be 10), but can't find those in the driver.

#3167 | daniel_k | ⇗ @Mov AX, 0xDEAD Did you evert try Vista 32-bit by any chance? Going to try it later today, seems to have issues with timer on Haswell and later, user mode services usually fail to load after hanging for a long time. Even with SP2, it happens.

#3168

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #3159

> Hi,
> this morning I make the ultimative ACPI test for the EVGA dark z390 board.
> First, I make with REVELPROG IS Epromer an update of its whole Bios chip 25Q127CSIG.
> 3 times I read XP friendly Bios vers. 092 out and compare. Ok, all copies are identic.
> Then I flash the brandnew BIOS 107 (September 2019), which is not XP friendly to this z390 board.
> Ok, first XP SP3 install gives A5 error and in a strange way also 7B.
> After testing and testing I succeed to install full ACPI XP on this board. I do not mod anything in Bios 107.
> Everything works: Lan, graphik, all USB.. under XP.
> The DSDT table of this Bios 107 is similar to the Bios of the Gene XI board
> or the Apex XI board or the z390 boards from Gigabyte.
> I have to add the registry entries for the STORAHCI driver by hand (see *.reg here in folder)
> Dietmar
> EDIT: USB boot of XP SP3 works on all(!) USB ports, nice:)).
> ⇗

⇗ @diderius6
Do you replace original files in STORAHCItxtSetup by yours in this attached file or use them standalone with Nlite integration please ?
Thanks

#3169

diderius6

⇗ @Doc.Brown
I use nlite for STORAHCI driver via txtsetup.oem.
I use only files from this folder package from attached file in
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (211)
I copy by hand storport.sy_ and this acpi.sy_
in i386 folder.
When you do all correct,
on next reboot you get BSOD 7B.
This happens, because some values are missed in registry for the STORAHCI driver.
This you have to do by hand with the *.reg file
Dietmar

#3170

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #3169

> @Doc.Brown
> I use nlite for STORAHCI driver via txtsetup.oem.
> I use only files from this folder package from attached file in
> ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (211)
> I copy by hand storport.sy_ and this acpi.sy_
> in i386 folder.
> When you do all correct,
> on next reboot you get BSOD 7B.
> This happens, because some values are missed in registry for the STORAHCI driver.
> This you have to do by hand with the *.reg file
> Dietmar

Ok thanks,but I don't understand how you could do this step if you can't boot with BSOD 7B ? Could you tell me more please

#3171

diderius6

⇗ @Doc.Brown
Yes, this procedure is unknown for most. It even works for Win2000, Win2003, Vista, Win7, win8, win10, (win12^^, all 32 and 64 bit) via XP(!) SP3. There is a tool from Microsoft, that overcomes any restriction for registry in any OS via XP. (There is a reason, why the US army uses only XP SP3 everywhere and also the german Bundestag.) Here we dont need this.
I make a try to describe:
Take the harddisk with BSOD 7B XP (PC1) out of the compi.
Put it in an USB case, connected to a XP compi (PC2).
On PC2 you type regedit in commandline.
Then you go on HKLM in this machine.
Left above on top click on "Load structure".
Then you look in windows\system32\config\ for the hive system (on the USB drive with XP from PC1)
Click open.
A window opens, for a name of the structure. Name it
otto
Click ok.
In PC2 registry you see under HKLM a new structure with name otto.
This is the open registry from PC1.
I prepare for you a storahciotto.reg just now.
On this storahciotto.reg you double click.
Then a message comes, if you want to add this to registry, click yes and then ok. Then the information is put to registry (of PC1).
Click on structure otto
so that it is just blue.
Then go above left "delete structure". (Dont click import or export!!!).
With otto marked blue click on it and then yes.
The new registry has been written to PC1 harddisk,
close registry on PC2, thats all. It works for any win version.
Dietmar
EDIT: Note that newer versions of Windows don't allow users to delete these registry keys. It may be necessary to run redgedit.exe from another software tool that grants elevated access to the registry. For example, users can run the following command from the command line to run regedit using the System account:
psexec -i -d -s c:\windows\regedit.exe
PsExec is a part of PSTools available from Microsoft at:
⇗ http://technet.microsoft.com/en-us/sysin...s/bb897553.aspx
diderius6 has attached files to this post

- ⇗ storahciotto.rar

#3172 | Doc.Brown | ⇗ @diderius6 Wow impressive ! Fresh iso is ready with only acpi and storahci(will add USB later if it works),I try to do this ^^ Thank you :) Edit: that's right I wasn't able do delete it(and to execute the file too,I had to add Total Control by clicking on Permissions) so I just unloaded the hyve but at next boot(XP) I had an error message that tell me system file in system32 is missing or damaged,I try with Psexec
#3173 | diderius6 | ⇗ @Doc.Brown Can you install XP in txtmode on the Gene XI board with 57 Bios? Dietmar
#3174 | Doc.Brown | ⇗ @diderius6 Don't know what is txtmode install It won't work even with Psexec under Win8.1,I can't erase otto, -s argument in commandline for Psexec return an error and without I'm not able to delete otto ...

#3175

diderius6

⇗ @Doc.Brown
Life is much easier when you use XP on PC2
Dietmar
PS: Txtmode in XP setup is the first phase of XP install, that you can chose harddisk and drivers gets installed before reboot.
The tool works also under win 8.1, I tested.
For to delete otto:
Just close regedit one time on PC2 and open it again.
Then you can delete otto there.

#3176 | Doc.Brown | ⇗ @diderius6 Yep I will set-up an old school motherboard to put easy XP ghost on it but on my 8.1(surely too much modded for benchmarking) that doesn't work unfortunately I guess Txtmode should work cause I can press F2/F6/F7 or F5 in the beginning of install
#3177 | diderius6 | ⇗ @Doc.Brown When you build correct XP SP3 setup CD, no need to press F5 during setup Dietmar

#3178

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #3166

> @Mov AX, 0xDEAD
> In your opinion there isn't anything else that can be done with this driver?
> If a error code 10 is shown, it's reported by the driver, right? Is there a reference list with "error codes" that a driver must report to Windows?
> I thought it would be something like 0xC000000A (A would be 10), but can't find those in the driver.

- i dont know what is wrong with driver, no ideas
- no, error 10 is "human" error of device manager, driver return another error like Cxxxxxx when windows call one of it functions (usualy IRP request). in case of VIA we have wdf and error can be inside of it

#3179

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #3167

> @Mov AX, 0xDEAD
> Did you evert try Vista 32-bit by any chance?

I plan to install Win7 with unlocked_pae and recheck all what i already found. Win7's hal DMA functions is similar to win2003.
Win8/10 hal is different beast

#3180

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #3177

> @Doc.Brown
> When you build correct XP SP3 setup CD,
> no need to press F5 during setup
> Dietmar

Yup I know,it was just an example to tell you txtmode is doable with my iso ^^
If you want to test it I can upload it ;)
Edit: also try to add register on my H24 Win10,Psexec works well but unable to delete the entry again,only option is to unload the hyve but some files stays in XP system32\config directory and when I restart the install already says that System is missing or damaged ... don't know what i'm doing wrong but i do xD

## Page 213

#3181 | diderius6 | ⇗ @Doc.Brown And what happens after txtmode? Dietmar

#3182

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #3181

> @Doc.Brown
> And what happens after txtmode?
> Dietmar

Nothing wrong just the BSOD after first reboot as you said that's why I'm trying to inject the reg file to pass the bsod ;)

#3183 | diderius6 | ⇗ @Doc.Brown You can upload your hive "system" from Bsod 7B XP SP3 and I add the registry entries for you Dietmar PS: And dont forget to look, if modded acpi.sys and storport.sys are at their place:)).

#3184

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #3183

> @Doc.Brown
> You can upload your hive "system" from Bsod 7B XP SP3
> and I add the registry entries for you
> Dietmar
> PS: And dont forget to look, if modded acpi.sys and storport.sys are at their place:)).

My mistake it was the storport,I'm a noobish xD
But always the same IRQL not less or equal after during devices set-up after first reboot :(
I try to put the reg file,you can find the system hive uploaded here : ⇗ System hive
Thanks

#3185

diderius6

⇗ @Doc.Brown
And here it is
Dietmar
PS: I noticed, that you also have drive D, E.
I deleted those entries in registry, because via this way XP does not know where to continue.
diderius6 has attached files to this post

- ⇗ system.rar

#3186

daniel_k

⇗ @Mov AX, 0xDEAD, I've found a pattern!
Drivers that use Mm64BitPhysicalAddress don't work properly. They seem to be badly coded.
ASMedia, TI and AMDxhc31 all share same code, which don't have any references to Mm64BitPhysicalAddress and always work.
Performing both 32-bit and 64-bit DMA:
⇗ https://community.osr.com/discussion/192085
Problem is, MCCI's drivers are really, really hard to hack, seems like there are sanity checks everywhere, not just some simple Device ID checks.
This code is from amdxhc31.sys v1.0.2.0 disassembled in IDA:

    		mov	[ebp+DeviceDescription.ScatterGather], dl
    		mov	dl, [eax+2]
    		mov	[ebp+DeviceDescription.Dma32BitAddresses], dl
    		mov	dl, [eax+0Ch]
    		mov	[ebp+DeviceDescription.IgnoreCount], dl
    		mov	dl, [eax+3]
    		mov	[ebp+DeviceDescription.Dma64BitAddresses], dl
    		mov	edx, [eax+8]
    		mov	[ebp+DeviceDescription.InterfaceType], edx
    		mov	edx, [eax+4]
    		mov	[ebp+DeviceDescription.Master],	cl
    		mov	[ebp+DeviceDescription.MaximumLength], edx
    		test	cl, cl
    		jnz	short loc_2BE1F
    		mov	cl, [eax+18h]
    		mov	[ebp+DeviceDescription.DemandMode], cl
    		mov	cl, [eax+19h]
    		mov	[ebp+DeviceDescription.AutoInitialize],	cl
    		mov	ecx, [eax+14h]
    		mov	[ebp+DeviceDescription.DmaChannel], ecx
    		mov	ecx, [eax+1Ch]
    		mov	eax, [eax+20h]
    		mov	[ebp+DeviceDescription.DmaWidth], ecx
    		mov	[ebp+DeviceDescription.DmaSpeed], eax

    loc_2BE1F:				; CODE XREF: sub_2BD82+7D j
    		mov	edi, ds:IoGetDmaAdapter
    		lea	eax, [esi+14h]
    		push	eax		; NumberOfMapRegisters
    		lea	eax, [ebp+DeviceDescription]
    		push	eax		; DeviceDescription
    		push	dword ptr [ebx+10h] ; PhysicalDeviceObject
    		mov	[ebp+DeviceDescription.Version], 2
    		call	edi ; IoGetDmaAdapter
    		test	eax, eax
    		jnz	short loc_2BE57
    		lea	eax, [esi+14h]
    		push	eax		; NumberOfMapRegisters
    		lea	eax, [ebp+DeviceDescription]
    		push	eax		; DeviceDescription
    		push	dword ptr [ebx+10h] ; PhysicalDeviceObject
    		mov	[ebp+DeviceDescription.Version], 1
    		call	edi ; IoGetDmaAdapter
    		mov	byte ptr [esi+20h], 0
    		jmp	short loc_2BE5B
    ; ---------------------------------------------------------------------------

    loc_2BE57:				; CODE XREF: sub_2BD82+B9 j
    		mov	byte ptr [esi+20h], 1

    loc_2BE5B:				; CODE XREF: sub_2BD82+D3 j
    		pop	ebx
    		test	eax, eax
    		jnz	short loc_2BE69
    		mov	[ebp+var_4], 0C000009Ah
    		jmp	short loc_2BECE

#3187

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #3185

> @Doc.Brown
> And here it is
> Dietmar
> PS: I noticed, that you also have drive D, E.
> I deleted those entries in registry, because via this way XP does not know where to continue.

⇗ @diderius6
Same BSOD at the same time again :(
Perhaps it's my XP I will try another iso less lighter

#3188 | diderius6 | ⇗ @Doc.Brown Does this Bsod happen during install of XP and which exact number has this BSOD Dietmar

#3189

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #3188

> @Doc.Brown
> Does this Bsod happen during install of XP
> and which exact number has this BSOD
> Dietmar

Yes always the same since the beginning in fact,occuring at the middle of device installation with those code :
⇗
I tried everything in bios,modded bios or stock from Asus,Fernando's AHCI or not,USBXHCI or not,each acpi files since weeks,install from X299 ... nothing help

#3190

diderius6

⇗ @Doc.Brown
Change your acpi.sys on the harddisk, where XP install already starts, against this one
Dietmar
PS: I have had exact the same symptoms. But via my install methode I overcome this. It is one single device,
which makes this happen.
diderius6 has attached files to this post

- ⇗ acpi.rar

#3191

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #3190

> @Doc.Brown
> Change your acpi.sys on the harddisk, where XP install already starts, against this one
> Dietmar
> PS: I have had exact the same symptoms. But via my install methode I overcome this. It is one single device,
> which makes this happen.

New BSOD 7E with this one :
⇗

#3192

diderius6

⇗ @Doc.Brown
Yes, this is the Bsod, when acpi.sys cries for debugger.
Here is last acpi.sys,
change it again.
After this, I am out of ideas
Dietmar
PS: Can you hit F8 and choose "Safe Mode" at the beginning,
just before Setup restarts?
diderius6 has attached files to this post

- ⇗ acpi.rar

#3193

diderius6

⇗ @Doc.Brown
One idea I have:
Copy just my hive "system" into your folder windows\system32\config
Dietmar
diderius6 has attached files to this post

- ⇗ system.rar

#3194 | Doc.Brown | ⇗ @diderius6 Ok but with wich acpi.sys do you want I test your system hive ? This XP compatibility is starting to make feel like a fool :D Edit: yes I can choose F8 at set-up start
#3195 | diderius6 | ⇗ @Doc.Brown In this row, as you tested acpi.sys just now Dietmar PS: IF F8 really works, this means new chance.

## Page 214

#3196

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #3195

> @Doc.Brown
> In this row, as you tested acpi.sys just now
> Dietmar
> PS: IF F8 really works, this means new chance.

Yes F8 works,I didn't try to boot in safe mode yet but I have the menu
So with your system file and the acpi before the last one you've uploaded 7E BSOD again but the 2 last codes changed :
⇗

#3197 | diderius6 | ⇗ @Doc.Brown This means nothing, because it is debug acpi.sys, try other too Dietmar
#3198 | Doc.Brown | This one is with your last acpi : ⇗ With the stock 0057 bios not the modded one I try with modded bios and the acpi from your EVGA compatibility STORAHCI rar

#3199

diderius6

This is interesting,
because I remember this was only one change something like 74 => EB
in acpi.sys
Dietmar
PS: This BSOD is gone with my Bios mod for 57, yes.
No, dont change this acpi.sys. Just flash Bios with 57 mod.

#3200 | Doc.Brown | BSOD 7B 0xB84C3524,0xC0000034 with acpi from z390 Dark Bios is flashing...

#3201

diderius6

⇗ @Doc.Brown
This means only, that the registry entries in "system" need to be renewed for STORAHCI driver.
Why this happen, I have no idea. But again put entries by hand into registry helps.
This was the way for me too
Dietmar
EDIT: May be, crazy Setup from XP tries to integrate "better" driver than the STORAHCI to registry "system".
In this case, at once would be clear, what happens.
But this can be tricked out: Just copy ntoskrnl.exe and hal.dll for "Standard PC" into
windows\system32. After setup, just change them back.

#3202 | Doc.Brown | Biggest improvement ever,set-up finished !!! With your last acpi.sys,modded bios and the system file patched ... but BSOD 0A IRQL not less or equal again after last reboot this time :/ I boot in safe mod and this time i've got the Standard driver for AHCI/SATA instead of Intel and the Microsoft ACPI exclamation mark so i will add the acpi.inf file to see if it will be gone,hope BSOD will be gone too but I doubt

#3203

diderius6

⇗ @Doc.Brown
Cool, this is exact what I thought, that the XP Setup tries to change the STORAHCI entry in "system".
This is exact, what happens to me. And Now I remember that I do after this the same steps.
Only install Standard driver for AHCI/SATA (is STORAHCI) via Safe Boot f8 and thats all
Dietmar
EDIT: acpi.sys needs no *.inf at all!

#3204

gordo999

> Zitat von ⇗ IntiMD im Beitrag ¶ #3162

> For those who don't know what am I talking about, it's about one of Rudolph "rloew" Loew's patches (the AHCI one)

@IntiMDI.... remember the guy. Just looking through the URL you supplied, he seemed to be well in advance of his time.
There were two versions of Win98....Win98 and Win98SE. I started with 98 on my C: drive and later added XP as a dual boot. Win98SE ran on FAT32 and my C: drive is still FAT32. That may be contributing to my problem.
Furthermore, back in those days it was not advisable to use an entire drive as an OS. So, I partitioned much smaller drives than we have today into 40 Gb partitions. An 80 Gb drive was the standard back then so I partioned my drives with 4Gb for W98 on C:, and 40 Gb for XP on D:. I added a third 40Gb logical partition for data.
Later, when 250 Gb and 500 Gb drives became available, if I transferred my C: and D: drives to the larger drive I still had the mentality of using smaller partitions. So, I'm stuck for the time being with many confusing drive letters due to numerous smaller partitions.
The idea was to use extended partitions for data only but 40Gb became too small for XP and I began installing apps on the extended partitions. I need to step back and do some housecleaning, moving apps and files to increase partition sizes and cut back on drive letters.
Remember Partition Magic? It had a need utility for allowing the user to move an app and have PM take care of all the new partition references in the registry. Wonder if it still works?

#3205 | gordo999 | @Fernando...don't know how the previous post re Win98 got into this thread. I replied to IntiMD using quotes on another thread and it showed up here. Update...sorry, I figured it out, it's the same thread. The post to which I replied is several pages back but I was lead to it from a PM so it appeared to be at the end of the thread.
#3206 | diderius6 | ⇗ @gordo999 AOMEI is from the same people which makes Partition Magic. Even the background and the name is the same Dietmar

#3207

Doc.Brown

⇗ @diderius6
That's ok now it seems,I installed STORAHCI and the reg in safe mode but windows replace ACPI(I will change it in SP3.cab for next iso) so I also put the system file mod and set-up restart another time :D but it seems ok in normal boot now and I understand what I have to do to(I hope)
Do you know if the system file is in the SP3.cab also or somewhere else to integrate it direct in the iso build ?
Is there a way to have a silent install for STORAHCI and his .reg file during set-up ?
Anyway you're the man my friend,you're skills and knowledge are huge,this succeed is yours,so much thanks :)
Now I have to add USB and NVMe support ans see if Asus TurboV works fine

#3208

diderius6

⇗ @Doc.Brown
I am happy, that in the end it works also for you on the Gene XI board.
When you read the end of my description from
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (199)
you see, there the same steps work. But today also a new acpi.sys is "born",
the acpi.sys from outer space ) now also with 10006 BSOD mod
Dietmar
EDIT: Dont forget to copy the modded hal.dll and intelppm.sys against the timer error into
windows\system32 and windows\system32\drivers.

#3209

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #3206

> AOMEI is from the same people which makes Partition Magic.
> Even the background and the name is the same Dietmar

@diderius6...interesting. I know Symantec bought PM out then dumped it. AOMEI must have resurrected it, which is good. PM was a very good partition manager in its day, far better than anything Symantec had to offer. Glad to hear it is still around, albeit in another form.
I have AOMEI on a new Hirens disk (v.1.01), I'll look closer to see if they kept the other files from PM for moving a partition.

#3210

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #3208

> @Doc.Brown
> I am happy, that in the end it works also for you on the Gene XI board.
> When you read the end of my description from
> ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (199)
> you see, there the same steps work. But today also a new acpi.sys is "born",
> the acpi.sys from outer space ) now also with 10006 BSOD mod
> Dietmar
> EDIT: Dont forget to copy the modded hal.dll and intelppm.sys against the timer error into
> windows\system32 and windows\system32\drivers.

What is this timer error ?
Could you provide me those files please I don't have them,should I put them in my SP3.cab modded ?
Thanks

## Page 215

#3211 | diderius6 | ⇗ @Doc.Brown It is here in the forum, some posts ago ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (197) halplusintelppm.rar Dietmar PS: You can integrate them. But I was to lazy, put them always later into harddisk:))

#3212

diderius6

Here is brandnew acpi.sys from outer space )
now also with mod against BSOD 10006 and C0140008
Dietmar
EDIT: I just test this nice acpi.sys from outer space ):
It works on EVGA dark z390 board with stock Bios 107.
Now we have 2 lines of working acpi.sys,
one based on 5512 (XP SP3)
and one based on 5048 (Longhorn).
diderius6 has attached files to this post

- ⇗ acpi.rar

#3213

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #3211

> @Doc.Brown
> It is here in the forum, some posts ago ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (197)
> halplusintelppm.rar
> Dietmar
> PS: You can integrate them. But I was to lazy, put them always later into harddisk:))

thank you,i didn't see them cause it's for PAE problems i was only focus on the damn ACPI problem until now :D

#3214 | infuscomus | ⇗ @diderius6 does this ACPI 5512 work for AMD Ryzen too?

#3215

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #3212

> Here is brandnew acpi.sys from outer space )
> now also with mod against BSOD 10006 and C0140008
> Dietmar
> EDIT: I just test this nice acpi.sys from outer space ):
> It works on EVGA dark z390 board with stock Bios 107.
> Now we have 2 lines of working acpi.sys,
> one based on 5512 (XP SP3)
> and one based on 5048 (Longhorn).

⇗ @diderius6
No need of modded bios with this one instead of the last one before so this one is better ^^
Everything seems fine :
⇗
Only little thing to solve is that I have an error Code 39 during USB driver installation :
⇗
I used modded amdxhx,hal and intelppm modded for timer and there's no USBD.sys in system32\drivers,copy manually but error is still here
Tried Renesas PCIE card but doesn't work too,I think I don't have the good drivers

#3216

infuscomus

⇗ @Doc.Brown
try reinstalling the driver now that you have usbd.sys copied across.
⇗ @diderius6
I have made a txtsetup.sif that successfully copies storport.sys and usbd.sys to c:\windows\system32\drivers every time
although i am not sure which modification i made actually does the copying across
infuscomus has attached files to this post

- ⇗ TXTSETUP.SIF.TXT

#3217

diderius6

⇗ @Doc.Brown
There may be a problem with the acpi.sys from outer space ) and USB,
because it can only handle 32 bit integer.
Lenovo solved this problem, just using during compile of their DSDT the -r1
switch in Iasl on all their notebooks.
In few min I send you a new 57 mod Bios for USB
Dietmar

#3218 | Doc.Brown | ⇗ @diderius6 USB works now,I used Z390 Dark tips and tools and after put Intel 3.1 USB driver to have it working ^^ Thanks

#3219

diderius6

⇗ @infuscomus
I just update the acpi.sys from outer space )
for to work also with Ryzen,
I think it is a major step,
please test
Dietmar
diderius6 has attached files to this post

- ⇗ acpi.rar

#3220 | diderius6 | ⇗ @infuscomus About Txtsetup.sif and storport take a look at ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (190) Dietmar
#3221 | Gelip | ⇗ @diderius6 I make new tests with WinXP x64 on UEFI. The system can also be booted from a GPT partition in pure UEFI mode with Secure Boot enabled I have also added more detailed logs from WinDbg: ⇗ Boot WinXP 32-bit/64-bit on UEFI 32-bit/64-bit
#3222 | infuscomus | ⇗ @diderius6 your outerspace acpi.sys worked! nice! question: do you have to change the version numbers after modifying files? i thought that was unnecessary
#3223 | diderius6 | ⇗ @infuscomus Dont forget that this acpi.sys is from outer space ). I am happy, that it works, because this type of hack for Ryzen makes boot possible on a lot of crazy Intel boards too Dietmar

#3224

diderius6

⇗ @Gelip
Please write a new Tutorial,
with all what you reach about UEFI boot for XP.
For example disable signature check, GPT partition boot, which kind of partitions are necessary for UEFI.
Bios with EFI files for ntfs, GPT and Fat32.
May be we find a way, to integrate vga with INT 10 as *.efi file
to Bios. And the question about 32bit XP SP3
Dietmar
PS: In next days I get 3 old notebooks x220 from Lenovo. They are MUCH better than the new Lenovo Flex 10, brrr..
EDIT: There a crazy ideas possible with UEFI boot of XP.
For example, until now it is not possible to boot XP via nvme, when there is no legacy support for.
I tested this a lot, may be chance would also be in an updated nvme.sys which uses scsiport.sys instead of storport.sys.
But via EFI boot of XP, at once you can use ANY uefi driver for nvme boot of XP.
EDIT2: Please add all needed files.

#3225 | infuscomus | ⇗ @diderius6 does changing the version number need to be done? or was it just for fun?

## Page 216

#3226 | diderius6 | ⇗ @infuscomus You need to ask outer space ) Dietmar
#3227 | diderius6 | The STORAHCI driver from ⇗ @skullteria works also with ASM106 controller. This is the only generic AHCI driver for XP Dietmar
#3228 | infuscomus | ⇗ @daniel_k doing some testing - i tried to load your generic amdxhci usb 3 driver in XP textmode setup and got a D0 BSOD - Bug Check 0xD0: DRIVER_CORRUPTED_MMPOOL on an AMD AB350 motherboard.
#3229 | daniel_k | ⇗ @infuscomus, that driver is only for Intel systems. For Ryzen, ask @diderius6. My last AMD rig was a socket 939 Athlon 64 3200+.

#3230

diderius6

I found an interesting Embedded compi,
which supports XP on Bay Trail cpu
EmNANO-i2300
EmQ-i2301
NAO-660E
ARES-5300
LYNC-708-3845G2
ASLAN-W810/812C-2930G2
It has an UEFI Insyde Bios,
with interesting switch in Bios menu
APCI Selection Select boot to Acpi 3.0/Acpi 1.0B
Options are Acpi 1.0B/Acpi 3.0/Acpi 4.0/Acpi 5.0
There you could compare as much as possible,
but I dont know, how to get any of this Bios, no downloads on Website for Bios
Dietmar

#3231

daniel_k

⇗ @Mov AX, 0xDEAD
Can you help me, please?
In a PE file with .rdata section with strings and reference pointers, how can I find the code which loads those?
IDA just shows strings -> reference pointers, but doesn't tell me where the code actually does something with them.
Is there a way to find out where a function is called from when it isn't called in a conventional way?
The code I'm analyzing is being called from something like this:

    8B861C010000             mov          eax,[esi][00000011C]
    85C0                     test         eax,eax
    741E                     jz          .000011627
    8B480C                   mov          ecx,[eax][00C] -> huh?
    85C9                     test         ecx,ecx
    7405                     jz          .000011615
    FF7004                   push         d,[eax][4]
    FFD1                     call         ecx

And this one? There is nothing at that offset, all zeroed? Is it filled at runtime?

    FF15C4100300                   call         d,[0000310C4]

#3232

Doc.Brown

During comparing and modding my TXTSETUP.SIF I see there's an HIVE.INF file for adding registry key but the format is different than a .reg file.My goal is to add the STORAHCI.reg keys into this HIVE.INF and have the most easy XP installation as it could.
Is someone is able to help me to translate it with the good format please ?
The STORAHCI.reg text :

    [HKEY_LOCAL_MACHINE\System\ControlSet001\Services\storahci]
    "Type"=dword:00000001
    "Start"=dword:00000000
    "ErrorControl"=dword:00000003
    "ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,\
       72,00,69,00,76,00,65,00,72,00,73,00,5c,00,73,00,74,00,6f,00,72,00,61,00,68,\
       00,63,00,69,00,2e,00,73,00,79,00,73,00,00,00
    "Group"="SCSI Miniport"
    "DisplayName"="@mshdc.inf,%storahci_ServiceDescription%;Microsoft Standard SATA AHCI Driver"
    "DriverName"="mshdc.inf"

    [HKEY_LOCAL_MACHINE\System\ControlSet001\Services\storahci\Parameters]
    "BusType"=dword:0000000b
    "IoTimeoutValue"=dword:0000000a

    [HKEY_LOCAL_MACHINE\System\ControlSet001\Services\storahci\Parameters\Device]
    "ResetInInit"=hex(7):56,00,45,00,4e,00,5f,00,31,00,31,00,30,00,36,00,26,00,44,\
       00,45,00,56,00,5f,00,36,00,32,00,38,00,37,00,26,00,52,00,45,00,56,00,5f,00,\
       2a,00,00,00,00,00
    "SingleIO"=hex(7):56,00,45,00,4e,00,5f,00,31,00,31,00,30,00,36,00,26,00,44,00,\
       45,00,56,00,5f,00,36,00,32,00,38,00,37,00,26,00,52,00,45,00,56,00,5f,00,30,\
       00,30,00,00,00,56,00,45,00,4e,00,5f,00,31,00,31,00,30,00,36,00,26,00,44,00,\
       45,00,56,00,5f,00,36,00,32,00,38,00,37,00,26,00,52,00,45,00,56,00,5f,00,31,\
       00,30,00,00,00,56,00,45,00,4e,00,5f,00,31,00,31,00,30,00,36,00,26,00,44,00,\
       45,00,56,00,5f,00,36,00,32,00,38,00,37,00,26,00,52,00,45,00,56,00,5f,00,32,\
       00,30,00,00,00,00,00
    "IgnoreHotPlug"=hex(7):56,00,45,00,4e,00,5f,00,31,00,30,00,30,00,32,00,26,00,\
       44,00,45,00,56,00,5f,00,34,00,33,00,38,00,30,00,26,00,52,00,45,00,56,00,5f,\
       00,2a,00,00,00,00,00
    "NeverNonQueuedErrorRecovery"=hex(7):56,00,45,00,4e,00,5f,00,31,00,30,00,30,00,\
       32,00,26,00,44,00,45,00,56,00,5f,00,34,00,33,00,38,00,30,00,26,00,52,00,45,\
       00,56,00,5f,00,2a,00,00,00,00,00
    "EnableCLOReset"=hex(7):56,00,45,00,4e,00,5f,00,31,00,30,00,30,00,32,00,26,00,\
       44,00,45,00,56,00,5f,00,34,00,33,00,39,00,31,00,26,00,52,00,45,00,56,00,5f,\
       00,2a,00,00,00,00,00
    "NoFUACommand"=hex(7):48,00,54,00,45,00,2a,00,00,00,48,00,69,00,74,00,61,00,63,\
       00,68,00,69,00,2a,00,00,00,48,00,54,00,53,00,2a,00,00,00,48,00,44,00,53,00,\
       2a,00,00,00,48,00,44,00,54,00,2a,00,00,00,00,00
    "NeedSetTransferModeCommand"=hex(7):4d,00,43,00,42,00,51,00,45,00,36,00,34,00,\
       47,00,42,00,4d,00,50,00,50,00,2a,00,00,00,00,00
    "NoLPM"=hex(7):57,00,44,00,37,00,34,00,30,00,41,00,44,00,46,00,44,00,3f,00,30,\
       00,30,00,4e,00,4c,00,52,00,31,00,2a,00,00,00,57,00,44,00,43,00,20,00,57,00,\
       44,00,37,00,34,00,30,00,41,00,44,00,46,00,44,00,3f,00,30,00,30,00,4e,00,4c,\
       00,52,00,31,00,2a,00,00,00,4d,00,61,00,78,00,74,00,6f,00,72,00,20,00,36,00,\
       56,00,3f,00,3f,00,3f,00,45,00,30,00,2a,00,00,00,4d,00,61,00,78,00,74,00,6f,\
       00,72,00,20,00,36,00,56,00,3f,00,3f,00,3f,00,46,00,30,00,2a,00,00,00,4d,00,\
       61,00,78,00,74,00,6f,00,72,00,20,00,37,00,56,00,3f,00,3f,00,3f,00,45,00,30,\
       00,2a,00,00,00,4d,00,61,00,78,00,74,00,6f,00,72,00,20,00,37,00,56,00,3f,00,\
       3f,00,3f,00,46,00,30,00,2a,00,00,00,00,00

    [HKEY_LOCAL_MACHINE\System\ControlSet001\Services\storahci\Parameters\PnpInterface]
    "5"=dword:00000001

    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\PCI#CC_010601]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="storahci"

and the HIVE.inf exemple of content :

    HKLM,"SYSTEM\CurrentControlSet\Control\FileSystem","NtfsDisable8dot3NameCreation",0x00010003,0
    HKLM,"SYSTEM\CurrentControlSet\Control\FileSystem","Win31FileSystem",0x00010001,0
    HKLM,"SYSTEM\CurrentControlSet\Control\FileSystem","Win95TruncatedExtensions",0x00010001,1
    HKLM,"SYSTEM\CurrentControlSet\Control\GraphicsDrivers",,0x00000012
    HKLM,"SYSTEM\CurrentControlSet\Control\GraphicsDrivers\DCI","Timeout",0x00010003,7
    HKLM,"SYSTEM\CurrentControlSet\Control\GraphicsDrivers\UseNewKey",,0x00000012
    HKLM,"SYSTEM\CurrentControlSet\Control\GroupOrderList","Base",0x00030003,\
    0e,00,00,00,0e,00,00,00,01,00,00,00,02,00,00,00,03,00,00,00,04,00,00,00,05,\
    00,00,00,06,00,00,00,07,00,00,00,08,00,00,00,09,00,00,00,0a,00,00,00,0b,00,\
    00,00,0c,00,00,00,0d,00,00,00
    HKLM,"SYSTEM\CurrentControlSet\Control\GroupOrderList","Boot Bus Extender",0x00030001,\
    05,00,00,00,\
    01,00,00,00,\
    02,00,00,00,\
    03,00,00,00,\
    04,00,00,00,\
    05,00,00,00
    HKLM,"SYSTEM\CurrentControlSet\Control\GroupOrderList","Extended Base",0x00030001,\
    03,00,00,00,01,00,00,00,02,00,00,00,04,00,00,00
    HKLM,"SYSTEM\CurrentControlSet\Control\GroupOrderList","Keyboard Class",0x00030003,\
    01,00,00,00,01,00,00,00
    HKLM,"SYSTEM\CurrentControlSet\Control\GroupOrderList","Keyboard Port",0x00030001,\
    03,00,00,00,01,00,00,00,02,00,00,00,03,00,00,00
    HKLM,"SYSTEM\CurrentControlSet\Control\GroupOrderList","Ndis",0x00030003,\
    09,00,00,00,01,00,00,00,02,00,00,00,03,00,00,00,04,00,00,00,05,00,00,00,06,\
    00,00,00,07,00,00,00,08,00,00,00,09,00,00,00
    HKLM,"SYSTEM\CurrentControlSet\Control\GroupOrderList","Network",0x00030003,\
    03,00,00,00,01,00,00,00,02,00,00,00,03,00,00,00
    HKLM,"SYSTEM\CurrentControlSet\Control\GroupOrderList","Parallel arbitrator",0x00030003,\
    01,00,00,00,01,00,00,00
    HKLM,"SYSTEM\CurrentControlSet\Control\GroupOrderList","PNP_TDI",0x00030003,\
    02,00,00,00,01,00,00,00,02,00,00,00
    HKLM,"SYSTEM\CurrentControlSet\Control\GroupOrderList","Pointer Class",0x00030003,\
    01,00,00,00,01,00,00,00
    HKLM,"SYSTEM\CurrentControlSet\Control\GroupOrderList","Pointer Port",0x00030003,\
    03,00,00,00,01,00,00,00,02,00,00,00,03,00,00,00
    HKLM,"SYSTEM\CurrentControlSet\Control\GroupOrderList","Primary Disk",0x00030001,\
    05,00,00,00,01,00,00,00,02,00,00,00,03,00,00,00,04,00,00,00,05,00,00,00
    HKLM,"SYSTEM\CurrentControlSet\Control\GroupOrderList","SCSI CDROM Class",0x00030001,\
    02,00,00,00,01,00,00,00,02,00,00,00
    HKLM,"SYSTEM\CurrentControlSet\Control\GroupOrderList","SCSI Class",0x00030001,\
    03,00,00,00,01,00,00,00,02,00,00,00,03,00,00,00
    HKLM,"SYSTEM\CurrentControlSet\Control\GroupOrderList","SCSI Miniport",0x00030001,\
    3f,00,00,00,\
    00,01,00,00,\
    01,01,00,00,\
    19,00,00,00,\
    01,00,00,00,\
    02,00,00,00,\
    03,00,00,00,\
    04,00,00,00,\
    05,00,00,00,\
    06,00,00,00,\

I don't know how to name DWORD,HEX... keys in this format,I think it's the values like 0x00030001 and 0x00030003 in the lines but don't understand what is really is ...
Thanks

#3233

diderius6

⇗ @Doc.Brown
For a first try you can use nlite.
Compare txtsetup.sif before integrating STORAHCI
with txtsetup.sif after STORAHCI integrated.
I remember, that it was 1 line (even only a word)
that XP Setup changed in registry,
which gives the BSOD 7B after reboot on XP install,
something like "just another name for STORAHCI"
Dietmar

#3234

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #3231

> In a PE file with .rdata section with strings and reference pointers, how can I find the code which loads those?
> IDA just shows strings -> reference pointers, but doesn't tell me where the code actually does something with them.
> Is there a way to find out where a function is called from when it isn't called in a conventional way?

there no way to determinate when and where will be used some of target address, you are found a part of some struct or enum.
ida is not perfect, sometime offset to string stored in other structure, so hex-search for offset too. in worst case code uses multi level relative access: mov esi, base; mov edi, [esi+43h]; mov eax, [edi+86h] - all offsets calculated at runtime

> Zitat von ⇗ daniel_k im Beitrag ¶ #3231

> And this one? There is nothing at that offset, all zeroed? Is it filled at runtime?
> FF15C4100300 call d,[0000310C4]

will be filled at runtime by loader (if it is import) or code itself before, [0000310C4] is just pointer to function

#3235 | daniel_k | ⇗ @Mov AX, 0xDEAD, thanks! Without using a debugger this is proving to be impossible.

#3236

Mov AX, 0xDEAD

> Zitat von ⇗ Doc.Brown im Beitrag ¶ #3232

> and the HIVE.inf exemple of content :

>     HKLM,"SYSTEM\CurrentControlSet\Control\FileSystem","NtfsDisable8dot3NameCreation",0x00010003,0
>     HKLM,"SYSTEM\CurrentControlSet\Control\FileSystem","Win31FileSystem",0x00010001,0
>     HKLM,"SYSTEM\CurrentControlSet\Control\FileSystem","Win95TruncatedExtensions",0x00010001,1
>     HKLM,"SYSTEM\CurrentControlSet\Control\GraphicsDrivers",,0x00000012
>     HKLM,"SYSTEM\CurrentControlSet\Control\GraphicsDrivers\DCI","Timeout",0x00010003,7
>     HKLM,"SYSTEM\CurrentControlSet\Control\GraphicsDrivers\UseNewKey",,0x00000012
>     HKLM,"SYSTEM\CurrentControlSet\Control\GroupOrderList","Base",0x00030003,\
>     0e,00,00,00,0e,00,00,00,01,00,00,00,02,00,00,00,03,00,00,00,04,00,00,00,05,\
>     00,00,00,06,00,00,00,07,00,00,00,08,00,00,00,09,00,00,00,0a,00,00,00,0b,00,\
>     00,00,0c,00,00,00,0d,00,00,00

> I don't know how to name DWORD,HEX... keys in this format,I think it's the values like 0x00030001 and 0x00030003 in the lines but don't understand what is really is ...

0x00000000 Default (only for key/leaf)
0x00000002 String
0x00010000 Multi String
0x00010001 Dword
0x00010003 Dword don't overwrite an exsting entry
0x00020002 Expandable String
0x00030003 Binary (sequence of bytes)
0x00000012 new key/leaf
⇗ https://msdn.microsoft.com/en-us/windows/desktop/ff546320

#3237

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #3233

> @Doc.Brown
> For a first try you can use nlite.
> Compare txtsetup.sif before integrating STORAHCI
> with txtsetup.sif after STORAHCI integrated.
> I remember, that it was 1 line (even only a word)
> that XP Setup changed in registry,
> which gives the BSOD 7B after reboot on XP install,
> something like "just another name for STORAHCI"
> Dietmar

Ok thanks for the tip,I will look for it perhaps it will indicate me how to intregate reg keys in this file ;)

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3236

> 0x00000000 Default (only for key/leaf)
> 0x00000002 String
> 0x00010000 Multi String
> 0x00010001 Dword
> 0x00010003 Dword don't overwrite an exsting entry
> 0x00020002 Expandable String
> 0x00030003 Binary (sequence of bytes)
> 0x00000012 new key/leaf
> ⇗ https://msdn.microsoft.com/en-us/windows/desktop/ff546320

Thank you it will help me to understand(or try to) so for an hex value I have to use the Binary value isn't it ? like for this for exemple :

    [HKEY_LOCAL_MACHINE\System\ControlSet001\Services\storahci\Parameters\Device]
    "ResetInInit"=hex(7):56,00,45,00,4e,00,5f,00,31,00,31,00,30,00,36,00,26,00,44,\
       00,45,00,56,00,5f,00,36,00,32,00,38,00,37,00,26,00,52,00,45,00,56,00,5f,00,\
       2a,00,00,00,00,00
    "SingleIO"=hex(7):56,00,45,00,4e,00,5f,00,31,00,31,00,30,00,36,00,26,00,44,00,\
       45,00,56,00,5f,00,36,00,32,00,38,00,37,00,26,00,52,00,45,00,56,00,5f,00,30,\
       00,30,00,00,00,56,00,45,00,4e,00,5f,00,31,00,31,00,30,00,36,00,26,00,44,00,\
       45,00,56,00,5f,00,36,00,32,00,38,00,37,00,26,00,52,00,45,00,56,00,5f,00,31,\
       00,30,00,00,00,56,00,45,00,4e,00,5f,00,31,00,31,00,30,00,36,00,26,00,44,00,\
       45,00,56,00,5f,00,36,00,32,00,38,00,37,00,26,00,52,00,45,00,56,00,5f,00,32,\
       00,30,00,00,00,00,00
    "IgnoreHotPlug"=hex(7):56,00,45,00,4e,00,5f,00,31,00,30,00,30,00,32,00,26,00,\
       44,00,45,00,56,00,5f,00,34,00,33,00,38,00,30,00,26,00,52,00,45,00,56,00,5f,\
       00,2a,00,00,00,00,00
    "NeverNonQueuedErrorRecovery"=hex(7):56,00,45,00,4e,00,5f,00,31,00,30,00,30,00,\
       32,00,26,00,44,00,45,00,56,00,5f,00,34,00,33,00,38,00,30,00,26,00,52,00,45,\
       00,56,00,5f,00,2a,00,00,00,00,00
    "EnableCLOReset"=hex(7):56,00,45,00,4e,00,5f,00,31,00,30,00,30,00,32,00,26,00,\
       44,00,45,00,56,00,5f,00,34,00,33,00,39,00,31,00,26,00,52,00,45,00,56,00,5f,\
       00,2a,00,00,00,00,00
    "NoFUACommand"=hex(7):48,00,54,00,45,00,2a,00,00,00,48,00,69,00,74,00,61,00,63,\
       00,68,00,69,00,2a,00,00,00,48,00,54,00,53,00,2a,00,00,00,48,00,44,00,53,00,\
       2a,00,00,00,48,00,44,00,54,00,2a,00,00,00,00,00
    "NeedSetTransferModeCommand"=hex(7):4d,00,43,00,42,00,51,00,45,00,36,00,34,00,\
       47,00,42,00,4d,00,50,00,50,00,2a,00,00,00,00,00
    "NoLPM"=hex(7):57,00,44,00,37,00,34,00,30,00,41,00,44,00,46,00,44,00,3f,00,30,\
       00,30,00,4e,00,4c,00,52,00,31,00,2a,00,00,00,57,00,44,00,43,00,20,00,57,00,\
       44,00,37,00,34,00,30,00,41,00,44,00,46,00,44,00,3f,00,30,00,30,00,4e,00,4c,\
       00,52,00,31,00,2a,00,00,00,4d,00,61,00,78,00,74,00,6f,00,72,00,20,00,36,00,\
       56,00,3f,00,3f,00,3f,00,45,00,30,00,2a,00,00,00,4d,00,61,00,78,00,74,00,6f,\
       00,72,00,20,00,36,00,56,00,3f,00,3f,00,3f,00,46,00,30,00,2a,00,00,00,4d,00,\
       61,00,78,00,74,00,6f,00,72,00,20,00,37,00,56,00,3f,00,3f,00,3f,00,45,00,30,\
       00,2a,00,00,00,4d,00,61,00,78,00,74,00,6f,00,72,00,20,00,37,00,56,00,3f,00,\
       3f,00,3f,00,46,00,30,00,2a,00,00,00,00,00

and String value for entry like this :

> Zitat

> "Group"="SCSI Miniport"
> "DisplayName"="@mshdc.inf,%storahci_ServiceDescription%;Microsoft Standard SATA AHCI Driver"
> "DriverName"="mshdc.inf"

Am I right ?
Thanks

#3238

diderius6

⇗ @Doc.Brown
From my original registry by hand entries I make a new STORAHCI.inf
using the nice tool reg2inf.
Now the way is easy: Integrate with nlite this driver
and BSOD 7B should be gone,
Dietmar
PS: When you want to know what happens for STORAHCI in Txtsetup.sif:
Just compare Txtsetup.sif before and after nlite. Also look at the post from ⇗ @daniel_k for the storport.sys integration.
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (190)
EDIT: This one automatically integrates also storport.sy_ in i386 folder.
But there are a lot of more changes, not only in txtsetup.sif.
diderius6 has attached files to this post

- ⇗ storahci.rar

#3239 | dencorso | ⇗ @diderius6: you should give Erwan Labalec's excellent OffLineReg a try! With it one can connect a drive to another machine via USB/SATA converter and then just point to the remote registry and edit it and save (or commit) the edits. It's much easier than the traditional "Otto" method you just reminded me of sof posts ago! Here are the links: ⇗ http://reboot.pro/files/file/313-offlinereg/ (the program - it does have a nice GUI version included) and ⇗ http://mistyprojects.co.uk/documents/off.../offlinereg.htm (a manual for the command line version). Enjoy!

#3240

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #3238

> @Doc.Brown
> From my original registry by hand entries I make a new STORAHCI.inf
> using the nice tool reg2inf.
> Now the way is easy: Integrate with nlite this driver
> and BSOD 7B should be gone,
> Dietmar
> PS: When you want to know what happens for STORAHCI in Txtsetup.sif:
> Just compare Txtsetup.sif before and after nlite. Also look at the post from @daniel_k for the storport.sys integration.
> ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (190)
> EDIT: This one automatically integrates also storport.sy_ in i386 folder.
> But there are a lot of more changes, not only in txtsetup.sif.

Wow awesome,so much thanks :)
I searched this afternoon for a tool or online converter without any success !
I compared my Txtsetup.sif with the one linked by Infuscomus member few post ago,added his entry for storport,usbd,usbxhc and usbhub30 in mine,not tested yet I'll give a try by the week but with this Storahci I don't need to test it anymore I think or only for usbd perhaps.

## Page 217

#3241

diderius6

XP SP3 Setup seems not to like the STORAHCI driver.
I make a direct CD install for the EVGA dark z390 motherboard with XP unfriendly 107 Bios,
with last acpi.sys from outer space )
and with all modifikations as above described.
All went ok.
But on the very last reboot I got again BSOD 7B.
The parameters in service for Storahci suddently are empty
and the most evil is new one, after I compare with working XP I found this key is missed in
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\PCI\VEN_8086&DEV_A352
"Service"="storahci"
Dietmar
PS: So, as before I add by hand the registry entries. Again Bsod 7B.
Then I add by hand also the missing "Service"="storahci"
and this time XP starts with full ACPI, strange..

#3242

XPLives

> Zitat von ⇗ daniel_k im Beitrag ¶ #3099

> > Zitat von ⇗ gordo999 im Beitrag ¶ #3090

> > > Zitat von ⇗ daniel_k im Beitrag ¶ #3085

> > > Won't help because that is the same driver modded by me.

> > Are you the same daniel_k from Creative driver mod fame? If so, good to see you here and thanks for all your good work in that arena.
> > Trying to get Win XP going on an 8th generation Asus B360M so I'll be reading through this thread for hints then posting some questions.

> Yep, that's me! Glad to help!
> At this point, we've solved most issues.
> Should be easy to get it working, many people contributing here!

⇗ @daniel_k
I had meant to post this on October the 13th. I wasn't sure at first where I've seen your name before over the years. But it is strange and out of the blue that you appeared and started modding things on this board. At first I had thought your name looked familiar but with the _K it could have been anyone that just happened to use the same name and I didn't know you were from Brazil.
Now it finally clicked although I've never used any of your sound drivers yet (but might for Vista/Windows 7 retro gaming sometime in the future) and it now makes sense why you've been doing this modding for USB and other drivers naturally with your Assembly skills. Now at first it threw me since you are from Brazil and did a little digging and found you are Daniel Kawakami and also Asian. The curiosity is I am actually located right by the Creative Labs original office which later became your future nemesis in a way.
So I have to wonder what originally drew you to this Win-RAID board? Or were you already here under another name?
What exactly is your goal here?
Are you a Windows 2000 / XP / 2003 OS fan?
Were you originally looking for some help with something specific?
Can you explain if there was a website link or a post on some other site somewhere that drew you to this board to make an account here?
I haven't written too many topics on Sound Cards here yet but were you a heavy Sound Blaster user from the early ISA days or did your interest begin during the PCI era of sounds cards like Ensoniq, Live, Audigy+ and then you switched to Vista OS which led you to start modding the drivers to get back the XP audio features that were missing?
It's a shame Creative Labs tried to crack down on you for that work as they couldn't see you were helping them and Microsoft Vista. I'm glad you are still around and have now focused on XP/2003 driver modding.
Thanks for your recent contributions.
You can respond to me privately if you wish if any of these questions are too personal to post answers here but I think many here would be curious.

#3243

infuscomus

⇗ @daniel_k
oh ok, I thought that because it was originally an AMD driver modded to work for intel I assumed it was generic would still work for AMD Ryzen.
do you still have all your modded usb3 driver attempts? - I'd assume they're still attached in this thread somewhere? it's hard to navigate this enormous thread.
I would like to test them all to see if any of them can be made to work in XP textmode setup.

#3244

Mov AX, 0xDEAD

I repeated previous tests on Windows 7 x32 Pro "N" with pae_license_unlocked:
1) original hal:
VIA USB3.0 driver - requests dma64, works fine
AMD USB3.0 hacked driver - requests dma64, works fine
Creative X-fi 2.30.0011- requests dma32, works fine
MS SATA ataport.sys/pciidex.sys - requests dma64, works fine
2) hal_force_high_addr
if driver declare support dma64 and request memory for dma (AllocateCommonBuffer), hal forced to allocate memory only from HIGH adressses. This mean hardware will survive only with adresses >4Gb
VIA USB3.0 driver - requests dma64, works fine
AMD USB3.0 hacked driver - requests dma64, works fine
Creative X-fi 2.30.0011 - requests dma32, works fine
MS SATA ataports/pciidex - requests dma64, works fine
3) hal_force_dma32
any dma64 request forced to dma32, same behavior as patchpae3, but patchpae3 miss limiting allocation <4Gb
VIA USB3.0 driver - dma64->dma32, not start, Error 10
AMD USB3.0 hacked driver - dma64->dma32, not work with Flash drives
Creative X-fi 2.30.0011 - dma32->dma32, works fine
MS SATA ataports/pciidex - dma64->dma32, works fine
Difference to WinXP:
- Creative X-fi x32 works on Win7 with any config
- AMD USB3.0 hacked driver works on Win7 with 64dma without problems
- Win7 allocate memory from HIGH range from top to low adresses (1:3E xx xx xx) vs WinXP low to top (1:00 5B xx xx). PC maximal physical address = 1:3F000000

#3245 | coldwove | Trying to get XP SP3 cooperating with Threadripper and it's not having any of it, keep on bsoding on A5. Any suggestions / advice? Did my best to follow the stuff that's been posted in the past regarding ryzen.
#3246 | skullteria | Well, i have a idea, however, i'm not good with it. We can find on last Nvidia driver with support for XP if can be hacked to support 3d on Geforce serie 1000 (like Geforce GTX 1060).

#3247

diderius6

⇗ @coldwove
Oh nice, Threadripper with 32 cores.
First we need to look, where the problem with XP SP3 is in this.
Have you tried an install with hitting F5 during setup?
Via this you can choose "Standard PC" and if this works,
I dont know a reason, why full XP install should not work.
Please write the exact number of your A5 BSOD
Dietmar

#3248

daniel_k

⇗ @Mov AX, 0xDEAD
Really interesting the differences between XP and Win7 memory allocation.
Can we hack the logic of XP's HAL to work like Win7?
As I've said before, drivers written by MCCI works perfectly. They managed to overcome those XP addressing issues.
Please take a look at these drivers I've attached:
- all standard drivers (no WDF)
- amdxhc, nusb3xhc and rusb3xhc corrupt NTVDM/VGA with PAE enabled.
- asmtxhci.sys and tixhci.sys work in all scenarios (my board has an ASM2142 controller). Attached first public versions of these drivers, and the IoGetDmaAdapter has always been the same in later versions.
- Fortunately, XP x64 has no issues with any of the USB drivers.
I thought about applying the MCCI's method of IoGetDmaAdapter in asmtxhci and tixhci. What do you think?

#3249

Doc.Brown

> Zitat von ⇗ diderius6 im Beitrag ¶ #3241

> XP SP3 Setup seems not to like the STORAHCI driver.
> I make a direct CD install for the EVGA dark z390 motherboard with XP unfriendly 107 Bios,
> with last acpi.sys from outer space )
> and with all modifikations as above described.
> All went ok.
> But on the very last reboot I got again BSOD 7B.
> The parameters in service for Storahci suddently are empty
> and the most evil is new one, after I compare with working XP I found this key is missed in
> [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\PCI\VEN_8086&DEV_A352
> "Service"="storahci"
> Dietmar
> PS: So, as before I add by hand the registry entries. Again Bsod 7B.
> Then I add by hand also the missing "Service"="storahci"
> and this time XP starts with full ACPI, strange..

Thanks for your feed back :)
Do you know what it could be the cause ?
There's a part for Delete keys after install in the HIVESYS perhaps that deserve to take a look if there's nothing for storahci

#3250

daniel_k

> Zitat von ⇗ XPLives im Beitrag ¶ #3242

> So I have to wonder what originally drew you to this Win-RAID board? Or were you already here under another name?
> ...
> Were you originally looking for some help with something specific?
> ...
> Can you explain if there was a website link or a post on some other site somewhere that drew you to this board to make an account here?

Getting UEFI BIOS modules up to date. Thanks to this forum and its contributors, now I'm very experienced to it and have my own techniques and hacks.
Had a long time experience with AMI and Award BIOS.

> Zitat

> What exactly is your goal here?

To fix what is broken or intentionally broken.

> Zitat

> Are you a Windows 2000 / XP / 2003 OS fan?

Kind of. It's fun to get legacy OSes running on modern hardware.
Pre-Vista OSes are non-bloated and have some unique features, such as Hardware Directsound. Compatible games run in all their glory.

> Zitat

> I haven't written too many topics on Sound Cards here yet but were you a heavy Sound Blaster user from the early ISA days or did your interest begin during the PCI era of sounds cards like Ensoniq, Live, Audigy+ and then you switched to Vista OS which led you to start modding the drivers to get back the XP audio features that were missing?

My first soundcard was an ISA SB32 PnP that came with a Multimedia kit. I've had SB Live! (4.1), SB Live! 5.1, SB Audigy, SB Audigy 2 ZS, SB X-Fi XtremeGamer PCI, SB X-Fi Titanium PCIe and SB Z.
Regarding Vista+, I was really pissed because Creative intentionally disabled some features if OS version is Vista or later.
Let's get back to the topic, please.

#3251

diderius6

⇗ @Doc.Brown
May be the problem is,
that nlite and XP nothing know about storahci driver.
If this is true, a look in the setupfiles from Win8 ) may help,
where storahci together with storport is at home
Dietmar

#3252

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #3251

> If this is true, a look in the setupfiles from Win7 may help,
> where storahci together with storport is at home

storahci is win8+ feature, not win7

#3253 | diderius6 | ⇗ @Mov AX, 0xDEAD I just look at Vista and there was no STORAHCI at all:)) Dietmar

#3254

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #3248

> Can we hack the logic of XP's HAL to work like Win7?

i'm working on it, don't expect much, just test to see what will happen

> Zitat von ⇗ daniel_k im Beitrag ¶ #3248

> Please take a look at these drivers I've attached:

sorry, i dont want to dig deeper with usb3 drivers, maybe later when i'l have enough time

#3255

XPLives

> Zitat von ⇗ daniel_k im Beitrag ¶ #3248

> ⇗ @Mov AX, 0xDEAD
> Really interesting the differences between XP and Win7 memory allocation.
> Can we hack the logic of XP's HAL to work like Win7?
> As I've said before, drivers written by MCCI works perfectly. They managed to overcome those XP addressing issues.
> Please take a look at these drivers I've attached:
> - all standard drivers (no WDF)
> - amdxhc, nusb3xhc and rusb3xhc corrupt NTVDM/VGA with PAE enabled.
> - asmtxhci.sys and tixhci.sys work in all scenarios (my board has an ASM2142 controller). Attached first public versions of these drivers, and the IoGetDmaAdapter has always been the same in later versions.
> - Fortunately, XP x64 has no issues with any of the USB drivers.
> I thought about applying the MCCI's method of IoGetDmaAdapter in asmtxhci and tixhci. What do you think?

⇗ @daniel_k , ⇗ @Mov AX, 0xDEAD
VIA USB3.0 driver - dma64->dma32, not start, Error 10
AMD USB3.0 hacked driver - dma64->dma32, not work with Flash drives
These are disturbing. So it is possible to convert these drivers to dma32?
These bugs may not limited to just flash drives. I found USB Webcams may hang or not work properly. You can try to access the Webcam in My Computer.
Another issue is using USB Audio combined with a USB hard drive and playing a video off the USB hard drive. Audio or Video may stutter during playback.
I did much testing with the USB 3.0 PCIe cards. Although the fastest model was the NEC on my benchmarks, I found the TI model had the best seek times. So if you were to skip to any point on a HD Video it had the lowest latency.
If you want the best driver to modify for universal USB 3.0 modding it's the TI model if all features transfer over.

## Page 218

#3256

Gelip

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #3230

> I found an interesting Embedded compi,
> which supports XP on Bay Trail cpu

Maybe Pineview Gateway LT23 Netbook - this have only 32-bit drivers (WinXP and Win7) and UEFI bios:
⇗
Probably the bios is UEFI 32-bit because if I extract some driver in UEFITool - Extract body... as an .exe file and open it in CFF Explorer, it says that the file type is Portable Executable 32:
⇗ Gateway -> Netbook -> LT Series -> LT23
⇗
⇗
P.S. Gateway is equivalent Packard Bell e.g. Packard Bell ENME69BMP = Gateway LT41P04u
It's probably similar with other models.

#3257 | Gelip | ⇗ @diderius6 Gateway LT23 is same as Packard Bell DOT SPT: ⇗ Packard Bell -> Netbook -> dot -> dot spt Exactly same bioses: ⇗

#3258

diderius6

⇗ @Gelip
Yes, thanks, I just extract its DSDT.
No ACPI2.0 word "tointeger" can be found there.
It is an Insyde Bios
and it can be used like the Rosetta Stone
for other Insyde Bios
Dietmar
diderius6 has attached files to this post

- ⇗ dsdtA.rar

#3259 | Gelip | PE Deconstructor also display architecture 32-bit (i686) of Dxemain.bin file extracted from UEFI Tool: ⇗ I think LT23 (DOT SPT) is a good model that can work with WinXP 32-bit in UEFI because have drivers for WinXP.

#3260

diderius6

⇗ @Doc.Brown
I make a new test with the same CD for XP SP3 using STORAHCI driver.
Again I get BSOD 7B on last reboot.
But now I add ONLY this value to registry and this is enough for full ACPI start
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\PCI\VEN_8086&DEV_A352
"Service"="storahci"
Dietmar
PS: This means, there is a conflict with entry in Services for STORAHCI and this ENUM above.
Services for STORAHCI is now empty.

#3261

daniel_k

⇗ @diderius6
You are having a hard time with driver integration because you are not doing it correctly.
I'm sharing my pre-tested integrated drivers, apply to a CLEAN XP SP3 English (ENU) extracted ISO.
\iaStor = legacy RST 11.2.0.1006
\iaStorA = RSTe 4.7.0.1098 (modded by me)
\storahci = StorAHCI from skullteria
Pick one of them and copy and overwrite the files in the \i386 folder of the extracted ISO.
Included USB drivers:
- Intel USB3 modded (amdxhc)
- ASMedia USB3 1.16.58.1
- VIA USB3 6.1.7600.5601
EDIT: Updated files, including original files from CD. To apply on localized ISOs, just compare modified and original and apply the changes.

#3262

daniel_k

> Zitat von ⇗ XPLives im Beitrag ¶ #3255

> VIA USB3.0 driver - dma64->dma32, not start, Error 10
> AMD USB3.0 hacked driver - dma64->dma32, not work with Flash drives
> These are disturbing. So it is possible to convert these drivers to dma32?
> These bugs may not limited to just flash drives. I found USB Webcams may hang or not work properly. You can try to access the Webcam in My Computer.
> Another issue is using USB Audio combined with a USB hard drive and playing a video off the USB hard drive. Audio or Video may stutter during playback.
> I did much testing with the USB 3.0 PCIe cards. Although the fastest model was the NEC on my benchmarks, I found the TI model had the best seek times. So if you were to skip to any point on a HD Video it had the lowest latency.
> If you want the best driver to modify for universal USB 3.0 modding it's the TI model if all features transfer over.

Those issues are related to PAE, otherwise they work as intended.
Are you trying PAE?
TI and ASMedia drivers are a nightmare to mod, very well "protected" against hacking, not a simple device ID check like the ones from Renesas, VIA and AMD.

#3263

XPLives

> Zitat von ⇗ daniel_k im Beitrag ¶ #3250

> > Zitat von ⇗ XPLives im Beitrag ¶ #3242

> > So I have to wonder what originally drew you to this Win-RAID board? Or were you already here under another name?
> > ...
> > Were you originally looking for some help with something specific?
> > ...
> > Can you explain if there was a website link or a post on some other site somewhere that drew you to this board to make an account here?

> Getting UEFI BIOS modules up to date. Thanks to this forum and its contributors, now I'm very experienced to it and have my own techniques and hacks.
> Had a long time experience with AMI and Award BIOS.

> > Zitat

> > What exactly is your goal here?

> To fix what is broken or intentionally broken.

> > Zitat

> > Are you a Windows 2000 / XP / 2003 OS fan?

> Kind of. It's fun to get legacy OSes running on modern hardware.
> Pre-Vista OSes are non-bloated and have some unique features, such as Hardware Directsound. Compatible games run in all their glory.

> > Zitat

> > I haven't written too many topics on Sound Cards here yet but were you a heavy Sound Blaster user from the early ISA days or did your interest begin during the PCI era of sounds cards like Ensoniq, Live, Audigy+ and then you switched to Vista OS which led you to start modding the drivers to get back the XP audio features that were missing?

> My first soundcard was an ISA SB32 PnP that came with a Multimedia kit. I've had SB Live! (4.1), SB Live! 5.1, SB Audigy, SB Audigy 2 ZS, SB X-Fi XtremeGamer PCI, SB X-Fi Titanium PCIe and SB Z.
> Regarding Vista+, I was really pissed because Creative intentionally disabled some features if OS version is Vista or later.
> Let's get back to the topic, please.

⇗ @daniel_k
Interesting... intentionally broken? I think the most important "broken" thing now would be the ACPI and really the only final obstacle. Been that way since SkyLake. Once this is completely fixed I would say that would bring compatibility back.
Makes sense now... :) What was your previous motherboard before you got the Coffee Lake?
True Pre-Vista OSes are non-bloated but can also be installed multiple times with their own drive letter on different partitions. Ever notice in Vista+ when you boot into your system the drive is always assigned C: rather than in 2K/XP/2K3 it actually uses the correct partition drive letter?
I'll leave the other comments to your PM.

#3264 | diderius6 | ⇗ @daniel_k Thanks a lot, this is really nice work:))! How do you know how to treat STORAHCI? Because USB and Iastor work for me with nlite, Dietmar
#3265 | daniel_k | ⇗ @diderius6 Maybe some typo in INF file, don't know. Maybe nlite doesn't like something. I don't use 3rd party software, do everything manually. Got used to do it. Please try it.

#3266

diderius6

⇗ @daniel_k
I make a compare between your and my TXTSETUP.SIF, SETUPREG.HIV, HIVESYS.INF, HIVESFT.INF, DOSNET.INF
they are nearly identic, nearly..
Now I test yours
Dietmar
EDIT: I find the important difference: nlite does not copy storahci.inf into folder i386 for me.
I thought, this was not necessary because of Txtsetup.oem. But now I see, what for all the drivers before
works is not ok, *.inf also in i386 is better.
EDIT2: Setup cries about some *.dll are missed. Yes, I found, that you have a Multilanguage Setup CD,
while mine is only german. So, MUILanguages entries are missed in my HIVESYS.INF and no *.dll for this, no problem.
Until now, all is ok, I am still installing:)).. No USB during install.
EDIT3: Happens on last reboot the same BSOD 7B as for me for STORAHCI, so the reason is still unknown.
In Services the storahci entry is also empty. The path to the driver storahci.sys is not there.
And exact as for me this entry is missed too
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\PCI\VEN_8086&DEV_A352
"Service"="storahci"
EDIT4: And the cure is also exact as for me: To add "Service"="storahci" there.

#3267

coldwove

⇗ @diderius6 Thanks for your reply, no 32 core, just a 1950x i'd like to bench. F5 got a bit further but crashed on 7B Here are the full codes for both modes:
7B
F78D2524
C0000034
0
0
A5
2
8A5C5450
1
8A590008
I guess some more system info: X399M Taichi and i'm running off of the chipset sata ports, this board has no extra controller.

#3268 | diderius6 | ⇗ @coldwove BSOD A5 (0x02,..) should not happen with acpi.sys from ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (215) Dietmar
#3269 | coldwove | ⇗ @diderius6 Sadly it seems not, same set of BSOD's. Could you outline what i should be doing with these files just in case i'm doing it wrong? Currently integrating them into DRIVER.CAB. Thanks.

#3270

daniel_k

⇗ @diderius6
Sorry, TXTSETUP.SIF in the \storahci folder was an older version.
Tested right now in VirtualBox, USB3 driver is installed just fine. You should see 2 warnings of unsigned drivers: one for STORAHCI and the other one for Intel USB3.
As this is an English language forum, I usually use an English ISO by default when sharing modifications.
I've updated the package and included original files, so just compare them and apply to your German ISO.

## Page 219

#3271

coldwove

⇗ @diderius6
Using a fresh iso + acpi.sys i'm getting a different A5 bsod:
A5
11
8
0xF75E7200
0x20120913

#3272 | diderius6 | ⇗ @daniel_k USB works now during installation with STORAHCI but BSOD 7B at last reboot stays the same Dietmar

#3273

infuscomus

⇗ @diderius6
in txtsetup.sif try these
storahci.inf = 100,,,,,,,20,0,0
storahci.reg = 1984,,,,,,,1984,0,0
storahci.sys = 100,,,,,,,4,0,0
storport.sys = 100,,,,,,,4,0,0
also in storahci.inf i changed
[SourceDisksFiles]
storahci.sys = 1
to
[SourceDisksFiles]
storahci.sys = 12
because it should already be in c:\windows\system32\drivers if it copied correctly.

#3274 | infuscomus | ⇗ @coldwove did you want to try my modded XP ISO?
#3275 | coldwove | ⇗ @infuscomus Yeah i'd love to, been trying for most of today and only failed so far.
#3276 | Adi681 | Hello ! I have a PC from 2017 with G4400 (skylake) and an MSI H110 Gaming Mobo. I would like to install XP on this machine but sadly I don't know wich drivers are required for integration into my original ISO (ripped from original DVD).
#3277 | infuscomus | ⇗ @coldwove i sent you a PM with my modded ISO.

#3278

coldwove

⇗ @infuscomus
Sadly that didn't work either:
A5
2
0x8D1BF828
1
0x8D1C4778

#3279 | infuscomus | ⇗ @coldwove my modded ISO already has the most recent patched ACPI 5048 driver so this means it's more complicated to fix. hopefully ⇗ @diderius6 might have some ideas for a fix for this.
#3280 | daniel_k | ⇗ @diderius6 Are you trying the ISO with which board? If it's Intel based, please try my modded iaStorA, this I'm sure it works. If it installs just fine on VM, then may be a driver related issue.

#3281

daniel_k

⇗ @Mov AX, 0xDEAD
Managed to add missing imports as ordinary functions (as if it was part of the driver code).
However, when an import is called many times, patching every single call is ugly and boring.
The call type is Near, absolute, indirect (FF).
What would you suggest?

#3282

diderius6

⇗ @infuscomus ⇗ @daniel_k
I try STORAHCI on the EVGA dark z390 board with XP unfriendly Bios 107.
The reason for this is, because I noticed, that only the STORAHCI driver works
on any board with AHCI. So, for a generic XP SP3 install CD only STORAHCI will work.
For a driver it is enough, when there is an entry for it in Services.
For critical drivers also in criticaldevicedatabase. This is on first view ok
for STORAHCI. So, really mysterium. Next I make try without any Acpi,
Dietmar

#3283

daniel_k

⇗ @diderius6
Just tried a clean install of XP SP3 using "my" files from storahci and ACPI.SYS 5048 (my BIOS is XP friendly, though).
No issues at all, no BSODs here, must be something on your end.
Definitively my package works, on VirtualBox and on real machine (Z370).
What about you flash the XP friendly BIOS and trying a ISO built with the files of my package?
Maybe something is related to the hacked ACPI.

#3284

daniel_k

⇗ @Mov AX, 0xDEAD
I'm porting storport.sys from Windows 7 to XP/2003.
Am I seeing something stupid here or am I the one who doesn't understand it properly?
StorPortExtendedFunction 11h

    .text:0001BF82                 mov     edi, edi
    .text:0001BF84                 push    ebp
    .text:0001BF85                 mov     ebp, esp
    .text:0001BF87                 cmp     [ebp+arg_4], 0
    .text:0001BF8B                 jnz     short loc_1BF94
    .text:0001BF8D                 mov     eax, 0C1000006h
    .text:0001BF92                 jmp     short loc_1BF9F
    .text:0001BF94
    .text:0001BF94 loc_1BF94:                              ; CODE XREF: sub
    .text:0001BF94                 push    [ebp+arg_4]
    .text:0001BF97                 call    ds:KeGetCurrentProcessorNumberEx
    .text:0001BF9D                 xor     eax, eax --> What ?!
    .text:0001BF9F
    .text:0001BF9F loc_1BF9F:                              ; CODE XREF: sub
    .text:0001BF9F                 pop     ebp
    .text:0001BFA0                 retn    8

Result from KeGetCurrentProcessorNumberEx is forced to zero?! So it is useless as EAX returned is always ZERO?
Now KeGetCurrentProcessorNumberEx from NTOSKRNL

    .text:0042F383                 mov     edi, edi
    .text:0042F385                 push    ebp
    .text:0042F386                 mov     ebp, esp
    .text:0042F388                 mov     ecx, [ebp+arg_0]
    .text:0042F38B                 mov     eax, large fs:20h
    .text:0042F391                 test    ecx, ecx
    .text:0042F393                 jz      short loc_42F3AC
    .text:0042F395                 mov     dx, [eax+3C6h]
    .text:0042F39C                 mov     [ecx], dx
    .text:0042F39F                 mov     dl, [eax+3C5h]
    .text:0042F3A5                 mov     [ecx+2], dl
    .text:0042F3A8                 mov     byte ptr [ecx+3], 0
    .text:0042F3AC
    .text:0042F3AC loc_42F3AC:                             ;
    .text:0042F3AC                 mov     eax, [eax+3CCh]
    .text:0042F3B2                 pop     ebp
    .text:0042F3B3                 retn    4

Is it really that simple?
I find this strange: mov eax, large fs:20h
Does it access a kernel variable location? Does it mean can only be run inside NTOSKRNL?

#3285

diderius6

⇗ @daniel_k
I just notice, that the same as to STORAHCI happens in registry to amdxhc,
but not to asmtxhci
Dietmar
EDIT: It is not related to acpi.sys. When I hit F5 (Standard PC) I get the same BSOD 7B on last reboot of XP install
and the same as above is true for amdxhc, but not to asmtxhci.
These devices are just not recogniced during XP Setup.
EDIT2: Also on the XP friendly Bios 092 happens exact the same. This means, this strange behavior
goes to STORAHCI in combination with storport. But with nvme boot together with storport this does not
happen, so it goes to STORAHCI.
This means, at the moment we dont have a generic AHCI driver, which works in any situation.
On a XP friendly Bios and on Intel board, all versions of Iastor work for XP Setup.

## Page 220

#3286 | infuscomus | ⇗ @diderius6 did you try my suggestion?
#3287 | infuscomus | ⇗ @daniel_k your modded USB 3.0 drivers from earlier, were any of them generic?

#3288

gordo999

@ infuscomus...tried your suggestion re changing W98 partition. I removed it completely and moved the XP partition 2 to partition 1. Edited boot.ini, added ntldr and ntdetect and it tried to boot. Got a bsod but it rebooted before I could read the bsod number.
Used my unofficial XP SP4 integrated disk based on my valid original XP install disk which was integrated with SP3. Tried a repair install and this time the installation carried on after the first reboot and got to the product key page.
I entered a valid product key and it claims the key is not valid!!! ARRRRRGGGGGHHH!!!! The key worked fine when I tried a repair install with the integrated XP SP3 disk.
I am encouraged that the USB keyboard is working during the install on an 8th gen mobo.

#3289 | infuscomus | ⇗ @gordo999 i'm guessing you either used a volume license key on a retail ISO or a retail key on a volume license ISO was your original XP install a retail or volume license?

#3290

gordo999

> Zitat von ⇗ infuscomus im Beitrag ¶ #3289

> was your original XP install a retail or volume license?

@infuscomus...it was actually an upgrade from W98, I presume it is retail since I purchased both. There is no OEM designation but the last three Pids digits in the setupp.ini file are 000 whereas retail is 335 and VL is 270. OEm is just OEM.
The product key did work on a repair install using the same XP disk slipstreamed with SP3.
I have discovered a possible solution, I used ntlite to slipstream the unofficial SP4 with my SP3 slipstreamed disk. Apparently some versions of ntlite can cause that problem if not used on an XP machine. I can always load XP on a VM and do the slipstream there.
I have d/l'd the most recent version of ntlite for XP SP3 and W7. I will try running the slipstream again, paying more attention to the unattend function and perhaps entering my product ID into the slipstream process.
Anyway, it's encouraging to see the repair install running so well complete with USB keyboard.
Thanks again for tip re W98 partition.

#3291

Mov AX, 0xDEAD

⇗ @daniel_k,
I finished modding halmacpi.dll v5687 to replace dma related procs from Win7 (xrefs also modded):

    HalpGrowMapBuffers
    HalpAllocateAdapterEx
    HalpAllocateAdapterCallback
    HalBuildMdlFromScatterGatherList
    HalBuildScatterGatherList
    HalCalculateScatterGatherListSize
    HalPutScatterGatherList
    HalGetAdapter

Results: nothing has changed, amdxhci stll not work with HIGH adresses, Creative X-Fi hangs with any dma

#3292

Mov AX, 0xDEAD

⇗ @daniel_k,

> Zitat von ⇗ daniel_k im Beitrag ¶ #3284

> Am I seeing something stupid here or am I the one who doesn't understand it properly?
> `.text:0001BF97 call ds:KeGetCurrentProcessorNumberEx
> .text:0001BF9D xor eax, eax` --> What ?!
> Result from KeGetCurrentProcessorNumberEx is forced to zero?! So it is useless as EAX returned is always ZERO?

this mean this proc has no return value, so it even may no touch eax

> Zitat von ⇗ daniel_k im Beitrag ¶ #3284

> Now KeGetCurrentProcessorNumberEx from NTOSKRNL
> `.text:0042F38B mov eax, large fs:20h`
> I find this strange: `mov eax, large fs:20h`
> Does it access a kernel variable location? Does it mean can only be run inside NTOSKRNL?

⇗ https://en.wikipedia.org/wiki/Win32_Thread_Information_Block
In ring0 i think fs point to other struct, but similar to TIB, data from begin of segment fs is thread stuff and can be used in any sys/dll/exe

#3293

gordo999

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3292

> In ring0 i think fs point to other struct, but similar to TIB, data from begin of segment fs is thread stuff and can be used in any sys/dll/exe

@ Mov AX, 0xDEAD
Curious as to how you are reaching ring0 code using windbg. I often traced through ring0 using softice. On one occasion, with a directx app written for full screen I had to trap a mouse message and trace it through ring0 to the DX code. I don't think that's possible with windbg, is it?
You can easily reach the beginning of directx code tracing from the OEP to where DX is initialized. However, the code running what you see on the screen of a DX app cannot be reached so easily from the OEP. That's why I came in the back door via trapped mouse messages.
I am a newbie on windbg and as yet have not seen a way to trace into ring0 code with it. Any time I reach the entry into ring0, windbg seems to do the work secretly and return a value. It does not seem to allow stepping into ring0 code. With softice I could step into it and trace through any ring0 code.
While tracing code into the NTFS mft structure (Microsoft calls everything a file) I did trace into HAL with softice but I cannot imagine how that could be done with windbg.
I have traced through k32, u32, etc., with windbg but that's not ring0.
Also curious about how you can mod hal without modding other kernel dlls and ntoskrnl. Are they not a set? With softice, every time a new kernel was produced, softice was issued a new set of patches with the new ordinals required for each kernel module to talk to each other.
Of course, the ordinals did not all change but if an ordinal changed in say ntoskrnl, certain calls between it and hal would crash the system.

#3294

gordo999

> Zitat von ⇗ daniel_k im Beitrag ¶ #3284

> @daniel_k

>     .text:0001BF8D                 mov     eax, 0C1000006h
>     .text:0001BF92                 jmp     short loc_1BF9F
>     .text:0001BF94
>     .text:0001BF94 loc_1BF94:                              ; CODE XREF: sub
>     .text:0001BF94                 push    [ebp+arg_4]
>     .text:0001BF97                 call    ds:KeGetCurrentProcessorNumberEx
>     .text:0001BF9D                 xor     eax, eax --> What ?!

> Result from KeGetCurrentProcessorNumberEx is forced to zero?! So it is useless as EAX returned is always ZERO?

I think the xor eax, eax is just initializing the eax register following the call. It may be done on purpose to negate the function return value, for whatever reason.
In a more sinister view, you might suspect that Microsoft does not want XP running in certain multi-processor environments.
Here's info on call...
⇗ https://docs.microsoft.com/en-us/windows...ocessornumberex
"The KeGetCurrentProcessorNumberEx routine gets the processor number of the logical processor that the caller is running on".
XP might not be expected to run on more than one processor hence they have cancelled any return value with an xor eax,eax.
Question arises as to what would happen if you NOPed that statement? Is there code following that could use the return value?

#3295

Mov AX, 0xDEAD

⇗ @gordo999
Hi,
- windbg has 2 mode - ring0 and ring3, in ring3 it can debug usual exe apps, ring0 mode is "Kernel Debugger", you can't switch between modes
- in ring3 you can not step to ring0 so you are right, it is impossible
- in ring0 windbg switch target kernel to special debug mode (kernel is "host", windbg is "client")
- ring0 can be used only with remote PC (vs softice), there exist also "local kernel debug", but it is useless
- they aren't set, newer hal.dll still compatible with older kernels. this is MS decision, MS do not change API between Hal and other parts
- for test debugging in ring0 i prefer using VMWare/QEMU because they have integrated GDB server + IDA as gdb client, windbg need for real hardware or when you need symbols on all loaded .SYS

#3296

Mov AX, 0xDEAD

> Zitat von ⇗ gordo999 im Beitrag ¶ #3294

>     .text:0001BF97                 call    ds:KeGetCurrentProcessorNumberEx
>     .text:0001BF9D                 xor     eax, eax --> What ?!

> I think the xor eax, eax is just initializing the eax register following the call. It may be done on purpose to negate the function return value, for whatever reason.

    int KeGetCurrentProcessorNumberEx(int *Ptr)
    {
         *Ptr=very_important_value;
        return 0;
    }

    - push [ebp+arg_4] - func fill result  to memory at *[ebp+arg_4]
    - call KeGetCurrentProcessorNumberEx
    - use eax for other purpose

#3297

gordo999

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3295

> - in ring0 windbg switch target kernel to special debug mode (kernel is "host", windbg is "client")
> - ring0 can be used only with remote PC (vs softice), there exist also "local kernel debug", but it is useless

⇗ @Mov AX, 0xDEAD
Thanks for information. I have wdbg setup via remote connection using serial ports. I use a laptop running w7 as host and I have used both W7 and W10 as clients on a desktop with an Asus B360M 8th gen mobo.
As I said, I am a newbie with wdbg and I have not yet managed to trace code right into ring0. The closest I came was hitting an Enter command using kernel mode. I mean the Enter command you reach when the system switches from ring3 to ring 0.
I hoped to trace right into the system but when I did a single step it kicked me right past the Enter command to the ret statement at the end of that code section.
I found it interesting in k-mode that I could freeze the desktop right at the beginning of the Windows boot stage and follow the loading process. It's pretty tedious, however, and I have not pursued that aspect of kernel debugging.

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3295

> - they aren't set, newer hal.dll still compatible with older kernels. this is MS decision, MS do not change API between Hal and other parts

That's good to know.

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3295

> - for test debugging in ring0 i prefer using VMWare/QEMU because they have integrated GDB server + IDA as gdb client, windbg need for real hardware or when you need symbols on all loaded .SYS

Interesting. So far, I have used only VMWare's free Workstation Player but it will run 32 bit XP and I can play with softice in the VM. Works pretty good for 32 bit apps.
I have tried to run a remote k-mode session using a VM but I prefer the serial connection. It was very hard to setup but I got it going using W10 and once the connection was established, it worked on W7 as well.

#3298

daniel_k

⇗ @Mov AX, 0xDEAD
It's a shame that patching those memory allocation related functions didn't help. Thanks for trying, though.
Do you have any suggestions for this?

> Zitat von ⇗ daniel_k im Beitrag ¶ #3281

> Managed to add missing imports as ordinary functions (as if it was part of the driver code).
> However, when an import is called many times, patching every single call is ugly and boring.
> The call type is Near, absolute, indirect (FF).

Managed to add storport functions 11h to 19h (except 17h), which are used by Openfabrics' NVME driver.
Jump table is correct, functions are called properly, relocations added for jump table and 3 new import calls.
Unfortunately it gives me the following BSOD:

    DRIVER_IRQL_NOT_LESS_OR_EQUAL

    0X000000D1 (0X00000001,0X0000000A,0X00000008,0x00000001)

Don't see anything wrong, can you please take a quick look at it? It's attached.

#3299

Mov AX, 0xDEAD

⇗ @daniel_k

> Zitat von ⇗ daniel_k im Beitrag ¶ #3298

> The call type is Near, absolute, indirect (FF).

- import is mess, i dont know how this import may work, in second record of ntoskrnl.exe pointer to INT TABLE is zero (0x00051028), IAT is normal
- offset to MmAllocateContiguousMemorySpecifyCache is not aligned to word (00051077)
- if need avoid "FF 15" create little stub and call it as IP-relative, add nop to fill 6 bytes

    my_memset:
        jmp ds:__imp__memset ;  need 1 reloc !
    endp
    .....
    call my_memset ; E8 xx xx xx xx 5 Bytes
    nop

- .newit probably need to be nonpageable, it contain IAT adresses
- this bsod is useless in static analyze, no any adresses

#3300

daniel_k

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3299

> - import is mess, i dont know how this import may work, in second record of ntoskrnl.exe pointer to INT TABLE is zero (0x00051028), IAT is normal
> - offset to MmAllocateContiguousMemorySpecifyCache is not aligned to word (00051077)
> - if need avoid "FF 15" create little stub and call it as IP-relative, add nop to fill 6 bytes
> ...
> - .newit probably need to be nonpageable, it contain IAT adresses
> - this bsod is useless in static analyze, no any adresses

Didn't think about imports. Thanks for checking it out.
Thought CFF Explorer was reliable, was wrong.
Added the imports with LordPE, seems correct now.
Still didn't work, so much work for nothing. Sad.

> Zitat

>     my_memset:
>         jmp ds:__imp__memset ;  need 1 reloc !
>     endp
>     .....
>     call my_memset ; E8 xx xx xx xx 5 Bytes
>     nop

Thanks, this is for iaStorA.sys.
About the AMDXHC USB3 driver, before I waste my time and effort...
I understand that DMA memory allocation is done by IoGetDmaAdapter, right?
Will try to implement the same allocation procedure in ASMedia and TI drivers.

Part 1 ◄ Part 2 ► Part 3 ► Part 4 ► Part 5