PUBG is having hard lag issues with low frame rates
PUBG is having hard lag issues with low frame rates
Smoke from games is making my computer go slow, dropping down to like 1 or 2 frames per second. I've noticed this isn't always happening, but sometimes it happens when I look at my wattage settings for my 3080 Ti. The drops only come when I hit more than 330 watts. Most of the time it stays under that, but if I look around or move things in smoke, the wattage slowly creeps up to over 330 watts. It freezes the game and never crashes. I have a laptop and play PUBG on it, but I've never had this smoke problem before.
Follow these steps one after another. First, turn off your internet. Then, remove the GPU driver using DDU and don't restart your computer yet. Finally, delete every processor from the Device Manager (you probably have 16 of them). When it asks you to restart, say no and keep going until everything is gone.
Follow these steps one by one carefully: First, turn off your internet connection. Then, remove the GPU driver using DDU but do not restart yet; click No when asked to restart and keep going with removing all processors in Device Manager. Also, uninstall AMD Chipset Software from your Control Panel if it is there (skip it if none exists). Next, restart your PC to go back into BIOS mode. Disable AMD Fast TPM and Secure Boot if you had them enabled before, save and exit the BIOS. Go back in again and flash the latest BIOS update. After that, load default or optimized settings inside the BIOS so you can disable CSM (Chipset Support) and enable Above 4G Decoding plus Resizable BAR if your graphics card supports it. Save and exit the BIOS to go back into Windows. Then, install the newest Chipset driver; aim for version 4.03.xx or newer, then restart. To finish uninstalling the old AMD software, open Control Panel again, find "AMD Chipset Software," and make sure it is already version 4.03.03 before continuing. Finally, download the latest NVIDIA driver and connect to the internet. *Do all of this without an internet connection until you reboot after installing the chipset driver; you might need another BIOS boot later to set XMP (and keep your other settings).* If you have only two RAM sticks, put them in slots A2 and B2. Download any highlighted files before starting step one and follow each step in order. Open Command Prompt as Administrator and run chkdsk /x /f /r to fix file issues on the hard drive. Then run sfc /scannow to check for system errors. Also, make sure your Windows Update is up-to-date (unless you specifically want an optional update), then turn on Hardware Accelerated GPU Scheduling in your NVIDIA graphics settings and restart again. Make sure every Power Supply Unit (PSU) cable connected directly to the GPU uses just one PCIe cable per slot; use a main power cable, not a split branch from somewhere else.
Thanks again, and I'll try that tomorrow once I'm back home. I'll also update you later.
Right now I am in the FTPM section where I can choose between switching to an AMD TPM or changing its state. Both of those options need to stay turned off.
Great help, things are working fine now. There were a few bumps earlier when my computer would crash, but I think it was because of my CPU speed set too high at 4.4 GHz. I lowered it to 4 and haven't had any crashes since. Also, the smoke smell never comes back!
so did you follow every step in the right order? if you're not sure, save this guide for later. The real thing is after everything finishes, make sure GPUZ shows Resizable Bar, Above 4G Decoding, and Hardware Acceleration Graphic Scheduling are all turned on. For the CPU clock, you might find the PBO option and turn it on instead of just letting it downclock automatically (let the clock go to auto, then enable PBO or try advanced if you want to undervolt using Curve Optimizer). Also, maybe consider trying enabling SR-IOV (often in PCIe settings) and IOMMU (sometimes under AMD CBB options) 😹
So PBO is actually what clocked at 4.4 and made it keep crashing. Now I have PBO on, but I said it to 4.0 and haven't had an issue yet. Either that or it was my XMP profile. I had it set to 4.250 the last time. Either way the stock on this was 3.6 I believe