Nice work! I'm really liking the GPU test, is stresses my video card to the max, now I know I got a cooling problem with it and will RMA it for sure. I can finally supply some screen shots to EVGA customer support :D
Printable View
Nice work! I'm really liking the GPU test, is stresses my video card to the max, now I know I got a cooling problem with it and will RMA it for sure. I can finally supply some screen shots to EVGA customer support :D
Just tried 3.0.0.b07 GPU test. Ati tray tools showed that only one gpu was utilized (HD3870X2, crossfire enabled under server 2003). Both windowed and full-screen mode were tested.
The PSU test is stressing the CPU now, but OCCT now only sees 3 of my 4 cores (1, 2, and 4).
OK, the problem is with OCCT, it only detects 3.6GB of memory. I'll check as soon as possible what's going on... i wonder though.Quote:
Originally Posted by karateo
Windows Server 2003 32 or 64-Bits ?Quote:
Originally Posted by cirthix
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 :/
I hope you mean ATI CrossFire. LOL :DQuote:
Originally Posted by Tetedeiench
And thanks for your response on my previous post. I tested with nVidia 8600GT and it worked flawlessly. Need a 'CUDA enabled driver' from nVidia.
Thanks again. You make me love OCCT more and more... :)
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 ?Quote:
Originally Posted by Xope_Poquar
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 ?
Can you doublecheck if the option "90% free mem" was really checked ?Quote:
Originally Posted by karateo
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.
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?Quote:
Originally Posted by Tetedeiench
Okay, that helps me a lot :DQuote:
Originally Posted by Xope_Poquar
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 :)
How credible are the volt graphs?
Quote:
Originally Posted by Tetedeiench
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.
http://i232.photobucket.com/albums/e...her/asdf-3.jpg
Weird, this time it's not even seeing my 4th Core and it was set default to GPU.
I would love a stress test with error checking for dual gpu's. That would be great. I love OCCT, btw.
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.Quote:
Originally Posted by Xope_Poquar
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.
32bit, crossfire is working as per 3d06 scores (18.6k for q6600@3.6+3870x2@850/1050)Quote:
Originally Posted by Tetedeiench
Quote:
Originally Posted by cirthix
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.
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...Quote:
Originally Posted by Fungus
got Asus P5K and E8400 here, it reads CPU speed 2Ghz ? CPU is clocked at stock speeds (3Ghz) though
Anyone?Quote:
Originally Posted by nullface
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
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).Quote:
Originally Posted by jmke
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.Quote:
Originally Posted by nullface
Quote:
Originally Posted by Tetedeiench
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!
cant complete my download. :(
thanks.
OCCT!!:bounces::bounces:
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.Quote:
Originally Posted by Tetedeiench
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.Quote:
Originally Posted by nullface
Great program! My only problem is that the gpu test dosent work properly with error checking, but when in full screen it does work with crossfire! If I just had crossfire with error checking I would be in heaven. I just did the psu test and realized it's time to pop my pc p+c 750w back in that I just got back from an rma. Im getting a little much of a ripple with my BFG 800w, like ~1% to 1.5%.
Always ask, but don't mind if i answer by the negative answer, that's my credo !Quote:
Originally Posted by cantankerous
That's a thing that comes up from time to time : having more custom voltages and temperatures.
Right now, i'd personally keep the 2 custom voltages and not jump to 4. In fact, i have to stop at a particular step before releasing, otherwise OCCT 3.0 will never reach the stable stage ;) In a later version though...
I'm currently changing the server, and switching to a dedicated one, and the download process will be made completely new (as i've got to include a licence text (that nobody will read) and i'm not happy with all those people that cannot complete their downloads.Quote:
Originally Posted by fireice2
It should be available during the next week. Sorry about that, and stay tuned for more updates ;)
doh! :doh: didn't checkQuote:
Originally Posted by Tetedeiench
Fair enough. There is surely more important things to worry about than my suggestion. Thanks for the reply and at least keep my suggestion in mind for a future release.Quote:
Originally Posted by Tetedeiench
Thank you for this tool. :up:
I love this tool and consider it a must have tool, its a keeper and will always be in my little toolbox for when I test.
Great program, having all the features/tests/monitoring together is very handy!
Sorry, i was a bit busy the past days (been working on the new server, revamping the download page... etc).
I released two new versions, but didn't take the time to post them here, sorry about that.
So here's the new version with the changelog included (both are fused so you know everything from b08 to b10) :
OCCT PT 3.0.0.b10 OUT !
Changelog :
- Linpack test has been updated, and is now much harder on core i7s.
- DirectX 9 version is detected and if not recent enough, the tab is disabled and you've got an error message
- Cuda is detected the same way (but incomplete, as it reports OK on GeForce 7s, and yu need GeForce 8 or more to run it).
- OCCT won't enter the crazy mode anymore if you click the on and off buttons ni a loop
- Core number detection improved (but there's still a bug going on there, sometimes OCCT detects only 3 cores out of 4, 1 instead of 2...)
- Graph size option has disappeared (unused)
- A new option has appeared "Generate graphs", checked by default. Guess what it does if unchecked... it won't generate graphs ! :D
- Due to a few power supply deaths, the Power Supply test bears a warning the first time you click on it.
- The GPU test now works in fullscreen mode with ATI crossfire cards, and the window can be moved to another screen without crashing
- The window position is now saved and restored upon startup.
- The aboutbox now has the correct design
- The bottom of the main form now has the right design (shape, size, color).
Enjoy !
http://www.ocbase.com/download.php?fileext=beta
PS : the download page has been revamped, there shouldn't be any corupted download anymore ;)
Thanks a lot as usual!
Curious however, have you actually had reported PSU deaths from running said test?
I upgraded to a Core i7 system and for me the new Linpack test does not stress the CPU at all. All cores are idle and at 37°C. Should be a bug. Happens both in 32bit and 64bit mode.
Yes, mostly from no-name PSE, marked as 480W, and in reality they're more like 250W or so.Quote:
Originally Posted by cantankerous
I know for sure i killed a brand New Heden PSU 480W with this test. The PSU died in 30s and fortunatly, it only damaged the Integrated Ethernet card on the motherboard. The computer was brand new :D
The one from older betas worked ?Quote:
Originally Posted by MKroenke
If that is confirmed, i may revert to the older version... until i can get my hands on a Core i7 configuration (which won't be happening until ... a year or so).
If only i had access to test hardware other than my own computer...
In built software +12 V bug
I can confirm this issue, and add to it. In b10, neither the linpack test or the normal OCCT test loads the CPU at all. Have not tried the earlier betas.Quote:
Originally Posted by Tetedeiench
Hi
What does the error 'debordement de pile' mean? Got it after 18h of OCCT RAM (Larger) on 3 beta 10 on system below.
Thanks
Andy
Older betas worked, but did not create that much heat compared to BOINC oder Prime95. On Core2 systems Linpack created much more heat than anything else.Quote:
Originally Posted by Tetedeiench
In b10 specs in sig the gpu test does not work at all. Just does not start.
It will only start for me if I have Infinite selected.Quote:
Originally Posted by BababooeyHTJ
Edit: and check for errors off.
It should work with this one :Quote:
Originally Posted by 003
OCCT PT 3.0.0.b12 Out !
Changelog :
- Several graphical glitches were fixed
- the Linpack test is now working again
- The OCCT test has been updated - check it out ;)
- the GPU test now correctly works on Crossfire configurations and SLI config too (SLI needs a profile)
- A few warnings were changed (just made more explicit, really)
Enjoy !
http://www.ocbase.com/download.php?fileext=beta
mmmh, Quad-GPU crossfire, interesting.Quote:
Originally Posted by BababooeyHTJ
I made some heavy changes to the GPU test recently. Could you test it and tell me if it works :
- In windowed mode or fullscreen ?
- In error check mode ?
Keep in mind that it takes 1 min for the test to start in Custom and Auto modes (the test always starts after 1 min).
d'oh -- you should remind those of use that usually use Infinite. And, why?Quote:
Originally Posted by Tetedeiench
In error checking mode here, I get 15fps and no movement of the pattern -- but GPU temp goes up like it's under load.
Without error checking, I get 75 fps and the pattern moves nicely.
Same thing in full screen except it's 12.5 & 84 fps. And, why do you use a low res screen? 640x480!
(Video card in sig. -- eVGA 7900 GT KO RoHS, Zalman VP900CU Cooling, mild OC to 645 MHz)
Edit: Also -- a feature request. I usually run LinPak for a certain number of tests, not for a fixed amount of time. Can you include that option?
And, if I run 90% of memory it won't run (no cpu load). I'm assuming that you're not setting memory correctly for 32 bit XP with 4G of memory (IMU, less is usable because of reserved space for memory mapped PCI cards).
No, it was just 2 refrence HD4870 512mb on Vista x64. Really wish it worked. That would be the only crossfire stress testing tool with error checking.Quote:
Originally Posted by Tetedeiench
I have to ask, are you sure the temp monitoring is accurate? With OCCT 2b at least it seemed to not be.. said my E4400 was well into the 90s under load :eek: So I put a temp probe in and ran OCCT again, sure enough the CPU was nowhere near those temps (was about 73c)
If you launch directly OCCTGPU.exe by clicking on it in the folder <OCCT>\bin\OCCTGPU ? It should report an error.Quote:
Originally Posted by BababooeyHTJ
Your DirectX9 version is probably not up to date ;)
The temp monitoring from OCCT is as good as HWmonitor, which is integrated into OCCT ;)Quote:
Originally Posted by Ket
That's an internal error of OCCT. it can mean your system isn't stable, as well as being a bug of OCCT.Quote:
Originally Posted by powellandy
I'll try to reproduce it, however i don't have a quad-core system :/
Oh, and i apologize for the logn reply delay, i knew i forgot something.
Anything I can do to help?Quote:
Originally Posted by Tetedeiench
Andy
Voltage +12V(-12;-5) wrong and GPU temp missing.Quote:
Originally Posted by Tetedeiench
HWmonitor 1.12 has several issues to be fix :(
Btw,
When loading OCCT PT 3.0.0.b13 in WINDOWS 7,receive notes:
-Your DirectX9 isn't up to date.OCCT GPU and Power supply tests will be disabled.
-Your graphic card doesn't support CUDA.You need Geforce 8 or higher.GPU memtest will be disabled.
Possible bug reports
- How is OCCT 3b12 supposed to behave on clean vista x64 sp1 install. Says dx9 not installed and no GPU tests - is this normal - should I install dx9?
- How is linpack OCCT 3b12 supposed to behave on Hyperthreading Intel P4 630 (Prescott). System info says 1 core and running linpack test shows 100% CPU usage in OCCT but only 50% in Process Explorer. Using CPU OCCT test with hyperthreading box ticked gives 100% usage in both. Should linpack stress both 'cores'?
Andy
Those are not issues, but they need explanations ;)Quote:
Originally Posted by powellandy
* You have to update DirectX9 even on vista (it is DirectX10, but it does have everything for DirectX9 too). That's why OCCT is complaining ;)
* That's hyperthreading ;) I'll try to keep the explanation short & understandable. Hyperthreading causes your OS to see twice the real amount of real cores on your system (for instance, if you've got 2 cores, Windows will see 4). However, you can view those 4 cores as "2 are real, 2 are "benefits only" from HT". So if you load the 2 real cores, and the 2 others are IDLE, you'll see, In the task manager, 50% workload. In reality, you'll have both of your physical cores loaded, and no benefit from HT taken. Those 50% means "95% of the real horse power of your CPU", to keep it short.
OCCT CPU test has 2 different behaviours :
* Without HT as DC, it will launch one test per physical core (i.e. "real" core). Thus you'll see 50% load, even if 95 or so% of your CPU is busy.
* With HT as DC checked (by default, as it proved more efficient on HT CPUs), OCCT will launch one test per core, physical or logical (i.e. real and "fake" cores). You'll see 100% workload in the task manager.
The linpack test has only one mode : 1 test per real core. Thus the 50% in the task manager.
The hard part is understanding that only half of your cores in the task manager are "real", and that the others represent the benefits from HT.
OCCT PT 3.0.0.b13 OUT !
Changelog :
- OCCT CPU Test fixed : Now the mode "large data set" works on core i7s
- A message now warns you to use fullscreen mode when you're using SLI/Crossfire. I'm currently working on the profile part in Nvidia's SLI (you do need one). Crossfire should be already supported flawlessly.
- Fullscreen mode is checked by default if you're using SLI/Crossfire, even in Auto mode
- Going back to "Auto" mode doesn't make you switch back to 500x500 anymore. 1024x768 is instead used, as intended.
- The Linpack test is now working again with 32 bits OS with more than 2GB of memory installed.
Enjoy !
http://www.ocbase.com/download.php?fileext=beta
Can someone with a crossfire confirm me that everything is well in Fullscreen mode with the GPU 3D test, even in error check mode ? Thanks !
Tetedeiench,
What are ci7-1, ci7-2, ... versions? Are they specifically made for core i7?
I see that italian translation is incomplete.
If you need an help, I am available. ;)
Quote:
Originally Posted by kiwi
They were debugging versions for the CPU OCCT problem. I'm currently deleting them :D
That would be great ;) I'm not done yet, but there will be alot of translation changes soon ;)Quote:
Originally Posted by Brama
There was an error in b13, i forgot to remove a debug message. It has been fixed and reuploaded ;)
OCCT PT 3.0.0.b14 OUT !
Changelog :
- The linpack test now works with 32 bits OS with more than 2GB of Memory
- OCCT's way of remembering window position as been changed for some people for which it didn't worked
Enjoy !
http://www.ocbase.com/download.php?fileext=beta
Quote:
Originally Posted by Tetedeiench
Thanks for this. I know what hyperthreading is... Just wanted to ensure it was working the way it should.... which it is! Thanks :D
Cheers
Andy
I can probably check that tomorrow at some point for you, stability testing a different system atm.Quote:
Originally Posted by Tetedeiench
I confirm I am available for translation of OCCT 3 from english to italian.Quote:
Originally Posted by Tetedeiench
If you need my help, let me know here or by a PM. :)
I've got so much to read and answer, sorry about the long reply delay ;)Quote:
Originally Posted by davidk21770
Error checking mode : this behaviour is normal. OCCT GPU checks the 3d output by comparing to a reference frame that was recorded a while ago. Thus, i disable all movement to be sure i've got the same rendering for each frame.
More, CPUs aren't capable of checking alot of frame per seconds. To prevent the CPU from dropping frames because the pile is full, i limit the fps to 15, which is already not bad. And for that, i augment the complexity of the scene. That's what you see at the beginning. It may happen if the pile is full : OCCT will then augment the complexity to avoid dropping frames (and thus, not cheking the results).
What do you mean by low-res screen ? You can configure it in OCCT's UI ;)
As for the linpack "run a fixed # of loops", yes, it is planned. I don't think it'll be done for 3.0.0 (i want to stop implementing features to be able to release a stable version), but in 3.0.1, i'll definitly think about it, as well as, in this case, outputting the GFlops value calculated by linpack.
Sorry to ask you, but can you send me your email by PM or to iench 'attttt' ocbase 'dot' com ? I'm usually communicating by email with people doing translations ;)Quote:
Originally Posted by Brama
Thanks ;)
OCCT PT 3.0.0.b15 OUT !
Changelog :
- News version of Linpack test : can someone checdk with XP 32 bits with more than 2GB of memory ?
- The Linpack test isn't limited to 2GB of memory on 64 bits systems. It was successfully tested on a 16GB memory computer - it takes about 13s to allocate all that memory :D
- The tab order is now correct in the option window
- SLI detection fixed : it should now work and enable fullscreen by default in GPU and Power Supply tests
- The warnings about SLI and Powersupply test now shows correctly (i.e. only once).
- Fixed several errors (invisible for you all) preparing for the translation process
Enjoy !
http://www.ocbase.com/download.php?fileext=beta
@Tetedeiench: thanks for the update!
OCCT PT 3.0.0.b16 OUT !
Changelog :
- The linpack test is now working again with XP32 with more than 2GB of memory
- the TAB key now works everywhere, and the order has been fixed
- The Temperature line is drawed in front of the CPU Usage line, in the graphs. This leads to better lisibility of the graphs.
Enjoy !
http://www.ocbase.com/download.php?fileext=beta
Just started playing with OCCT ... really like it. I have two questions, pertaining to the first system in my sig:
1) For some reasons, it's not showing the 5V reading for the Power Supply ... it shows disabled, and there is no 5V setting showing up when I do the drop down menu. It does show ... and looks okay with PC Probe II (I read earlier that it's best to remove this app ... haven't done that yet). Also, I pass the PSU test fine.
2) When I run the GPU MEM test, it passes - but shows a large number of errors. I think I also read that this may not work for ATI GPUs ... is that still the case?
It happens to me too, with an ATI X1900 and Catalyst 0812.Quote:
Originally Posted by shazza
No errors with my second PC with a Nvidia 8800 GTS 512.
This is a problem with the CPU-Z hardware detection routine used. I have the same thing (with an Asus Maxiumus 2 Formula). I PM'd the chap at canard PC who writes it and he said he was looking into it....Quote:
Originally Posted by shazza
Cheers,
Andy
Thanks, Brama and Andy ... good to know it's not just me. I googled for the 5V issue, but couldn't find much.
Since it passes all tests, and everything seems very stable, guess I'll keep on going.
1) Somebody else already answered this :) I can't do a thing about it unfortunatly.Quote:
Originally Posted by shazza
2) GPU memtest will always work - but reports the number of errors found. I'm not happy with the current state of this test, and it will be revamped soon. Right now, don't put too much trust in it ;)
Thanks very much for your answers, Tetedeiench. Just happy to know it's not indicating a problem with my system. I'll be donating some $$ for this excellent application.
Can't wait for a final version of OCCT v3, liking how its shaping up :up:
Thanks for your support :) I'm getting closer and closer, but i've still got some work to do - translation stuff, OCCT Test, 1 core missing problem, and 4GB memory under XP.
As soon as all that is fixed, it's going stable ;) Expect a new beta by tuesday (if i've got enough time, and i do hope so)
Just downloaded the .b16 beta and I noticed the GPU:OCCT and Power Supply tabs do not work for me. They are grey where the others are red.
Your DirectX9 version isn't up ta date, that's why ;) OCCT displays a message telling you to update it... you clicked OK too fast, i guess ;)Quote:
Originally Posted by clo007
Oh, and there are 2 known bugs :
- Linpack test is not working fine on some sstems with ore than 4GB of memory on 32 bits OS
- OCCT Test will report a "error : memory cannot be read" if an error is detected. It only occurs when an error is detected. It is fixed in b17, but this release isn't ready yet ;)
Thanks for the heads-up. When i get home from work today I will try to resolve this.
ok, who uses more then 4gb on a 32bit OS? :shrug: :rofl:Quote:
Originally Posted by Tetedeiench
me :)Quote:
Originally Posted by ThugsRook
me too :)
EDIT: Well when using XP, dual boot Vista x64/32bit XP.
What does the extra memory get used for? Seems like a waste since it comes in 1 or 2 GB sticks you could drop to 4 by just pulling 2 sticks? And the OC would be much easier.Quote:
Originally Posted by ThugsRook
PAE lets you use all of itQuote:
Originally Posted by davidk21770
Ahhh... Thanks. I considered it for the extra gig on my system but read that could be quirky so I filed it away (forgot about it ;)).
Well... Them.Quote:
Originally Posted by ThugsRook
In fact, i shoudl have said "More than 2GB". Sorry for that mistake ;)
no chit?Quote:
Originally Posted by cirthix
i thought PAE lets you use 4gb on 32bit, i didnt realize you could use more :shocked:
linky?
> sorry for going slightly OT :confused2
Interesting...how do you get all of the voltages and temps displayed and recorded? The earlier version had two additional recording options.
Is it possible to get OCCT to record while not running a test. It would be nice to get a normal application load graphed for comparison.
On my Vista 64 system it reports an obsolete version of DirectX 9 is installed. I believe I have the lastest and 3DMark06 has no problems.
You can configure the monitoring options, and OCCT can record up to :Quote:
Originally Posted by DavidNJ
- 4 CPU temps
- 4 GPU Temps
- 2 Custom temps
- 4 "basic" voltages (vcore, 3?3, 5 and 12V)
- 2 "custom" voltages
OCCT cannot record without a test running. I had a few people asking for this feature, but i didn't want to implement it yet, as OCCT isn't a monitoring program per se, it is a stability testing program ;) I'm not decided yet if i will do so.
You probably don't. Just check if you've got the file D3DX9_37.dll in your windows\system32 folder. Under Vista, you have to install DX9 for it to work (i have to admit i'm not using vista that much, and my install is kinda old, so i'm not 100% sure about that).
Your check for DirectX 9 may be too system specific.
HOW do you get the custom temps and voltages in the new version. In the old, the setup area had two screens one of which allowed mapping of all the volt and temp sensors and labeling the custom ones. I can't find similar functionality in the new one and the display shows 4 temps and voltages with no configuration options. How does this work?
Quote:
Originally Posted by DavidNJ
Not really, as this DLL is the file required by OCCT GPU to run. It is always located in the System32 folder. Do you have that file ?
In the options tab, you'll have two buttons, the first one, orange, allowing you to get access to the monitoring options, which is almost the same as the old one, but for the new GPU sensors.