-
Similar Content
-
By Guardian241
Hi,
I've recently got my hands on an M17x R4 Alienware Laptop from 2013 which I love. I've replaced the screen, keyboard, RAM, and hard drive to make it into a fully modern laptop. However, I'm currently waiting on a replacement for the 680m GPU with a 980m from ebay. My question for you all is, do I need to do anything with the BIOS to make this 980m work? Is there a way to prevent the laptop from using Intel HD Graphics with Optimus? I think the Intel HD Graphics on this laptop are currently broken as I see static-looking dots flash on the screen. (See image below for example). My theory is that because Intel HD Graphics with Optimus is still in-use while in-game, the dots are being caused by it.
Thanks for any help in advance.
- M
-
By Crustieraxe
Hello Guys this is my first post here!
So my original post was this:
"I don't even know if any active forum is out there on this laptop and on this issue, but after installing my new DHCG2 LTN173HT02 120hz display, I am unable to boot up on it. I do have a modded bios which the video setting is set to PEG, and just about read every forum about this but have not found a solution. I have tried resetting the bios, made sure the cable is plugged into the Edp port, and have made sure I have an UFEI Windows installation and legacy mode is turned off. I don't know what else to do and if anyone could help it would mean alot to me! "
The reason it was not booting up on a pure UEFI environment is because my 660m did not have the GOP compliant driver vbios. You would need this in order to boot up in a pure UEFI environment which at the time I didn't know, and my fix was to stick to legacy. Any card before the 660m will most likely require this if you need to boot up in a pure UEFI environment. If you do not have this vbios driver while it is set to UEFI and plug in the 120hz lcd, it will beep 8 times and you will be forced to plug back in the 60hz display to change it back to legacy.
This was the vbios that I can say worked for me and had the GOP compliant driver for the 660m
https://www.techpowerup.com/vgabios/144032/144032
------------------------------------------------------------------
These are the steps to upgrade from a normal 1600x900 60hz display to a 1920x1080 3D 120hz Display which is needed if you want to update your graphics card to a more modern one.
I am making this guide because I felt frustrated that for this awesome computer, there aren't really any post in 2020 to upgrade the LCD panel to the 3D 120hz one. And The older posts I scavaged through really helped me little in doing this upgrade.
Anyways lets begin
1) If you have a stock AMD graphics card, and are wanting to install the 120hz display, then your journey ends here and you will have to upgrade to an NVIDIA graphics card to do so. If you have an NVIDIA, you may continue
1a) ( Only if upgrading to pascal graphics card )Your NVIDIA card Needs to have a GOP compliant vbios or else it will not let you select the UEFI option on the bios. This is needed because you need to set a UEFI environment before upgrading to a 1060/1070 Since these cards don't support legacy mode. This means you will need to flash a vbios onto your card that will allow you to boot on a UEFI Environment. You will need to verify first wether your card has a GOP compliant vbios by searching up your vbios version in GPU-Z. If you have a 660m that doesn't have this, then here is the link to that vbios that does. https://www.techpowerup.com/vgabios/144032/144032 I think that all of the Nvida 6XXm are not GOP driver compliant and need this but do not quote me.
2) On the 60hz display, I would start by making sure that you have windows 10 installed or reinstall with UEFI support as it is needed if you are installing a pascal graphics card. If you have legacy mode enabled, and are not planning to upgrade to a pascal graphics card and keeping your old Nvidia 6XXM, then disregard this and head on to step 5 (although I would recommend to read everything)
3) turn the laptop off and boot into the bios. In order to boot into the bios, spam the F2 key while it is turning on.
4) Once in the bios, go to the Boot menu, and make sure to Disable "Secure Boot", Make sure that importantly if you converted over to a UEFI installation of windows, UEFI mode is chosen (UEFI Environment will be needed for a pascal graphic card and legacy will not be compatible) then again, if you are on a legacy installation of windows 10, disregard this if you don't want to upgrade to a pascal graphics card.
5) we can now start looking at the 120hz display. I bought mine on ebay with this seller https://www.ebay.com/itm/New-Dell-Alienware-M17X-R4-17-3-FHD-WLED-3D-V-M-LCD-Screen-DP-N-DHCG2-GN36T/273644412867?hash=item3fb67a5fc3:g:9A0AAOSw5AhcP1pw:sc:USPSPriority!32720!US!-1 (Just in case the link goes bad, this was the listing name"Alienware M17X R4 17.3" FHD WLED 3D V M LCD Screen DP/N DHCG2 GN36T" with the screen model being LTN173HT02 and Dell part number GN36T )
6) Since my listing came with the video cables, I did not have to go out and look for the video cable. If yours did not come with the cables, You will also NEED to get the video cable it is required. the Dell Part number is N392W. I cannot stress enough This video cable is required and the 60hz's video cable CANNOT be used with the 120hz one or else you will brick your computer from what I read.
7) Once it comes In, we can start to take apart the computer to Install our new display. I watched this video to remove the old 60hz and install the 120hz panel
8) Before I would remove the whole 60hz lcd panel, I would first make sure that you can boot on the 120hz panel. Notice that there is one connecter with screws on both sides right next to where the 60hz screen connecter is. Make sure that you put the 120hz one with the connector where screws are. This is known as the Edp port and cannot be confused with the LVDS port. Again, you want to plug the new 120hz display into the EDP port and unplug the 60hz one.
9) If the installation was done correctly, then you should have no problem booting with the screen. if it is giving you 8 beeps, then just plug in the 60hz display, and navigate back to the bios to make sure everything is in order and refer back to steps 2-3. If you happen to be an advanced user like me and went ahead and installed a modded bios, then on the 60hz display make sure that the video setting is set to PEG. I dont think this is necessary to have a modded bios since the bios automatically changes the video setting when the 120hz display is detected and should be a last resort option to install a modded bios. I got my modded A12 bios from a guy in this forum named klem for 10 US dollars thorough paypal. Shoot him a message in the forum below.
10) Once the new LCD is tested and you know you can boot up with no problems, go ahead and finish removing the old 60hz LCD and proceed to finish installing the 120hz LCD. And you are done.
A couple of words from my personal experience: When I installed the 120hz display, and booted up windows on it, and turned the computer off, it refused to turn on for some weird reason. I don't know why it would turn on when the AC and battery where on. regardless of what this was, I fixed it by Reseting the CMOS. If you don't know how to do this, do a quick google search and after turning it on i got 5 beeps which i then turned the computer off, and then turned it back on which the computer just reset itself and when it turned back on I was able to boot up into windows.
This is the forum that I was able to find about upgrading the graphics card to the 1060.
Anyways I hope I at least helped someone transform their computer! In 2020!
-
By danger007
Well I am back, sort of.
Reminder of Stats
*Alienware M17x R4 (bought June 2012) w/ Intel i7 [email protected] (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
-
By MessiWessi
Hi,
I bought a alienware m17x r4 a few weeks ago. The problem is: I have noise (distorsion) on the right speaker. Had anybody in past the same problem and is it a known problem regarding this model? I feared at the beginning that the soundblaster is defect but I tested it with headphones and everything is fine. I already ordered a new speaker pair and will install it within the next weeks.
But if you tell me that this problem is known and not resolvable I can save my effort.
-
By Skyl3r
Hello all,
I purchased a Clevo 980m to upgrade my current system as described below:
Alienware m17x r4 24GB (8+8+4+4) i7-3920xm GTX 680m SVL7 A11v2 Unlocked BIOS Windows 10 Professional
I was able to install the GPU with no major issues. (Had to remove the clevo backplate, and use the clevo screws instead of the Dell screws).
What I attempted to do to make the GPU work was the following:
Before install, I set laptop to UEFI, disabled legacy ROM, enabled Windows 8 Fast Boot. I also left switchable graphics on, because I am fine with Optimus I booted the laptop and did a clean install of Windows 10 Windows 10 automagically detected my hardware, including the 980m. So I tried just downloading 980m drivers from NVidia and installing them The 980m does not work. It shows in Device manager with the yellow exclamation point saying "Windows has detected a problem with this device ..." So I tried running DDU, then modifying the INF by following the guide here https://null-src.com/posts/nvidia-notebook-driver-inf-mod/post.php (I searched for a device in the Dell/Alienware .inf that had a PC model code of 0551 which I obtained from the hardware ID of the 980m, then cloned that line, changing the GPU model code to reflect the 980m's GPU model code. Then added an entry into the [Strings] section for it.) I had the same results after installing the drivers with my (perhaps incorrectly?) modified INF. I tried rebooting with PEG only and Integrated disabled, then running DDU and reinstalling using the same modified .INF and had the same results. Windows loads fine, and ONLY shows the 980m in device manager, but still says it has an issue.
Above is what I did in the order I did it.
Does anyone have an idea if I did something completely wrong or I missed a step or anything? I heard this was the best place to ask
EDIT:
This has been solved now. Thanks much to naightmehr. The solution was a correctly modified .inf file with the right driver version.
If you find yourself in the same situation try installing some old driver verisons. The one that worked for me was 352.84! Rock on fellas!
-