Dietmar

@Mov AX, 0xDEAD @RandyOC Yesssa, without any hack via my new acpi.sys with OS fake and the Kai Storahci SATA I am just installing XP64 on the MSI z690-A Pro DDR4 board, via CD on Sata CD rom. Firadisk does not work for 64bit here Dietmar

@Mov AX, 0xDEAD On the Asrock z370 k6 XP64 installs without problems and without any hack via my new build acpi.sys with OS fake Dietmar

@Mov AX, 0xDEAD @RandyOC Dirty hack against Bsod A5 (0x03,..) at a lot of places does not work. Gives new Bsod 0xA. I also tried the last version from @George King from 4. Dezember 2022, also with dirty hack against Bsod A5 (0x03,..) , gives the same Bsod 0xA Dietmar

@Mov AX, 0xDEAD On this board, Debug is not possible because no Lan Debug for 64 bit and no serial Debug works there. I make a try on the Asrock z370, because there Serial Debug works, endless time^^ needed Dietmar

@Mov AX, 0xDEAD @RandyOC The fresh build bit 64 acpi.sys gives Bsod A5 (0x03,..) on the MSI z690-A Pro DDR4 board. I try dirty hack but there is a problem Dietmar

@Mov AX, 0xDEAD There must be an nvme.pdb for this driver, until now I dont have. Is there any chance, that we can edit this nvme.sys by hand via assembler Dietmar

@UsefulAGKHelper Yepp, the idea is from @daniel_k. I never tested it for XP64 but now I make a try Dietmar

I just compile fresh the acpi.sys for XP bit64 with FakeOS (free and debug version) thanks to @daniel_k . This was the biggest hurdle for me for to make a general xp.iso bit64 Dietmar https://ufile.io/lsyr6dtw

I just get confirmation from @RandyOC that XP SP3 works to full on the 13900k cpu Dietmar

