Dietmar

@Damnation I just set up a fresh XP SP3 (june 2022 version) from @Outbreaker on the Asrock z370 k6 board with Customized Option; 4,5,C,E,H for to avoid any conflict with your new ntoskrn8.sys . Until now, no Lan driver is installed. First I make a copy of this fresh installed XP so that I can go back later very easy to a definite start situation Dietmar EDIT: I get an endless running bar for the i219-V . Please tell me, which other files I have to install together with your new ntoskrn8.sys .

Because I want to understand, what is going on with the Biostar z690A board, I make a XP SP3 german real setup DVD with all SP3 updates until April 2014 and all Posready until May 2019 via Nlite 1.4.9.3 . Into this I integrate by hand the Intel 1006 driver but only with the entry for iaAHCI_600_6 = "Intel(R) SATA AHCI Controller DEV_7AE2 added by Dietmar" because I noticed, that the Setup routine always takes a wrong variant of this Intel driver during TXT setup, which gives Bsod. With UltraIso I put my laast acpi.sys V5 into the *.iso. The size of this *.iso is 836.354.048 Bytes. This is the minimal size of an original XP SP3 with all updates. And voila, XP installs via this modded Intel 1006 driver direct on the Biostar z690A board, very fast because it is via DVD Dietmar

@Dave-H The only way of debugging the Flex 10 is via its internal PCIe mini port. This works only with the use of an EEpromer, because you have to kill the Whitelist from Lenovo in its Bios chip Dietmar

@Mov AX, 0xDEAD I succeed with the direct Sata install of XP SP3 and the acpi.sys V5 on the Biostar z690A board. But this install works only with install of XP from a real CD. The Intel 1006 driver seems to come in conflict with the video output (some strange symbols appear on screen during install of XP) and then Bsod. The only generic Sata driver until now is the driver from Kai Schtrom Dietmar PS: No other version of Windows bit32 can be installed on the Biostar z690A board, only XP SP3.

