It means your DirectX 9 version is too old. OCCT requires DirectX 9 from March 2008 or newer, even under Vista.

You can manually check it easily : just look for the file "d3dx9_37.dll" in the following folder "<Windows dir>\System32".

If it is not present, just download the latest DirectX9 update for your OS and everything should run fine afterwards !

OCCT (stands for "OverClock Checking Tool) is a CPU stability testing program, developped by myself.

Its features :

• 3 different test types
  • CPU = no RAM tested, alot of heat generated on the CPU, errors are usually CPU-centered
  • RAM = Maximum error detection, tests the whole chain CPU-Chipset-Memory
  • Mix = CPU and RAM alternated
• 3 tests modes
  • Auto = 1h long Mix test
  • Custom (Infinite) = Infinite loop of the test type of your choice
  • Custom (fixed) = A test of the type of your choice, and of a duration of your choice
• Integrated monitoring and System information thanks to CPU-Z and HWmonitor engine
• External Monitoring Program support through plugins (Everest, Speedfan, and many more)
• Graph output showing temperatures and voltages of your computer

Here's how to translate OCCT in a foreign language. Just click on "to be continued" to get the full explanation (it is too big to be in the FAQ as is)

to be continued

My advice would be to lower your CPU frequency, or do anything that can make your computer stable under OCCT.

OCCT stresses components alot. If an error was detected, your computer can generate those. they may happen everytime, usually under heavy loads. Thus, by ignoring this warning, you can have unexpected behaviour, for instance while playing, or while encoding a video...

Sometimes, this error isn't noticeable ( for instance, if in one frame of your favorite fps one point is not at the right spot, you probably won't notice it, and it won't crash your game). Sometimes, it is really noticeable ( if it happens in a critical CPU process, blue screen ! or if you were encoding, your video file will be corrupted).

I really advise you not to ignore OCCT's warning.

As said before, generating errors is a random task. So, if your computer is unstable, the error might be generated at the beginning of the test, and on the second run, much much later. However, tests tends to behave the same, mostly, and errors happens usually around the same time. Not always, but usually. if OCCT detected an error, you can stop there : there's a problem with your computer !

Right now, OCCT is reliable. No known bug will detect an error if there isn't. So if OCCT detects an error : something is wrong.

However, generating errors is random. There are cases where the computer is unstable and OCCT won't detect it. Usually, the longer the test, the higher the chance of detecting an error. For alot of people, 30 minutes-long tests are enough. You can jump to 2 hours or more if you want to double-check. Some people are known to test their computer for 24h !

OCCT currently supports Speedfan, Motherboard Monitor 5 and Everest. Systool support is also planned.

In order to add support for another monitoring app, i have 2 requirements

• This app has to be able to run on my own computer (I own a gigabyte motherboard, so exit Asus Probe and others for now :()
• It needs to have a "Shared memory" feature, or anything to access the values from outside the application. Without it, it's still doable, but much much much harder, and especially not as reliable ( one update and support might be gone )

As of now, i have no means of getting test hardware, especially motherboard. I even created OCCT on a Single-core CPU ! So as of now, i'm kind of stuck :( Maybe later. If the software you want support for fills the 2 requirements above, send me a mail to iench at ocbase dot com, i'll see what i can do :)

You probably have a processor with Intel's HT Technology ( Hyperthreading ).

This technology emulates 2 CPUs when there's only one.

However, this is just virtual, and for testing purposes, not relevant. Thus OCCT detects only one physical core, or processor, and uses it. Don't worry, your CPU is really at 100%, as displayed on OCCT !