Hello guys,
i have a big problem while updating to newest nvidia driver.
The screen always went black if i try to update the current driver (359.06).
I have already tried a clean install using DDU and i tried to update using Geforce Experience.
Nothing helped.
Please help me..
I have an alienware 18 with 2 gtx 980m`s inside.
Any previous drivers are working flawlessly without blackscreens or crashes.
-
Stay away from that driver... You will need to reinstall Windows, that driver looks like it's corrupted your installation...
-
There you go... looks like you already know what to do.
-
those drivers are utter crap! stay away: 359.xx is better.
-
Yes sure. I only want to update to newest driver because of the fix of sli throtteling in battlefront..
Lets hope that nvidia will release a new working driver soon..
but thank you guys for your help! -
Edit:
I recently solved the problem with a reflash to the original vbios for the gtx 980m's and i deinstalled evga precision x.
I don't know why but the 361.43 works flawlessly since i did these stepsMr. Fox likes this. -
Precision X is dangerous to use now. Try ASUS GPU Tweak or NVIDIA Inspector instead. Both allow GPU voltage control, whereas MSI Afterburner does not.
-
woodzstack Alezka Computers , Official Clevo reseller.
Jesus... nVidia and drivers in the last year... *Insert more expletives*
-
you shouldn't have to reflash the stock vbios for it to work.
-
I tried it for e few times now.
With stock vbios the driver works perfect and with prema vbios i receaved code 43 in device manager.
Very bad behaviour!
probably @Prema could have a look on it. -
It's driver's problem, doesn't play well with Prema vBIOS! Just get 359.12...
Sent from my LG-H811 using Tapatalk -
Yes i think so..
All previous drivers were working flawlessly. -
woodzstack Alezka Computers , Official Clevo reseller.
Hmm few people getting black screens during install. -
361 is FUBAR and doesn't work with older vbios.
Stock or mod doesn't matter, it just happens that the Mods are based on old vbios.
Same way latest vbios crashes on old driver, again stock or mod doesn't matter.
Even with new vbios the 361 driver creates a lot of problems for user. But if you still want to use it, just use my AW18 vBIOS Mod instead of the Clevo based one. It's based on a newer vBIOS...Last edited: Jan 9, 2016 -
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 Nvidia 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. -
Latest report:
My primary gpu seems to be bad since the driver update..
Always blackscreens.
i changed the primary card with the slave card and now it's working! But only with the slave card in first slothmscott likes this. -
Latest NV drivers are alfa-tests. Better use something older but stable
-
The last couple of drivers they have released are almost like malware. Not sure what the nvidiots are doing, but I really don't appreciate the pathetic garbage drivers they are producing. The introduction of Windows 10 seems to have magically ruined their reputation for producing good drivers, but the timeline may be a coincidence. I haven't seen such a horrible driver mess since back in the days I was trying my best to make AMD GPUs run right and couldn't due to their worthless trash drivers. NVIDIA is just not very good at what they do any more, and they don't have any compelling reason to be. I wish AMD would strike while the iron is hot and release a GeForce killing product on MXM, but I seriously doubt that will happen.
-
chewbakaats58 Notebook Evangelist
I'm having the exact same issue on latest Nvidia drivers..so annoying!
http://forum.notebookreview.com/threads/intel-rapid-store-technology-problem.786690/#post-10176101 -
After few tests i'm sure that one of my gpu's went bad after the driver update. I sent it in for warranty.
-
-
It's too bad that nvidia releases such crappy drivers... shame on nvidia!
But i had luck i will get a new card in a few days thanks to ceg hardcorecustoms.Mr. Fox likes this. -
WTH?? Is this even possible? How could a driver kill a gpu? My 980m died as well but I never even installed 361.43... This is getting seriously depressing... I am shipping back my 980m to eurocom and it would SUCK if the replacement I get dies a few day later because of something as random as a driver installation!!!
Sent from my iPhone using Tapatalk -
Only a few people have the problems not all!
-
Don't be Nvidia's earli adopters. A good advice from me
woodzstack, hans12321, hmscott and 1 other person like this. -
Many of the posts on 45 pages on Nvidia's support forum disagree
Official 361.43 Game Ready WHQL Display Driver Feedback Thread (12/21/15)
https://forums.geforce.com/default/...hql-display-driver-feedback-thread-12-21-15-/ -
woodzstack Alezka Computers , Official Clevo reseller.
EXACTLY. Don't be a test puppy for nVidia, they clearly do not have good Q/A
Avoid drivers that are not at least 1 month old, and do not have any feedback.Last edited: Jan 18, 2016 -
The new beta driver solved the problem for me. (361.60)
Edit: probably ralated to the new card i recently got from warrantyLast edited: Jan 19, 2016 -
@Prema
probably the blackscreen is really related to the vbios.
I got a new card and flashed the modded vbios from you and blackscreen during install. With original vbios everything went through and no blackscreens!
Probably you can have a look at the newest drivers (361.60) if something changed to older one's.
Thank you for your great work I really appreciate your vbios in my aw 18!
-
The latest 361.75 driver is working on my m18xr2 with the vbios driver prema was nice enough to put out tho I'm still trying to nail the issue of my cards dropping to p1 and showing pwr/sli on gpuz under certain conditions on dx11 in ffxiv.
-
My 980M SLI was doing that in the M18xR2 from the very beginning, going all the way back to December 2014. Never could make it stop and finally gave up and bought a P570WM to use the GPUs. A few months later, around March, I started having the same problem with 780M SLI in the M18xR1, M18xR2 and Alienware 18. Any drivers released after 345.20 cause my 780M SLI setups to run like garbage, dropping to 405MHz on core and 400MHz on memory. Chalk it up to NVIDIA GeForce cancer drivers being worthless trash. They haven't released what I would consider to be a truly decent driver in almost a year. I also loosely associate Windows 10 with this. The 780M SLI throttling problems began as they started adding support for Windows 10 to their drivers. Something definitely changed, and whatever they did was not good. Now BSOD, lock-ups, black screens and all sorts of GeForce driver instability issues are causing lots problems for many NVIDIA-powered notebook and desktop users.
-
Hmm. I can keep trying drivers for a while just incase they fix it but if not I can always look into getting that sky x9 that you guys have been working on and get em to ship it without gpus. Would easily shave a grand or so off the price. Also have the option of setting up an 8.1 and 10 dual boot and keep 350.12 working on 8.1 as well. So far only ffxiv is the one thats noticable but theres probably others that might be affected by this that Ive yet to test.
Gonna try setting p1 the same as p0 like prema suggested as well and see if that works.Mr. Fox likes this. -
Good luck. That did not work for me, but it's definitely worth trying. I have also tried using NVIDIA Inspector to force P0 and tried modding the vBIOS so that P0 is the only available performance state, and neither of those tweaks worked. The drivers somehow seem to manage to force it to throttle no matter what for me, which really sucks.
Infinaris likes this. -
Did try the force p0 state but no luck yesterday. Will keep an eye out on that custom bios thread just incase they can get the maxwell cards working with the m18x completely but Ive already considered getting a new laptop as well. The only thing stopping me from goin shut up and take my money on that skyx9 is the fact its not an 18 inch+ screen (very hard to find a BIG laptop). Waiting to see if alienware release a new model 18 series tho its a long shot as well.
Edit: Prema commented on the custom bios tho he said if not done right could burn the board out over time if not careful.Mr. Fox likes this. -
Yeah looks to be doing the same thing for me. Set P1 GPU core clock at 1126 which is what FFXIV is running at and even used force p0. Still switches between p0 and p1. Locking at 60FPS seems to greatly reduce it (and anything above it is pointless with a 60hz monitor anyway.) It still throttles occasionally as before but at least were talking minor throttling of mebbe 5 seconds now and again. With the cap off tho its constantly dropping to P1. Definately has to be something in the driver unfortunately and theres no way to get around it it seems. May have to just simply reinstall win 8.1 on a seperate partition with 350.12 for FFXIV and put win10 on a seperate partition for testing with the latest drivers. Maybe they might fix it but its unlikely atm.
Edit: Just to show you. Where I took off the FPS limit is what I get in a part of pharos sirius where its triggering for me and the other part is what its normally like with the FPS cap. Really odd too since power is all stable and everything.Mr. Fox likes this.
NVIDIA 361.43 blackscreen during installation
Discussion in 'Alienware' started by hans12321, Jan 5, 2016.