Damnation

@Dietmar meed more information. Install HWMonitor and report CPU and GPU temps when both idle and stressed.

@LanXing have you got a 2nd PC to spare for LAN debugging? If you're willing to setup LAN debugging that's your best chance of getting a solution.

@Mov AX, 0xDEAD If you're feeling motivated, can we start working on NDIS6 support for XP? missing imports - ndis - NtTraceControl KeRegisterProcessorChangeCallback RtlNumberOfSetBitsUlongPtr KeTestSpinLock IoGetDeviceNumaNode NtQuerySystemInformationEx netio - MmAllocatePagesForMdlEx KeFreeCalloutStack KeAllocateCalloutStack SeCaptureSubjectContextEx KeTestSpinLock SeAccessCheckFromState RtlCreateHashTable RtlDeleteHashTable RtlGetNextEntryHashTable RtlLookupEntryHashTable RtlRemoveEntryHashTable RtlInsertEntryHashTable RtlEndEnumerationHashTable RtlEnumerateEntryHashTable RtlInitEnumerationHashTable RtlContractHashTable RtlExpandHashTable msrpc - IoSetIoCompletionEx ZwAlpcCancelMessage ZwAlpcCreatePortSection ZwAlpcCreateResourceReserve ZwAlpcCreateSectionView ZwAlpcCreateSecurityContext ZwAlpcDeletePortSection ZwAlpcDeleteSectionView ZwAlpcDeleteSecurityContext ZwAlpcDisconnectPort ZwAlpcQueryInformation ZwAlpcSetInformation ZwCreateIoCompletion ZwImpersonateAnonymousToken ZwRemoveIoCompletionEx

@Mov AX, 0xDEAD @Andalu You just need a USB crossover cable, https://www.datapro.net/products/usb-3-0-super-speed-a-a-debugging-cable.html

If anyone else wants to have a go and try to make this work then just ask and I'll send you the source code.

@Andalu USB to LAN adapters aren't going to work. kdnet would need to implement part of the USB driver stack ontop of the code for all the LAN chipsets. very unlikely to ever be implemented. kdnet is hardcoded to support specific hardware, and they're all PCI/PCI-E lan adapters.

@Mov AX, 0xDEAD yep, that was it. stupid failing eyesight!

@Mov AX, 0xDEAD In w2003_tools_update.zip should I copy everything across? or just tools? I've been copying everything across. edit: oh I see now! my eyes skipped over the renaming public to public2 - I literally didn't see until just now - that's probably the issue.

@Mov AX, 0xDEAD redid the build environment, made sure swapped out the compiler with the newer one. original unmodified acpi driver code compiled correctly. but as soon as I apply your 4.2 patch file and compile I get errors. srv03_acpi_build_errors.zip

@Mov AX, 0xDEAD Something isn't working in amd64_helpers.asm

I tried acpi.sys compiled by @George King No A5 BSOD which is good. 149C USB3 controller still non functional at boot though, I was hoping @Mov AX, 0xDEAD's doubled device definition workaround might help to get it to work, no luck sadly.

@Mov AX, 0xDEAD I got these errors when trying to compile 2003 amd64 version - edit: tried build /Zcegbw no difference.

@Mov AX, 0xDEAD did you forget to post the link for the 2003 version? or is it not finished yet?

@sonyu I know the windows 8.0 acpi sys you're referring to, that acpi.sys just has a skip DDB error hack, the error I was having has been solved through debugging and @Mov AX, 0xDEAD's genius. Seriously dude the whole XP enthusiast community can't thank you enough for all your hard work, without which none of this would be possible! Sincerely, thanks a lot! @Mov AX, 0xDEAD much appreciation!

@Mov AX, 0xDEAD For my AMD AM4 systems I've only ever seen the CrackPRT 7E BSOD that has already been solved. I have not seen either of these BSODs on my AMD systems. When my new B550 build arrives I'll test it, I think it should be fine though.

@genieautravail What error code is device manager giving you for the 6600m? try using DDU to wipe clean the GPU drivers and then try reinstalling the drivers.

@Mov AX, 0xDEAD Was this behaviour what you were expecting?

@Mov AX, 0xDEAD This one is much larger - https://ufile.io/dp9sa4h1

@Mov AX, 0xDEAD I don't see an option to save the log file in the Open/close logfile window.

@Mov AX, 0xDEAD Here is what I could copy out of the debug window, it's not the whole thing though, it got cut off at some point, I'm not sure how to get the whole thing. @daniel_k No, without an acpi.sys hack I get BSOD A5 0x11 0x8 DDB error. Windows 8.0 has same problem. Windows 8.1 works. TRX40_DESIGNARE_ACPI_DEBUG_2.zip

@Mov AX, 0xDEAD I'm guessing this would require a BIOS and SSDT modification? or can the acpi.sys driver be written to handle it in this way by itself?

@Mov AX, 0xDEAD Yeah, I'm going with commenting out those 3 lines as a sub-optimal solution. I'll email gigabyte about it and maybe they'll fix it, I wouldn't get my hopes up though, they'll likely just say to RMA my board rather than giving an actual solution.

@Mov AX, 0xDEAD Could there be some hints in the linux kernel source for how to handle this properly? https://github.com/torvalds/linux/search?q=AE_ALREADY_EXISTS

@Mov AX, 0xDEAD I would like to try and find the exact cause of the USB\RESET_FAILURE problem for devices connected to the HUB on the 149C USB3 controller. I don't know where to start going about this with my debugging setup though, would you be willing to help me do this? I don't think this will be easy, as XP reports USB3 Controller and Hub as working normally, only the devices themselves report a problem.

@Dietmar here - https://ufile.io/1obwi832 note: the way I did is sloppy so put it in it's own XPSP1_64 source tree away from the 32bit tree, seems to break the 32bit tree if left in there.