You can try installing win10 first and if the computer works, then try installing 24h2 with an upgrade. if you have another hard disk, you can replace it and maybe the problem will not exist. Most likely the problem is with the hard drive, using a partitioning tool to clear all current partitions or even low level formatting it all over again can fix the problem.
Thank you, I saw this thread and remembered patching windows to trick AutoCAD to work on cheap CPU's. That was a long time ago, windows 95, with DOS based AutoCAD.
That was back in the 386/486 CPU days. Intel released 2 variants of the chips, one was cheaper but lacked the math co-processor. Intel had a way to emulate the co-processor, but that wasn't the fix. It was when someone wrote a co-processor emulator patch that tricked programs like AutoCAD to think the CPU had the needed co-processor allowing the program to run, albeit slower then the if it really had a co-processor but it worked. This was back in the 1990's when the Pentium CPU's were too expensive, EDO RAM, IDE drives with master/slave jumpers. Ram had clock frequency jumpers to set the multipliers. I remember it had to be entered in the config.sys file to run on the boot. That was 30 years ago. Why I posted it was to bring light to the idea of emulators to provide the appearance of the required processor. I was thinking that someone a lot smarter than me would see this as a way around the limitation and figure a way to emulate the SSD 4.2 chip. Does anyone write code in assembly language anymore?
Apart from the emulator (i87fpu, slow) one could also install an NPX coprocessor (Numeric Processor eXtension), for example from Weitek.
Even if someone eventually manages to inject SDE into the boot process, an OS shouldn't rely on emulation for mathematical tasks. It will be just too slow and not practical.