How many use AW 17 with 120hz screen and still use Win 10?

Is it possible to sum up how many people who use AW 17 or older with 120hz screen and still use Win 10? I am testing the junk Win 10 on my AW17 with 120hz 3D screen before I go back to something else within the deadline(30 days). Excited to see how long it takes before the screen problems come .

 

My Alienware 17 with 120Hz screen has been running Windows 10 without a problem since 29/7/2015. So almost 4 weeks.

 

i'm still waiting for my cable boo hoo!

 

S
Likewise, my AW17 with 120Hz screen been running Windows 10 since 29th July. Single 780M and standard GeForce 353.62. No dramas.

 

+1 here ... Using old driver 353.38 @120Hz/50% brightness

 

Then i wonder who was the 1 that had their panel go bust and what config they have?

 

@andrewsi2012 if I am not mistaken had a 120Hz display that got messed up.

 

That won't help anything. My M18x R2 had Win 10 since the 29/7/2015 too and I never got any issue. I just downgraded (today) because I need to have my emails syncing and W10 didn't want to sync them.

 

They probably would not sync because the Windows 10 trojan bot had already read and copied your emails while they were still on the server. Since they already got they wanted and did not need to harvest them from your hard drive, and you didn't "need" to see them anymore. I'm sure if there was anything important they would have forwarded that to your email client.

 

The 120hz screen wasn't eDP.
Write access is possible with eDP, only more complicated. Mind that all four panels reported so far were LVDS, even the 120Hz LGs (2nd post needs an update).
http://forum.notebookreview.com/thr...ware-lcd-panels.779449/page-101#post-10074947

 

Well there's nothing I can hide there. They are the client, so they already have them since day 1

 

I was not aware Alienware ever had any 120Hz LVDS display panels.

 

then what type is the 120hz panels in the AW17 R1: LVDS or EDP? if it's LVDS then what's the point of it going through the EDP port on the motherboard?

EDIT: the cable i ordered via amazon is now in canada so should get it today or thursday.

 

Lets dumb this down a bit.

LVDS = Standard LCD connection on 60Hz screen that does NOT have screws.

eDP = Slightly larger connection with screw on each side.


Both have different motherboard connections, one in front of the other


Is this right?





The guy who has been extracting info from the faulty displays (at least I think it was him) said the LCD panel I had was a 120Hz with LVDS, but the faulty screen I replaced had a cable with screws, which makes it a eDP cable, is this right????

Maybe I got one of the number wrong when I posted the LCD model number

 

but what i mean is that is the signals going to the panel still LVDS but with an EDP connector because EDP has a different wire config to LVDS.

 

Yes, that is correct. Maybe the model is simply incorrectly identified as LVDS when it is eDP, or the display is dual input capable?

 

Perhaps @t456 is the best suited to provide an explanation for this ? It's nice to get a confirmation of what is right...

 

Wires are wires, regardless whether they serve eDP or LVDS. Connectors too; same are used no matter the interface type. Surest method it to look at the panel's specification sheet or, failing that, the motherboard's schematics.

With this specific panel it's quite tricky; SEC5448 points to about a dozen panels, some of which are lvds, at least. Without the spec. sheet it's a bit of a deduction, but all eDP 3D panels are 50-pin and all LVDS 3D panels are 40-pin (insofar as spec. sheets are available). Good photo of the panel's pcb should clear it, though. By tracing the connections and labels it's possible to tell which interface it uses:

Spoiler: 3D 1080p, eDP vs. LVDS

Hmm ... kinda worried now because of the 'dozen panels' bit ... Samsung has used PnP id SDC4C48 for these lcds, amongst others:

Spoiler: Samsung SDC4C48 "the ubiquitous"

... which is against regulations:

That identifier is pulled from the header of the panel's edid. Comparing the various SDC4C48 edids shows that while the PnP id is identical, the timing values are not:

Spoiler: SDC4C48 edids

The consequence is that we cannot rely upon the device id to id the device . Seriously, though, that is not good! Drivers will have the same problem, after all. Also, if we want to flash an edid to a bricked display; we had better flash the correct one! Pretty sure the 10.8" edid wouldn't play nice with the AW 18 ...

