Jump to content

octiceps

Registered User
  • Posts

    1016
  • Joined

  • Last visited

  • Days Won

    6

Posts posted by octiceps

  1. If 1080M is not at least as fast as 980 Ti it's a fail in my eyes. But 1920 CUDA cores probably means between 980 and 980 Ti performance, closer to 980 Ti I'd hope. 1080 is only 25% faster than 980 Ti and that's by virtue of its high clocks due to 16nm FinFET. Contrary to Jen-Hsun's bullshit-as-usual 2x efficiency claim, 1080 is only 1.5x the perf/watt of 980.

  2. 15 hours ago, Prema said:

    @octiceps

     

    Ah, that's not the Clevo doing this but the Dell charger itself needs a signal modification or it won't allow you to pull more than 220W-ish:

     

     

    We are pulling over 820W+ from a P870DM...they don't block these things on a hardware level.

     

     

    Actually the PSU shuts off before 200W drawn from the wall, so it's not that. Could be the Bix converter cable I used is not up to snuff, supposedly it's 16AWG rated for 10A max.

  3. 2 hours ago, Prema said:

    @octiceps

     

    Clevo doesn't block the use of other chargers (Dell and their chargers do), but the Dell charger may not be able to handle the "FlexiCharger" controller configuration.

    Disabling that in BIOS should let the AC Adpater work also under load.

     

    The P650SG doesn't have the FlexiCharger feature. I know it's an issue inherent to the laptop because other P650SG owners have reported the same thing, and the Dell 240W/330W works just fine with my Lenovo Y500.

  4. At the very least, Clevo needs to allow third-party charger compatibility. For example, Dell 240W/330W adapters don't work with the P65xSx/P65xRx. They charge the battery when laptop is idle, but disconnect under load. The P65xSx/P65xRx at stock already nearly maxes out the included 180W/200W brick.

  5. 8 hours ago, CanTOKER said:

    Edit : Game still crashing after 5-6 minutes. Dxdiag error says that graphic card removed or undetected.. :too_sad2:

     

    If it doesn't happen at stock, then the OC is unstable.

     

    8 hours ago, CanTOKER said:

    And also check the picture, there are some drops after i open the game ; voltage drops from 1050 mV to 0.812 mV than its going again to 1000 mV than 1050 mV..
     

    55555.jpg

     

    7 hours ago, CanTOKER said:

    For now, at desktop i just saw that kind of drops at Ultrabay GPU. Everything was OK, but my voltage's are not stable..

    Check this out ;imageproxy.php?img=&key=2ac7e5ac02b90b29

    77777.jpg

    666666.jpg

     

    Looks OK to me. If adaptive power mode is selected in Nvidia driver, it will dynamically switch P states (hence frequency and voltage) depending on load. You can change it to prefer max perf if desired to prevent this.

     

    You're using a voltage offset of +162.5 mV in Inspector, which is effectively a +50 mV overvolt, or 1.05 V. The reason max voltage is reported as 1.087 V is that the normal vBIOS behavior will drop it down to 1.05 V after GPU reaches ~60C. Same behavior is observed on stock voltage but it drops from 1.025 V to 1 V.

     

  6. 3 hours ago, CanTOKER said:

    Hi again guys, i did it :rofl:

    But now i have some problems with voltage control, before when i had stock bios, my GPU's voltage was 0.812 V and when i was playing games it was going to 1000-1025 mV.

    Now i changed the voltage but it didnt effect, it seems like stock. Still going on games 1000-1025 mV, and my game (Need For Speed 2016) crashes after 5-6 minutes.

    So what can i do? Thanks for replies.

    1111.jpg

    22222.jpg

    44444.jpg

    3333.jpg

     

    The actual 'zero' for voltage offset is at +112.5 mV. So +125 mV adds 12.5 mV to stock, +137.5 mV adds 25 mV, etc.

  7. 4 hours ago, CanTOKER said:

    Hi again, i have a question;

    I'm using BIOS v2.04. I have SLI confugration. I'm going to be able to update my first GPU.. (After i paid 6 bucks to save time)

    But how will i do for ultrabay GPU? 

    Because -svl7- says that " Flashing the ultra bay 650m - only for SLI users with BIOS v2.02: "

    So what can i do?  Thanks for answers.

    SS-GPU.jpg

     

    Don't worry, Ultrabay vBIOS is separate from primary GPU and will flash fine on v2.04.

     

    3 hours ago, Bless said:

    can u get the files sent to me

     

    Read

    • Thumbs Up 1
  8. On 3/17/2016 at 2:49 PM, reverenddak said:

    Oh man. UPDATE! 

     

    So, I was able to update the bios on the Ultrabay 650m. I used the latest NVflash64 for Windows I could find (v.5.265_win) that I could find. Remembered to UNLOCK the EPROM (nvflash64 -r). Then Followed the instructions. I think the different thing I did this time was REBOOT IMMEDIATELY, before doing any futzing around. 

     

    I may have forgotten to say that this was all on Windows 10 Pro (64bit). I'm pretty happy about this. Totally extending the life of my Y500 from 2013/14??? I can't even remember. Next up will be to install a mSATA SSD drive as a new boot drive with a FRESH install of Windows 10, and not have to worry about losing all my stuff (meaning game installs) on the slow stock HDD.

     

    y500_650mOC1.thumb.png.cdce87b8e366f7a3a

     

    Good job, 1100 MHz on stock voltage (1V) is a nice result for the 650M. If mGPU support was as good as it was in early 2013 when I bought my Y500, instead of getting worse, then OCed 650M SLI would still be quite viable for the duration of this current console gen.

     

    4 minutes ago, CanTOKER said:

    Hi, i just found this amazing work.
     I have a y500 with 650m SLI, and today i want to overlock my GPU's and i found here.But i couldn't download " Y500 -Y400 - SLI 650m - 80.07.27.00.33 - OC.rom.zip" file, i dont know why..

    Can anyone please send this file to me?
    Thank you.

     

     

    I suggest reading the site rules, specifically this.

    • Thumbs Up 1
  9. 2 hours ago, Kango said:

    Running a eurocom Sky x6 with gtx 970m. Downloaded the vbios for my card. For some reason GPU-Z shows my default clock speed of 540mhz and when I over clock the card, it just increases the values from 540mhz. It also says the default memory is 1253mhz and pixel fillrate is at 25.9gpixels. 

     

    Should i I just ignore the data from GPU-Z?

     

    What does the sensor reading for core clock say under actual 3D load?

  10. On 2/7/2016 at 5:13 AM, Centurion said:

    I could reach 81hz with my y510p.Dont know if it is glossy screen or matte but when i try 82 it goes black.because 81 is max I think it is the matte screen.So is it harmful to overclock the lcd ?

     

    You can't tell the difference between glossy and matte??? J/k j/k

     

    Most likely matte since 80Hz seems to be the common limit for that panel and 100Hz for glossy. But YMMV as with any kind of OC. I was lucky to have a panel that can do 120Hz (see above).

     

    I haven't heard of any horror stories resulting from LCD overclocking.

  11. Strange. Looks like Intel's MLAA is temporally borked. Only side effect of MLAA I've seen is blurring similar to FXAA but this depends on implementation.

     

    Although this begs the question of why the Intel 3D settings even work if you're not playing on the iGPU.

  12. 9 hours ago, Prema said:

    - Reset Clevo Control Center to defaults

    - Make a full shutdown (not standby/sleep)

    - Remove AC Adapter for 30s

    - Plug it back in and reboot

     

    Also make sure to flash the "cool" EC when flashing the Prema Mod).

     

     

    Thanks for the suggestions, Prema. Cool EC is what I had flashed. Rebooting fixes the fan behavior. But what caused it in the first place? I think I know now. I recently increased my GPU overclock, which caused some driver crashes/resets. If, after a driver crash, I click apply defaults in Inspector while max fans is engaged, auto and custom fans stop working until the next reboot. Those are the exact steps that triggered the bug. Weird, huh? :P

  13. 22 hours ago, octiceps said:

    Hi @Prema, I seem to have encountered a couple bugs. Occasionally, after waking my P650SG from sleep, the 980M will be automatically overclocked to +810MHz core and +1000MHz memory. Obviously this is not good and if I hadn't bothered to check Inspector before firing up a 3D app, I woud've gotten an instacrash trying to run almost 2GHz core and 7GHz VRAM. In addition, the auto fan profile is borked and the fans don't spin up even when GPU reaches 92C and throttles, unless I force max fans. I'm using Hotkey v3.09.21 on W7, Performance plan. These two bugs only occur after waking from sleep, and seem to be triggered if I reset my GPU to stock before entering sleep.

     

    Edit: Nvm figured it out, MSI AB was the problem.

     

    OK the auto-overclocking was because of Afterburner, but I am still having the fan issue. Automatic and custom fan profiles are completely broken and fan speed doesn't change at all, GPU heats from 40C to 90C within 30 seconds. Only max fans still works. It's as if whatever is controlling fan speed is no longer reading temperatures correctly.

     

    I had an unexplained BSOD yesterday, could that have something to do with it? Or is it a hardware issue?

  14. Hi @Prema, I seem to have encountered a couple bugs. Occasionally, after waking my P650SG from sleep, the 980M will be automatically overclocked to +810MHz core and +1000MHz memory. Obviously this is not good and if I hadn't bothered to check Inspector before firing up a 3D app, I woud've gotten an instacrash trying to run almost 2GHz core and 7GHz VRAM. In addition, the auto fan profile is borked and the fans don't spin up even when GPU reaches 92C and throttles, unless I force max fans. I'm using Hotkey v3.09.21 on W7, Performance plan. These two bugs only occur after waking from sleep, and seem to be triggered if I reset my GPU to stock before entering sleep.

     

    Edit: Nvm figured it out, MSI AB was the problem.

×
×
  • 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.