fastfishy2

So far I've had no stress test hangup. One thing I have noticed is that my former (until yesterday) 860 EVO boot SSD was showing LBA errors in Samsung disk utility when doing a short SMART test. Neither my 970 Evo plus NVME (My current boot drive) or my 870 QVO SATA 2TB (My current bulk storage drive) had this problem. Could have been a contributor. In any case I'll keep re running various tests when I get time to see if the issue crops up again.
 
On the upside though, the system is definitely snappier running off an NVME. And the NVME is happy because it has one of those EK passive heatsinks on it.
 
EDIT: also as of this morning the 860 evo had nothing on it except an empty steam library folder, and as it's only 500gb and a few years old I just removed that storage space on disk manager and then powered down the system and physically removed it. I won't miss it. I did also check all my other drive firmware was up to date.

so, reboot and try the process again. Got it.
 

I can confirm from setting the mobo max cpu fan ramp temperature lower, and monitoring package and core, the mobo is taking its cpu fan speed cues from CPU, not package. I'll just have to account for that in my fan curve.

Ok so, there's a lot going on here.
I ran HWinfo64 for the first time in ages and realised that the temps reported by OCCT and Ryzen master are CPU package temp, whilst there is a separate temperature for the CPU core itself which is around 10c lower. This explains the strange fan curve behaviour as the motherboard is likely reading CPU core temp whilst I've been looking at package temp the entire time.

ok so it seems to be a sensor discrepancy or some quirk of the bios - if the CPU hits 90c (i.e. prime95) the fan will ramp right up to absolute maximum and read around 1420 rpm.

Ok so, there's a lot going on here.
I ran HWinfo64 for the first time in ages and realised that the temps reported by OCCT and Ryzen master are CPU package temp, whilst there is a separate temperature for the CPU core itself which is around 10c lower. This explains the strange fan curve behaviour as the motherboard is likely reading CPU core temp whilst I've been looking at package temp the entire time.

well the temps so far are already awesome, I'm really pleased with it, and this is before it even breaks in.

(((My goals are beyond your understanding)))

Nah, so the idea is DLSS starts with  900p, upscales it to 1440p, and displays that to my 1080p monitor. It effectively acts as anti aliasing.

Not in my experience. DLSS seems to do a far better job of anti aliasing than most AA techniques while maintaining image quality and a lower performance hit

RTX 4070. Was playing some Control on fullscreen mode, maxed out settings including ray tracing, DLSS set to quality.
I have DSR factors enabled so that I can run games at a higher internal resolution than my 1080p monitor, it makes images smoother at the cost of performance.
Now, Control does something when I alt-tab / windows key to interact with my second monitor. The DLSS render resolution stays the same, but the overall render resolution reverts back to native (1080p).
I never had this problem before because I'd run at 1440p default res and the DLSS resolution would be at around 1700 x 920 or so. So when I alt-tabbed, the output resolution (1080p) was still larger than the DLSS resolution (920p ish).
Today I tried running it with 4k internal render resolution, which moved the DLSS render resolution up to 1440p. That ran fine, if a bit slowly, but I alt-tabbed to look at something on my other monitor and then jumped back into the game to witness some truly horrific artifacting. After retrying the problem a few times, I noticed something. DLSS is still trying to render the game at 1440p and upscale it, but the output resolution in the game has defaulted back to 1080p instead of 2160p/4k (or anything above 1080p for that matter), and of course now DLSS gets very confused and upset and the whole thing turns into a grid-shaped clown car. 
 
TL;DR: don't put yourself in a situation where your render output resolution is somehow smaller than the base resolution DLSS is trying to upscale from. It doesn't like it at all.
EDIT: No, it doesn't do this in heavy benchmarking (port royal etc) or any other games, and simply reminding the game what resolution it's meant to be running at solves the issue. It also doesn't have a problem with other resolutions as long as the DLSS render resolution is smaller than whatever native res the game reverts back to.
 

yeah, as I said though the only test it gets to 90c with is OCCT small data set. Medium and large data sets it stays well below 90c, low 80's at worst but usually high 70's, and it does well enough in cinebench etc.

yeah I'll give it a go *if* it happens again
 

oh fair enough, somehow I forgot about watercooling lmao

Just got a brand new RTX 2070 Gaming OC from gigabyte, one of the three fans (closest to the display output side) has verrry slight wobble which gets less noticeable the higher speed the fan runs at. It's not making any noise and is running fine. Getting the card fixed or replaced under warranty is not something I really want to do so, is this likely to be much of a problem or is this fine? If not, where can I order a replacement fan as I'd much rather go through that process myself rather than mucking around with the retailer (or god forbid Gigabyte's RMA team especially at this time) over what is otherwise a perfectly fine card.

and as an added note, as GamersNexus mentioned, the retention force on most CPU coolers is well high enough to just push aside any excessive amount anyway, so unless you go some stupidly creative flavour of overboard, too much actually doesn't do much detrimental... to cooling performance at least.

fair enough, would B450-based boards be a better bet?