Thing is, 'Horizontal/Vertical Display Size' will fetch a panel of proper size, but that is not to say the same applies to eDP/LVDS. The difference in panel numbers is just a single character at times. One eDP, the other LVDS. If Samsung has used the same id for both types ... that's fairly troubling. It wouldn't even have mattered, actually, but Dell (in its infinite wisdom) replaces the full model strings with its own inventory numbers:

Spoiler: The evil buggers ...

Those are meaningless to keep the panels apart. So ... has better remove all ambiguous edids from the 'correct edids' file. That is, until the edid can be matched to the actual panel nr. as reported on the back of the lcd. Result would be multiple 'unique' pnp ids, but a different edid for each.

Samsung & Dell; wth ?!!!

 

man, i can't find anything on the panel i bought.

 

Brother's AW17 - 4900MQ, 780m uses the 120hz 3D Display with Windows 10. So far no issues.

 

I have now been using Windows 10 since Aug 16 with no major problems. But who knows... Anyway, this OS a huge disappointment. Maybe I buy a Win 7 Pro or Ultimate version or go back to 8.1 after trying out this garbage.

 

still wondering if older drivers are ok to use like 353.49 hotfix.

 

Maybe try Dell's 353.54 driver for Win 10 and AW17 / 18 if you wish to try Win 10?

 

Are there any modded INFs for them?

Sent from my HTC One using Tapatalk

 

been running 10 since launch and have not had any problems aside from an odd graphic glitch when Windows first loads. I get random bars of colour just before windows comes up for about 2 seconds and then they are gone and everything goes back to normal.

 

And, you're OK with that? I'd be concerned about the underlying reason(s) for that and what it may ultimately lead to.

 

Forgot to say that I have walked over from Win X HE to Win 7 Ult. Not without reason .

 

Sure many more will use eDP now that you need it for Pascal cards.
Officially NECROTHREADED ! come my pretty ! Come back to life !

 

The TH1 was a huge mess for Maxwell upgrades or whatever old machines - Not to forget the LVDS Panel bricks and EVGA PX massive misfire when mixed with the Winblows 10.

RS1 seems to be stable for now, but the Ngreedia drivers are still a huge fiasco.. No idea what the future will hold. I don't have the eDP screen neither the Win10 I will shift to 120Hz once I see the 1070 Zotac MXM is fully working with the AW17/ M17x R4 without any hitch, Then Ranger / Voyager notebooks will enjoy a few more years as the Last True Alienware computers.

But yeah the perpetual alpha phase of the Win10 even with Enterprise or LTSB builds is a HUGE PITA, making me to stop downgrading from 8.1 to 10. An Abomination from Micro$lop decimating the PC.

 

W10 is a piece of trash... made by trash for trash-lovers. Every time they spam me with unsolicited email or pop-up survey questions asking for feedback I tell them in a very rude and abusive manner that they suck and so do their products. We cannot even do something as basic as disabling Skype filth in non-Micro$lop web browser using their webmail because they are such retarded Nazis.

 

And here I am, happily computing away on Win 7 Ultimate X64. No reason to ever leave it, not until the security patches stop. It works beautifully, and vulkan > DX12 anyhow.

 

Maybe but Vulkan is dead.

 

LOL ! Who said that ? Nougat 7.x welcomes it and all latest ARM and Custom mobile chips support it, New Engines are adding support like Cry Engine, Unity which previously didn't bother & Proof Exists that Vulkan is amazing - DOOM

DX12 days are numbered.

 

There are even no games coming built with Vulkan when there are dozens of DX12 titles coming. There was only one AAA game that used it and it was DOOM. ID software game, they always wanted to use OpenGL and they always suffered because of that.

ARM and custom mobile chips are not PC market. Silly mobile games may use Vulkan but we want AAA PC titles.

Cry Engine is partially dead as CryTek is going to bankrupt. Unity is the only engine that may change something with Indie titles.

AAA companies also ignore Vulkan because there is no multi-gpu support. They should did multi-gpu support and then release API, not release incomplete API. It's very important for high-performance laptop users to have SLI support.

 

^I agree what you've said but I don't believe Vulkan is dying.

 

Been using Windows 10 since before launch with the 120 hz and never experienced any problems.....

 

