Dietmar

@RandyOC Most easy way is to install via Firadisk on USB stick to harddisk Dietmar PS: You have a message.

@RandyOC I have the MSI z690-A Pro DDR4 just without wifi. I succeed after loong testing to install XP SP3 to this board with 12900k cpu. Please tell me, which drivers you want and I make an xp.iso for you Dietmar

@Mov AX, 0xDEAD Do you have an idea, what I can test more with this new nvme.sys driver? May be, with the working XP SP3 install with this nvme.sys as scsi boot driver? Or what can be changed, tested in the NTOSKRNL Emu_Extender ? It is a nice driver, because it recognices ALL nvme devices and if it is work, it is stable. I also make an try with the last version of the acpi.sys 6666 from outerspace ). This gives exact the same Bsod 7F, (0x08,..) Dietmar EDIT: Can I enlarge the stack by hand in this nvme driver by hand in .text:00413979 sub esp, 0AA8h

@Andalu This means, that this new nvme.sys driver is not usable on normal XP SP3 install. IF you succeed to install it, it is stable. No crash then, all ok. All nvme devices are recogniced. The Silicon nvme driver you succeed to install, but then behaves unstable, brr.. The Toshiba nvme driver recognices only Toshiba nvme devices, there it is stable. So, until now only the Microsoft stornvme.sys works correct always under XP SP3 with any nvme device, the OFA 1.3 nvme driver (works with most nvme devices), is stable and sometimes the Samsung nvme driver (does not recognice a lot of non Samsung devices), is stable. Until now no trim under XP SP3 on nvme and no working CrystalDiskInfo. Today again I make a very strange discovery with the Samsung 970 Pro 1 TB nvme device: After about 17% zero out with WinHex, it hangs. When you trim it via win10, you can wipe out 50%, again crash. And the most most bad: from 3970 MB/sec speed goes down to 20 MB/sec, much less than any harddisk. When you connect the Samsung 970 Pro with an USB encloser, only about 50% files that you copy, are in real there. When I use the Optane 900P or 905P, such crazy bad things never happen and it is from feeling always faster than any other nvme Dietmar

@Mov AX, 0xDEAD When I compare nvme2.txt with nvme3.txt I see, that the crash belongs to the graphik driver together with the nvme.sys, very near to the end of the boot process Dietmar nvme2.txt MiSessionWideReserveImageAddress: NO Code Sharing on \SystemRoot\System32\drivers\dxg.sys, Address 0xbf000000 *** Fatal System Error: 0x0000007f (0x00000008,0xBA3D0D70,0x00000000,0x00000000) nvme3.txt MiSessionWideReserveImageAddress: NO Code Sharing on \SystemRoot\System32\nv4_disp.dll, Address 0xbd012000 8A21A080 8 (0x886fb008): ACPIDeviceIrpDeviceFilterRequest - Transition to D2 8A21A080 8 (0x8a0a7730): ACPIDevicePowerProcessPhase0DeviceSubPhase1 = 0x00000000 8A21A080 8 ACPIDeviceCompleteGenericPhase = 0x00000000 8A21A080 8 (0x8a0a7730): ACPIDevicePowerProcessPhase0DeviceSubPhase2

@Mov AX, 0xDEAD Here is the succesful acpiLOG of the new nvme driver Dietmar https://ufile.io/0fndmhi6

@Andalu I succeed to boot with this new nvme.sys driver on the Samsung 970 Pro, and graphikcard gt730 Nvidia and all the devices under IRQ16. For this I setup my original XP SP3 *.iso, modd it via Ramsey, but edit all by hand. I use my new acpi.sys with OS fakes. The setup took place via Firadisk and the Kai driver for HD on my Asrock extreme z690 board with 12900k cpu. Then, I install really everything on this HD. And at the end also the new nvme.sys driver by hand. This XP SP3 on HD I "show" to the 970 Pro, means I connect the 970 Pro. In registry I set Start = 4 for the stornvme.sys. Then I copy via AOMEI 7.0 this whole HD to the 970 Pro. Voila, boots very fast via the new nvme.sys, no Bsod Dietmar

