Jump to content

sirana

Registered User
  • Posts

    163
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by sirana

  1. Yeah I notice on the AB OSD that I get 70% usage at times in BF3.

    @john, can you go into Multiplayer, Caspian Borders 64p Conquest and run out of the US base? If you pass the rocks on the road right side you could experience the same under utilization as me, please test it.

    Here the AfterBurner monitoring window:

    http://img11.imageshack.us/img11/5759/monitoru.png

  2. Will there be a newer edition of the overvolted clevo 680m vbios? I am using the one that i found on the post about using your 680m to its fullest potential, but i am wondering if and when a newer vbios will be coming out. i would be very interested in testing such a vbios.

    Svl7 mentioned a few posts above that he is working on improving his mods, but of course not 24/7 so it will take some time.

    And @timrogerswert82 I have Samsung VRAM too on my Clevo 680m

  3. The tweaks I've done in the files you mention won't work in the vbios you posted. Not sure why your system doesn't work with it, that's odd. I can do a more moderate mod on the OEM vbios, that should work.

    Could you please add a little voltage up on the Clevo rom to prevent throttling? Also some weeks ago you mentioned you might have figured out a way to enable proper GPU Boost, how about that, any progress?

  4. Keep in mind this throttling is mainly in test 1, so if you test a game with similar overclock you should see a gain in performance.

    Finally it's the weekend, @svl7 is likely out enjoying it.

    Yes I do get a small performance increase in games, but even 830/1800 is not very stable and causes under utilization for me i.e. in BF3. (CPU: i7 980 so no bottleneck)

    With the MSI vbios of the other thread (default 915/2250, and overvolted) the game plays steadily at that clocks for some minutes and then the core and memory get stuck at 324. This stays also if I re-launch the 3D app and stays until I reboot.

    I tried this with 306.02, 306.97, 310.33 and a 305.xx driver.

    And yeah I hope svl7 is enjoying the weekend :D

    It's just that he did not reply to several questions here in this thread while being very active in the M18x thread, hence my question.

  5. I don't understand. how would 3Dmark 11's first test be giving different values for the various vbioses? The problem is that relatively, the over-volted vbioses do not do as well as the base 0.912V vbios.

    still can't seem to get to a 7000+ score on 3dmark 11.

    I can get 9000 for the Physics score. so the CPU bit seems to be okay

    Same here... can't get past 7000 with any overclock you could imagine, just because the card throttles like a b.... :D@svl7 are you still active in this thread?

  6. I tried both MSI vbios's. They did not brick my card but did not work well either. As I mentioned a couple of times, the MSI vbioses cause my core and memory to be stuck at 324Mhz in 3D applications, but only after 1. some minutes of gameplay or 2. if I restart the application.

    At the first launch of the 3D app the clocks are at 915/2250 perfectly as should be, but after some minutes they clock down to 324 and stay there until I reboot my Notebook. Even if I launch a different 3D app the clocks stay stuck.

  7. Hmmm I think I will give the MSI vbios another try... just because I'm desperate and svl7 has not updated the Clevo rom yet that is :)

    Speaking of which, @svl7 do you know when/if you are releasing your next vbios?

    I tried the 915/2250 MSI vbios again, and the official +200 Core one from your OP. Both had the issue that after a the first launch of a game the core AND memory stays at 324 :( reverted to your unlocked Clevo OC New one...

  8. In case you flash a wrong vbios or fail at flashing, you can always blind flash it back. Therefore I would suggest to you guys to set "Boot from USB" as first priority in the boot order. Then in case you fail you only need to wait for like 1min, then type the command for flashing the backup-rom that you should have taken prior to trying a different rom.

    Just follow svl7's sticky regarding the flash process, it is actually really easy. You just need a USB stick, put the win98 DOS files on it as well as your new rom (and also save your current rom on it), then boot from it, and then type "nvflash -6 <romname>.rom" without the "" obviously.

  9. Hello All,

    I am new to this forum and very interested in this discussion. I recently purchased my new Sager 9370 with dual 680m graphics cards and I want to push them to the max. I have never flashed the Vbios before on any of my cards. For a new person to do something of that nature, what are my chances of bricking the cards?

    If you closely follow the guides in the stickys the chance is bricking a card is pretty slim. And once you set your BIOS to boot from USB as #1st priority, you can always blind flash your original vbios back.

    I too was anxious of flashing vbios's, but I went ahead and did it (correctly) and so far it has proven to be awesome.

    Just that this specific vbios of this thread does not work very well with my Clevo 4GB 680M. It does not jump to it's correct clocks in 3D games after I exited any game. Means first try it jumps from idle to the promised 915 Mhz, but as soon as you close the game and restart it the core and memory clock is stuck at 324. No idea why. The Clevo_OC_New rom of Svl7's sticky thread works find for overclocking manually though. Just that I get massive throttling past 850 on Core. 888 is the last stable OC with that vbios. But he will probably soon release a new updated version, and possibly even with a working GPU boost :D

  10. @0xsergy - set 3DMark11 to run test 1 only. Set your core at 850 and leave the memory stock. See if the throttle goes away. If it does, set it for 1000Mhz and test again.

    I guess you mean +100Mhz on memory, not 1000 :)

    I tried that. My highest Core without throttling is +170 in 888, the Core shows 888. If I go ANY higher, it throttles. This is with Memory on stock, 1800. The last stable OC is only +20 on memory, and even that throttles sometimes -.- So basicly 888/1800 is the last stable OC with the Clevo New vbios. This also only results in 6,5k 3dmark11 points for me. With my throttling OC of 888/2000 I can get 200 points more, but that's not worth it if the FPS dip in the low 20's at times.

    I really hope svl7 is making progress on a new Clevo rom that does not throttle so much! :D

    EDIT: I get it, you meant setting it to 1000 instead of 900. No idea why the Memory is sometimes stated as 1800 and sometimes as 900...

  11. To be honest, it doesn't surprise me that AMD needs to drop some employees. I pretty much saw it coming as they have suffered from several factors.

    The first one is, as you mentioned, the Bulldozer disaster. That definately turned off most of their "loyal" customers and early adopters, causing newcomers often to not even consider AMD's CPUs an option. But they learned the lesson and more or less halted their Desktop CPU developement and mostly switched to developing Smartphone/Tablet CPUs.

    The second critical failure was ignoring peoples demands and suggestions towards the GPU driver (Catalyst) development. While AMD's graphic cards are predominantly on par with Nvidia counterparts in terms of hardware, they were hold back by their driver support. I learned this myself as I bought my Clevo x7200 with two AMD 6970M's. The drivers offered became worse and worse over the months, causing new deal-breaking bugs and problems while often fixing unnecessary things. This definately killed my trust in AMD, maybe for good. I estimate I am not the only one, so perhaps many "AMD first-timer" will never look at AMD again if they encounter only half of what I went through. Also, just look at what AMD did with Enduro to their new mobile flagship, the 7970M. It can't even be turned off in most recent Clevo Notebooks, hence crippling the performance by approximately 20% in many games. And I know AMD promised a fix for that, but the card is out like half a year now and according to polls in the NBR-Forum a large number of people are unhappy with their 7970M. And that is a shame since the 7970M has the power of performing equal to the 680M while costing like half as much. The pricing definately attracts people, but does not convince them to stick with AMD in the long run, hence I don't expect AMD to become more dominant in either of those 2 markets again.

    People often consider Nvidia overpriced, and it is true that their pricing is sometimes ridiculous. But at the same time, they don't leave their customer behind with a bad feeling for purchasing their product after one month. They develop "proper" drivers, which are crucial in the mid- to long term to satisfy the customer.

    I am glad I god rid of my 6970M's and switched to a GTX 680M, which is not even officially supported in my Notebook and yet performs without a single issue in any game and application I tried.

    • Thumbs Up 2
  12. Hey bro. If you installed 3DMark11 using the custom option and added the 32-bit binary version you can use HWiNFO64/Afterburn OSD combo. The reason it does not work is because the Rivatuner OSD plugin is not compatible with native 64-bit programs. If you installed it, the 32-bit executable will be in the C:\Program Files\Futuremark\3DMark11\bin\x86 (default) installation folder. If not, you can run the installer again and select it. You'll get a slightly lower 3DMark11 score, but it's good for check out behavior in real-time.

    Thanks, that worked. I figured out my clocks actually jump to 919/2250 but throttle a lot, hence the low score.

    I'm so looking forward to his next vbios :)

  13. I need to correct my post!

    Actually I get immense throttling after 850 on core :( Even at 850... look at the pics:

    This is on stock clocks, no throttling

    stockb.th.png

    This is on my fail OC 919/2250, I believed it was stable... well I had no artifacts but throttling

    plus200core450memory.th.png

    Same performance with 850/2250, and even there a small tad of throttling

    135core450memory.th.png

    Sad to post this. @svl7 I wish your progress all the best. Btw, if you manage to provide a vbios that does not throttle so badly, I will buy you a few beers. I have some money left on my PayPal account :)

    Probably based on the rom I gave you, since it's "supposedly newer"? And also slightly overvolted, as I heard that stabilizes the card at higher clocks... but you know what to do, you're the pro! :D

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.