I'm having troubles with windows 10 and my 120mhz screen. Ever since I went to it I get endless beep at boot. Have to reboot about 20 times before I get a display normal boot. This only happened when I updated to w10. I've ran a full 2 hr diagnostic check through dells website and everything checks out fine. I put it in sleep mode instead of shutting her down and she loads right back out of sleep perfectly fine.. I don't get it lol?! Maybe motherboard needs replaced, anyone know we're to get one ?

 

From what you describe, it sounds like your laptop screen has the EDID corrupted. If you get 8 beeps-pause-8 beeps endlessly, that is a dead giveaway. This is a known issue and there is a strong indication that the piece of trash known as Windows 10 creates a vulnerability that facilitates that problem. You need to use Linux or a programmer tool to re-flash the EDID. The corrupted EDID is serious problem ONLY DURING POST thanks to Dell's retarded approach to having the BIOS check for EDID every time you turn the machine on. That is why you get the beeping.

*** Windows 10 + NVIDIA WHQL Drivers are Killing Alienware and Clevo LCD Panels *** < Original Report - Breaking News (closed thread)

Windows 10 + GeForce Drivers are Killing Samsung and LG Notebook LCD Display Panels | GeForce Forum < No recent activity

***EVGA Precision X and Windows 7/8/8.1 and especially 10 bricking systems*** < Active Thread here at NBR

 

Oh my Mr .fox that's insane lots of threads I just read through and still not a definitive answer that it is fixed or how to do it simply! ? Ugh.. thanks for the info. Never tried Linux ever.. what programmer tool to use and I have to snip a wire to my screen wtf lol?!

 

Look for the posts by @t456 for instructions and the special Linux package to download in the first and third link in my last post.

It's not difficult and you use a bootable USB thumb drive for that. You don't need to know anything about Linux, just follow the instructions and you should be good to go. Using a programmer tool should be a last resort because it involves spending money. Using Linux costs nothing but your time. It is very fortunate that you can get it to boot once in a while without beeping or you would have to spend money hotswapping a spare screen or buying a programmer. Many of us were not so lucky.

Do not snip any wires... waste of time and won't help anything.

 

ok i've been spoiled by youtube, anyone going to make a video on how to do this. Look at those files and instructions , i dont think i'll be able to do thi

 

I can't make a video as I have nothing to use to make the video demonstrating the fix since I don't have an Alienware with a bricked EDID that I can fix to demonstrate the process. If you are struggling with the instructions provided by @t456 (a few folks did) maybe a condensed version will help. You will still need to use the correct "clean" EDID file from his package so you have something to write to the EEPROM.

You need to learn how to do this, because even if you replace the LCD panel there is always a chance it could happen again under the right (or wrong) conditions.

http://forum.notebookreview.com/thr...levo-lcd-panels.779449/page-158#post-10090770

Below are the steps I followed using a good spare display to fix the bricked one. You could skip the hotswap part if you can catch your machine at a point in time it is willing to POST:

• Booted Mint Linux "Live" distro from my USB thumb drive
• Downloaded this and extracted in "Downloads" folder: ChalkElec/write-edid
• Downloaded this and extracted in "Downloads" folder: bulletmark/edid-rw
  
• Installed these pre-requisite packages:
  Using terminal: sudo apt-get install python-smbus edid-decode
  Using terminal: sudo apt-get install edid-decode
  Using Synaptics Package Manager found and installed i2ctools, edid-decode, read-edid, libparse-edid-perl
• Opened terminal in edid-rw folder and ran this command to confirm the right enumeration
  Command: sudo ./edid-rw 0 | edid-decode (returned errors and garbage, so display 0 not enumerated)
  Command: sudo ./edid-rw 1 | edid-decode (returned good EDID specs, confirmed display 1 was enumerated)
• Downloaded my good SEC5448.bin file and put it in the write-edid folder
• Set run permissions for write-edid program using terminal
  Command: chmod a+x write-edid.sh
  
• Hot-swapped corrupted display panel (unplugged good one, plugged in bad one)
• Opened terminal in write-edid folder and ran this command to flash the EDID to EEPROM
  Command: sudo ./write-edid.sh 1 SEC5448.bin

If you're fed up with Alienware BS and ready to move on to something better, you might want to look into this special offer.
http://www.eurocom.com/ec/future()ec