Cases Montech HS01 Pro & HS02 Pro Case Review: Thermal Benchmarks, Build Quality, & NoiseMay 1, 2025Last Updated: 2025-05-01We put Montech’s new Montech HS01 and HS02 cases through a variety of benchmarks that include thermal performance, acoustics, and tests for build qualityThe HighlightsThe HS02 Pro is a fishtank-style case with a curved cornerThere are many ATX cases that can compete with the HS01 on the marketWhat makes the cases interesting is that they can easily invertOriginal MSRP: $130 (HS01 Pro with fans), $140 (HS02 Pro with fans)Release Date: April 2025Table of ContentsAutoTOC Visit our Patreon page to contribute a few dollars toward this website's operation (or consider a direct donation or buying something from our GN Store!) Additionally, when you purchase through links to retailers on our site, we may earn a small affiliate commission.IntroWith removable feet that can be swapped from the top to the bottom, Montech has 2 new cases that can quickly invert. Those two cases are based on the same chassis: They are the Montech HS01 Pro and HS02 Pro cases, differentiated by the glass or mesh, and each includes 5 fans.Editor's note: This was originally published on April 30, 2025 as a video. This content has been adapted to written format for this article and is unchanged from the original publication.CreditsTest Lead, Host, WritingSteve BurkeTesting, WritingPatrick LathanCamera, Video EditingVitalii MakhnovetsCameraTim PhetdaraWriting, Web EditingJimmy ThangMajor points of interest include the recessed motherboard tray, ventilated rear chamber cover, and abnormal power supply location up in the front. It’s not all good news, however. The power-supply area has some ventilation problems we’re not happy about, but there are some mechanical upsides. The rear fans remove as a single piece without becoming a proprietary nightmare, which is a welcomed feature. The case tries to plan around back-connect boards, running into the chicken-or-egg problem that both boards and cases are facing.As always, we have some critiques of the case, but we were also overall happy with its build quality and assembly. The cases land at $130 to $140 with fans or $100 to $110 without them. SpecsModel NameHS01 PROHS02 PROColorBlack / WhiteBlack / WhiteDimensions(L*W*H) 480*235*368mm (Case) / 563*323*573mm (Carton)480*235*368mm (Case) / 585*334*532mm (Carton)MB SupportATX /Micro-ATX / Mini-ITX (Back-Connected MB Supported)ATX /Micro-ATX / Mini-ITX (Back-Connected MB Supported)Front I/OUSB3.0*2 / Type-C*1 / Mic*1 / Power Button / Audio*1 / LED Button*1USB3.0*2 / Type-C*1 / Mic*1 / Power Button / Audio*1 / LED Button*1PCIe Slots77Compatibility / MaximumCPU Cooler 170mmGPU 400mmPSU 200mm ATX / SFXCPU Cooler 175mmGPU 420mmPSU 200mm ATX / SFXDrive Support / Maximum3.5” HDD 22.5” SSD 43.5” HDD 22.5” SSD 4Pre-installed Fan(s)Bottom 120mm*3Rear 120mm*2Bottom 120mm*3Rear 120mm*2Fan SupportTop 120mm*3Front 120mm*3 / 140mm*2Bottom 120mm*3Rear 120mm*2Top 120mm*3Bottom 120mm*3Rear 120mm*2Radiator SupportTop 120 / 240 / 360mmBottom 120 / 240mmRear 120mmTop 120 / 240 / 360mmBottom 120 / 240mmRear 120mmDust FilterBottomBottomEAN4710562747621 / 47105627447124710562741377 / 4710562745719Warranty1 Year1 YearSpecs copied from manufacturer materials, please read review for our own measurements and opinionsThe BuildMontech is probably best-known for its King 95 chassis. The company has had some hits and some misses since it started, but the HS01 and HS02 blur the lines between a more traditional case and a dual-chamber case.The big marketing play is toward inversion. Cases have inverted in the past, but some of the original invertible cases we covered were difficult to flip around and required dozens of screws.Modern invertible cases, like the be quiet! Light Base series, have made this process way faster.Inversion is the headlining feature of the HS cases, and the process is extremely easy. The top cover moves to the bottom, the bottom filter and legs move to the top. That's it. The process is optionally toolless: the legs are magnetic, but they can also be screwed into place when the case isn't inverted. The main downside of making the process so simple is that aspects of the case which are designed to work right-side-up aren't altered at all in the inversion process, so the side panels and rear fan bracket are installed upside-down when the case is inverted and the PSU power switch becomes inaccessible. Other aspects of case configuration are also easy to deal with. The top panel is magnetic and pulls off easily. The company uses a rubber/fake leather strap at the back. The rear two-fan bracket comes off as a single unit (which we liked), and the rear expansion slots rotate vertically with minimal effort. Removing the top panel gives immediate access to the PSU switches (like power and eco mode), as well as the RGB hub connections in Pro variants.The HS02 has what Montech calls "an 8° Curved Glass front pane." It’s not 8 degrees -- it’s 90, so maybe they meant the radius of the bend was 8mm. The media kit came complete with an illustration of the corner with an 8° label though. Either way, the bend is, in fact, 90 degrees in total, and the front panel butts up against the side panel to look (sort of) like a continuous pane, similar in some parts to the King 95. It's not as impressive as the HAVN HS420 (read our review), but it's definitely less expensive. The glass panels are beveled where they meet the angled plastic pillars for a flush fit.The chassis design strikes us as being optimized for back-connect boards. Back-connect boards have gotten some traction, but they aren’t a significant portion of the market yet. Case makers have a challenge: It's too early to prioritize back-connect at the expense of compatibility with normal boards (unless marketing specifically for a back-connect board), but also, not building for it at all means no adoption of change.The motherboard and fans have what Montech describes as a "sink-in design," meaning that ATX or even mATX boards are surrounded by metal on all sides. As a consequence, it's difficult to reach board connections with normal motherboards (which is most of them): for example, we were forced to use the stock flat EPS12V cables for our SilverStone PSU because our custom-sleeved CableMod replacements couldn't cleanly fit. Routing the 24-pin cable required an uncomfortable bend, and fitting the USB headers into place was nearly impossible. There's no good route for the GPU power cable either, although that's a common issue with open-bottomed cases and not specific to Montech.The PSU area leaves a lot to be desired: Unfortunately, we end up with 3 layers of blockages from the PSU case mesh, the interior cover door mesh, and the exterior panel mesh. The two case panels overlap and obstruct each other, which already overlap with the PSU ventilation. Stacking 3 layers atop each other reduces flow and increases resistance, which can increase noise or minimally reduce cooling. Fortunately, PSUs tend to be less thermally sensitive, but we’d like to see fewer overlapping obstructions.With the PSU fastened down, we found our normal SilverStone PSU pushed the cover up without screws to hold it in place, which we added.The PSU mounting bracket can be rotated to mount either a standard ATX or a smaller SFX PSU; this bracket then slides into place and is screwed to the top of the chassis. There's no particular reason to use an SFX PSU with this case. The extension cable that runs from the rear of the case to the bracket at the front must be routed through the bracket before it's installed.This is mostly an air cooling case, which is how we’re testing it. Radiator support is restricted, though. The front of the HS02 obviously doesn't support radiators since there are no mounts, but even in the HS01, the PSU placement overlaps with the front fan mount. That means there's only space for mounting on the outside of the chassis, and only normal 25mm thick fans fit (no radiators and no extra-thick fans). At the top of the case, Montech claims support for radiators up to 123mm wide, which is a strict limit due to the bumps on the ATX PSU bracket that pokes through, leaving small bumps to interfere with clearance. The bottom mount works fine for radiators other than obstructing the bottom edge of ATX boards, but Montech (correctly) doesn't claim compatibility above 240mm due to the cramped space. There's no 140mm-wide radiator compatibility in either case, and only the HS01 has support for any 140mm fans.Generally speaking, we don't like all the plates and covers and brackets that Montech has stuffed into the HS01 and HS02. They hide some cable clutter, sometimes at the cost of thermals, but most clutter would be invisible behind the steel side panel anyway. There are times where we like this type of feature, but with this case, there are already tradeoffs in the depth and the accessibility for some connectors in some areas. Sacrificing more of that for the metal plates can sometimes work against it. Even still, cable management space is generous, but we'd happily trade some of that space for better access to normal motherboard connectors and some small clearances in the main chamber.Moving on to the hardware: Cases generally include a set of "SSD" screws for attaching 2.5" drives. The HS01 and HS02 do not, however: as the manual notes, every screw included in the accessory kit is 6-32 TPI. The cases claim compatibility with up to four 2.5" drives, so the screws are a strange omission. It’s not a big deal to bring your own screws, but not standard for a case to cut this corner.The front panels of the HS01 and HS02 aren't directly interchangeable since there are some differences to the support structures, like the support corner pillar in the HS01 and some plastic trim in the HS02 that’s not on the HS01. This was inconvenient for our testing, but it's unlikely to ever come up from a customer perspective, so it doesn’t matter much unless you wanted to swap it later.All variants include ARGB lighting strips at the bottom of the case, with the Pro cases also including ARGB fans and a built-in controller. The fans use separate (standard) connections for ARGB and fan control, which we generally prefer, but it does lead to a confusing mess of wires. If you've bought into one of the proprietary RGB ecosystems, the Pro cases really aren't the best for working with that.  Thermals Grab a GN15 Large Anti-Static Modmat to celebrate our 15th Anniversary and for a high-quality PC building work surface. The Modmat features useful PC building diagrams and is anti-static conductive. Purchases directly fund our work! (or consider a direct donation or a Patreon contribution!)The Pro variants ship with fans and the non-Pros do not, so all stock tests shown here represent Pro performance. We tested the HS01 stock and inverted, but Montech's marketing materials push the "natural airflow" chimney effect angle, so by that logic, inverting the case without rearranging the fans should lead to worse performance. We'll see.CPU Full Load Thermals - Noise-NormalizedWe’ll start with noise-normalized CPU thermals, which means we use our hemi-anechoic chamber in the lab to collect highly controlled noise data for comparison.Inverting the case didn’t produce a significant change. The HS01 Pro ran at about the same temperature in both tests. The glass panel versus mesh panel also had minimal impact.The stock fan layout is the same in both cases, meaning that the HS01's mesh front won’t do much unless the fans are re-arranged; if anything, it could allow some air to escape where we’d rather keep it in. The CPU averaged 49 degrees Celsius above ambient in the HS01 Pro, 52 degrees on the P-cores, and the results for the inverted HS01 and for the HS02 were within the normal range of variance. The fans were run at slightly different speeds in each of the three configurations to hit the 27 dBA threshold, which is where the chamber comes into play (as we can actually measure those tiny acoustic differences now), but that wasn't enough to make a difference thermally.Montech's own moderately more expensive King 95 Pro with a glass front beat the HS cases in this test with an average of 47 degrees above ambient. The Antec C8 ARGB (read our review) is also more expensive, but it has relatively weak CPU cooling with the stock fan layout, and the HS cases beat it by 1-2 degrees. More traditional designs like the Lancool 207 (read our review) and 216 (watch our review) fly past the HS01 and HS02, setting a ceiling and giving perspective on cooling. The G400A (read our review) also accompanies these two.GPU Full Load Thermals - Noise-NormalizedThe range for the GPU thermal results was just as tight, with the inverted HS01 averaging 42.8 degrees above ambient and the HS02 averaging 43.2, which is within variance, but that’s still not even one full degree of difference. It's not a surprise that the chimney effect isn't a factor when active airflow is involved, nor is it a surprise that changing the front panel has no impact when there aren’t any fans installed at the front of the case.Although the different configurations didn't make much difference, the HS cases performed well overall for GPU thermals, respectably close to the C8 ARGB's 42 degree average. Like the C8, the HS cases have bottom intake fans that force cool air directly into and through the GPU and with minimal obstruction beyond a dust filter. The King 95 Pro also has bottom intake fans, but they're less effective, resulting in a 48 degree average. The Flux Pro and Lancool 207 remain leaders here, but one is in a different price class and both are different styles.GPU Full Load Thermals - Full SpeedFull speed case fans are next, dropping the noise control and testing GPU thermals.At full speed, we can finally see a difference between at least the regular and inverted HS01 results, with the inverted layout averaging 40 degrees above ambient to the regular layout's 42 degrees above ambient. The bottom intake fans move enough air that flipping them to the top of the case where they can breathe more freely is beneficial. The inverted layout also directed slightly more noise towards our mic placement, but not enough for an audible difference at 38.5 versus 38.0 dBA. The regular HS02 result closely matched the HS01 result at 42 degrees, but the HS02 was quieter (as measured from the front) due to its solid front panel blocking noise egress. The drop to 35.8 dBA is noticeable, if barely. However, remember that at the 27 dBA threshold performance and noise levels were both equal.As before, the Antec C8 ARGB's GPU cooling is on par with the performance of the HS cases at 41 degrees above ambient, with noise levels equivalent to the HS01. The King 95 also averaged about 37 dBA, but with worse GPU thermals, averaging 46 degrees.CPU Full Load Thermals - Standardized FansOur standardized set of fans can't be installed in the HS02 due to the lack of 140mm mounts, which made this test simple. We installed the two 140mm intake fans at the front of the HS01 and the single 120mm exhaust in the lower of the two rear slots.With this layout, average CPU temperature was 41 degrees above ambient and 45 degrees for the P-cores. For this case specifically, those are lower than the stock results, but that's not surprising given the more direct airflow aimed at the CPU cooler. It’s also completely normal performance for a mesh-fronted case in this test, landing between the Fractal Meshify 2 Compact (watch our review) and Phanteks P400A Digital (watch our review). The Antec C8 and King 95 Pro results on this chart were both tested with side intake, so performance is predictably worse than the HS01.GPU Full Load Thermals - Standardized FansOn the other hand, moving to the normal front-to-back layout with the standardized fans hurt GPU thermals. Removing the stock bottom intake fans that made the HS01 competitive in this category led to an average GPU temperature of 45 degrees above ambient, which isn't terrible, but allowed the King 95 Pro and C8 ARGB to take the lead at 43 degrees for both. Montech's stock fan layout seems like the best compromise.VRM & RAM Full Load Thermals - Noise NormalizedTo finish things off, we'll move back to the noise normalized testing. VRM thermals were nearly identical for each of the three tested configurations, averaging 33 degrees above ambient in the HS02 Pro, which lands the HS cases in the middle of the chart between the C8 ARGB at 33 degrees and the King 95 Pro at 31.The SPD Hub sensor readings from the RAM told a similar story: all three configurations averaged close to 25 degrees above ambient, close to the C8 ARGB's 24 degree average, although the King 95 Pro scored well in this specific instance at 21 degrees.ConclusionGrab a GN Soldering & Project Mat for a high-quality work surface with extreme heat resistance. These purchases directly fund our operation, including our build-out of the hemi-anechoic chamber for our acoustic testing! (or consider a direct donation or a Patreon contribution!)Montech's strength has always been in the budget space. The Montech HS01 Pro and HS02, however, are sort of in that mid-range category with their prices. The recent tariff situation is obviously going to affect that market. Montech contacted us to confirm MSRPs a few days prior to launch, so hopefully these prices will stay stable for some time.As a fishtank case with a curved corner, the $140 HS02 Pro is a reasonably priced alternative to the more expensive cases that match that description like the HAVN HS420, Antec C8 Curve, HYTE Y60 (watch our review), or even Montech's own King 95 Pro. We seriously recommend watching the build section of our video review, because there were some features we didn't like, but it's up to you to decide whether the savings are worth it. If you use a back-connect motherboard, that may solve many of the issues we saw, including with cabling.The HS02's thermal performance wasn't abysmal or amazing. It was fine. Of these two cases, we're more willing to accept middling performance from the one that looks interesting, in other words, the glass-fronted option. The HS01 has greater cooling potential thanks to its mesh-front panel, but it's also more generic: there aren't a ton of fish-tank cases that can compete with the HS02's price, but there are many, many $100-$150 mesh-fronted cases that can compete with the HS01. These include options like the Lian Li Lancool 207, Fractal North (watch our review), Phanteks G400A, or many of the other cases we've reviewed in the past couple years are all viable alternatives to a mesh-fronted case. There’s a lot of competition at that price class. If you love Montech’s case here or really like how it looks, we can say “it’s fine.” We do think the fish-tank version makes a little more sense for most people. If you really want a mesh case, there are better alternatives.

