Jump to content
Just now, TheGamingBarrel said:

No. Not at all.

So, say if I wanna oc my card to 1300 mhz on the core, I can do it and it's not going to have "slower response time" (I seriously don't know if that's even the right term to describe what I'm saying xD)

Link to comment
https://linustechtips.com/topic/540645-risks-of-gpu-oc/page/2/#findComment-7165351
Share on other sites

Link to post
Share on other sites

Just now, MarkoCroatiaMC said:

So, say if I wanna oc my card to 1300 mhz on the core, I can do it and it's not going to have "slower response time" (I seriously don't know if that's even the right term to describe what I'm saying xD)

No, and with a SeaHawk you should do better than 1300, seeing as the strix BOOSTS higher than that.

My current build - Ever Changing.

Number 1 On LTT LGA 1150 CPU Cinebench R15

http://hwbot.org/users/TheGamingBarrel

Link to comment
https://linustechtips.com/topic/540645-risks-of-gpu-oc/page/2/#findComment-7165358
Share on other sites

Link to post
Share on other sites

35 minutes ago, MarkoCroatiaMC said:

 

 

 

Also, my friends told me that if you oc a card, the faster you oc it, the longer "response time" it has. I think they meant as if I oc a card to around 1400 Mhz on the core, it will take longer time for my oc'd card to send a signal to my monitor (it will be slower), and my non-oc'd card will take shorter time to send a signal to my monitor. Is that true?!?!

No.

 

Once the card is done rendering the frame, it will hold it in its memory until the monitor tells the card that it is ready for the next frame. This is assuming that you have Vsync on. In between drawing the frames the card my do some Physx work or something while it waits for the monitor to be ready (I'm not 100% sure on how the Physx system is set up on Nvidia cards so don't quote me).

 

If you have Vsync off it will send the rendered frame to the monitor whether it is ready for the next frame or not. This is what causes screen tearing because the monitor is displaying part of one frame and part of the next.

Intel Xeon 1650 V0 (4.4GHz @1.4V), ASRock X79 Extreme6, 32GB of HyperX 1866, Sapphire Nitro+ 5700XT, Silverstone Redline (black) RL05BB-W, Crucial MX500 500GB SSD, TeamGroup GX2 512GB SSD, WD AV-25 1TB 2.5" HDD with generic Chinese 120GB SSD as cache, x2 Seagate 2TB SSHD(RAID 0) with generic Chinese 240GB SSD as cache, SeaSonic Focus Plus Gold 850, x2 Acer H236HL, Acer V277U be quiet! Dark Rock Pro 4, Logitech K120, Tecknet "Gaming" mouse, Creative Inspire T2900, HyperX Cloud Flight Wireless headset, Windows 10 Pro 64 bit
Link to comment
https://linustechtips.com/topic/540645-risks-of-gpu-oc/page/2/#findComment-7165567
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×