Damnation

@Dietmar The Bab-el-Mandeb strait would be more relevant for China to Europe shipping. So it's the Houthi's who might sink your boat, not the Iranians. Fingers crossed it'll make it through.

@Dietmar https://www.aliexpress.com/item/1005012704088998.html

@Dietmar Not yet, it hasn't arrived.

I went and purchased one. @Dietmar Also, this forum seems to go down more and more frequently nowadays, should we move to level1techs or some other forum? level1techs seems to have most of the old Win-RAID forum migrated over to it, I wonder if my old Win-RAID account moved over too? I'll have to check.

@Dietmar I recently watched this video - https://www.youtube.com/watch?v=6fSLN-Fk7VE Did you know about these AMD B650 chipsets on PCIe cards? I wonder if the M.2 slots are bootable?

@Dietmar Oh OK. I didn't know Intel's 14.x XP driver did that. No worries with 5449 then, it'd good enough that you made the 5445 mod.

@Dietmar Success for me too! https://ibb.co/yF15pPPr Thanks very much! Can you apply the same fixes you did to the 5449 driver too? (5449 is the last intel graphics driver released for XP as far as I know) https://buzzheavier.com/9ktobfemwe7o edit: Also, can you figure out why AGP texture acceleration is not available in direct X? I think it should be available?

@Dietmar Yep, this is the same BSOD at the same memory address as my Toughbook. Are you confident that you can find the cause of this BSOD?

@Dietmar Did your Toughbook arrive?

@Dietmar Can you help me to setup Intel LAN debugging on XP? Or are you just going to wait for your own Toughbook to arrive for debugging yourself?

@Dietmar NO_OPREGION, NO_VBT and BOTH all gave same 0x50 BSOD at F000EEF3 as before. POST_ABORT_DIAG gave Code 10 in device manager with no BSOD,

@Dietmar Back to the same location in memory as before with the OpenBSD edits. https://ibb.co/6779ck9F I suppose I'll need your help to get intel LAN debugging setup and running to solve this.

@Dietmar Is it just me or is MSFN running really slow right now?

@Dietmar Sorry it took me so long to reply, I finally got around to testing your first set of binary patches. Here is the result with the DESKTOP patch https://ibb.co/4ZykW8pr This seems to have the BSOD occurring at the same memory address as the original. Here is the result with the FALLBACK version https://ibb.co/XxWXGvmr This still returned a 0x50 BSOD but this time pointing to igxpdv32.dll I'll try out your OpenBST STRICT patch and report back.

@Dietmar I hope you had a nice holiday. I have XP drivers 5445 and 5449 that list the DEV_0A16 in the INF file. I had a look through the CF-53 BIOS and couldn't find anything related to the GPU memory allocation. It might be a hidden option but I don't know how to check for one. I've reimaged it back to windows 10 for now, I'll do a reinstall of XP tomorrow before we start debugging. Do you want me to send you the XP drivers I have for DEV_0A16?