Question Screen Tearing

[kodydoty]

Hello, so im getting screen tearing in everything. Im getting tearing in all games, and media sites. I get screen tearing in Netflix, Hulu, and YouTube.
I have gone into the nvidia settings and turned off v-sync and there are no other reasons i can figure out.
The whole tearing thing is starting to piss me off... only thing i can think is the ram is taking a shit but i dont know totally.

Machine specs:
i9-9900k
RTX 2080
24GB Ram
No overclocking

Spoiler: System Information copy

OS Name Microsoft Windows 10 Pro
Version 10.0.17763 Build 17763
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-UJM8R8K
System Manufacturer Micro-Star International Co., Ltd.
System Model MS-7B12
System Type x64-based PC
System SKU Default string
Processor Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz, 3600 Mhz, 8 Core(s), 16 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 1.10, 9/27/2018
SMBIOS Version 2.8
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer Micro-Star International Co., Ltd.
BaseBoard Product MEG Z390 ACE (MS-7B12)
BaseBoard Version 1.0
Platform Role Desktop
Secure Boot State Off
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = "10.0.17763.529"
User Name DESKTOP-UJM8R8K\kodyd
Time Zone Pacific Daylight Time
Installed Physical Memory (RAM) 24.0 GB
Total Physical Memory 23.9 GB
Available Physical Memory 15.2 GB
Total Virtual Memory 35.9 GB
Available Virtual Memory 23.6 GB
Page File Space 12.0 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not InstantGo, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

 

[SkyNetRising]

Increase count of max pre-rendered frames and set vsync to adaptive (in Nvidia Control Panel).

 

[kodydoty]

Increase count of max pre-rendered frames and set vsync to adaptive (in Nvidia Control Panel).

What is a good setting for the pre-rendered frames?

 

[SkyNetRising]

Increase it by 1 - 3 from current value. This will smooth out frame-rate spikes/drops.

 

[kodydoty]

Well turning vsync to adaptive did not help the tearing so i dont know.

 

[SkyNetRising]

BTW - did you have a different gpu before this one? Did you reinstall GPU drivers with clean install option?

 

[kodydoty]

BTW - did you have a different gpu before this one? Did you reinstall GPU drivers with clean install option?

Yes i had a different GPU before this. Yes i did a clean install of the drivers

 

[SkyNetRising]

What model gpu did you have before?

By any chance - did you upgrade motherboard also? If yes - did you reinstall windows?

 

[fagetti]

what monitor

 

[failboat]

Is your monitor plugged into your gpu?
Can you post a picture of it?
Use HWMonitor to check for high temps on anything.

If you just bought something new you need to return it inside the RMA window.

 

[kodydoty]

I upgraded the MOBO. However i did not reinstall windows.

 

[SkyNetRising]

Motherboard upgrade is major hardware change. It is recommended to reinstall windows after this.

 

[kodydoty]

Yeah i decided not too because all of the drivers are the same as the old MOBO

 

[SkyNetRising]

What was your hardware before upgrade?

Even if you upgrade to same chipset motherboard, chipset drivers have to be reinstalled. This is bare minimum.
Next is GPU drivers. If you upgraded from Nvidia to Nvidia GPU, then it's enough to reinstall gpu drivers with clean install option checked. But, if you upgraded from AMD to Nvidia, then AMD drivers have to be removed with Display Driver Uninstaller first.
Remaining drivers from old system have to be removed manually using Device Manager.

With clean windows install you wouldn't have to do any of this.