@Andalu
looking at your log file symbols should go here
Symbol search path is: C:\WINDOWS\Symbols
this path should be on your HOST machine (the one running windbg) not your TARGET machine (the one with the BSOD)
@Welder
Welcome!
This would be an extremely difficult task - Vista and later use WDDM driver model whereas XP and earlier use XDDM driver model.
I'm not saying it'll never happen, but it's not likely.
Best use XP compatible Maxwell and earlier GPUs for nvidia on XP.
@George King@Mov AX, 0xDEAD
We could also try the ACPI OS version lie trick in the driver instead of editing the DSDT.
I don't remember how to do the trick though.
but I'm sure ACPI OS version is defined somewhere in the code.
@Andalu
I got you PDB symbols for all 4 ntoskrnl's
hope this helps.
https://anonfiles.com/vbK9Z1Y7xa/andalu_ntkrpamp_symbols_7z
for acpi.sys PDB symbols, build from source.
@George King
Forgot to ask, did you want free or checked amd64 build?
edit:
oh, I see the problem - missing imports
KeInitializeSpinLock
KeQueryInterruptTime
@George King
I've made an amd64 build for you - I used old versions of ACPIDevicePowerProcessPhase3, OSNotifyDeviceCheck just to get a successful compile.
https://anonfiles.com/9555z5Ybx0/acpi_xp_amd64_forGK_7z
lets see if this one works.
@Mov AX, 0xDEAD
Out of curiosity I wanted to ask, was there any particular reason why functions like ACPIDevicePowerProcessPhase3, OSNotifyDeviceCheck were implemented in assembly and not C code?