Nvidia 347.09 Beta

Drivers | GeForce (x64)

Those with sli 980m/970m systems dont install this.
Read through thread for possible workarounds if you have that setup.

Enjoy all

 

Just beware that SLI isn't supported yet:

 

I can only imagine the outrage of those who install this without reading the release notes, lol.

 

You'd think something as major as this would be in BOLD CAPITAL LETTERS on the download page. But typical nVidia of course.

 

That SLI stuff... Glad I read this topic before installing the drivers in my dual 880M Clevo

 

Erm you'll be fine.

 

Oh. For 980 and 970 only.. XD. My bad

 

Yes this sli problem only applies to 980m and 970m which are farely new so most of you guys should not have any issues. Installed on sli 680m's fine.

 

no problem with 880m ,sli works fine

 

The issue with 970/980M SLI.. Read man read

 

Can't download it at all. Anybody has a mirror link not from nvidia? The only good driver for like a 2 months and Nvidia immediately deletes it!

 

This is just a laptop driver, not desktop, correct?

 

Working link is http://international.download.nvidi...book-win8-win7-64bit-international-beta-g.exe

 

In this driver, Nvidia finally fixed the 6-year-old bug of limited RGB color range in HDMI and DisplayPort. WOO FREAKIN' HOO!!!

 

Works fine with 980M sli.

 

Nice, ill give this a shot!

 

I will have to test it once my 980M cards arrive. Looks like it won't be until Saturday and I have other plans.

 

i'll have to ask for a definititive guide to installing modded drivers and stuff cos with the amount of INFs going around in the 980M threads is making my head spin (like a record baby, right round, round, round!)

 

I just did some other test to see why they said not to install them.
If you try to disable one card you will get a black screen. Haven't tested it against a hard driver crash yet.
You can enable and disable sli fine, but it seems like it also flashes the display brightness on screen setting. So this could be part of the problem.

Edit: Overclocking seems to be broken as well.

 

still required to mod the drivers? i am curious as to why the drivers need to be modded if they already have support for them?

 

Because your "specific" driver id might not be listed as being supported.

 

m18x R2 Driver Mod with SLI on the Fly

http://www.filedropper.com/34709

 

Are you seeing throttling at stock clocks ? Is it in game, benching or both ?

 

As far as i can tell, it was working fine at stock with no throttling for me, but then im using a modded vbios and not a factory stock one.
Game seem to run fine, but it did lock out over clocking. It could be something I did, but wont know till it get back around to testing it all out. I re installed my original driver and everything is working as it should.

 

Darn, seems like everyone is working against us, lately. Alienware wussing out on cheap new machines and building them with soldered filth, Intel crapping out Haswell turds, now ramming BGA feces down our throats, and now this second wave of NVIDIA bull hockey. They (OEMs) must want all overclockers to die or just go away. I wonder if they don't understand that we will stop buying their crap if it we can't do whatever we want to with it, and we will bad-mouth and ridicule their products all over the internet, so that even the noobs that parrot everything they hear others saying will start to hate it without ever owning it? This is getting to the point of being ridiculous. Seems like there is blockage at every turn now with these so-called enthusiast components. You reckon they are stupid retards, or just downright evil on the inside?

 

All these changes..I wish they were idiots..but I'm almost certain they know what they are doing and their end game is tyrannical control. One must slowly turn up the heat to boil a frog.

 

Tested this new beta set on my desktop, and i've achieved lower overall scores in benchmarks (3Dmark 11 for example went to around P22900 vs P23600 achieved with latest WHQL).

Reverted back to WHQL.

 

For all those people whining, it's a beta driver and not WHQL! It's still better then any AMD driver though

 

I don't see people whining, just reporting their findings on the new beta driver.

Also, AMD driver support has improved by a lot, actually their drivers are showing better frame pacing than NVidia ones in most cases. I own both NVIDIA and AMD and your statement may have been true in the past, not any more.

 

Arrogance and contempt for their most loyal customers due to perceived lack of competition.

