*OFFICIAL* Alienware 17 R2/R3 Owner's Lounge

So 17r2 won't power up (again). This time the power light comes on as if the laptop is sleeping, but turns off immediately once pressed.

The power light only comes on (sometimes) when the power cable and battery are both connected. If the power cable is not, then nothing lights up.

Edit: Never mind, power button to motherboard connection was damaged, that'll need to be replaced.

 

Does anybody know of a way to reset the phyiscal bios password on the 17 r2 please? i have pulled the CMOS battery once, it's still logged in guessing NVRAM?

 

Trying to use this guide but it's a mess, and it links off to some other thread that is supposed to have a Prema MEI tool that is nowhere to be found.

It also doesn't mention how to get an Intel ME .bin file.

Anyway, after messing around I see that my problem is likely that I'm stuck on ME firmware version 11.0.0.1194 H, and the Alienware 15R2/17R3 BIOS install doesn't update the ME firmware even though Local FWUpdate is Enabled for me.

How do I get the ME firmware updated? Do I just grab a .bin file from Station Drivers and use FWUpdLcl64.exe to install it? If so, which .bin file do I want?

 

When you click Prema ME11 tool link which will direct you to another thread. On that thread click the link Team Blog which will redirect you to prema's website where you can download the MEtool to update.
OR heres the link:
https://premamod.wordpress.com/
Once you in prema's website go to maintenance tab then firmware update. You should fine the MEtool for ME version 11.
Also on guide http://forum.notebookreview.com/thr...-17-r3-or-possibly-other-bgas-as-well.813803/
I will skip guide number 4 5 6 and 7 as I believe are not essential. Just install Dell's ME driver which is this http://www.dell.com/support/home/uk/en/ukbsdt1/drivers/driversdetails?driverId=7CDG2
then carry on.
Please see and try the guide as you localME Firmware update is enable. You will have mo chance of success compare to me which mine is disabled. Hope this helps.

 

Earlier I linked to the MEIFW directly but Prema asked to add website instead of direct link so that any user must read T&C before patching.
You can get the file from Win-raid called MEI 11 system tools and FW. Or unzip Prema ME11 tool and open Powershell or cmd as admin by pointing to the directory and use the cmd I mentioned in the guide.
If you need more clarification PM me.

 

Thanks, I got it sorted: http://forum.notebookreview.com/thr...ther-bgas-as-well.813803/page-8#post-10700807

Local FWUpdate was enabled for me, but the Prema thing disabled it and then tripped over itself because of that. Shorting the CLRP1 pins under my RAM was required to clear the CMOS and re-enable local FWUpdate, then I was able to flash using stuff from the win-raid forum/thread.

Thanks for trying to help, but the Prema site/tool and "Updating Intel ME Firmware" thread were more confusing than helpful on the whole.

 

I got an email from Dell today talking about a critical nVidia driver update to GTX 960/970/980M in Alienware 13/15/17's.

Should I install this or just update my standard nVidia software via Geforce now?

 

Use the latest driver from nvidia. Usually dell doesn't email you. It might be Dell update notified you of the update.

 

Dell's stuff is almost always ancient compared to what you can get directly from the hardware vendor. Presumably this is because Dell runs some level of compatibility testing on every version they release, and they have a never-ending queue of testing to do.

 

This is exactly whats up. They do indeed soem testing and repackage it for distribution through their channels.

 

Hi my first post the forum .

I recently got a 17 r2 with 4710hq and 980m very cheap to replace a dead gigabyte p35 . this is my first Alienware/Dell product so thought I would give it a go. lovely design but over the last 4 weeks of using it mainly for gaming I noticed something wasn't right .
So with a little google search I found this forum and I have spent the last couple weeks going through all the posts and got my knowledge on the 17 r2 the 1st thing I did was flashed the 980m with a modded vbios . I also done my home work on throttlestop and I am currently running a -70mV underclock and my temperatures don't go over 89c with a fresh thermal repaste.

The system came with the 180w power brick . It is currently running the latest A10 bios but I still get random fps drops which really are annoying .