@Andalu It looks, as if XP uses only the model for IRQ 0...17 (not enlarged). And with this, about 10 devices have IRQ 16. This does not like this new nvme.sys driver. I catch the moment of fail: 9 devices have already IRQ16. With the graphikcard NVIDIA install, this next device wants IRQ16 also. This is too much, gives Bsod 7F on next reboot. But the compi starts in Safe Mode, without graphikcard on IRQ16. @Mov AX, 0xDEAD Do you have an idea, how to enable the enlarged IRQ (0...255?) under XP SP3 Dietmar

@Andalu I change on the Ramsey XP the whole HIVE system against my working one. On Safe Mode, the Ramsey XP boots for few seconds to full desktop, without any error message, then reboots. On normal boot, I get the Bsod 7F again. This is really crazy Dietmar EDIT: That the Ramsey XP boots in Safe Mode is an indicator for an driver conflict of the nvme.sys driver.

@Andalu I make the same with original Ramsey xp.iso settings in Integrator v3.4.1.11 Options Menu (rxrepl).cmd Customized Option; 2,5 (my laast free acpi.sys and your nvme.sys only) with your nvme.sys ==> stornvme.sys clothes. This gives again Bsod F7 Dietmar PS: Now I check in windows\system32\config the entries in HIVE system against may working ones.

@Andalu I use for my original XP SP3 xp.iso only my laast free acpi.sys and your nvme driver in clothes for stornvme in Ramsey Integrator. This works. Ultrafast install of this XP in 6 min, boottime to full Desktop with the Samsung 970 Pro is 9 sec. So, may be there is really an IRQ conflict on Setup, which XP cant solve Dietmar

@Andalu I noticed, that there are errors in your script Options Menu (rxrepl) (MOD x NVMe).cmd . So I make a try with the script from Ramsey and just rename your driver nvme.sys ==> stornvme.sys and copy it in the patch folder for the Microsoft stornvme driver. This overcomes any error in the *.inf definition, because windbg tells me, that acpi cant decide, if it is APIC mode or ACPI mode for the IRQs. I remember that a problem happens with registry entries for MSI. Ok, so with faked stornvme.sys install of Ramsey XP starts. But exact on laast reboot comes the same error Bsod 7F. I think, that it has to do with a problem for to find the correct IRQ for this nvme driver Dietmar PS: Now I start the same fake methode with my german XP SP3 xp.iso, but modded with ramsey.

@Mov AX, 0xDEAD I found this place of Bsod in the nvme driver Dietmar PS: @Andalu can send to you the "Source" Code in Assembler. .text:00413976 ; =============== S U B R O U T I N E ======================================= .text:00413976 .text:00413976 ; Attributes: bp-based frame .text:00413976 .text:00413976 sub_413976 proc near ; CODE XREF: sub_401000+57p .text:00413976 ; sub_40173C+38p ... .text:00413976 .text:00413976 var_AA8 = byte ptr -0AA8h .text:00413976 arg_0 = dword ptr 8 .text:00413976 arg_4 = dword ptr 0Ch .text:00413976 arg_8 = dword ptr 10h .text:00413976 .text:00413976 push ebp .text:00413977 mov ebp, esp .text:00413979 sub esp, 0AA8h .text:0041397F lea eax, [ebp+var_AA8] .text:00413985 push esi .text:00413986 push edi .text:00413987 push 0AA8h .text:0041398C push 0 .text:0041398E push eax .text:0041398F call sub_4145B0 .text:00413994 mov edx, [ebp+arg_0] .text:00413997 lea esi, [ebp+var_AA8] .text:0041399D mov eax, [ebp+arg_4] .text:004139A0 add esp, 0Ch .text:004139A3 mov ecx, 2AAh .text:004139A8 mov edi, edx .text:004139AA rep movsd .text:004139AC mov [edx], eax .text:004139AE mov eax, [ebp+arg_8] .text:004139B1 pop edi .text:004139B2 mov [edx+4], eax .text:004139B5 mov dword ptr [edx+0Ch], 1 .text:004139BC pop esi .text:004139BD leave .text:004139BE retn 0Ch .text:004139BE sub_413976 endp .text:004139BE .text:004139BE ; --------------------------------------------------------------------------- .text:004139C1 align 10h .text:004139D0

