Well I am back, sort of.
Reminder of Stats
*Alienware M17x R4 (bought June 2012) w/ Intel i7 3720QM@2.6ghz (Ivy Bridge) including the igpu Intel 4000 HD series
8GB Ram, 17 Inch, SoundBlaster software only Recon 3DI, and the normal stuff that comes with it
*Graphics Card: Originally shipped 660m, upgraded to 7970m, 7970m died early, with community help moved to MSI 4GB 680M (flashed to Dell thanks to @svl7) and installed I think 314.xx drivers with help from many (sorry can't remember everyone but notable was @J95), was running 7970m in whatever they called their hybrid drivers, the 680m is run in Optimus)
*OS: Windows 7 64bit Service Pack 1
*Storage: Msata 1tb Samsung 850 Evo, 2 Hitachi 1TB 7200 rpm 2.5" drives (yes I used all 3 GB or will)
So what will you read. What got me started on this project and then using all the resources on the net, from @J95 and legions of others I owe all credit for the project too. Please note I take no credit, take no rights, this is simply something to help others out based on working with what has already been laid down for us. Installing the latest Nvidia 417.67 mobile/notebook drivers for a 680m for Windows 7 Service Pack 1 on Alienware M17x R4
When I got things up and running back in 2016/2017 with the noted people above I saw a new driver and with the STO game having a driver issue I upgraded to it. Now I didn't notice anything wrong, the game worked and so paid no attention. When I started to get unable to eject 680m error messages I thought great who got this, ejecting a gpu, wrong. I then tried the uninstall Intel, Nvidia, use DDU in Safe Mode, disable AV/Firewall, disable driver enforcement, etc then reinstall intel, nvidia (removing certain folders) with the modified inf but now the game said it couldn't find any feature set and wouldn't let me play. Finally removing the Nvidia drivers allowed at least the iGPU to run the game. Used Unigine Heaven 4.0 to encounter more errors with Nvidia.
I moved back to my msata install of windows 7 that I haven't had a chance to work on since 2017 (i know pathetic) that only had system drivers, expired Norton, and not yet registered/activation. Seems fine. Tried to run Heaven, same error. Well after 3 days of trying to duplicate what I had been instructed to do, I finally sat down with a nice big bottle of Fiji Water (courtesy of lovely lady at the Oscars in almost every background pic) and decided I was determined to fix things. I downloaded the 419.67, copied the nv_dispi.inf & nvdmi.inf to get to work. After reading the content and using comparisons once again from the noted individuals and the legions of other, I had them modified and decided to give it a try on the clean win 7 install from 2 years ago. After the uninstall, ddu, deleting folders, copying mod. inf to their directory (also included the change to setup.cfg - credit once again goes to individuals like @J95), gyrxiur, DeathAngel , creator of Notepad++, sora and many others) I was able to launch the Heaven 4.0 Benchmark. So I am assuming that I have the new 419.67 working on my system. I did a benchmark of the 680m in 419.67 with unigine Heaven 4 to go with the files I am posting. Please note the bios was provided by I believe @svl7 (sorry if I got wrong person) and no overclocking of it other than what the changed vbios did.
I am attaching below the following:
Nvidia 419.67 modified inf and config - nvdmi.inf, nv_dispi.inf, setup.cfg (no credit to me all credit belongs to others)
The Unigine benchmark results (txt file).
Now the shortened legalize warning
Please remember you are to take all risk when using modified inf files, I take no responsibility (no virus or other dildrus included) if they don't work with your GPU. The usual.
This was tested and used on Alienware M17x R4 running the last bios they released A12 or A13 and so it the system bios is not modified at all, the card is a MSI 680m 4Gb flashed vbios to Dell 680m 4GB, and installed in Windows 7 64bit Service Pack 1. Hopefully if you have only a different card you can make any minor adjustments you need to.
Please let me know how they work. I will also be reporting back on the reinstall on my other laptop install I use to play Neverwinter/ Star Trek Online - was suppose to be a temp solution till new install was finished, and if they worked on it as well.
Alienware M17x R4 680m 419.67 Mod Inf and Setup and Heaven 4 Benchmark.zip
I picked up a Dell 680m - vBIOS 80.04.5B.00.02 - I think it is a 2GB version after doing some photo comparisons online.
After doing some research I fitted it into my Clevo P150HM hoping it would work, but and I get no POST, the LCD screen is blank, the HDD light does show activity but after ~ 15 seconds or so, 3 blinking lights appear on the left (power light, caps and insert buttons?) and the computer beeps about 4 times before it completely powers off.
I'm guessing that I'm going to need to flash it to a clevo bios since the clevo bios doesn't recognise the dell vBIOS?
I am running the latest 1.01.14 bios and 1.00.13 EC firmware for my P150hm.
Does anyone have any ideas on what I can do? I thought i would at least get a POST but then struggle with the driver installation but i cant even get it to POST...
My issue: one of the two 680M GPUs started displaying an "Windows has stopped this device because it has reported problems. (Code 43)". My hardware: Clevo P37EM / Sager NP9370 My OS: Windows 10 Enterprise 2016 LTSB x64 I keep the OS always up-to-date (Windows LTSB only ships security and fix updates). I also have very few softwares installed. Basically, my computer was working normally, but today I was playing Overwatch (which I always play) and after some hours, I suddenly heard a Windows beep, the game froze and the computer restarted. When I was back at the desktop, I noticed the resolution was not right and then I opened the Device Manager to see that one of the 680M was giving a Error Code 43. Both GPUs appear on my BIOS setup, the BIOS correctly identifies them as 680M. I found it strange, so I check my GPU VBIOS and noticed something odd, one of them was at 80.04.33.00.10 and the other was at 80.04.67.00.01 (I get these drivers here). I know for a fact that since some older NVIDIA Driver, the VBIOS must be 80.04.33.00.10 or else I got some errors on this SAGER model, so I flash 33 on both a while back. I then proceeded to flash the correct version again. When I run DDU I notice it only detects the VBIOS version for one of the GPUs, the other one doesn't show the VBIOS version. My results are: NV Driver 398.36 ROM 33 PCI BUS 2 working PCI BUS 1 error code 43 ROM 67 PCI BUS 2 working PCI BUS 1 error code 43 NV Driver 391.35 ROM 33 PCI BUS 2 working PCI BUS 1 error code 43 ROM 67 PCI BUS 2 working PCI BUS 1 error code 43 Can a Nvidia update or Windows update brick a GPU? How can I know if it's a software or hardware issue? I'm afraid that one GPU died as I don't have the money to replace it now and it would be difficult to find a spare new 680M (which is now old hardware) where I live. I'm panicking a little...
M17xR4 upgrade 680m to 1060
I kindly apologise for my atrocious formatting, I have never written such a long thread before.
Hey everyone, this is my experience regarding upgrading my m17xR4(2012) with a 680m and a 3D 120hz display to a GTX 1060. Please bear with me as it will be a long story.
A little bit of background, on May 11, 2017, my laptop suddenly shut itself down when playing some Witcher 3. No response, no power, no lights, certainly dead.
Called Dell India, they recommended motherboard replacement (not quite as much as a recommendation but as an only option.) 15000INR for that. (~235USD)
Still not resolved, no light, no post, no power. But if I remove the 680m, the laptop boots but gives 8 beeps, indicating a GPU or LCD failure. Putting the gpu back in causes a short circuit and no power to system.
Dell technician recommended GPU and LCD replacement. Will cost about 15000INR(235USSD) for GPU and 8000INR(125USD) for the LCD.
Sure, why not.
New GPU time. And boy oh boy, I was in for a headache.
Initial plan was for GTX 980m, easy and simple upgrade, tried and tested.
I contacted @woodzstack, he suggested me the 1060, approx. 30% more performance for the same price. I went ahead with that.
He is a well-known and an excellent seller here on NBR and other forums.
So I got myself a 1060 with a heatsink. The heatsink on my 680m had worn out screws and I couldn’t remove it to reuse it (tried a Dremel to make grooves). The 1060 was available and ready to ship, the heatsink was on back order which caused some delay. Thankfully, woodzstack provided me with a free upgrade to faster shipping. Thanks!
Then came the headaches. As I didn’t have a backup or fall back gpu (680m died), I wasn’t able to change the settings in bios required for 1060 and the system won’t boot with a 1060 ass the settings were incorrect. Also, I had the motherboard replaced which had stock bios. Got 8 beeps with 1060 installed, indicating gpu or LCD failure, which it wasn’t. Also, being a 120hz 3d display, I couldn’t use the intel gpu, as it won’t be able to run the display.
Stuck in catch22 situation there. I contemplated returning the gpu as I hadn’t gotten it to work, and it had gotten quite expensive(motherboard+gpu+heatsink). I posted on various forums for 2nd hand 680Ms or even lower gpu. Woodzstack offered a 680M but shipping was quite expensive.
Then @maxslo came to my rescue, he offered a used Quadro K1000M. Just pay for shipping and its mine. Notebookcheck states that its equivalent to a GT 630M, so it was from my series of gpu. I didn’t know if it would work or not, I took a gamble, if it didn’t work I would return all the stuff and get a new laptop (or a desktop maybe?)
It took its own sweet time to come as it was via national post (can’t complain, got the card only for shipping cost)
And when it came, I installed it, hit the power. I TURNED ON. It was alive!
I quickly got into bios, changed the settings and installed the 1060.
But alas, it didn’t start. 8 beeps again. Woodzstack helped here again.
The issue was default display setting in bios and the uefi settings. Uefi needs a compatible gpu to save that setting and boot with that gpu. As k1000m wasn’t a uefi compliant gpu, I was stuck again. But changing the graphics settings to auto and then it let me disable the legacy settings.
After applying these settings and installing the 1060, it let me boot.
No bootable media detected. Press any key to restart.
Turns out that the gtx 1060 is fussy even about bot drive partitions. Had to reinstall windows on a GPT partition. MBR to GPT conversion did not work. Needed a fresh install.
Finally, after 3 months of patience, I could revive my laptop.
II would like to thank these threads and their authors
Note: for 680m, the benchmark was done on max overclock +300 core and +500 memory. Stock score would be nearer to 3DM11 P=6300-6500, Ex=2200-2400
Unfortunately, I don’t have 3dmark scores for 680m
Note: This is same as my thread on NBR. Posting here as well for people not on NBR.