Windows 10 + GeForce Drivers are Killing Samsung and LG Notebook LCD Display Panels
  1 / 33    
As the thread title suggests, I installed my "free" Windows 10 Upgrade on my Alienware M18xR2 and Alienware 18. Both have Samsung displays. Both machines have GTX 780M SLI. The M18xR2 was the first to die. Windows 10 installed without any issues. I used the drivers mentioned in the thread subject line, downloaded from NVIDIA. Everything seemed fine for about 24 hours. Without any kind advance of visible warning signs, the machine failed to POST with 8 beeps. GPUs, LVDS cable tested fine. This left only the motherboard or the LCD as being the problem. I have an M18xR1 with the identical display panel. I moved it to the M18xR2 and everything worked. Installing the Samsung panel from the M18xR2 on the M18xR1 induces the same problem. I immediately dismissed this as being an ordinary hardware failure. Nothing lasts forever, right? I wish... Within 24 hours the Samsung LCD panel that I moved to the M18xR2 has failed with exactly the same problem. So, it seems to not be an ordinary hardware failure after all. The Samsung display panel either failed or was damaged as a direct result of upgrading to Windows 10 and/or using the 353.62 display drivers for Windows 10. But, the problem doesn't end here, unfortunately. I had Windows 10 on the Alienware 18 running on Intel HD Graphics. This machines also has a Samsung display. Everything seemed fine for about 16 hours, so I switched over to GTX 780M SLI and downloaded 353.62 drivers for Windows 10. They installed effortlessly. In less than two hours this machine made a click and shut itself off. It now fails to POST with 8 beeps, exactly the same as the M18xR2. So, I have three super-expensive laptops with costly 18.4" Samsung display panels that are dead. They are out of warranty, but even if they were still under warranty, this is not a warrantable repair and not something Dell/Alienware is responsible for. I have alerted Alienware to the issue in the interest of customer service and raising awareness. Other than that, I don't know what to do next. I don't have the money to buy three displays, so this will likely be a long and expensive project to try to recover from. I was going to install Windows 10 on my Eurocom Panther (Clevo P570WM) but now I am terrified of breaking the only working laptop that I have left to use. [b]****UPDATED 8/9/2015****[/b] Affected models identified: [LIST] [*]Alienware 17 [*]Alienware 18 [*]Alienware M18xR1 [*]Alienware M18xR2 [/LIST] As of 8/9/2015 all reported LCD failures involve: [LIST] [*]Windows 10 Operating System [*]NVIDIA GPUs (780M, 880M and 980M) [*]60Hz LVDS Samsung and LG Displays [/LIST] It appears systems running UEFI without Legacy/CSM support may be able to boot from HDMI or mini-DP even when they experience 8-beeps and fail to POST using the native display. It appears the limited number of Alienware 17" single GPU laptops with 120Hz eDP 3D-capable display may be exempt from issues. No reports of LCD failures with this configuration as of 8/9/2015. It appears that using drivers older than 353.62 may help avoid this problem, but there is not enough information to suggest that doing so is actually safe. Some with affected models are using older drivers, including my 345.20 desktop driver mod, under Windows 10 and have not experienced this issue... yet. [b]****UPDATED 8/12/2015****[/b] [img]http://i.imgur.com/dHdd5iT.jpg[/img]
As the thread title suggests, I installed my "free" Windows 10 Upgrade on my Alienware M18xR2 and Alienware 18. Both have Samsung displays. Both machines have GTX 780M SLI.

The M18xR2 was the first to die. Windows 10 installed without any issues. I used the drivers mentioned in the thread subject line, downloaded from NVIDIA. Everything seemed fine for about 24 hours. Without any kind advance of visible warning signs, the machine failed to POST with 8 beeps. GPUs, LVDS cable tested fine. This left only the motherboard or the LCD as being the problem. I have an M18xR1 with the identical display panel. I moved it to the M18xR2 and everything worked. Installing the Samsung panel from the M18xR2 on the M18xR1 induces the same problem. I immediately dismissed this as being an ordinary hardware failure. Nothing lasts forever, right? I wish... Within 24 hours the Samsung LCD panel that I moved to the M18xR2 has failed with exactly the same problem. So, it seems to not be an ordinary hardware failure after all. The Samsung display panel either failed or was damaged as a direct result of upgrading to Windows 10 and/or using the 353.62 display drivers for Windows 10.