I must say, with nVidia refusing to fix the SLI voltage issue and going so far as to proclaim "it's normal" and "the end user gains nothing" (100% fresh bovine excrement), AMD may become the real enthusiast brand once again.

 

Hmm... Doubtful, but still possible. I really like GPU wars, and it would be sweet to see if AMD actually still has something that resembles gonads lurking somewhere in the crotch of their console-loving filth.

So, yeah... go ahead AMD. Show us something worth having in a laptop. I dare ya! In fact, I double-dog dare ya! (But, I'm not holding my breath.)

 

Anyone else seeing these drivers not allowing installation on gtx980m at all? I downloaded from NVidia site just now and looking in nvdmi.inf there are no references to the 980/970m at all! It just returns no compatible hardware found when run.

I thought these could be installed but had the caveat to disable SLI when uninstalling? Has anyone else successfully installed these for gtx980m?

 

They only add support for some systems.

 

I did at least get a pair of cards which have very similar voltage levels so I have not had that headache to deal with for which I am glad.

 

The driver seemed to work fine on my 780M SLI setup. I did notice a bit of texture flashing in CS:GO that never happened before. But that might have been a fluke.

 

OK... Download the 347.09 desktop version and use the files in the zip archive to replace the originals in the Display.Driver folder.

Used registry keys and installation parameters for GTX 980 desktop GPU.

Modded for Alienware and Clevo with the following GPUs:

Code:

NVIDIA_DEV.13C0 = "NVIDIA GeForce GTX 980"
NVIDIA_DEV.11A0 = "NVIDIA GeForce GTX 680M"
NVIDIA_DEV.119F = "NVIDIA GeForce GTX 780M"
NVIDIA_DEV.1198 = "NVIDIA GeForce GTX 880M"
NVIDIA_DEV.13D8 = "NVIDIA GeForce GTX 970M"
NVIDIA_DEV.13D7 = "NVIDIA GeForce GTX 980M"

http://us.download.nvidia.com/Windows/347.09/347.09-win8-win7-winvista-desktop-release-notes.pdf


View attachment 347.09-Desktop-Driver-for-Laptop-Tweak-AW+Clevo.zip
Remember to reboot with Driver Signature Enforcement disabled before attempting to install on a system running Windows 8 or newer OS or the installation will fail.

 

Hello john.
I still get huge throttle even with single 980m with stock vbios.
I know you're working with unlocked vbios. How about stock vbios? Did it work well or did it also throttle?

 

Stock vbios throttle when going above stock.
Voltage does not work on any stock vbios. It's just there for looks.
Brother fox was also able to narrow some more things down having to do with cpu over clocking which help out allot.
But at the end of the day....I would immediately flash a higher power target. Problem is....It's such a hassle to flash anything in the alienware 18/M18r2. And trial and error can take 1 to 100 flashes to find the right setting.

 

One of my friend who experienced the same throttle in m17x R4 said that with 347.09 beta driver, he is not experiencing the throttle any more.
He is testing it with v10 stock vbios.

 

Are you using ThrottleStop? If so, continue using it, but use a hotkey combo to toggle it OFF after setting your clock speeds. You can uncheck the "Set Multiplier" box and that will stop GPU throttling as well, but then you won't be able to change clock speeds. Toggling ThrottleStop ON/OFF is the easy workaround and using hotkeys is effortless.

Try using cTDP overclocking for the Extreme Edition setting in the BIOS. You can still use ThrottleStop to set different overclock values. Using cTDP allows Windows to dynamically adjust the CPU based on load demand. I am getting zero GPU throttling using cTDP overclocking and my Physics scores are exactly the same as using the BIOS option for Extreme Edition overclocking.

You will also need to enable DPTF and install the DPTF drivers for cTDP to shake hands with Windows correctly. Set your overclocking values (power limits and multiplier) on THIS SCREEN and THIS ONE. (Set Turbo Activation Ratio for Profile 0 to 47 instead of 43. I just used some photos I already had to show where to go.) Be sure the Configurable TDP Lock is set to DISABLED or you'll get nowhere with overclocking using cTDP.

Something with the Maxwell vBIOS seems to have hooks into the CPU and the GPUs try to downclock to draw less power if the CPU is running too fast and furious. I don't know how to explain it other than how it looks in layman's terms. Using ThrottleStop to block Windows from dynamically adjusting the CPU clock based on load (which is how I have always rolled) flips a switch on the Maxwell GPU and causes it to throttle. If this is accurate, NVIDIA needs to mind their own business and not care, or even stop to look at what I am doing with my CPU. My gosh, I absolutely LOATHE "efficiency" and "power saving" technology.

I am going out of town to visit family. Be back in a few days. May stop in to check on things if I have time.

 

It appears to cause an issue with Firestrike failing
Also i tested this driver earlier in optimus and when i was playing counter strike GO the game would hang randomly and skip like crazy then just drop me completely... So this driver is buggy as hell from when i tested it a day ago or so, but i never really tested to see if it had a fix for the throttling, this i will do today and report back tomorrow or as soon as i see it return. The one issue is it wont allow for an OC unless you have a modded vBios, which i do so it is being test with that also.

 

So it does look to be stable in a sense that the throttling stops... more so its now just micro throttling for example with my modded vBios it will boost to 1278 then drop to 1126, back and forth through out the whole Heaven benchmark. The issue i mentioned in the last post with this driver, that being the hanging while play counter strike or any game i assume. during Heaven the driver stopped responding 3 times during that run, obviously with a beta driver that is to be expected, but damn that is no bueno, see attachment, and notice the Memory and Core bouncing like a pulse... Not normal, to include the complete non responsive driver crash that is highlighted in yellow.

 

View my post i just made and tell your friend to try the same test i just did, he should experience the chaos, since he is running stock v10 and i am running a decent OC on my BIOS see what he gets during firestrike and Heaven benchmark.

 

Alright so it seems my unlocked vBios was not stable with the clocks i was running at for the 347.09 drivers, and the throttling went away completely. Since there is no OCing support i will be tinkering with a new vBios and testing it out.

 

Going by your picture...Your memory is suppose to be a straight line. Not dropping then return back to normal over and over again. Or did you mean to do that?


Edit:
It should like this for clocks.

 

Yep, fixed that issue had to alter a few things in the vBios, but i still cant seem to iron out the damn drop on the core. After flashing several times to different vBios mods and no success with the core, i decided to watch the P-states. What i noticed was that P0 (1266 core, 2858 mem) enables while running a benchmark... as it is suppose to do, but it immediately drops to P1, and the core drops back to stock boost 1126... and it will repeat this up and down behavior the whole test (view attachment). It seems that the 347.09 driver has some sort of fail safe... Regardless why in the heck is it going to P1??? i even modded P1 to act like P0, but still the damn core drops to 1126.

Is there a string in the 347.09 driver package that is causing this to happen which we are able to modify???

 

I noticed that with this driver GPU clock oftenly drop from 1110 to 500 and even further when I am in a game menu or something. Perhaps it is due to a frame limit I set however I have not noticed this thing before. I thought that maybe that was due to DDU fresh install because at the first time after non-clean install 347.09 I did not see such behavior.

P.S. Mikecacho, do you use programs to tweak GPU BIOS or can do it yourself through HEX editing?

 

Looking at the graph its the power limit kicking in.

 

Nope i use a program, maxwell bios tweaker 1.36. As for DDU that is not the cause at all. What you need to do is shutdown the PC completely and then power it back on if you are just restarting after using DDU it will show all clocks as they should be, meaning no drops and such it will hold full boost. So shut down the PC to allow the BIOS to reset and you will notice the strange behavior.

 

You think? i upped the wattage limit by 17w from stock 103w/108w -- 110w/120w. The card is OC at +137 core and +350 mem.

Update----------------

I could be hitting the power limit on the 240W PSU...