Thanks, it was my fault not to tell that Prema told me that those drivers along his latest mod, fix the throttling problem on the R2. But it seems that the drivers works for the minority of people.
-
There have been posts of people with 361.43 working, only to have them come back later after uninstalling and reinstalling, and it stops working for them.
For me I thought it was working fine, but it turns out my laptop model doesn't like it while booted on battery, at least 2 of us have the same problem.
Fortunately we can boot on Intel GPU on battery, so I have left 361.43 installed for now. It might not install/work again if I play with uninstalling it.
PM Prema to help work out the conundrum.Last edited: Jan 11, 2016 -
359.14 is Clevo's latest official and stable driver...not sure though if they have made it public, yet.
If you want to try the 361.43, then flash my AW18 vBIOS instead of the Clevo version (it's based on newer stock version, which is almost mandatory to even install this driver).Last edited: Jan 11, 2016jaybee83, James D, Spartan@HIDevolution and 1 other person like this. -
Spartan@HIDevolution Company Representative
In the past, I tried flashing to the XMG BIOS which is the same as the stock clevo BIOS but has the XMG boot logo. After using it for a while, I noticed that my screen is flickering heavily, it would even do it while I was in the BIOS screen not only in Windows.
@Mr. Fox told me that is probably because I didn't wait for 30 secs with the system powered down after I flashed it. I was running the stock VBIOS as well on my 980Ms
Yesterday, I played Need For Speed for about 30 mins then that flickering happened again. This time I was using Eurocom's Prema BIOS Mod. It bothered me a lot so I flashed the stock CLEVO BIOS again and now it hasn't happened. Today I flashed the PREMA VBIOS on both my GPUs again but with the stock CLEVO BIOS, I will monitor the situation and see if it happens again, I really don't know what is the issue here....
PS: Running drivers 359.00 BTW -
By cross-flashing non matching versions, you may only end up bricking the system.Papusan and Spartan@HIDevolution like this. -
Spartan@HIDevolution Company Representative
As to why I did it, I didn't know what else to think or try, I didn't think it would be driver related if it even happened while I wa in the BIOS screen. Something seems to have triggered it after that XMG BIOS Flash then it went away for a long time, then yesterday it came back but I wasn't on the PREMA VBIOS yesterday it was the stock VBIOS so today I went back to the PREMA VBIOS
PS: It didn't happen while everything was stock, it happened while I was on the XMG BIOS then happened yesterday on Eurocom's Modded BIOS -
XMG BIOS is stock Clevo (apart from name/logos).
If it happened in DOS...well not good...maybe a broken screen cable...
Also when you flash my Mods, make sure to use BIOS/ME/EC/EC2 & vBIOS that come bundled with, as that's the way we test them before it's pushed to partner/public.
EDIT: Also wrong thread, sorry for OT.Last edited: Jan 11, 2016jaybee83, Spartan@HIDevolution and hmscott like this. -
Spartan@HIDevolution Company Representative
I wasn't aware if there were other steps required to manually updated ME or EC or EC2 -
Sorry, whatever you flashed there isn't my stuff then...
-
Sorry maybe I misunderstood you. :/ -
So wait, these newer drivers need the AW18 version to work right? I hope that's not the case going forward, I like my undervolted vbios!
hmscott likes this. -
NVIDIA broke this driver while trying to please an ODM...should be fixed in the next release.
Otherwise I already have new Mods using newer bases, so either way no problemo.Ionising_Radiation, D2 Ultima, TBoneSan and 7 others like this. -
I'd be interested in a VBIOS mod you may have that solves the 361 driver install failure, Prema. Under my current VBIOS the driver runs and installs flawlessly but crashes Windows completely under your AW18 v1.1.1 mod :/
Thanks! -
Edit: Irrelevant post,was commenting on 361.60 didn't realize a thread already existed
Last edited: Jan 14, 2016 -
@Ethrem you didn't mention it, but have you tried managing TDR's with TDR Manipulator, the same guy that does DDU:
Wagnard Tools (DDU,GMP,TDR Manipulator, *new* CPU Core Analyzer)-(Updated 01/04/2016)
https://forums.geforce.com/default/...zer-updated-01-04-2016-/post/3846695/#3846695
"...In other words, TDR usually enhance stability. But in some case where a problem in the videodriver is making some thread to be stuck a bit too long on the GPU, that you can have some TDR (GPU reset) happening and making games crash as resetting the GPU while playing is not a good idea, by disabling TDR or play a bit with the value, it can help workaround your issues or help identifying problems." -
-
-
-
Sent from my LG-H811 using Tapatalk -
Prema can fix it. See my post in the 361.60 thread
http://forum.notebookreview.com/threads/nvidia-361-60.786773/page-5#post-10179645 -
Why? -
Spartan@HIDevolution, TomJGX and i_pk_pjers_i like this.
nVIDIA Graphics Drivers v361.43 Findings & Fixes
Discussion in 'Gaming (Software and Graphics Cards)' started by Spartan@HIDevolution, Dec 21, 2015.