Anyone overclocked their TP2

[quick99si]

Quick update... I just uninstalled OCT1.5 using SKTools and doing a force uninstall. The only two traces left is the "OCT" key in the registry and the "OverClockTool" directory, but they're both completely empty of course.

[gera229]

Originally Posted by Maxx134

Only when reading & writing, like when the app is saving a file, first opening a file,etc.
You may not notice as it also will depend on the card and at most we are prob looking at maybey a half sec worst case average but that is a broad guess as there are just too many variables.

File list is the only big difference I see. Read is similar, but write I don't think it will matter a lot and when playing like games "save data" won't be that long to write nor will it lag it in any way anyway.

And file list is what? The list that appears when you open up file explorer?
Or what is file list?
Yeah as long as its faster than stock by a lot then I am more than happy. It's not something to compare with OCT and I think wimospeed wins hands down anyways.
"windows" folder loaded in 8 seconds on overclock and 9.5 secs on stock speed. But with OCT it may be faster, but if file list is just and ONLY that(the list it loads in file explorer) and not based on and does not affect the performance of app, games, network, and other performance then I won't bother since file explorer file is is the ONLY thing that's affected. But you can correct me if I am wrong.

[CalltheHogs]

I have over clocked now for about 2 months works great over clocking at 729 MHz. One issue that I can't find a fix for is occasional black screen shut down a reboot fixes it but it can happen at any time for no reason. Anyone else having this issue?

[quick99si]

Originally Posted by CalltheHogs

I have over clocked now for about 2 months works great over clocking at 729 MHz. One issue that I can't find a fix for is occasional black screen shut down a reboot fixes it but it can happen at any time for no reason. Anyone else having this issue?

The problem you're experiencing is the common SOD aka screen of death. Search around the forums for possible culprits and fixes, but it seems that WiMoSpeed does not have the same issue. I've been using it without an SOD for a long time, but that may not mean much since I didn't get it with OCT either.

If you like OCT, I recommend you try my settings for a few days and see if the problem persists. It's possible that the cause is related to so much more besides the settings, but it's worth a try IMO.

(this is going from memory, so the order won't be right)
Interval 2000ms
Max speed 729.x
Steps 2
Step load set to 0% and 100% (effectively disabled)
Jump load set to 3% and 30%

Here's the reg file that I've used to auto-configure this after hard resets.