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

Great to see you chime in..

Great to see you chime in - I can't comment on the LCD but I think the external monitor was a possibility if the BIOS was in a UEFI state? So no Windows 10 installed but prepped and you say an nvidia driver may have downloaded in the background? could you jog your memory maybe and try to remember? I was curious as to why mine is lasting quite some time.. difference between me and maybe a small chunk was the only drivers I installed since 10 was only on 8.1 and was Mr Foxes old nvidia drivers.

 

Had Winshite 10 all winshite updates but no drivers off web, reverted to 8.1 and installed Mr Fox's 344.75 - nearly 3 days in and still ok

 

Hello, and welcome to our community. Glad you're with us, but not glad about the reason that brought you here.

Interesting. I will have to stop using HWiNFO64 (which I have been using several years without issue) and see if it still happens.

Don't buy a screen. You need 5 posts and overnight processing to use the private messaging system. Don't buy a new screen because (a) it will become unusable, just like the one you have now; and, (b) I can fix the one you have now for much less. Either way, new or fixed, the problem is going to come back again until the underlying issue is resolved. Once you have 5 posts and your account goes through overnight processing, send me a PM and we can visit about fixing your LCD.

 

@Mr. Fox does your driver disable updates?

 

Well... jogging my memory at this point is not terribly likely, I'm afraid. *laughs* If I can get the system to boot I can check the driver version and update history as simplicity itself. Barring that, I can pull the system drive and look for traces of nVidia files downloaded the day of; I just am trying to avoid pulling apart the drive assembly until absolutely necessary (don't expect anything to go wrong, but then, I didn't expect anything to go wrong when I shut the system down, either XD ). ((And yes, I know its ridiculous to have torn the system down to the mainboard and stripped the heatsinks off the graphics cards and balk at loading a SSD into an external drive bay... ))

 

I could get mine to boot without the internal display attached just using a HDMI cable to my TV. The thing is it HAS to be using UEFI or UEFI with legacy rom enabled.
It will beep no matter what you do if the BIOS is set to Legacy.

BTW I got my AW17 to boot with a scummy 15.6" 1366x768 display. As long as its the correct connector on the back the AW system does not appear to be picky

Spoiler: screen

 

