OCCT Perestroika - 3.0.0.b04 released ! Stable : 2.0.1

[Tetedeiench]

Any reason why b05 monitors the temp of my 3rd core, but b07 doesn't?

That's weird. What happens if you restart OCCT and try to configure it yourself by clicking on the big orange button in the options ?

I didn't change many things from b05 to b07 regarding the CPU temps...

Do you see it appearing in the dropdown list in the option frame, or is it just not automatically detected ?

[Tetedeiench]

These are the file contents

LinPack Custom Test File (OCCT)
Intel(R) LINPACK data
1
21977
21977
65536
4

Can you doublecheck if the option "90% free mem" was really checked ?

Either my memory detection algorithm isn't right (but i can't see where it's wrong), either the option wasn't checked (which sounds ok, as 3.5GB of memory detected = 7GB at 50%, vista taking 1GB, which sounds Okay-ish).

I spent 1 hour playing with it, and i can't see where i'm wrong Can you doublecheck ? And be sure to select the 90% free mem option.

[Xope_Poquar]

That's weird. What happens if you restart OCCT and try to configure it yourself by clicking on the big orange button in the options ?

I didn't change many things from b05 to b07 regarding the CPU temps...

Do you see it appearing in the dropdown list in the option frame, or is it just not automatically detected ?

It's in there, just not automatically detected. I fixed it in the options, but the program by default didn't have it correctly set. Maybe just a fluke in my config?

[Tetedeiench]

It's in there, just not automatically detected. I fixed it in the options, but the program by default didn't have it correctly set. Maybe just a fluke in my config?

Okay, that helps me a lot

Can you do a screenshot of the temp list in the options showing the name of the Sensor please ?

With that i should be able to fix it

[nullface]

How credible are the volt graphs?

[karateo]

Can you doublecheck if the option "90% free mem" was really checked ?

Either my memory detection algorithm isn't right (but i can't see where it's wrong), either the option wasn't checked (which sounds ok, as 3.5GB of memory detected = 7GB at 50%, vista taking 1GB, which sounds Okay-ish).

I spent 1 hour playing with it, and i can't see where i'm wrong Can you doublecheck ? And be sure to select the 90% free mem option.

Actually with the latest beta 0.07b it works!
I don't have any more the 0.04b that I had the problem with.

If you haven't changed anything on linpack from 0.04b to 0.07b then it's probably my mistake, sorry.

[Xope_Poquar]

Weird, this time it's not even seeing my 4th Core and it was set default to GPU.

[BababooeyHTJ]

I would love a stress test with error checking for dual gpu's. That would be great. I love OCCT, btw.

[Tetedeiench]

Weird, this time it's not even seeing my 4th Core and it was set default to GPU.

This seems to be a bug with the SDK i'm using. I'll report it ASAP. I'll check my autodetection routines, but what may happen is that the autodetection took place when the core temp #3 wasn't available ni the list for some reason.

Could you read this thread again tomorrow, or send me an email so that i can contact you directly if you don't want to follow this thread ? This bug is critical, and as it involves 3rd party, i may have to send you a debug version so that we can audit the problem, probably by getting a debug function ready

email : iench 'atttt' ocbase dot com.

[cirthix]

Windows Server 2003 32 or 64-Bits ?

Did you try making a profile under the ATI driver ? I know you need one to get the SLI working for Nvidia, i don't know about ATI though.

I really have to look at those profiles, i wonder if i can temper with them programmatically without screwing everything.

Too bad i don't have an ATI SLI configuration :/

32bit, crossfire is working as per 3d06 scores (18.6k for q6600@3.6+3870x2@850/1050)

[Tetedeiench]

32bit, crossfire is working as per 3d06 scores (18.6k for q6600@3.6+3870x2@850/1050)

Yes, but SLI isn't "i work - i do not work". 3dmark2006 shows god scores because a profile for this app exists in the Catalyst drivers, telling which mode to use for this particular applicaton.

Right now, there're no profile at all for OCCT GPU in any display driver... that's why SLI isn't working with OCCT GPU. I don't have control on it.

I'm looking into the Nvidia display driver mechanism, it seems easy enough. I'll have to look into the ATI one to automatically add a profile for OCCT GPU.

[Fungus]