GPUs Get It Together, NVIDIA | Terrible GPU Driver StabilityApril 14, 2025Last Updated: 2025-04-14We investigate whether NVIDIA’s new drivers are behind the recent GPU instability issuesThe HighlightsWe read through numerous user reports and set forth to replicate NVIDIA’s stability problemsNVIDIA has major driver instability problems right now, and that impacts newer RTX 50 series cards as well as RTX 40 and 30 series GPUsWe found issues with setups using DLSS4, frame generation, G-Sync, and even just the monitor ports in a multi-monitor setupTable of ContentsAutoTOC Grab a GN15 Large Anti-Static Modmat to celebrate our 15th Anniversary and for a high-quality PC building work surface. The Modmat features useful PC building diagrams and is anti-static conductive. Purchases directly fund our work! (or consider a direct donation or a Patreon contribution!)IntroHow the tables have turned. NVIDIA, is now playing the role of AMD circa Vega, which is not good. NVIDIA’s drivers have had stability problems since the launch of its RTX 50 series GPUs and we’ve been able to replicate them.In one game, we had system crashes after enabling NVIDIA’s frame generation, which is unfortunate since it marketed the 50-series on the back of MFG and fake frames. We had reboots loading into Cyberpunk, crashes and driver errors in Tomb Raider, and issues with screen distortion and artifacting.Editor's note: This was originally published on April 6, 2025 as a video. This content has been adapted to written format for this article and is unchanged from the original publication.CreditsTest Lead, Host, WritingSteve BurkeCamera, Video EditingVitalii MakhnovetsTesting, Writing, ResearchTannen WilliamsWriting, Web EditingJimmy ThangBut these issues didn’t show up in our review of the 50-series, which was our first hint that it’s related to a driver version issue. Game developers have recently begun recommending rolling back to older NVIDIA drivers: inZOI, the studio which NVIDIA has heavily promoted for partnership with its AI features, threw NVIDIA under the bus, stating, “Using driver versions 572.xx or later may result in occasional frame drops or stuttering [...] If issues persist, we recommend installing version 566.36.” This driver is from December. Developer Neople stated, “Using driver versions 572.xx or later may result in occasional frame drops or stuttering.”This aligns with our findings from the past week, where we’ve been trying to replicate these issues that have been widely reported online. Interestingly, we found that the order of the monitors in Windows, as in the display out order of monitor 1 and monitor 2 in the OS via the actual hardware connection to the video card, seemed to affect stability. User reports commonly note various display problems like black screens, flickering, and sometimes even unprompted system reboots and crashes to desktop. This includes other types of crashes too, like crashing to desktop. Upon a closer inspection, it wasn’t only 50-series users dealing with the issues. Many users of NVIDIA’s previous generations of GPUs, particularly the 40 and 30 series, are also affected by the recent drivers. Several users speculated on the impact of multiple monitors, the impact of mixed or higher refresh rates, and even how NVIDIA’s own G-Sync might be affecting the driver stability. There’s been at least one megathread on Reddit with hundreds of reports and these issues have been in the news since the launch of the 50-series. We’ve been able to replicate these issues and have isolated some of the causes. We also have some stopgap solutions. They’re not great, but may help for the time being. This also applies to multiple card generations. As far as we know, it impacts the 30 to 50 series GPUs.  User reports seem to point to driver 566.36 as the most stable recent driver. This version was released on December 5th, 2024, just prior to the 50 series launch in January. In the four months since that driver’s release, NVIDIA has posted six GeForce Game Ready Drivers and at least four GeForce “Hotfix” Drivers specifically aimed at fixing bugs and system crashes.Testing ConfigurationTime to get into our testing configuration.In order to better understand the driver problems that previous generation NVIDIA users are currently experiencing, we attempted to recreate some of the issues ourselves. Before we began, we went through an assortment of user reports to find games, system configurations, and specific settings that seemed especially problematic to get a starting point for our testing.For our testbench setup, we used a modified version of our standard test bench. We also bought a couple games that people had particular issues with. Our standard GPU review bench did not exhibit any of the issues with drivers initially, so we modified it.Components included these:CPU: 9800X3DGPU: 4070 SuperMonitors: Dual-monitor setup using an Acer 4K 60Hz monitor (not G-Sync compatible) and a Dell Alienware 1080p 360Hz monitor that is G-Sync compatible, which we ran at 240Hz. Both were connected via DisplayPort. And this part is important: In Windows, we manually set the monitor order:Monitor 1: Acer 4K displayMonitor 2: Alienware monitor, which was checked as the main display in the Windows settings). Motherboard: ASUS ROG X670E HeroRAM: 2x16GB (32) of DDR5 6,000Mhz Trident Z5PSU: EVGA 1600 T2Driver version: We used 572.83 initially as it was the most recent when we began our testing, which was released on March 18th, 2025So we have a very intentional mix of different resolution displays, different G-Sync compatibility, different refresh rates, and, of course, we’re going to change the drivers as we go through our testing.Our first goal was to simply identify a game crashing. From there, we’d recollect what occurred leading up to the failure and then document a process that we could follow to ensure the crash happened every time. Once we were able to consistently reproduce the complication, we’d change one variable at a time while keeping all others the same in order to isolate the factors involved and determine possible causes. For each instance, we separately disabled G-Sync, frame generation, DLSS, and sometimes other settings (depending on the game). We also moved to a single monitor and then swapped output ports on the GPU between the two monitors for each game issue we experienced. Suffice it to say, this all took a while.Broad Findings Grab a GN Tear-Down Toolkit to support our AD-FREE reviews and IN-DEPTH testing while also getting a high-quality, highly portable 10-piece toolkit that was custom designed for use with video cards for repasting and water block installation. Includes a portable roll bag, hook hangers for pegboards, a storage compartment, and instructional GPU disassembly cards.Here’s what we found:In our testing on NVIDIA’s most recent driver, 572.83, we found four different instances of game crashes that could be consistently reproduced. In Star Wars Outlaws, we experienced failures after selecting “resume” in the startup menu. In Marvel Rivals, we’d observe system reboots either directly after applying frame generation in the pre-menu settings, or after applying the settings and then exiting to desktop from a match. In Cyberpunk 2077, we encountered reboots when loading into the game. In Shadow of the Tomb Raider, when running the in-game benchmark we faced a game crash along with a driver error. After rolling back to a previous driver, we could no longer replicate any of these same failures on any of these games. And that’s the reason this took a week or 2 to put together because we tried to isolate to see if it was a game problem, something relating to NVIDIA, or NVIDIA settings in that game.Based on our initial findings, we believed the driver issues may be affecting some users that are operating on a specific combination of hardware and displays/graphics settings. Specifically, those using two monitors with G-Sync and frame gen enabled. We also found something really interesting regarding the physical output ports on the GPU itself and how the monitors are identified in Windows display settings. We don’t fully understand it yet, but we’ll go over that observation shortly.We have more findings to go over first.Less Conclusive FindingsDLSS and Reflex may also factor into the equation, but unfortunately we weren’t able to make a clear determination. In some games, DLSS or Reflex is automatically enabled when using frame gen. Meaning, we weren’t always able to fully isolate each of these variables because one will force the other. Additionally, sometimes lowering the refresh rate to 120Hz on our second monitor would resolve issues, while other times it didn’t. Something that especially stood out to us was that we could only replicate 3 of the 4 failures when both monitors were connected via DisplayPort and when monitor 2 was checked as the main display in Windows settings. As seen in the image above, when our Acer monitor was plugged into what we’re calling slot 3 and our Alienware monitor was plugged into what we’re calling slot 2, we didn’t have any issues. But when we swapped the slots the monitors plugged into, effectively converting “monitor 1” to “monitor 2” within Windows and vice versa, and then made monitor 2 the main display, we saw the crashes again consistently. This is less to do with the physical ports being used and more to do with how Windows and the drivers are treating the monitors in their “1” and “2” slots. We couldn’t tell you why this behavior causes issues, but if you’re having trouble, swapping monitors 1 and 2 could potentially help.We actually found this by accident. The day after we recorded our first game crash, we reconfigured the bench and began trying to trigger it again, but couldn’t. It wasn’t until we realized that the only difference was that the DP output slots on the GPU had been changed. After switching them back to the original position, we were suddenly able to observe the failure again. To our surprise, this same circumstance appeared in multiple games.Game CrashesAs for similarities between the issues: In Star Wars Outlaws, Marvel Rivals, and Cyberpunk 2077 (all games that natively support DLSS 4), we were unable to produce a failure when either G-Sync or frame gen were disabled. We also separately couldn’t trigger a crash after swapping output slots or on a single monitor setup.DLSS 4 and frame gen are also problems here. It’s not just the monitor order or the monitor ports.The error in Shadow of the Tomb Raider was different from the games previously discussed. This game was unaffected by G-Sync. It also doesn’t feature a frame gen setting (at least the version we tested doesn’t). Additionally, it experienced the same failures on a single monitor and after swapping output slots. So none of the other issues we’ve talked about thus far were the cause for Shadow of the Tomb Raider.Instead, we were able to boil this problem down to having “RTX Shadow Quality” set to Ultra in the in-game settings. And we know for a fact that this didn’t always cause a crash because we have run tests on it with RTX Shadow Quality set to Ultra in prior versions of our benchmark suite with different drivers. In regards to our analysis, the main commonality between all four of these games is that they crashed on NVIDIA’s most recent drivers at the time of testing, but after rolling back to 566.36, we were no longer able to trigger that same error. Rolling back to driver version 566.36 doesn’t guarantee that crashes will stop. From what we’ve read online, there are still issues with that driver. In our case, we are unable to prompt the same failures we had previously been able to. This, along with various user reports, seems to suggest that driver 566.36 is currently the most stable driver that NVIDIA has released recently. 566.36 is from December and predates the launch of the RTX 50 series, so would not be compatible with 50-series cards.There are a lot of other issues reported online, but that’s what we’ve replicated so far.Many users saw problems in games that didn’t occur until after multiple hours of gameplay. As much as we’d like to, we can’t spend several hours playing a random game to see if it will possibly crash. It’s just too unpredictable. On the same note, just because we weren’t able to repeat our failure when we turned G-Sync or frame gen off, doesn’t mean that turning these options off will solve all problems, but hopefully it’ll help some of you.Other Common IssuesThere were some other issues we commonly saw in our research:We’ve seen multiple reports that there’s an issue with waking from sleep or resuming from idle states and we were able to create at least one of these by accident. We noticed on one of our personal PCs that there were issues waking the system from sleep when the PC had been idle. And on wake, the monitors appear to turn on but don’t receive any signal and the screens remain black. Fixing this required a PC reboot. Windows has its own decades of issues with sleep and S3 states, so it’s hard to specifically pinpoint who’s at fault for this one between NVIDIA and Microsoft.Another issue we’ve seen going around has to do with the alt+tab shortcut acting buggy and freezing games when switching windows while playing a game. We did occasionally encounter this bug, but it wasn’t something we saw every time and seemed to be resolved pretty easily by pressing the Windows key or alt+tabbing back into the game. Again, this one is difficult to pinpoint between NVIDIA and Microsoft. NVIDIA Driver NotesNVIDIA has had some driver notes addressing parts of this, despite the driver not fixing everything.In NVIDIA’s 572.83 driver release notes, one open issue states, “[Cyberpunk 2077/Half-Life 2 RTX] PC may bugcheck with error 0xd1 when playing game while using DLSS Frame Gen + G-SYNC [5144337].” We’re glad that issues relating to frame gen and G-Sync are being acknowledged, but we’d like to see more from NVIDIA here. This is a relatively vague description and only mentions two games that are affected by this much larger issue. NVIDIA has also had multiple hot fixes. We’ve reported on some of them where it’s saying it’s trying to fix issues with the original 50 series and then just basically everything. Suggestions for Those AffectedWe’ve known that NVIDIA has shifted its focus towards larger business clients and away from its gaming market. That’s fine -- but it shouldn’t be screwing up areas where it has long had such refinement. NVIDIA is known for its driver stability, and the company, in its series of screwups for 2025, is starting to chip away at that in an era where AMD’s drivers have become relatively stable. These driver issues are another mark upon NVIDIA’s tarnished gaming reputation with the 50-series launch as the company shifts focus, but losing prior-gained ground shouldn’t be in the cards, and NVIDIA hopefully will recognize that these issues are damaging to its long-term brand credibility.We’ll end off with some suggestions for users experiencing issues:For non-50 series users who are confronted with game crashes on NVIDIA’s latest drivers, we’d first recommend swapping the order of your display outputs on the GPU itself. We don’t fully understand how effective this fix is yet, but it’s simple and worked for us. We’d also suggest swapping cables to HDMI, which is not ideal, to see if that changes anything as a stopgap.If you don’t feel strongly about G-Sync or frame generation being enabled, we would then suggest disabling one of those settings and see if you’re able to resolve the issue that way until NVIDIA is able to get its s*** together. Considering NVIDIA’s whole marketing gimmick lately has been frame generation, this is a bad solution for NVIDIA, but hopefully it’s a stopgap.If neither of the above work for you, our last suggestion would be to rollback to a previous driver. If you’re able to recall a specific driver that you previously used that didn’t cause any problems for you, we’d advise reinstalling that one. In our case, 566.36 seemed to remedy our problems and seems to be shared by users as one of the more stable ones currently available. As general process control, we’d recommend installing drivers directly from NVIDIA’s website and disconnecting from the internet for installs and uninstalls. We always uninstall previous drivers using Display Driver Uninstaller (DDU) in safe mode, pause windows updates, and perform a clean install before reconnecting to the internet. It’s not something that we experienced, but we have seen user reports claiming that installing drivers using the NVIDIA App led to certain issues, and reinstalling the same driver but from NVIDIA’s website instead solved those problems. Conclusion Visit our Patreon page to contribute a few dollars toward this website's operation (or consider a direct donation or buying something from our GN Store!) Additionally, when you purchase through links to retailers on our site, we may earn a small affiliate commission.Unfortunately, all of these suggestions are only temporary workarounds, and we can only wait for a new NVIDIA driver to provide a legitimate solution and get it together. This has been an absolutely abhorrent and completely embarrassing launch for the company. This is the worst NVIDIA launch we’ve covered and it may be the worst GPU series launch we’ve ever covered. That’s saying a lot considering AMD has had some impressively bad drivers for years. NVIDIA has taken that over. At least with Intel Arc and its Alchemist GPUs, our expectations were low, and Intel has taken notable steps to address its issues. NVIDIA, on the other hand, continues to fumble in impressively bad ways. This is the type of thing that helps the company lose market share. In the meantime, we will continue to monitor the driver situation and will provide an update when we find a more stable solution provided by NVIDIA.

