You can disable it from windows device manager, go to Device Manager > System Devices > High Precision Event TimerThe HPET setting isn't there.
Using approved RAM is the best way to avoid compatibility problems, especially on HP machine, but very often uncertified RAM works fine, also it's important to use the proper RAM slots when not all slots are used, so I tried to suggest checking it to exclude another possible issue.valis wrote: ↑Sat Mar 07, 2020 8:52 am It''s rare that certified RAM makes a difference, though in our current era using RAM that runs at JEDEC speeds versus XMP Profiles MAY in some cases improve stability (XMP overclocks RAM past JEDEC defaults, and changes timings, which in most cases is fine but it can reduce the lifespan of RAM or cause poorly binned chips to show flaws relatively quickly). On this era of machine, that's irrelevant. What certified DOES tell you is that the manufacturer 'approves' of it due to their testing, which of course can give peace of mind.
However I had stated somewhere above that 4GB of RAM is far too little for Win10 + Live. The dual core system I gave my daughter was only usable for light web browsing and low end gaming with 4GB ram, by upgrading it to 8GB it became immensely more responsive. If you're on a 64bit version of Live, 16GB might be better but I'm not sure 4GB DDR2 sticks are all that affordable outside of used on ebay, so 8GB is probably more reasonable. I bought new warranteed 4GB kits (2x2GB) on amazon for about $17.99 per kit (~$37 total including tax). They're certainly not certified since it's some "Kuesuny" brand, but stability tests with AIDA64 show no issues.
That probably won't solve your DPC latency issues however. Something on that system is not playing well...sorry to say.
GDI+ is XP era (GDI for NT4/Win98/ME). My understanding was that the DWM didn't allow GDI+ to run any longer but rather ran it emulated. Either way, glad that this got it working, interesting that it kicked it when you put the old GPU back in. Just documenting this as it may be needed info later when u have to sort this out again (due to OS updates or who knows).The file name is Options.txt and the option is -_ForceGdiBackend
Found it on Ableton forums, so it's something specific to Ableton Live, there are several threads about how to trick GDI on stackoverflow if you take a look.valis wrote: ↑Sun Mar 08, 2020 9:04 pm From the link to the Ableton forum above:GDI+ is XP era (GDI for NT4/Win98/ME). My understanding was that the DWM didn't allow GDI+ to run any longer but rather ran it emulated. Either way, glad that this got it working, interesting that it kicked it when you put the old GPU back in. Just documenting this as it may be needed info later when u have to sort this out again (due to OS updates or who knows).The file name is Options.txt and the option is -_ForceGdiBackend
