Jump to content

nick81

T|I Elite Legacy
  • Posts

    43
  • Joined

  • Last visited

Posts posted by nick81

  1. On 14/05/2016 at 9:31 AM, wuruochong said:

    I've recently flashed Prema's vbios for my single GTX 980M in a M18x R2. I did notice a noticeable increase in gaming performance, but also a pretty significant increase in temperatures. With stock vbios/clocks and a cooling pad at 22C ambient I get 78C locked on the GPU. With Prema's vbios that increases to about 80-82 in demanding games like Rise of the Tomb Raider. Took the cooling pad off and the temperatures went up to 87C with no signs of stopping before I got too worried and pulled the plug. 

     

    I'm definitely starting to suspect something is wrong with my system GPU side (thermal paste? bad fan curve?). What sort of temperatures do you guys get with a 980M? And what would be considered safe? (Prema's bios has throttle protection kick in at 92C and I'm getting dangerously close to that without a cooling pad) 

     

    Hey man

     

    Under no circumstances should your GPU temp exceed 75 degrees (for the 980m) except if you're OC'ing

     

    Mine, with Prema's vBios v2 and in dedicated mode idles at 40 degrees and doesn't exceed ~72 degrees under HEAVY load. For most games, including Rise of Tomb Raider it doesn't exceed 70 degrees. Of course this is with a cooling pad (notepal U3)

     

    Two things to keep in mind when you have a temp problem:

    1 - Use quality TIM. I use GE Extreme. Other great TIM's are Grizzly Kryonaut. Use the pea method and you should be fine. Make sure to properly clean the GPU die and heatsink before applying the TIM.

     

    2 - Do NOT screw the heatsink too tight. This has helped me personally in the past and at least one person on another forum. BAsically what happens if you tighten too much the screws is that the heatsink warps and the space between the GPU and heatsink actually INCREASES. So what you want is to leave 1/2mm loose when tightening the screws. In my case it reduced my temps by almost 10 degrees (not kidding...)

     

    Do not worry about vBios. And one recommendation, do NOT OC the 980m. There are countless stories of 980m dying. Many people's opinion is that especially the RAM modules aren't very good and tend to die fairly easily.... Make sure you put extra thermal pads for these by the way. Temp controllers will NOT monitor the temp of the RAM so you won't see their death coming...

     

  2. 56 minutes ago, angel_ennix said:

     

    i will give it another try. for now im using my old 680m i don't know how i would fry my vrams im not over clocking it and im running nvidia inspector set to temp limit at 65C so it downclocks when ever it reaches that temp.

    thanks for the reply.

     

    Well that's exactly what I asked around when my 980m died... I NEVER OC'ed it and I am absolutely certain that I applied thermal pads properly on the vRam when installing the GPU.

    But just so you know, Nvidia Inspector won't help with vRam temp. The 65C limit is applied only to the GPU temp, not its vRAM. There is no simple way of measuring the temp of the vram unless you use maybe a IR thermometer/gun or something...

  3. @J95

     

    Hey man

     

    Hope you can clarify something for me.

     I keep reading about throttling yet I've never faced it myself with my 980m. I did get some throttling with my old 880m but that was solved by flashing to SLV's vbios.

    With the 980m, flashed to Prema's vbios, I have never faced throttling on any driver version....

     

    How come others with practically the same setup as mine face severe throttling at time? Could it be hardware related, as in depend on the quality of the GPU itself? (ASIC?...)

  4. 5 hours ago, angel_ennix said:

     

    hi guys

    got a bit of a serious problem here so any help is much appreciated.

    while i was browsing the internet my screen suddenly turned black, so i restarted my laptop then for some reason it used the onboard gpu of my mother board.

    i restarted again and it didn't change anything.

    so what i did was i run DDU and clean un-install the gpu then re-install the gpu driver again.

    but its not letting me re-install the gpu driver for some reason it keeps on showing me this.

     

    http://s108.photobucket.com/user/ennix4690/media/force%20driver%20failed_zpsbxsxt0be.jpg.html

    http://s108.photobucket.com/user/ennix4690/media/2failed_zpsti0n5kdf.png.html

    the screen was showing some flickering too unfortunately i wasn't able to include it on the screen shot.

    i was using the 353.00 PEG mode with prema's bios CLEVO_8GB_GTX980M_OC_PM_v1.1.1 for months now ever since i bought the gpu and this is the 1st time i had encountered this problem.

    any help/ response are greatly appreciated especially right now that im lost and don't what to do.

     

    Thanks.

     

    System

    M17xR4 120 hz pannel using Nvidia GTX980m 8gb non optimus

    Sounds like what happened to me with my 1st 980m....

    Well to make sure the issue is only with the GPU, you could try the following:

     

    1- Run DDU in safe mode and select the option to Shutdown (install new GPU)

    2- Replace the 980m with your previous GPU if you still have it. If not, then just unseat, clean the port and reinstall the 980m.

    3- Boot with DSE disabled and install the last driver that worked for you (100%) to avoid the chance of the driver being the issue.

    4- If it still doesn't work, then you've got a dead GPU... Can you try checking the GPU info from HWInfo? GPUz in my case hanged but you could try checking it as well. In my case it was the vRam that had fried for some reason.

    5- One LAST Thing you could try is to do a clean install of Windows... I have reasons to belive that DDU isn't perfect and that there are files not being deleted even in safe mode.

    Good luck!

  5. On 17/03/2016 at 6:35 PM, J95 said:

    @nick81 you will need to increase voltage for Rise of the Tomb Raider, even my stable 24/7 OC/OV  @1266/1.087V, 3DM11 & FS loop settings, incl Valley...364.51 delete unnecessary folders and don't install GFE, don't use RTSS either...FPS counter Steam overlay (latest version) w/ DX12 support

     

     

    Rise of the Tomb Raider DX12 option.                                                                                                                                          

    Tomb_Raider3.thumb.PNG.3f050df803bb34619

    RAM used.

    Tomb_Raider_RAM.PNG.684bb8a21c4e77b1c595

     

     

     

    Don't install v364.51. Instead, flash Prema v1.1.1 before installing Win10 throttle free PEG mod 352.84.

     

    v364.51

     

     

     

    @J95

     

    Hey man

     

    I still don't understand why you're asking me to increase voltage for Tomb Raider. I was actually able to resolve the issue by disabled Steam Overlay and uncheck the option "Exclusive Fullscreen". I just beat the game tonight and I didn't get a single crash since doing these 2 "fixes".

     

    I am honestly not touching (OC'ing) my 980m until I build my "monster" HTPC in the near future. Just waiting for the Pascal GPUs and if the rumors are right we might very well see a Titan grade GPU in April-May and a Ti grade GPU by June. I guess we'll know if it's right or not by next week! A part of me is actually praying AMD's lineup is better but I seriously doubt that'll be the case...

    I've got the $$$ ready for the Titan purchase... I want that baby to last me at least 3 years and to be able to finally game in 4k on my TV.... *fingers crossed*

     

  6.  

    You shouldn't apply too much pressure when placing the heatsink. Pros suggest you leave at least 1-2mm margin for each screw. I believe this was to avoid warping which will actually INCREASE the gap between the heatsink and the GPU die...

     

    As for the info you asked me about:

    - VBIOS: prema v2

    - Driver: 361.75 (peg dedicated modded inf by j95 posted above)

    - Stock clocks and voltage (~0.85 right now in GPUz, core clock of 135 and mem clock of 162, with idle temp of 34)

     

    I reapplied the paste again last night and I hardly put any pressure on it at all, it seems to have helped but I'm still not near as low as you are. I tried out prema v2 vbios last night and I'm still running on older drivers I think its 347.25 due to the throttle issue I was seeing. ( I don't think I installed the peg dedicated drivers right so I went back to 347.25). I had no hard locks ups last night while playing, most of the time my temps was 68c but there was odd moments (mainly idle moments in gta V that I seen my temps go as high as 77c?) also when trying Ark Evolved I seen my temps hit 78c so I stopped, everything seems stable though but I don't want to run it hot, you should download FFXIV Heavensward benchmark and run it on extreme and see what your temps are, are you running a M18XR2 as well or which laptop are you running? I wonder if your cooling system is better than mine.

    I have an AW17 R5 (2013). I just ran the FFIV benchmarks and the max I hit was exactly 70

    Sent from my iPhone using Tapatalk

  7. 22 hours ago, 82280zx said:

     

    How much pressure did you put on the heatsink when screwing it down? I'm paranoid about tightening it to much, I don't want to squish the paste out the sides of the chip, at one point when I had it applied the highest I seen it get was maybe 71? Also what vbios and drivers are you using if you don't mind me asking, and whats your voltages look like under gpu z?

     

    You shouldn't apply too much pressure when placing the heatsink. Pros suggest you leave at least 1-2mm margin for each screw. I believe this was to avoid warping which will actually INCREASE the gap between the heatsink and the GPU die...

     

    As for the info you asked me about:

    - VBIOS: prema v2

    - Driver: 361.75 (peg dedicated modded inf by j95 posted above)

    - Stock clocks and voltage (~0.85 right now in GPUz, core clock of 135 and mem clock of 162, with idle temp of 34)

  8. 3 hours ago, 82280zx said:

     

    I'm still pretty new at this and don't dare proceed till I ask some questions.  I have a M18xR2 with a GTX980m I bought from woodstacks, I've already flashed over to prema's v2 vbios (after backing up the stock one that came with it) but have questions about installing this driver.

     

    • Run DDU "Clean & Shutdown (Safe Mode)
    • Extract driver using 7-Zip <---- I assume I download the main driver from Nvidia's site for the 980m and match your driver version then extract it right?

    This is what I had before playing with this

    Display device : GeForce GTX 980M on GM204-A GPU
    Display driver : 347.25
    BIOS : 84.04.22.00.12

     

    My temps look good as far as I can tell, they float around 75-76c , I'm using Fujipoly 16w/mk on everything but the memory and I'm also using GC-Extreme thermal paste. When playing GTA V under load I get a  hard lock randomly, the video just freezes completely, I can hear people in teamspeak, I can talk to them but I have to hard power the system down before I can use the system again. I'm open for suggestions and help if anyone can help get me running, I'd really like to use this 980m it would bring my M18xr2 back to life for a while. I'm running Windows 10 64 bit, and I've been steering clear of evga precision etc after reading about all the bricked displays.

     

    75-76 is very hot for a 980m. With GC Extreme I get personally sub-40 temperatures on idle and a max of 67-68 when gaming/benchmarking. I also a use a cooling pad: the notepal U3.

    You might want to reapply the paste as even without the cooling pad my temps will never go as high as mid-70s...

     

     

  9. Well it's not exactly rocket science and I didn't learn it on my own. There is a very detailed topic on the subject on these forums and like I said, a tool like WinMerge can show exactly what is being added to the drivers.

    Practically nothing is changed, aside from adding the hardware ID of the GPU you're using.

    I don't see how you could ruin a system if you're just copy pasting a hardware ID. 

    I wouldn't call this being "experienced". You need to be careful sure. 

    I was only asking that question to make sure I am not missing something. I've never faced a single problem modding my own drivers (following J95's advices and tutorials).

     

  10. On 03/02/2016 at 5:38 AM, thegh0sts said:

     

    any modded INFs for that?

     

    Quick question which I already asked in the past...

    If you download a small software called WinMerge which basically compares 2 text files line by line, the only differences in the Optimus inf files are the ones related to adding the HW ID of the 9xxm GPUs while the Dedicated inf files, also show one or two differences related to audio or 3D drivers I think (nv_disp.inf)

     

    Is there any point to wait for a modded driver anymore (if one is comfortable modding his own drivers of course)? The one exception I think is the 353 Peg Mod which had a big list of differences if I remember correctly.

     

     

  11. On 24/12/2015 at 11:48 PM, J95 said:

    Confirmed broken driver *361.43* AW/ 980M & 970M, under safe mode uninstall using DDU "Clean & Shutdown", reinstall  353.06 or 359.12

     

    M18xR2, M17xR4 120Hz & AW17 120Hz install PEG MODs.

     

    GeForce 353.00 PEG MOD Win7/8.1 - Latest profiles

     

    PEG MOD v352.84 Win 10 - Latest profiles

     

    @J95

     

    Hey man

     

    I finally decided to give dedicated GPU a try. I used the Fn-F5 to activate it and rebooted my computer. I used DDU to clean my drivers and restarted with DSE disabled.

     

    I first tried installing the 361.43 drivers without success. All I got was a black screen whcih I could only get out of by doing a hard shutdown. I then tried to install 359.06 which worked without a single problem.

    Performance DO seem better than with Optimus...

     

    My big question now is: do you recommend I give Windows 10 one final try now that I am using dedicated mode... I know many people, you included have warned against EDID corruption. But considering I never used (and will never) precisionX or any other overclocking software do you think I might be safe?

    Has any progress been done by the community in resolving/avoiding this issue?

     

    Thanks a lot!

  12. Hi Erik

     

    I don't have a 970m but I did upgrade my own GPU to a 980m mxm. I remember reading someone with similar issues fixing it by reseating his GPU and properly placing thermal pads to cover the memory on the GPU. In my case the 980m's memory chips were placed differently than the ones on my old 880m so I had to position it differently.

     

    So even though the GPU's temp might show up as being "ok", this doesn't mean the memory isn't overheating. Also temps in the 70's still seem a bit high for me. The max I get with my 980m is 69-70 and that is under heavy load. Can you tell us precisely how high your temps go?

    Other than that, I can't really recommend you do anything you've already tried:

    - Flash to Prema's vbios

    - Get a decent driver (one that is know NOT to cause throttling. Please note that in my case I have never faced throttling on any driver but I know some people who did get some on a couple drivers versions recently).

    - Try doing the P-states thing described by j95 (I didn't do it personally as I am not getting any throttling).

  13. On 20/12/2015 at 6:52 PM, Observer said:

    At this point of time, even Eurocom aftermarket upgrade is also not supporting Win 10, only Win 8.1.

     

    http://www.eurocom.com/ec/upgrade(2,263,0)ec

     

    However, after using Win 10 for 2 months, and now I am back to Win 8.1, I can't say I miss Win 10. Personally I am more comfortable with Win 8.1, and I never use Cortana, Edge, etc. The only feature will be missed is DX12, in the long run that is. 

     

    Yeah my only concern is DX12 and I would've loved running the latest DX12 benchmarks in 3DMarks once they're released in Q1 2016. Looks like that will have to wait until I completely replace my laptop. The modding community doesn't look interested in W10 at all (or borderline disgusted by it) so I doubt we'll see vbios/drivers to make our mxm cards work anytime soon.

     

    Edit: on a side note new drivers got released by Nvidia (361.43). Will test them tonight. Nothing special aside from VR stuff.

  14. 2 hours ago, Observer said:

     

    I rolled back from Win 10 to Win 8.1 due to Win 10 kept forced installing an older version driver for 970M, no matter what I did to prevent it.

     

    Once I am in Win 8.1, I switched back to Optimus mode and followed your steps, using modded nvcvi.inf with 358.91, and the blank screen issue after cold boot/reboot is gone. 

     

    Well I am feeling more and more like we're going to be stuck with Win8.1 with our upgraded 970/980m mxm cards... Unless Prema, slv and j95 sit together and figure out how to make these cards work properly in Win10 (in Optimus) I honestly can't see any solution to these issues... I don't think it's only a driver issue. I have a feeling something needs to be changed/added to the custom vbios that has already been released by Prema. I haven't tried SLV's vbios but I doubt it'll make a difference.

  15. @J95

    I was just reading the exchange of posts between you and @angel_ennix and took a look at my own GPUZ info. There is something peculiar which I hope you can explain to me. Here are a few screenshots I took:

    post-27906-14495001351136_thumb.jpg

    post-27906-14495001351253_thumb.gif

    post-27906-14495001351441_thumb.gif

    ASIC is decent I guess and I am using Prema's vbios 1.1.1. I didn't overclock my GPU at all currently but isn't the voltage very low? 0.85v?

    Thx a lot!

    EDIT: Nevermind... NVInspector shows a voltage of 1.062V which I guess is the stock voltage for the GPU. I wasn't aware voltage varied depending if the GPU is under load or not.

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