I read in a other threat that a user have the same Windows crash after he flashed prema vbios with the New driver.
I have @Prema vbios too and cant install the New driver. Tried on Win7 / 8.1 and 10!!
Is it a coincidence or try nvidia to block now prema OC mods?
People with the same install problems whats your GPU and vbios?
-
Don't even entertain that thought...they didn't block anything..we have tested several systems with that driver and the Mods just fine. Same systems with same vBIOS, some have problems while others don't. Also it seems to dislike older vBIOS in general (stock or Mod doesn't matter).
That driver is simply a mess for many, stock, mod, notebook, desktop, errors, crashes and black screens for many people:
https://forums.geforce.com/default/...hql-display-driver-feedback-thread-12-21-15-/Last edited: Dec 28, 2015TomJGX, Spartan@HIDevolution, jaybee83 and 3 others like this. -
glad i haven't made the move to the new drivers.
i_pk_pjers_i likes this. -
I'm sorry, but this recalls me situation when mice were crying, were getting pricked but they still continued eating cactus. (they were hungry)
I wanted to write this long time ago but thought that rights of making a choice must be respected... to some limits as appears
Just stop being hungry of newish graphics drivers - it's dangerous afterall. -
Ionising_Radiation ?v = ve*ln(m0/m1)
Why can't they sit down take a deep breath and take however long they need, open-source the drivers, get public feedback for features/bugs/performance issues, and release a sparkling, squeaky clean, bug-free set of drivers?
Is that so hard?Ashtrix, jaybee83, i_pk_pjers_i and 1 other person like this. -
-
Ionising_Radiation ?v = ve*ln(m0/m1)
Damnit. Guess we're stuck with crappy drivers? -
i_pk_pjers_i Even the ppl who never frown eventually break down
-
Until they start losing market share because of it... but that would require AMD to be a significant degree BETTER than them, so word of mouth states it's time to buy AMD.i_pk_pjers_i likes this.
-
meh, sticking to 358.91 for the time being
Sent from my Nexus 5 using Tapatalki_pk_pjers_i likes this. -
i_pk_pjers_i Even the ppl who never frown eventually break down
-
When I stop being lazy, I'm going to 359.00 as it was the last driver that wasn't "for" something. Don't forget guys, this is a "VR driver". May not be for a game, but you know...
jaybee83, TomJGX and Spartan@HIDevolution like this. -
yep, 359.00 is decent enough....359.06 has some issues for me with NCP.
-
I only really update if there's a game I want to play tbh. I bought Just Cause 3 the other day and I was on 358.91, so I just went to the these ones which included JC3 fixes/optimizations/whatever from 359.06. I feel the same way about BIOS updates, if it works pretty much leave it alone until there is something you need/want.
JC3 is pretty neat by the way. I didn't play it pre-patches but it runs quite nicely for me.hmscott likes this. -
I'll wait for a huge sale first
-
I got mine for £18.99 and it's totally worth it.. Game has had 1-2 random crashed in 5-6hrs of play but that's fine! Loving it so far!
-
decided to check out the JC series as well, lets see how it goes
hmscott likes this. -
I don't buy from Steam so I already got it at a large discount (prob the equivalent of 40% off). But I understand if people don't trust those sites.hmscott likes this.
-
Im getting wierd performance issues with even the 359.12 (hotfix for 860M) driver, seemed alright at first. Since I keep too many tabs open, I guess my RAM is reaching it's limit while gaming....effects dota2 more than borderlands presequel, which is super wierd.
And now this is bug ridden, some one need to beat em hard for gimping (Well that was rude..but the driver mess since 5 months after that 347.88. So, It's justified
)
Last edited: Dec 28, 2015Ionising_Radiation likes this. -
I get games there as well. I mean, $15 for a game of the year edition that includes everything.
-
Another nVidia fail. I'm sticking with 359.06... Come on nVidia......
Spartan@HIDevolution likes this. -
Spartan@HIDevolution Company Representative
Clevo just updated the nVIDIA Driver on the P870DM-G to 359.00. must be a golden version since it's approved by them. That's what I'm running nowhmscott likes this. -
so there's a custom clevo NVIDIA driver?
-
i_pk_pjers_i Even the ppl who never frown eventually break down
Nope. It's just Clevo probably thought that the 359.00 is stable/new enough to be "approved" by them. -
ah, i'm already using that driver so i guess it's good
hmscott, Ethrem and i_pk_pjers_i like this. -
I didn't really notice a difference between 359 and 359.06 so I didn't see a point in downgrading but yes, 359 is the most stable driver since 347.88.hmscott, i_pk_pjers_i and Spartan@HIDevolution like this.
-
Spartan@HIDevolution Company Representative
yeah they've very close to each other. The point is, when a manufacturer posts a website, say Aliwnare or CLEVO or whoever, it usually has had to go through a bit more tests than the meaningless nVIDIA WHQL tag which means nothing so I think even though older, it gives me that extra peace of mind to grab a driver from my laptop's manufacturer even if I won't have the latest bells and whistles.hmscott and i_pk_pjers_i like this. -
Another interesting piece of 361.43 info.
It runs fine on AC power for me on Windows 8.1 GT80 SLI-263, but boot from battery the display driver black screens and crashes every 30 seconds.
It's very annoying
@Risechi found the problem, I just confirmed it.
For me I can run 361.43 without problem on AC, and when on battery I run the Intel GPU, so I am going to stay with 361.43 for now.Papusan and Spartan@HIDevolution like this. -
I've started having TDRs with 359.06 so maybe it's time to update. TDRs on the desktop are unacceptable.......
-
Spartan@HIDevolution Company Representative
What is TDR bro? -
Timeout Detection and Recovery. Aka driver crashes.Spartan@HIDevolution likes this.
-
Maybe just use Driver Crash, it's so much more universally recognized
I have to think about it every time you say TDR... -
Well TDR is the official name for it from Microsoft. Its built-in to the WDDM platform and basically resets the video card(s) when it has detected something like 2 seconds where the card(s) have stopped responding as opposed to potentially freezing the system or causing a BSOD or perpetually black screen. It's more a driver reset that Microsoft built-in to Windows than an actual driver crash.
-
Yeah, I know, but you can see TDR's not globally recognized by most everyone
Here are some more globally recognized definitions for TDR
https://en.wikipedia.org/wiki/Time-domain_reflectometer
http://www.urbandictionary.com/define.php?term=TDR
http://www.businessdictionary.com/definition/troubled-debt-restructuring.html -
It took me awhile to get used to TDR too but it's a lot more accurate than calling it a driver crash which would inevitably cause a kernel panic followed by a BSOD or a straight up freeze.
Either way, getting TDRs in 2D mode is unacceptable.hmscott likes this. -
For those following along...
Timeout Detection and Recovery (TDR)
https://msdn.microsoft.com/en-us/library/windows/hardware/ff570087(v=vs.85).aspxPapusan, Ethrem and Spartan@HIDevolution like this. -
Yeah, that's what I was getting booted on battery with 361.43, the little dialog from Nvidia comes up and says "driver restarting" (or something close to it).
That's the visible clue for most people, driver reset, driver restart = driver crash ==> nowhere does it say TDR
Ethrem likes this. -
You know, I wonder if changing the delay til TDR to something like 5 or 10 seconds instead of 2 would help things any?
Its ridiculous that throughout the history of Windows, the most common causes of crashes in unmodified (meaning no hardware or software mods to boost performance of GPUs) systems have always been graphics drivers and audio drivers... You would think they would have fixed that by now. I mean really all TDRs are doing is trying to prevent a bug-check BSOD (it will still do so if you get 5 in 60 seconds) so if you think about how often we see them, the situation has gotten much worse, not better, its just being masked by a smart scheduler that detects it before it happens.hmscott likes this. -
If the frequency of occurance was low, like one or two daily, trying to extend the timeout might help - if the driver actually does recover at some point within 5-10 seconds.
But, for the battery TDR's with 361.43, not really, since it is happening every 30 seconds
-
Yeah I don't try to use my battery at all lol. I'm just thinking if I change the delay, the graphics driver might not actually be crashing, its getting caught up in something it might resolve on its own. I mean I can run Heaven for hours on 359.06 and I have zero issues with these new cards so it seems odd to be getting TDRs from watching video in 2D mode.
There's registry keys that you can modify to change the behavior of TDRs
https://msdn.microsoft.com/en-us/library/windows/hardware/ff569918(v=vs.85).aspx
Might be something I'll look into if I get many more. It just started the other day so for all I know it could be a problem with Chrome's pepper API Flash.hmscott likes this. -
That was lovely... DDU for a clean install, start installing 361.43, system shuts off and restarts itself. =/
Edit: just did it again.hmscott likes this. -
Lol yeah I'm not using these drivers, rolled back to 359. I can't get them to install and DDU is leaving behind the miracast driver and GFE from 359.06 so I just rolled back to 359. What a joke...
-
Correct me if I'm wrong but Nvidia deserved royal Peace Of Crap NBR Award and they worked hard to earn it.
jaybee83, i_pk_pjers_i, Papusan and 2 others like this. -
What I found in the numerous negative feedback here is that the only OK driver was non-GameReady one and that Clevo made it official. I guess it was exactly 359.XX (12 or 00)
It's worth to remember even if i'm not going to try it anyway.Last edited: Jan 10, 2016 -
359 works fine, 359.06 is buggy.
What I don't get is why 3DMark keeps either locking up the system or causing a TDR when it gets to the physics tests. I was playing Lego Harry Potter with DSR at 4K and everything maxed out last night for a few hours without so much as a hiccup but both Fire Strike and that Cloud something or other won't pass the physics test - FS TDRs and Cloud freezes the system. -_-Spartan@HIDevolution, i_pk_pjers_i and hmscott like this. -
Has anyone fixed this drivers? I mean, with my system (check my signature), there is no way I could install these drivers and make it even boot up. It will reboot by itself till the end of times.
I would like to test these drivers because it might solve the problem between SLI 980M with R2 along Prema vBIOS (1.1.1) but as I am not able to boot up I can not tell.
Anyone with an R2 could make these drivers to work?
thanks -
@Prema has already posted here:
http://forum.notebookreview.com/thr...43-findings-fixes.785618/page-6#post-10165174
And, here:
http://forum.notebookreview.com/thr...enix-has-arisen.781814/page-237#post-10164236
And, here:
http://forum.notebookreview.com/thr...enix-has-arisen.781814/page-236#post-10164061Last edited: Jan 11, 2016Ethrem, TomJGX, Prema and 1 other person like this.
nVIDIA Graphics Drivers v361.43 Findings & Fixes
Discussion in 'Gaming (Software and Graphics Cards)' started by Spartan@HIDevolution, Dec 21, 2015.