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

Discussion in 'Alienware' started by Mr. Fox, Aug 1, 2015.

Thread Status:
Not open for further replies.
  1. GodlikeRU

    GodlikeRU Notebook Deity

    Reputations:
    165
    Messages:
    1,254
    Likes Received:
    562
    Trophy Points:
    131
    Were there any reports for broken screens on not windows 10?
     
  2. Mr. Fox

    Mr. Fox BGA Filth-Hating Elitist

    Reputations:
    34,426
    Messages:
    37,027
    Likes Received:
    61,896
    Trophy Points:
    931
    Yes, running Windows 7 and 8.1 there are reports, but these are almost all machines that had Windows 10 installed earlier and something may have been corrupted in the BIOS to cause it (having nothing to do with Windows) even after Windows 10 has been removed. There are two machines with 8 beeps that never had Windows 10 installed, so there are too many unknown variables to be certain.
     
    TomJGX, PC GAMER and ajc9988 like this.
  3. liteon6x

    liteon6x Notebook Geek

    Reputations:
    18
    Messages:
    98
    Likes Received:
    29
    Trophy Points:
    26
    I had a Alienware 18 ( 2013) 780m sli.

    The monitor was overclocked to 100z when I installed windows 10, and it when thru flawlessly.

    Looking on this thread, I would never had attempted such feat
     
    TomJGX, PC GAMER and Mr. Fox like this.
  4. t456

    t456 1977-09-05, 12:56:00 UTC Moderator

    Reputations:
    1,932
    Messages:
    2,579
    Likes Received:
    2,023
    Trophy Points:
    181
    Yes, either that or (v)bios corruption. You still have a booting system, so flash those first ...

    Actually, make backup of both and then flash. It would help immensely if we can compare them to pre-10/non-flashed versions. Write this .img to usb stick and check the various flash programs, there's .txt files that will tell you which command switches to use to make an export. Ignore the 'autoflash' bit, that's only if you rename an xyz.bat to autoexec.bat and drop it to the root of the stick.
    Try the write-edid tool, it was written to circumvent the same bug. And does export work after hotswapping? Might try 'i2cdetect -l' again first; it may not like the hotswap.

    Hm, what size is that usb stick? Mine are either 32GB or 1GB, nothing in-between ... Damn Small Linux works, but it's ... not right for this.
     
    Mr. Fox and Scerate like this.
  5. Scerate

    Scerate Notebook Evangelist

    Reputations:
    224
    Messages:
    687
    Likes Received:
    649
    Trophy Points:
    106
    ^This, i mean i can be somewhat semi happy, cause i don't have to reinstall every day and go into Bios, but still for me it definitely happened about the 355.60 > 355.82 update, cause when i were at gamescom 2015, 6-9 august i actually was reinstalling windows 8.1 several times from windows 10 due to the fact everything went berserk, or better say nothing worked on w10 (SSD Freezed and very very much Permission errors) was fixed after a update tho. Back then i had definitely no EDID issues, so just to say i could enter bios, dos and do that stuff before the nV drivers get's initialised. I just updated to W10 beginning september, just do give it a go paried with the new Prema v2 Bios, cause i thought maybe the compatibility is there then, and i still had the 355.60 from the update process and i know i still had no EDID issues, cause i were actually configuring the Prema v2 Bios, so it must have happened somewhere going from 355.60 to 355.83, dunno if using DDU was the mistake i made, i dunno.

    Edit: The reason i had to upgrade from x.60 to x.83 were actually, that when i came back from hibernation my screen flickered and thought i would give the newer drivers a go.

    thx will try it tomorrow then, so far i noticed brightness isn't working too anymore. And about the backup, i can only give a backup of my 980M.rom i already flashed back from Prema v2 to stock 1.03.16(?).
     
    Last edited: Sep 14, 2015
    PC GAMER and ajc9988 like this.
  6. Mr. Fox

    Mr. Fox BGA Filth-Hating Elitist

    Reputations:
    34,426
    Messages:
    37,027
    Likes Received:
    61,896
    Trophy Points:
    931
    @t456 - might have worked. We're about to find out. The terminal output is encouraging.
    Code:
    mint@mint ~/Downloads/write-edid-master $ sudo ./write-edid.sh 1 SEC5448.bin
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x00
    Writing byte 0xFF to bus 1, chip-adress 0x50, data-adress 0x01
    Writing byte 0xFF to bus 1, chip-adress 0x50, data-adress 0x02
    Writing byte 0xFF to bus 1, chip-adress 0x50, data-adress 0x03
    Writing byte 0xFF to bus 1, chip-adress 0x50, data-adress 0x04
    Writing byte 0xFF to bus 1, chip-adress 0x50, data-adress 0x05
    Writing byte 0xFF to bus 1, chip-adress 0x50, data-adress 0x06
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x07
    Writing byte 0x4C to bus 1, chip-adress 0x50, data-adress 0x08
    Writing byte 0xA3 to bus 1, chip-adress 0x50, data-adress 0x09
    Writing byte 0x48 to bus 1, chip-adress 0x50, data-adress 0x0a
    Writing byte 0x54 to bus 1, chip-adress 0x50, data-adress 0x0b
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x0c
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x0d
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x0e
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x0f
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x10
    Writing byte 0x14 to bus 1, chip-adress 0x50, data-adress 0x11
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x12
    Writing byte 0x04 to bus 1, chip-adress 0x50, data-adress 0x13
    Writing byte 0x90 to bus 1, chip-adress 0x50, data-adress 0x14
    Writing byte 0x29 to bus 1, chip-adress 0x50, data-adress 0x15
    Writing byte 0x17 to bus 1, chip-adress 0x50, data-adress 0x16
    Writing byte 0x78 to bus 1, chip-adress 0x50, data-adress 0x17
    Writing byte 0x0A to bus 1, chip-adress 0x50, data-adress 0x18
    Writing byte 0xC8 to bus 1, chip-adress 0x50, data-adress 0x19
    Writing byte 0x95 to bus 1, chip-adress 0x50, data-adress 0x1a
    Writing byte 0x9E to bus 1, chip-adress 0x50, data-adress 0x1b
    Writing byte 0x57 to bus 1, chip-adress 0x50, data-adress 0x1c
    Writing byte 0x54 to bus 1, chip-adress 0x50, data-adress 0x1d
    Writing byte 0x92 to bus 1, chip-adress 0x50, data-adress 0x1e
    Writing byte 0x26 to bus 1, chip-adress 0x50, data-adress 0x1f
    Writing byte 0x0F to bus 1, chip-adress 0x50, data-adress 0x20
    Writing byte 0x50 to bus 1, chip-adress 0x50, data-adress 0x21
    Writing byte 0x54 to bus 1, chip-adress 0x50, data-adress 0x22
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x23
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x24
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x25
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x26
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x27
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x28
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x29
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x2a
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x2b
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x2c
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x2d
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x2e
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x2f
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x30
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x31
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x32
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x33
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x34
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x35
    Writing byte 0x29 to bus 1, chip-adress 0x50, data-adress 0x36
    Writing byte 0x36 to bus 1, chip-adress 0x50, data-adress 0x37
    Writing byte 0x80 to bus 1, chip-adress 0x50, data-adress 0x38
    Writing byte 0xA0 to bus 1, chip-adress 0x50, data-adress 0x39
    Writing byte 0x70 to bus 1, chip-adress 0x50, data-adress 0x3a
    Writing byte 0x38 to bus 1, chip-adress 0x50, data-adress 0x3b
    Writing byte 0x1F to bus 1, chip-adress 0x50, data-adress 0x3c
    Writing byte 0x40 to bus 1, chip-adress 0x50, data-adress 0x3d
    Writing byte 0x18 to bus 1, chip-adress 0x50, data-adress 0x3e
    Writing byte 0x10 to bus 1, chip-adress 0x50, data-adress 0x3f
    Writing byte 0x25 to bus 1, chip-adress 0x50, data-adress 0x40
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x41
    Writing byte 0x99 to bus 1, chip-adress 0x50, data-adress 0x42
    Writing byte 0xE6 to bus 1, chip-adress 0x50, data-adress 0x43
    Writing byte 0x10 to bus 1, chip-adress 0x50, data-adress 0x44
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x45
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x46
    Writing byte 0x1A to bus 1, chip-adress 0x50, data-adress 0x47
    Writing byte 0x1C to bus 1, chip-adress 0x50, data-adress 0x48
    Writing byte 0x24 to bus 1, chip-adress 0x50, data-adress 0x49
    Writing byte 0x80 to bus 1, chip-adress 0x50, data-adress 0x4a
    Writing byte 0xA0 to bus 1, chip-adress 0x50, data-adress 0x4b
    Writing byte 0x70 to bus 1, chip-adress 0x50, data-adress 0x4c
    Writing byte 0x38 to bus 1, chip-adress 0x50, data-adress 0x4d
    Writing byte 0x1F to bus 1, chip-adress 0x50, data-adress 0x4e
    Writing byte 0x40 to bus 1, chip-adress 0x50, data-adress 0x4f
    Writing byte 0x18 to bus 1, chip-adress 0x50, data-adress 0x50
    Writing byte 0x10 to bus 1, chip-adress 0x50, data-adress 0x51
    Writing byte 0x25 to bus 1, chip-adress 0x50, data-adress 0x52
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x53
    Writing byte 0x99 to bus 1, chip-adress 0x50, data-adress 0x54
    Writing byte 0xE6 to bus 1, chip-adress 0x50, data-adress 0x55
    Writing byte 0x10 to bus 1, chip-adress 0x50, data-adress 0x56
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x57
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x58
    Writing byte 0x1A to bus 1, chip-adress 0x50, data-adress 0x59
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x5a
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x5b
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x5c
    Writing byte 0xFE to bus 1, chip-adress 0x50, data-adress 0x5d
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x5e
    Writing byte 0x48 to bus 1, chip-adress 0x50, data-adress 0x5f
    Writing byte 0x47 to bus 1, chip-adress 0x50, data-adress 0x60
    Writing byte 0x54 to bus 1, chip-adress 0x50, data-adress 0x61
    Writing byte 0x33 to bus 1, chip-adress 0x50, data-adress 0x62
    Writing byte 0x4A to bus 1, chip-adress 0x50, data-adress 0x63
    Writing byte 0x80 to bus 1, chip-adress 0x50, data-adress 0x64
    Writing byte 0x31 to bus 1, chip-adress 0x50, data-adress 0x65
    Writing byte 0x38 to bus 1, chip-adress 0x50, data-adress 0x66
    Writing byte 0x34 to bus 1, chip-adress 0x50, data-adress 0x67
    Writing byte 0x48 to bus 1, chip-adress 0x50, data-adress 0x68
    Writing byte 0x54 to bus 1, chip-adress 0x50, data-adress 0x69
    Writing byte 0x0A to bus 1, chip-adress 0x50, data-adress 0x6a
    Writing byte 0x20 to bus 1, chip-adress 0x50, data-adress 0x6b
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x6c
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x6d
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x6e
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x6f
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x70
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x71
    Writing byte 0x41 to bus 1, chip-adress 0x50, data-adress 0x72
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x73
    Writing byte 0x9E to bus 1, chip-adress 0x50, data-adress 0x74
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x75
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x76
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x77
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x78
    Writing byte 0x02 to bus 1, chip-adress 0x50, data-adress 0x79
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x7a
    Writing byte 0x0A to bus 1, chip-adress 0x50, data-adress 0x7b
    Writing byte 0x20 to bus 1, chip-adress 0x50, data-adress 0x7c
    Writing byte 0x20 to bus 1, chip-adress 0x50, data-adress 0x7d
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x7e
    Writing byte 0xA8 to bus 1, chip-adress 0x50, data-adress 0x7f
    Writing done, here is the output of i2cdump -y 1 0x50:
    No size specified (using byte-data access)
         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
    00: 00 ff ff ff ff ff ff 00 4c a3 48 54 00 00 00 00    ........L?HT....
    10: 00 14 01 04 90 29 17 78 0a c8 95 9e 57 54 92 26    .????)?x????WT?&
    20: 0f 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01    ?PT...??????????
    30: 01 01 01 01 01 01 29 36 80 a0 70 38 1f 40 18 10    ??????)6??p8?@??
    40: 25 00 99 e6 10 00 00 1a 1c 24 80 a0 70 38 1f 40    %.???..??$??p8?@
    50: 18 10 25 00 99 e6 10 00 00 1a 00 00 00 fe 00 48    ??%.???..?...?.H
    60: 47 54 33 4a 80 31 38 34 48 54 0a 20 00 00 00 00    GT3J?184HT? ....
    70: 00 00 41 01 9e 00 00 00 00 02 01 0a 20 20 00 a8    ..A??....???  .?
    80: ff ff ff ff ff ff ff ff ff 01 ff ff ff ff ff ff    .........?......
    90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
    a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
    b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
    c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
    d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
    e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
    f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
    mint@mint ~/Downloads/write-edid-master $
    
     
    andrewsi2012 and ajc9988 like this.
  7. Mr. Fox

    Mr. Fox BGA Filth-Hating Elitist

    Reputations:
    34,426
    Messages:
    37,027
    Likes Received:
    61,896
    Trophy Points:
    931
    YAY! It worked! God Bless @t456.

    I am typing this from my M18xR1 with one of the hot-swapped display panel that was corrupted by Windows 10 on the M18xR2. Now, the question is, will it stay fixed on the M18xR2 now that the system BIOS has been affected by Windows 10?

    I did not need to do this. It flashed without scanning using that command after hot-swapping. The error message was EXACTLY the same bug in that link you posted and the write-edid tool did the trick.

    I am using my ADATA USB 3.0 32GB S102 Pro thumb drive with the "Live" bootable Mint Linux distro on it. I did not even need to install Linux to do this. I had to install some packages, including python and the other tools mentioned in the posts for edid-rw and write-edid, but once those were installed everything was easy. I flashed the good .bin file that I had posted last week.

    Code:
    mint@mint ~/Downloads/write-edid-master $ sudo ./write-edid.sh 1 SEC5448.bin
    Yay-Flashed-EDID.JPG M18xR1-Flashed-LCD.jpg Mint-Linux-USB.JPG

    Here are the steps I followed:
    • Booted Mint Linux "Live" distro from my USB thumb drive
    • Downloaded this and extracted in "Downloads" folder: ChalkElec/write-edid
    • Downloaded this and extracted in "Downloads" folder: bulletmark/edid-rw
    • Installed these pre-requisite packages:
      Using terminal: sudo apt-get install python-smbus edid-decode
      Using terminal: sudo apt-get install edid-decode
      Using Synaptics Package Manager found and installed i2ctools, edid-decode, read-edid, libparse-edid-perl
    • Opened terminal in edid-rw folder and ran this command to confirm the right enumeration
      Command: sudo ./edid-rw 0 | edid-decode (returned errors and garbage, so display 0 not enumerated)
      Command: sudo ./edid-rw 1 | edid-decode (returned good EDID specs, confirmed display 1 was enumerated)
    • Downloaded my good SEC5448.bin file and put it in the write-edid folder
    • Set run permissions for write-edid program using terminal
      Command: chmod a+x write-edid.sh
    • Hot-swapped corrupted display panel (unplugged good one, plugged in bad one)
    • Opened terminal in write-edid folder and ran this command to flash the EDID to EEPROM
      Command: sudo ./write-edid.sh 1 SEC5448.bin
    I will try to replicate this process on another display that has been corrupted and take screen shots or photos and provide more detail the next go 'round. I basically stumbled my way through the process and the above steps are based on my memory using trial and error. I am not a Linux expert by any means... total noob at Linux.

    OK, corrupt LCD #2 flashed
    LCD not found enumerated as display #0
    Code:
    mint@mint ~/Downloads/edid-rw-master $ sudo ./edid-rw 0 | edid-decode
    Traceback (most recent call last):
      File "./edid-rw", line 141, in <module>
        main()
      File "./edid-rw", line 129, in main
        edid = [dev.read(i) for i in range(EDID_HDR)]
      File "./edid-rw", line 48, in read
        return self.smb.read_byte_data(EDID_ADDR, n)
    IOError: [Errno 6] No such device or address
    Extracted contents:
    header:          00 00 00 00 00 00 00 00
    serial number:   00 00 00 00 00 00 00 00 00 00
    version:         00 00
    basic params:    00 00 00 00 00
    chroma info:     00 00 00 00 00 00 00 00 00 00
    established:     00 00 00
    standard:        00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    descriptor 1:    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    descriptor 2:    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    descriptor 3:    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    descriptor 4:    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    extensions:      00
    checksum:        00
    
    No header found
    Manufacturer: @@@ Model 0 Serial Number 0
    EDID version: 0.0
    Analog display, Input voltage level: 0.7/0.3 V
    Sync:
    Image size is variable
    Gamma: 1.00
    Monochrome or grayscale display
    Established timings supported:
    Standard timings supported:
    non-conformant standard timing (0 horiz)
    non-conformant standard timing (0 horiz)
    non-conformant standard timing (0 horiz)
    non-conformant standard timing (0 horiz)
    non-conformant standard timing (0 horiz)
    non-conformant standard timing (0 horiz)
    non-conformant standard timing (0 horiz)
    non-conformant standard timing (0 horiz)
    Manufacturer-specified data, tag 0
    Manufacturer-specified data, tag 0
    Manufacturer-specified data, tag 0
    Manufacturer-specified data, tag 0
    Checksum: 0x0
    EDID block does not conform at all!
        Bad year of manufacture
        Manufacturer name field contains garbage
    mint@mint ~/Downloads/edid-rw-master $
    
    LCD found enumerated as display #1
    Code:
    mint@mint ~/Downloads/edid-rw-master $ sudo ./edid-rw 1 | edid-decode
    Extracted contents:
    header:          00 ff ff ff ff ff ff 00
    serial number:   4c a3 48 54 00 00 00 00 00 14
    version:         01 04
    basic params:    90 29 17 78 0a
    chroma info:     c8 95 9e 57 54 92 26 0f 50 54
    established:     00 00 00
    standard:        01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
    descriptor 1:    29 36 80 a0 70 38 1f 40 18 10 25 00 99 e6 10 00 00 1a
    descriptor 2:    1c 24 80 a0 70 38 1f 40 18 10 25 00 99 e6 10 00 00 1a
    descriptor 3:    00 00 00 fe 00 48 47 54 33 4a 80 31 38 34 48 54 0a 20
    descriptor 4:    00 00 00 00 00 00 41 01 9e 00 00 00 00 02 01 0a 20 20
    extensions:      00
    checksum:        a8
    
    Manufacturer: SEC Model 5448 Serial Number 0
    Made week 0 of 2010
    EDID version: 1.4
    Digital display
    6 bits per primary color channel
    Digital interface is not defined
    Maximum image size: 41 cm x 23 cm
    Gamma: 2.20
    Supported color formats: RGB 4:4:4, YCrCb 4:2:2
    First detailed timing is preferred timing
    Established timings supported:
    Standard timings supported:
    Detailed mode: Clock 138.650 MHz, 409 mm x 230 mm
                   1920 1944 1960 2080 hborder 0
                   1080 1082 1087 1111 vborder 0
                   +hsync -vsync
    Detailed mode: Clock 92.440 MHz, 409 mm x 230 mm
                   1920 1944 1960 2080 hborder 0
                   1080 1082 1087 1111 vborder 0
                   +hsync -vsync
    ASCII string: HGT3J�184HT
    Manufacturer-specified data, tag 0
    Checksum: 0xa8
    EDID block does NOT conform to EDID 1.3!
        Missing name descriptor
        Missing monitor ranges
    mint@mint ~/Downloads/edid-rw-master $
    
    STOP: Unplug good display and connect LVDS cable for corrupted display
    Flash corrupted display with known good EDID (in this example SEC5448.bin for M18xR1/R2)
    Code:
    mint@mint ~/Downloads/write-edid-master $ chmod a+x write-edid.sh
    mint@mint ~/Downloads/write-edid-master $ sudo ./write-edid.sh 1 SEC5448.bin
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x00
    Writing byte 0xFF to bus 1, chip-adress 0x50, data-adress 0x01
    Writing byte 0xFF to bus 1, chip-adress 0x50, data-adress 0x02
    Writing byte 0xFF to bus 1, chip-adress 0x50, data-adress 0x03
    Writing byte 0xFF to bus 1, chip-adress 0x50, data-adress 0x04
    Writing byte 0xFF to bus 1, chip-adress 0x50, data-adress 0x05
    Writing byte 0xFF to bus 1, chip-adress 0x50, data-adress 0x06
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x07
    Writing byte 0x4C to bus 1, chip-adress 0x50, data-adress 0x08
    Writing byte 0xA3 to bus 1, chip-adress 0x50, data-adress 0x09
    Writing byte 0x48 to bus 1, chip-adress 0x50, data-adress 0x0a
    Writing byte 0x54 to bus 1, chip-adress 0x50, data-adress 0x0b
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x0c
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x0d
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x0e
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x0f
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x10
    Writing byte 0x14 to bus 1, chip-adress 0x50, data-adress 0x11
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x12
    Writing byte 0x04 to bus 1, chip-adress 0x50, data-adress 0x13
    Writing byte 0x90 to bus 1, chip-adress 0x50, data-adress 0x14
    Writing byte 0x29 to bus 1, chip-adress 0x50, data-adress 0x15
    Writing byte 0x17 to bus 1, chip-adress 0x50, data-adress 0x16
    Writing byte 0x78 to bus 1, chip-adress 0x50, data-adress 0x17
    Writing byte 0x0A to bus 1, chip-adress 0x50, data-adress 0x18
    Writing byte 0xC8 to bus 1, chip-adress 0x50, data-adress 0x19
    Writing byte 0x95 to bus 1, chip-adress 0x50, data-adress 0x1a
    Writing byte 0x9E to bus 1, chip-adress 0x50, data-adress 0x1b
    Writing byte 0x57 to bus 1, chip-adress 0x50, data-adress 0x1c
    Writing byte 0x54 to bus 1, chip-adress 0x50, data-adress 0x1d
    Writing byte 0x92 to bus 1, chip-adress 0x50, data-adress 0x1e
    Writing byte 0x26 to bus 1, chip-adress 0x50, data-adress 0x1f
    Writing byte 0x0F to bus 1, chip-adress 0x50, data-adress 0x20
    Writing byte 0x50 to bus 1, chip-adress 0x50, data-adress 0x21
    Writing byte 0x54 to bus 1, chip-adress 0x50, data-adress 0x22
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x23
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x24
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x25
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x26
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x27
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x28
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x29
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x2a
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x2b
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x2c
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x2d
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x2e
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x2f
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x30
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x31
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x32
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x33
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x34
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x35
    Writing byte 0x29 to bus 1, chip-adress 0x50, data-adress 0x36
    Writing byte 0x36 to bus 1, chip-adress 0x50, data-adress 0x37
    Writing byte 0x80 to bus 1, chip-adress 0x50, data-adress 0x38
    Writing byte 0xA0 to bus 1, chip-adress 0x50, data-adress 0x39
    Writing byte 0x70 to bus 1, chip-adress 0x50, data-adress 0x3a
    Writing byte 0x38 to bus 1, chip-adress 0x50, data-adress 0x3b
    Writing byte 0x1F to bus 1, chip-adress 0x50, data-adress 0x3c
    Writing byte 0x40 to bus 1, chip-adress 0x50, data-adress 0x3d
    Writing byte 0x18 to bus 1, chip-adress 0x50, data-adress 0x3e
    Writing byte 0x10 to bus 1, chip-adress 0x50, data-adress 0x3f
    Writing byte 0x25 to bus 1, chip-adress 0x50, data-adress 0x40
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x41
    Writing byte 0x99 to bus 1, chip-adress 0x50, data-adress 0x42
    Writing byte 0xE6 to bus 1, chip-adress 0x50, data-adress 0x43
    Writing byte 0x10 to bus 1, chip-adress 0x50, data-adress 0x44
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x45
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x46
    Writing byte 0x1A to bus 1, chip-adress 0x50, data-adress 0x47
    Writing byte 0x1C to bus 1, chip-adress 0x50, data-adress 0x48
    Writing byte 0x24 to bus 1, chip-adress 0x50, data-adress 0x49
    Writing byte 0x80 to bus 1, chip-adress 0x50, data-adress 0x4a
    Writing byte 0xA0 to bus 1, chip-adress 0x50, data-adress 0x4b
    Writing byte 0x70 to bus 1, chip-adress 0x50, data-adress 0x4c
    Writing byte 0x38 to bus 1, chip-adress 0x50, data-adress 0x4d
    Writing byte 0x1F to bus 1, chip-adress 0x50, data-adress 0x4e
    Writing byte 0x40 to bus 1, chip-adress 0x50, data-adress 0x4f
    Writing byte 0x18 to bus 1, chip-adress 0x50, data-adress 0x50
    Writing byte 0x10 to bus 1, chip-adress 0x50, data-adress 0x51
    Writing byte 0x25 to bus 1, chip-adress 0x50, data-adress 0x52
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x53
    Writing byte 0x99 to bus 1, chip-adress 0x50, data-adress 0x54
    Writing byte 0xE6 to bus 1, chip-adress 0x50, data-adress 0x55
    Writing byte 0x10 to bus 1, chip-adress 0x50, data-adress 0x56
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x57
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x58
    Writing byte 0x1A to bus 1, chip-adress 0x50, data-adress 0x59
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x5a
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x5b
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x5c
    Writing byte 0xFE to bus 1, chip-adress 0x50, data-adress 0x5d
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x5e
    Writing byte 0x48 to bus 1, chip-adress 0x50, data-adress 0x5f
    Writing byte 0x47 to bus 1, chip-adress 0x50, data-adress 0x60
    Writing byte 0x54 to bus 1, chip-adress 0x50, data-adress 0x61
    Writing byte 0x33 to bus 1, chip-adress 0x50, data-adress 0x62
    Writing byte 0x4A to bus 1, chip-adress 0x50, data-adress 0x63
    Writing byte 0x80 to bus 1, chip-adress 0x50, data-adress 0x64
    Writing byte 0x31 to bus 1, chip-adress 0x50, data-adress 0x65
    Writing byte 0x38 to bus 1, chip-adress 0x50, data-adress 0x66
    Writing byte 0x34 to bus 1, chip-adress 0x50, data-adress 0x67
    Writing byte 0x48 to bus 1, chip-adress 0x50, data-adress 0x68
    Writing byte 0x54 to bus 1, chip-adress 0x50, data-adress 0x69
    Writing byte 0x0A to bus 1, chip-adress 0x50, data-adress 0x6a
    Writing byte 0x20 to bus 1, chip-adress 0x50, data-adress 0x6b
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x6c
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x6d
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x6e
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x6f
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x70
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x71
    Writing byte 0x41 to bus 1, chip-adress 0x50, data-adress 0x72
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x73
    Writing byte 0x9E to bus 1, chip-adress 0x50, data-adress 0x74
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x75
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x76
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x77
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x78
    Writing byte 0x02 to bus 1, chip-adress 0x50, data-adress 0x79
    Writing byte 0x01 to bus 1, chip-adress 0x50, data-adress 0x7a
    Writing byte 0x0A to bus 1, chip-adress 0x50, data-adress 0x7b
    Writing byte 0x20 to bus 1, chip-adress 0x50, data-adress 0x7c
    Writing byte 0x20 to bus 1, chip-adress 0x50, data-adress 0x7d
    Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x7e
    Writing byte 0xA8 to bus 1, chip-adress 0x50, data-adress 0x7f
    Writing done, here is the output of i2cdump -y 1 0x50:
    No size specified (using byte-data access)
         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
    00: 00 ff ff ff ff ff ff 00 4c a3 48 54 00 00 00 00    ........L?HT....
    10: 00 14 01 04 90 29 17 78 0a c8 95 9e 57 54 92 26    .????)?x????WT?&
    20: 0f 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01    ?PT...??????????
    30: 01 01 01 01 01 01 29 36 80 a0 70 38 1f 40 18 10    ??????)6??p8?@??
    40: 25 00 99 e6 10 00 00 1a 1c 24 80 a0 70 38 1f 40    %.???..??$??p8?@
    50: 18 10 25 00 99 e6 10 00 00 1a 00 00 00 fe 00 48    ??%.???..?...?.H
    60: 47 54 33 4a 80 31 38 34 48 54 0a 20 00 00 00 00    GT3J?184HT? ....
    70: 00 00 41 01 9e 00 00 00 00 02 01 0a 20 20 00 a8    ..A??....???  .?
    80: ff ff ff ff ff ff ff ff ff 00 ff ff ff ff ff ff    ................
    90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
    a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
    b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
    c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
    d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
    e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
    f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
    mint@mint ~/Downloads/write-edid-master $ 

    Update:
    Good news (sort of). Unfortunately, the M18xR2 almost immediately re-bricked the display. First reboot was fine, so was the second, but the third reboot the screen did a bright flash, EDID corrupted and 8 beeps. I think the flash might be the writing of corrupt data to EDID. Before rebooting I removed the latest and greatest Intel Chipset and Intel ME drivers and installed those from dell.com/support designed for the M18xR2, not generic versions from the web. I flashed the system BIOS to stock A10, dumped the vBIOS and flashed stock vBIOS. In spite of all that, it still corrupted the EDID and made the machine unbootable.

    So, I re-flashed the display again. Got out a spare LVDS cable and my X-acto knife. @t456 was correct (as usual). I severed the wire for pin #5 (fourth wire in from the right) and everything is working. It has not re-bricked itself again. I flashed the A10 unlocked system BIOS and I am about to flash my unlocked vBIOS.

    Now, another observation... a couple of times I puckered up my glutimus maximus really hard, almost got a charlie horse, thinking it was going to brick itself. With the 4th wire (pin #5) cut there is a brief pause of black screen, maybe for one second, similar to what it would do before the screen flash and 8 beeps. It's like something is trying to write and can't. So, maybe that is really great news as far as usability. But, it makes me wonder what Windows 10 did even more now. Something got changed and it's still changed. Not happy about that part, but if my gorgeous red banshee beast is back from the dead, then there is reason for everyone affected by this Micro$haft trojan malware cancer OS the way I have been to be happy.

    Will report if there are any more issues. I don't want to jump the gun, so let's give it more time to see if this is really a permanent fix.

    EDIT: Don't waste your time snipping the LVDS wire. It doesn't do any good and won't stop it from happening again if you are using EVGA Precision X.

    Here is a safe version of EVGA Precision X that will not brick the LCD panel.

    https://drive.google.com/file/d/0Bwdqi25LDwZyYjJTRHZVbTBXazA/view


    wp_20150914_20_48_24_pro.jpg
     

    Attached Files:

    Last edited: May 25, 2016
    flyingfool, codzor, ole!!! and 17 others like this.
  8. Cass-Olé

    Cass-Olé Notebook Evangelist

    Reputations:
    722
    Messages:
    336
    Likes Received:
    974
    Trophy Points:
    106
    "affected by Windows 10" ... or infected ...

    looks like old sneaky Fox may've pulled off a form of alien-exorcism
    ... duck if that sucker spits out some grean pea soup at ya then thump it with the good book ...
     
    Last edited: Sep 14, 2015
    ole!!!, andrewsi2012 and Mr. Fox like this.
  9. Mr. Fox

    Mr. Fox BGA Filth-Hating Elitist

    Reputations:
    34,426
    Messages:
    37,027
    Likes Received:
    61,896
    Trophy Points:
    931
    LOL, exorcism indeed and "infected" is definitely the more accurate word choice.
     
    Cass-Olé and andrewsi2012 like this.
  10. thegh0sts

    thegh0sts Notebook Nobel Laureate

    Reputations:
    947
    Messages:
    7,700
    Likes Received:
    2,818
    Trophy Points:
    331
    are you still going to do the pin #5 hack?
     
    Mr. Fox likes this.
Loading...
Thread Status:
Not open for further replies.

Share This Page