GPUs More Marketing BS: NVIDIA GeForce RTX 5060 Ti Review & Benchmarks vs GTX 1060, 4060 Ti, & MoreApril 17, 2025Last Updated: 2025-04-17We benchmark the RTX 5060 Ti against the RTX 4060 Ti 8GB, the RTX 3070 Ti, 3080, RX 9070, and dozens of other GPUsThe HighlightsNVIDIA’s RTX 5060 Ti ships in either 8GB or 16GB variantsCounter to NVIDIA’s claims, the 5060 Ti does not offer a “50x” performance increase over a GTX 1060The 5060 Ti is about 13%-27% better than the 4060 Ti at 1440pOriginal MSRP: $430Release Date: April 16, 2025Table of ContentsAutoTOC Grab a GN15 Large Anti-Static Modmat to celebrate our 15th Anniversary and for a high-quality PC building work surface. The Modmat features useful PC building diagrams and is anti-static conductive. Purchases directly fund our work! (or consider a direct donation or a Patreon contribution!)IntroThe shortest possible conclusion upfront is that the 5060 Ti is about 13%-27% better than the 4060 Ti at 1440p, typically in the range of 20-25%. At 1080p, the new card is 11-24% better, typically about 18-20%. Against the 3060 Ti from 5 years ago, the 5060 Ti at 1440p is 16-39% improved, depending on the game. 1080p posted 21-40% gains, with a huge exception in Black Myth with ray tracing enabled, where there was a 56% uplift. The 3060 Ti was also the card that the 4060 Ti sometimes lost against.For older devices or possible used candidates, the closest alternatives (by performance) to pay attention to in our charts will be the 3080 (watch our review) and 3070 Ti (watch our review), which often flank the 5060 Ti, and the 7700 XT (read our review) or 7800 XT (read our review) on AMD's side.Editor's note: This was originally published on April 16, 2025 as a video. This content has been adapted to written format for this article and is unchanged from the original publication.CreditsTest Lead, Host, WritingSteve BurkeTesting, EditingMike GaglioneWritingJeremy ClaytonCamera, Video EditingVitalii MakhnovetsCameraAndrew ColemanWriting, Web EditingJimmy ThangBut pricing is the big challenge today. NVIDIA says that this card has an MSRP of $430, with the 8GB variant at $380 and RTX 5060 non-Ti at $300, launching in May. The 5060 Ti cards launch today with the reviews. We only have the 16GB model right now. We might look at the 8GB version later.Full transparency up-front. We’re keeping this review as simple and focused as possible, mostly because we’re currently traveling with a big story we’re working on. We still have dozens of gaming charts, but we wanted to be clear on that. We’re also going to keep our concluding thoughts simple because we need to see how the actual pricing shakes-out before making firmer judgments, which means there’ll be more discussion in the coming weeks -- likely in HW News or potentially another dedicated story.With that out of the way, here’s a quick version of the specs:The short version is that NVIDIA’s RTX 5060 Ti ships in either 8GB or 16GB variants. The review samples we’re aware of are the 16GB model. There shouldn’t be any difference between these beyond the memory, from what we’re told. These cards have 4608 CUDA cores, 144 TMUs, and a gacha box of ROPs. Memory bandwidth is rated at 448GB/s with a memory bus of 128-bit, which is why we have the multiples of 8GB for memory.The RTX 5070 technically has a lower memory capacity at 12GB. Theoretically, they could do a 24GB model, but these options stem from the bus width and controller choices.The RTX 5060 non-Ti will ship in May and have 3840 CUDA cores with an 8GB framebuffer, also on a 128-bit bus.AMD’s competition will include the, in theory, RX 9060 series, for which we don’t have full details yet. We’ll hear about that more likely next month.We’re keeping it simple today, so let’s just get into the benchmarks.RTX 5060 Ti Gaming BenchmarksFFXIV 4KFinal Fantasy 14 at 4K is up first.This one was bad for the RTX 4060 Ti, with the card landing at an abysmal 41 FPS AVG as compared to the 3060 Ti FTW3’s 48 FPS AVG. RIP EVGA. We explained this regression in our 4060 Ti review previously, which we titled “Do Not Buy.” Spoiler alert: The conclusion was to not buy it.The 5060 Ti isn’t really competing with the 4060 Ti here: It’s competing with the 3060 Ti, and against that, we see an uplift of 12% to 54 FPS AVG. The improvement over the 4060 Ti looks more impressive, but that’s because the 4060 Ti sucks. The uplift over its 41 FPS AVG was 31%. The RTX 5070’s 78 FPS AVG has it about 43% ahead of the 5060 Ti.Used RTX 3070 (watch our review) and 3070 Ti cards might be worth exploring: We saw completed and sold listings on eBay ranging from $270 to $340, which would put them below the 5060 Ti if it even hits its marketed MSRP, which it probably won’t. The 3070 is about equal to the 5060 Ti, with the 3070 Ti slightly ahead.AMD’s RX 7800 XT is its closest performer to the 5060 Ti, landing at 58 FPS AVG and leading the 5060 Ti by almost 7%. AMD’s RX 7600 (watch our review) falls way down the chart and runs at 32 FPS AVG. But then again, AMD does overall poorly in this particular game, with its 9070 XT (read our review) down below the RTX 5070. We talked about that in our 9070 series reviews.Finally, NVIDIA’s claimed 50x performance increase over the GTX 1060 (watch our revisit) doesn’t come to fruition when not arbitrarily enabling and disabling favorable settings. The 1060 ran at 16 FPS AVG. 16 x 50 is 800 FPS, which would be 4x the performance of an RTX 5090 (read our review). We’ve gone beyond an RTX 5070 = 4090 and to a RTX 5060 Ti = RTX 9090. In reality, the 5060 Ti is 236% ahead. That’s still a big jump, but no need to stretch the truth about it.FFXIV 1440pAt 1440p, the RTX 5060 Ti landed at 104 FPS AVG, which has it functionally tied with the 3070 Ti’s 108 FPS AVG and only slightly ahead of the 7700 XT’s 98 FPS AVG or 3070’s 97 FPS AVG. The lead over the 3060 Ti is now 16%, or about 25% ahead of the 4060 Ti. These gains are down from 4K. Lows are where you’d expect them for each card, with no meaningful differences.The 5070 is about 47% ahead of the 5060 Ti, slightly up from the lead at 4K.AMD’s 9070 ran at 126 FPS AVG here, producing a 22% advantage. The MSRP is higher, but then so is everything, including the companies that set these prices.The GTX 1060 ran at 33 FPS AVG here, the 1650 (watch our review) at 23 FPS, 6500 XT (watch our review) at 31 FPS, and 3050 (watch our review) at 45 FPS AVG. Predictably, the 5060 Ti is a big improvement over all of these, but again, not 50x.FFXIV 1080pAt 1080p, the 5060 Ti ran at 160 FPS AVG. That’s about the same as the 7700 XT and slightly ahead of the 3070 Ti. It’s finally moving up the relative ranking compared to Ampere. We think you’d still be better off with a used card right now. The 4060 Ti ran at 133 FPS AVG here, so the 5060 Ti improves by 20%. Against the 3060 Ti, the 5060 Ti is about 25% better. The 4060 Ti is finally better than the 3060 Ti when at 1080p, so those two have flipped as well.The lower-end round-up includes the GTX 1060 at 51 FPS AVG, 3050 at 66, 1070 (watch our review) at 70, and 2060 (watch our review) at 83. The 6600 (watch our review) ran at 86 FPS AVG and AMD’s 7600 ran at 107 FPS AVG.Black Myth: Wukong - 4KBlack Myth: Wukong is up now, first at 4K. The 5060 Ti ran at 31 FPS AVG. That’s obviously unplayable and is because of the resolution and settings, but it’s still useful for relative scaling.The result has it about equal to a 7800 XT. The 3080 leads by 18%, with the 5070 leading by 29%. The 3070 Ti ran a lower framerate than the 5060 Ti in this one.Let’s move to something more playable.Black Myth: Wukong - 1440pAt 1440p, the 5060 Ti ran at 57 FPS AVG and landed right between the 7800 XT and RTX 4070 (watch our review). These are all effectively tied. The 5070 held a 72 FPS AVG, or 27% ahead. That’s slightly down from 4K. The 5060 Ti is ahead of the 3070 Ti by 13%, the 4060 Ti by 27%, and the 3060 Ti by 34%. This is one of the games where the 4060 Ti and 3060 Ti are right next to each other. AMD’s 7600 ran at 31.6 FPS AVG and isn’t really in the same class of card as what we’re reviewing today. Its 7800 XT and 7900 GRE (read our review) are the most comparable, but in theory, the inbound 9060 XT should be fighting in this territory.Black Myth: Wukong - 1080pAt 1080p, the 5060 Ti pushed 81 FPS average with lows where you’d expect given the average. There is no particularly special frametime consistency benefit.The 5060 Ti ends up at about the same level as the RTX 3080 and RTX 4070 (watch our review). The 5070, which still doesn’t equal a 4090 (no matter what NVIDIA says), and its 98 FPS AVG puts it 21% ahead of the 5060 Ti.As for the last generations, NVIDIA’s new 5060 Ti leads the 4060 Ti by 24%, or the 3060 Ti by 40%. AMD’s 7900 GRE is its closest card here, slightly ahead of the 5060 Ti, with the 7800 XT just behind. Intel’s B580 cards are at around 46 FPS AVG, which has them similar to the RX 7600.Starfield - 4KIn Starfield at 4K, the 5060 Ti ran at 41 FPS AVG with lows at 34 and 29, proportional to the cards around it. This puts the 3080 ahead of the 5060 Ti and the 5060 Ti ahead of the 3070 Ti. AMD’s 7800 XT outdoes the 5060 Ti by 18%, with the more expensive 9070 non-XT up at 63 FPS AVG.The RTX 5070 ran at 54 FPS AVG here, 32% ahead of the 5060 Ti. We’ll move to 1440p for prior generations.Starfield - 1440pAt 1440p, the 5060 Ti landed at 65 FPS AVG. Unfortunately for NVIDIA, this is a terrible result: The 4060 Ti was at 58 FPS AVG, narrowing the uplift to only 13.4%. That isn’t a big improvement. The lead over the 3060 Ti’s 50 FPS AVG is 30%, also not that impressive for two generations.AMD’s 7800 XT leads the 5060 Ti by 15.5%, with the 9070 (read our review) obviously way ahead given its higher theoretical price and positioning.For those considering used options, the 5060 Ti only outdoes the 3070 Ti by about 8%, making it a reasonable alternative that might save some money.Starfield - 1080pAt 1080p, the 5060 Ti held an 82 FPS AVG with lows positioned about the same as everything around it. The 3070 Ti’s 76 FPS AVG encroaches on the 5060 Ti’s result and, from an actual human perspective, would look about the same. The 4070 outperforms the 5060 Ti by 16%, with the 5070 ahead by 26%. The 4060 Ti’s 74 FPS AVG means the 5060 Ti is about 11% better, overall a boring generational jaunt. The uplift over the 3060 Ti is 28%.Dragon’s Dogma 2 - 4KDragon’s Dogma 2 at 4K is up next.The 5060 Ti ran at 40 FPS AVG, so it’s nearly exactly tied with the 3070 Ti. The 0.2 FPS AVG advantage is well within run-to-run variance. Lows are also tied. AMD’s 7800 XT is 17% ahead of the 5060 Ti’s average FPS, with the 5070 ahead by 41%.We’ll move to lower resolutions to look at the prior generation 60 and 60 Ti-class cards.Dragon’s Dogma 2 - 1440pAt 1440p, the 5060 Ti ran at 70 FPS AVG, planting it right in the middle of the 3080 and 7700 XT. The 3070 Ti is right behind with a 65 FPS AVG, with the 4060 Ti at about the level of the 3070. The new 5060 Ti leads the 4060 Ti by 22% and the 3060 Ti with its 53 FPS AVG by 32%.AMD’s 7600 is far down this chart, so it’ll need something newer in the 9060 class to compete here. Intel’s B580 is also down near the RTX 4060 and RX 6600 XT (watch our review).As for what’s better than the 5060 Ti: Other than the 3080, the 4070 is about 12% better and 5070 is about 37% higher average FPS.Dragon’s Dogma 2 - 1080pAt 1080p, the 5060 Ti ran at 93 FPS AVG, landing between the 3080 and 7700 XT again. The improvement over the 4060 Ti is just 19%, followed by the 3060 Ti’s 68 FPS AVG for an uplift of 36%. The 3070 Ti gives the 5060 Ti just a 10% lead, doing better than the 4060 Ti.As for the GTX 1060, considering 50x its performance would put it over 1,100 FPS, we’d say NVIDIA missed the mark on this by orders of magnitude.Cyberpunk 2077: Phantom Liberty - 4KCyberpunk 2077: Phantom Liberty is next. This is newer data, so we haven’t re-run the 4060 Ti, 4060, and 3060 series cards through here yet. We’ll show it anyway for the other comparisons.At 4K/Ultra without RT first, the RTX 5060 Ti ran at 31 FPS AVG. This has it meaningfully ahead of the 3070 Ti by percentage, improved by 19%. The 7800 XT leads the 5060 Ti by about 10% here, with the 5070 about 30% ahead of the 5060 Ti.Cyberpunk 2077: Phantom Liberty - 1440pAt 1440p, the 5060 Ti ran at 68 FPS AVG, putting the 5060 Ti between the 3080 and 3070 Ti. The 5070 ends up about 30% ahead with its 88 FPS AVG, meaning that, if we just pretend that the MSRP numbers stick, you’re paying about 1% more money for every 1% more performance between the 16GB 5060 Ti and 5070. Cyberpunk 2077: Phantom Liberty - 1080pAt 1080p, the 5070 is down to a 27% lead over the 5060 Ti. The 5060 Ti now leads the 3070 Ti by 20% and the 3070 non-Ti by 27%. The 7800 XT is about 8% ahead of the 5060 Ti here.Let’s move to something where we have last-gen numbers.Dying Light 2 - 1440pDying Light 2 at 1440p is one of the situations that was bad for the 4060 Ti versus the 3060 Ti: The two cards are indistinguishable, with performance identical between them. The RTX 5060 Ti ran at 74 FPS AVG, so it outperforms the 4060 Ti (and therefore 3060 Ti) by about 23%. It took them two generations, but they’ve finally beaten the 3060 Ti in this game. The 4070 is about 6% better than the 5060 Ti here, with the 7800 XT about 14% ahead. The 5070 leads the 5060 Ti by 44% here, so if anything, the 5060 Ti stands to make the 5070 look better. Against the Intel B580’s 63 FPS AVG, NVIDIA’s 5060 Ti is about 17% better in one of the better B580 showings. Dying Light 2 - 1080p1080p has the 3060 Ti and 4060 Ti again roughly adjacent to one another, with the 5060 Ti leading the 4060 Ti by 19%. The 5060 Ti’s lead has diminished from the 1440p result. The 5060 Ti is similar to the 7700 XT’s performance here, including in lows, with the 4070 leading the 5060 Ti by almost 9%.Against older cards, the 5060 Ti improves on the GTX 1060 by not 50x, to nobody’s surprise, and instead by about 3.8x. Even with MFG, you would not get 50x. Maybe with DLSS at Ultra Sh*t quality and upscaling from 144p, we’re not certain you could squeeze 50x out of this lemon, though. You’d have to go out of your way to hurt the 1060.For those still on an RTX 2060, you can expect about a doubling of performance to the 5060 Ti in a scenario like this. Resident Evil 4 - 4KResident Evil 4 is up now, first at 4K and without ray tracing. The RTX 5060 Ti ends up performing about the same as the 7700 XT. The RTX 4070 leads the 5060 Ti by about 10-11% here, at 63 FPS AVG to 57, with the 5070 leading by 38%. That’s similar to what we’ve seen elsewhere so far. The 3060 Ti also launched for $400. Adjusted for inflation, that amounts to $491. The new card is $430. So things haven’t changed that much. The price is similar/slightly lower and performance has hardly improved. The improvement over the 2060 is about 135%. Resident Evil 4 - 1440pAt 1440p, the 5060 Ti leads the 3070 Ti by 13% and the 4060 Ti by 23%, followed by the 3060 Ti at 36.5%. The reduced resolution has benefitted the 4060 Ti marginally, allowing it to distance itself from the 3060 Ti. The B580 (read our review) is actually around the 3060 Ti’s performance, excepting 1% lows.As for the RTX 5070, which remains not a 4090 (watch our review), NVIDIA’s biggest lie leads the 5060 Ti by 36%. AMD still doesn’t have a new and direct competitor here, but probably will in May in the 9060 series. For now, the 7700 XT is the closest and outperforms the 5060 Ti slightly.RTX 5060 Ti Ray Tracing Benchmarks Our fully custom 3D Emblem Glasses celebrate our 15th Anniversary! We hand-assemble these on the East Coast in the US with a metal badge, strong adhesive, and high-quality pint glass. They pair excellently with our 3D 'Debug' Drink Coasters. Purchases keep us ad-free and directly support our consumer-focused reviews!Ray tracing is up next. These games are generally a heavier load, so we have a mix of upscaled benchmarks and of native resolution benchmarks, but all of them are with RT on now.Ray Tracing - Black Myth: Wukong 4KIn Black Myth: Wukong at 4K upscaled, the RTX 5060 Ti landed at 29 FPS AVG. That has it ahead of the RX 9070, which is more of a problem for AMD than it is a positive for NVIDIA. We already knew this about this game and AMD, though. The 9070 XT ends up about tied with the 5060 Ti here, and actually, the 3090 non-Ti (watch our review) at 29.8 FPS AVG is only about 3-4% ahead of the 5060 Ti. This game remains heavily favored for NVIDIA, especially with ray tracing. The RTX 5070 has a large lead at 40 FPS AVG, although its memory capacity can prove problematic in some of these heavier scenarios. The 5070 leads by 39% here. The 5060 Ti also shows more meaningful gains over the 3070 Ti in this test than in some of the raster tests, at 31% improved.Ray Tracing - Black Myth: Wukong 1080pAt 1080p upscaled, the 5060 Ti's 74 FPS AVG has it ahead of the 9070 XT, 3090, and 3080. It also leads the 4060 Ti by 19% and the 3060 Ti's 48 FPS AVG by 57%.The generational RT uplift is helping the 5060 Ti distinguish itself more here than it did when rasterized.Against the first-gen ray tracing 60-class card, the RTX 2060, we're seeing a 175% improvement.Ray Tracing - Dragon’s Dogma 2 4KIn Dragon's Dogma 2 at 4K and with ray tracing, the RTX 5060 Ti ran at 35 FPS AVG and roughly tied (but technically led) the 3070 Ti. That has it better than the 2080 and 2080 Ti of years past, although the 3080 still manages to best the 5060 Ti. AMD's 7900 GRE outperforms the 5060 Ti slightly, with its newer 9070 cards performing up around 3090 Ti levels -- but at a higher theoretical base MSRP than the 5060 Ti.Ray Tracing - Dragon’s Dogma 2 1440pAt 1440p with RT, the 5060 Ti ran at 62 FPS AVG and kept the lows consistent with the average. There's nothing particularly impressive or bad for the frametime consistency and lows. It’s just kind of where we’d expect it. The 4070 and 7800 XT are about 9% ahead of the 5060 Ti. And for that matter, the 3080 is around that same area. The 5070's 82.8 FPS AVG is around 34% ahead of the 62 FPS for the 5060 Ti. We've seen higher in other games.As for the lower-rank cards, the 4060 Ti ran at 49 FPS AVG and yields a 26% uplift to the 5060 Ti. The 3060 Ti isn't far behind the 4060 Ti in this one, but at least they're in the order you'd expect them to be. Ray Tracing - Dragon’s Dogma 2 1080pAt 1080p, the 5060 Ti's 82 FPS AVG landed it between the 3080 and 7700 XT again. This has been consistent. This result gives it a 20% improvement over the 4060 Ti and 37% improvement over the 3060 Ti.Ray Tracing - Dying Light 2 4KDying Light 2 is up next. Dying Light 2 at 4K upscaled with ray tracing has the 5060 Ti at 31.8 FPS AVG and exactly tied with the 7900 GRE for average and 1% lows. The 5070 improves to 43.7 FPS AVG, or 37% once again. This seems to be a fairly consistent percentage improvement to the 5070.Ray Tracing - Dying Light 2 1440pAt 1440p upscaled with RT, the 5060 Ti ran at 60 FPS AVG. We haven't yet re-run the 4060 Ti or 3060 Ti in this one, leaving us to compare instead with the 7900 GRE -- where they're about equal -- and the 3080, which remains a bit ahead of the 5060 Ti. The 5070 leads at 81 FPS AVG, or 34%.Ray Tracing - Dying Light 2 1080pAt 1080p, we re-introduce the 4060 Ti and 3060 Ti. The 5060 Ti's 87 FPS AVG has it about 20% ahead of the 4060 Ti, which itself was only 11% ahead of the 3060 Ti. The B580 is actually somewhat close here, roughly tying the 3060 Ti. As for AMD, the 7900 GRE remains the next closest to the 5060 Ti.Ray Tracing - Resident Evil 4 4KResident Evil 4 is up with ray tracing now, first with 4K and upscaled. The 5060 Ti's 67 FPS AVG has it tied with the 7700 XT, including in the 1% and 0.1% lows. The 4070 and 3080 lead these results, as they have for the past games. The 5070 leads the 5060 Ti by 36%, close to prior results. As for the 4060 Ti, its 52 FPS AVG gives the 5060 Ti a lead of 30% for one of the larger gaps.Ray Tracing - Resident Evil 4 1440pAt 1440p, the 5060 Ti again falls between the 7700 XT and RTX 3080. The lead over the 4060 Ti is narrowed to 24% now, with the uplift over the 3060 Ti at 39%.Ray Tracing - Cyberpunk 1080p RT MediumIn Cyberpunk 2077: Phantom Liberty at 1080p RT Medium, the 5060 Ti ran at 63 FPS AVG and sat between the 7900 GRE and 7900 XT. The lead over the 3070 Ti is about 10 FPS AVG here, or 17%. The 5070's 82 FPS AVG has it 31% ahead of the 5060 Ti, down in relative improvement from other benchmarks.Ray Tracing - Cyberpunk 1080p RT UltraAt 1080p and with RT Ultra, the 5060 Ti ran at 50 FPS AVG (which is really not bad when considering how heavy this workload is), or just ahead of the 7900 XT Hellhound. The 3070 Ti hit 40 FPS AVG here, with lows suffering for the 0.1% value. The 5060 Ti's lows are OK in this one, supported by the 16GB capacity.Conclusion Visit our Patreon page to contribute a few dollars toward this website's operation (or consider a direct donation or buying something from our GN Store!) Additionally, when you purchase through links to retailers on our site, we may earn a small affiliate commission.We’ve provided the benchmark numbers above. At the very least, you have the data you need to figure out if an upgrade makes sense for you. This is going to be one where we withhold full value judgment until it properly launches because we do not trust the MSRP to persist for the majority of purchasers.It certainly isn’t going to 50x a GTX 1060, though.GPU Price Comparison | GamersNexusApril 2025Used pricing is an average of recent sale prices for used cards on Ebay.GPUPrice at RetailPrice UsedRTX 5060 TiMSRP $430N/ARTX 4070New: No 1st Party AvailableOpen Box: $600$621RTX 4060 Ti (16GB)N/A$540RTX 3080Open Box: $520$449RTX 3070 TiOpen Box: $487$358RTX 3060 TiN/A$266RX 7900 GREN/A$627RX 7800 XTN/A$556RX 7700 XTN/A$472RX 6950 XTN/A$575The 16GB RTX 5060 Ti’s MSRP is set at $430, whether or not we see it at that. That’s better than the previous 16GB 4060 Ti’s launch MSRP of $500, which was atrocious. The 4060 Ti 8GB model was $400, so 8GB more memory used to be a $100 upsell, but no one bought that, so now it’s a $50 upcharge. Accounting for inflation favors the 5060 Ti over the 4060 Ti for the 16GB models with MSRPs. Nearest performance neighbors to the 16GB RTX 5060 Ti are typically the RTX 3080 and RX 7800 XT above, and RX 7700 XT and RTX 3070 Ti commonly below.We’d love to dig into value comparisons between the 5060 Ti and its current competitors, but the availability of GPUs at retail in this price bracket ($380-$480) is terrible. Using Newegg as a representation shows only 9 SKUs of any video card sold by Newegg in stock in that price range, and only one of them is actually brand new. It’s an EVGA RTX 3060 XC (not a Ti) for $440, which is an awful price.So without any new cards to buy in this price bracket, we can look toward used options -- and this is where we think people should be seriously looking.The RX 7900 GRE was around $627 average for sold listings, followed by the RX 6950 XT and 7800 XT at $556-$575 on average and the RX 7700 XT at $472 average.There’s a potential edge case where a good deal on an RX 6950 XT could be an interesting higher-performing wild card – but that’s only if you’re entirely focused on raster performance, and you’re willing to hunt for a deal on one around $500. Higher power consumption is also something to consider. NVIDIA’s 5060 Ti is more efficient.A used RTX 3070 Ti at $358 average would be a good lower-performing budget option below the MSRP of a new RTX 5060 Ti of any capacity. We found some that were in the upper $280-$290 to lower $310 range, which would be worth seriously considering. VRAM may be limiting in some situations. The RTX 3080 is going for around $449 and typically beats or is close to the 5060 Ti. The 3080 isn’t cheap enough on the second-hand market yet to get our strong recommendation in this specific scenario. That’s doubly the case for used RTX 4070s at the time of writing, which are newer and have been selling for $621 on average.And that brings us to what we’ve said a lot in the past: if your computer is doing what you need it to do and if you don’t feel a need to upgrade, then we’d say hold off. But some people do either “need” to buy new devices to replace aging hardware or just really want the escape of building a PC, which we also appreciate and relate to. It’s just going to come down to your price tolerance.Right now, we really don’t have the answers. We’re trying to figure them out, which is why we’re currently flying all around the US at our own expense to talk to companies about the pricing situation. We hate to not be able to give a value judgment at the end of a review, but until this card is actually available -- which will coincide with the launch of this review -- we just can’t know what it’s going to cost.Once it is, we’re going to do a recap either in the news or standalone.Just for context: We just met with a distributor that buys hundreds of thousands of GPUs per year. Last week, we saw their cost to buy RTX 5090s. The cheapest was around $2,400 up to $3,000, and that’s their cost. That means $2,000 is impossible. We’re not sure to what extent that’ll affect the 5060 Ti cards, especially after the launch period where pressure to maintain the price is off.Now maybe that’ll change with the partial tariff exemptions, but those are up in the air.

