PDA

View Full Version : build 728


rbsmontemor
11-19-2006, 12:04 AM
I've taken a little few bugs:

My VGA temps drop about 6ºC, in comparision with CCC:

http://img135.imageshack.us/img135/9127/issue01eg4.jpg

And I can't use "Memory SPD Data" coz it dont recognize my rams :(

http://img175.imageshack.us/img175/3487/issue02vo9.jpg

Sorry my poor english :banghead:

Lan Party Ultra D
Corsair XMS rev 1.2 (TCCD)
X1900XTX

Thanks

majorlamda
11-20-2006, 07:58 PM
Hello, sorry for my porr english.

When we launch a harddisk benchamrking, the temperature in the systray change to "1" .
I have the same problem about the Ram and my motherboard is doesnt recognize.

Gigabyte Ga-k8-NF9
Corsair 512Mo XMS PC3200 Twinx C2

HDD : Hitachi 7K250, 250go SATA

pokazene_maslo
11-28-2006, 01:54 PM
In CPU overclocking card after several hours of running stability test the timer was displaying this time: 6:401:15 and counting, or 6 hours and 401 minutes.

__Miguel_
12-21-2006, 10:44 PM
Hello. This is my first post, I just found out this impressive software package. I have, however, some problems I think need fixing.

I am running Windows XP x64 on a P5B Deluxe and E6400, and here are my problems:

1) CPU Core temperatures are not shown in the Hardware monitoring Tab (only "-" appears)

2) EIST is unavailable, it shows "0x" in the multiplier and "0.838v" in the voltage; my E6400 only goes as low as 1.162v @ 6x (actually, it can do that @ 8x too :P), so there is definetely something wrong there (or I am doing something VERY wrong...)

3) P965 Memory Timings cannot be written: I tried changing my CAS# latency from 5 to 4 and nothing happened; however, when I accidentally pressed "Write" before ever pressing "Read" (every field blank), the system automatically froze (as I said, it was an accident, I meant to press "Read" - you might want to add some safeguard to that button, so it cannot write before a read command...

4) Again, multiplier shows as "0x" in the CPU Overclocking section. FSB Speed is accurate, however.

As you say the software may be buggy in x64 OSes, I think these can be some of those bugs (either that or the fact I am using the latest version - couldn't find an older one, though). If they are really bugs, I hope they can be fixed, SysTool is just AMAZING to manage the CPU...

Keep up the good work!

Cheers.

Miguel