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

On day 2 of my lg panel replacement. If it wasn't pulled out of an alienware/dell is it possible it's immune? Want to disable optimus but don't have the balls for it yet since it died shortly after doing that last time.

 

Well, this just happened to me on my M18. So of course I come to my trusty notebookreview to see if I can get any advice and again ... no surprise, Mr. Fox is already on it!

As a guy that owns / has owned a bunch of Dells (XPS 9300, XPS 1210, XPS 11) & Alienwares (M11r2, m14 R1, m18r1, 14 and lastly 18) - I've been pretty lucky. I've only had to use the warranty service once on my latest AW18 (was SLI, one of the 780's kicked the bucket) but of course after I get it back and a few weeks after the warranty expires (ended August 9th) ... this happens.

I'm subbing to this thread and going back to my AW14 and my desktops until they figure what the heck is going on. No point in paying for parts / repairs until they fix the cause of the issue.

 

My panel is....
SAMSUNG LTN173HT02P01

 

Oh, man... sorry to hear it happened to you also. Windows 10? Do you know what version of GeForce driver was installed?

Please post in the GeForce Community thread (link near end of post #1) and send an email to Federico (see instructions in post #2) if you have not already done so.

Well, did you see the post below? I hope the P771ZM doesn't run into the same problem that @ajc9988 did with his P770ZM. Stay away from Windoze OS X trojan just to be safe. Did you order it with Windows 7 or 8? Be sure to use Group Policy to disable Automatic Windows [Malware] Updates in 7 or 8 to keep the cancerous telemetry updates from infecting your new machine.

 

so far my new panel is good. will see in a week if i want to convert the old panel into a secondary display or just donate it.

 

Struth that is a nightmare if it is the case.

 

that means a new BIOS for sure if they want to fix this BS!

 

So I have a question...

Have we seen a single instance of an eDP panel dying to these drivers? Because I had to upgrade to 355.60 recently (a couple days ago) due to some features with SLI and such simply not working on some recent games even if I force it on 353.06 which I have been on since it came out and I determined it was stable for me. I know most of the dead panels are LVDS but I do not have the $1100 TTD required to ship my laptop up to Mythlogic for a dead screen should anything happen, and the dead P770ZM is honestly scaring me.

 

That's crazy, it couldn't have died due to excessive heat unless you were playing 24/7 at 100+ degrees Celsius. Then again, I've heard of people running their laptops at 120 degrees Celsius with no adverse effects. That being said, I feel you, the 2014 and 2015 AW lineups are a joke compared to the previous model.

 

@thegh0sts , wouldn't that be an extreme solution cause the BIOS needs to be specifically done for each laptops affected. AW is not the only brand affected, Clevo just joined the ranks as well as some desktop users too. If what @GodlikeRU said is true, an NVIDIA driver would help a lot. @D2 Ultima , do a windows 8.1 clean install and stay away from windows 10. I am guessing you are experiencing memory leaks while running SLi, NVIDIA just released a new driver which addresses that.

 

i wonder if anyone has used the latest drivers on 8.1 and it have it break on them?

 

I am using Win 8.1 as it says in my signature. I also said I went straight from 353.06 to 355.60. It's just getting to an annoying part where staying on older drivers is hampering my ability to game. If I had 980Ms and I could simply force single GPU to great enough effect, that'd be fine, but for SLI I appear to be at the mercy of drivers.

The reason I asked is because Win 8.1 users for AW have had their screens break.

 

that's what i want to know if the newer drivers are breaking in 8.1 or 7.

 

http://forum.notebookreview.com/thr...nware-lcd-panels.779449/page-88#post-10073451
Thank you very much for this, @t456. I can confirm that correct eeprom (LGD02DA in my case) brings the screen back to full working order - screen replacement is not required. I was able to use the legacy again and install all VGA drivers. Below are the 2 screenshots done before LCD firmware flashing and after the flashing. You need to use external hardware for screen eeprom flashing though, I could not find any software, which would be able to write a new eeprom.

After confirming the screen works fine again (loaded into W10 safe mode and wiped nvidia drivers), I wiped the SSD and installed Windows 8.1 Update 1, had Windows updates completely turned off. Then I switched from Optimus to dedicated and installed the supposedly fixed nvidia driver 355.83 - it was a big mistake. My screen is bricked again, nvidia did not fix their broken drivers!

@Mr. Fox, could you add t456 post with the correct edids attached to the first or second page please?


I will attach the eeprom extracted from the broken display later.

 

Man that's some hard work

 

That's fantastic news, man !!! Great job ! Dying to see that edid you extracted.

Have some tools, but they're all Linux-based and need non-UEFI boot. Think UEFI's possible, but that still won't help on the older, non-HDMI-booting systems. Hardware-flash is the only option for these.

Might be, the spec. sheets shows some were custom-ordered for Dell. Can you copy/paste MonInfo's 'Raw Data' section?

And you, as well? The other SEC5044 was LTN173HT02- T01, would be good idea to compare the two. Difference may be trivial (as with the TLB3), but better to rule out significant changes.

 

Ok. If this is the real case, I'll simply guinea pig with 355.60 then. I confirmed I have brightness control and all that with this driver, so if my screen doesn't die out then it might mean eDP panels (or at least my Clevo) is safe. But this is REALLY something that needs fixing. It can't be the manufacturers' faults if the notebooks worked fine for years and all of a sudden nVidia's drivers corrupt EEPROMs. Obviously nVidia did something to their drivers and they haven't reverted it at all, and it isn't resultant of Windows 10 either as we just got confirmation of.

Edit: It's been 3 days on this driver (going by system uptime) already, mind you. I've also confirmed that overclocking works using Firestrike.

 

Can we please stop posts about GPU upgrade and Gaming Performance results? It begins over and over again. I wouldn't be so critical if it hadn't been happened multiple times already while topic's name clearly says what it is about. Does someone wants to spoil the thread or what?
Maybe it's selfish from my side but I am willing to see a Topic Update notification when there is something new about the topic related problem like new cases, new way to solve it, update from official sources or anything else like that.
I already struggle to follow concrete cases after someone updates it due to 10 posts per page only (I can't seem to find any way to increase it to 20) so browsing through multiple pages of offtopic posts clearly doesn't help it at all.

Sorry again but being silent for all these days didn't help.

 

Which probably proves again that Windows 10 does something with BIOS to allow Nvidia write something to EDID so even after reinstall it keeps breaking again and again.
It would be interesting to compare both scewed EDIDs to each other. If they are the same then it clearly will show that this scewing was made on purpose, not just an accident.

And this is why you better learn how to fix it yourself instead of buying new screens again and again.

 

Ok, here are the 2 EDIDs attached. The first one is from @t456 and the second is from my broken screen (pulled from the screen before flashing with the good EDID).

 

But haven't we seen someone who has been on Win 8.1 only and has had his EDID corrupted?

 

Monitor
Windows description...... Generic PnP Monitor
Manufacturer............. LG Display
Plug and Play ID......... LGD03FB
Serial number............ n/a
Manufacture date......... 2013, ISO week 0
Filter driver............ Monitor
-------------------------
EDID revision............ 1.4
Input signal type........ Digital
Color bit depth.......... 6 bits per primary color
Color encoding formats... RGB 4:4:4
Screen size.............. 380 x 210 mm (17.1 in)
Power management......... Not supported
Extension blocs.......... None
-------------------------
DDC/CI................... n/a

Color characteristics
Default color space...... Non-sRGB
Display gamma............ 2.20
Red chromaticity......... Rx 0.640 - Ry 0.335
Green chromaticity....... Gx 0.320 - Gy 0.630
Blue chromaticity........ Bx 0.150 - By 0.060
White point (default).... Wx 0.313 - Wy 0.329
Additional descriptors... None

Timing characteristics
Range limits............. Not available
GTF standard............. Not supported
Additional descriptors... None
Preferred timing......... Yes
Native/preferred timing.. 1920x1080p at 60Hz (16:9)
Modeline............... "1920x1080" 139.000 1920 1968 2000 2080 1080 1083 1088 1113 -hsync -vsync
Detailed timing #1....... 1920x1080p at 40Hz (16:9)
Modeline............... "1920x1080" 92.670 1920 1968 2000 2080 1080 1083 1088 1113 -hsync -vsync

Standard timings supported

Report information
Date generated........... 8/29/2015
Software revision........ 2.90.0.1000
Data source.............. Registry
Operating system......... 6.1.7601.2.Service Pack 1

Raw data
00,FF,FF,FF,FF,FF,FF,00,30,E4,FB,03,00,00,00,00,00,17,01,04,90,26,15,78,02,F1,95,A3,55,52,A1,26,
0F,50,54,00,00,00,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,4C,36,80,A0,70,38,21,40,30,20,
35,00,7E,D7,10,00,00,19,33,24,80,A0,70,38,21,40,30,20,35,00,7E,D7,10,00,00,19,00,00,00,00,00,00,
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,02,00,0C,33,FF,0A,3C,96,32,23,51,96,00,00,00,00,B0

 

Timing is a bit off, but not so much it would harm the display. Main thing is that it's a CRT again (non-digital), same as with Daniel1983's panel (formerly an lcd, as well ):

Spoiler: spec. sheet edid vs. corrupted edid

Think it would be wise for anyone running 10+nvdia+lvds to export edid and copy/paste the raw data. Either here or just check it on the Web Based EDID Reader site. The thing to check for is ' Valid Checksum':



That should always be 'TRUE', if not; drop some Valium (and the edid here).

 

The second is true, at least. From nvidia's Features & Benefits:

So ... anti-ghosting then (not to be confused with AMD's OverDrive, which is for OC-ing). Nvidia's feature is, indeed, running panels at faster timing values. However, that's been around for a while ... the change may have been G-Sync; relatively recent and hooks into Overdrive functionality. Shouldn't matter for an LVDS panels, as G-Sync is eDP only, but they may have screwed up some of the changes.

Still ... even if this is so, that should not affect the edid ... unless:

Spoiler: LP173WF1-TLB3 - pin arrangement

Even that should not matter, except if the eeprom was improperly implemented. Chip manufacturers warn of this because of the possibility of erroneous write command due to voltage spikes; ' don't leave floating pins' and ' connect the write-protect pin as designed'. The result (increased electro-magnetic interference), would be similar to this report:

Spoiler: Friendly warning: 'Techno-babble' ^^

A.k.a.: crosstalk. So ... disable overdrive and see what happens?

That's a bit ... disheartening.

Compared the 355.60 and 355.83 drivers; no edid-related changes in any of the ini/inf/nvi files, the only major difference is in the nvlddmkm2.sys. This also contains Overdrive setting, but these haven't changed.

 

All of the examples of a machine affected by EDID corruption, except maybe one Alienware 18 and an M18xR1 which may have failed for some other totally unrelated reasons, first failed with Windows 10 installed. The repeat failures after LCD replacement occurred on machines that had Windows 10 installed before after having all Windows Updates applied and being Windows 10-ready. After crisis recovery flashing my BIOS, diskpart clean and then secure erase on the SSD before restoring my Windows 8.1 image my replacement display panel on the M18xR2 has not failed again. I am running my 345.20 desktop driver mod and have no plans to install any driver newer than that until the cause of the problem is clearly identified and corrected.

If that doesn't happen before too long I may just sell my the M18xR1, M18xR2 and all of their spare parts on eBay. Life is to short to have to put up with this kind of nonsense due to the incompetence and mistakes of NVIDIA and/or Micro$oft. If this situation is primarily NVIDIA's fault, which it may not be, one would think their engineers would be bright enough and intimate enough with their own product that they should know what they changed that might cause this and straightaway remove it from their drivers.

Very well could be something relating to GSYNC or DSR, since both screw around with timings and resolutions that are out of scope with the specs of our display panels. Looking at the timeline, it appears the enablement of both features on notebooks seems to coincide fairly close to the point in time when the EDID corruption began to surface.

 

I completely understand, and you are right about that.

I don't think it's Gsync or DSR. DSR's been in the drivers (even if not working) for a good long while, and it's been out (and used) for a decent while too without issues. I think it's just that all of this tech is coming out this year already in a cycle of bad drivers that's the problem. I also don't think DSR is an issue since we had the ability to use custom resolutions from before that, and DSR is turned off by default in the drivers (at least it is and always has been for me). I also find it funny that in all of this testing that nVidia is supposedly doing, some users here have got some visible progress, and toggle-able SLI is *STILL* not in the drivers (as of 355.60) without modding. But they're "working on it".

I stand by all my original statements: if this was affecting even a single desktop panel that people could prove, then we'd have had a new driver within days of blowing the issue open.

 

Very well said @Mr. Fox. How many AW18s have been identified so far?

 

DSR has been around longer than gsync when it comes to driver support and there were no issues detected but then win 10 was in "beta" for a short period.

Sent from my HTC One using Tapatalk

 

Just sharing my experience: M17x R4, upgraded yesterday from 680M to 980M. Windows 10-64; Unlocked A11 sBIOS; Disabled Optimus; drivers installed 352,84; Screen LGD02DA. For now no big issues, however I noticed this random behavior: after a standby or a shutdown sometimes the display will not "wake up"/turn on. So I see the Alienware logo and Windows booting circle and then when Windows takes over the drivers the screen would become black and I continue hearing the booting sounds. In case of wake up after standby - same thing, but obviously no booting screen. If I can share any data of any use, let me know, will try to do my best.

 

check your event viewer at the time of the black screen. for me it kept showing the nvidia driver crashing and recovering until i pressed the power button to do a hard shutdown.

 

@thegh0sts yep, you were right. "Display driver nvlddmkm stopped responding and has successfully recovered."

 

Questions: We know what is causing the displays to not work. How can we know for certain if it is Nvidia or Microsoft? From my observation it appears that Nvidia's drivers are doing this; but a fact is essential.

Think about how many people had to go through this who are unaware of the problem and not tech savvy enough to discern the root cause. How many have replaced their LCD's through no fault of their own??? I think a lawsuit is in order here, all affected should sue the responsible party for their negligence & be compensated for the damage caused. If not, they will just keep on getting away with what they do at other people's expense & frustration. This needs to go viral so everyone is aware. We need to take it seriously.


Sent from my iPhone using Tapatalk

 

we haven't heard of issues with the same drivers on 8.1 or 7 so it might be a certain requirements like win 10 + nvidia. but then win 10 + amd have no issues so that just makes me even more confused.

though unfortunately i have no idea what's causing the driver to crash. i have seen this on the win 10 previews and it drove me nuts and now i can't be sure if it happens on stock GPUs since i sold my stock GPU a few months ago.

 

The same thing happens with my AW17R1 120hz 3D screen + gtx780m (testing win 10 and 353.38). After a standby or a shutdown sometimes the display will not "wake up" / turn on. Quite annoying... What the hell is this? The official Windows 10 version is not really anything than a beta build. Have never experienced anything so freaking.
Edit: I've adjusted my powerbutton to do a normal shutdown so I don't have to force a "hard" shutdown.

 

no, it was not happening on my stock GPU. I used win 10 for 3 week before the upgrade.

 

No no, i mean i can't test if it only affected aftermarket GPUs on my system because i no longer have the stock GPU that the notebook came with. but since we know that the latest drivers are killing panels with stock GPUs i guess that doesn't really need to be answered.

if your screen doesn't have any backlighting turned on then that's the same problem i have with win 10. for maybe a day or less after installing it would be fine but then it would start to break and cause the blackscreens. There's no hardware damage as i can go back to 8.1 and it works fine, but it works fine with the intel GPU without the nvidia drivers installed. now that i have a 120hz panel the iGPU is not an option.

when it was running it was fine but with panels dying that's really put the icing on the cake for me not to even bother. stick with 8.1.

 

Hi, How did you fix the screen again? Are you able to flash it with the screen attached to the machine or what?Just info on this part would be a great help.. Last I heard the USB stcik with DOS and flash file wasn't working due to legacy causing 8 beeps.

Just go back to 8.1 and 353.00... No point risking your machine for Windows 10...

 

I have original 7 that came with my laptop, so at least using "alternative" versions of 8.1 (which I avoid for moral principle), I would revert to that. Yeah, you people here scared me a lot, but I'm sure that nobody comes here at least something bad happens, so hopefully statistically there are more working machines than not.

 

No, the screen had to be connected to a usb device, which was controlled from another PC. I could not find any software solution to flash the eeprom.

 

no one is scaring you here.

 

@Daniel1983 , sadly filing a lawsuit against either Microsoft or NVIDIA is but a futile option. Those giant tech companies have too much money and power to even be remotely affected by some random dudes and their lawsuits. Plus we don't have the necessary amount of backers for it to even be considered. Keep in mind that only "gaming laptops" are affected at the moment and this demographic is small by itself. This would have been totally different if we had desktop users on our side as well.
@Maksym Karpov , I experienced the same issue too during the first week of using windows 10 along with the newest driver at the time. Mine was a little different though as it only popped up when testing the 3dmark "API OVERHEAD TEST" while SLi was enabled. Worked fine with single gpu though.

 

Read this post's. Can we please stop posts about everything else...

 

Not much info on that id and the model string is blank (again). It's one of these 7 panels, so LP173WF1-TL**. One way to narrow it down is searching the PnP of all seven panels, ruling out the others. Manufacturing date 2013 would also discount four discontinued panels, but best method is to check the sticker on the back. Either way, edid is ok so far, but it is an LVDS and pretty close to the TLB3 ... don't count on it being immune. Added it to the list, so there's a backup, at least. Do think it's better to play safe, unless you can fix it in case of mishap.

dell panels, correct edids, v3

With 2x ok+corrupt edids we have something to compare:

For an explanation of the values, see VESA's E-EDID standard v1.4.

There's a bit more with the LG, but nothing that can't be explained by it being a much older edid version (two timings blocks are identical, which is nonsensical, so probably an early/quick revision). Now, it might seem that offset 14 is significant, but think it's just a coincidence; the 0 or 1 makes for a major difference here. Driving an lcd as an analog display's not a terribly good idea, so 8-beeps might even be a good thing (well, better than the alternative ...).

If ' random writes' is correct then you'd expect gradual changes to the edid. A bit here, a byte there, whatever. Nothing of great consequence; just a flickering image, banding, tearing. Perhaps a short black-out or missing lines from top or bottom, stuff like that. That is, until it hits something critical. Digital vs. analog would do, but also any change to the edid-start string (00 FF FF FF FF FF FF 00). Now ... the ' checksum check' (the last byte) is simply a feature that comes with the standard. It's there to check the integrity of the data, but there's no mandate to actually use it. Nor as what to do when it fails that check. So ... what if Dell designs their bioses to halt on ' edid checksum = fail', whereas other brands do not and POST regardless ?

Would be good to make a regular edid check of all 10+lvds+nvidia systems. If true and these continue running with invalid display parameters then the result would be even worse than with the Dell systems; damage permanent. Only it'd take more time to notice this since minor changes would not cripple the laptop ... yet.

Just a theory, mind, until someone finds a corrupt edid on a non-Dell.

 

I attached my edid info, hope it helps.

Also, I tried Edid web reader and got the following:

Header Information
Valid Checksum: FALSE
EDID Header: ERROR
EISA ID: 0BL
Product Code: 44A3
Serial Number: 80
Manufacture Date: 0/2006
EDID Version: 1.22


Number of Extensions: 0
Checksum: 0x0

Chromaticity Coordinates
Red X: 0.626
Red Y: 0.335
Green X: 0.553
Green Y: 0.316
Blue X: 0.352
Blue Y: 0.586
White X: 0.164
White Y: 0.127

Timing Bitmap
720×400 @ 70 Hz
720×400 @ 88 Hz
640×480 @ 60 Hz
640×480 @ 67 Hz
640×480 @ 72 Hz
640×480 @ 75 Hz
800×600 @ 56 Hz
800×600 @ 60 Hz
800×600 @ 72 Hz
800×600 @ 75 Hz
832×624 @ 75 Hz
1024×768i @ 87 Hz
1024×768 @ 60 Hz
1024×768 @ 72 Hz
1024×768 @ 75 Hz
1280×1024 @ 75 Hz
1152x870 @ 75 Hz

Standard Display Modes
X Resolution: 248
X:Y Pixel Ratio: 16:10
Vertical Frequency: 60

Detailed Timing Descriptor
Pixel Clock: 2.57MHz
Horizontal Active: 1281
Horizontal Blanking: 3841
Vertical Active: 3385
Vertical Blanking: 3200
Horizontal Sync Offset: 368
Horizontal Sync Pulse: 56
Vertical Sync Offset: 4
Vertical Sync Pulse: 0
Horizontal Display Size: 1072
Vertical Display Size: 32
Horizontal Border: 53
Vertical Border: 0
Interlaced: false
Stereo Mode: 3
Sync Type: 3

2-Way Line-Interleaved Stereo: false

Detailed Timing Descriptor
Pixel Clock: 43.11MHz
Horizontal Active: 256
Horizontal Blanking: 2816
Vertical Active: 0
Vertical Blanking: 0
Horizontal Sync Offset: 15
Horizontal Sync Pulse: 0
Vertical Sync Offset: 0
Vertical Sync Pulse: 0
Horizontal Display Size: 0
Vertical Display Size: 80
Horizontal Border: 0
Vertical Border: 0
Interlaced: false
Stereo Mode: 0
Sync Type: 0

2-Way Line-Interleaved Stereo: false

Detailed Timing Descriptor
Pixel Clock: 153.6MHz
Horizontal Active: 3990
Horizontal Blanking: 3600
Vertical Active: 0
Vertical Blanking: 0
Horizontal Sync Offset: 256
Horizontal Sync Pulse: 254
Vertical Sync Offset: 16
Vertical Sync Pulse: 48
Horizontal Display Size: 864
Vertical Display Size: 846
Horizontal Border: 54
Vertical Border: 84
Interlaced: true
Stereo Mode: 0
Sync Type: 0

2-Way Line-Interleaved Stereo: false

Detailed Timing Descriptor
Pixel Clock: 141.29MHz
Horizontal Active: 1331
Horizontal Blanking: 1096
Vertical Active: 10
Vertical Blanking: 32
Horizontal Sync Offset: 256
Horizontal Sync Pulse: 768
Vertical Sync Offset: 0
Vertical Sync Pulse: 0
Horizontal Display Size: 1024
Vertical Display Size: 256
Horizontal Border: 33
Vertical Border: 158
Interlaced: false
Stereo Mode: 0
Sync Type: 0


2-Way Line-Interleaved Stereo: false

 

@Solo wing Checksum: 0xD1 valid

SEC5044

Code:

00 FF FF FF FF FF FF 00 4C A3 44 50 00 00 00 00  
01 16 01 04 95 26 15 78 02 A0 55 8D 51 5A 96 2A  
1C 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01  
01 01 01 01 01 01 5F 39 80 DC 70 38 40 40 30 20  
35 00 7E D7 10 00 00 1B 00 00 00 0F 00 00 00 00  
00 00 00 00 00 3C 96 10 FE 00 00 00 00 FE 00 47  
4E 33 36 54 80 31 37 33 48 54 0A 20 00 00 00 00  
00 00 41 21 9E 00 00 00 00 02 01 0A 20 20 01 D1

LGD02C5

Code:

00,FF,FF,FF,FF,FF,FF,00,30,E4,C5,02,00,00,00,00,01,14,01,04,95,26,15,78,02,5F,35,A4,58,56,9E,26,
0F,50,54,00,00,00,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,02,3A,80,18,71,38,2D,40,58,2C,
45,00,7E,D7,10,00,00,1B,D4,9A,80,C8,73,38,24,41,30,20,35,00,7E,D7,10,00,00,1B,D4,9A,80,C8,73,38,
A8,40,30,20,35,00,7E,D7,10,00,00,1B,D4,9A,80,C8,73,38,40,40,30,20,35,00,7E,D7,10,00,00,1B,01,27

 

Maybe try removing the "Fast Start-Up" option in Windows - that caused me issues with starting up Windows from a cold boot, see the following pic where to find it, you have to click the 'run as admin' symbol towards the top of the window before you can uncheck the "Fast Start-Up" option:

 

like black screens? maybe fastboot is causing the nvidia drivers to break.

is this the same as the fast boot in the UEFI?

 

It didn't create black screens, just strange problems when cold booting - as soon as it got to the Windows logo it would restart the laptop, and then I'd get a beep code error for a failed GPU, I'd then have to solve that by clearing the CMOS (power drain with power button held down & battery removed), then it would cold boot one time without issue, then subsequent cold boots would go through the same process I've just described - was only possible to solve this by removing the "Fast Start-Up" option. "Fast Start-Up" option is not to do with UEFI, it's a windows option (I included a pic in my previous post where to find it). I'm definitely not saying that removing "Fast Start-Up" option solves the EDID LCD failures we're seeing here, but for Papusans start-up problem I thought it could be relevant as I don't think his issue is necessarily related to the failures we've been seeing here.

 

I have forwarded this thread to the regional manager of Europe - DELL for him to let the engineers to look at it.

 

@Matrix Leader
Good idea. We might actually get somewhere with more bodies working on this. As it stands, the only progress that we have gotten in the past month is from our forum members. That's pretty damn sad if you ask me.