@Mov AX, 0xDEAD Hm, with the debug acpi.sys V5 Windbg tells no A5 error but this. Bsod happens, before the DriverEntry point of acpi.sys is reached via bu acpi!DriverEntry https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/ntddk/nf-ntddk-ioraiseinformationalharderror Dietmar *** Fatal System Error: 0x0000000a (0x00000008,0x00000002,0x00000000,0x8086061F) 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 Jun 4 16:16:53.343 2022 (UTC + 2:00)), ptr64 FALSE Loading Kernel Symbols ............................................................... .............................. Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {8, 2, 0, 8086061f} Probably caused by : ntkrnlmp.exe ( nt!IoRaiseInformationalHardError+1b4 ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 808109c2 cc int 3 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: 00000008, 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: 8086061f, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: 00000008 CURRENT_IRQL: 2 FAULTING_IP: nt!IoRaiseInformationalHardError+1b4 8086061f 3b5008 cmp edx,dword ptr [eax+8] DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xA ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre TRAP_FRAME: 80884f48 -- (.trap 0xffffffff80884f48) ErrCode = 00000000 eax=00000000 ebx=81a659e8 ecx=8088ee10 edx=c000012d esi=00000000 edi=8088ee18 eip=8086061f esp=80884fbc ebp=80884fc8 iopl=0 nv up ei pl nz na pe cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010207 nt!IoRaiseInformationalHardError+0x1b4: 8086061f 3b5008 cmp edx,dword ptr [eax+8] ds:0023:00000008=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 8086457f to 808109c2 STACK_TEXT: 80884afc 8086457f 00000003 80884e58 00000000 nt!RtlpBreakWithStatusInstruction 80884b48 80865056 00000003 00000008 8086061f nt!KiBugCheckDebugBreak+0x19 80884f28 8080ea16 0000000a 00000008 00000002 nt!KeBugCheck2+0x574 80884f28 8086061f 0000000a 00000008 00000002 nt!KiTrap0E+0x180 80884fc8 8086cdbd 0100012d 00000000 00000000 nt!IoRaiseInformationalHardError+0x1b4 80884fd8 80856aab 8088ff20 00000000 81a31d68 nt!MiCauseOverCommitPopup+0x5e 80885020 8082d7ad 00000000 81a31e30 809004c5 nt!MiChargeCommitment+0x108 80885044 80900538 00000000 81a31d68 80885158 nt!MmCreateProcessAddressSpace+0x1c 80885058 809004e5 81a31d68 80885158 808851f0 nt!MmInitializeHandBuiltProcess+0x49 808851a0 809f43d0 809c92cc 001f0fff 80885224 nt!PspCreateProcess+0x29a 8088524c 809f4085 80081000 808853e8 809ea96d nt!PspInitPhase0+0x34e 80885258 809ea96d 00000000 80081000 8088fcc0 nt!PsInitSystem+0x33 808853e8 809f110d 00000000 80081000 8003fc00 nt!ExpInitializeExecutive+0x783 8088543c 809f0d97 8088ff20 8088fcc0 80885700 nt!KiInitializeKernel+0x4f6 00000000 00000000 00000000 00000000 00000000 nt!KiSystemStartup+0x2c4 STACK_COMMAND: kb FOLLOWUP_IP: nt!IoRaiseInformationalHardError+1b4 8086061f 3b5008 cmp edx,dword ptr [eax+8] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: nt!IoRaiseInformationalHardError+1b4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 5c34e27b IMAGE_VERSION: 5.1.2600.7649 FAILURE_BUCKET_ID: 0xA_nt!IoRaiseInformationalHardError+1b4 BUCKET_ID: 0xA_nt!IoRaiseInformationalHardError+1b4 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0xa_nt!ioraiseinformationalharderror+1b4 FAILURE_ID_HASH: {929afa2d-924a-a4ee-b8ae-b3ca03308a8c} Followup: MachineOwner ---------

@Mov AX, 0xDEAD Yessssaaa I get Windbg on XP TXT Setup to work. The crazy Biostar board always enables the internal Lan device. After I check check check in Bios, that the internal Lan device is DISABLED, I get connection Dietmar

@Mov AX, 0xDEAD I prepare all for Windbg of TXT Setup of XP. But now comes this message: I edit TXTSETUP.SIF with the following lines but no connection via Lan Debug [SetupData] OsLoadOptions = "/DEBUG /DEBUGPORT=NET /HOST_IP=192.168.2.101 /HOST_PORT=50000 /ENCRYPTION_KEY=1.2.3.4 /CPUFREQ=3000 /TARGET_IP=192.168.2.103 /BREAK" [SourceDisksFiles] kdcom.dll = 1,,,,,,3_,2,0,0,,1,2 kdnet.dll = 1,,,,,,3_,2,0,0,,1,2 kdstub.dll = 1,,,,,,3_,2,0,0,,1,2 Because I have no idea what the numbers behind those files mean, I just copy the entries from kdcom.dll . Now, XP TXT at "Windows Setup" stops, I think because of "BREAK" but no connection via Lan Debug Dietmar

@Mov AX, 0xDEAD Here is the DSDT.dsl and DSDT.raw from the Biostar z690A board Dietmar https://ufile.io/u40d1f36

@Mov AX, 0xDEAD On the Biostar z690A VALKYRIE I get the famous A5 Bsod with the new acpi.sys V5, when I install XP SP3 via the Intel Sata 1006 driver. But the most crazy thing is, when I use my already installed generic XP SP3, no Bsod with Intel 1006 driver and acpi.sys V5 at all. With the generic XP I can boot the same XP SP3 via the Intel 1006 Sata driver together with acpi.sys V5. So, this Bsod will be really hard to debug because it is only shown during TXT Setup of XP. With the acpi.sys 6666 from outerspace ) I get message: Out of memory, Setup cant be continued Dietmar EDIT: Because of this "Out of memory" message I replace the DDR4 ram with a single 4GB stick. Same A5 Bsod, also on the second Asmedia Sata Slot for ALL Sata drivers, that I have. With generic XP SP3 I can change the Sata drivers and through all slots. No Bsod with acpi.sys V5. I can install XP SP3 only direct to nvme device on the Biostar z690A VALKYRIE board.

@Andalu I think, that this USB3 crash happens not randomally on Intel USB3. It depends on, which files where copied first, second etc. . The crash happens, when a lot of files with a size of about 2 Gb are copied one after the other Dietmar

