<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - amdgpu [RX Vega 64] system freeze while gaming" href="https://bugs.freedesktop.org/show_bug.cgi?id=109955#c118">Comment # 118</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - amdgpu [RX Vega 64] system freeze while gaming" href="https://bugs.freedesktop.org/show_bug.cgi?id=109955">bug 109955</a> from <a class="email" href="mailto:rodamorris@gmail.com" title="Rodney A Morris <rodamorris@gmail.com>"> Rodney A Morris</a> <pre>(In reply to haro41 from <a href="show_bug.cgi?id=109955#c117">comment #117</a>) > ...are this craches more frequently with VSYNC enabled? > > If yes, it could be the same thing like this bug: > > <a class="bz_bug_link bz_status_NEW " title="NEW - Kernel 5.1-5.3 MCLK stuck at 167MHz Vega 10 (56/64)" href="show_bug.cgi?id=110777">https://bugs.freedesktop.org/show_bug.cgi?id=110777</a> vsync is defintely on for both Stellaris and Hearts of Iron. I looked over the bug report you linked to. It is very interesting and I will follow with interest. The next time I play Stellaris or Hearts of Iron IV, I will have to see if I can record my memory frequency values to see if they are indeed not moving off the base frequency under low load with v-sync enabled. The problem manifesting under low load would explain why I cannot replicate the problem while running Unigine Superposition. I began to wonder if powerplay and the frequency at which the chip and memory were operating were not the problem after reading the following bug report for Vega 20: <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Crashes / Resets From AMDGPU / Radeon VII" href="show_bug.cgi?id=110674">https://bugs.freedesktop.org/show_bug.cgi?id=110674</a> Last Friday, I attempted to capture the operating frequency and temps, but my attempt utterly failed. I will disable v-sync and see if that improves and report back here. If I manage to capture frequency data, I will report back here and may be your thread.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>