But, the problem doesn't end here, unfortunately. I had Windows 10 on the Alienware 18 running on Intel HD Graphics. This machines also has a Samsung display. Everything seemed fine for about 16 hours, so I switched over to GTX 780M SLI and downloaded 353.62 drivers for Windows 10. They installed effortlessly. In less than two hours this machine made a click and shut itself off. It now fails to POST with 8 beeps, exactly the same as the M18xR2.

So, I have three super-expensive laptops with costly 18.4" Samsung display panels that are dead. They are out of warranty, but even if they were still under warranty, this is not a warrantable repair and not something Dell/Alienware is responsible for.

I have alerted Alienware to the issue in the interest of customer service and raising awareness. Other than that, I don't know what to do next. I don't have the money to buy three displays, so this will likely be a long and expensive project to try to recover from. I was going to install Windows 10 on my Eurocom Panther (Clevo P570WM) but now I am terrified of breaking the only working laptop that I have left to use.

****UPDATED 8/9/2015****

Affected models identified:
  • Alienware 17
  • Alienware 18
  • Alienware M18xR1
  • Alienware M18xR2

As of 8/9/2015 all reported LCD failures involve:
  • Windows 10 Operating System
  • NVIDIA GPUs (780M, 880M and 980M)
  • 60Hz LVDS Samsung and LG Displays

It appears systems running UEFI without Legacy/CSM support may be able to boot from HDMI or mini-DP even when they experience 8-beeps and fail to POST using the native display.

It appears the limited number of Alienware 17" single GPU laptops with 120Hz eDP 3D-capable display may be exempt from issues. No reports of LCD failures with this configuration as of 8/9/2015.

It appears that using drivers older than 353.62 may help avoid this problem, but there is not enough information to suggest that doing so is actually safe. Some with affected models are using older drivers, including my 345.20 desktop driver mod, under Windows 10 and have not experienced this issue... yet.

****UPDATED 8/12/2015****
Image

HIDevolution EVOC P870DM3 | 7700K | GTX 1080 SLI | 1440p 120Hz | 64GB DDR4-3333 | 780W AC Adapter
EUROCOM Tornado F5 | 7700K | GTX 1080 | 1080p 120Hz |32GB DDR4-3000 | 330W AC Adapter

#1
Posted 08/03/2015 06:45 PM   
The response to this from nVidia will be interesting to hear. It's clearly not a Windows 10 issue alone due to the fact that the intel GPU did nothing to harm the screens.
The response to this from nVidia will be interesting to hear. It's clearly not a Windows 10 issue alone due to the fact that the intel GPU did nothing to harm the screens.

Clevo P370SM3:
i7-4800MQ | 16GB DDR3L 1600MHz | GTX 780M SLI | 128GB Plextor M6M SSD | Samsung PM841 512GB SSD | 1TB 7200RPM HGST HDD | Intel 7260ac | 120Hz Matte screen

#2
Posted 08/03/2015 07:18 PM   
if that's the case then it must be the nvidia driver and we need to test older drivers to confirm that IT IS the 353.62 drivers.
if that's the case then it must be the nvidia driver and we need to test older drivers to confirm that IT IS the 353.62 drivers.

