9/22/2023 0 Comments Power management mode nvidia crashThe most stable intermediate overclock I've found in the past month is 1246 base clock, 1386 boost clock, and 1903 memory clock. What got my attention the most was when I tried playing around with my overclocks to try to find a solution I found that an intermediate overclock was the most stable for Warframe (even though I've been told numerous times Evolution Engine hates overclocking). This is by far the most unstable, crashing within 1-2 minutes of getting into game. I set my "reference clock" as 1037 base clock, 1177 boost clock, and 1750 (7000) memory clock. The Nvidia reference specs are 1050 base clock, 1178 boost clock, and and 1750 (7000) memory clock. I then tried to remove the factory overclock and get as close to the Nvidia reference specs as possible. This also caused crashing within the first 5 minutes of Warframe or so. I then decided to reset my overclock back to the factory overclock (default clock 1076, boost clock 1216, memory clock 1753 (7012), all in MHz). When I overclock to my usual max stable specs (this causes no problems even on demanding engines like Frostbite 3) I usually crash within the first 5 minutes of Warframe. Despite this, I did some experimenting and found some interesting results. I've been told that overclocking the GPU causes problems with the Evolution Engine. GPU: Zotac Geforce GTX 970 (base version, not AMP! Extreme or OMEGA) I’ll try the kernel parameter and report back.I've had problems recently with Warframe repeatedly crashing my GPU driver while playing. Is the freeze on wayland a known issue? Any bug I could you’re probably right that it’s dpm-related, here are the log messages from the crash (which, if anyone is curious, I obtained by running journalctl -b -1 on the next boot): Feb 13 02:56:46 fedora kernel: amdgpu: No response from smuįeb 13 02:56:46 fedora kernel: amdgpu: Failed message: 0x4c, input parameter: 0x2830001, error code: 0x0įeb 13 02:56:48 fedora kernel: amdgpu: No response from smuįeb 13 02:56:50 fedora kernel: amdgpu: No response from smuįeb 13 02:56:50 fedora kernel: amdgpu: Failed message: 0x4c, input parameter: 0x2830001, error code: 0x0įeb 13 02:56:53 fedora kernel: amdgpu: No response from smuįeb 13 02:56:55 fedora kernel: amdgpu: No response from smuįeb 13 02:56:55 fedora kernel: amdgpu: Failed message: 0x4c, input parameter: 0x2830001, error code: 0x0įeb 13 02:56:57 fedora kernel: amdgpu: No response from smuįeb 13 02:56:59 fedora kernel: amdgpu: No response from smuįeb 13 02:56:59 fedora kernel: amdgpu: Failed message: 0x4c, input parameter: 0x2830001, error code: 0x0įeb 13 02:57:04 fedora kernel: ] *ERROR* Waiting for fences timed out! And if I have to logout when I play a game, I might as well boot to all the way to Windows instead, it’s not that much slowerĭevice-1: AMD Vega 10 XL/XT driver: amdgpu v: kernelĭisplay: wayland server: X.Org 1.21.1.4 driver: loaded: amdgpu,ati Buttery smooth Wayland is pretty much the main reason I switched away from Windows. I’d expect fan control to not be affected by wayland/X, but alas.Īnyway, it wouldn’t be worth it as a workaround for me: I can’t stand Xorg – the stutter and dropped frames are way too obvious in GNOME. It’s strange because under wayland it’s all good. Switching to Xorg only replaces one problem with another: yeah, it no longer freezes, but apparently the drivers then forget to spin up my GPU fans, for some reason, so after a minute or so the GPU’s thermal protection kicks in, it shuts down and the fans go to max.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |