*** Windows 10 + NVIDIA WHQL Drivers are Killing Alienware and Clevo LCD Panels ***

no, there's no cases of 120hz panels going bust yet, doesn't mean they will or won't.

 

My thoughts exactly

120 Hz here using 353.38 hotfix and working so far normal and even using 3D vision.

I need to mention that I never go beyond 50% brightness cuz it hurts my eyes and I never OC the screen beyond 120 Hz

 

it must be something to do with how EDP is detecting the display. still haven't gotten my cable yet.

 

Hi, if it was 8 beeps with black screen, try the following to see if it works:
FYI my model is Alienware 18 980M Sli

1) open up the case and remove two Nvidia Cards
2) reboot the machine, it should boot with on-board intel video cards
3) to see if your screen is light up

This is to check if your LCD is burnt out or not.
I came across the 8 beep thing when Dell replaced my MB, which originally the bios boots with Legacy mode, not EFI.

Currently my AW 18 installed Windows 10 with 353.62, my lap is connected with a DELL U2913WM (HDMI) , using it for days, heavy use, all fine.
Having been using insider Win 10 with previous NV drivers for months, all fine.
Maybe it is because the U2913 screen

 

Zipped entire INF directory and uploaded it here.
What about G-Sync panel validator? Is that means we can get G-Sync support for built-in monitors?

 

accidentally stumbled across this thread.
i just upgraded to w10 and now reverted back to w7.

 

I can confirm theae drivers arent good. I installed em in my alienware prior to rolling back to 8.1. Found out with gpu-z that with ffxiv running the gpu ram was only at 180mbish instead of the normal rate of 2gbish ie 10% of normal operation levels.

 

Actually, that is an SLI issue with Nvidia drivers and Windows 10 not reporting the correct usage. I have verified that the correct VRAM usage is reported with Windows 10 on my desktop PC when NOT using SLI.

 

i'm still out of a working a m18x r2 and two LCD. Lucky my AW 18 came back online (power button/board issue).

 

Windows 10 + nVidia driver 355.60 bricked LG display on Alienware M17x R4:

Just to rule out any driver issues etc I re-installed Windows 10 (UEFI, legacy off, secure boot off) on my spare SSD. When no drivers are installed yet, built in display works fine to the point. If Intel VGA drivers are installed, internal display goes black and stays like that. The only way to to get the picture back is by plugging hdmi in and uninstalling the Intel VGA drivers. nVidia drivers can be installed with a modded inf as usual, but GPU does not work properly (due to no Intel drivers, therefore broken Optimus I suppose). nVidia card does not work properly on external display either (in fact, hdmi no longer works when nVidia drivers are installed). I am 100% confident now that my LG display firmaware was overwritten somehow by Windows 10+nVidia drivers 355.60.

CompatibleID is quite interesting *PNP09FF

https://support.microsoft.com/en-us/kb/295296
http://forum.notebookreview.com/thr...een-now-shows-generic-pnp09ff-monitor.198498/

 

Thanks for posting. I added the M17xR4 to the list of affected models in post #2.

 

if you have any of the 17 inch models with...

- win 10
- 120hz display

sound off if you're also seeing LCD failures. i wonder if the EDP is preventing the EEPROM corruption?

 

ouch didnt know win10 can be this big of a problem to alienware. wonder how this happened how can LCD die and GPU 8 beeps with jsut a software upgrade, assuming downgrade back to win7 would solve the problem, anyone knows?

 

Nope, downgrading doesn't do squat. The EDID information in the LCD's EEPROM appears to be getting corrupted somehow. Probably a huge bug in the GeForce drivers, but Windows 10 seems to be making the damage really easy to inflict for some reason. The only solution is to buy another display or figure out how to reprogram the EEPROM. If you take the display off of the machine that has been messed up and put it on another machine that isn't messed up it will have exactly the same symptoms as the machine you took it of off until you put back the LCD panel that hasn't been screwed up.

 

thats pretty scary, i was just going to upgrade to windows 10 tonight and thought i'd check out see any driver difference especially on nvidia drivers locking overclocking capability and came across this. a software destroy hardware.. great MS.

 

Well, the good news is, if you want to be a guinea pig, AMD-powered systems appear to be exempt from this problem. I am not aware of even one Alienware with AMD GPUs that has this problem. For the first time in a very long time, having AMD GPUs instead of NVIDIA is a very good thing if you're planning to install the shiny new Windoze OS X spyware host.

 

we still need to see if displays via EDP are unaffected.

 

Haven't we already head from more than a few 17" Alienware owners with 120Hz eDP running Windows 10 without issues? Or, am I mistaken on that? (I'm actually asking this in a serious way, not a sarcastic way.) I agree with what you posted earlier about it appearing that eDP is not allowing whatever is happening to the EDID information to happen like it has been with LVDS.

 

yeah, there's only 1 person that stepped up.....1! that one might just be a fluke for all we know.

1 data point does not a conclusion make.

EDIT: and no it's been nearly 4 weeks and no sign of my cable arriving

 

That driver has an issue ? I have used them on stock setups for over 30 different laptop models, no reported issues. Course I also use the ones I modified myself and Eurocom's and no one else's.
What makes you believe there is an issue, and for which laptop and which bios and vbios, can you give us more information ?>

 

Just read the first two posts please, so I won't have to retype everything that has already been spelled out for all to see.

 

I think running Windows 10 on an Alienware notebook, especially one with SLI, is totally nuts if you don't have a warranty to pay for the damage that may result. Just because we haven't seen any examples of certain models developing display problems doesn't mean they won't. Until they figure out exactly what is causing it, tells us what they found, and fix it, I don't think can say with certainty that it is truly safe to run Windows 10 on an Alienware with any driver version, with stock or aftermarket NVIDIA GPUs.

I'm sticking with dual-boot Windows 7 and 8 until they find and fix the problem. If and when they do find the problem and fix it, there is still all of the other nonsense Windows 10 brings that still has to be dealt with. Since DX12 is still irrelevant, there's really no legitimate reason to feel compelled to install Windows 10 anyway. Overall, Windows 10 performance is worse than both 7 and 8 and if you tweak Windows 8 the right way the Windows 10 has nothing to offer except a reduction in functionality. I'm running it on my Clevo now and keeping an open mind about it, but honestly... there is really nothing impressive about it that I can identify. Nobody actually "needs" Windows 10 at this point.

 

I am that one but really shouldn't be considered as I am using an old driver and when I was using the 353.62 my screen exhibited very strange behavior so I removed it in the same day.

So maybe it affects the 120Hz on new drivers but with one working machine I am using everyday I ain't putting that theory to the test

 

So on win 10 + which driver?

Sent from my HTC One using Tapatalk

 

To put it mildly.

It has just happened to me.

You can now add 120Hz 3D monitors to the list.


AW17 3D 120Hz Panel
I7 4910 (Stock - No OC)
8GB GTX 880M (Stock - No OC)
32GB 1600Mhz Samsung Memory
512GB Samsung Evo 840 mSATA (Boot Drive) 2 x 1TB Samsung Evo 840 SSD's
Killer 1202 WiFi

NVIDIA DRIVER VERSION: 353.62

Laptop ran fine, actually had better benchmarks and lower GPU temps than windows 8, I turned it off 2 weeks ago, tried to start it tonight and got the dreaded windows 10 8 beeps

 

Try to reset BIOS/power drain, connect to HDMI and then turn it on. Or even disconnect LCD after power drain and then connect to HDMI and power it up.

 

Now it is safe to assume than there is a BIG problem on using Windows 10 + Nvidia driver.

 

353.38 hotfix

 

trying fix's now.

I don't hold much hope though

 

Complete power drain - No luck.
External monitor - A quick flash as if it want to connect or is beginning the process followed by a slight pause then 8 beeps

 

I'm going to replace the LCD next, I'll report back shortly

 

I've replaced the LCD and laptop booted first time.
HDD with win 10 is being overwritten now, back to windows 7 I suppose.
The faulty 120Hz panel is Samsung.

 

So the 120hz monitors just take longer then Huh?

 

Appears to be a time bomb. How long the fuse is would be anyone's guess.

Brother @andrewsi2012 - sorry to hear this. It's very disheartening.

At least we have a definitive answer to @thegh0sts question about eDP and 120Hz being safe. Answer: Nope.

 

Looks like we are all going to be getting new laptops lol.

 

Being able to enter OS with connected bricked (before or afterwards) may give opportunity to reflash and recover that LCD.

 

