UsefulAGKHelper Posted December 28, 2022 Share Posted December 28, 2022 10 minutes ago, Dietmar said: @RandyOC Most easy way is to install via Firadisk on USB stick to harddisk Dietmar PS: You have a message. It can also be done using SVBUS driver btw. Link to comment Share on other sites More sharing options...
Dietmar Posted December 28, 2022 Share Posted December 28, 2022 Best is to burn the xp.iso to a real CD and use a SATA CD-rom Dietmar Link to comment Share on other sites More sharing options...
Dietmar Posted December 28, 2022 Share Posted December 28, 2022 Here is everything complete with Tutorial, how to install XP SP3 via Firadisk Dietmar https://ufile.io/vtf22sj7 Link to comment Share on other sites More sharing options...
Dietmar Posted December 28, 2022 Share Posted December 28, 2022 (edited) @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 Edited December 28, 2022 by Dietmar 1 Link to comment Share on other sites More sharing options...
Mov AX, 0xDEAD Posted December 29, 2022 Author Share Posted December 29, 2022 19 hours ago, Dietmar said: Do you have an idea, what I can test more with this new nvme.sys driver? EDIT: Can I enlarge the stack by hand in this nvme driver by hand in .text:00413979 sub esp, 0AA8h @Dietmar 1) run !thread after BSOD to see stack limits 2) you cannot change sub esp, 0AA8h without rewriting code after 3) nvme.sys must be patched to execute MmGrowKernelStack() somewhere in init phase when storport called us: 4) where is .pdb for this nvme.sys ? Quote ba295a44 b9d915e5 885c3298 898e8004 8844239c nvme+0x13985 ba295a6c b9da1672 898e8004 8844239c ba295aa8 nvme+0x135e5 ba295a7c b9da31e6 899cca90 8844239c 885c3010 storport!DllInitialize+0x2e1 ba295aa8 b9da346a 899cc9f0 8981f6a0 00000000 storport!DllInitialize+0x1e55 Link to comment Share on other sites More sharing options...
Mov AX, 0xDEAD Posted December 29, 2022 Author Share Posted December 29, 2022 (edited) . Edited December 29, 2022 by Mov AX, 0xDEAD Link to comment Share on other sites More sharing options...
Dietmar Posted December 29, 2022 Share Posted December 29, 2022 @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]) Link to comment Share on other sites More sharing options...
Dietmar Posted December 29, 2022 Share Posted December 29, 2022 (edited) I just get confirmation from @RandyOC that XP SP3 works to full on the 13900k cpu Dietmar Edited December 29, 2022 by Dietmar Link to comment Share on other sites More sharing options...
RandyOC Posted December 29, 2022 Share Posted December 29, 2022 absolutely massive thank you to @Dietmar 13900K and 980Ti on my Z690-A D4 working! 1 Link to comment Share on other sites More sharing options...
UsefulAGKHelper Posted December 29, 2022 Share Posted December 29, 2022 (edited) @Mov AX, 0xDEAD @Dietmar I am a begginer at C and I managed to compile x64 ACPI.sys 2.0 v7 without compiling errors using Mov's tool (thanks to practicing using WinDDK 7600 to compile ntoskrn8 to add functions to drivers, I even learned how to port drivers by adding blank stubs, modifying inf and changing imports using CFF explorer even tho I don't have any experience of adding code in WinDDK besides only functions that are blank stubs, this is relevant because WinDDK has made me learn how to add code in C properly). I wonder if the razzle tool from source code can compile the other files aside from acpi without problems? Because if that's the case, then I will try to compile bootvid.dll so I can try to change the resolution of the kernel vga driver from 640x480 to 1024x768 so I can try to force BSOD to show (using FlashBoot bootmgfw.efi VGA emulator on pure-uefi laptop) to show if XP crashed while booting from 16497 winload pure uefi (with only /BOOTLOGO specified in LoadString, NOGUIBOOT isn't needed), to see if the problem is caused by ACPI.SYS (for debugging purposes on only one computer because I can't afford to buy a second one). Specs: VivoBook Asus X509FA , Intel(R) Core(TM) i7-8565 CPU @ 1.80 GHZ (8 CPUS), ~2.0 Ghz, 8 GB Ram, supports Windows 11, Intel (R) UHD Graphics 620, 500GB NVME SSD (supports IaStorAC.sys/IaStorAVC.sys driver (intel premium optane rst) as mass storage controller, or generic nvme driver on ahci mode), no CSM support (UEFI Class 3), no VGA port, no Optical drive etc. Edited June 10, 2023 by UsefulAGKHelper Link to comment Share on other sites More sharing options...
Dietmar Posted December 29, 2022 Share Posted December 29, 2022 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 Link to comment Share on other sites More sharing options...
UsefulAGKHelper Posted December 29, 2022 Share Posted December 29, 2022 (edited) 11 minutes ago, Dietmar said: 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 By "FakeOS" you mean that the acpi files you have specify a different version of OS rather than the original version? If this solves incompatibility problems then it's great. Edited December 29, 2022 by UsefulAGKHelper Link to comment Share on other sites More sharing options...
Dietmar Posted December 29, 2022 Share Posted December 29, 2022 @UsefulAGKHelper Yepp, the idea is from @daniel_k. I never tested it for XP64 but now I make a try Dietmar Link to comment Share on other sites More sharing options...
Mov AX, 0xDEAD Posted December 29, 2022 Author Share Posted December 29, 2022 8 hours ago, Dietmar said: 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 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 20: kd> !thread Stack Init ba238000 Current ba235eb8 Base ba238000 Limit ba235000 Call 0 @Dietmar This is 100% stack problem, ba234fc4 < ba235000 I made little table based on @Andalu debug log (if we can trust to windbg log), even MS drivers sometime allocate stack memory above 400 bytes, of couse NVMe is badly written, it request most of all: 2728 bytes ! Stack size NVMe+0x13985 5908 22792 40 NVMe+0x135e5 5930 22832 16 storport!DllInitialize+0x2e1 5940 22848 44 storport!DllInitialize+0x1e55 596c 22892 24 storport!DllInitialize+0x20d9 5984 22916 40 HAL3!HalBuildScatterGatherList+0x202 59ac 22956 48 storport!DllInitialize+0x5d25 59dc 23004 64 storport!DllInitialize+0x2175 5a1c 23068 16 storport!DllInitialize+0x21c5 5a2c 23084 32 storport!StorPortExtendedFunction+0x5fcd 5a4c 23116 64 storport!DllInitialize+0x7301 5a8c 23180 32 storport!StorPortExtendedFunction+0x3988 5aac 23212 32 storport!StorPortExtendedFunction+0x671e 5acc 23244 28 storport!DllInitialize+0x645b 5ae8 23272 24 nt!IopfCallDriver+0x51 5b00 23296 20 CLASSPNP!SubmitTransferPacket+0x82 5b14 23316 48 CLASSPNP!ServiceTransferRequest+0xe4 5b44 23364 36 CLASSPNP!ClassReadWrite+0xff 5b68 23400 24 nt!IopfCallDriver+0x51 5b80 23424 20 MirDisk+0x1b6e 5b94 23444 24 nt!IopfCallDriver+0x51 5bac 23468 16 PartMgr!PmReadWrite+0x2f 5bbc 23484 24 nt!IopfCallDriver+0x51 5bd4 23508 28 ftdisk+0x11c6 5bf0 23536 24 nt!IopfCallDriver+0x51 5c08 23560 16 VolSnap!VolSnapRead+0x26 5c18 23576 24 nt!IopfCallDriver+0x51 5c30 23600 16 Ntfs+0x11c3 5c40 23616 480 Ntfs+0xd26 5e20 24096 224 Ntfs+0x36f6 5f00 24320 432 Ntfs+0x300a 60b0 24752 56 nt!IopfCallDriver+0x51 60e8 24808 20 nt!IopPageReadInternal+0xf3 60fc 24828 32 nt!IoPageRead+0x1b 611c 24860 132 nt!MiDispatchFault+0x691 61a0 24992 108 nt!MmAccessFault+0xdde 620c 25100 0 nt!KiTrap0E+0xdc 620c 25100 216 nt!CcMapData+0x137 62e4 25316 32 Ntfs+0x26a6e 6304 25348 116 Ntfs+0x26c89 6378 25464 56 Ntfs+0x26b96 63b0 25520 56 Ntfs+0x26aed 63e8 25576 176 Ntfs+0x3573d 6498 25752 216 Ntfs+0x3535c 6570 25968 600 Ntfs+0x356f5 67c8 26568 228 Ntfs+0x25f2d 68ac 26796 100 nt!IopfCallDriver+0x51 6910 26896 232 nt!IopParseDevice+0xb6a 69f8 27128 120 nt!ObpLookupObjectName+0x590 6a70 27248 84 nt!ObOpenObjectByName+0x140 6ac4 27332 124 nt!IopCreateFile+0x43b 6b40 27456 96 nt!IoCreateFile+0xd4 6ba0 27552 780 win32k!EngGradientFill+0x7a7e 6eac 28332 60 win32k!EngQuerySystemAttribute+0xa03 6ee8 28392 52 win32k!EngLoadModule+0x9a 6f1c 28444 16 win32k!EngLoadModule+0xf 6f2c 28460 100 ativvaxx!vMMDLLInitFuncs+0x8290 6f90 28560 436 ativvaxx!vMMDLLInitFuncs+0x32450 7144 28996 40 ativvaxx!vMMDLLInitFuncs+0x30c5f 716c 29036 28 ativvaxx!vMMDLLInitFuncs+0x2e12f 7188 29064 20 ativvaxx!vMMDLLInitFuncs+0x1a69a 719c 29084 32 ativvaxx!vMMDLLInitFuncs+0x20985 71bc 29116 16 ativvaxx!vMMDLLInitFuncs+0xf6e3 71cc 29132 84 ativvaxx!vMMDLLInitFuncs+0xf65f 7220 29216 232 ativvaxx!vMMDLLInitFuncs+0x5734 7308 29448 28 ativvaxx!vMMDLLInitFuncs+0x5c36 7324 29476 20 ativvaxx!vMMDLLInitFuncs+0x5bdc 7338 29496 72 ati3duag!bDdHslVideoMemoryFree+0x22e7 7380 29568 568 ati3duag!bDdHslVideoMemoryFree+0x7eb4 75b8 30136 24 ati3duag!bDD4DISPInitDD+0x72 75d0 30160 40 ati2dvag+0x17b09 75f8 30200 888 ati2dvag+0x18070 7970 31088 80 win32k!EngQuerySystemAttribute+0x5b4 79c0 31168 72 dxg!vDdEnableDriver+0x8a 7a08 31240 28 dxg!DxDdEnableDirectDraw+0xbf 7a24 31268 Link to comment Share on other sites More sharing options...
Dietmar Posted December 29, 2022 Share Posted December 29, 2022 @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 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now