Damnation

@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?

I used this to image my XP drive. https://rargb.to/torrent/acronis-true-image-build-42980-bootable-iso-crackshash-6635281.html You'll want to image the whole disk so that it copies to boot record too.

@HarryTri Yes I'm installing the right driver.

@Dietmar I'm willing to try with LAN debugging if you're willing to help me get it set up and can help me find what to look for. I won't have the Intel Graphics driver symbols though.

@HarryTri The BSOD always happens whenever I install the Intel GPU driver and then reboot. This happens even on a new fresh XP install with nothing else installed.

Hi @Dietmar I recently purchased a Panasonic Toughbook CF-53 off of ebay with the intention of turning it into a rugged XP laptop to last for years. https://www.ebay.com.au/itm/256347295953 My assumption was that there would be XP drivers for everything in this laptop, except for perhaps the internal wifi. This turned out to be true, I found drivers for everything in this laptop except for the internal wifi, which I worked around by purchasing this USB wifi dongle. https://www.ebay.com.au/itm/336201595217?var=545751826956 There is even an XP driver for it in the driver download for it. https://www.realtek.com/Download/List?cate_id=664&menu_id=297 I know it doesn't list XP on the site, but the driver for XP is in there and it works. Unfortunately, I've run into an issue where even though the Integrated Intel HD 4400 chip has XP drivers and they do install correctly. https://www.upload.ee/files/12999940/WinXP32_Last_driver_4000_.zip.html Upon reboot I always get a 0x50 PAGE_FAULT_IN_NONPAGED_AREA BSOD at boot. I'm not skilled enough to figure out why this BSOD is happening. Can I ask you to purchase one of these laptops and find out what is causing the Intel GPU driver to BSOD? It's got XP drivers so it really should just work. https://www.ebay.com.au/itm/256347295953 I can contribute some of the $500CAD to help purchase this if you need it. The one I got is pristine, pretty much unused and brand new which is good. I'd really like you help to get this laptop to work in XP. Would you be interested in this? (I had written this as a PM at first but apparently you can't receive them?)

Turn on CSM in your BIOS and then try to boot.

@reboot12 Are you going to be putting everything you've worked on into a WIM image for easy UEFI 64bit installation? You could probably use something like Universal NT Installer to apply the image, but getting the UEFI boot part working might need some additional script of some sort.

@UsefulAGKHelper Best to start over again with a fresh, unmodified source code tree and reapply the patches over again then.