@Mov AX, 0xDEAD Here is the wished. I fake the new nvme.sys driver with stornvme.sys name Dietmar 20: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 00000008, EXCEPTION_DOUBLE_FAULT Arg2: ba3e0d70 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 TSS: 00000028 -- (.tss 0x28) eax=ba234fc4 ebx=8952c004 ecx=86f4257c edx=00000000 esi=86f4257c edi=00000000 eip=b9ee8985 esp=ba234fc4 ebp=ba235a6c iopl=0 nv up ei ng nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282 stornvme+0x13985: b9ee8985 56 push esi Resetting default scope DEFAULT_BUCKET_ID: DRIVER_FAULT PROCESS_NAME: csrss.exe ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre TRAP_FRAME: ba236334 -- (.trap 0xffffffffba236334) ErrCode = 00000000 eax=0000000f ebx=00000000 ecx=c4b03400 edx=00000000 esi=ba236424 edi=86f3e668 eip=80b198af esp=ba2363a8 ebp=ba2363f4 iopl=0 nv up ei ng nz ac po cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293 nt!CcMapData+0x137: 80b198af 8a0c0a mov cl,byte ptr [edx+ecx] ds:0023:c4b03400=bc Resetting default scope LAST_CONTROL_TRANSFER: from b9ee85e5 to b9ee8985 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. ba235a6c b9ee85e5 870d9298 8952c004 86f4257c stornvme+0x13985 ba235a94 b9e6b672 8952c004 86f4257c ba235ad0 stornvme+0x135e5 ba235aa4 b9e6d1e6 894e0190 86f4257c 870d9010 storport!DllInitialize+0x2e1 ba235ad0 b9e6d46a 894e00f0 897e8bb0 00000000 storport!DllInitialize+0x1e55 ba235ae8 801055de 894e0038 00000000 870d9064 storport!DllInitialize+0x20d9 ba235b10 b9e710b6 00000000 894e0038 870d9064 HAL3!HalBuildScatterGatherList+0x202 ba235b40 b9e6d506 894e02a0 894e0038 868946b0 storport!DllInitialize+0x5d25 ba235b80 b9e6d556 894e02a0 00001000 ba235bb0 storport!DllInitialize+0x2175 ba235b90 b9e7b3d8 894e00f0 870d9010 86f42338 storport!DllInitialize+0x21c5 ba235bb0 b9e72692 00000000 86f42338 ba235bd0 storport!StorPortExtendedFunction+0x5fcd ba235bf0 b9e78d93 007e8b28 86f42338 00000000 storport!DllInitialize+0x7301 ba235c10 b9e7bb29 897e8b28 86f42338 86f42338 storport!StorPortExtendedFunction+0x3988 ba235c30 b9e717ec 897e8b28 00000000 897e8a70 storport!StorPortExtendedFunction+0x671e ba235c4c 80a21c8d 897e8a70 86f42338 86f423cc storport!DllInitialize+0x645b ba235c64 ba0f8fdd 00000000 86894e70 86f424d0 nt!IopfCallDriver+0x51 ba235c78 ba0f8cdc 86f424d0 87084b70 86894f70 CLASSPNP!SubmitTransferPacket+0x82 ba235ca8 ba0f8dcd 00001000 00001000 87084ab8 CLASSPNP!ServiceTransferRequest+0xe4 ba235ccc 80a21c8d 87084ab8 00000000 87084878 CLASSPNP!ClassReadWrite+0xff ba235ce4 ba0c903f 00000000 8958e4f8 ba235d28 nt!IopfCallDriver+0x51 ba235cf4 80a21c8d 87084878 86894e70 86894e70 PartMgr!PmReadWrite+0x9a ba235d0c b9f1d1c6 894a6e30 86894e70 00000000 nt!IopfCallDriver+0x51 ba235d28 80a21c8d 894a6e30 86894e70 86fc6100 ftdisk+0x11c6 ba235d40 b9cd01c3 ba236024 86894e70 ba235f30 nt!IopfCallDriver+0x51 ba235d50 b9ccfd26 ba236024 894a6e30 c0083000 Ntfs!NtfsSingleAsync+0x6d ba235f30 b9cd26f6 ba236024 86894e70 87141e68 Ntfs!NtfsNonCachedIo+0x2f8 ba236010 b9cd200a ba236024 86894e70 00000001 Ntfs!NtfsCommonRead+0xbdd ba2361c0 80a21c8d 86fc6020 86894e70 87147dd0 Ntfs!NtfsFsdRead+0x22d ba2361f8 80a22cab 00000000 86894688 86894678 nt!IopfCallDriver+0x51 ba23620c 80a22cd3 87147dd0 86894607 86894690 nt!IopPageReadInternal+0xf3 ba23622c 80a7eecb 89532e28 868946b0 86894690 nt!IoPageRead+0x1b ba2362b0 80aa5374 c0033333 c4b03400 c0625818 nt!MiDispatchFault+0x691 ba23631c 80ae20a8 00000000 c4b03400 00000000 nt!MmAccessFault+0xdde ba23631c 80b198af 00000000 c4b03400 00000000 nt!KiTrap0E+0xdc ba2363f4 b9cf5a50 89532e28 ba236424 00000400 nt!CcMapData+0x137 ba236414 b9cf5c6b 86f00340 87141e68 00083400 Ntfs!NtfsMapStream+0x46 ba236488 b9cf5b78 86f00340 86fc6100 e13de458 Ntfs!NtfsReadMftRecord+0x86 ba2364c0 b9cf5acf 86f00340 86fc6100 e13de458 Ntfs!NtfsReadFileRecord+0x7a ba2364f8 b9d06945 86f00340 e13de450 e13de458 Ntfs!NtfsLookupInFileRecord+0x37 ba2365a8 b9d06564 86f00340 00000001 e13de450 Ntfs!NtfsUpdateFcbInfoFromDisk+0x3e ba236680 b9d068fd 86f00340 86dbea60 86dbeba8 Ntfs!NtfsOpenFile+0x2e6 ba2368d8 b9cf4f0d 86f00340 86dbea60 ba236930 Ntfs!NtfsCommonCreate+0x134a ba2369bc 80a21c8d 86fc6020 86dbea60 87147dd0 Ntfs!NtfsFsdCreate+0x1dc ba236a38 80b42450 894a6e18 80102524 86f47900 nt!IopfCallDriver+0x51 ba236b20 80bbe888 894a6e30 00000000 86f478d0 nt!IopParseDevice+0xb6a ba236b98 80bb8c28 00000000 ba236bd8 00000240 nt!ObpLookupObjectName+0x590 ba236bec 80b2f75d 00000000 00000000 00000000 nt!ObOpenObjectByName+0x140 ba236c68 80b302ca ba236da8 001200a9 ba236d60 nt!IopCreateFile+0x43b ba236cc8 bf87fe8d ba236da8 001200a9 ba236d60 nt!IoCreateFile+0xd4 ba236fcc bf83279b ba2370d0 ba236ff4 00000000 win32k!bCreateSection+0xfc ba237028 bf88f277 e13716b8 e11fcca0 e11fcca4 win32k!EngMapFontFileFDInternal+0xd1 ba237084 bf8aa771 ba2370d0 00000022 00000001 win32k!PUBLIC_PFTOBJ::bLoadFonts+0x18f ba2372e0 bf95a301 ba237338 ba237308 0000000a win32k!PUBLIC_PFTOBJ::bLoadAFont+0x77 ba23778c bf95a497 00000000 ffffffff 00000000 win32k!bAppendSysDirectory+0x3f2 ba2377a8 80c00791 e1371770 00000001 e1371734 win32k!BuildAndLoadLinkedFontRoutine+0x68 ba2377f4 80c00bc5 bf9b67f0 e1371734 ba237854 nt!RtlpCallQueryRegistryRoutine+0x235 ba237858 bf8a9d20 00000000 000000a6 00000001 nt!RtlQueryRegistryValues+0x1c3 ba237874 bf89515a bf9a4060 00000000 00000003 win32k!BuildAndLoadLinkedFontRoutine+0xd0 ba237cc0 bf8aa560 00000000 00000001 ba237d58 win32k!BuildAndLoadLinkedFontRoutine+0x2a2 ba237cf0 bf8ac1b9 0015fd98 bf9bf401 00000000 win32k!bInitializeEUDC+0x156 ba237d3c bf8ab602 ba237d64 80adedd8 00050000 win32k!InitializeGreCSRSS+0x164 ba237d44 80adedd8 00050000 00000194 00000198 win32k!NtUserInitialize+0x62 ba237d44 7eb3e514 00050000 00000194 00000198 nt!KiFastCallEntry+0x158 0015fd80 75b686df 75b68669 00050000 00000194 ntdll!KiFastSystemCallRet 0015fdb0 75b43472 00000000 00000000 0016274d winsrv!NtUserInitialize+0xc 0015fe20 75b4301b 0016272a 00162731 00000003 CSRSRV!CsrLoadServerDll+0x1a0 0015ff74 75b430f3 0000000a 001624f0 7eb3dc9e CSRSRV!CsrParseServerCommandLine+0x2d6 0015ff88 4a68115d 0000000a 001624f0 00000005 CSRSRV!CsrServerInitialization+0x95 0015ffa8 4a6818d7 0000000a 001624f0 0016251c csrss!main+0x4f 0015fff4 00000000 7ffd4000 000000c8 000001d1 csrss!NtProcessStartup+0x1d2 STACK_COMMAND: .tss 0x28 ; kb FOLLOWUP_IP: stornvme+13985 b9ee8985 56 push esi SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: stornvme+13985 FOLLOWUP_NAME: MachineOwner MODULE_NAME: stornvme IMAGE_NAME: stornvme.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5cddb429 IMAGE_VERSION: 4.4.0.1003 FAILURE_BUCKET_ID: 0x7f_8_stornvme+13985 BUCKET_ID: 0x7f_8_stornvme+13985 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x7f_8_stornvme+13985 FAILURE_ID_HASH: {d0239ac1-15ec-3c11-c70d-4d80f769e454} Followup: MachineOwner --------- 20: kd> !thread THREAD 86f3e668 Cid 01fc.0200 Teb: 7ffdf000 Win32Thread: e13e8698 RUNNING on processor 14 IRP List: 86dbea60: (0006,0190) Flags: 00000884 Mdl: 00000000 Not impersonating DeviceMap e10086e0 Owning Process 0 Image: <Unknown> Attached Process 86f40b20 Image: csrss.exe Wait Start TickCount 637 Ticks: 0 Context Switch Count 116 IdealProcessor: 0 LargeStack UserTime 00:00:00.000 KernelTime 00:00:00.015 Start Address csrss!NtProcessStartupForGS (0x4a6811a3) Stack Init ba238000 Current ba235eb8 Base ba238000 Limit ba235000 Call 0 Priority 13 BasePriority 13 PriorityDecrement 0 DecrementCount 0 ChildEBP RetAddr Args to Child ba3e3d10 80a30d7b 00000003 ba3e406c 00000000 nt!RtlpBreakWithStatusInstruction (FPO: [1,0,0]) ba3e3d5c 80a319e6 00000003 00000000 00000000 nt!KiBugCheckDebugBreak+0x19 (FPO: [Non-Fpo]) ba3e413c 80ae0fc7 0000007f 00000008 ba3e0d70 nt!KeBugCheck2+0x574 (FPO: [Non-Fpo]) ba3e413c b9ee8985 0000007f 00000008 ba3e0d70 nt!KiTrap08+0x48 (FPO: TSS 28:0) WARNING: Stack unwind information not available. Following frames may be wrong. ba235a6c b9ee85e5 870d9298 8952c004 86f4257c stornvme+0x13985 ba235a94 b9e6b672 8952c004 86f4257c ba235ad0 stornvme+0x135e5 ba235aa4 b9e6d1e6 894e0190 86f4257c 870d9010 storport!DllInitialize+0x2e1 ba235ad0 b9e6d46a 894e00f0 897e8bb0 00000000 storport!DllInitialize+0x1e55 ba235ae8 801055de 894e0038 00000000 870d9064 storport!DllInitialize+0x20d9 ba235b10 b9e710b6 00000000 894e0038 870d9064 HAL3!HalBuildScatterGatherList+0x202 (FPO: [Non-Fpo]) ba235b40 b9e6d506 894e02a0 894e0038 868946b0 storport!DllInitialize+0x5d25 ba235b80 b9e6d556 894e02a0 00001000 ba235bb0 storport!DllInitialize+0x2175 ba235b90 b9e7b3d8 894e00f0 870d9010 86f42338 storport!DllInitialize+0x21c5 ba235bb0 b9e72692 00000000 86f42338 ba235bd0 storport!StorPortExtendedFunction+0x5fcd ba235bf0 b9e78d93 007e8b28 86f42338 00000000 storport!DllInitialize+0x7301 ba235c10 b9e7bb29 897e8b28 86f42338 86f42338 storport!StorPortExtendedFunction+0x3988 ba235c30 b9e717ec 897e8b28 00000000 897e8a70 storport!StorPortExtendedFunction+0x671e ba235c4c 80a21c8d 897e8a70 86f42338 86f423cc storport!DllInitialize+0x645b ba235c64 ba0f8fdd 00000000 86894e70 86f424d0 nt!IopfCallDriver+0x51 (FPO: [0,0,0]) ba235c78 ba0f8cdc 86f424d0 87084b70 86894f70 CLASSPNP!SubmitTransferPacket+0x82 (FPO: [Non-Fpo]) ba235ca8 ba0f8dcd 00001000 00001000 87084ab8 CLASSPNP!ServiceTransferRequest+0xe4 (FPO: [Non-Fpo]) ba235ccc 80a21c8d 87084ab8 00000000 87084878 CLASSPNP!ClassReadWrite+0xff (FPO: [Non-Fpo]) ba235ce4 ba0c903f 00000000 8958e4f8 ba235d28 nt!IopfCallDriver+0x51 (FPO: [0,0,0]) ba235cf4 80a21c8d 87084878 86894e70 86894e70 PartMgr!PmReadWrite+0x9a (FPO: [Non-Fpo]) ba235d0c b9f1d1c6 894a6e30 86894e70 00000000 nt!IopfCallDriver+0x51 (FPO: [0,0,0]) ba235d28 80a21c8d 894a6e30 86894e70 86fc6100 ftdisk+0x11c6 ba235d40 b9cd01c3 ba236024 86894e70 ba235f30 nt!IopfCallDriver+0x51 (FPO: [0,0,0]) ba235d50 b9ccfd26 ba236024 894a6e30 c0083000 Ntfs!NtfsSingleAsync+0x6d (FPO: [Non-Fpo]) ba235f30 b9cd26f6 ba236024 86894e70 87141e68 Ntfs!NtfsNonCachedIo+0x2f8 (FPO: [Non-Fpo]) ba236010 b9cd200a ba236024 86894e70 00000001 Ntfs!NtfsCommonRead+0xbdd (FPO: [Non-Fpo]) ba2361c0 80a21c8d 86fc6020 86894e70 87147dd0 Ntfs!NtfsFsdRead+0x22d (FPO: [Non-Fpo]) ba2361f8 80a22cab 00000000 86894688 86894678 nt!IopfCallDriver+0x51 (FPO: [0,0,0]) ba23620c 80a22cd3 87147dd0 86894607 86894690 nt!IopPageReadInternal+0xf3 (FPO: [Non-Fpo]) ba23622c 80a7eecb 89532e28 868946b0 86894690 nt!IoPageRead+0x1b (FPO: [Non-Fpo]) ba2362b0 80aa5374 c0033333 c4b03400 c0625818 nt!MiDispatchFault+0x691 (FPO: [Non-Fpo]) ba23631c 80ae20a8 00000000 c4b03400 00000000 nt!MmAccessFault+0xdde (FPO: [Non-Fpo]) ba23631c 80b198af 00000000 c4b03400 00000000 nt!KiTrap0E+0xdc (FPO: [0,0] TrapFrame @ ba236334) ba2363f4 b9cf5a50 89532e28 ba236424 00000400 nt!CcMapData+0x137 (FPO: [Non-Fpo]) ba236414 b9cf5c6b 86f00340 87141e68 00083400 Ntfs!NtfsMapStream+0x46 (FPO: [Non-Fpo]) ba236488 b9cf5b78 86f00340 86fc6100 e13de458 Ntfs!NtfsReadMftRecord+0x86 (FPO: [Non-Fpo])

Oh.. Ice-Age is coming again, I am happy to see Sid, Manfred and Diego again Dietmar

@Mov AX, 0xDEAD @Andalu I install my just brandnew build xp.iso of Ramsey XP SP3 with my laast acpi.sys with OSfakes and the settings in Integrator Patch Integrator v3.4.1.11 1,3,5,6,A,C,D,E on Options Menu (rxrepl).cmd via Firadisk to the MSI z690-A Pro DDR4 board to harddisk. There I install sound, lan, graphik NVidia, just all. I delete the pagefile. All unneeded devices I disable in Device Manager. This may be important. Then I show to it the Toshiba RD400 nvme device and install for this on harddisk the new nvme.sys driver. The RD400 is recogniced at once. Via AOMEI 7.0 I copy the whole harddisk to the RD400. And voila, at once the RD400 boots via the new nvme.sys, so in any case it will be a nice driver for Ramsey. I hope, that with the help of @Mov AX, 0xDEAD we find the reason for Bsod 7F, may be driver conflict Dietmar

Here is everything complete with Tutorial, how to install XP SP3 via Firadisk Dietmar https://ufile.io/vtf22sj7

Best is to burn the xp.iso to a real CD and use a SATA CD-rom 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