Metabox Prime-X P870DM-G (w/ Prema BIOS): Intel Core i7 6700K 4.0GHz (OC @ 4.4GHz -60mv) | G.Skill Ripjaws 64GB (4 x 16GB) DDR4 2400MHz RAM | 2 x Samsung 950 Pro 512GB M.2 SSD | 2 x Samsung 850 Pro 512GB 2.5" SSD | NVIDIA GTX 1070 Notebook 8GB (+130MHz core OC) | 17.3" IPS G-Sync WLED (1080p75) G-Sync disabled :( | Windows 10 Pro x64 CU | 330W PSU

#3
Posted 08/03/2015 07:41 PM   
That would require a brave soul with spare parts to sacrifice to the Jolly Green Giant. It does seem that those who have used older drivers for Windows 10 may have not been affected. I know one M18xR2 owner with GTX 780M is using my old 345.20 driver mod for Windows 10 and having no problems. It may be a failure induced by this particular driver.
That would require a brave soul with spare parts to sacrifice to the Jolly Green Giant. It does seem that those who have used older drivers for Windows 10 may have not been affected. I know one M18xR2 owner with GTX 780M is using my old 345.20 driver mod for Windows 10 and having no problems. It may be a failure induced by this particular driver.

HIDevolution EVOC P870DM3 | 7700K | GTX 1080 SLI | 1440p 120Hz | 64GB DDR4-3333 | 780W AC Adapter
EUROCOM Tornado F5 | 7700K | GTX 1080 | 1080p 120Hz |32GB DDR4-3000 | 330W AC Adapter

#4
Posted 08/03/2015 08:36 PM   
as mentnioned over at NBR it might be possibly panel specific. so far all the panels that i know of that have failed have been samsung 60hz panels. I have yet to hear any laptops with AUO 60hz panels failing yet nor any 120hz panels. but the simple fact of the matter is that if it is affecting only a certain brand of panels we shouldn't have to cherry pick them just to work.
as mentnioned over at NBR it might be possibly panel specific. so far all the panels that i know of that have failed have been samsung 60hz panels. I have yet to hear any laptops with AUO 60hz panels failing yet nor any 120hz panels.

but the simple fact of the matter is that if it is affecting only a certain brand of panels we shouldn't have to cherry pick them just to work.

Metabox Prime-X P870DM-G (w/ Prema BIOS): Intel Core i7 6700K 4.0GHz (OC @ 4.4GHz -60mv) | G.Skill Ripjaws 64GB (4 x 16GB) DDR4 2400MHz RAM | 2 x Samsung 950 Pro 512GB M.2 SSD | 2 x Samsung 850 Pro 512GB 2.5" SSD | NVIDIA GTX 1070 Notebook 8GB (+130MHz core OC) | 17.3" IPS G-Sync WLED (1080p75) G-Sync disabled :( | Windows 10 Pro x64 CU | 330W PSU

#5
Posted 08/03/2015 09:11 PM   
And, finding out by random accident the way I did, that my panels are going to be executed by Windows 10 or this driver, is definitely not a good thing. I would not wish this sort of tragedy on anyone. At least three different people, three separate laptop models identified have this issue. But, I wonder how many people are having this issue that we don't even know about that have no clue what is happening to their laptop? Even I assumed the first one was a random hardware failure. I only know otherwise because of it happening to three of my displays. That cannot be a coincidence.
And, finding out by random accident the way I did, that my panels are going to be executed by Windows 10 or this driver, is definitely not a good thing. I would not wish this sort of tragedy on anyone.

At least three different people, three separate laptop models identified have this issue. But, I wonder how many people are having this issue that we don't even know about that have no clue what is happening to their laptop?

Even I assumed the first one was a random hardware failure. I only know otherwise because of it happening to three of my displays. That cannot be a coincidence.

HIDevolution EVOC P870DM3 | 7700K | GTX 1080 SLI | 1440p 120Hz | 64GB DDR4-3333 | 780W AC Adapter
EUROCOM Tornado F5 | 7700K | GTX 1080 | 1080p 120Hz |32GB DDR4-3000 | 330W AC Adapter

#6
Posted 08/03/2015 09:41 PM   
The ONLY way I can think of that the card and drivers could be killing monitors would be if the card was overclocking their refresh rates and the monitors board is poorly designed and lets its self be damaged that way. I know for a fact that mine is not as I tried to do so manually and going even 1hz gives me invalid input on the monitor. Barring that, the only other way I can think of to damage one would be with improper voltage, but I would think firmware would handle that. Interesting case
The ONLY way I can think of that the card and drivers could be killing monitors would be if the card was overclocking their refresh rates and the monitors board is poorly designed and lets its self be damaged that way. I know for a fact that mine is not as I tried to do so manually and going even 1hz gives me invalid input on the monitor.

Barring that, the only other way I can think of to damage one would be with improper voltage, but I would think firmware would handle that.

Interesting case

#7
Posted 08/03/2015 10:57 PM   
Yeah, we don't really know why this has happened. Windows showed me native resolution and refresh rates... assuming the information display by Windows was accurately reported, but no way to find out now.
Yeah, we don't really know why this has happened. Windows showed me native resolution and refresh rates... assuming the information display by Windows was accurately reported, but no way to find out now.

HIDevolution EVOC P870DM3 | 7700K | GTX 1080 SLI | 1440p 120Hz | 64GB DDR4-3333 | 780W AC Adapter
EUROCOM Tornado F5 | 7700K | GTX 1080 | 1080p 120Hz |32GB DDR4-3000 | 330W AC Adapter

#8
Posted 08/03/2015 11:11 PM   
On Windows 10, I get hanging black screen and BSOD on Nvidia Geforce 560m, please fix asap! This is with both 353.62 and the driver right before it.
On Windows 10, I get hanging black screen and BSOD on Nvidia Geforce 560m, please fix asap! This is with both 353.62 and the driver right before it.

#9
Posted 08/04/2015 12:49 AM   
It's been 12 hours, nVidia. I'm waiting for a response to this.
It's been 12 hours, nVidia. I'm waiting for a response to this.

Clevo P370SM3:
i7-4800MQ | 16GB DDR3L 1600MHz | GTX 780M SLI | 128GB Plextor M6M SSD | Samsung PM841 512GB SSD | 1TB 7200RPM HGST HDD | Intel 7260ac | 120Hz Matte screen

#10
Posted 08/04/2015 07:03 AM   
What is taking you so long to respond? Most AW owners are unaware of the potential consequences of installing Win10 driver v353.62. Samsung LCD displays: Alienware 18 R1 , M18xR1, M18xR2, Alienware 17 R1 60Hz & 120Hz (Samsung & AUO), M17xR4 120Hz...
What is taking you so long to respond? Most AW owners are unaware of the potential consequences of installing Win10 driver v353.62.

Samsung LCD displays:
Alienware 18 R1 , M18xR1, M18xR2, Alienware 17 R1 60Hz & 120Hz (Samsung & AUO), M17xR4 120Hz...

#11
Posted 08/04/2015 11:51 AM   
What the hell?! I've just posted similar thread, havent seen his one. My tv hasnt crashed yet, but from what i see now i should disconnect 2nd monitor and uninsall 353 geforce experience as fast as possible
What the hell?!

I've just posted similar thread, havent seen his one. My tv hasnt crashed yet, but from what i see now i should disconnect 2nd monitor and uninsall 353 geforce experience as fast as possible

#12
Posted 08/04/2015 12:10 PM   
Sorry to hear about this. Looks like you are the second Alienware 17 owner we have identified with this type of problem. [quote="Sc12"]Hi guys, I've read a lot about win 10 and nvidia problems but looks like mine situation is kind of diffrent and i coouldnt find solution. I read about black screen problems after win 10 installation etc bit my problems occur some hours after work. I got dell alienware 17 geforce gtx 770m. I got also tv connected as extended screen. I did clean install with partition format after upgrade also. I installed latest mvidia drivers with geforce experience package. All windows updates are up to date to Everything works fine, no issues. I can watch movie and for 3 hours all is good but suddenly my screen goes black, only that cursor is visible and it looks like pc crash. I was able to go ctrl alt del once and logoff and login back and was fine but yesterday i couldnt do anything. I do all my work on pc and its impossible for me to work now as this crash might happen wvery moment. Whole installation process was fine. Can anyone help with it please? I read that there were problems with drivers and automatic updates after release but i got all updated to latast including 353.62 nvidia drivers Please help Sc12[/quote]
Sorry to hear about this. Looks like you are the second Alienware 17 owner we have identified with this type of problem.

Sc12 said:Hi guys,

I've read a lot about win 10 and nvidia problems but looks like mine situation is kind of diffrent and i coouldnt find solution. I read about black screen problems after win 10 installation etc bit my problems occur some hours after work.

I got dell alienware 17 geforce gtx 770m. I got also tv connected as extended screen. I did clean install with partition format after upgrade also. I installed latest mvidia drivers with geforce experience package. All windows updates are up to date to

Everything works fine, no issues. I can watch movie and for 3 hours all is good but suddenly my screen goes black, only that cursor is visible and it looks like pc crash. I was able to go ctrl alt del once and logoff and login back and was fine but yesterday i couldnt do anything. I do all my work on pc and its impossible for me to work now as this crash might happen wvery moment. Whole installation process was fine.

Can anyone help with it please? I read that there were problems with drivers and automatic updates after release but i got all updated to latast including 353.62 nvidia drivers

Please help
Sc12

HIDevolution EVOC P870DM3 | 7700K | GTX 1080 SLI | 1440p 120Hz | 64GB DDR4-3333 | 780W AC Adapter
EUROCOM Tornado F5 | 7700K | GTX 1080 | 1080p 120Hz |32GB DDR4-3000 | 330W AC Adapter

#13
Posted 08/04/2015 03:42 PM   
Nvidia's costumer support has gone down the drain, now you have this issue to add to the fact that 3DTV paying costumers cannot even activate their product because the activation servers haven't been working properly for months and nobody at Nvidia gives anyone any status updates on this issue. I wish AMD offered proper alternatives in mobile gaming :/
Nvidia's costumer support has gone down the drain, now you have this issue to add to the fact that 3DTV paying costumers cannot even activate their product because the activation servers haven't been working properly for months and nobody at Nvidia gives anyone any status updates on this issue.

I wish AMD offered proper alternatives in mobile gaming :/

Alienware 17 R3 GTX 980M (internal GPU)
RAM: 32GB
Storage: 4*512GB SSD

Display: Samsung UE55JU7500 (55 inches 4096x2160 capable display , 3840x2160 native resolution @ chroma 4:4:4 over HDMI 2.0)

Alienware Graphics Amplifier + GTX1080 connected to the above configuration (external GPU)

#14
Posted 08/04/2015 03:49 PM   
I have an Alienware 17 with a burnt out screen also like Mr. fox. Installed clean install windows 10 pro with latest nvidia drivers 353.62. Ran for 1 day and ended up with 8 beeps indicating lcd failure. I swapped the graphics car thinking maybe my gpu had failed but same 8 beeps indicating lcd failure with both cards. I now have to replace an lcd panel which is very expensive for these computers all thanks to nvidia's failure to make an acceptable driver. Nvidia needs to take responsibility for these gpus and either pay the damages or recall all these cards and give people their money back. At this rate it won't be long before a lawsuit like apple users have done with their MacBook display issues.
I have an Alienware 17 with a burnt out screen also like Mr. fox. Installed clean install windows 10 pro with latest nvidia drivers 353.62. Ran for 1 day and ended up with 8 beeps indicating lcd failure. I swapped the graphics car thinking maybe my gpu had failed but same 8 beeps indicating lcd failure with both cards. I now have to replace an lcd panel which is very expensive for these computers all thanks to nvidia's failure to make an acceptable driver. Nvidia needs to take responsibility for these gpus and either pay the damages or recall all these cards and give people their money back. At this rate it won't be long before a lawsuit like apple users have done with their MacBook display issues.

#15
Posted 08/04/2015 04:29 PM   
  1 / 33    
Scroll To Top