Clevo M570RU latest firmware

Hi to all,
I have a big confusion about which is the latest firmwares available..
Did anyone tried this http://www.mediafire.com/?ustmvy2m3xs 1009b??
Are there any difference? It is possible now OC both CPU & GPU together??
Why Zfactor says that it doesn't work??
And which is the latest KBC firmware? I have v106 and I have the problem that fans start at maximum speed, then settle theriself at right speeds automatically.
I have red that there is a v107sh with manual fan control but they start at maximum or not?
Thanks to all

 

okay we NEED a sticky (mods?? i can write it up if you want?? lmk)

the 1.00.07sh IS NOT THE SAME THING AS THE 1.00.09B. the 1.00.09b is a BIOS the 1.00.07sh is only the keyboard part of it..

the fan normally comes on like that at least on all the systems ive worked on. the latest kbc firmware (NOT BIOS ITS DIFFERENT) is 1.00.08 but it does not allow for fan control any longer. i have it and im going to look more at it tomm to see if that can be added back in

 

Z write it up and PM Chaz about this, it's getting way out of hand
KBC firmware ≠ BIOS revision...

 

im looking at .09b right now ill see what has changed

 

im going to do that here in a bit.. ill send him a pm asap..

 

I know it's different.. I'm not stupid,I read. I wrote this infacts,wich are the latest for main and KBC..
I have red that the only difference in 1.00.9b is a LAN PXE, is right?
I am very interested in OC both CPU& GPU!!

 

No,don't worry,it's not about you, but a lot of people update their BIOS and the firmwares, and they are similar in numbering, and confused many users.
That's why Z is working on a sticky for it

For OCing, follow the link in my sig...

 

I know well your thread and I (and my T9300) are gratefull to you for the undervolting, but what I'm interested in is OC CPU and GPU at the same time without problems..
Audigy said something about a voltage chip but is out for a while I think he is on vacations..
So I would like to know if with these new bioses are there any differences, and exactly wich are the best firmwares at the moment.

 

is there a newer system BIOS than the .08? What is this .09 bios?

 

As far as i know it is a novatech specific bios which updates the lan pxe rom to increase compatibility with their auto installation systems. It has no other differences

 

Whad Audigy is attempting will probably kill your warranty so I sugest OCing your GPU via flash and the CPU via SetFsb, but on a moderate basis.
If you game a lot of RTS type games, focus more on the CPU, with the ,of course,added attention to heat, if you're more into fps and fast action games with awesome graphics..the GPU is your concern.

 

What were they thinking removing fan control?! Thanks for the info I know not to update now.

 

they didn't remove it, the fan control feature was added by Sager.

 

Ahem, added by Clevo at sager's request.

 

okay the new bios does not add anything to worry about. he was right about it being (i belive) novatech. this is prob like what sager did with the fan control.. dont worry about it...

 

it seems you are correct. after carefully going through it it doesnt seem like i can find any other differences..

 

ROFL, a supposed "new" BIOS where the only change is in the boot screen!

 

My GPU is already OCed via bios but it doesn't matter, when you try to OC also the CPU, a crash is behind the corner.
With KBC 1.00.7Sh my fans start very softly like I want them..

 

yeah you cant really oc both at the same time..

 

I've been researching OC'ing both at the same time. I'm still conducting some tests and doing some research as to why this cannot happen, and if there is perhaps a way to make the OC between both the CPU and GPU possible. So far, the system BIOS seems like the most likely reason. Certain aspects are OC'able while a GPU OC is active, such as the PCI-E Frequency, but I believe the problem lies in the FSB. After running over the many BSOD minidump files, it seems corruption from a kernel halt occurs in the PCI-E path while synchronizing the clock between the CPU and GPU. If its not BIOS, it very well may be that the mobo that does not allow it. If this is the case, then there is not really anything we can do. I will continue testing on that though.

 

Thank you emike09!

 

i do agree for the most part .. i have went thorugh the bios many times.. and everything i have tried has resulted in it not working the way it should.. i also agree there is most likely a different factor involved

 

Well a little bit more of an update on that CPU w/ GPU OC Update. It would seem that by matching the PCI-E Frequency up with the FSB on a divisible scale, I can increase the stability quite a bit. I've gotten the first bench on 3DMark 06 to come close to completing, instead of the disp. kernal halting in the first few seconds. An example, if I set the PCI-E freq to 130MHz, I would want a FSB frequency that can by divisible by 2 on that level. At 2730MHz, divided by 21, a whole number, I get the PCI-E of 130. This seems to be very stable when synchronizing information through whole numbers. I'm still lead to believe that some chip on the mobo is responsible for the crashing, particularly the NB, which facilitates and coordinates proper data transfer between the PCI-E, CPU, RAM, and SB. I'm not sure who the actual manufacturer of the mobo is, but I just don't think they intended for the frequencies of both FSB and GPU to be altered together. Again, a BIOS upgrade could fix this. We'll see. I have my doubts that anybody at Clevo really care. I'm going to email them anyways and request it be looked at.

 

Yes, Audigy was talking about this problem in this thread http://forum.notebookreview.com/showthread.php?t=249470 .. (page 30 about) In the Clevo M570RU there is a problem in the IC voltage Chip.. He was starting to know some informations on that chip guessing it would be pin-moddable but then he have gone on vacations and he is still out!!...

 

Hmm so it would seem. It all makes sense with the IC chip. Hard modding is not something I'm experienced with. Would be interesting to see whats going on with it though. I'll wait for Audigy to look deepoer into it.