I used nHancer to create a profile for it. ATITrayTools should have a similar function.

[Tetedeiench]

I used nHancer to create a profile for it. ATITrayTools should have a similar function.

That's my thought, really. I wonder where are the contacts in Nvidia and ATI for profile management...

[jmke]

got Asus P5K and E8400 here, it reads CPU speed 2Ghz ? CPU is clocked at stock speeds (3Ghz) though

[nullface]

How credible are the volt graphs?

Anyone?

[Tetedeiench]

OCCT PT 3.0.0.b08 OUT !

Changelog :

• The EXACT Linpack formula for Problem Size <-> Memory used has been found - OCCT Exclusive ! (This caused "no CPU Usage" bugs on this test under Vista (experienced here !).
• OCCT GPU does not force the resolution anymore - It can be run in window, fullscreen mode,...
• OCCT GPU in "error detection" mode now is now multithreaded - the checking algorithm will exec on several CPUs
• If your CPUs cannot check that many frames per second, OCCT GPU will now adapt dynamically its speed, instead of "just at the beginning".
• CPU Usage is now correctly calculated (it was minored in some cases (Linpack mostly)
• CPU Usage in Power Supply mode is now the sum of the CPU Usage of both tests (Linpack and GPU3D, not just Linpack)
• The display is only refreshed once per second, instead of once per 1/4s.
• The Linpack default mode is now Max stress instead of Mid.

Enjoy !

http://www.ocbase.com/download.php?fileext=beta

[Tetedeiench]

got Asus P5K and E8400 here, it reads CPU speed 2Ghz ? CPU is clocked at stock speeds (3Ghz) though

The CPU speed will jump up as soon as you launch a test. Speedsztep, C1E and other technologies are probably active (and they are by default).

[Tetedeiench]

Anyone?

They are as "credible" as your Volt sensors are. Personally, i rely mostly on the drops and fluctuation rather than the value displayed, but that's just me.

[cantankerous]

OCCT PT 3.0.0.b08 OUT !

Changelog :

• The EXACT Linpack formula for Problem Size <-> Memory used has been found - OCCT Exclusive ! (This caused "no CPU Usage" bugs on this test under Vista (experienced here !).
• OCCT GPU does not force the resolution anymore - It can be run in window, fullscreen mode,...
• OCCT GPU in "error detection" mode now is now multithreaded - the checking algorithm will exec on several CPUs
• If your CPUs cannot check that many frames per second, OCCT GPU will now adapt dynamically its speed, instead of "just at the beginning".
• CPU Usage is now correctly calculated (it was minored in some cases (Linpack mostly)
• CPU Usage in Power Supply mode is now the sum of the CPU Usage of both tests (Linpack and GPU3D, not just Linpack)
• The display is only refreshed once per second, instead of once per 1/4s.
• The Linpack default mode is now Max stress instead of Mid.

Enjoy !

http://www.ocbase.com/download.php?fileext=beta

Awesome! Thanks a ton for this!

One thing I have been wondering on just about every OCCT release. Very minor, but would it be possible to have the ability to list 3 special voltage, instead of just the default two? Perhaps add an extra line for a 3rd option? I would like to monitor my NB/VTT AND DRAM volts, not just two of the three. Again, very minor but hey, thought I would ask!

Keep up the great work!

[fireice2]

cant complete my download.

[stasio]

Direct link

[fireice2]

thanks.

[strange|ife]

OCCT!!

[nullface]

They are as "credible" as your Volt sensors are. Personally, i rely mostly on the drops and fluctuation rather than the value displayed, but that's just me.

Ok becorse i get some nasty spikes on vcore both negative and positive spiks. And it makes me a bit uncomfterble, my 5v is going crazy too looks like this "\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/" and spreds over 0.5V, if you understand what i mean. Will add pictures if requested.

[BababooeyHTJ]

Ok becorse i get some nasty spikes on vcore both negative and positive spiks. And it makes me a bit uncomfterble, my 5v is going crazy too looks like this "\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/" and spreds over 0.5V, if you understand what i mean. Will add pictures if requested.

If you have any of that asus adware crap instaled like pcprobe that comes with with the driver cd that could be your problem. I had that happen too then a clean install later without that crap and all was well.