topic Black Screen after driver update (Asus UX32VD-DB71) in Graphics

Black Screen after driver update (Asus UX32VD-DB71)

APivk — Mon, 17 Feb 2014 06:56:40 GMT

Hi,

I replied to the official black screen thread, but it looks like that thread isn't going anywhere...

I am creating a new thread because this seems to be a recurring issue without an answer.

(see )

Looks like that question remained unanswered...

Problem:

After installing the intel driver(v 9.11.10.2828 from ASUS) [tried to updating to 10.18.10.3345 (package 15.33.8.64.3345) as well], the built-in screen turned off and wouldn't display an image (even at boot/post).

I've tried to create an EDID override in windows(ie. monitor driver), as well as trying to create a DDC connection to read (and update) the EDID. PowerStrip can't create a connection and read-edid tells me the EDID is probably wrong (and that something special has happened).

My laptop is no longer under warranty, so I'll have to pay ~$200 for a screen replacement. This is not an issue IF I can understand why this happened and how to prevent this in the future.

Right now it looks like the Intel update corrupted the LCD. and I would appreciate if anybody could suggest any ideas about how to fix this and why this happened in the first place.

Thanks

Re: Black Screen after driver update (Asus UX32VD-DB71)

Allan_J_Intel1 — Tue, 18 Feb 2014 15:53:36 GMT

Drivers updates cannot corrupt hardware such displays. The problem might be related to the monitor EDID not interacting with graphics VBIOS.

Please try updating computer BIOS, this will hand shake Video BIOS. Please bear in mind the graphics controller is part of the processor and the graphics portion can get damaged.

Please update BIOS and try to install latest Intel graphics driver.

Allan.

Re: Black Screen after driver update (Asus UX32VD-DB71)

APivk — Tue, 18 Feb 2014 16:08:11 GMT

Thanks for your reply allan.

I already have the latest BIOS version (214) for my laptop, according to ASUS.

I even tried downgrading it back to older versions and then updating to the new version again (And installing the newest driver), but alas.

Thanks.