@Mov AX, 0xDEAD Here is the output from acpi LOG. May be, that there cant be enabled an IRQ for the nvme device. For wish from @Andalu, I changed the original driver name to nvme everywhere Dietmar https://ufile.io/kwwj7fx8

@Mov AX, 0xDEAD @Andalu I succeed to see the endless running bar, when I change at driverentry of nvme.sys the first 2 bytes against EB FE. But I cant Pause windbg. With hitting "pause", nothing happens, endless bar continues. But when I hit break, I come back to the point, from where I started. @Mov AX, 0xDEAD any idea, how I can stop the endless running bar, but do not loose the EIP for the driverentry of nvme.sys Dietmar

@Andalu The Bsod seems to be: ACPI_FAILED_PIC_METHOD Dietmar

@Andalu I change the HIVE system from the working XP to the XP with Bsod 7F. On reboot I get the same Bsod 7F. But in "Safe Mode" I get this strange message, have never seen before, and then reboot Dietmar

@Andalu No Bsod on the Asrock Extreme z690 board with 12900k cpu. I test also Intel Optane 905P, Intel 750 Series and Samsung 950Pro. All work. Nice driver. Now I make a try with install of XP of pur Ramsey XP to the 970 Pro on the Asrock Extreme z690 Dietmar PS: First I change in Ramsey XP the acpi.sys to my very laast version with SHA-1 80EE71969EC13FBBC091A17C4A1C8534D3FECA0C EDIT: Ultrafast install of XP, less than 7min. But on last reboot I get the same Bsod 7F as you

@Andalu On the Asrock z370 k6 board, this nvme.sys driver works for me. No Bsod. I test Optane 900p, Samsung 960Pro, Samsung 970 Pro, Toshiba RD400. I use my original XP SP3 german CD with ntoskrn8.sys from Ramsey and all the storport.sys from Ramsey. My Nvidia driver is 344.11-desktop-winxp-32bit-international.exe , from which I think, that it is the best Dietmar PS: Now I try the Asrock z690 Extreme board.

@Andalu So, now we know for sure, that it is the nvme.sys driver. You can edit the driver entry for nvme with the trick from @Mov AX, 0xDEAD. With IDA Pro change in driverentry of nvme.sys the first bytes against EB FE which gives an endless loop. Hit "break" in windbg. You are at the driverentry, see the EB FE. Then you can change (in the to memory loaded nvme.sys driver) those 2 bytes back to its original ones. At the driver entry of nvme.sys hit again and again "t" until the Bsod. Then, you will get the reason for Kernel Trap (example division by zero) Dietmar PS: Send me this whole nvme driver. I will test also on my compis.

@Andalu Just hit "g". And then again "i" and again "i".. until Bsod Dietmar PS: Delete the breakpoint for nvme in windbg.

@Andalu This is the normal break of windbg, for to have a fixed start point. Now you only need to hit "g" in commandline. Later, may be you have to hit "i" again and again, this means nothing. Then you should come to desktop. After this, install without windbg (just use 1. setting in boot,ini) the Nvidia driver. And then use windbg again. Windbg should show to you, which device makes the 7F Bsod Dietmar EDIT: I think, that the command ed Kd_ACPI_Mask 0x7FFFFFFF works only with the debug version of acpi.sys. At the moment, use the normal free acpi.sys because I think, that the error is not acpi related. And that there is no aquivalent for nvme.

@Andalu Use the original ISO XP and set up there ntos3.exe and hal3.dll for a debug session. Check, if windbg runs without problem. Then install the graphikdriver and run windbg for to fetch the 7F Bsod Dietmar

@Andalu Make sure, that you use the latest acpi.sys Dietmar acpi.sys free and debug laast V7 with OSfake https://ufile.io/trphcl2x

@Andalu I have this crazy Bsod with 7F also sometimes after installing the nvidia graphikcard. May be, that there is an ressources conflict. For to check this, set up a minimal XP SP3, only with the drivers which you want to test. Disable everything other in Bios and in Device Manager. And then hit just "g" after breakpoint for to see, which driver gives this Bsod Dietmar