Jump to content

How Long Should I Run OCCT For?

Over the last few weeks, I have found OCCT with error check enabled to be very helpful in finding a stable overclock for gameplay, however, I'd like some input on test settings, specifically testing duration and safety

 

I've been stress testing my ASUS Radeon 7950 HD with the following test settings:

 

  • Duration = 30 minutes
  • Idle periods = 0 at beg., 0 at end
  • DirectX version = DirectX11
  • Resolution = 1920x1080
  • Full screen = Enabled
  • Error check = Enabled
  • Shader complexity = 7
  • Memory used = Unchecked
  • FPS limit = 120 fps

Question #1:

 

After you've found your relative core and memory "maxes" using tests of shorter duration, how long do you like to run the final tests in OCCT (with error check enabled) to make sure that things are truly stable during game play?

 

Note: I think that 30 minutes in duration should be the minimum for final testing.

 

Question #2:

 

Using OCCT with error check enabled and with my settings listed above, how long in duration do you think I can safely run OCCT GPU stress testing?

 

Thank you!

 

BigDay

Link to comment
Share on other sites

Link to post
Share on other sites

didnt even know OCCT had a tool for GPU testing :D

 

but i would actually test the GPU with Heaven or Valley and let it run for a couple hours and look out for artifacts!

Usually when the OC isnt stable or something, you will find artifacts or crashes really soon though so 30mins is usually enough.

Gaming HTPC:

R5 5600X - Cryorig C7 - Asus ROG B350-i - EVGA RTX2060KO - 16gb G.Skill Ripjaws V 3333mhz - Corsair SF450 - 500gb 960 EVO - LianLi TU100B


Desktop PC:
R9 3900X - Peerless Assassin 120 SE - Asus Prime X570 Pro - Powercolor 7900XT - 32gb LPX 3200mhz - Corsair SF750 Platinum - 1TB WD SN850X - CoolerMaster NR200 White - Gigabyte M27Q-SA - Corsair K70 Rapidfire - Logitech MX518 Legendary - HyperXCloud Alpha wireless


Boss-NAS [Build Log]:
R5 2400G - Noctua NH-D14 - Asus Prime X370-Pro - 16gb G.Skill Aegis 3000mhz - Seasonic Focus Platinum 550W - Fractal Design R5 - 
250gb 970 Evo (OS) - 2x500gb 860 Evo (Raid0) - 6x4TB WD Red (RaidZ2)

Synology-NAS:
DS920+
2x4TB Ironwolf - 1x18TB Seagate Exos X20

 

Audio Gear:

Hifiman HE-400i - Kennerton Magister - Beyerdynamic DT880 250Ohm - AKG K7XX - Fostex TH-X00 - O2 Amp/DAC Combo - 
Klipsch RP280F - Klipsch RP160M - Klipsch RP440C - Yamaha RX-V479

 

Reviews and Stuff:

GTX 780 DCU2 // 8600GTS // Hifiman HE-400i // Kennerton Magister
Folding all the Proteins! // Boincerino

Useful Links:
Do you need an AMP/DAC? // Recommended Audio Gear // PSU Tier List 

Link to comment
Share on other sites

Link to post
Share on other sites

didnt even know OCCT had a tool for GPU testing :D

 

but i would actually test the GPU with Heaven or Valley and let it run for a couple hours and look out for artifacts!

Usually when the OC isnt stable or something, you will find artifacts or crashes really soon though so 30mins is usually enough.

 

Thanks for the reply!

 

I've used both of those tools before I used OCCT and they did not provide me with an accurate assessment of a stable overclock during game play. I'm using OCCT with error check enabled because I've found it to be superior in providing me with accurate assessments. There are errors that will occur in Heaven or Valley that you'll not be able to see, which may make your OC unstable during game play.

 

OCCT with error check is a great tool.

 

I will however use Heaven or Valley to assess and compare my benchmark score to my stable overclock score.

BigDay

Link to comment
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

×