#PC takes awhile to shutdown after coding
1 messages · Page 1 of 1 (latest)
Might be a hot take, but I noticed something similar when I tried to dial in some overclocks. In particular reducing voltages (curve optimizer on amd) or tighter ram timings.
What i noticed was, that the overclock wouldn't be 100% rock stable, but stable enough to do benchmarking, gaming etc. (so you could assume it was stable, but it wasn't)
Windows would behave absolutely normal, but after heavily utilizing the system (benchmarks, stress tests), it seems like the system had some kind of "silent stroke", as if some bits "tilted", but not enough to bluescreen on you, but enough that something was of.
My reboots also took longer after this kind of "silent stroke" and I noticed that some things like minimizing a window could also take longer or had some kind of unusual delay.