|
Dr. Video Games 0031 posted:Users who might want some advantage from overclocking but don't want to manually oc for funsies should just use the buildzoid timings. Despite him being wrong about a few things, his DDR5-6000 timings are highly compatible with Hynix kits and provide a tangible benefit over stock DDR5-6000 expo. There seems to be a bigger gap between buildzoid's timings and EXPO timings than there is between buildzoid timings and the DDR5-7800 config. Yeah, BZ timings are great. He did a good job of choosing conservative enough timings that still capture the majority of the performance benefit of manual tweaking. IIRC his suggestion of using 2033MHz is because the early AGESAs actually hard enforced the 2:3 ratio by silently upping the MCLK/UCLK to match, so his 2033 numbers are actually running at 6100MT/s which is why he sees a performance benefit. Newer AGESAs don't do this and will absolutely let you desync your FCLK, and doing it to gain 33MHz is not worth it.
|
#
?
Feb 26, 2024 13:02
|
|
|
|
| # ? Apr 29, 2024 08:33 |
|
|
Dr. Video Games 0031 posted:Users who might want some advantage from overclocking but don't want to manually oc for funsies should just use the buildzoid timings. Despite him being wrong about a few things, his DDR5-6000 timings are highly compatible with Hynix kits and provide a tangible benefit over stock DDR5-6000 expo. There seems to be a bigger gap between buildzoid's timings and EXPO timings than there is between buildzoid timings and the DDR5-7800 config.
|
|
#
?
Feb 26, 2024 16:33
|
|
|
Dr. Video Games 0031 posted:Users who might want some advantage from overclocking but don't want to manually oc for funsies should just use the buildzoid timings. Despite him being wrong about a few things, his DDR5-6000 timings are highly compatible with Hynix kits It's just that I've the 2033MHz FCLK set because of some rambling in the same video, that it'd always be off somehow and the added 33MHz are supposed to give an improvement. Yet these quoted benchmarks a few posts above show a latency improvement that seems worthwhile by just dropping 33Mhz.
|
|
#
?
Feb 26, 2024 18:09
|
|
|
BlankSystemDaemon posted:As in, it'll show a noticeable performance benefit in real-world gaming, or synthetic benchmarks that just benefit from bandwidth and don't take latency into account? The chart at the top of the pic BurritoJustice posted shows figures for a mix of games and other software.
|
|
#
?
Feb 26, 2024 19:56
|
|
|
BlankSystemDaemon posted:As in, it'll show a noticeable performance benefit in real-world gaming, or synthetic benchmarks that just benefit from bandwidth and don't take latency into account? I mean in real-world videogame Baldur's Gate 3 you're gaining 10FPS just from BZ timings over EXPO in the chart I posted. It's been true for generations now that if you are running highly tuned/overclocked ram you're basically a generation ahead on gaming performance. A 9900K with tuned to the gills ram sits roughly in between a 5800X and 5800X3D in games.
|
|
#
?
Feb 27, 2024 04:55
|
|
|
ConanTheLibrarian posted:The chart at the top of the pic BurritoJustice posted shows figures for a mix of games and other software.  BurritoJustice posted:I mean in real-world videogame Baldur's Gate 3 you're gaining 10FPS just from BZ timings over EXPO in the chart I posted. I'll need to look up if I have Hynix A/M-die memory, so that if I ever get a game that's not already pushing +300FPS (like Elite Dangerous is, at max settings, which is the only game I play currently), I can take advantage of it. Also, it's this set of timings, right?
|
|
#
?
Feb 27, 2024 11:56
|
|
|
BlankSystemDaemon posted:Also, it's this set of timings, right? That's the one, yeah.
|
|
#
?
Feb 27, 2024 12:02
|
|
|
How generous is AMDs warranty process? I had a two month old 7800x3d keel over and die basically out of nowhere. I dropped my old 7600 in and it works fully fine now. Stock clocking settings, liquid cooled system that had no thermal problems. Not seeing and dead contact pads on the bottom nor is there any thermal muck.
|
|
#
?
Feb 27, 2024 15:54
|
|
|
DeathSandwich posted:How generous is AMDs warranty process? I recently rma'd my 2 year old 5950x (I've posted about its issues before) and it was fine. I explained what I'd tried, sent a pdf of my invoice and photo of the chip, got a prepaid shipping label, took a few days after they received it to get a new I'd obviously provided enough technical info in the ticket as no questions were asked about that
|
|
#
?
Feb 27, 2024 16:18
|
|
|
DeathSandwich posted:How generous is AMDs warranty process? Back when people noticed that Intel's fine print defines running XMP memory as "overclocking" and therefore out of warranty, gamers nexus did some anonymous trials to see if they could get a CPU warranty denied. In every case they were unable to get AMD or Intel to deny a warranty. Including when they boldly admitted stuff like "I was overvolting the CPU a lot, that's not covered by warranty right?" Nope, send it in, here's a new CPU. I think the safe conclusion is that DIY overclocking enthusiasts are a rounding error for these companies so they just replace stuff no questions. And the warranty restrictions on overclocking are more aimed at keeping OEMs from doing anything crazy. edit: also with the previous brouhaha over exploding x3ds I bet you could get a warranty replacement for a 7800x3d even if you were overvolting it with 120V AC.
|
|
#
?
Feb 27, 2024 16:20
|
|
|
I cannot imagine you'll have any trouble RMA'ing a 2 month old 7800x3d
|
|
#
?
Feb 27, 2024 17:02
|
|
|
BurritoJustice posted:A 9900K with tuned to the gills ram sits roughly in between a 5800X and 5800X3D in games. ...is it possible to learn this power?
|
|
#
?
Feb 27, 2024 17:15
|
|
|
forbidden dialectics posted:...is it possible to learn this power? Look at your mobos QVL RAM list, pick the highest validated speed you see on the list, crank up the voltage one notch past that and run tight timings. Every board's QVL list has some insane poo poo on there like running a 2400 kit at DDRR-4400 or faster at 1.6V or something.
|
|
#
?
Feb 27, 2024 17:27
|
|
|
Klyith posted:edit: also with the previous brouhaha over exploding x3ds I bet you could get a warranty replacement for a 7800x3d even if you were overvolting it with 120V AC. Electroboom/Gamers Nexus crossover?  Unrelated what would be the best AMD CPU for a NAS build these days? I was looking at the 8700G but seems like no ECC, I can’t decide if this is a dealbreaker. My previous cpu didn’t have it either (2500K).
|
|
#
?
Feb 27, 2024 17:37
|
|
|
BurritoJustice posted:That's the one, yeah.
|
|
#
?
Feb 27, 2024 22:39
|
|
|
priznat posted:Electroboom/Gamers Nexus crossover? I think DDR5 has error correcting baked in each module? Just not the interconnects between the module and the CPU?
|
|
#
?
Feb 27, 2024 22:50
|
|
|
A Bad King posted:I think DDR5 has error correcting baked in each module? Just not the interconnects between the module and the CPU? The important part of ECC is the reporting, and normal DDR5 does not have that.
|
|
#
?
Feb 27, 2024 22:58
|
|
|
It's kind of a travesty that (fast) ECC UDIMMs are still kinda bleh to get by, where as soon as the Zen4 Threadrippers were announced, companies like G.Skill et al hopped on the high frequency ECC RDIMM train for what's essentially a way more niche platform than people wanting to run ECC RAM in their regular desktop computers.
|
|
#
?
Feb 27, 2024 23:07
|
|
|
priznat posted:Electroboom/Gamers Nexus crossover? if you are just running it as a NAS with some light VM/Linux ISO Downloading work, you can go way cheaper than an 8700G. something like a 2500k.  i personally ran a 3770S for a number of years and was satisfied until i went to gigabit internet and I could actually fully saturate the CPU while downloading things over a WireGuard VPN.if you are running it as a Plex server, youre gonna probably want to use Intel 11th-gen or later to take advantage of QuickSync. AMD's encoder is not well liked and i believe is currently bugged with a desync issue. if you wanna go all in on AV1 though, intel wont have that integrated in the DIY sector until Arrow Lake later this year, so you are basically stuck adding an intel Arc/Nvidia dGPU just for encoding. im personally waiting to make the AV1 switch until later. x265 is pretty widely supported by end user devices so transcodes are limited, and the QuickSync x265 encoder is pretty speedy. Cygni fucked around with this message at 23:13 on Feb 27, 2024 |
|
#
?
Feb 27, 2024 23:10
|
|
|
A 1000 series Nvidia GPU if you can find one for free/cheap does a good job with transcoding as well!
|
|
#
?
Feb 27, 2024 23:13
|
|
|
A Bad King posted:I think DDR5 has error correcting baked in each module? Just not the interconnects between the module and the CPU? GDDR5 did it right and mandated full ECC support. Both specs were necessary because the speeds got so fast that bit error rate got above what JEDEC considered acceptable.
|
|
#
?
Feb 28, 2024 00:14
|
|
|
priznat posted:Electroboom/Gamers Nexus crossover? Using a 5600G here. Never felt like I needed ECC.
|
|
#
?
Feb 28, 2024 00:17
|
|
|
Craptacular! posted:Using a 5600G here. Never felt like I needed ECC. Every other form of storage in PCs already has ECC; the CPU caches all have it, as does both spinning rust and non-volatile flash storage (well, most of them use ECC because it's cheap to implement in hardware).
|
|
#
?
Feb 28, 2024 07:50
|
|
|
Even all (critical) buses in the system use some form of error correction. Basically everything except the goddamn RAM.
|
|
#
?
Feb 28, 2024 08:55
|
|
|
BlankSystemDaemon posted:This post is an excellent argument for ECC with MCE I'm not running production machinery here, but what started 15 years ago as a Windows Media Center DVR that added an old 32 bit ARM consumer NAS, now running VMs for storage and occasional services. That 'feeling' was more like an opinion from talking to plenty of people about it across multiple forums but sure just presume I'm being a clown.
|
|
#
?
Feb 28, 2024 09:20
|
|
|
Actual studies of memory errors* in giant-scale production environments have shown that uncorrelated one-off errors are uncommon. In a facebook study, about 2% of servers had a error per month. Half of the servers with errors are strongly predicted by other repeating errors -- ie hardware fault. (And of course hardware fault generates the vast majority of errors by absolute count.) ECC is definitely nice insurance, but as a home user it's good to think about the probabilities involved: How often will my memory have errors? A bit more than 1% chance per month that you'll have a spurious error somewhere in your memory, the cosmic ray bit-flip type event. And a little less than 1% that something in your hardware will start generating repeatable errors. How much of my memory is hosting critical data? On something like a NAS the answer is "not much". Your critical data is sitting on a drive. It only passes through memory when you're reading, writing, or the FS is doing scrubs or other maintenance. (And if you read but don't save, an error doesn't matter.) What does that mean? The chance that the unpredictable error strikes at just the right time and location to corrupt your data is low. For something like a home NAS, what you are worried about is the failure that generates frequent ongoing errors, because those make lots of errors. Now you have reasonable odds of an error hitting something you care about. Therefore, testing your memory on a regular (1-3 times per year) basis is pretty good protection for most home user purposes. Not absolute: get ECC if you're really paranoid, or if your home server is more than a home server. But it is well after stuff like offsite backups as far as data protection, and IMO unnecessary. Also if you spring for ECC memory on your NAS but not your desktop, and aren't doing those periodic memtests on the desktop, you probably have just as good odds of corrupting your data. *these studies are using ECC ram to see errors, but I see no reason the results would not apply to normal ram
|
|
#
?
Feb 28, 2024 15:26
|
|
|
Klyith posted:Actual studies of memory errors* in giant-scale production environments have shown that uncorrelated one-off errors are uncommon. In a facebook study, about 2% of servers had a error per month. Half of the servers with errors are strongly predicted by other repeating errors -- ie hardware fault. (And of course hardware fault generates the vast majority of errors by absolute count.) Another important element of the paper, if I remember it correctly (I haven’t read it in years and I only re-read the abstract and intro), is quote:non-DRAM memory failures from the memory controller and memory channel cause the majority of errors, which means that ECC wouldn’t even necessarily protect you AIUI. On the other hand, that was DDR3, and the susceptibility of DRAM to corruption increases in 5 (hence on-chip non-signalling ECC), right?
|
|
#
?
Feb 28, 2024 15:52
|
|
|
Klyith posted:Actual studies of memory errors* in giant-scale production environments have shown that uncorrelated one-off errors are uncommon. In a facebook study, about 2% of servers had a error per month. Half of the servers with errors are strongly predicted by other repeating errors -- ie hardware fault. (And of course hardware fault generates the vast majority of errors by absolute count.) All so that some PC clones could get a bit more money out of the purchasers.
|
|
#
?
Feb 28, 2024 15:53
|
|
|
I run ECC on my NAS because: 1) It greatly reduces the chance of outages due to soft errors. 2) It greatly increases the chance that I will notice if the RAM actually starts to fail before I start getting mysterious outages. 3) The cost increase vs. non-ECC DDR4 (which is the only downside of ECC) was only about $60 for 32GB, less than 5% of the total cost of the system after I include drives. I know that there are hypothetical benefits for file data integrity, but it's a distant fourth as priorities go - I expect ZFS to play a greater role there since file data spends a lot more time on the disk than it does transitioning through system memory. I have found ZFS to be very good at handling the aftermath of sudden outages, so to me the importance of this system's reliability is more about uptime and avoiding the work of recovery than avoiding data loss. Of course, if your data is all easily replaceable then this is even more true. On the other hand, if you are using something less resilient than ZFS then you might really want to avoid sudden outages. I think it's totally valid for a home user to not give ECC serious consideration, if your preferred platform doesn't support it (e.g. Intel) or if you aren't very concerned about the possibility of soft error outages. Soft error outages don't seem to be especially common in my experience even now that we are getting into the tens of gigabytes of memory, so that's fine. However, if your platform does support it then the cost is not bad. For that reason, I think it's a bit apples vs. oranges to say "you should have an offsite backup first" considering that could easily double the cost of the overall solution. You should have an offsite backup for anything critical or irreplaceable, but that is not most of the contents of many home NAS systems. I also don't understand the claim that it's comparably important to have ECC (or periodic testing) on your desktop vs. your NAS. It would be nice, sure, but a soft error on my desktop only affects me and maybe the data on its one SSD. Most of that data is Steam games and can be replaced in a heartbeat, and that which isn't easily replaceable is backed up... mostly to the NAS. The vast majority of the data on the NAS isn't even transferred through the desktop, I download it through VMs also hosted on the NAS. Eletriarnation fucked around with this message at 16:35 on Feb 28, 2024 |
|
#
?
Feb 28, 2024 16:04
|
|
|
and if you're talking about theoretical performance losses from going to ECC, even registered ECC ram has XMP and EXPO now. granted, DDR5 now properly silos off registered and unregistered RAM.
|
|
#
?
Feb 28, 2024 16:15
|
|
|
Subjunctive posted:Another important element of the paper, if I remember it correctly (I haven’t read it in years and I only re-read the abstract and intro), is ECC bits are kept over the bus, so yes true ECC would protect you from controller and bus problems. Otherwise it would just be the DDR5 form of ECC, protecting from errors on the module itself. Subjunctive posted:On the other hand, that was DDR3, and the susceptibility of DRAM to corruption increases in 5 (hence on-chip non-signalling ECC), right? Mostly the susceptibility to errors increases with density. I think DDR5 getting on-chip ECC wasn't really about the DDR4->5 transition, it just happens to be a convenient place where they could change the spec to mandate it. Which means late-generation high-density DDR4, where they fit 16GB on a single-side stick, is the worst case for uncorrelated memory errors. That may be the place where you have the most incentive to use ECC. (Or some old sticks of low-density ddr4 in your parts bin.) Eletriarnation posted:I think it's totally valid for a home user to not give ECC serious consideration, if your preferred platform doesn't support it (e.g. Intel) or if you aren't very concerned about the possibility of soft error outages. Soft error outages don't seem to be especially common in my experience even now that we are getting into the tens of gigabytes of memory, so that's fine. Good points, there's definitely a lot of personal priority stuff going on. To me a 1% chance to crash isn't really worth paying extra to avoid, even if I have to get up and walk to reset it. Repeated crashes because something went wrong -- such as the memory going bad -- are more annoying but eminently solvable problems. (Edit: I do agree that if the platform supports it, ECC is not a big splurge. But that's a big if, as we started this convo with "what's a lot-cost CPU that supports ECC?") Crashes are temporary, data loss or corruption is forever. My house burning down would suck for many reasons, and if that included losing everything I've ever done with bits it would suck worse. That's why offside / cloud is more important than ECC to me. Eletriarnation posted:I also don't understand the claim that it's comparably important to have ECC on your desktop. ... The vast majority of the data on the NAS isn't even transferred through the desktop, I download it through VMs also hosted on the NAS. Again, in my mind the thing that's important is personal and irreplaceable data. Whatever bullshit that I download from the internet isn't that. Some of it would be annoying to lose, but not important. If I'm editing a document or photo or whatever and it gets silent corruption in flight, that could easily become irreplaceable. That could happen just as easily on my desktop as my NAS (if I had a NAS).
|
|
#
?
Feb 28, 2024 16:56
|
|
|
Klyith posted:Your critical data is sitting on a drive. It only passes through memory when you're reading, writing, or the FS is doing scrubs or other maintenance. (And if you read but don't save, an error doesn't matter.)
|
|
#
?
Feb 28, 2024 20:35
|
|
|
Combat Pretzel posted:I know I keep harping on this one, but are we again ignoring that disk caching is a thing in this type of discussion? Personally, I've currently 52GB of (meta)data hot in RAM on my NAS. Ok. You got 00 on this month's roll of the d100, and now have a bit-flip error somewhere in that 52GB cache. For that error to matter, you would need to: 1) access the file containing the error before the cache gets refreshed or the machine reboots 2) use / modify the file and save it back to disk including the error 1 isn't that unlikely, the cache is full of stuff the machine thinks you'll use. But 2 needs a little thinking: Did the error strike a file you'll modify, or just a video you might watch? Does the file format have any independent checksumming / integrity / features that will make corruption obvious? Will the entire file be written back to disk whole? If you're working with a big file -- the ones most likely to be hit by the error -- you'll probably only write a portion back to the drive. A large file with data blocks like "ABCDEFGH" which I modify to be "ABCDEXGH", only the X and some bits of the E and G get modified on disk. If there was a memory error in A it doesn't matter. I know I keep harping on this, but is there any explanation for why ECC is super important that accounts for how constant file corruption is not a thing we observe on the zillions of PCs that don't have ECC? (And when you do see file corruption it is generally paired with non-mysteries like a drive that has bad sectors all over.)
|
|
#
?
Feb 29, 2024 03:06
|
|
|
Especially with desktop systems, running overclocked RAM pushing the limits of stability, I am not convinced RAM errors are that rare. All the studies have been of servers running ECC in-spec. Even when the RAM itself is fine the memory controller can be unstable, and that can pass memtest for extended periods. I made the questionable choice of going with 4x32GB ddr5 this time around and even with BIOS updates I got ~weekly corrected errors (across all sticks) as low as 4400mhz and was able to pass short memtest checks at 4800. While I'm pushing the capacity that Zen 4 is willing to tolerate, I assume a lot of these just-barely-stable overclocks with two DIMMs are also not actually that stable on the memory controller side. I've also had two DIMMs go bad after multiple years of stability even without overclocks. One of those was ECC which was at least easier to conclusively narrow down.
|
|
#
?
Feb 29, 2024 13:04
|
|
|
I grabbed a 5700x on sale this weekend so I could throw my 5600 into a new build for my girlfriend who's laptop just randomly died. I chucked some DDR4 I had in a spare machine my kid uses occasionally in there, but need to replace that at some point, and was considering grabbing something faster than the cheap 32gb 3200 kit I have in my PC and passing that on to her too. The TridentZ Neo 3600 kit seems pretty heavily recommended, but I'm wondering if there's anything quicker I should be looking at, as I plan on sticking with this 5700X setup for another year or two at least. DDR4 being cheap atm, it might be a good time to snap up something higher-end. I know conventional wisdom used to be that 3600 was the sweet spot for Zen 3, but my experience in the past has been that older platforms can get a big late-life boost from tricked out RAM...
|
|
#
?
Mar 11, 2024 02:45
|
|
|
depending on how good your chip's memory controller is, after 3800 you likely have to set the FCLK to 2:1 (async) mode which will hurt performance. You might be able to downclock retail 4000 MT/s ram to 3800 (use the same T values as 4000 if you want to be safe), but 3600 will work virtually 100% of the time and sets are actually sold for that costing barely more than 3200 kits. Kits with a preset 3800 profile are extremely rare and were probably only sold in number when Zen 2 was coming out.
Anime Schoolgirl fucked around with this message at 04:56 on Mar 11, 2024 |
|
#
?
Mar 11, 2024 04:19
|
|
|
priznat posted:Electroboom/Gamers Nexus crossover? used EPYC. you can get combo deals like $500-800 for MB/16 core CPU/ECC RAM. They're older, and vulnerable to some local information leak exploits but you're not selling timeshares like AWS so it's not an issue. If there's malicious code running on your server it's already game over. 7402p is pretty cheap and performant Just remember that EPYC part numbers read backwards because ... gently caress it, I have no idea why. An epic coke budget for the marketing department? The last numeric digit is the generation, so a 7501 is worse than a 7402. https://www.cpu-world.com/info/id_model/AMD-server-conventions.html DO NOT BUY A BARE EPYC CPU. ONCE OUT OF A MOTHERBOARD IT IS BRICKED There's dogshit vendor-locking by blowing fuses inside the chip. As soon as you put it in a board it's hard-locked to that manufacturer. And if the manufacturer key is "facebook" nobody else can ever run them. They claim it's for "security" on supply chain attacks but that's a lie. It's entirely about making them e-waste and killing the secondary market. Harik fucked around with this message at 07:17 on Mar 14, 2024 |
|
#
?
Mar 14, 2024 07:11
|
|
|
If I am looking to jump into AM5 from a i9 10850k. Would it make sense to save some cash and go for a 7600x instead of 7800x3d? My other specs RX 7800 XT Resolution is at 3440x1440
|
|
#
?
Mar 14, 2024 09:39
|
|
|
Harik posted:DO NOT BUY A BARE EPYC CPU. ONCE OUT OF A MOTHERBOARD IT IS BRICKED a. It is a maybe, not an always. If the feature in the previous motherboard was turned on the CPU is locked, but that depends on the vendor & operator. (I still wouldn't buy a used bare epyc, at least not from anywhere I wasn't 100% sure if I could get my money back.) b. It really is for security. UEFI firmware attacks are real, they have been caught in the wild, and experts don't even know how prevalent they are because they're so hard to detect. They're very much in the state-level zone where the only people who have to worry are important targets, but that describes people who buy a lot of server CPUs. And the only way to protect against it is keys in the CPU that can prevent unsigned UEFI from loading. The other option is Intel Boot Guard, where there is a permanent key in the CPU. That has potential weakness to the whole ecosystem if the private key gets out -- and exactly that happened when MSI got a bunch of poo poo hacked. AMD's method is more secure because a huge operator like facebook can make their own key pair and not worry about some other company's poor security. Green Gloves posted:If I am looking to jump into AM5 from a i9 10850k. Would it make sense to save some cash and go for a 7600x instead of 7800x3d? Yes, if you think you might upgrade the CPU next year when there's a newer and better x3d out. Or if $150 is dear to you. A 7600X is still a pretty good CPU. No, if you want to put a box together and let it ride for 4 years. (Also there are rumors that Zen 6 will still be on AM5, so even 4 years from now you may have a decent upgrade path.)
|
|
#
?
Mar 14, 2024 13:33
|
|
|
|
| # ? Apr 29, 2024 08:33 |
|
|
Klyith posted:a. It is a maybe, not an always. If the feature in the previous motherboard was turned on the CPU is locked, but that depends on the vendor & operator. (I still wouldn't buy a used bare epyc, at least not from anywhere I wasn't 100% sure if I could get my money back.) It's not about security, any state level actor who can replace the firmware in a supply chain attack can afford to throw in a new epyc that immediately locks to their key. The proper way to do it is to have a OTP region/256 efuse bits on your flash chip that the processor reads first. It's less secure than doing it properly, because a physical supply chain attack now only has to replace a designed-to-be-removed processor instead of bringing in the full suite of SMT rework tools to remove a ROM from the board. One of these things you can do in a few unattended minutes, the other you can't. Serial flash chips with OTP already exist for doing exactly this kind of thing: https://www.macronix.com/Lists/ApplicationNote/Attachments/1898/AN0218V1%20-%20Serial%20Flash%20Secured%20OTP%20Area%20Introduction.pdf https://www.infineon.com/dgdl/Infineon-AN98515_Using_OTP_Regions_in_S25FL-P_SPI_Multi_I_O_Flash-ApplicationNotes-v04_00-EN.pdf Doing the way they did is 100% about killing the secondary market using "security" as an excuse. I still buy EPYC for my work servers but I'm not going to pretend this isn't a super dick move on AMDs part.
|
|
#
?
Mar 14, 2024 15:16
|
|