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

Would it be safe to first uninstall the GTX 560 driver from Device Manager, so that the windows 10 upgrade happens using the onboard intel gfx. Then after the Windows 10 upgrade install the GTX560 driver using gforce experience ? Would this be safer ?

 

When i had geforce experience installed i had problems with black screen time to time. After removing it, removing card from device manager and just letting Windows 10 update, install nvidia drivers by them i did not have any problems with that black screen so far. Not sure about the others but just saying how it works for me. Wont install geforce until they bring new drivers and its confirmed its ok.

Take in mind that i dont play any games and use intel graphic as primary one now for just web/work etc, no idea if nvidia works fine right now.

 

I'd just do the in-place upgrade without changing anything, see how the upgrade goes, and then check all your devices after the upgrade to find out their status & the drivers Win 10 has decided to use - then make changes as you see fit. If you've got an external drive, install Macrium Reflect (Free) & do a Win 7 image of your drive before upgrading.

 

In-place upgrade of Alienware M17x R3 (I think - it's my son's laptop) with an AMD 6970: no issues.

 

I made pcmark8 today. http://www.3dmark.com/pcm8/8159651

Yet again in the benchmark test this is what i get. Why it uses only 3GB of the graphic card while i got 16GB? I thought its only display on support assist program as you said, but why then pcmark used also only 3gb instead of 16?

Graphics Card
NVIDIA GeForce GTX 770M
Vendor
Dell Computer Corporation
# of cards
1
SLI / CrossFire
Off
Memory
3,072 MB

 

Okay, I updated back to win10. This time I'm using Dell/AW "RECOMMENDED", driver 353.54. I modded the NVDM setup file. Oddly, this driver did not have a Nv_dispi setup file, the one I normally would modd. I figure I have two years left on my warranty WTH. If the screen blows I can tell customer service I was using the driver they said to use. I am cheating a little, I'm using my external monitor-my internal one looks so small (I'm spoiled). Fingers crossed.

 

I got a new screen in today and forced the iGPU in BIOS. Booted into 10 just fine and I used DDU to uninstall the previous Nvidia driver (353.62). I rebooted and downloaded 352.84 then enabled the discreet GPUs - rebooted into Windows 10 no driver verification mode and installed those drivers. Rebooted and everything was fine. Enabled SLI, everything seemed OK and even played GW2 for a minute. Rebooted the laptop - 8 beeps.

@Mr. Fox - It may be specific to 353.62 with this problem and Windows 7. 8, 8.1, and 10 - but even earlier drivers for Windows 10 are bricking the LCD.

 

WHY would you load Windows 10 on a replacement screen?! Sorry you had to go through that. The engineers are working on resolving this; until then no windows 10.


Sent from my iPhone using Tapatalk

 

Because it was assumed to be specific to 353.62 - it is most definitely not so.

 

That was made rather clear. Oh man. I feel bad for you; hope you didn't have to pay out of pocket for this.


Sent from my iPhone using Tapatalk

 

(It's reporting you have 3GB of VRAM on your 770M, which is normal & expected - your graphics card does not have 16GB of VRAM).

 

What was made rather clear? Per Mr. Fox's updated (and rolling updates) second post:

"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."

Looks like it wasn't yet known, and I verified that it is indeed a problem because 352.84 is the earliest WHQL driver available for Windows 10.

 

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.

The underlined part means don't risk trying it LoL.

For anyone else-the only way to be safe is through avoiding windows 10 entirely.

 

@Arestavo , I feel sorry for your LCDs too but if I were in your shoos 2 hours before I would enable iGPU, format Windows 10 partition and recovered previous OS by Macrium Reflect or Acronis, and then I would have risked... trying to hotplug broken LCD for reflshing, not using Win10 again.

Lets hope Nvidia agrees to receive your 2 LCDs for testin purposes. there were 2 different drivers afterall.

 

Brother @Arestavo I am so sad this happened to you twice. Obviously, I know how horrible that feels.

Not we know Windows 10 with any NVIDIA driver is not safe for an M18xR1/R2/18... like playing Russian Roulette with your beast. I just feel sick for you, man. But, this is a valuable lesson and others can benefit from your tragedy.

I am updating the first page, again.

 

are we any closer? i don't think we are.

 

Can anyone who still has access to the Windows 10 drive, partition or, perhaps, an image of the installation make a (zipped) copy of all * .inf files in the ' C:\Windows\inf\' folder and drop/upload it somewhere? Shouldn't be more than a few mb's.

The plot thickens ... there's something strange going on with Samsung (or Dell), either of which is responsible for the properly encoding the ' Plug and Play and ACPI ID' in their product:

Now, Daniel1983's 18 had a Samsung LTM184HL01 with PNP/ACPI id "SDC4C48". Search this id (e.g., on Notebookcheck) and, supposedly, all these laptops contain the exact same panel:

• Dell Venue 11 Pro 7000
• Dell Inspiron 13 7347
• Alienware 13
• Dell Latitude E5550
• Alienware 15
• MSI GT80

The GT80 is perfectly alright, of course, but-t-t-t-t-t-t ............ a 10.8", 13.3", 15.6" and an 18.4" with the same panel ????!

We do the same for Mr. Fox's RGB-LED panel. The Samsung LTN184HT02-S01, or pnp ' SEC5448':

• Dell Studio XPS 16 (1640)
• Alienware M18x
• Alienware M18x R2

Come again? A 16.0" and an 18.4" ?

But what of the LG? It's an LP173WF1-TLB3, or 'LGD02DA'; and these are all 17.3", which is as expected ... though if there are different panels with the same id then (hopefully) one of those infs will show that.

Remember that the id is what the driver installers sails by to install the appropriate files and (registry) settings. If an identical id points to multiple devices then the matched result will the the topmost of the list (which is the oldest display, probably). Hence, one should also think that the owners of those other laptops suffer the same problems ... so let's search 'laptop XYZ+'windows 10'+'display'+'black':

• Alienware 13
• Alienware 15
• Alienware M18x
• Alienware M18x R2
• Dell Inspiron 13
• Dell Latitude E5550
• Dell Studio XPS 16
• Dell Venue 11 Pro
• MSI GT80

Hello !!!

 

I luckily enough had an image backup of my Windows 8.1 installation on 350.12 Drivers on a reserve driver prior to upgrading to windows 10 so decided to roll back to it after Windows 10 seemed to get buggy off cold boot

Examples being: Incorrect DPI on start (125%), Screen not coming on after POST, and on the last boot proir to rolling back stuff wasnt coming on right (antivirus, .net 4.0 not starting, alienfx not running etc).

Cant tell myself why the newer stuff isnt working so for now back on 8.1 with the last stable drivers I have (later drivers that I installed when I cold booted would lead to freezing and unfreezing every few seconds and previously corrupted the OS and forced me to clean install again). Dont know what it is with newer drivers thats breaking stuff while the system works perfectly fine under 350.12 C_C

 

do you get a black screen from a cold boot with no backlight?

 

Well, I am glad MicroSh@ft is giving me 12 months for me to upgrade... I will wait for all this to be fixed before upgrading. Thanks Guys for heads up, ill follow this thread from now on.

 

***ATTENTION***ATTENTION***ATTENTION***​

Alienware has asked me to post this request for information.

If you have an Alienware that has been affected by this 8 beep/no boot problem, even if you have already called them and have a ticket number, please send the following information to them ASAP. Even if you are out of warranty, please send the information for investigative purposes.

Email:

(this is a JPG - please do not re-post it in text format)

Email Subject Line: 8-Beep/No Boot Issue

Please provide:

• Your Contact Information
• Your Service Tag
• Your GPU info (whether stock or aftermarket)
• Your OS version at the time of failure
• Your driver version at the time of failure
• System BIOS version (if you know it)
• BIOS boot configuration at the time of failure (Legacy, UEFI with Legacy, UEFI, Secure Boot, etc. if you know how it was set up)

You may not receive a personal reply. For now they are looking to document the system configurations that are affected and identify any similarities. If you are still covered by warranty and have not requested a repair, you still need to do that independent of reporting these details to Mr. Hernandez.

This is the only information I have at this time.

I will update post #2 with this information as well.

 

Sent. Thank you for working with them @Mr. Fox

I'm glad we have someone extremely competent helping Nvidia and Dell out.

 

Very glad to see this kind progress. Hoping things continue like this.

 

Here: https://onedrive.live.com/redir?resid=CFCF7E45C98497E9!99122&authkey=!AA2BWogY2c-P71w&ithint=file,7z

 

If I am not affected by this 8 beep/no boot problem, do you need my .inf files?

 

I am happy to see any form of action is taken to tackle these issues, starting with info collecting.
Sent them my info and I go hope we can hear back from them

 

Never checked the backlight tbh. I would get the POST along with the windows loading screen but when it moved to the login screen the screen would go off and not come back on. Basically had to turn the machine off and on again to get it to boot. Most of the time the issues are when I'm cold booting where something doesnt go right and usually its down to the display drivers. Like I said 350.12 is the last trustworthy drivers I seem to be able to use as the later ones are regularly having issues with cold boots.

With the whole unknown about windows 10 atm I can wait a good while till these issues are fixed since I did the upgrade and wont have to worry about activation if I do a clean install in the future. Really the only thing I need for certain is 100% stable display drivers which seems to be non existant since April :/

 

Im running windows 10 and latest nvidia drivers from dell webpage, no issues so far. With latest nvidia drivers after a while I had no video on internal laptop screen but unit was POSTing and working fine with external display. LCD panel was not functional, every time i wanted to switch to internal screen using windows key+P my unit was shutting down. LCD started to work properly after clearing NVRAM.

 

All the thanks goes out to Fox for his continued work and support for Alienware machines for our community of enthusiast.

 

Today release new Win10 WHQL driver 355.60. : http://www.geforce.com/drivers/results/89127

 

" There are still so many Alienwares with working screens" - Nvidia.

 

I not tested,still use win7 and waiting for a miracle...

 

Did they really say that somewhere?

 

Nah, but I'm not surprised if somebody there thinks so.

 

on windows 10, i'm having terrible problems updating my 770m to 352 drivers, keeps saying hardware not compatible/driver install failed, any workaround at the moment?

(driver failed after i modify the nvdmi and nv dispi.\)

 

With Windows 8, 8.1, and 10 you have to boot into a type of safe mode that disables driver verification to install modified drivers.

But you are asking this on the very thread where so many people have posted about broken LCD screens on Windows 10 with these drivers and you still want to install those drivers on Windows 10 anyways? Really? It blows my mind away that you would still want to.

 

It blows my mind the amount of people wanting to beta test a OS for Microsoft at the chance of killing their machine. Windows 7 and 8 if you must is fine at this point and I highly suggest everyone NOT install this crap for a few months. Their is absolutely NOTHING windows 10 does that 7 or 8 if you must cant do.

 

Technically there is one thing - you can only do the 3DMark DX12 benchmark using Windows 10. But that really ins't important and 3DMark even states that it shouldn't be used to compare GPUs.

 

That's right... it's not a very meaningful benchmark at this point. There should be no sense of urgency to have DX12 support when almost nothing uses DX12, LOL.

Speaking of which... here is a comparison of single versus SLI 980M on my Panther: http://www.3dmark.com/compare/aot/63413/aot/63415

 

can people test if the new driver has fixed the LCD failure issue please

 

2nd dead screen. Computer was working perfectly for 24 hours, I rebooted and it was STILL fine.

I enabled secure boot and all went to hell, 8 beeps.perhaps I'm dealing with a different issue...

 

Nope, same issue. If you are trying to catch up with me, only one more left to kill to be tied.

I added some comments to this article... Windows 10 vs. 8.1 vs. 7 Performance: Microsoft's latest OS put to the test

No way, Jose. Windows 10 ain't going to be inflecting any of my Alienware systems again until we have evidence of what caused it and conclusive proof that it is fixed and Windows 10 is safe to install.
Why aren't you testing it? Don't like the idea of sacrificing your display to the Jolly Green Giant.

 

1) 1 and only lappy. i'd love to have another gaming lappy to test but i am cheap (clearly).
2) waiting for my display cable.

 

