Could anyone check if they get errors when testing with MSI Kombustor (GL) msi-01 (first test from the dropdown menu), enable Artifact Scanner and see if there are errors logged even when running default clocks/voltages?
No, actually it doesn't error even with OC preset, as my VRAM clocks never go above 1538 [Maybe as i only have 1920*1080. I cannot see how 4k would be, because all data is off the screen]. Without OC they are even lower, most of the time at 909 mHz.
But i do hit 3150 mHz or so running it with OC (only 2750 or so without it) doing artifact scanner. Max frequency is not THAT much of an issue for boost algorithm it seems (it does take some time to reach it though).
Will try to enforce max VRAM frequency (at cost of performance, of course).
-- Well, not consistent 2557 mHz reported, but no artifacts either. So... Are you sure it is not your OC that is unstable? For me unstable VRAM will just cause sudden hard reboot and throws single critical WHEA 18, even at idle occasionally. There is some range where vulkan_memtest will throw errors, sure (at around 2650+FT for me, while 2660+FT will just instantly reboot under load). But after multiple reboots (and VRAM reduction) atm my VRAM is stable at 2570+FT. It took actual WEEK of PC uptime for it to cause a last reboot at 2580+FT btw.
I also wonder how for you people 1050 mV and below can be even possible other for some very limited use cases? ASIC 69.0%.
Granted, i SPECIFICALLY have game that is absolutely brutal on GPU stability. 890-900 was fine to run Superposition, but Time Spy and Warframe won't even launch. 970 was fine to run TimeSpy, but Warframe will easily crash. At around 1060 i thought i managed to get away from crashes, but then i limited FPS to 144. And, oh boy... Right now i am at 1100mV already (1090 mV just crashed today on Archon Hunt). I know it would be able to run plenty of games at 1060 or slightly higher. But that is not my target. That is why i currently brutalize my GPU with Warframe with limited FPS. I should be close to stability right now, and please... Fate? Let 1100 mV be enough (1. Round number, 2. Why should it be higher?).
Btw, for information purposes. RDNA3 boost algorithm is instantaneous (meaning it doesn't hold frequency at value you see as reported, frequency is always wildly swinging from low to high and vice versa) and limited both by peak and average power consumption. Meaning on low enough FPS you can see either 30-2400 mHz core (no mistakes, it will report 30 mHz because load time is not enough for it to report any higher sometimes). Or it will report something like 3100+ mHz for example in artifact scanner. But that way of power management despite being efficient in saving power should have huge downside - transient response. Meaning if you don't account for peak to peak voltage drop, GPU won't become stable. And if you run higher FPS, or higher load stuff, it can actually be more stable than when you drop load to some extend, so GPU would idle in between.
---
Can you download and run GravityMark? After completing the benchmark (default settings are fine), leave it running in the background where it shows your results. In my experience, running 3000+ max clock will result in artifacts in that benchmark section.
GravityMark downloads like turtle from 20 years ago (62.5 KBps), when i finish downloading it, will try it out. I had some artifacting (in line of purple-ish corruption effect), but only in EXTREMELY specific place (on one title screen with 480 FPS limiter) when FPS dropped from single frame due to two games running simultaneously, and i cannot reproduce it right now because i cannot get frames to drop again. And that also happens on default settings, so, no... It is not OC issue.
Will report when i try.
UPD: No artifacting after GravityMark except shimmering from lots of details on small resolution and pop-in on some asteroid's textures. GPU autoboosted to 2970-->3025 mHz (first to 2970, then SLOWLY to 3025 within some timeframe). Result: 42799 pts with default settings.
Currently have:
Min_clock = 500 mHz
Max_clock = 3100 mHz
Voltage_curve = [1100 mV crashed] 1110 mV
Power limit = +15%
VRAM_freq = 2570
Fast Timings = enabled
