Search the Community
Showing results for tags 'performance patch'.
Found 12 results
-
Adblock: Google did not slow down and lag YouTube performance with ad blocker on
hellowalkman posted a topic in Front Page News
Adblock: Google did not slow down and lag YouTube performance with ad blocker on by Sayan Sen Back in November, the internet was abuzz with conspiracy theories of Google purposely slowing down YouTube on Mozilla Firefox while its own browser, Chrome, would work fine. However, those rumors were shot down soon after as Google explained that it was not just Firefox that was the subject of "suboptimal viewing" experience and that it was happening irrespective of the browser. Google put the blame on "installed ad blockers." Fast forward two months, now in January we just had another similar incident with several user reports online of YouTube being slow with adblockers. As is usually the case in these instances, most netizens of course were quick to once again point the finger at Google. The issue was first brought to attention by Reddit users and the thread blew up with many more chiming in to say they were experiencing a similar thing. As it turns out, the bug was not YouTube or Google and was in fact a problem with Adblock and Adblock Plus' recent update Version 5.17.0. Hence if you were using something else like uBlock Origin (like me), you probably did not notice any slowdown. Adblock Plus developers noted the issue as performance regression on its GitLab repo. It wrote: Recently, ABP released version 3.22 which upgraded the bundled extension engine version to 1.1.1. AdBlock released version 5.17.0 which also updated the extension engine to version 1.1.1. We've had several reports of slow response time since the update. It appears to be an issue in the extension engine since ABP, AdBlock, and the EWE test extension all seem to experience a similar issue with the 1.1.1 version of the extension engine. The issue has now been fixed with the latest eyeo's Web Extension Ad Blocking Toolkit (EWE) version 1.1.2, where the breaking change has been reverted. Name: @eyeo/webext-ad-filtering-solution New version: 1.1.2 Reverted "Content filters are now updated via the history.pushState() event, when single page apps navigate using the browser's history API (EE-14, EE-90)". Breaking changes: None. Other changes: Reverted performance regression. Hence, if you are one of those users who is experiencing issues with Adblock and Adblock Plus, you should update your extension. It is also advised not to run multiple content filters or adblockers on your browser if you are facing performance issues. As an online publication, Neowin too relies on ads for operating costs and, if you use an ad blocker, we'd appreciate being whitelisted. In addition, we have an ad-free subscription for $28 a year, which is another way to show support! -
Microsoft getting serious about fixing Windows 11's slow File Explorer, freezes, crashes
hellowalkman posted a topic in Front Page News
Microsoft getting serious about fixing Windows 11's slow File Explorer, freezes, crashes by Sayan Sen Windows Insider builds are like a box of chocolates as one never fully knows what they are gonna get. For example, some users have noticed that the new Outlook was automatically installed on the latest Beta channel build. This was not disclosed in the release notes though a senior Microsoft official confirmed it was expected behavior. The announced changes list though also has some important improvements and fixes that many will likely appreciate. Microsoft seems to be making a conscious effort to improve the File Explorer performance in Windows 11. Back in 2021, when Windows 11 was new, Microsoft acknowledged that there were problems and promised better performance in 2022. Again in 2022, Microsoft's Panos Panay reiterated the company's new OS was all about delivering the "highest quality". Earlier this year, the tech giant also expressed in detail the performance improvements it delivered over the last year. The firm notes that it fixed a memory leak issue related to File Explorer Home which means load times should be quicker. The release notes say: We made some more improvements to help with the performance of loading Home. Also fixed a memory leak related to Home that would grow each time Home was refreshed or accessed. The latest Dev build, among other File Explorer improvements, notes multiple upgrades related to performance as well as crash fixes: Fixed an issue where rapidly opening two File Explorer windows might make explorer.exe crash. Made a few more fixes to help improve File Explorer launch performance, including fixing a leak which would impact performance over time. Fixed an issue which could make explorer.exe crash when navigating away from Home. Fixed an issue where trying to open Gallery after new images had been added might result in a crash. Fixed an issue where the progress wheel in the tab would get stuck showing that File Explorer was loading a folder when the loading had actually already finished. In case you are not aware, Microsoft has published a new redesigned File Explorer and it is based on WinAppSDK (WinUI). However, there are several reports suggesting it is rather sluggish in overall performance and responsiveness. It has also been proven to be true when more in-depth tests were conducted vs. Windows 10. Funnily, users recently discovered a full-screen (F11) bug recently which ironically boosted the performance. -
After AMD's RT fix, Nvidia outs hotfix to resolve Ratchet & Clank DirectStorage stuttering
hellowalkman posted a topic in Front Page News
After AMD's RT fix, Nvidia outs hotfix to resolve Ratchet & Clank DirectStorage stuttering by Sayan Sen Ratchet & Clank: Rift Apart came out on PCs this July and as is often the case, the launch has had its fair share of issues on both AMD and Nvidia. Surprisingly, Intel, which released its driver first among the three, might be the least affected. On the AMD side, Vega GPUs had a rendering issue where the characters' legs wouldn't render. This visual bug was resolved with game update version 1.727.0.0 Hotfix. Ray tracing also had problems on Radeon's RX 7000 series cards, which too, was resolved with a special driver update version 23.10.23.03. Over on the Nvidia side, users reported performance loss and stuttering with DirectStorage 1.2 enabled. The title is only the second one to feature Microsoft's modern storage API. The company claims it has fixed the issue with a hotfix driver, version 537.09 (download link below): GeForce Hotfix display driver version 537.09 is based on our latest Game Ready Driver 536.99. This hotfix addresses the following issue: [Ratchet & Clank: Rift Apart] Performance fluctuations due to issues between DirectStorage and some in-game settings Nvidia has also explained that this is sort of like an emergency release without its WHQL certification and so if users are unaffected by the issue, they could wait for the next such release. The GeForce Hotfix driver is our way to trying to get some of these fixes out to you more quickly. These drivers are basically the same as the previous released version, with a small number of additional targeted fixes. The fixes that make it in are based in part on your feedback in the Driver Feedback threads and partly on how realistic it is for us to quickly address them. These fixes (and many more) will be incorporated into the next official driver release, at which time the Hotfix driver will be taken down. To be sure, these Hotfix drivers are beta, optional and provided as-is. They are run through a much abbreviated QA process. The sole reason they exist is to get fixes out to you more quickly. The safest option is to wait for the next WHQL certified driver. You can download the driver at this link (it's a .exe application file). It works on both desktops and notebooks on Windows 10 and 11. -
VirtualBox major update fixes TPM crashes, Windows 11 graphics bugs, Mac performance issues
hellowalkman posted a topic in Front Page News
VirtualBox major update fixes TPM crashes, Windows 11 graphics bugs, Mac performance issues by Sayan Sen Oracle has released today a major update for VirtualBox with the latest version 7.0.10. The changelog states there are general improvements related to the Oracle Cloud Infrastructure (OCI), as well as performance issue fixes in the VMM (Virtual Machine Manager) for macOS Ventura. On the Windows side of things, graphics bugs pertaining to Windows 11 guests are fixed, and a crash-fix related to TPM (Trusted Platform Module) 1.2 has also been added. Meanwhile, Linux kernel 6.5 and 6.4 support is here. For those that have never used it, VirtualBox is a free tool you can install on your computer to run other operating systems. For example, if you run Windows but want to use Ubuntu, VirtualBox lets you use Ubuntu within a window on Windows. The full release notes are given below: This is a maintenance release. The following items were fixed and/or added: OCI: Introduced general improvements VMM: Fixed sluggish performance starting with macOS Ventura 13.3 (bug #21563, bug#21596) VMM: Fixed a bug while walking page tables while executing nested VMs causing flooding of the release log as a consequence (Intel hosts only, bug #21551) GUI: Added general improvements TPM: Fixed a crash when a VM has a TPM version 1.2 configured (bug #21136, #21515) Guest Control/VBoxManage: Fixed parameter "--ignore-orphaned-processes" Guest Control/VBoxManage: Fixed behavior of how handling argument 0 for a started guest process works: One can now explicitly specify it with the newly added option "--arg0". This will effectively restore the behavior of former VirtualBox versions Audio: Also use the PulseAudio backend when pipewire-pulse is running instead of falling back to ALSA (bug #21575) NAT: Adjusted UDP proxy timeout from 18-21 to 21-24 range to respect intended 20 second timeout (bug #21560) Linux Host: Added initial support for Indirect Branch Tracking (bug #21435) Linux Host: Added initial support for kernel 6.5 (NOTE: Guest Additions do not support kernel 6.5 yet) Solaris Host: Introduced general improvements in the installer area Linux Host and Guest: Improved condition check when kernel modules need to be signed Linux Host and Guest: Added initial support for RHEL 8.8 (bug #21692), 8.9 (bug #21621) Linux Guest Additions: Fixed issue when kernel modules were rebuilt on each boot when guest system has no X11 installed Linux Guest Additions: Added initial support for kernel 6.4 Linux Guest Additions: Fixed issue when vboxvideo module reloading caused kernel panic in some guests (bug #21740) Linux Guest Additions: Introduced general improvements in the installer area Windows Guest Additions: Introduced general improvements in graphics drivers area You can download the latest VirtualBox 7.0.10 update via Neowin or by visiting the official website itself. -
AMD finally fixes high idle power, VR performance issues with 23.7.1 Windows WHQL driver
hellowalkman posted a topic in Front Page News
AMD finally fixes high idle power, VR performance issues with 23.7.1 Windows WHQL driver by Sayan Sen Update: AMD has acknowledged the issue still remains. While AMD Radeon RX 7900 series GPUs, namely the RX 7900 XTX and 7900 XT, offer better value now compared to Nvidia, especially at the prices they are selling for currently (~$700 for 7900 XT and ~$900 for 7900 XTX), a couple of high power draw issues plagued these otherwise excellent video cards. In instances of video playback and multi-monitor connections, both the 7900 XTX and XT exhibited very high power consumption (via TechPoweUp). AMD fixed the video playback power issue in December last year with driver version 22.12.2, and today, with the latest driver, Team Red has also fixed the multi-monitor high power draw issue. Alongside the power bug, AMD claims it has also resolved performance issues with virtual reality (VR) games and apps. The full changelog for Windows WHQL driver version 23.7.1 is given below: Highlights Support for additional Vulkan® extensions. VK_KHR_cooperative_matrix for Radeon™ RX 7000 series VK_KHR_ray_tracing_position_fetch for Radeon™ RX 6000 and newer series VK_KHR_video_decode_h264 VK_KHR_video_decode_h265 VK_KHR_video_decode_queue VK_KHR_video_queue VK_EXT_device_address_binding_report VK_VALVE_mutable_descriptor_type VK_EXT_mutable_descriptor_type VK_EXT_dynamic_rendering_unused_attachments Fixed Issues Certain virtual reality games or applications may encounter suboptimal performance or occasional stuttering on Radeon™ RX 7000 series GPUs. Application crash or driver timeout may be observed during playback of AV1 video content using DaVinci Resolve™ Studio. Improvements to high idle power when using select 4k@144Hz FreeSync enabled displays or multimonitor display configurations (such as 4k@144HZ or 4k@120Hz + 1440p@60Hz display) using on Radeon™ RX 7000 series GPUs. Intermittent corruption may be observed playing WWE 2K23™ on some AMD Graphics Products, such as the Radeon™ RX 7900 XTX. Intermittent corruption may be observed after switching windows while playing Nioh 2™ on some AMD Graphics Products, such as the Radeon™ RX 6800 XT. Known Issues Application crash may be intermittently observed while playing RuneScape™ on some AMD Graphics Products, such as the Radeon™ RX 5700 XT. Intermittent corruption may be observed around some player models while playing Hatsune Miku: Project DIVA Mega Mix+™ on some AMD Graphics Products, such as the Radeon™ RX 6900 XT. Stuttering may be observed while playing Call of Duty®: Modern Warfare® II with Radeon™ Anti-Lag enabled. As a temporary solution, users encountering this are recommended to disable the Anti-Lag in the per-game settings. Performance Metrics Overlay may report N/A for FPS on various games. Display signal may be lost after switching windows on certain Adaptive-Sync enable displays on some AMD Graphics Products, such as the Radeon™ RX 7900 XTX. Higher than expected GPU Memory Utilization when using certain Record and Stream settings such as Instant Replay. To download the driver, head over to AMD's official website. The driver supports Polaris (RX 400/500 series), Vega (something which will soon be in maintenance mode for ROCm), and all RDNA GPUs (RX 5000 series, 6000 series, and 7000 series). -
Microsoft brings performance boost with new DirectStorage 1.2 even on slower HDDs
hellowalkman posted a topic in Front Page News
Microsoft brings performance boost with new DirectStorage 1.2 even on slower HDDs by Sayan Sen Microsoft has released the latest version of its DirectStorage API. The new version, 1.2, brings some new features as well as bug fixes. There is also performance boost in store thanks to some changes made. With DirectStorage 1.2, Microsoft is bringing buffered IO mode. The company says it is in response to developers wanting to use the same code path, both on solid-state drives (SSDs) as well as hard disk drives (HDDs). HDDs operate on buffered IO mode since they have much longer seek times. The company writes: DirectStorage currently opens files in unbuffered mode. This allows us to avoid unnecessary copies, getting the data onto the GPU as quickly as possible. However, we heard from some developers that they’d like to be able to use the same code both on high-speed SSDs as well as legacy hard drives. The legacy hard drives require buffered IO in order to mask the long seek times. For this reason, we added the ability to configure DirectStorage to open files in buffered mode. Aside from buffered IO, a new GetCompressionSupport API has been introduced which adds the ability to query the decompression path used, whether it is the GPU or the fallback CPU path. The full changelog for DirectStorage 1.2 is given below: New Features Add support for enabling buffered file IO for use on HDDs that may benefit from OS file caching behaviors. Add IDStorageQueue2::GetCompressionSupport API to indicate what path the DirectStorage runtime will take when decompressing a supported GPU decompression format. Update dstorage.h and dstorageerr.h to be covered by the MIT License. Add Microsoft.Direct3D.DirectStorage.winmd, to ease generation of non-C++ bindings to the API. Bug Fixes Add "Reserved1" field to DSTORAGE_REQUEST_OPTIONS. This makes the in-memory layout of the structure more explicit, but doesn't actually change the layout from previous versions. Fix DSTORAGE_REQUEST_DESTINATION_TEXTURE_REGION for 3D textures. Fix scheduling issue that manifested when transferring uncompressed data from memory to buffers Performance improvements Move the copy after GPU decompression onto the compute queue for GPUs where this is faster. You can find more details on the official blog post here. -
AMD fixes Microsoft DX 11 Ryzen and Radeon performance issues on Windows 11 and Windows 10
hellowalkman posted a topic in Front Page News
AMD fixes Microsoft DX 11 Ryzen and Radeon performance issues on Windows 11 and Windows 10 by Sayan Sen Earlier today, we tested and published our own report evaluating some of the recent rumors of performance boost regarding ray tracing on AMD graphics cards. Although AMD fans would probably have loved to see some massive gains, things were more bad than good, at least in our test scenario. However, while that wasn't such a cheery situation, AMD's newest WHQL driver version 23.2.2 claims to fix certain performance issues on its Radeon RX 6000 cards and Ryzen processors in Microsoft's DirectX 11. The fixed issues section in the release notes for the latest driver mentions: Situational performance drop may be observed in DirectX® 11 based games on Radeon™ RX 6000 series GPUs using Ryzen™ processors. An interesting thing to note here is that the issue wasn't documented in previous AMD driver notes in the open issues section, and could explain why the company specifies that the performance bugs were "situational" as they may have been difficult to trigger or replicate consistently. Although AMD specifically mentions its 6000 series GPUs in the changelog, the company does not highlight any specific Ryzen family, indicating the issues were probably prevalent on all Zen-based systems. In related news, AMD also promised performance optimizations for Windows related to its new Ryzen 7000X3D processors. Besides that, Linux users also have something to cheer about as latest testing shows some enormous gains for Ryzen over the years. -
AMD's latest Windows 11 driver seemingly brings FineWine magic to ray tracing and much more
hellowalkman posted a topic in Front Page News
AMD's latest Windows 11 driver seemingly brings FineWine magic to ray tracing and much more by Sayan Sen Update: We tested the ray tracing performance boost rumors and the results were certainly somewhat interesting. At long last, AMD released drivers for its AMD Radeon RX 6000 series (RDNA 2) GPUs earlier today. The new driver, version 23.2.1, has some very notable improvements, which include fix for a launch error on Windows 11 22H2 for the 6000 series GPUs. AMD had already resolved the issue on its newer RX 7000 cards. And although AMD took a long time to finally release new drivers for its 6000 series GPUs, the wait was worth it for Radeon owners as the company highlights excellent performance gains with up to 27% improvement compared to the Windows 11 21H2 launch drivers. In other games, AMD says there is anywhere between 9 to 21% betterment. The tests were conducted on a Radeon RX 6900 XT. AMD says other Radeon 6000 cards will also benefit from the new drivers where the gains can be anywhere from as low as 6% on the Radeon RX 6400 to 20% in case of the more powerful cards and it makes sense as stronger GPUs face more driver overhead issues. And although not highlighted separately by AMD, some Twitter users claim that the new 23.2.1 driver has huge gains in terms of ray tracing, sometimes by up to 40%. However, these gains may only be confined to synthetic benchmarks like those from UL Benchmarks. Twitter user @JirayD says they gained around 37% performance on an RX 6900 XT in 3DMark's DirectX Ray Tracing feature test with the new driver compared to the older 22.11.2 driver. Meanwhile the Port Royal benchmark only saw a 5% gain. Another Twitter user DOer chimed in on the same thread claiming a 40% improvement, also on a 6900 XT. While the graphics side of things is looking bright for AMD, the CPU side though has had bad news earlier today. That's because stuttering and freezing issues related to fTPM have now begun affecting Linux, something which was Windows-only initially. Though there is some positive news for CPUs as well as AMD has confirmed that it recently fixed a high-severity security flaw in Ryzen Master. Source: AMD via Twitter (1) , (2) -
Linux could leave Windows 11 in the dust as Intel hybrid CPUs get further optimizations
hellowalkman posted a topic in Front Page News
Linux could leave Windows 11 in the dust as Intel hybrid CPUs get further optimizations by Sayan Sen Back at its Architecture Day 2021 event, when Intel shared the core design details of its Alder Lake CPU architecture, the firm stated that Windows 11 was optimized in a way to best take advantage of the Alder Lake's Performance Hybrid architecture and the new Thread Director technology that helps Windows 11 task scheduling. Following this announcement, head to head testing back in November 2021, indeed showed Windows 11 outperforming Linux quite easily thanks to the special optimizations baked into Microsoft's new OS. In fact, it was beating out Windows 10 too, even when using an older Lakefield CPU. Fast forward to August of 2022 and things are looking quite different than they were previously. Linux has since been optimized further with changes made under the hood to close the gap with Windows 11. The latest test on Ubuntu using Linux kernel version 5.18 shows an Alder Lake-S Core 19-12900K being barely any worse than when compared to a Windows 11 system. However, further optimizations are still being done according to a new patch by Intel's Linux engineer Ricardo Neri. The new patch basically talks about improving task scheduling between the Bigger P-cores (performance cores) and the Bug E-cores (efficiency cores). On processors with a mixture of higher-frequency SMT cores and lower- frequency non-SMT cores (such as Intel hybrid processors), a lower- priority CPU pulls tasks from the higher-priority cores if more than one SMT sibling is busy. Do not use different priorities for each SMT sibling. Instead, tweak the asym_packing load balancer to recognize SMT cores with more than one busy sibling and let lower-priority CPUs pull tasks. Removing these artificial priorities avoids superfluous migrations and lets lower-priority cores inspect all SMT siblings for the busiest queue. With this Linux can potentially leave Windows 11 in the dust depending on the kind of improvements the new optimization sees. Besides it will be beneficial either way since Intel's upcoming 13th Gen Raptor Lake as well as future 14th Gen Meteor Lake CPUs will all be employing the same Performance Hybrid-based design. Via: Phoronix -
Microsoft confirms Visual Studio, .NET broken for Windows 11 Insiders, fix incoming
hellowalkman posted a topic in Front Page News
Microsoft confirms Visual Studio, .NET broken for Windows 11 Insiders, fix incoming by Sayan Sen For a few days now, Windows 11 Insiders who develop using Visual Studio 2022 have been complaining about severe performance issues. According to user reports, some of the recent Windows 11 Insider builds including the 22H2 RTM build 22621 are affected. The issues however are not exclusive to Visual Studio and all .NET-based applications like Blazor, JetBrains Rider, among others, are affected. Form the reports, it looks like there is high CPU usage in the range of 90-100% which is causing the whole system to slow down making the apps unusable. Microsoft though is aware of the issues and it has confirmed that the problem stems from the Windows 11 Beta Channel. We're aware of high CPU/severe slowdown of Visual Studio and other .NET apps on (what appears to be) Windows insider builds in past 24 hours. We're actively investigating: https://t.co/10k5kkcFIC — David Kean (@davkean) June 23, 2022 It affects all apps on the machine, particularly bad for .NET-based apps. We have fix for this - your machine should automatically pick up the fix soon. — David Kean (@davkean) June 23, 2022 The company provided a temporary workaround of switching over to the Release Preview Channel. However, that probably won't be necessary as a patch has been deployed and will be rolling out soon. Are you developer on the Windows 11 Insider channel affected by this issue? Let us know in the comments below if the performance patch works for you. -
Intel's Speed Select Technology ironically hurting performance, but a fix is coming
hellowalkman posted a topic in Front Page News
Intel's Speed Select Technology ironically hurting performance, but a fix is coming by Sayan Sen Intel's Speed Select Technology (SST) is a power management solution from the company that allows users to manage core prioritization and frequency regulation depending on the workloads in order to improve performance and efficiency. However, as an Intel engineer has observed, there is performance regression by more than 10% in benchmarks with the mode enabled. And while it isn't stated, the impact in a real workload might be lower but it's still a cause for concern. The engineer further explains that the standard Linux PCI interface which is used here is causing the delay as it searches through hundreds of PCI devices, during mapping, that are attached to the system. For those wondering why the need to mention hundreds of devices here, that's because Intel SST is a complex solution and is only available in Xeons and not in the mainstream Core lineup. Since the root cause of the problem has been identified, the good news is that a patch that promises to fix this should be available soon via a future firmware if it isn't already out. The fix is a fairly simple one and will use the cached data that will speed up the search process. Here's what the full LKML message says: It was observed that some of the high performance benchmarks are spending more time in kernel depending on which CPU package they are executing. The difference is significant and benchmark scores varies more than 10%. These benchmarks adjust class of service to improve thread performance which run in parallel. This class of service change causes access to MMIO region of Intel Speed Select PCI devices depending on the CPU package they are executing. This mapping from CPU to PCI device instance uses a standard Linux PCI interface "pci_get_domain_bus_and_slot()". This function does a linear search to get to a PCI device. Since these platforms have 100+ PCI devices, this search can be expensive in fast path for benchmarks. Since the device and function of PCI device is fixed for Intel Speed Select PCI devices, the CPU to PCI device information can be cached at the same time when bus number for the CPU is read. In this way during runtime the cached information can be used. This improves performance of these benchmarks significantly. Intel launched SST back in 2019 inside Cascade Lake Xeon CPUs. The technology is quite versatile as it enables several options like setting core prioritization, base clock tweaking, and more. As stated above, SST is implemented in the firmware and carried out by the processor's Power Control Unit (PCU). For more information on SST, visit Intel's official site here. -
AMD Ryzen CPUs reportedly get a boost in Cyberpunk 2077 thanks to this unofficial patch
hellowalkman posted a topic in Front Page News
AMD Ryzen CPUs reportedly get a boost in Cyberpunk 2077 thanks to this unofficial patch by Sayan Sen A Redditor by the name 'UnhingedDoork' has made a performance patch for AMD Ryzen CPUs which enables utilization of the logical processors as well as the physical cores in CDPR's new extremely popular futuristic RPG Cyberpunk 2077. Apparently, the game, in its current state, does not seem to utilize Simultaneous Multi-threading (SMT) on AMD Ryzen CPUs while it does so on Intel processors. The patch, for the most part, is fine however another Reddit user 'CookiePLMonster' has slightly modified some values so that it plays better across different CPU architectures. Users on the Reddit thread are reporting much better frametimes and 1% lows post-patch and that makes sense since in the most CPU demanding scenes of the game, like while driving through Night City, the SMT must be kicking in to aid in the workload distribution and dispatch. Here's how the utilization of cores is on a Ryzen 9 5950X before and after the patch: A step-by-step guide (provided by u/chaosxk) on how to install the patch is provided below however, it is cautioned to proceed at your own risk and if any problems are to occur, revert back to the older values. Download HxD Hex Editor Find your Cyberpunk2077.exe, (GOG version is in Cyberpunk 2077\bin\x64) and (Steam: Steam\steamapps\common\Cyberpunk 2077\bin\x64\Cyberpunk2077.exe) Make a backup copy of Cyberpunk2077.exe just in case Drag Cyberpunk2077.exe to HxD, a bunch of hex numbers should appear (like 01 FF 0D, etc) Press CTRL+F, change column to Hex-Values Put in "75 30 33 C9 B8 01 00 00 00 0F A2 8B C8 C1 F9 08" in the search string without quotes, those values should be highlighted Copy "EB 30 33 C9 B8 01 00 00 00 0F A2 8B C8 C1 F9 08" without quotes Back in HxD right click the highlighted values and select "paste insert" to overwrite the above "75 30 33 ...." value, ie, after doing this, the "75"should be replaced by "EB"and the rest of the string values should remain unaltered. Now go to top bar and click the save icon logo Done You might require a system reboot for the patch to take effect. For those who prefer a video tutorial, here's one provided by u/qa3rfqwef: It is reiterated that if you face any issues after the patch just revert back to older values in the Hex Editor or the backup Cyberpunk2077.exe that you have created. That said, AMD Ryzen owners who proceed with the patch, feel free to let us know the results in the comments below. Ryzen before/after image via u/BramblexD