@Damnation Until now, there is no USB3 driver for XP, build from win8.1. But this will be a nice task, also together with ndis6 Dietmar

I thought, that may be the crash on Intel USB3.0 is because to which device the files are copied. But the same crash happens, when I copy whole content of 200 GB from Sandisk USB3.2 to the Optane 905P drive, from which I know, that read and write speed does not matter at all, how big and how much splitted the files are. This test I do on the Asrock z370 k6 again. Now, copy is much faster, only 17 min until crash ;)) Dietmar EDIT: No crash on Asmedia USB3. Whole content of 200Gb is copied from Sandisk to Optane in 20min. EDIT3: Correction: On the Asmedia USB3 only with the own Asmedia USB3 driver no crash happens. With the from Win8 modded driver, it crashs also on Asmedia very fast after 3 min. This makes the situation a little bit more difficult. So it seems, that only the VIA USB3 on XP SP3 works perfect with the from Win8 modded USB3 driver. So it makes sense, to make a try with an USB3 driver for XP SP3 from Win8.1 build. EDIT2: I also test the for XP modded USB3 AMD 145 driver on Intel USB3. Same crash with this driver after 3min on Intel USB3.

Now I make a test with the same Sandisk 256Gb ultrafast USB3.2 stick, the same board Asrock z370 k6 with Win8.1 (all Updates). On the Intel USB3 the situation is not better. Even copy starts faster, after 30 min the speed goes down to zero for about 60sec few times, see photo. No crash. Time for copy is 43min, means compi with FX58m from 2009 is faster. Second run without disconnecting the stick was 40min, may be because of deleted files.. And the most crazy: Win8.1 refuses some files to copy, tell some are malware and delete(!) some on the Sandisk USB3 stick without asking, brrr.. At once I understand, why I like XP Dietmar PS: Asmedia USB3 with same original Win8.1 USB3 driver needs 38min for to copy whole Sanddisk stick.

@Damnation I just download NTLite. May be for win7 it is a nice tool, but it does not work under XP SP3 Dietmar

The Asmedia USB3 chip on the Asrock z370 k6 did not crash. It has the same original win8 driver as before. In 34min the whole 200Gbyte from the Sandisk ultrafast USB3.2 stick are copied. And I also make the same test, without disconnecting the stick, once more I copied ALL, same speed, no crash on Asmedia USB3 Dietmar

Now I just copy the whole content under win8 from the 200Gbyte Sandisk USB stick to the harddisk. There is only the original win8 USB3 driver. Crazy, it starts fast with about 200MByte/s but now it is sometimes slow as much as possible, speed goes down to 5(!!!)kb/s, less than from Floppy disk Dietmar PS: Whole time for to copy is more than 1 hour on Intel USB3 until now. In 40min on the VIA PCIe USB3 slotcard on XP SP3 all(!) was copied. Yesssa, at the end speed goes down as much as possible but does not crash. Then, I copy the same content of the USB stick (without disconnect(!)) to a new folder, and, voila crash, see photo. This simple means, that the Intel USB3 is not so very good

I succeed to change the acpi.sys on the win8 installations DVD. But setup on the Asrock z690 Extreme board still hangs also with the new acpi.sys, modded against DDB Bsod, at the menu, where I get choose the language Dietmar PS: @Damnation Do you remember, which acpi.sys win8 works for you for win8 bit32, modded for DDB BSOD? I make acpi1.sys, acpi2.sys, acpi3.sys and acpi4.sys for win8. Just now I try with acpi4.sys. EDIT: With the for DDB Bsod modded acpi.sys I can install win8 on the Asrock z370 k6 board. So, may be it is not an acpi Bsod, also possible, that the Sata driver from win8 does not work on the Asrock z690 Extreme board.

@Damnation Nlite gives to me often error because of disrupted DVD structure. After a lot of searching I found the nice tool gimagex. This works also under XP SP3. Waaoh, now I can edit any *.wim files simple with copy and paste under XP. And I set up a new version of Ultraiso. Now I have new win8.iso with my for DDB error hacked acpi.sys and soon I test it Dietmar