Yeah, I'm rather skeptical about HwINFO being the cuplrit, too, but since it was being bandied about I figured I'd better chime in. (It was high on my list of "things I know I changed right before stuff stopped working," but there's really no body of evidence implicating it in any similar issues I can find.)

I do appreciate the offer; I'll very likely take you up on that contact in a day or two when I'm permitted to do so.

 

Haha bloody legend, maybe I can fit a 4k in mine when it goes.. little bit of glossy plastic and happy days

 

Good to know; I'll have to see if I can flip the boot settings when I get home. (Got the system used and as I recall the blasted BIOS was locked; finally just shuffled the drives around to get it to work and called it a day.) I do rather like the FrankenMonitor look, if only it were actually A) an "upgrade" and B) not required by the present circumstances.

 

No HWinfo installed on mine - just chiming in as mine is still ok. And I also admire your sense of humor on the last post given the circumstances. I hope the dots are joined and a resolution is found.. so many laptops wasting away for now :/

 

Heh, it's been two weeks at this point, might as well laugh a little. Running FFXIV on a media center PC and having to get all my actual work done on a Win 10 laptop - if I didn't laugh, I'd probably break something. XD

 

No HWinfo installed on mine - just chiming in as mine is still ok. And I also admire your sense of humour on the last post given the circumstances.

It's the best way of thinking to have..and my days I don't want to ever see Cortana pop up in near sight, the only thing she assists is LCD suicide. On a positive though, the LCD can be flashed and something installed this horrible program so surely it can be removed. I think it's a matter of time than possibility.

 

To think people complain about 'thick bezels' . Lovely solution .

Thought about two potential workarounds before;

1. Hook-up eeprom with edid to the LVDS's edid wires.
2. Clip edid wires completely.

For option #2:

Spoiler: LVDS cable, disconnecting all edid pins

That is based on the following theory; not all panels have an edid and ' no signal = good signal'. If it works then you could boot happily with a working display, even. Then reconnect the wires and flash the edid right after. No need for a second panel to hot-swap, then.

 

Pulled this from my Alienware 17's GTX 860m Kepler... I have installed windows 10 and used it for nearly 2 months but reverted back to 8.1 last week after reading. Currently using 355.82 and I haven't had any issues, so far. *fingers crossed*

GTX 860m Kepler ROM - The version matched the one requested in your post, @t456, so I linked it.

 

the 5th was cut last time wasn't it and it still bricked the EDID? have you cut all four and looked if it still come on?

 

Weyy what a legend, didn't think that would come across any time soon

 

I want to know how to prevent/fix this as much as anyone. I'll look for any opportunity to assist in any way I can. =P

 

No. For Windows, you do that with a registry hack or Group Policy. (Turning it off in Windows Update doesn't stick.) For the display drivers, you turn that off in NVIDIA Control Panel.

 

Just bringing it up, one the cause is found, instead of multiple cases, you collect names, contact info, damaged property, length of time without the use of your hardware, etc. It's better, if common cause, to handle it in one go...

 

Thanks Mr Fox, how's your setup going without those 780's? Just a thought is it worth doing what T456 is doing but comparing my 780 vbios with yours if this test falls through?

 

Isn't the end result found but cause still being discovered? And yeah makes sence, if mine dies I need to add myself to that sad list

 

Unfortunately it is identical to my one. We need one from someone who has never installed win10 on the system it has been used with.

 

I thought that might be the case, figured I'd give it a shot.

 

I am going to be running it on Intel HD Graphics another day or two to see if an EDID corruption occurs with the 780M cards sitting on a shelf. If it does not, I will snip the other three black wires before I install the 780M SLI again.

I have not tried booting from a television through HDMI. I did try external monitors and HDMI input on the M18xR1 and Alienware 18 and that did not work. I remember @Daniel1983 was able to boot using his TV set and so has @syphear so I am wondering if something different about the TV is allowing it to work. That might be worth investigating as well. If it will boot from a TV with a corrupted LCD, then it can be flashed that way.

I also got my spare motherboard fixed thank to @Khenglish and will be testing that as a fix (never touched by Windows 10). Might be another week or so because I will be traveling on business next week and will have no opportunity to do any of this stuff.

 

2 months on Windows 10.. Pretty stable given other users experiences. Someone told me some guy lasted a month, but it seems most people have it happen pretty quick within hours of nvidia drivers

 

I was using the first driver released with it too, I think 353.62. Never went up to 355 until I reinstalled 8.1 and went ahead and gave it shot since it was a clean install.

Sent from my SM-N900P using Tapatalk

 

You're braver than me, after stumbling upon this thread and problem I get nervous installing Photoshop.. Never mind different versions of nvidia given it comes up a lot in the equation lol

 

Without the cause of the effect, you have no proof of defendants' attachment to the effect. You can know it has something to do with them, but can you reach the standard of proof?

Edit: BTW, found this site with some interesting suggestions to disable some of M$ telemetry!
http://superuser.com/questions/9725...ering-telemetry-data-from-windows-7-8-and-8-1

 

I read up on it but I figured if its gonna break, its gonna break. Judging by how its randomly happening with others. I increased my warranty for a year and threw caution to the wind. I'm not waiting for if, I'm waiting for when. So far, its been okay. I do get nervous anytime I reboot it.

Sent from my SM-N900P using Tapatalk

 

Sorry for noob question: How do i eaxtract vbios from my 860m so i can upload it here?

 

I used GPU-Z

 

Yes, GPU-Z is the easiest way.

I dumped the vBIOS from both of my 780M cards in the M18xR2 and they both have a checksum that matches the ROM that I have been using for a long, long time.

I forgot how much Intel HD Graphics sucks. I miss my GPUs already. But, there is one feature that's redeeming about the crappy integrated graphics. Not many 18" monsters can claim 6+ hours. Big laptops have room for big batteries, LOL. Of course all of the lights are off and the screen is dimmed, but that's more hours than I typically sleep on any given day.

Edit: Grrr... Linux changed my clock again. I need to apply that registry tweak to fix that issue.

 

1. Here is my vbios from 860m I hope it helps ( File attached at bottom of post).I am using stock 344.75 drivers



2. Regarding Moninfo as I wrote before it is possible to get a live EDID of your monitor as you can see from the screenshot below.It is the first option titled Real Time. If you can not get the Real TIme option then maybe this is a bad sign already.



3. Also another thought I had regarding bad EDID. Maybe people with bad EDID can check ePSA and see what error they get if they can access the diagnostics. If a screen is about to die you should be able to access ePSA and at least get an error code as mentioned here:

http://www.dell.com/support/article/us/en/19/266787

4. Also I found a Microsoft document describing how someone can fix a broken EDID by using an *.inf file.

http://www.google.gr/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&uact=8&ved=0CDIQFjACahUKEwiLtoOCt5HIAhVBORoKHTJlBlU&url=http://download.microsoft.com/download/a/d/f/adf1347d-08dc-41a4-9084-623b1194d4b2/edid_over.docx&usg=AFQjCNHpEbOryFifKXcQdDvuXqdI0CxvEw&sig2=HUajQ97VA7FfFvTJYRajSA&bvm=bv.103627116,d.d2s

 

So this is from your computer that has had anything but win10 installed? The rom is identical to the one @Narkoleptik posted up and my one.

Mmmm interesting, I have never had that bit come up on any of my computers before.
My trusty little XPS I am using now has never seen win10 and it's display is completely fine yet I don't have that Real-Time part . I'm not going to take this as a bad sign.

 

So our VBIOS' are not corrupt? Interesting...

 

I guess not if the .rom @_Alex provided was from a system that has never had any contact with win_x

 

My laptop had Win10 installed from upgrade that never got activated (if it makes any difference). I posted my vBios because i am not getting any of the bad EDID indications so i thought maybe it would help.
Sorry for any confusion. I thought it was clear because i had written in about my case a few pages back. ALl the details about my process can be found a few pages back

 

Just for the record, my M18x R1 does not boot even with a tv connected Via HDMI. Has only been alive for the 4 hours after I replaced the screen about a month ago :/

 

All good, there is quite a few pages to this thread now and its hard to remember who has done what and in what order. My second AW17 was also running win_x for about a week without corrupting a panel and I had the latest nvidia drivers installed at the time. The only thing I can say for sure I did different was to never run in discrete GPU mode only. I used a gtx 860m and 880m and both were ok.

Do you know what your BIOS was set to boot? Legacy or UEFI?

 

I was running legacy both times.

 

@syphear M18xR1 can't have full UEFI. It's EFI is forced to work as full legacy mode. But remember that this is still EFI forced to work as bios, not a pure bios system.

 

Yea the only thing you can do, to get your machine to post would be to put another display on it like I did

Spoiler: screen

Quickly get into the BIOS (do not let windows start) then change the boot option to UEFI or UEFI+Legacy and save. Then you should be able to use a TV or a Monitor.

Well whatever it is, as long as its not Legacy by itself it should boot.

 

Unfortunately until the cause gets figured out, I can't fix it because even when I did a fresh install of Windows 7 it still bricked after only 4 hours.

Btw, I'm still interested in the HWiNFO theory. Seems like a couple of us were running it. If it's killed displays before, then that could be what's doing it now. I had installed it before my display bricked both times.

 

No don't replace the display, just use another one to bypass the 8 beeps and get into your BIOS so you can change the boot mode.
Then remove the good display (having never booted further than the BIOS thus leaving it intact) from the system and put it back into whatever you stole it out of.
You then should be able to boot your computer with or without the integrated display connected and see what is going on using the HDMI output to a TV or Monitor.

 

I would just rather wait for a fix then take apart my computer every couple days lol. That is way too much work to be practical for day to day use but I definitely appreciate the suggestion. Always an option if I need it I suppose.

 

Each to their own, this is how I roll.

Spoiler: The rig

 

That's one aerodynamic frame

Also, has somebody @Mr. Fox or @t456 got a list of the laptops with a died LCD stating what was done and software put on? I was just thinking when somebody thinks of something like HwInfo being a possibility it would be great to reference back to a list to see if another died without HWInfo.. and if not HWinfo maybe we will pick up some other similarity on the way.

 

I believe the only things Mr. Fox has catalogued are effected models/displays. Those are on the first page.

 

Yes, they are generalized to OS and Drivers but people probably wouldn't have thought to pick up os software installed as well so at the moment other than 1 or 2 mentioned that's all we have to go on for it. I'm going to shut down and restart my laptop after this and see if the EDID in EDID Manager still reads ok.

 

Anyone have their laptop brick without installing HWiNFO?