So my question is basically is anyone still using the AW 17 2R2 and what bios you using and will the 240/330w Supply defiantly help as DELL/Alienware wont give me one as I`m not the original owner and plus its out of warranty , as I really don't wont to spend £70+ on "possible" fix

Sorry for the long 1st post thanks for any input

 

240w psu will help but not 100% sure if it will fully fix the dreaded 799MHz syndrome. See also http://forum.notebookreview.com/thr...tles-to-0-78-ghz-xtu-says-thermal-but.801219/

@VICKYGAMEBOY can probably help.

 

@Papusan
Cheers I`ve done powercut in throttle stop but didn't think of locking the CPU @3.0GHZ

locked the CPU @3.1GHZ OMG why didn't I do this earlier it has made a 100% improvement. no limit reasons in throttlestop either but still getting a micro second where the FPS drop by about 10-15 fps , could this be the GPU lacking gigawatts from the 180W power brick?

 

I've had a problem recently,

Whenever I am running a game at max load, my charger turns on/off. And another problem that has risen is that I have insane screen tearing now when I don't run v-sync, which was not the case before.

This problem started occurring around 3 months ago.

Specs:
Alienware 17 R2
Bios A10
i7-4720HQ
GTX 980M
16GB RAM

I thought it was GPU drivers but rolling back and updating further didn't change anything.

 

You need 230W or more Watts adapter if you're overclocking the CPU upwards of 3.5GHz. @judal57 has locked all core turbo to 31X using throttlestop and with undervolting the power is reduced. Look at removing nvidia bloatware drivers and go for minimal install which will reduce the screen tearing if recording option is enabled in nv GFE.

 