GPUs AMD Fake Frame Image Quality, AFMF, & FSR 4 vs. FSR 3.1 ComparisonApril 21, 2025Last Updated: 2025-04-21We compare AMD's in-game frame generation, AFMF, and FSR against “native” rendering in many gamesThe HighlightsOur tests were performed using an AMD RX 9070 XT and RX 7900 XTXWith frame generation, you still get some really nasty images that aren’t representative of how the game was intended to lookFSR 4 generally improves image quality and stability over prior versionsTable of ContentsAutoTOC Grab a GN15 All-Over Print Component Mouse Mat for a high-quality mousing surface that'll fit your keyboard & mouse. These mouse mats use a high-quality yellow rubber underside, a blue stitched border for fray resistance, and are covered in PC parts. This is the best way to support our work and keeps us ad-free to support consumer-first reviews!IntroToday, we're giving AMD the NVIDIA treatment: We're inspecting AMD's fake frames to compare them to real frames, but we aren't yet comparing NVIDIA's fake frames to AMD's fake frames, because that'll come later.That means that this article will include frame-by-fake frame analysis of AMD's generated images versus native-only rendering.Editor's note: This was originally published on April 8, 2025 as a video. This content has been adapted to written format for this article and is unchanged from the original publication.CreditsTest Lead, Host, WritingSteve BurkeTesting, Writing, QCPatrick LathanJeremy ClaytonVideo EditingVitalii MakhnovetsTim PhetdaraAndrew ColemanWriting, Web EditingJimmy ThangSometimes, you can see ghost images, such as in Kratos' swing over this snowy background, where there's a blurring of the axe and arms as AFMF, or Advanced Fluid Motion Frames from AMD, interpolates in-between frames. We'll also talk about FSR 4 vs. prior FSR iterations and native: In some scenes, like the one above, image clarity and stability are greatly improved over prior FSR versions. The Ultramarine's armor and hanging cables both show significant improvement in the newer version versus the older.In other scenes, like the one above showing an air assault, we can see heavy warping with FSR 3.1, but still modulation with FSR 4 for the flying units. The ground assault shows issues with shadows pulsing underneath the Tyrannids in both versions. Smeared trails behind NPCs and barrels are improved upon with FSR 4, but sometimes still present.So, we'll be looking at AMD's Fidelity FX Super Resolution version 4 with the new RX 9070 XT (read our review) GPUs and comparing it against the prior version. This is an image quality specific test, and like we said in the NVIDIA coverage of DLSS and MFG, not all fake frames are created fake equal. This will look at that in part. What we're not doing here yet is comparing FSR 4 and AFMF to DLSS and MFG. That might be a later piece if there's interest, but we need to lay the groundwork for each technology independently first.One important thing to remember with all of this, just like with NVIDIA’s that we looked at, is that we’re closely inspecting these images today for image quality. That means we’re pausing things and zooming in. In real play, it’s likely that some of these differences would go unnoticed at full speed and “zoomed out.” One other note is that YouTube/video compression makes things sometimes difficult to fully appreciate.Let’s get into it.FSR 4 OverviewAMD’s FidelityFX Super Resolution (FSR) upscaling has finally moved into the “AI” buzzword era with FSR 4’s machine-learned Convolutional Neural Network (CNN) model co-developed with Sony. Sony and AMD announced a collaboration effort back in December of 2024, dubbed “Project Amethyst.”Sony strongly implied that it’s going to use a rebranded version of FSR 4 as its own “PSSR” in order to target 1080p native rendering on the PS5 Pro, but with the upscaler doing the work to output a good looking image at “4K.” On the PC side, FSR 4 will only run on the new Radeon RX 9000 series graphics cards for the time being, with no official word on back-porting to RX 7000. We’re unsure at this time whether it’s a technical limitation or a product segmentation move on AMD’s part.The official support list for FSR 4 has 36 games at the time of writing, which is late March. That’s not a lot, but the number will hopefully grow as more games are updated. Several of the listed games are big Sony titles as well, indicating that the company is serious about utilizing the tech, but also shows the partnership between them.The previous generation, FSR 3.1, is technologically distinct from its predecessor (FSR 3) by way of being implemented as a modular .dll file rather than being entirely baked-in to the game. This paves the way for future revisions of FSR to be more easily implemented by the game developers or just in general.FSR 4 also uses a .dll file, and can be swapped-in officially in FSR 3.1 games via a driver-level override in AMD’s Adrenaline software in a very similar way to NVIDIA’s DLSS override. However, the games have to also be on AMD’s official whitelist to get the toggle to appear in the driver software. Unofficial tools like OptiScaler open the door for a lot more flexibility, but we haven’t tested them yet so we can’t make a recommendation, but there’s stuff like that out there.AFMF 2.1 OverviewAMD also includes in-game frame generation, or “fake frames,” under its FSR umbrella, and we haven't seen any indication from AMD that its in-game framegen algorithm has changed since FSR 3.1. In AMD's words, "Advanced frame generation interpolation technology when used with AMD FidelityFX Super Resolution (FSR) 3 inserts 1 frame between existing ones."However, AMD also has separate driver level frame generation known as Advanced Fluid Motion Frames (AFMF) that can be applied without in-game support. AFMF 2.1 is a new introduction alongside FSR 4.0. To use it, you need AMD Software: Adrenalin Edition 25.3.1 or newer, RX 6000 or newer, and a DX11, 12, or Vulkan game. RX 6000 only supports AFMF in exclusive fullscreen mode, while RX 7000 and newer support borderless windowed, and the AMD 9070 (read our review) reviewer guide stated that "in-game display setting should be set to borderless fullscreen mode." And that's a lot of rules, but keep in mind that Smooth Motion, NVIDIA's answer to AFMF, is exclusive to the RTX 50-series. NVIDIA has stated that "support for GeForce RTX 40 Series GPUs will be coming in a future update." We're focusing on AFMF 2.1 here, so this isn't a direct 1:1 equivalent to the piece we just ran on NVIDIA's in-game frame-gen, but we’ll also be looking at the frame generation performance for AMD. For this article, the performance we care about is image quality, and not the actual literal framerate performance. That will be a separate test along with potentially latency. This is an isolated test so that we can build foundational knowledge first, just like we did for NVIDIA. The direct comparison would be NVIDIA Smooth Motion versus AMD Fluid Motion Frames, but we’re focusing on just AMD today. That comparison may come later.As for FSR testing, our FSR comparisons will focus on FSR 3.1 vs. FSR 4, with a couple references to native capture as an anchor. We captured everything at 4K resolution with FSR running at the Performance preset, meaning it’s upscaling from 1080p base render resolution. We disabled anti-aliasing, camera effects, and motion blur where possible to get the cleanest images we could.The objectives today are purely image quality, not performance. We’ll be comparing frame-by-fake-frame image quality, FSR iteration quality, and looking at behavioral patterns in general.Let’s get into the image quality comparisons.Warhammer 40,000 Space Marine 2First up is Warhammer 40K Space Marine 2. Like everything else we tested for this piece, FSR 4 support comes by way of the driver-level override. We used the High graphics preset, turned off camera shake, and set motion blur to off; however, we found the latter doesn’t actually work and motion blur persists regardless, but that’s a game thing.ArmoryWe’ll start the comparisons with a scene in the Armory, or “Armouring Hall” in native Grimdark. Even before walking forward, the difference between FSR 3.1 and FSR 4 is stark. Static elements like the floor of the walkway that shift and shimmer heavily with FSR 3.1 are now stably locked-in. On top of that, the entire image is much clearer and more detailed. Examples of this include the floor, where we see improved image stability and clarity, the Ultramarine’s armor showing similar improvements in a side-by-side, the distant hanging cables, and the tech priests’ hoods. Distant candle flames that can’t even be made out with FSR 3.1 are visible with FSR 4, bringing them back into existence.As we walk forward and the… we’ll call it a “kiosk,” drops down, the difference in clarity is so obvious it’s almost like looking at two different resolutions. No matter where you look there’s improvement. The fine details under the main monitor, the tech priest’s mask, and even just the general contrast and visual discernability of all the mechanical arms and tubes are all vastly improved. We double-checked our settings and confirmed that they were running as intended for a like-for-like comparison, so it really is just that much better in this example.This is a very promising start for FSR 4.Let’s compare FSR 4 to native 4K. Space Marine 2 forces either TAA or upscaling at all times (even at native), so we went with the default of TAA for the native capture. We also did this in our DLSS comparison, which showed how some scenarios, like Cyberpunk, can actually look worse than upscaling because of TAA.The flickering and shimmering on the floor in Space Marine 2 we saw with FSR 3.1 is also present at native with TAA. That makes FSR 4 look even more impressive here – even at the performance preset – since it’s taming an undesirable behavior. We said this before, but we shouldn’t be seeing things that look worse with all defaults at native than with an upscaling technology. General detail before moving – like in the floor, walls, and priest hoods – is a toss-up between native with TAA and FSR 4 Performance mode. That’s simultaneously a critique of TAA and a praise of FSR 4. The green orb far in the distance looks very slightly better with native TAA. As the “kiosk” drops down, the level of detail between native with TAA and FSR 4 Performance is very close. However, we think FSR 4 actually comes out slightly ahead – most obviously in the round speaker-looking elements on top of a couple of the monitors.Like we said in the DLSS piece, upscaling should never look better than “native,” and game developers shouldn’t be leaning on upscaling technologies in this way. The only reason it ever does look better is because of issues such as those with TAA, which is the default here.CommandWe’ll briefly look at another indoor scene in the campaign’s command bridge before moving on to a mission. Again, everything is sharper, clearer, and easier to discern when using FSR4. Gadriel’s face, Titus’ hair, and Chairon’s armor – particularly the chest decoration – stand out as night-and-day differences.Looking at the bridge’s holographic map area, FSR 3.1 suffers from distracting flickering on some of the round grates (underneath the three skulls and on the right side of the main terminal). Switching to FSR 4 almost entirely eliminates this behavior. The thin lines within the hologram that shimmer and boil with FSR 3.1 come across as much cleaner with FSR 4. The other ship visible out the left windows doesn’t show much difference, however.It could be that the largest areas of improvement with FSR 4 are in dimly-lit or low contrast scenes. We’ll test that with the next comparison.“Decapitation” Mission - Scene 1Loading into the “Decapitation” Operations mission gives us a brighter outdoor area. While the marine’s armor is again visibly better-looking with FSR 4, the effect on the rest of the scene is more subtle, more like lifting a haze rather than a transformation. You can clearly see this in the texture of the ground and on the shoulders of the statues.Once in motion, FSR 3.1 starts to deteriorate, but FSR 4 keeps the image clean. Unfortunately, the bugged permanent motion blur makes it hard to draw a distinction between the two FSR revisions while the marine is rolling down the stairs. Elements such as the detail in the inlaid stone floor and the buildings to the right look better during motion with FSR 4. So far, it looks like most of the FSR 3-to-4 improvements are visible in motion.“Decapitation” Mission - Scene 2Strafing to the side shows off a huge improvement favoring FSR 4 over FSR 3.1. Every single element on screen looks better with FSR 4 – the textures on the sides of the stairs, the statues, the murals against the far wall, and the guardsmen. It again gives the impression of running at a higher resolution.This would be a very interesting scene to compare the most up to date implementations of DLSS and FSR head-to-head in a future piece.“Decapitation” Mission - Scene 3Last for Space Marine 2 is an upscaling torture test by way of a slow pan of the Tyrranid assault. The flying creatures passing over the front of the massive building cause the windows to warp and blur heavily when using FSR 3.1. It still happens with FSR 4, but to a lesser extent. This is close to a worst case scenario for any upscaler, period.In both the air and on the ground, FSR 3.1 causes the creatures to blur into a mass, sometimes phasing in and out of existence or blending together. FSR 4 isn’t totally immune here either, but again does a way better job than the prior version.Since this scenario is so hard on upscalers, let’s compare to native with its forced TAA again. Watching the flying creatures in front of the windows shows us what it’s supposed to look like, free of the heavy warping seen with FSR 3.1, or even the warping-lite modulation seen with FSR 4.Looking at the ground assault again shows just how well FSR 4 is handling this relative to FSR 3.1. It’s very close to the look of the native capture, but still suffers from an effect that makes the shadows underneath the Tyrranids appear to pulse and shift underneath them. At this level of fine detail and chaotic movement, even native with TAA struggles a little bit with grain and warp. Some areas are cleaner, but like we said earlier, this particular game has toss-up comparisons between them.Monster Hunter WildsMonster Hunter Wilds is up next. We used the High graphics preset, but turned off anti-aliasing and camera effects like motion blur, vignette, and depth of field. We also reduced camera shake to its minimum levels. Cutscenes are entirely in-engine, which is useful, so we got a mix of those with some actual in-game capture.Title ScreenTaking a quick look at the title screen animation shows little difference between FSR 3.1 and FSR 4. Textures and edges are slightly sharper with FSR 4. The stippled effect on fur as seen with FSR 3.1 is also almost entirely gone with FSR 4. There’s not much else to discuss here so we’ll move on.OasisJumping into the actual game at the point you choose your weapon by the small oasis shows an ugly pattern superimposed over the sand when using FSR 3.1 that goes away with FSR 4. It doesn’t make the game unplayable or anything, but it’s pretty distracting.When talking to Alma, we can see that FSR 4 handles the fine strands of her hair a little better than FSR 3.1 does. It also adds sharpness to the weapons immediately to her left. While running towards the training barrel, we see that FSR 4 keeps the detail of the hunter’s clothes and equipment sharper. It’s not a huge difference, however.Going to CampThe long cutscene that takes you to the main camp shows much the same. FSR 4 has a slight advantage to image quality via sharpness and minor detail enhancement. Hair, fur, and feathers benefit the most by way of FSR 4 reducing the appearance of patterns or stippling superimposed over them.One clear difference is in trails behind objects moving across a patterned background. For example, when the two Felynes drop the barrel, it leaves a smeared trail behind it on the wooden walkway, as does the NPC on the left side of the screen and the unfortunate Felyne as it falls backwards. We think FSR 3.1 handles this very poorly – FSR 4, while not perfect, definitely does better.Considering what we saw in Space Marine 2, the less drastic differences between FSR revisions in Monster Hunter Wilds is surprising.Marvel RivalsThe final game we'll analyze for FSR upscaling is Marvel Rivals. To keep things consistent, we used the training range to gather footage.Rocket JumpStatic scenes don’t differ much between FSR 3.1 and FSR 4 in Rivals, possibly because of the game’s art style and strong default sharpening filter. We’ll need to look at movement to suss out the differences, and blasting forward with Rocket’s dash is a good place to begin.Even before dashing, we can see a blob of pixels around Rocket’s head getting distorted in the FSR 3.1 recording, which isn’t nearly as pronounced with FSR 4. As soon as we blast forward, FSR 3.1 turns into an over-sharpened, grainy mess, as seen on Rocket’s gun, jetpack, tail, and the ground below. FSR 4 is able to cope with the sudden movement far more gracefully, and only gets bad around the finer points of detail like the spikes on Rocket’s knees and the hair/fur on his head.Rocket StrafeNext we strafed to the side while shooting. Before moving, we can see a repeating pattern overlaid on the left side of the ground, similar to what we saw in Monster Hunter Wilds, that’s not present with FSR 4.Once we do start moving and shooting, FSR 4 retains more detail in the bullet trails than with FSR 3.1. After dropping off the first ledge and reloading, FSR 3.1 responds to all the motion by giving everything in the vicinity of Rocket’s model a kind of deep-fried-meme look, and ghosting on the trailing edge of his jetpack. There’s still a little bit of ghosting with FSR 4, but it’s greatly reduced – and the deep-fried look is gone.Rocket WallrunLast, we tried a wallrun. FSR 3.1 handled it overall better than we anticipated, but still left horrible ghost images as Rocket climbs up across the purple banner. FSR 4 still has them slightly, but they’re not noticeable to us at full speed in real-time.For the rest of the run, there’s not a huge difference between the two FSR revisions outside of a slight clarity advantage and reduced ghosting with FSR 4.AFMF 2.1 Image Comparisons Grab a GN15 Large Anti-Static Modmat to celebrate our 15th Anniversary and for a high-quality PC building work surface. The Modmat features useful PC building diagrams and is anti-static conductive. Purchases directly fund our work! (or consider a direct donation or a Patreon contribution!)We’re getting into the AFMF and frame generation comparisons now. We’ll play some side-by-side, frame-by-frame comparisons while setting this section up.For comparison purposes, we selected games that support in-game frame generation to compare with driver-level changes. In the real world, you should almost always opt for in-game frame generation over AFMF at the driver if in-game is available. The most obvious downside of AFMF is that it has no awareness of UI elements, so menus, text, and icons may be distorted (although we saw NVIDIA struggle with this even with in-game frame generation).All footage for AFMF comparisons was captured at 4K 120FPS. A 7900 XTX (watch our review) with Adrenalin 25.2.1 was used for AFMF 2.0 capture and a 9070 XT with Adrenalin 25.3.1 was used for everything else. AFMF Search Mode was set to High and Performance Mode was set to Quality, the recommended settings for our setup. AMD is more direct than NVIDIA about recommending framegen only in scenarios where the game can already run at at least 60FPS, and we stuck to that recommendation.As with NVIDIA framegen, the vendor's capture utility (Radeon ReLive in this case) was the most practical way to capture, but because we can't manipulate the rate of frame generation (like we could for NVIDIA), we'll have to rely more on frame-by-frame comparisons. We constantly had issues with AMD's Record & Stream tab disappearing after reboots, so if AMD is reading this, please fix that (and yes, our IGP is disabled).Warhammer 40,000 Space Marine 2We used the same settings for Space Marine 2 that we did for the FSR comparisons, with Resolution Upscaling set to FSR and Render Resolution set to Native since it can't be explicitly disabled. We set Motion Blur Intensity to Off even though the setting doesn't work. Framegen worked with fullscreen enabled, so we left that setting alone.ScreenshakeWe’ll start with the worst-case scenario.We recorded an additional scene in Space Marine 2 to show the downsides of frame generation. These clips aren't tightly controlled or synchronized; we just loaded into the main hub and shook the mouse around violently, so we’ll freeze frame some parts to show the issues. Besides making it very obvious that motion blur was still on (despite being toggled off), this allows us to see multiple frames where AFMF is definitely applied on top of UI elements like the "Assemble" waypoint. Applying frame generation on top of UI elements can cause ghosting and duplication of UI elements, which just looks bad. We can compare this to the in-game frame generation option, which is also a garbled, muddy mess in this scenario, with distortions around the edges that almost look like eye floaters. It completely breaks in this scenario, but perfectly preserves the UI layer even in the worst frames. Rapid movements like this aren't out of the question for mouse-and-keyboard users. They’re especially common in certain types of games, like shooters in particular where a fast or twitchy response necessitates them. Compared to native, these types of rapid movement scenarios are a worse experience with frame generation.ArmoryOur armory scene is relatively slow, but we can still see the effects of frame generation on moving limbs versus native rendering. The telltale sign of generated frames here is the slight blurring of detail on the marine's armor in frame-by-frame playback, like the back of his right leg as he passes under the light, but this is only really visible when closely examining individual frames in a specific location. The mandatory motion blur and application of FSR also help disguise the generated frames, since both of these effects lead to the same kind of temporal smearing that generated frames are subject to.The frame-by-frame playback of AFMF 2.0 versus 2.1 reveals greater differences, with a prominent secondary image surrounding the marine's right arm in advance of its movement in the next "real" frame. This only affects moving elements of the scene; there's no noticeable sign of frame generation in the relatively static background even with the older version.“Decapitation” Mission - Scene 1By rolling down the stairs, we can see a weak point of frame generation, although the inescapable motion blur makes it harder to detect. There are multiple frames where the fine details on the marine's armor are blurred, like the bottoms of his boots where lines are lost. Moving frame by frame with native and AFMF 2.1 capture side by side, there's a clear difference between the even and predictable motion blur and the irregular, faded outlines of generated frames. The marine's feet change position more than any other part of his armor during the dive and roll, which is why they're especially prone to blurring and transparency.The generated frames are also identifiable by ghosting behind the bullets being fired in the background, with classic ghosting behavior causing an undesirable look. In our recent piece discussing NVIDIA's framegen, we noted similar behavior with raindrops that made the rain effects look softer and more transparent in motion.Comparing AFMF 2.0 to 2.1 at similar framerates, 2.1 appears to have less ghosting than 2.0, which should help make the effect less noticeable during gameplay. In each generated frame of the AFMF 2.0 capture, there's a clear secondary image of the marine in advance of the next real frame, as we noted to a lesser degree in the armory scene. Blurring and loss of detail can be issues, but ghosting is a much more visible downside of framegen and one that can ruin the experience. A comparison to in-game frame generation at the same timestamp demonstrates that it's predictably much better at preserving detail, since it's given more information to work with directly from the game engine. The in-game generation causes a crisp outline in advance of the marine's movement, visible above around his gun and his arms, but the detail within his boots isn't distorted at all. This could still lead to the shimmering outlines that we saw with NVIDIA's framegen, but the individual frames are closer to reality than with AFMF.“Decapitation” Mission - Scene 2We'll start off this next scene with another native comparison to establish which elements are due to regular motion blur and which are due to frame generation. The AFMF 2.1 capture matches native with its rendered frames, but it's interspersed with generated frames where the marine's armor loses sharpness on the fast-moving legs. That's clearly the area we need to focus on, so we can move to a 2.0 versus 2.1 comparison with that knowledge.Walking sideways in front of a light background makes the difference between 2.0 and 2.1 more obvious, with 2.1 showing some slight irregularities around the edges of the marine's legs where 2.0 shows massive secondary images. As usual, the resulting effect would be easier to notice in motion if there weren't already other blurring effects forced on us with this game.God of War RagnarökGod of War ran well above 60FPS on the 9070 XT even at Ultra, which made it harder to capture generated frames, so we kept our testing brief. The ultra preset was used with motion blur, film grain, and camera shake disabled. We expected FSR to be forced when in-game framegen was enabled, but the options menu didn't reflect that, so the scaling method was set to TAA and the quality to Native for all tests (scaling cannot be explicitly disabled).AxeAs expected, the moments of rapid movement during Kratos' windup and swing are the most difficult for AFMF to deal with. Whereas the native capture clearly shows each frame of his arms and the axe as it moves, the AFMF 2.1 capture has individual frames with obvious attempts at interpolation. This is most noticeable directly on the models, since the trail of particles behind the axe is already an intentional smear.By swinging Kratos' axe in front of the white snowy background, we can clearly see ghost images with the older AFMF 2.0 frame generation. Direct frame by frame comparison is more difficult here due to the lower frequency of generated frames, but it's clear that the generated frames with 2.0 more commonly have ghosting around the axe and even Kratos' model. 2.1 shows some artifacts as well, but it's usually in the form of unevenness in the outline of the axe and Kratos' arm as they swing forward, while the core of his model is better preserved.Checking back against God of War's specific implementation of in-game frame generation, we see the same behavior as in Space Marine 2 where the details of Kratos and the axe are excellently preserved, but there's a distinct outline where framegen has done its version of content aware fill in the area that those objects will occupy in the next real frame. In comparison, the fullscreen AFMF 2.1 effect has more distortion around the usual axe and arm area.LogThe movement of the axe in this small QTE was too rapid for either 2.0 or 2.1 to keep up with, with the large deltas between frames leading to a similar appearance from both AFMF versions. The head of the axe appears doubled in some generated frames, with additional distortion around the handle. It's difficult for any type of frame generation to compensate for large deltas between frames, which is part of why AMD recommends running at 60FPS before turning it on (with latency being the other part).Marvel RivalsMarvel Rivals is next.Mantis 3Starting with the jump pad, we can see at the beginning of this scene that both AFMF 2.0 and 2.1 show ghosting on the rings that rise up from the pad. Once in motion, both iterations have trouble keeping up with the rapid movement, but 2.1 does a moderately better job of preserving Mantis' outline. The distance between the secondary image and the core of Mantis' model with 2.0 creates a greater blurring effect, and although the generated frames with 2.1 only roughly maintain the shape of her hands and feet, the resulting silhouette is stronger. As she approaches the apex of the jump, the distortion occurs in the background instead, with 2.0 more commonly showing doubling of scenery elements like the railing immediately in front of her.Marvel Rivals' in-game frame generation version behaved in the same way as God of War's and Space Marine 2's,  with crisp outlines around the next known position of Mantis' model, visible above the knees in these frames, coupled with some afterimages trailing behind the arms. The overall effect is still far cleaner than AFMF, especially since the artifacts only apply to Mantis' model, leaving the scene behind her almost completely clear of framegen problems.Mantis 2We don't recommend using framegen for games like Marvel Rivals where latency is a concern and rapid mouse movements are common. Framegen is kind of like v-sync in that at best it's a cosmetic upgrade maybe, and at worst it's a source of latency. In this scene, we can see distortion around Mantis' hands with AFMF 2.1 in advance of the motion they're about to make as she fires, but a rendered frame was buffered in order to generate that image, whereas without framegen, rendered frames are simply delivered when they're ready.Notice also that with AFMF, Luna Snow's nametag is distorted on the first frame where the camera shakes, which is a further disadvantage of AFMF versus in-game frame generation. Using the in-game option, the nametag is preserved.Cyberpunk 2077In Cyberpunk, we used the High preset without ray tracing and set FSR 3 to Native AA, since FSR was required in order to enable in-game framegen.CarFirst is a car scene. Keeping an eye on the headlight beam as it passes over shrubs and rocks to the right of the road, we can see that the scenery appears to wiggle slightly with AFMF 2.1 as the generated frames don't place objects in precisely the correct location. With AFMF 2.0 in the same areas, there's a much simpler loss of detail as every generated frame is a blurry mess. The area on the shoulder that tracked slightly wrong with 2.1 is instead completely layered with a ghost image with 2.0; we prefer the newer version here, but native rendering without fake frames still looks cleanest.Moving to a 2.1 versus native comparison, we can see that the wiggling behavior is definitely an artifact of AFMF and not something carried over from the original native render. The native capture has fewer frames, obviously, but the objects to the right side of the road track in a clear, straight line between frames as opposed to the slight side-to-side shifting with AFMF 2.1. Native should typically be crisper, even if less smooth, so this makes sense.BenchmarkUsing the game's built-in benchmark scene, we can again see that 2.1 is more prone to distortion in areas where 2.0 would blur and ghost, with the vertical pillar here turning into a wavy line in fake frames. As the camera passes the corner with pages from the Night City Journal, 2.1 does a much better job of preserving text and fine detail where 2.0 just ghosts. Moving to a later part of the scene, frame by frame playback reveals more distortion visible with 2.1 as the camera passes over the barbed wire fence: straight lines remain clear with 2.1, but they don't remain straight. As usual, 2.0's equivalent is a fully duplicated ghost image of the fence in each generated frame.Again, we can check back against the native footage for confirmation that the behavior we're seeing comes from AFMF. The horizontal fence bars are straight and uninterrupted in each frame of the native capture, whereas they're frequently broken up and uneven in the AFMF 2.1 footage, although AFMF 2.1 does do a fairly good job of preserving the scene behind the fence without major framegen distortion.Conclusion Visit our Patreon page to contribute a few dollars toward this website's operation (or consider a direct donation or buying something from our GN Store!) Additionally, when you purchase through links to retailers on our site, we may earn a small affiliate commission.In terms of image quality, FSR 4.0 is an improvement over FSR 3.1. And AFMF 2.1 is an improvement over 2.0. Both of these are good things because if those weren’t the case, then AMD is using numbers wrong. Whether or not it’s worth using these technologies at all is more situational, just like with DLSS. First of all, it’s going to be highly specific to the games and also the person playing them. The use case for these, take FSR for example, is definitely a good alternative to lowering the settings, but when we’ve polled our audience in the past, there are a lot of people who prefer to lower the settings than to use an upscaling approach like FSR or DLSS. It’s really going to be something that users should toggle and decide if they like. While that might sound like a wishy-washy answer, that is the answer. It is very situational. The good news is that it’s easy to turn these technologies on and off to see if you like it. Some people will prefer the higher graphics quality with the potential image quality losses that upscaling technologies provide and other people won’t. Going back to whether it’s worth turning on, the best answer we can provide is that we think it’s a good alternative, just like DLSS, to lowering settings in some games compared to running games at lower performance. So if you’re trying to fix performance issues and you want the higher settings, generally speaking, both the newest versions of DLSS and FSR work well for that. In the games we tested using FSR 4.0 as an override was an improvement over past versions, which is good. While AMD has made improvements to these technologies, the question you should ask is whether you want to use them at all. With frame generation, you still get some really nasty images that aren’t representative of how the game was intended to look. You get ghosting, doubling up of images, and distortion of text. A lot of people will see that and want to turn it off. This will also depend on the game. It’s a little less clear what the decision should be on the upscaling front because it will depend on how much you’re struggling to run a particular game. It becomes a choice of sacrifice between graphics settings or image quality crispness. For some people, it may not be a choice if the game is running too poorly. Overall, FSR 4, just like DLSS 4, is an improvement over its preceding version. This is what we want to see. But like DLSS, the degree of improvement on the scale of a little bit better vs totally transformative, it’s going to be closer to the a-little-better side. It won’t change how you fundamentally see games. Next, we may look at FSR 4 vs DLSS vs XeSS in a future content piece. That will let us look at the direct comparison between competitors.

Tariffs TimelineApril 23, 2025Last Updated: 2025-04-24We provide a detailed breakdown and timeline of the tariffs impacting the United StatesThe HighlightsThe US has imposed wide-spread tariffs on most of the countries in the worldOur timeline chronicles the shifting nature of the tariffsTariffs have impacted the pricing and availability of hardware in the US Grab a GN15 Large Anti-Static Modmat to celebrate our 15th Anniversary and for a high-quality PC building work surface. The Modmat features useful PC building diagrams and is anti-static conductive. Purchases directly fund our work! (or consider a direct donation or a Patreon contribution!)Our timeline below accompanies our deep-dive investigation into the impact of the tariffs roll-out on the computer hardware industry. Our investigation focused on not just the percentages, but specifically, the way in which they were announced and applied. We flew around the country to meet with factories in the US, manufacturers who use contract manufacturing in other countries (like China, Vietnam, Thailand, Taiwan, Singapore, Japan, so forth), German manufacturers, and more. Our interview list included Hyte, Thermal Grizzly, Protocase/45 Drives, iBUYPOWER, CyberPower PC, Corsair Components, freight forwarding company Straight Forwarding, and Louis Rossmann of Rossmann Repair.You can find that video embedded below. Below that, we have included the entire timeline of tariff changes that we could find. It is dated back to 2018. Please note that we have likely missed a few things, as this situation changes nearly daily and our regular coverage spectrum has not traditionally included following these changes; however, we believe we have compiled all of the major changes that are directly relevant to this story, particularly as it relates to computer hardware. This was a huge team effort at GN and required a massive investment in travel and time to complete our 3-hour documentary. If you find it educational, we ask that you please support us directly by buying something from our store. You can find high heat resistant project and soldering mats, PC building Modmats, T-shirts with paper launch GPUs or Honey Pots from our lawsuit against PayPal, copper-plated stainless steel mule mugs with thermal conductivity written on them, tabletop gaming dice with embedded inductors or cats, and more. Thank you.CreditsHost, Writing, Lead EditingSteve BurkeLead Camera, Storyboarding, EditingVitalii MakhnovetsPre-Cut, LabelingMike GaglioneTim PhetdaraAnimations, LabelingAndrew ColemanWriting, ResearchJimmy ThangBen BensonUS Tariffs TimelineThis timeline is sorted chronologically. We have attempted to present it as neutrally as feasible and from a place of covering the impact and events. As a part of this effort, we are also including links to sources with ideologies we may not agree with, but which we believe are appropriate for establishing the timeline of events.Note on SourcesOur intent is to cite primary sources, including government documents, and a variety of secondary sources. In some cases, we link only to secondary news stories. This can occur when a government announcement happens during briefings or interviews with reporters.Background: Tariffs During The First Trump Administration & Biden Administration Jan. 22, 2018: The Trump Administration imposed tariffs on solar panel components and residential washing machines. Solar panel components had a 30% tariff, which would decline over four years. The administration levied a tariff of 20% on the first 1.2 million imported washers, which could increase to 50%. March 8, 2018: President Trump announced a 25% tariff on steel imports and 10% tariff on aluminum imports for many countries, not including Canada and Mexico. Federal Register (1, 2)NPR May 31, 2018: The Trump Administration imposed a 25% tariff on steel imports and 10% tariff on aluminum imports for Canada, Mexico and the European Union. The administration said it had “reached arrangements on steel with Australia, Argentina, and Brazil, and with Australia and Argentina on aluminum.”June 29, 2018: Canada announced tariffs targeted at U.S. steel and aluminum products, in addition to other goods. The tariffs would go into effect on July 1, 2018. Sept. 18, 2018: The United States issued $200 billion in tariffs on Chinese imports, citing the need to protect “intellectual property.” Government Trade ReleaseMay 17, 2019: The United States removed tariffs for steel and aluminum imports from Canada and Mexico.July 1, 2020: The USMCA - a trade agreement among the United States, Canada and Mexico - goes into effect. USMCA TextSept. 30, 2021: In a Politico interview, a Biden administration official said the United States will “build on” existing tariffs that are levied against China.PoliticoMay 14, 2024: The Biden Administration increased tariffs on imports from China for electric vehicles, solar cells, lithium-ion vehicle batteries, and semiconductors, among other products. Tariff increases ranged from 25% to 100%. Sept. 13, 2024: The Biden Administration finalized tariff rates and exceptions from the May tariff announcement. Updates included new timing, rates and exclusions for some medical devices, solar manufacturing equipment, and wafers. Government Trade Release Tariffs During The Second Trump Administration  Grab a GN Tear-Down Toolkit to support our AD-FREE reviews and IN-DEPTH testing while also getting a high-quality, highly portable 10-piece toolkit that was custom designed for use with video cards for repasting and water block installation. Includes a portable roll bag, hook hangers for pegboards, a storage compartment, and instructional GPU disassembly cards.Monday, Jan. 20 On inauguration day, President Trump said the U.S. government would implement 25% tariffs on imports from Canada and Mexico, starting on Feb. 1. SourcesAssociated PressSunday, Jan. 26 The Trump Administration said it would impose 25% tariffs on imports from Colombia after an immigration dispute. In response, the Colombian government threatened 25% tariffs on imports from the United States. The situation deescalated after the two countries reached an agreement.  SourcesSaturday, Feb. 1The Trump Administration announced 25% tariffs on imports from Canada and Mexico. Energy imports from Canada would have a lower tariff rate of 10%.The Trump Administration announced 10% tariffs on imports from China. The tariffs on Canada, Mexico, and China would go into effect on February 4. SourcesMonday, Feb. 3The Trump Administration agreed to a 30-day pause on tariffs with Canada and Mexico after negotiations. President Trump told reporters that the European Union could face tariffs soon.SourcesTuesday, Feb. 4The United States imposed a 10% tariff on imports from China, as announced on February 1. China announced new tariffs on imports from the United States, including a 15% duty on coal and liquefied natural gas. China also announced 10% tariffs on imported crude oil, agricultural machinery, and pickup trucks. These tariffs would go into effect on February 10. China announced export controls on several minerals and began investigating Google for antitrust violations. SourcesChina - Government Documents (1, 2, 3)Associated PressCNNBBCMonday, Feb. 10In a continuation of tariffs from 2018, the Trump Administration announced a 25% tariff on imported steel and aluminum, which would go into effect on March 12. The administration stopped providing exemptions for steel and aluminum imports from Argentina, Australia, Brazil, Canada, Japan, Mexico, South Korea, the European Union, Ukraine, and the United Kingdom. To avoid confusion with other tariff names, we will refer to these as steel tariffs and aluminum tariffs going forward. China’s tariffs on imports against the United States went into effect, as announced on Feb. 4. SourcesThursday, February 13The Trump Administration announced the Fair and Reciprocal Plan, a trade plan intended “to reduce [the United States’] large and persistent annual trade deficit in goods and to address other unfair and unbalanced aspects of [its] trade with foreign trading partners.” The White House said the trade plan would determine “the equivalent of a reciprocal tariff with respect to each foreign trading partner.” To avoid confusion with other tariff names, we will use the reciprocal tariff naming for these specific tariffs going forward.  SourcesMonday, March 3The Trump Administration raised tariffs on imports from China from 10% to 20%. SourcesTuesday, March 4The United States’ 20% tariffs on imports from China go into effect. The United States’ 25% tariffs on imports from Canada go into effect. The United States taxed Canadian energy imports at 10%, rather than 25%. The United States’ 25% tariffs on imports from Mexico go into effect. SourcesChina announced tariffs of 10%-15% on U.S. farm and food exports and added 10 U.S. companies to its unreliable entity list. SourcesChina - Government Documents (1, 2) Reuters (1, 2)XinhuaCanada announced 25% tariffs on many U.S. imports. The Canadian government said the tariffs would cover U.S. goods worth C$30 billion (~$20.7 billion) immediately. SourcesWednesday, March 5 The Trump Administration paused tariffs on cars coming into the United States from Canada and Mexico for one month. According to White House officials, the pause happened after President Trump spoke with leaders of Ford, General Motors, and Stellantis. SourcesThursday, March 6The Trump Administration paused tariffs on some products from Canada and Mexico that are compliant with the USMCA (United States-Mexico-Canada Agreement), a free trade agreement. White House officials informed media outlets that 50% of Mexican imports and 38% of Canadian imports are compliant with the USMCA.  SourcesMonday, March 10  As announced on March 4, China began imposing 10-15% tariffs on many farm products from the United States, including soybeans, wheat, corn, beef and chicken. SourcesWednesday, March 12 The United States’ 25% tariffs on steel and aluminum imports go into effect. Canada increased its tariffs on U.S. imported steel and aluminum products by 25%. The Canadian government said the affected products include tools, computers, servers, and display monitors, among other products. The tariffs would go into effect on March 13. The European Union responded with its own tariffs against the United States. The EU said that its countermeasures could “apply to US goods exports worth up to €26 billion.”SourcesThursday, March 13President Trump threatened the European Union with a 200% tariff on European alcohol. SourcesMonday, March 24The Trump Administration issued an executive order that would impose a tariff of 25% on imports from countries that import oil from Venezuela, starting on April 2. SourcesWednesday, March 26The Trump Administration announced a plan to impose 25% tariffs on imported automobiles and car parts, such as engines, transmissions, and electrical components. Tariffs would begin on April 3. The administration included exemptions for USMCA-compliant auto parts.SourcesThursday, March 27Industry impacts:Hyte announced higher prices due to incoming tariffs: Hyte blog Wednesday, April 2 Consistent with the Fair and Reciprocal Plan from February 13, the Trump Administration announced reciprocal tariffs on many countries. In addition, the administration announced a 10% tariff on nearly all countries. The administration said the 10% tariff rate would go into effect on April 5. The reciprocal tariffs would go into effect on April 9. As stated on February 13, the administration implemented different reciprocal tariff rates for many trading partners. Examples: Vietnam - 46%Thailand - 36%Taiwan - 32%Japan - 24%European Union - 20% The administration added a 34% reciprocal tariff to China, on top of the existing 20%, bringing the total to 54%.SourcesThursday, April 3As announced on March 26, the Trump Administration's 25% tariffs on imported automobiles went into effect. The administration delayed tariffs on automotive parts until a date no later than May 3. SourcesIndustry impacts:META PCs issued a statement about possible price increases: Statement Our fully custom 3D Emblem Glasses celebrate our 15th Anniversary! We hand-assemble these on the East Coast in the US with a metal badge, strong adhesive, and high-quality pint glass. They pair excellently with our 3D 'Debug' Drink Coasters. Purchases keep us ad-free and directly support our consumer-focused reviews!Friday, April 4China’s government said it will impose additional tariffs of 34% on U.S. goods starting on April 10. China announced export controls on several rare earth minerals. SourcesChina - Government Documents (1, 2)CNNTom’s HardwareIndustry impacts:Hyte published an update on price increases: Hyte statement. iBUYPOWER issued a statement about the tariff impacts: iBUYPOWER statement.Nintendo delayed Switch 2 pre-orders to the United States: Statement to IGN.Saturday, April 5The Trump Administration’s 10% tariff goes into effect for many countries, as announced on April 2. SourcesMonday, April 7Industry impacts:Framework paused sales of several Framework Laptop 13 models to the United States: Twitter statement. Tuesday, April 8The Trump Administration increased the tariff rate on imports from China by 50%. Through an executive order, the administration amended the reciprocal tariff rate for China from 34% to 84%. This tariff rate increase was in addition to the 20% tariff rate from March 4. SourcesIndustry impacts:Reports surfaced of Razer stopping laptop sales to the United States. Razer did not publicly confirm this, but U.S. consumers were unable to buy laptops on Razer’s website. SourcesWednesday, April 9The Trump Administration’s reciprocal tariff rates went into effect shortly after midnight. Later that day, with the exception of China, the Trump Administration paused many reciprocal tariffs for 90 days. The administration did not pause the 10% tariff on imports from April 5. China responded with an additional 50% tariff on U.S. imports. U.S. goods shipped to China now faced an 84% tariff, when accounting for the existing 34% tariff from April 4. The Trump Administration raised tariffs on imports from China to 125%.The European Union approved new tariffs against the United States. The EU said details would come later. SourcesIndustry impacts:Per a report in Nikkei, a newspaper in Asia, Apple requested suppliers to air ship premium devices to the United States before the April 9 tariff deadline. Framework increased prices and delayed some shipments to the United States: Framework blog Thursday, April 10 The Trump Administration clarified to reporters that the 125% tariff on Chinese imports was in addition to the previously announced 20%. The White House confirmed the tariff rate for imports from China is 145%. The European Union paused its tariffs against the United States. As announced on April 4 and April 9, China’s tariffs on imports from the United States go into effect.SourcesFriday, April 11 China increased tariffs on imports from the United States from 84% to 125%. China said the new tariff rate would go into effect on April 12. SourcesIndustry impacts:Per a report in Commercial Times, multiple OEMs paused laptop shipments to the United States. The reported companies included Dell, HP, and Lenovo. Mashable reached out to the three OEMs for comment; Mashable has not published a comment yet. Friday, April 11 - Saturday, April 12 On April 11, the US federal government published guidance stating that some electronics, including smartphones and computers, are exempted from the reciprocal tariffs. Media reported that the exemptions are intended to help U.S. technology companies like Apple. SourcesSunday, April 13 President Trump said the United States will announce tariffs on semiconductors soon. An administration official clarified that tariff exemptions for electronics are “temporary.” SourcesMonday, April 14In a meeting with reporters, President Trump said he may give tariff exemptions to automobile manufacturers. SourcesAssociated PressIndustry impacts:NVIDIA announced that it will begin building AI supercomputers within the United States: NVIDIA blogTuesday, April 15In a White House fact sheet, the administration said imports from China face tariffs of up to 245% on certain goods, including electric vehicles, when accounting for all previous tariffs. SourcesWhite House Fact SheetFriday, April 18The federal government announced fees for ships made in China destined for US ports. The fees could begin in October and increase over time. SourcesSunday, April 20The Chinese government warned countries about cooperating with the United States on trade at the expense of China’s interest. According to a translation via the BBC, the Chinese Commerce Ministry said, “China firmly opposes any party reaching a deal at the expense of China's interests. If this happens, China will never accept it and will resolutely take countermeasures.”SourcesTuesday, April 22The US Department of Commerce “determined that imports of solar cells from Cambodia, Malaysia, Thailand, and Vietnam are being dumped into the U.S. market.” The Internal Trade Commission, a separate agency, will make the final decision on tariffs. SourcesHelpful Timelines Visit our Patreon page to contribute a few dollars toward this website's operation (or consider a direct donation or buying something from our GN Store!) Additionally, when you purchase through links to retailers on our site, we may earn a small affiliate commission.Please consider watching our investigation for more information.

Features Insecure Code vs. the Entire RGB Industry | WinRing 0 Driver, ft. Wendell of Level1 TechsApril 28, 2025Last Updated: 2025-04-28We provide the rocky history of WinRing 0 and share how important it’s been to the PC industryThe HighlightsThe WinRing 0 driver has propped-up the fan control and RGB industry for over a decadeSecurity updates have broken WinRing 0’s codeThis has resulted in a mad dash for hardware vendors to re-develop RGB and fan control softwareTable of ContentsAutoTOC Our fully custom 3D Emblem Glasses celebrate our 15th Anniversary! We hand-assemble these on the East Coast in the US with a metal badge, strong adhesive, and high-quality pint glass. They pair excellently with our 3D 'Debug' Drink Coasters. Purchases keep us ad-free and directly support our consumer-focused reviews!IntroThere’s one piece of obscure 2007 code that has propped-up the entirety of the fan control and large parts of the RGB industry. It’s a driver called WinRing0, and now, the software that uses it to control hardware through Windows is breaking.If you're like us, you've always felt some sense of looming dread when you install a piece of software that controls fans or LEDs.There's something ominous about a half-baked app with a broken UI taking control of hardware in meat space.Editor's note: This was originally published on April 17, 2025 as a video. This content has been adapted to written format for this article and is unchanged from the original publication.CreditsHost, WritingSteve BurkeWriting, ResearchPatrick LathanVideo EditingVitalii MakhnovetsTim PhetdaraWriting, Web EditingJimmy ThangAs always, being pessimistic about this kind of thing has eventually paid off, with Hyte emailing us in March and The Verge posting a story about WinRing0 being flagged as a threat by Windows Defender (that article is worth a read for the statements provided by several developers). We contacted our own list of developers, and then reached out to Wendell from Level1Techs to help us talk through the technical aspects. This article explores the history and story of the WinRing 0 driver.History Part 1: WinRing0's CreationWinRing0 is a library originally released in 2007 by Noriyuki Miyazaki [宮崎 典行] (AKA hiyohiyo), and he regrets it.The developer is best-known for CrystalDiskMark and CrystalDiskInfo. According to the active GitHub repository, "WinRing0 is a hardware access library for Windows" and "WinRing0 library allows x86/x64 Windows applications to access I/O port, MSR (Model-Specific Register), [and] PCI." Basically, WinRing0, the driver, is a unique open-source window into hardware. Over the years, it's become the equivalent of that XKCD comic for small developers who can't afford to develop and certify their own loopholes for controlling hardware like RGB LEDs and fans. If you're part of a small team that wants to distribute software for monitoring or controlling any of the hardware in a PC, WinRing0 has been the go-to option.Hiyohiyo announced the end of development in February 2010, stating (in Japanese) that "WinRing0 is essentially a library that should not exist [...] I wanted to share the joy of low-level programming with as many developers as possible, so I developed and released WinRing0 after fully understanding the various issues, but I had no choice but to accept that this is no longer acceptable in today's age." He repeated that sentiment to us in an email, saying that "I consider it a complete youthful indiscretion on my part not to have accepted the changing times." The final update from hiyohiyo was WinRing0 2.0.0 in July 2010, where he intentionally removed almost all functionality, apologized again, and described the project (again, in Japanese) as a "big failure."There’s something sad about that sentiment. For better or worse, the WinRing0 driver was actually not a big failure: A ton of hardware companies transacting hundreds of millions of dollars in revenue have relied upon it; however, this is probably why hiyohiyo views it as a failure.Technical ExplanationGiven what WinRing0 is -- a method of low-level access to hardware -- it makes sense that hiyohiyo has distanced himself from the project so much, especially since he currently collaborates with Microsoft. The releases of Windows Vista in 2007 and Windows 7 in 2009 made it increasingly clear that Microsoft is no longer in the business of letting you f*ck around with this stuff: Windows was moving away from low-level programming. The idea of old-school unrestricted memory access is scandalous these days. As Martin Malik of HWiNFO stated to The Verge, "since the driver has access and doesn’t restrict the range, it can read/change other processes, secrets in memory or protected kernel registers. This is very dangerous." As hiyohiyo stated when closing WinRing0 development 15 years ago, "If you think about why the OS restricts access to I/O ports, physical memory, MSR, etc., and why signing kernel-mode drivers is mandatory since Vista x64, you will understand."We don't want to get too into the weeds here, but kernel-mode is the alternative to user-mode. We interviewed Wendell from Level1Techs, who went on to explain:“What is the kernel? [You may have] heard of the Linux kernel but Windows has a kernel, too. So the kernel is responsible for management of your system; so process management, memory management, hardware abstraction, security isolation, and system calls, which is like a programmer's calls, like the kernel is going to provide this programmer's interface. You call [it] as a programmer and then the kernel goes off and does something. And so the buck stops with the kernel. So your programs just run and they don't have to deal with things like, ‘which processor am I running on,’ ‘how do I allocate memory?’ It just says I would like to allocate memory and the kernel [asks] how much memory would you like and then you get an address and then that's all handled; memory management, all of the abstraction for all those kinds of things. So the kernel is really the smallest, lowest part of your operating system and it is typically engineered to be as uncomplicated as possible. It's only as complex as necessary to do the task and if it has bugs that leads to a lot of problems, not just in terms of system instability but also security issues and that sort of thing.Sometimes it's fun to think of it abstractly. Your computer is a bus and all of the apps on the bus are the passengers. The kernel is the driver of the bus and your computer hardware is like the engine, the wheels, the door, the brakes, and that kind of thing. The driver gets to decide how to use everything safely and effectively and if one of the passengers wet willies the driver then that's bad because it may put everybody in danger.”The only reason that analogy is a bit confusing is because Wendell uses the word “driver” to explain the operation of the vehicle and he uses the word bus to explain the vehicle. With that in mind, let's take time to explain WinRing0's namesake: security Ring 0. Wendell elaborates, “There's a lot of ring 0 drivers as it turns out. Ring 0…kernel mode. I'm not a Windows developer [as my] day job but kernel operating system…it kind of makes sense. The things that are close to the hardware are ring 0 and they're supposed to have a relatively low surface area. If you are running an application and the application does something bad, which is ring 3, I believe, the application crashes. If you're running something at ring 0 and it crashes, it has the potential to affect the entire system and so the entire system will crash. Windows blue screens are probably ring 0. What has really accelerated Microsoft giving the boot to ring 0 is the CrowdStrike thing. This has been a problem forever but the CrowdStrike thing taking out the vast majority of infrastructure that runs Windows and Crowdstrike…Microsoft sees this as a problem and so this is basically a casualty of war.Ideally you have things running in user mode ring three, all things running in user mode ring three. And so all of your software runs at ring 3 and the driver is very small and very low level and very lightweight and doesn't need to run quite as low level as ring 0 but is still sort of in the administrative permissions mode. But at a very low fundamental level, you can use software to update your BIOS and that is a pre-boot environment. You could have malware that lives in your BIOS. I would prefer having a motherboard that has a jumper so that when I want to re-flash the BIOS, I physically have to move a little switch to say yes.”When we brought up Asus Armory Crate, Wendell added, “It goes the other way too, the BIOS could run arbitrary software.”Kernel-mode drivers are almost always hardware device drivers, and within the x86 structure these (typically) occupy the highest security ring alongside the kernel: Ring 0. This is why a device driver literally named WinRing0 getting handed out to anyone who wants it might be a little alarming to Microsoft. As confusing as it is, Wendell's still pretty positive on the basic concept of security rings: “The ring 0, ring negative 1, ring 1…that’s all very tightly coupled with hardware features of x86 to provide isolation, which is great. There's different approaches from AMD and Intel, but there is there is a hardware aspect of this that is very nice for users as well so it's not just like you're entirely reliant on a 100% Microsoft software solution but a lot of this is how Microsoft has chosen to implement the various security levels but it dovetails with a lot of functionality that is at the hardware level, which is nice because the hardware is trying to protect you from code that shouldn't be executed.”Digital Signatures Visit our Patreon page to contribute a few dollars toward this website's operation (or consider a direct donation or buying something from our GN Store!) Additionally, when you purchase through links to retailers on our site, we may earn a small affiliate commission.Microsoft's method for mitigating those concerns has been to require digital signatures for kernel-mode drivers in all Windows versions since 64-bit Vista. A digital signature is a certificate issued by a "trusted Certification Authority" (CA) that verifies that: "the file, or the collection of files, is signed. The signer is trusted. The certification authority that authenticated the signer is trusted. The collection of files was not altered after it was published." Back when WinRing0 was first published, individuals (in Japan) could sign drivers themselves, which hiyohiyo did. More expensive and difficult-to-obtain Extended Validation (EV) certificates were required starting in the Windows 8 era, and they're only issued to businesses, but old drivers were grandfathered in.Over the years when installing a piece of software, you might have seen some kind of popup about the driver signatory, the lack or the presence of a signature. And we see this a lot with the prototype versions of software where they haven't signed it yet but as for why digital signatures are a useful idea in general, we turn again to Wendell who stated:“As part of Microsoft’s strategy to deal with…driver signing, in general, any kind of executable signing is actually sort of fun and interesting. It’s a fun and interesting way of approaching security. If you right click on basically any executable on any modern Windows system and you look at the properties, you can see that the executable is digitally signed. That's an identity thing [that indicates] this is from [a particular] company. Drivers are a great way to hide malware and so it has to kind of be a walled garden and so the certificates you have on a website are really not [too] different or the executables from programs are really not [too] different from what you have for a driver. Basically you create the driver. You submit it to Microsoft and well, the submit-it-to-Microsoft process doesn't actually technically have anything to do with signing, but theoretically, Microsoft looks at you as a company and says ‘Okay, yes, we're going to be able to do business with you.’ And you get something that you can sign that is trusted and it is it is the standard certificate signing process where [you say] ‘here is my certificate’ [and] I'm going to send this somewhere that will then say: ‘okay, yes, we are going to sign the certificate that you have asked for except instead of being based on a hash or something ephemeral, it's based on the hash of the actual binary of the driver.’ And so this driver with this hash has been signed and if somebody tampers with the driver or changes it then the cryptographic signature will no longer match and the driver doesn't work anymore and so it's a nice way to affirm that something has signed off on the contents of this driver and this driver is good.”Wendell also interestingly pointed out that CAs can be broken into and certificates can (and have been) stolen, but that's a subject for a different time.So, hiyohiyo apologized for pulling the plug and refusing to maintain WinRing0's certification back in 2010, seemingly with the expectation that its certification would be pulled and everyone's projects would break: "WinRing0 was discontinued without any alternative plan in order to avoid the worst case scenario of the signature being revoked" and  "if the digital signature for WinRing0 is revoked, all WinRing0-based applications will be unable to start in an x64 environment."History Part 2: WinRing0's AdoptionThat brings us to the second part of WinRing0’s history.WinRing0 actually became a foundational element of many, many projects, and some of those projects—like Open Hardware Monitor, later forked as LibreHardwareMonitor—would themselves become foundational to even more software on top of that. So there are nested layers of reliance on something that hasn’t really been even maintained or even liked by its original developer for 15 years. Seriously: You have very likely encountered WinRing0 in some capacity, and with the changes Microsoft is making for security reasons, a lot of those software encounters would no longer work today.And that’s for good reason: Over the years, hiyohiyo's concerns were repeatedly validated.In 2019, HP got in hot water for including WinRing0 pre-installed in its HP Touchpoint Analytics service "preinstalled on most HP PCs." This became a massive security concern from one of the biggest OEMs.In 2020, WinRing0 was named in another CVE, or Common Vulnerability and Exposure, for EVGA's Precision X1. In 2021, it was Crucial's turn. Even though specific software was called out each time this happened, HP, EVGA, and Crucial were using the same 1.2.0 version of WinRing0 that everyone else was. As GermanAizek put it to us, "The driver was made in 2007. CVE in 2020. Microsoft started blocking it in 2025. Vulnerability has been around for 18 years." As for why Microsoft hasn't blocked it before now, according to OCCT, "They haven't done it yet because big corporations were lazy enough to use it in their software in the past, so that would invalidate their own software, so they cannot do it right away."And the list of software that has used it at some point, and therefore software that has had vulnerabilities and attack vectors, is huge: CapFrameX (but not PresentMon), Precision X1, Crucial MOD, HP Touchpoint Analytics, SignalRGB, OpenRGB, and many more are on the list.The issue isn't that Precision X1 or Crucial MOD or any of the vast array of affected software (CapFrameX, OpenRGB, SignalRGB, at least some versions of Afterburner, et cetera) are compromised: the issue is that they install an insecure driver (WinRing0) that's then accessible to any other software that wants it, including malware. This is precisely what happened with actual malware SteelFox starting in 2023; the vulnerability is real and has been actively exploited for profit. This isn’t just some proof of concept, this is an actual, in-the-wild malware that has been used to illicitly make money. Calling it "theoretical," as CapFrameX did, is irresponsible and dangerous, and it's not really relevant whether the software that installs the driver is itself safe. To quote OCCT:"It's vulnerable as f*ck."And here’s what Wendell thought, “If you say the last time the driver was meaningfully updated was in 2008 and it has not yet been exploited by malware, then that's a miracle.” We had to interject and say that it has been exploited by malware. For another example of a Ring 0 driver problem (not WinRing 0), check out what Wendell had to say about Crowdstrike, “So what happened was Crowdstrike has a ring 0 malware detection driver and Crowdstrike is otherwise very good software. It's very effective at what it does. It's an interesting security architecture. They made a mistake in their software and as a result of the mistake, the system tried to jump to memory address zero or start executing memory address zero. I don't really remember exactly what the details were but it was something obviously incredibly stupid and there was no safety rails for anything at this level and so systems would crash. And it was an impossible situation because the system would [consistently] boot and crash. If you were lucky after the 20th or 30th time, it would do that, the system would notice and deal with it and so Microsoft is saying ‘this is the wild west. We’ve got to deal with this ring 0 problem immediately and software like CrowdStrike cannot run at ring 0. We as operating system vendors have to provide a lower level facility to let these software vendors do what they need to do but without compromising the integrity of an update process without compromising the integrity of a boot process to provide fallbacks' and that sort of thing. As a result of that…I mean, internally, Microsoft has known this is an issue almost since day one. They didn't care until millions of machines had very large problems, basically every crowd customer that got the update.”Beyond the current wave of Windows Defender alerts, WinRing0 and similar drivers also have a tendency to get flagged by software like Easy Anti-Cheat due to their ability to read and rewrite memory. You can make your own judgement about how serious the issue is, but these are not false positives. We want to make sure that’s clear. It isn’t a “false positive,” it’s just a true positive.As hiyohiyo stated fifteen years ago: "although a general-purpose hardware access library such as WinRing0 1.x is very useful for prototyping, developers would need to develop dedicated device drivers for public release." But there needs to be a better, secure solution to gain access to this control and hardware. There is one and there has been one. As a developer, the 100% proper by-the-books response to this (from talking to numerous people) is to drop WinRing0, develop your own dedicated driver for your specific product, and obtain a signature for it. This is apparently the path that EVGA took back in 2020 after that CVE we mentioned.  New signatures for kernel-mode drivers are really only accessible to large companies, though, with smaller dev teams unable to afford dedicating their time and money (in recurring payments) to the process, not to mention the software development work. Other manufacturers, including Hyte, have informed us that EVGA was somewhat propping-up fan control and RGB software by getting signatures on the driver. We’ve had a tough time trying to verify some of these claims, but that seems to be the belief held by, for example, Hyte. Therefore, WinRing0 has been eternally recycled and eternally frozen at vulnerable version 1.2.0. If you dig around in LibreHardwareMonitor's source code (for example), it references WinRing0.sys 1.2.0.5 from July 2008, which makes sense: hiyohiyo's next release included a reference in a patch note, saying that "it would have been an easy fix if only a digital signature could be obtained, but since the kernel mode driver cannot be updated, this was scrapped." According to Martin Malik of HWINFO64, this day of reckoning has been a long time coming, with Microsoft repeatedly warning that the driver would be blocked.Again, we've heard unconfirmed reports that EVGA possibly took up the maintenance for WinRing0's digital signature in the post-2010 era, possibly arranging for its renewal (as we understand that certificates expire over time) or just convincing Microsoft not to revoke it. If EVGA had any involvement, it probably ended in 2020 when the company stopped using WinRing0, or at least in 2022 when the company basically halted operation. Microsoft's statement to The Verge that "we are aware of reports about gaming and monitoring applications being flagged as a threat due to the use of unsigned versions of the WinRing0 driver" implies that the driver is now unsigned, which could be a further clue that EVGA was doing some kind of upkeep behind the scenes.Somehow, we continue to learn EVGA’s impact beyond its GPUs.The Future of WinRing0All of this is a problem, because there are limited tools to control hardware through the OS -- and for good reasons -- but there needs to be something, and currently, many of those tools are breaking or broken. Or insecure.That brings us to the future of WinRing0.The easiest solution to all this would be to patch WinRing0 itself. After hiyohiyo's last constructive contribution in 2009, Herman Semenov [Герман Семёнов] (AKA GermanAizek) took over maintenance in 2019, initially with the goal of optimizing crypto mining with access to CPU MSR registers. As he stated to us, "around 2023, many people wanted to build WinRing0 Windows driver themselves to increase mining hashrate, even though it was much more difficult than just mining on Linux."In a weird way then, crypto mining potentially provided something directly useful to those controlling hardware for non-mining use cases.Development accelerated in 2023 as other members contributed to the project, adding x64 support and fixing some BSOD triggers in the old driver. Eventually, the team applied patches to address the open CVE from 2020. Critically, this fork of WinRing0 remained unsigned: only the un-optimized, insecure version from 2008 had the valid signature vital to projects like LibreHardwareMonitor.This is where HYTE has stepped in. HYTE originally contacted us with the story, stating that it wants to take the version of WinRing0 that GermanAizek's team has been updating, submit it to Microsoft for signing, and fork LibreHardwareMonitor to integrate the patched, signed driver. HYTE would then take on the responsibility of paying Microsoft, basically replacing EVGA’s assumed role in this chain.The direct benefit is that HYTE's own software can continue to function, while the rest of the industry gets to keep using WinRing0 (and LibreHardwareMonitor) without getting auto-quarantined by Windows Defender.GermanAizek told us that "these fixes restrict the use of the driver only to programs running with administrator rights." This is certainly safer, but (as Martin Malik of HWiNFO warned The Verge), this just means that an app has to be run as admin before it can access the driver. We asked Wendell about this. Specifically about running things as admin and how much that might help. Here’s his response:“That's probably not unreasonable. Short of Microsoft getting involved and offering a better solution or somebody that is that deep in the Microsoft kernel driver developer ecosystem, that's probably what it would take: somebody that has very deep intricate knowledge of the operating system and also knows what the operating system is capable of. As far as I know, you're on your own to implement a lot of the functionality that would be needed to do that. So this driver is probably still your best hope to do that. Microsoft probably doesn't want to adopt the driver, which would also be a reasonable outcome. At the same time, Microsoft probably doesn't want to re-implement the functionality that's in the driver, but how this is usually done is you peel away the minimum functionality and you stuff that in your ring 0 driver and then you have all of the other stuff live somewhere else. And that ring 0 driver, you trust not to be able to be manipulated to access memory, it's not supposed to or write to a bus address that it's not supposed to be able to.”So, as Wendell helped us understand, the idea that a combination of patches and signatures can fix the root cause of the problem is arguably misguided. We contacted Franck Delattre of CPUID (CPU-Z, HWMonitor), who explained that CPUID has had similar difficulties with its own software. "In order to fix the problems, we had to move a big part of the user code into the kernel code, in the unique goal of reducing exposure. We could do that because only our code uses our driver, but for a generic driver like WinRing0, this was simply not possible since its functions were used in a different context by the different application. To go further, this means that no replacement of WinRing0 is possible, at least not with the same genericity that WinRing0 provided until today." In other words, the thing that makes WinRing0 uniquely useful is the same thing that makes it dangerous. GermanAizek is literally the frontman for the "fixed" version of WinRing0. He told us that "personally, I migrated to Linux and BSD systems because Windows has become really insecure, and as a Unix developer, such operating systems really seem convenient to me." He also openly asked that developers use the InpOut32 driver instead of WinRing0 (although we've seen other developers express concerns about that as well).OCCT has also announced that it will be providing a publicly-available but closed-source alternative to WinRing0, and it's possible that other organizations will follow suit.Wendell informed us that there are other bigger-picture alternatives, “For sensors and fan speed, one way that you could solve this architecturally is to just move it to a USB controller. That's slightly more cost or if somebody wants to build in a USB client interface then that's probably a marginal cost increase. I'm slightly surprised it hasn't gone in that direction but I'm also slightly surprised because this is a problem for Windows server in the context of the system management bus because servers need access to the system management bus and kind of hilariously, you have the out-of-band management that also has access to the system management bus so like servers have a whole other computer inside them that has access to the system management bus and the same controllers and so you can use that computer within a computer to monitor the sensors. You could just not have that and plug it into USB in the case of client computers. Like I say, we put important things on the system management bus and so like controlling CPU voltage probably should be on the system management bus. Controlling fan speed…You could probably do that through USB, but when it's through USB, the chipset and other things probably are not able to control fan speed. So you end up with a chipset that needs a system management bus so low-level parts of the system can make those controls but user overrides have to come through another path like through USB or something that's low security. Or Microsoft can provide a reasonable facility that is reasonably locked down to access the system management bus facility.”Conclusion Grab a GN15 Large Anti-Static Modmat to celebrate our 15th Anniversary and for a high-quality PC building work surface. The Modmat features useful PC building diagrams and is anti-static conductive. Purchases directly fund our work! (or consider a direct donation or a Patreon contribution!)That’s the story of how this small piece of code has supported an entire industry and its software for 15 years now, even in spite of its own developer disowning it and regarding it as not only a mistake, but a failure. We feel bad for hiyohiyo who now is powerless to stop people from using his youthful development project, but these multi-million and billion dollar companies have the resources to develop a responsible alternative. That includes Microsoft, Razer, and everyone else. That brings us around to what power an end user has, if any.Our recommendation is to do what your antivirus software says: if Windows Defender quarantines WinRing0, let it happen, and if anyone tells you to ignore the warnings, treat them with extreme skepticism. Some manufacturers and developers have called these “false positives,” but they are not. They are real positives, and there are real vulnerabilities that have been used which can exploit your machine.Microsoft appears to have paused the "ban" as of this writing, but it's only a matter of time. If everything goes according to plan, though, the patched driver should be usable soon thanks to HYTE, at which point you can decide whether requiring admin privilege for access meets your personal standard for security. For whatever it's worth, the Windows Dynamic Lighting RGB control feature continues to be developed, although it doesn't feel great to be railroaded into using it just because Microsoft bricked the alternatives. Still, it's probably the right direction for Microsoft with Wendell stating, “There is one aspect of this where Microsoft is doing the right thing and that is RGB control. Windows 11 allows you to control RGB directly in the operating system. Microsoft [shouldn’t take] half measures here and add some fan controls and or at least provide a programming interface. [Microsoft doesn’t] have to [provide] a GUI for fan control like it did with RGB control but wherever that's plumbed in, [Microsoft should] go ahead and plumb in the other stuff. It's really not any more complicated than that.”Thanks to the various developers that provided quotes for this piece, as well as Wendell.