Should get interesting soon =)
https://developer.nvidia.com/blog/nvidia-transitions-fully-t...
Yet to personally try it out, but this should eventually enable better integration with the library ecosystems. =3
I also increased UMA to 4 GB, it reduced the crash frequency, but it still happens.
The discrete NVIDIA GPU I use at the same time is fine.
If there is enough data here, we may be able to see a common key detail emerge. i.e. if the anecdotal problem(s) remain overtly random, than a solution from the community or OEM may prove impossible.
Thanks in advance, =3
Stability has been fine since. The bug report has since been closed but I haven't tested in a while to see if disabling PSR is still needed or if the issue has actually been fixed.
I haven't seen significant stability issues on Windows, although I don't use it much on the AMD device.
Your tip may help some folks in the future. =)
With PSR in the mix, is the system really hanging or is it just failing to update the screen somehow? I.e. can you tell the difference with logs or a remote connection or configure and use an unprompted shutdown via the power button?
I can't remember the details of it. It effectively hung in the sense that I couldn't get the system into a usable state again locally without rebooting. I'm not sure if the system responded to the power button or not, or whether there was useful log output.
I didn't bother trying with a remote connection since the hang was frequent enough that it wouldn't have been of any use as a workaround anyway. I'd guess switching to another virtual console probably didn't work because I'd probably remember it if it did.
I can try re-enabling PSR and see if the problem is still there if you're interested.
So, I don't really know if the system was fully hanging, or if the display was just unable to update any more, but it was likely exactly the same that happened to other people with Parade TCONs in that bug discussion.
sudo apt-get install cpu-x
sudo cpu-x
I think comparing your specifications may help other users narrow down if a manufacturing or software defect is present.
Thanks in advance =3
Increasing the VRAM size (UMA size) to 4 GB fixed the frequent driver timeouts for me.
Reverting to older driver (driver cleaner -> driver v23.11.1) fixed the memory leak. This memory leak is weird since PoolMon doesn't show anything unusual. Nothing shows as using too much memory anywhere, except committed memory size grows to over 100GB after few days of uptime and RamMap shows a large amount of unused-active memory.