Who is going to give them? Last time I received a new laptop as a Class Action lawsuit member involving NVIDIA we got a nearly worthless disposable turd with a lower spec and retail value equal to about 50% of the value of the original machine, and about half the performance, as a court approved settlement. I'd rather pay to have it fixed than be molested again. The only winners in Class Actions are usually the attorneys.

 

Eww, maybe just a check this time huh?

 

GRRRRRRRRRRRRRRRRRRRRRRRRRRRRR


I've had a vent now so I'm OK,lolhaha.



Still felt like a kick in the guts, maybe because I was half expecting it to happen
I might able to write this off on tax, unfortunately most people here cannot - So I hate to say this to myself but I'm probably one of the few people who can absorb this without to much expense, so I don't mind being a guinea pig if it saves other alienhead's some heartache.

SO PLEASE ALL YOU ALIENHEADS OUT THERE - DROP WINDOWS 10 LIKE A BOMB, IF YOU DON'T IT MAY GO OFF, ANYTIME, UNEXPECTEDLY.


IT'S COMING FOR YOU TOO



It's a conspiracy I tell you, ISIL have infiltrated micro$haft and NGreedia and are targeting us Lol, hahaha

 

Updated post #2...

 

You forgot to update this

 

Just come back to Windows 7. It is better here

 

After I get my new screen then there isn't much choice. What drivers work best on windows 7 btw now that we are on the subject? I know Mr. Fox said they haven't had decent drivers since March but what was the driver number befor the started crippling the 780m and others?

 

Thanks! I just fixed it.

344.75 and 345.20 are the newest driver versions that function 100% correctly for me with GTX 780M SLI.

At this point I think that anyone attempting to run Windows 10 on a pre-2015 Alienware laptop needs to have their head examined. Or, maybe they have so much money to blow on experiments that end in failure that they just don't care, LOL.

 

One guy claims that he got good results with newer driver. He says that on every driver he tried he had either severe throttling on his 780M on AW17x R4 or there were no good result after overclocking. But then he tried:
1. This driver http://www.laptopvideo2go.com/drivers/win8x64/353.12/disclaimer
2. This vBIOS http://forum.techinferno.com/genera...-editions-modified-clocks-voltage-tweaks.html
3. Used EVGA PrecisionX 16: Core +180 = 1036, Memory +480 = 2980, Voltage 1.050v

 

I'll try that one and see what happens. I think that it will end poorly because it seems they added something in the drivers that caps GPU performance with system power draw around 325W and with SLI all you have to do it start running benchmarks at stock GPU clock speeds to hit 325W. If I disable SLI, any driver I use works fine, but even with an extreme overclock the system never hits 325W. It seems to me that 780M is the only Kepler GPU affected this way, so they probably screwed up something in the SLI profile for 780M and they're too busy trying to sort out Maxwell issues to be put off long enough to fix what they broke.

But, thank you for posting that. I was not aware of any single GPU 780M owners experiencing bad throttling like I do. I have been contacted by a couple of Clevo owners with 780M SLI that are having throttling issues like I have with all three Alienwares with 780M SLI.

 

My 880M SLI clock is too low for me to test it because im using 780M clocks

 

Consider that the AW bios is Legacy +UEFI; after 10 installs it has the capability to access to its NVRAM sectors. Of course, it shouldn't, but there's nothing physically holding it back ... where 8/8.1 may have played nice and respected Legacy boot, 10 may not play by the rules. One way to find out would be a pre-10 bios export and compare with a post-10 bios export (both on legacy). There shouldn't be a single bit of difference between these two.

One difference is that eDP uses a single pin for EDID (AUX CH), which serves a variety of other control purposes as well, whereas LVDS needs 3 or 4 pins. An eeprom has a write-protect, read and clock pin. If eDP uses a single pin for its control, then it has to be hooked indirectly to the eeprom via a control IC (which splits the single data channel into its composite parts). With LVDS the connection is direct, that's why it was possible to write the eeprom via the cable (on the overclockers.ua forum), bricked eDP might need direct pin access to the chip or de-soldering from the board first.

Did some checking and found a good image of the LTM184HL01 (PnP SDC4C48). Couldn't find its spec sheet (for free), but did find one for the LTN173KT03, which appears to use an identical pin configuration:

So the 184HL does have an eeprom, at least. Actually, come to think of it; if anyone has a defective panel and a soldering iron; unsolder it and send me the chip only. A lot cheaper, faster (airmail) and even easier to read/write to. The result would be conclusive:

1. It was corrupt; write back proper values and display might run again (if panel is otherwise ok).
2. It was fine; driver killed it, whichever driver was to blame. New edid won't revive it then.

Thanks. And no; nvidia checks if your panel is amongst the whitelist that the manufacturer has paid nvidia for. But there's no physical difference between non-gsync and gsync panel; they're only 'approved' ... for your safety, of course ... or was it $s?

If the display is still running, please try the 'autoreadedid' usb stick and post the .bin files:
http://www.filedropper.com/autoreadedid

Spoiler: instructions

Export the .7z and write the .img to a usb stick (min. 1GB) using USB Image Tool. You'll probably need to clear cmos first (to disable Secure Boot) and find some method to force booting from the usb drive. If it has successfully booted (and run both readers) then there'll be a 3-second beep and you can shutdown the system.

It pulls edid directly from the eeprom, not indirectly via registry, like MonInfo or other 'soft'-tool (hence it's OS-independent). If it is corrupt then those bins will proof that. Even if your display hasn't failed, it may be a good idea to run that thing anyway in order to get a proper backup of its values. Also because not every corrupted byte will cause problems; more panels may be afflicted, except not in a position where it causes mayhem (Daniel's panel was two byte-changes 'ok'-ish, and two not so ok).

Noticed that as well in RaSeven's and Rotary Heart's setup logs. They have a different panel than your LG, yet both default to the fall-back display install:

Spoiler: search SDC4C48 or SEC5448 in setupapi.setup.log

Code:

>>>>>>>>>>>>> search SDC4C48 or SEC5448 in setupapi.setup.log <<<<<<<<<<<<<<<<<

[Device Install Log]
     OS Version = 10.0.10240
     Service Pack = 0.0
     Suite = 0x0100
     ProductType = 1
[BeginLog]

[Boot Session: 2015/07/29 20:06:43.489]

>>>  [Setup Plug and Play Device Install]

RaSeven:        set: DISPLAY\SDC4C48\1&8713BCA&0&UID0 -> Configured and started [monitor.inf:*PNP09FF,PnPMonitor.Install] (ConfigFlags = 0x00000000).
Rotary Heart:    set: DISPLAY\SEC5448\1&8713BCA&0&UID0 -> Configured and started [monitor.inf:*PNP09FF,PnPMonitor.Install] (ConfigFlags = 0x00000000).

>>>>>>>>>>>>> search PNP09FF in monitor.inf <<<<<<<<<<<<<<<<<

; *PNP09FF is the compatible device ID for monitors with descriptors, but we treat it as a h/w device ID,
; since registry settings for PnP monitors are different from legacy non-PnP ones.
; This will get matched when an INF with the Monitor\<venID><prodID> hardware device ID for the PnP monitor isn't found by the PnP manager.
%PnPMonitor.DeviceDesc% = PnPMonitor.Install, *PNP09FF

[PnPMonitor.Install]
CopyFiles=MonitorClassFunctionDriver
DelReg=DCR
AddReg=PnPMonitor.AddReg, 1600, DPMS
AddPowerSetting=Monitor_Brightness, Monitor_Dim_Brightness

[PnPMonitor.Install.Services]
AddService = monitor, %SPSVCINST_ASSOCSERVICE%, Monitor_Service.Install   ; install monitor class function driver

[PnPMonitor.Install.WMI]
WMIInterface = {123c80d2-937f-4cfe-80f4-c40d596e48b7},,WMIGuidSecurity_Full     ; WmiMonitorBrightnessEvent_GUID
WMIInterface = {479b20b4-5559-46fe-be97-7d222154421f},,WMIGuidSecurity_LocalFull; WmiMonitorBrightnessMethods_GUID
WMIInterface = {d43412ac-67f9-4fbb-a081-1752a2c33e84},,WMIGuidSecurity_LocalFull; WmiMonitorBrightness_GUID
WMIInterface = {671a8285-4edb-4cae-99fe-69a15c48c0bc},,WMIGuidSecurity_LocalFull; WmiMonitorID_GUID
WMIInterface = {9831b7e6-09ac-491f-8d07-3c3d649d8240},,WMIGuidSecurity_LocalFull; WmiMonitorBasicDisplayParams_GUID
WMIInterface = {2E2D2463-B537-4da7-8EEE-51306F1F482F},,WMIGuidSecurity_LocalFull; WmiMonitorConnectionParams_GUID
WMIInterface = {a56dbcf9-c4f0-44a8-9c1b-bb3b3f774b4d},,WMIGuidSecurity_LocalFull; WmiMonitorAnalogVideoInputParams_GUID
WMIInterface = {51565945-498a-4a77-acc6-151becc805ca},,WMIGuidSecurity_LocalFull; WmiMonitorDigitalVideoInputParams_GUID
WMIInterface = {ea324793-51bb-486a-aa9d-0f5552353413},,WMIGuidSecurity_LocalFull; WmiMonitorColorCharacteristics_GUID
WMIInterface = {6dc76655-063c-4524-a862-b8410c26281b},,WMIGuidSecurity_LocalFull; WmiMonitorListedSupportedSourceModes_GUID
WMIInterface = {5341576e-75c4-4aeb-a82b-873cd3c6b384},,WMIGuidSecurity_LocalFull; WmiMonitorDescriptorMethods_GUID

[PnPMonitor.AddReg]
HKR,"MODES\1600,1200"

;-------------------------------------------------
; User visible strings
PnPMonitor.DeviceDesc = "Generic PnP Monitor"

Not sure if it matters; looks like a fairly common stock install. Would be interesting to compare to, for instance, an AUO panel's install log. Can check the ' setupapi.****.log' file in any Windows version (' C:\Windows\inf\' folder). Searched my panel's PnP id (SHP13FF) in the Windows 7's install log:

Spoiler: search SHP13FF in setupapi.****.log

Code:

     dvi: Searching for hardware ID(s):
     dvi:      monitor\shp13ff
     dvi: Searching for compatible ID(s):
     dvi:      *pnp09ff
     inf: Opened PNF: 'C:\Windows\System32\DriverStore\FileRepository\monitor.inf_amd64_neutral_ab477c4d805d044f\monitor.inf' ([strings.0409])
     dvi: Selected driver installs from section [PnPMonitor.Install] in 'c:\windows\system32\driverstore\filerepository\monitor.inf_amd64_neutral_ab477c4d805d044f\monitor.inf'.
     dvi: Class GUID of device changed to: {4d36e96e-e325-11ce-bfc1-08002be10318}.
     dvi: Set selected driver complete.
     ndv: Driver selected, now performing install...
     ndv: {Core Device Install} 16:09:46.997
     inf:      Opened PNF: 'C:\Windows\INF\monitor.inf' ([strings.0409])
     pol:      {Device installation policy check [DISPLAY\SHP13FF\4&2A00B1D&0&UID68092928]}
!!!  pol:           The device is explicitly restricted by the following policy settings:
!!!  pol:           [-] Restricted installation of devices not described by policy
!!!  pol:      {Device installation policy check [DISPLAY\SHP13FF\4&2A00B1D&0&UID68092928] exit(0xe0000248)}
!!!  ndv:      Installation of device is blocked by policy!
     ndv:      Device install status=0xe0000248
     ndv:      Performing device install final cleanup...
!    ndv:      Queueing up error report since device installation failed...
     ndv: {Core Device Install - exit(0xe0000248)} 16:09:47.075
     ump: Server install process exited with code 0xe0000248 16:09:47.106
<<<  Section end 2014/12/19 16:09:47.106
<<<  [Exit status: FAILURE(0xe0000248)]

Heh, so they tried to do the same with 7's SP1 install, but have automatic driver install disabled (policy setting), so it failed.

Where did it say "Samsung"; in the OS or on the panel's sticker? Can only find these four LGs for ~17.3"+120Hz, so it may have been misreporting values/capabilities.

 

@t456 - not sure if they would be of any value for examination/comparison purposes, but I have attached my logs from the Clevo for Windows 7 and Windows 10 to see if Windows 10 is doing things differently than Windows 7 as far as the display setup is concerned. I will try pulling the same logs files from the M18xR2 Windows 7 installation (no longer has Windows 10) and manually browse the Windows 10 drive still in the currently non-functional Alienware 18. I will post them later.

 

OK, here are the log files I pulled off the Windows 10 installation on the Alienware 18 that is still non-functional.