Problems? See this thread at archive.org.
Great news, just make sure to regularly check for any signs of your edid being corrupted. Other than that, you are most likely fine as you would already have experienced several issues if it were infected. Had windows 10'installed for almost a week before reverting back to win8.1, got the same result as you. But as others are saying, I would stay the hell away from win 10 not just because of this issue but the OS itself is a disappointment.
-
so far so good... 47 days and counting on win10 pro x64 / driver 353.62 / Clevo P750ZM / UEFI Boot / no CSM / no Secure Boot / Fast Boot enabled but Hibernation deactivated / eDP Panasonic VVX16T020G00 2880x1620 Panel
![[IMG]](images/storyImages/HcHGwEk.jpg)
![[IMG]](images/storyImages/3IOLkBy.png)
not going to change a thing about my current config though
not taking any risks...
Attached Files:
-
ill check in my bios in a bit and provide some pics, wanna make sure that i didnt just post some humbug here
ull know in a bit ultima
Sent from my Nexus 5 using TapatalkPC GAMER likes this. -
yes im aware of that, but thanks for the headsup i kept in mind that the actual win8 fast boot needed the hibersys file to be present in order to be properly executed, so with that disabled it shouldnt ne possible to use it anyways, right?
Sent from my Nexus 5 using Tapatalk -
-
MahmoudDewy likes this.
-
On my old system I just revived, 352.xx was causing flashing when waking the system from sleep, just like 355.xx was. I went back to a 347.xx (January being the oldest driver without going to the archive) driver, the flickering stopped! This is on win 7. Suggests the new drivers aren't there yet!!!
PC GAMER likes this.
-
-
-
Checking the hex code read from the EEPROM, it was definitely altered from its prior state.
Flashed the EDID again using the USB programmer and now it boots fine again. It has been sBIOS flashed 4 times now and vBIOS flashed 4 times, but something continues to write to and/or corrupt the EDID in EEPROM. I don’t know of any other explanation for this or how to fix it other than replace the motherboard with one that has never been screwed up by Windows 10.
I'm glad I found an easy way to correct it, but this nonsense is really getting old. We need a permanent fix for this. We should not have to fix anything. The morons that caused it should be tripping over themselves rushing to apologize and taking care of it.
hmscott, D2 Ultima, Scerate and 1 other person like this. -
I'm already a few steps ahead, but developer support for Linux gaming is still horrible... at least for the kind of games I enjoy, it's extremely limited selection and very few titles that I care about. I'm also a multi-GPU fanboy and have no plans to ever change that. Linux support for SLI sucks really bad as well. I used to dual boot Windows 7 and 8.1, but since Windows 10 screwed everything up, I have been dual booting Windows 7 and Mint Linux on the M18xR2. I'm running Mint on the 256GB mSATA. It's fun for enthusiasts and power users to tinker with. The main trouble with Linux is disorganization and being supported by volunteers that haven't agreed on compliance with a universal set of standards. Add to that the fact that all development is pretty much on a volunteer basis... you get what you pay for with Linux (which is obviously free). Because of those circumstances, it will never be able to replace Windows for the masses. And, because it cannot and will not, game developers are probably not overly excited about devoting resources to a platform that hardly anyone uses, especially gamers.
My passion/hobby is overclocked benching. Gaming is something I do when I don't have something better or more fun to spend time on. Linux support for CPU/GPU overclocking is all but non-existent (I guess Linux developers don't do it, so it's not something they burn any calories on) and almost none of the benchmark utilities used on overclocking leader boards are supported by Linux. It really is a Windows World despite what crApple and Linux fanboys would like us to believe.
I installed Mint to the mSATA with all other drives disconnected so I can manually choose it from the BIOS boot selection menu. Then I used EasyBCD and NeoGrub to add Mint to my Windows Boot Manager.
-
Sometimes we have to laugh in order to avoid crying or cursing, neither of which solves the problem. (Although both sometimes feel good... for a few minutes away.) I swear, this machine needs snaps and zippers now. It had been apart so many times in the past month that I've lost count.
All righty... M18xR2 LCD bricked again already. This time I took my spare LCD, booted from that, hotswapped it and booted into Mint Linux instead of using the USB programmer. Here's the corrupted EDID, which looks different than it has in the past, unless I just wasn't paying attention.
The descriptor 3 and 4 strings from the corrupted EDID are identical.
The descriptor 3 and 4 strings from the valid EDID are not identical.
Successful Linux flash using write-edid-master...Code:owner@M18xR2 ~/EDID/edid-rw-master $ sudo ./edid-rw 1 | edid-decode [sudo] password for owner: 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: 00 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 4c 54 4e 31 38 34 48 54 30 32 53 30 31 descriptor 4: 00 00 00 fe 00 4c 54 4e 31 38 34 48 54 30 32 53 30 31 extensions: 00 checksum: a0 Manufacturer: SEC Model 5448 Serial Number 0 Made week 0 of 2010 EDID version: 1.4 Analog display, Input voltage level: 0.7/0.3 V Blank level equals black level Sync: Maximum image size: 41 cm x 23 cm Gamma: 2.20 RGB color display 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: LTN184HT02S01ASCII string: LTN184HT02S01Checksum: 0xa0 (should be 0x30) EDID block does NOT conform to EDID 1.3! Missing name descriptor Missing monitor ranges EDID block does not conform at all! Block has broken checksum owner@M18xR2 ~/EDID/edid-rw-master $
After flashing...Code:owner@M18xR2 ~/EDID/write-edid-master $ sudo ./write-edid.sh 1 m18xr2-EDID.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 0xFC to bus 1, chip-adress 0x50, data-adress 0x5d Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x5e Writing byte 0x4C to bus 1, chip-adress 0x50, data-adress 0x5f Writing byte 0x54 to bus 1, chip-adress 0x50, data-adress 0x60 Writing byte 0x4E to bus 1, chip-adress 0x50, data-adress 0x61 Writing byte 0x31 to bus 1, chip-adress 0x50, data-adress 0x62 Writing byte 0x38 to bus 1, chip-adress 0x50, data-adress 0x63 Writing byte 0x34 to bus 1, chip-adress 0x50, data-adress 0x64 Writing byte 0x48 to bus 1, chip-adress 0x50, data-adress 0x65 Writing byte 0x54 to bus 1, chip-adress 0x50, data-adress 0x66 Writing byte 0x30 to bus 1, chip-adress 0x50, data-adress 0x67 Writing byte 0x32 to bus 1, chip-adress 0x50, data-adress 0x68 Writing byte 0x53 to bus 1, chip-adress 0x50, data-adress 0x69 Writing byte 0x30 to bus 1, chip-adress 0x50, data-adress 0x6a Writing byte 0x31 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 0xFE to bus 1, chip-adress 0x50, data-adress 0x6f Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x70 Writing byte 0x4D to bus 1, chip-adress 0x50, data-adress 0x71 Writing byte 0x72 to bus 1, chip-adress 0x50, data-adress 0x72 Writing byte 0x2E to bus 1, chip-adress 0x50, data-adress 0x73 Writing byte 0x20 to bus 1, chip-adress 0x50, data-adress 0x74 Writing byte 0x46 to bus 1, chip-adress 0x50, data-adress 0x75 Writing byte 0x6F to bus 1, chip-adress 0x50, data-adress 0x76 Writing byte 0x78 to bus 1, chip-adress 0x50, data-adress 0x77 Writing byte 0x27 to bus 1, chip-adress 0x50, data-adress 0x78 Writing byte 0x73 to bus 1, chip-adress 0x50, data-adress 0x79 Writing byte 0x20 to bus 1, chip-adress 0x50, data-adress 0x7a Writing byte 0x6C to bus 1, chip-adress 0x50, data-adress 0x7b Writing byte 0x63 to bus 1, chip-adress 0x50, data-adress 0x7c Writing byte 0x64 to bus 1, chip-adress 0x50, data-adress 0x7d Writing byte 0x00 to bus 1, chip-adress 0x50, data-adress 0x7e Writing byte 0xB8 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 fc 00 4c ??%.???..?...?.L 60: 54 4e 31 38 34 48 54 30 32 53 30 31 00 00 00 fe TN184HT02S01...? 70: 00 4d 72 2e 20 46 6f 78 27 73 20 6c 63 64 00 b8 .Mr. Fox's lcd.? 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ owner@M18xR2 ~/EDID/write-edid-master $
Any thoughts @t456?Validated checksum after flashing...Code:owner@M18xR2 ~/EDID/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 fc 00 4c 54 4e 31 38 34 48 54 30 32 53 30 31 descriptor 4: 00 00 00 fe 00 4d 72 2e 20 46 6f 78 27 73 20 6c 63 64 extensions: 00 checksum: b8 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: Mr. Fox's lcdChecksum: 0xb8 EDID block does NOT conform to EDID 1.3! Name descriptor not terminated with a newline Missing monitor ranges owner@M18xR2 ~/EDID/edid-rw-master $
Code:00 ff ff ff ff ff ff 00 4c a3 48 54 00 00 00 00 00 14 01 04 90 29 17 78 0a c8 95 9e 57 54 92 26 0f 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 29 36 80 a0 70 38 1f 40 18 10 25 00 99 e6 10 00 00 1a 1c 24 80 a0 70 38 1f 40 18 10 25 00 99 e6 10 00 00 1a 00 00 00 fc 00 4c 54 4e 31 38 34 48 54 30 32 53 30 31 00 00 00 fe 00 4d 72 2e 20 46 6f 78 27 73 20 6c 63 64 00 b8
PC GAMER likes this.
*** Windows 10 + NVIDIA WHQL Drivers are Killing Alienware and Clevo LCD Panels ***
Discussion in 'Alienware' started by Mr. Fox, Aug 1, 2015.
![[IMG]](images/storyImages/8Ddwyu6.jpg)
![[IMG]](images/storyImages/sARpHQx.jpg)
![[IMG]](images/storyImages/MZRcgdL.jpg)
A sense of humor helps in any situation. It's good to see you haven't lost yours.