Yeah, I have the 240W adapter, and I used to be able to have GFE overlay on w/ recording (which I don't even use anymore) and it still didn't tear as bad. I'm going to try using throttlestop now though.

I also don't know what you mean by removing Nvidia bloatware drivers. I have the 3D Vision, HD Audio, Graphics, PhysX, and GFE drivers installed.

 

I don't install 3d vision, GFE and other bloatwares after seeing custom j95 nv mods. Additionally, try the desktop nvidia drivers I'm desktop ones these days since I felt notebook drivers were slowing down/throttling my 980M.

 

There is always screen tearing without vsync. It might that before you had vsync forced in drivers or something like that. Borderless window mode also enabled vsync even though the game says not.

Regarsing your psu turning off. Might be the internal dc in cable that's fried.

 

even i install driver only, with physx software and hd audio.. no 3d and GFE. btw u got throttle on gpu ??

 

Yeah I noticed the degraded performance on newer notebook driver post 376.xx drivers.

 

Hmm, i have to test this out, but how do u install desktop driver, does the inf contains 980m ??

 

Papusan said 980 had a notebook version which didn't have M variant so I installed desktop driver and it supports most GPU dating back to keplers.
One difference is you need to keep nvaad folder intact if you use hdmi quite often.

 

You might be right in that there was some sort of vsync enabled because I don't see any other explanation.

I forgot to mention that I did try another charger, and I still had the same problems if that's what you mean by internal dc in the cable.

 

He meant to open back panel and check cable next to battery cable and see if its burnt or not?

 

can the 17r3 980M still be overclocked using Afterburner? I've always oced using it but I don't since when it started to stop working, the core and memory slider had been greyed out. All drivers and software version at latest update

 

Use nvidia inspector.

 

Follow @Mr. Fox guide.. http://forum.notebookreview.com/thr...rvolting-overclocking-and-overvolting.817033/
I assume you have prema's vbios.. If so you can use MSI Afterburner as it is what I am using.. Hope this help and Thank Mr. Fox. hehehe..

EDIT:
Heads up in case you are using RivaTuner OSD for PUBG. If you use OSD it will cause a micro stuttering. A alternative solution is to create a profile in RivaTuner and set Application Detection Level to None. What I do I open PUBG with global setting where OSD is working. I then alt tab and add the profile of PUBG and set Application Level to None. If you do that the OSD screen/monitor will still be there and no Micro Stuttering.. Hope this helps..

 

Not sure you can increase voltage and limits for Maxwell graphics (17r3 980M) with MSI Afterburner.

 

aw maybe.. dont really know.. I have the 970m(Maxwell card) and msi afterburner works for me.. sry if i have given the wrong info..

Edited:
Here's a Image of my Afterburner with Core Voltage is not grayed out.

 

You can set core voltages in MSI AB? I am seeing grayed out option in older MSI AB UI. So I use nvi inspector to overvolt.

 

You need to follow @Mr. Fox guide which is posted in the previous post so that it won't be grayed out.. This is me assuming you have a modded vbios..

 

thanks

I've been using that bios all the time. MSI Afterburner used to work for me but I don't know since when it just stopped working. Its been quite a while since I went to check because I just leave it to start up automatically when I boot windows

[EDIT] the weird thing about my issue.... I can adjust core voltage and temp limit, these are not greyed out.

 

@0lok Thanks for pointing @Mr. Fox video.
Now its working. For some reason, my 980M uses 1.075V when active.

 

So I just reinstalled Afterburner and its working as it should now.... probably something fked up in between the long inactive period

[EDIT] wait no... it's still the same. Core clock and mem clock sliders greyed out, voltage slider can be adjusted. Guess I'll try nvidiainspector

 

Have you watch Mr. Fox vid guide and the description? It should work if you follow it..

 

yes I've tried it, editted the files. Didn't work

 

Just add these lines on top of existing nvidia profile in MSI AB/profiles/

Code:

[Startup]
Format=2
CoreClkBoost=
MemClkBoost=
ThermalLimit=
ThermalPrioritize=
CoreVoltageBoost=
[Settings]
VDDC_Generic_Detection=1

The file name will be something like this: VEN_10DE&DEV_13D7&SUBSYS_07081028&REV_A1&BUS_1&DEV_0&FN_0.cfg

 

That's what I did, according to the video. I even edited the other file which I believe belongs to my Intel GPU, as Mr Fox said in the description that you should edit both. Nothing changed after I restarted Afterburner, only the voltage slider is available for adjustment.

NvidiaInspector is working fine for me now

 

I didn't change intel profile at all! You need to change the old UI to new UI for example, Cyborg edition.

 

Hello.
I currently have a 17R3 laptop and it seems to me like it just takes forever to boot up. Is there anyway to speed this up.

 

Try updating to latest KIONIXX sensor driver from 15 r4. If it doesn't fix it, check your RAM modules by testing one at a time. Mine had the same issues and its root cause was bad RAM.

 

Thank you for a reply I will try it

 

Has anyone had any issues with the Trusted Platform Module 2.0 driver loading correctly in Windows 10? About 50% of the time after I boot, my device manager indicates it is "not working properly". I'm on BIOS 1.3.12 and updated my Intel ME firmware manually per HunterZ0's method on this thread a little while back. I do believe I was having the issue before I did the ME firmware update as well. I've tried doing some research on the issue, but don't see much for solutions with the exception of lots of suggestions to update the BIOS to the latest version. Based on what I read around here though, I should stay away from 1.4.4.

 

Switch off secure boot and boot windows. Afterwards, shutdown the PC. Now, go to BIOS and switch back to secure boot. Now, you should see TPM working fine until the problem pops up.

 

I had this problem with the original ME firmware 11.0. Since the Clear CMOS and the manual upgrade to ME version 11.8 it never appeared again.

 

If you never change Secure boot status you won't get the error. I frequently change secure boot modes testing YUMI and other things.

 

I did two days ago to use a Live CD for secure erasing my SSD without triggering the error. Before with ME firmware 11.0 the error appeared on every second boot with or without changing the secure boot setting.

 

I disabled Secure Boot and Windows would not boot as expected (got an error that system storage device could not be accessed or something like that). I re-enable Secure Boot and had the same issue on the second boot.

 

Are you using RAID?

 

RAID is indeed enabled in BIOS.