OCCT Perestroika - 3.0.0.b04 released ! Stable : 2.0.1

[icecold316]

Is GPUmemtest to be trusted? I'm getting errors all over the place with my gtx280 which seems to be stable in all the games I play

Same for me. My Gtx260 throws shows 40,000+ errors.

[Tetedeiench]

How come LinX is able to load all 8 threads 100%? Maybe check with dualist to see how he was able to do that. OCCT is great now, it just needs to be able to load 8 threads on the i7 with linpack and it would be perfect!

He's just launching two linpack, i guess. Nothing proves that this is better than launching only one, at the moment I guess i'll implement that feature later on, but really, i don't think that a really good idea

[Tetedeiench]

Same for me. My Gtx260 throws shows 40,000+ errors.

Yes, GPU: Memtest isn't reliable at all on GTX260/280 and cards of the same generation. I couldn't test it at all on those cards.

I guess that's what comes of limited access to test hardware

[stasio]

Any changes in beta1?

[Tetedeiench]

I'm centralizing betas in my own board - much less hassle for me

http://www.ocbase.com/forum/viewtopic.php?f=5&t=19

[stasio]

Thanx

[Tetedeiench]

For those with GTX260 and such cards and GPU:Memtest problems : are you using XP or Vista ?

I suspect a problem with Nvidia's implementation in GT200 Vista drivers, as i've got a few GT200 users under XP without problems...

[Tetedeiench]

For those with GTX260 and such cards and GPU:Memtest problems : are you using XP or Vista ?

I suspect a problem with Nvidia's implementation in GT200 Vista drivers, as i've got a few GT200 users under XP without problems...

For those who still wonder, this problem seems to be due to a bug in GT200 drivers under Vista, not to a bug in my test

I'm working on it with Nvidia

GT200 users, if you want to give a shot to GPU:Memtest, it works fine with Windows XP !

[Tetedeiench]

OCCT PT 3.0.1.b02 fixes the GPU:Memtest problem encountered by GT200 users under Vista.

More info centralized over there :

http://www.ocbase.com/forum/viewtopic.php?f=5&t=23

As usual, the download link : http://www.ocbase.com/download.php?fileext=beta .

It has been reported as ok with GT200 and vista.

YOU NEED 181.22 OR HIGHER DRIVERS FOR IT TO WORK

[Ket]

Are there any final release versions in sight yet?

[003]

Tetedeiench, I think nvidia has gimped your GPU test in the 182.05 and 182.06 drivers! With 181.22, the GPU test would get my GTX280 up to 46C+, but now on 182.05 it won't break 34C, the idle temp. FurMark still hits 45C+.

EDIT:
I'm on water of course.

[xaver]

OCCT 3.0.1 final
http://www.ocbase.com/perestroika_en/index.php?Download

[Tetedeiench]

Tetedeiench, I think nvidia has gimped your GPU test in the 182.05 and 182.06 drivers! With 181.22, the GPU test would get my GTX280 up to 46C+, but now on 182.05 it won't break 34C, the idle temp. FurMark still hits 45C+.

EDIT:
I'm on water of course.

Can you tell me more ? (OS especially ? )

i'm using a GTX260, XP32, and 182.06 drivers, and GPU:OCCT (from version 3.0.1, which haven't changed a bit since 3.0.0) still runs perfectly fine and reaches about the same temp than furmark ...

Perhaps you left the Error check mode enabled, which load the GPU much less, which is, for now on, normal (unfortunatly).

[Tetedeiench]

OCCT 3.0.1 final
http://www.ocbase.com/perestroika_en/index.php?Download

I came here to announced it

It especially fixes the GTX260/Vista problem, which was due to a CUDA limitation under vista which i can't yet explain and thus label as a bug.

Be sure to use 181.22 drivers, at least.

[phsinc1]

my 8800gts 640mb fail the gpu memtest in the pass 2 .... it always doesn't detect errors in pass 1, but can't complete pass 2, I tried to manually change it to only make 1 pass, and it passes, I make the test again and again but just manually, I did it 5 times and it doesn't show any errors.
games are working fine.
I'm using 182.06

[003]

Can you tell me more ? (OS especially ? )