I sent an email to the editors @ Windowscentral regarding this issue. Added a link to this thread & the one on Geforce forums.
waiting for an update.

Good luck.

 

I wiped the drive clean, installed Win 8.1, completed all updates, installed the new driver, 8 beeps no post without HDMI cable. A driver will not fix this damage. Replacing the screen & staying away from Windows 10 is the ONLY fix until we hear otherwise.

 

Hello everyone . Has been on a 4 weeks holiday without data. LoL. Came precisely home and see this tread(like a horror story ) This was a long thread... Works Windows 10 on Aw17R1 without problems or is it still much trouble? I have not installed the free Win10 home edition yet. Which Windows 10 version do you all recommend? Should I buy another windows 10 version than the one I have that are free (home edition)?
Which Windows update patch number do I need to be allowed a download of Win 10? I do not want to download unnecessary Win update patches. Have a lousy internet speed. Some say that Nvidia drivers burnt out their display. What the hell is this? This applies also my 3D screen??? I see that Dell has a few Windows 10 drivers(Wifi network - Bt4.0 -Audio - Nvidia - Synaptics Touchpad), but not all drivers. Shall I use old Win 8.1 drivers for the other drivers that are missing?

 

Stay AWAY from windows 10.


Sent from my iPhone using Tapatalk

 

Stay away from Windows 10! Avoid it like the plague!

Make sure you hide these updates or uninstall them if you already have them installed by going to the control panel/programs and features/view installed updates and carefully scan with your eyes to see if any of them are installed:

Windows 7:

KB3035583
KB2952664
KB3021917
KB2505438
KB2670838


Windows 8:

KB3035583
KB2976978
KB3021917

 

Is Microsoft gone mad??? First Dell who slaughtered Aw using soldered hardware in ther high end gaming laptop models, then came Nvidia and destroyed oc for mobile graphics. Intel deliver only garbage laptop processors most intended for tablet / mini pc. Now put Microsoft nail in the coffin with a new trash os. Is all hardware and software manufacturers gone crazy now?

 

Make sure you read this thread carefully, you will NEVER upgrade after reading it:

http://forum.notebookreview.com/threads/why-i-dont-like-windows-10.779540/