Hi, can somebody here write a short Tutorial, how to change a single file acpi.sys in install.wim from win8 bit32? And can I use ImgBurn to make a new win8.iso from all those files extracted from the original win8.iso? Best Tutorial would be for XP SP3, but I also can use Win7 SP1 or Win8.1 Dietmar

@daniel_k I cant install win8 bit32 on the Asrock z690 Extreme. When the message about to choose language appears, compi hangs Dietmar PS: May be, this happens because of DDB error in the acpi.sys of win8. But when I try to edit the win8.iso with UltraIso, I see only a *.txt file. With Virtual Clone I can see all the files on the win8 DVD, so I can extract them and change acpi.sys against the DDB error modded one, but how to put this install.wim with modded acpi.sys back into the win8.iso?

@Damnation We want to make things better. For me it is also a hard job, to look deeper at this error, because it only happens after transfer of such a lot of files through USB3. Yesterday in the evening I was soso much astonished, that with the same USB3 driver ported from Win8, the same XP SP3 installation but now USB3 via VIA Pcie slotcard this long standing error on Intel USB3 not happens Dietmar

Hi, I make an interesting discovery: On all boards z370, z390, z690 that I tested under XP SP3 with ram patch all with 32 Gbyte ram and the Win8 USB3 driver, after about 40 Gbyte of millions of files, photos, movies, docs, pdf etc. comes a message, that not enough system resources. When I disconnect the 200 Gbyte Sandisk ultrafast USB3.2 stick, the same happens after the next 40 Gbyte. But today I copy this 200 Gbyte stick on an Acer Aspire m7720 with FX58m board from 2009 (!) with 6Gbyte DDR3 Ram and i920 cpu and an 4 port USB3 card in Pcie slot. And voila: The whole stick on this old compi is copied in half of the time compared with an z690 board and no message about not enough system resources appears Dietmar EDIT: This 4 port PCIe card is from Via with VEN_1106&DEV_3483 but not with its original VIA driver. The USB3 driver is the nice one from @Mov AX, 0xDEAD ported from Win8. So it seems to be a problem of all(?) Intel USB3. EDIT2: This 40GB problem under XP SP3 happens on all Intel USB ports, USB3.0, USB3.1, USB3.2. USB2 I do not test because for this I need days. And it happens after the same 40Gb from USB stick also without the nice memory patch from @daniel_k. EDIT3: On the Asrock z690 Extreme, on all USB3 ports, the Sandisk USB stick shows more than 240 Mbyte/s with Crystal diskmark. On the VIA USB Pcie card the same stick shows 140 Mb/s. But in real, the copy on the Via USB3.0 card is about a factor 2 faster for millions of files. For all those tests I use the same USB3 driver modded from Win8 from the last Integrator package Optional Patch Integrator v3.3.0b3 from @Outbreaker. But it seems not to be a problem of this USB3 driver, because on VIA USB3 Pcie 4 slot card VEN_1106&DEV_3483 this driver works perfect. Other versions of this driver show exact the same 40Gb problem on all(?) Intel USB3. EDIT4: It depends not on the USB stick. A Kingston Workspace with 64Gb shows the same error after copy of about 40 Gbyte. And the same happens vice versa, when I copy more than about 40 Gbyte from harddisk to this USB stick. All is formatted with NTFS and has all patches for XP SP3 until May 2014 and also all Posready updates.

@steregushchyy Make a try, which drivers work best for you with the XP SP3 from Ramsey, there you can choose drivers http://www.zone94.com/downloads/software/operating-systems/123-windows-xp-professional-sp3-x86-integral-edition Dietmar

@steregushchyy Just copy new acpi.sys instead of acpi.sy_ into folder i386 (delete acpi.sy_ there). No need to compress. And you need to extract with 7Zip the folder sp3.cab in i386 and change there acpi.sys against new one and compress it again with cabpck14, place it after this with same name sp3.cab into i386 folder Dietmar

@steregushchyy Until now, on each board you can install XP SP3 as long as its Bios offers CSM. On newer boards you may find only Lan i219, where until now no driver for XP exists. I have 2 boards, where XP SP3 runs very nice: First is Asrock Fatal1ty Z370 Gaming K6 (stable, fast, 3 full armed PCIe slots, overclock, all drivers for XP) Second is Asrock z690 Extreme, for this you need an external Lan card for XP Dietmar