i'm using a GTX260, XP32, and 182.06 drivers, and GPU:OCCT (from version 3.0.1, which haven't changed a bit since 3.0.0) still runs perfectly fine and reaches about the same temp than furmark ...

Perhaps you left the Error check mode enabled, which load the GPU much less, which is, for now on, normal (unfortunatly).

I think you're right, now that I have error check disabled, it seems to be working normally again, with one small quirk. It is reporting a lower GPU temperature than EVGA Precision 1.4 by about 6 degrees. I don't remember this problem on the 181.22 drivers, but I may just have a bad memory. I'm using XP x64 SP2.

[Tetedeiench]

my 8800gts 640mb fail the gpu memtest in the pass 2 .... it always doesn't detect errors in pass 1, but can't complete pass 2, I tried to manually change it to only make 1 pass, and it passes, I make the test again and again but just manually, I did it 5 times and it doesn't show any errors.
games are working fine.
I'm using 182.06

I recently discovered that G80 aren't compatible with Cuda 2.0. You need G84 or better cards. Sigh.

This is seriously starting to hinder the GPU:MEMTEST usefulness for me, and i'm looking into CUDA alternatives... i may have fallen onto something though. Stay tuned.

[Big Myke]

I'm using version 3.0 and I ran the PSU test and my computer powers off within 5 seconds of testing. Does this mean I have an insuffient powersupply or the PSU is crapping out on me. I should say that my computer powers off after 4 mins of playing crysis. I absolutely have no issues with temperatures on my motherboard, CPU and video cards.

Current specs
PC power and cooling 1000W
e8400 @ 4.2
4 gigs of ram OCZ
Striker II extreme
285 gtx in sli

[stasio]

Three weeks ago released another version:

OCCT 3.0.1a.b01

[TiTON]

Hey guys..

I have been using OCCT to stress my CPU, but having issues with it on the GPU.

Setup:
AMD Phenom II 940 BE
Silverstone Zeus
Gigabye 790GX mobo
(2) AMD 4870 (CF)
Windows Vista 32.

I can run the CPU just fine, but I can't do GPU.

The program complains that I'm not running Direct X 9, and something about Cuda.

Since I'm running Vista, I have DirectX 10, and Cuda shouldn't matter since I am on AMD / ATI Gpu.

Any suggestions?


- Ton

PS - dude.. i love the logging feature!! Graphs and CSV.. it is awesome.

PSS - Just installed 3.0.1ab01, and sitll have the issue.

[stasio]

OCCT needs an updated DirectX9 to be able to properly run. Vista comes with DirectX 10, and only 10. If you update DirectX10, you only update DirectX10, and not 9.
Go to the microsoft website, and update DirectX. Easiest way is to go to google, and search for "dxwebsetup.exe".
This should be the best way, and has a validation required :
http://www.microsoft.com/downloads/d...displaylang=en
If you don't want the validation, you can always get the redist version, but it is a bit more cumbersome (download the whole thing, extract the directory manually, go there, and launch the setup file) :
http://www.microsoft.com/downloads/d...8-9f20f1244a8e

[TiTON]

Stasio - thanks for the update. I will give it a shot later tonight.

- Ton

[stasio]

OCCT 3.0.2.b02

* CPU:Linpack now supports Hyperthreading. Just make sure the HT checkbox is checked.
* The "Hyperthreading as dual-core" checkbox as been renamed as "Hyperthreading". Simpler, and much easier to understand.
* The Hyperthreading Checkbox is now checked by default for the CPU:OCCT and CPU:Linpack tests if your CPU supports HT. It will only be so on the first run, of course. If you uncheck it, OCCT will remember it.

[Angmaar]

This program is an awesome all in one tool for overclocking. The gpu test heats my gpu to the same temperature as furmark. The only thing this program would need is a gpu clock/voltage adjustment panel (like EVGA precision). Good job this program rocks!!

[khamo]

Tetedeiench
I have been using your program in varoius versions since jan 2008 and what an awesome job you have done with the development. Love the 3.0.1 version. The test mode under Linpak and OCCT is greyed out whenever I first launch (vista 32 bit, even launch as administrator) but becomes available after runing with default setting on the first run. Is this intentional or am I doing something wrong?
Ok, I just had to change the test type to custom ! lol