AW17 R4 - 4K Screen Design Fault???

Hello all and thankyou for reading my post. @t456 hopefully you can help, you were a gem with the windoze 10 edid mess

I seem to have a complicated problem that may actually be a design flaw in the new Alienware 17 R4 laptop.

I currently have two AW17 R4 laptops.

Laptop 1:

I7 6700HQ

GTX1070M

3840 x 2160 with Tobii

32GB 2133MHz RAM

1 TB SSD & 2TB HDD

Win 10 Pro.


Laptop 2:

i7 7700HQ

GTX 1070M

1920 x 1080p non Tobii

24GB 2667MHz RAM

1TB SSD & 1TB HDD

Win 10 Pro


Laptop 1 was where the problem started.

This is hard to explain so if I sound childish it’s because I don’t want to miss any details.

There is something wrong with the UHD screen.

When you place the mouse cursor to the left of the screen is stops about 2-3mm before the edge/bezel, same on the top of the screen.

When you place the mouse cursor to the right side of screen it disappears underneath the bezel, if you take the bezel off it even disappears underneath the black tape lining the edge of the screen, it also does this at the bottom of the screen.

If the top of screen is north and bottom south it is like the whole PICTURE (NOT SCREEN) needs to move north/west about 3mm INSIDE THE SCREEN. Repositioning the actual screen will not work, it is the picture inside the screen that needs to move.

I ordered two new LCD cables and 2 new UHD screens, I have tried both new screens and cables on laptop 1 but the issue still persists.

I have also completed the following troubleshooting on laptop 1.

1. Full power drain
   
   
2. Different setting in Intel Graphics properties.
   
   
3. Disabled iGPU via function/F5
   
   
4. Tried three different GPU drivers including original Dell GPU drivers
   
   
5. Updated system BIOS to latest (S1.1.7) as it has QMax GPU update
   

None of these steps worked, so then I moved onto laptop 2.

Laptop 2 originally had a 1920 x 1080 screen, this screen worked without any of the issues mentioned above.

When I used one x new cable and new UHD screen on laptop 2 it started with the exact same issue as laptop 1.

So now I have two current AW 17R4’s that have each had two brand new UHD panels and screens fitted and they both present the same problem, but as I mentioned previously, it does not happen with the 1080p screen.

Given the troubleshooting I have completed and the brand new spares I have used I have come to the conclusion there may be a design fault in this model with this configuration.

 

4K cable P/N: 02PVJC
4K LCD panel P/N and brand: 08CJK2, B173ZAN01.0, AU Optronics

 

Sure, it could be an edid bug combined with this specific panel.

Have a few different versions of this panel, but not from that Dell part nr. (08CJK2). Could you copy/paste it using MonInfo or the like?

Something else to consider; the ZAN is an optional gsync model. Does the rest of your system(s) support that? If not (or if you don't care much for gsync) then you can cut pins #34 and #35 on one of the cables and see if that fixes the issue.

Lastly, to rule out a faulty panel (black, backlight-cover tape aligned ok?) it'd be best to run it on a different system. Might be hard to find another 40-pin/4-lane eDP of course, but if you do then it's almost guaranteed to be compatible. Signal-wise that is, not physically; display size is irrelevant.

 

Also isnt the part number for the UHD cable for AW 17 R4 - WTNR3?

IIRC that is also the 40 Pin cable that is used with the 120Hz QHD Gsync panels.

 

Here is info from one of the brand new 4K panels I purchased, I will upload info from original panel shorty.
I have two almost identical system, this screen over run issue affects both, specs for both laptops are in my original post.
Thanks for your help guys.

 

It's been my experience that Dell commonly used more than one part number for the same item with little or no difference between them, I think from memory the part number you have it for a 4K with Tobii, my part number is for a 4K without Tobii.
The cable with Tobii is slightly longer I think.

 

This info is from the original panel issued with laptop number 1 by Dell/Alienware.

 

Yes both systems support gsync, but you can disable that somewhat by switching to dedicated discrete GPU (GTX1070M) only with F5 key combo which disables Intel HD Graphics

 

This is really weird, haven't seen any other 17 r4 owners report this issue. Specially the ones who installed the UHD panel on their own.
And the latest system BIOS is 1.1.8 afaik.
Also MaxQ is a GPU vBios / very system specific thing. I do not think the AW17 falls in that category. Only the specific AW15 R3.

 

It may be they have not realized yet, it would be good to ask one of them to test and see if they experience same issue!

 

It has the same weird, out-of-place Hsync parameter as the other Dell edid. The system should ignore it, but perhaps it won't because the gsync pins on the panel are hooked up. They also have 48 Hz timings, which the stock AUO edids lack. Could try verifying the current refresh rate on Blur Buster's UFO Test.

Apart from cutting the two wires, you could flash one of the stock edids:
AUO109B - B173ZAN01.0 edids, checksum 3B and 3D.7z

Problem is how; it is highly unlikely this modern panel is not write-protected. Have flashed them with a programmer, but these eeproms are puny (TSSOP8) and also contain the non-edid firmware, so you have to be very careful to choose the correct, eeprom-specific write mode in order not to corrupt the existing data.

Remember to check that black felt; it could be a simple manufacturing error on both panels if the machines were mis-aligned at the factory in the same batch. Peel back or scratch a little of the tape from the bottom or right side of the panel and see if the image continuous underneath. If so then fixing it may be tricky since it'll probably be attached pretty firmly and pulling it risks taking the polarizer along with the tape. Best rma then or, if that is not an option, use a heat gun or kerosene.

 

Hiya, that does not sound good.
Please correct me if I'm wrong, cutting the two wires you suggested will disable gsync, is that right?
Does gsync use Nvidia or Intel or both?
If it does not use both I may be able to test either individually. Testing the NVidia by itself is no problem as I can use function &F5 key and enable NVidia GPU only, I can also test the Intel HD by itself with a little screwing around, if this worth trying? Will it make any difference?

I remember Mr Fox purchasing a LCD programming tool during the windoze 10 mess, will this not work to reflash one of the stock EDID's to these panels?

I dont think this is a edge tape issue, the edge tape seems to be of equal width all the way around screen, and yes on the bottom and right of panel the mouse cursor will travel underneath tape, I have peeled it back a little but dont want to take it any further. I dont think this would solve the problem anyway, even if I was able to peel tape back to expose true edge of screen I would then have to reposition the entire LCD panel as cursor would then run underneath bezel, so it really need the image moved inside the panel, moving the actual panel will not work

I noticed in the test results that one panel (The original Dell issue) was original AUO but the other looked to be a rebranded Sanyo with AUO stickers, does this make any difference? I'm just wondering if this fault is in the AUO EDID? Maybe another brand panel would not do it? What are your thoughts?

 

I found this

 

And this

 

Un related.

True, but not sure how its related your case, unless G-Sync not working is also an issue you are facing. But on my Friends AW17 R4, where i replaced his QHD120Hz panel with the UHD , GSync doesnt work, but thats a personal preference thing. Im replacing this FHD panel on my 17 R4 with a UHD later this week, so we will see what happens there.

This happens only if you do not pay attention when purchasing. Most listing cleverly hide the work "compatible". While others which cost a little more, clearly state the brand and model. I havent had this issue a single time buy multiple panels for multiple laptops.
That Line this he is talking about however is an issue with original B173QTN01.0 / 01.1 / 01.2 panels, and has reportedly been fixed in the latest iteration, B173QTN01.4.

 

I'm on a bit of a learning curve so not sure of all the info I have read.
I only mentioned the gsync thing as t456 suggestion cutting two of the pins but said gsync would not work. I don't actually think it works on these panels anyway, from what I have read the gsync option should be in Nvidia control panel and I don't see it there, I've read the AW 17 R4 is capable of gsync but I don't seem to have that option, even when using the original Dell 4K panel.

 

UFOTest from original Dell 4K panel.

 

Hi,
I also have two AW17. When I do the test, I have the same problem as you, on my two 4k screens. ( They are original Dell screens )

1 AUO109B Data string. 8CJK2€B173ZAN RGB 4:4:4


2) SHP1446 Data string. CK7T7€LQ173D1 RGB 4:4:4, YCrCb 4:4:4

FIRST :

Monitor Manufacturer............. AUO Plug and Play ID......... AUO109B Data string.............. 8CJK2€B173ZAN [*CP437] Serial number............ n/a Manufacture date......... 2015, ISO week 0 Filter driver............ None

EDID revision............ 1.4 Input signal type........ Digital (DisplayPort) Color bit depth.......... 8 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................... Not supported

Color characteristics Default color space...... Non-sRGB Display gamma............ 2,20 Red chromaticity......... Rx 0,656 - Ry 0,314 Green chromaticity....... Gx 0,212 - Gy 0,711 Blue chromaticity........ Bx 0,148 - By 0,057 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.. 3840x2160p at 60Hz Modeline............... "3840x2160" 533,500 3840 3888 3920 4000 2160 2163 2168 2222 +hsync -vsync Detailed timing #1....... 3840x2160p at 48Hz Modeline............... "3840x2160" 426,800 3840 3888 3920 4000 2160 2163 2168 2222 +hsync -vsync

Standard timings supported

Report information Date generated........... 2017-07-14 Software revision........ 2.90.0.1020 Data source.............. Real-time 0x0100 Operating system......... 10.0.15063.2

SECOND:

onitor Windows description...... Generic PnP Monitor Manufacturer............. Sharp Plug and Play ID......... SHP1446 Data string.............. CK7T7€LQ173D1 [*CP437] Serial number............ n/a Manufacture date......... 2015, ISO week 34 Filter driver............ None

EDID revision............ 1.4 Input signal type........ Digital (DisplayPort) Color bit depth.......... 8 bits per primary color Color encoding formats... RGB 4:4:4, YCrCb 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...... sRGB Display gamma............ 2,20 Red chromaticity......... Rx 0,640 - Ry 0,329 Green chromaticity....... Gx 0,210 - Gy 0,710 Blue chromaticity........ Bx 0,149 - By 0,060 White point (default).... Wx 0,313 - Wy 0,328 Additional descriptors... None

Timing characteristics Range limits............. Not available GTF standard............. Not supported Additional descriptors... None Preferred timing......... Yes Native/preferred timing.. 3840x2160p at 60Hz (16:9) Modeline............... "3840x2160" 533,250 3840 3888 3920 4000 2160 2163 2168 2222 -hsync -vsync Detailed timing #1....... 3840x2160p at 48Hz Modeline............... "3840x2160" 426,600 3840 3888 3920 4000 2160 2163 2168 2222 -hsync -vsync

Standard timings supported

Report information Date generated........... 2017-07-14 Software revision........ 2.90.0.1020 Data source.............. Registry Operating system......... 10.0.15063.2

 

Hi 123eureka, that's definitely not a good sign.
I'm getting a feeling we might be the tip of the iceberg.

 

Most definitely a big issue if its common and people havent realized it yet, will either of you guys be able to make a video showing this problem?

 

Yes, but you don't have that now so it doesn't matter. The 4k ZAN cannot do much more than +10% anyway and you can always reconnect/-solder the two wires if you like. These pins are optional by design (eDP standard) and will not break display output on any system.

Unlikely, since these cannot disable the physical, chip-side of the write-protect. Needs some soldering to fix that before you can flash.

Would guess both panels will do fine on a non-R4 system, but only one way to make that definitive.

Could you upload the moninfo.txt dump, same as andrewsi2012 has done?

That Sharp doesn't have the weird hsync option, but it also has a 48 Hz timing, same as both Dell versions of the AUO.

 

I can confirm this over the weekend, will test out both my UHD panels in the R4.

 

Spoiler: SHARP.txt

Monitor Asset Manager Report, generated 2017-07-20
Copyright (c) 1995-2016, EnTech Taiwan.
---------------------------

Monitor #1 [Real-time 0x0100]
Manufacturer............. Sharp
Plug and Play ID......... SHP1446
Data string.............. CK7T7€LQ173D1 [*CP437]
Serial number............ n/a
Manufacture date......... 2015, ISO week 34
Filter driver............ None
-------------------------
EDID revision............ 1.4
Input signal type........ Digital (DisplayPort)
Color bit depth.......... 8 bits per primary color
Color encoding formats... RGB 4:4:4, YCrCb 4:4:4
Screen size.............. 380 x 210 mm (17,1 in)
Power management......... Not supported
Extension blocs.......... None
-------------------------
DDC/CI................... Not supported

Color characteristics
Default color space...... sRGB
Display gamma............ 2,20
Red chromaticity......... Rx 0,640 - Ry 0,329
Green chromaticity....... Gx 0,210 - Gy 0,710
Blue chromaticity........ Bx 0,149 - By 0,060
White point (default).... Wx 0,313 - Wy 0,328
Additional descriptors... None

Timing characteristics
Range limits............. Not available
GTF standard............. Not supported
Additional descriptors... None
Preferred timing......... Yes
Native/preferred timing.. 3840x2160p at 60Hz (16:9)
Modeline............... "3840x2160" 533,250 3840 3888 3920 4000 2160 2163 2168 2222 -hsync -vsync
Detailed timing #1....... 3840x2160p at 48Hz
Modeline............... "3840x2160" 426,600 3840 3888 3920 4000 2160 2163 2168 2222 -hsync -vsync

Standard timings supported

Report information
Date generated........... 2017-07-20
Software revision........ 2.90.0.1020
Data source.............. Real-time 0x0100
Operating system......... 10.0.15063.2

Raw data
00,FF,FF,FF,FF,FF,FF,00,4D,10,46,14,00,00,00,00,22,19,01,04,A5,26,15,78,0E,DF,50,A3,54,35,B5,26,
0F,50,54,00,00,00,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,4D,D0,00,A0,F0,70,3E,80,30,20,
35,00,7E,D7,10,00,00,18,A4,A6,00,A0,F0,70,3E,80,30,20,35,00,81,D7,10,00,00,18,00,00,00,FE,00,43,
4B,37,54,37,80,4C,51,31,37,33,44,31,00,00,00,00,00,02,41,03,28,00,12,00,00,0B,01,0A,20,20,00,75

---------------------------

Hardware data
BUS_SLOT = PCI00000.PCI00004.PCI00008.PCI0000C.PCI00010.PCI00014.PCI00018.PCI0001C
00000000 = 59108086.20900006.06000005.00000000.00000000.00000000.00000000.00000000
00000008 = 19018086.00100407.06040005.00810010.00000000.00000000.00010100.0000E0E0
00000010 = 591B8086.00100400.03800004.00000010.DE000004.00000000.7000000C.00000000
00000020 = 19038086.00900006.11800005.00000000.FE028004.00000000.00000000.00000000
000000A0 = A12F8086.02900406.0C033031.00800000.DD190004.00000000.00000000.00000000
000000A2 = A1318086.00100002.11800031.00000000.DD1BB004.00000000.00000000.00000000
000000B0 = A13A8086.00100406.07800031.00800000.FE03C004.00000000.00000000.00000000
000000B8 = 28228086.02B00407.01040031.00000000.DD1A0000.DD1B9000.0000F091.0000F081
000000E0 = A1108086.00100404.060400F1.00810010.00000000.00000000.003B3B00.200000F0
000000E4 = A1148086.00100407.060400F1.00810010.00000000.00000000.003C3C00.2000D0D0
000000E5 = A1158086.00100406.060400F1.00810010.00000000.00000000.003D3D00.200000F0
000000F8 = A1548086.02000007.06010031.00800000.00000000.00000000.00000000.00000000
000000FA = A1218086.00000000.05800031.00800000.DD1B4000.00000000.00000000.00000000
000000FB = A1718086.00100006.04030031.00002010.FE030004.00000000.00000000.00000000
000000FC = A1238086.02800003.0C050031.00000000.DD1B8004.00000000.00000000.00000000
00000100 = 1BA110DE.00100407.030000A1.00000010.DC000000.B000000C.00000000.C000000C
00003C00 = E0B11969.00100007.02000010.00000010.DD400004.00000000.0000D001.00000000
00003D00 = 003E168C.00100546.02800032.00000010.DD200004.00000000.00000000.00000000
--------

Spoiler: AUO.txt

Monitor Asset Manager Report, generated 2017-07-20
Copyright (c) 1995-2016, EnTech Taiwan.
---------------------------

Monitor #1 [Real-time 0x0100]
Manufacturer............. AUO
Plug and Play ID......... AUO109B
Data string.............. 8CJK2€B173ZAN [*CP437]
Serial number............ n/a
Manufacture date......... 2015, ISO week 0
Filter driver............ None
-------------------------
EDID revision............ 1.4
Input signal type........ Digital (DisplayPort)
Color bit depth.......... 8 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................... Not supported

Color characteristics
Default color space...... Non-sRGB
Display gamma............ 2,20
Red chromaticity......... Rx 0,656 - Ry 0,314
Green chromaticity....... Gx 0,212 - Gy 0,711
Blue chromaticity........ Bx 0,148 - By 0,057
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.. 3840x2160p at 60Hz
Modeline............... "3840x2160" 533,500 3840 3888 3920 4000 2160 2163 2168 2222 +hsync -vsync
Detailed timing #1....... 3840x2160p at 48Hz
Modeline............... "3840x2160" 426,800 3840 3888 3920 4000 2160 2163 2168 2222 +hsync -vsync

Standard timings supported

Report information
Date generated........... 2017-07-20
Software revision........ 2.90.0.1020
Data source.............. Real-time 0x0100
Operating system......... 10.0.15063.2

Raw data
00,FF,FF,FF,FF,FF,FF,00,06,AF,9B,10,00,00,00,00,00,19,01,04,A5,26,15,78,02,24,25,A8,50,36,B6,26,
0E,50,54,00,00,00,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,66,D0,00,A0,F0,70,3E,80,30,20,
35,00,7E,D6,10,00,00,1A,B8,A6,00,A0,F0,70,3E,80,30,20,35,00,7E,D6,10,00,00,1A,00,00,00,FE,00,38,
43,4A,4B,32,80,42,31,37,33,5A,41,4E,00,00,00,00,00,02,41,01,A8,00,11,00,00,0B,01,0A,20,20,00,2A

---------------------------

Hardware data
BUS_SLOT = PCI00000.PCI00004.PCI00008.PCI0000C.PCI00010.PCI00014.PCI00018.PCI0001C
00000000 = 59108086.20900006.06000005.00000000.00000000.00000000.00000000.00000000
00000008 = 19018086.00100407.06040005.00810010.00000000.00000000.00010100.0000E0E0
00000010 = 591B8086.00100400.03800004.00000010.DE000004.00000000.7000000C.00000000
00000020 = 19038086.00900006.11800005.00000000.FE028004.00000000.00000000.00000000
000000A0 = A12F8086.02900406.0C033031.00800000.DD110004.00000000.00000000.00000000
000000A2 = A1318086.00100002.11800031.00000000.DD136004.00000000.00000000.00000000
000000B0 = A13A8086.00100406.07800031.00800000.FE03C004.00000000.00000000.00000000
000000B8 = A1028086.02B00407.01060131.00000000.DD130000.DD134000.0000F091.0000F081
000000E0 = A1108086.00100404.060400F1.00810010.00000000.00000000.003B3B00.200000F0
000000E4 = A1148086.00100407.060400F1.00810010.00000000.00000000.003C3C00.2000D0D0
000000E5 = A1158086.00100406.060400F1.00810010.00000000.00000000.003D3D00.200000F0
000000E8 = A1188086.00100406.060400F1.00810010.00000000.00000000.003E3E00.200000F0
000000F8 = A1548086.02000007.06010031.00800000.00000000.00000000.00000000.00000000
000000FA = A1218086.00000000.05800031.00800000.DD12C000.00000000.00000000.00000000
000000FB = A1718086.00100006.04030031.00002010.FE030004.00000000.00000000.00000000
000000FC = A1238086.02800003.0C050031.00000000.DD132004.00000000.00000000.00000000
00000100 = 1BA110DE.00100407.030000A1.00000010.DC000000.B000000C.00000000.C000000C
00003C00 = E0B11969.00100007.02000010.00000010.DD500004.00000000.0000D001.00000000
00003D00 = 003E168C.00100546.02800032.00000010.DD200004.00000000.00000000.00000000
00003E00 = A804144D.00100406.01080200.00000010.DD400004.00000000.00000000.00000000
--------

 

Just copy paste the text and use a spoiler.

 

Thanks for the edid. Only thing is again the power/bandwidth-saving 48 Hz mode. This should kick in when hooking up a high-res external monitor that needs more bandwidth than the DP or HDMI port can handle (or if power-saving in enabled in Intel HD).

Could check both 4K models on my 13.3" Clevo (it has 4-lane eDP out and use a 40-pin cable atm), but that wouldn't be very practical with shipping and all. Try to find some 3k/4k systems you may be able to borrow and we can check whether these can run the AUO or Sharp.

For research, flashed an edid to my 2560x1440 panel with a different, reduced blanking interval; it now has to opposite problem of the AUO and Sharp; the image is off-set to the top-left of the screen. Double-checked the 48 Hz values again and these are clearly wrong on both the Dell AUOs and the Sharp. With the lower refresh rate the vertical blanking interval should've been reduced as well, but it's been copy/pasted from the 60 Hz and thereby off by 13 lines (62 vs. 49). That would explain the offset to the bottom-right, but only if the display were running at 48 Hz, so ... still odd.

Try hooking up an old, pure 60 Hz monitor over DP or HDMI and see if that fixes things by forcing 60 Hz, also making sure it's hookup up before boot ( W10's hibernate mode had to be turned off). That's also something else to consider; make a separate W7 or Linux install. With W10 you can expect all kinds of exotic hardware issues.

 

Here is the data from the 4k AUO in my DM1 -

Spoiler: B173ZAN01.0

Monitor
Manufacturer............. AUO
Plug and Play ID......... AUO109B
Data string.............. B173ZAN01.0
Serial number............ n/a
Manufacture date......... 2015, ISO week 0
Filter driver............ None
-------------------------
EDID revision............ 1.4
Input signal type........ Digital (DisplayPort)
Color bit depth.......... 8 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................... Not supported

Color characteristics
Default color space...... Non-sRGB
Display gamma............ 2.20
Red chromaticity......... Rx 0.656 - Ry 0.314
Green chromaticity....... Gx 0.212 - Gy 0.711
Blue chromaticity........ Bx 0.148 - By 0.057
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.. 3840x2160p at 60Hz
Modeline............... "3840x2160" 533.500 3840 3888 3920 4000 2160 2163 2168 2222 -hsync -vsync

Standard timings supported

Report information
Date generated........... 7/21/2017
Software revision........ 2.90.0.1020
Data source.............. Real-time 0x0100
Operating system......... 10.0.14393.2

Raw data
00,FF,FF,FF,FF,FF,FF,00,06,AF,9B,10,00,00,00,00,00,19,01,04,A5,26,15,78,02,24,25,A8,50,36,B6,26,
0E,50,54,00,00,00,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,66,D0,00,A0,F0,70,3E,80,30,20,
35,00,7E,D6,10,00,00,18,00,00,00,0F,00,00,00,00,00,00,00,00,00,00,00,00,00,20,00,00,00,FE,00,41,
55,4F,0A,20,20,20,20,20,20,20,20,20,00,00,00,FE,00,42,31,37,33,5A,41,4E,30,31,2E,30,20,0A,00,3B

 

Yes, that is a stock AUO edid (checksum = last bytes = 3B). If that version (and the 3D checksum variety) run fine on the R4 then the issue is with the buggy 48 Hz timing on the Dell edids. If it suffers the same fault then look into cutting those two gsync wires on the eDP cable. Mind that there may be different revisions of the R4's cable; one that has #34 and #35 populated and one that simple lacks those wires altogether.

 

Ill test my AUO's on the R4 tonight or tomorrow.

 

https://www.facebook.com/video.php?v=1236798686431658

 

Great. Progress.

So if you have the same problem there is a chance we can fix this with cutting a couple of pins?

 

Cutting or blocking either MIGHT work. Not sure though.

 

@t456 @andrewsi2012 @123eureka

Just finished testing 2 of my 4k Panels from both my Clevo's. And my R4 doesnt have this issue.
I test 2 AW 17 R4 motherboards - 1. 7700HQ / GTX 1060 and 2. 6820HK / GTX 1080.
On both of them the edges are perfectly within the bezel/limits.

The 6820HK board has the 1.0.12 Bios initially, and the 7700HQ board had the 1.1.6 Bios. No issues with these version.
Updated to 1.1.8 (latest) and similar results.

 

Interesting, so looks like yours are OK. They are AUO like mine but your have a different revision number is that right? What part number is on your cable?
@123eureka do you have the part number for your LCD cable too?

 

02PVJC
And im not sure about the revision number. Just that my Panels did not come from Dell or Clevo, i bought then directly from China. So literally bone stock / factory EDID/Firmware.

 

I have the same exact issue on my 4K screen. Courser goes under the bezel on the right, stops exactly where the bezel begins on the left, dissapears on the bottom and stops on the top at the bezel.

 

Try do the test again on a white background. Consider the top left corner of the mouse cursor as the "tip."

When you move the mouse cursor as far right as it will go, on the right hand side of the screen all you should be able to see is the left flat side of the mouse cursor which will look like vertical black line (the width of one pixel).

When you move the mouse cursor down as far as it will go, at the bottom of the screen all you should be able to see is the top tip of the mouse cursor which will look like a single black pixel.

 

Gotcha, doing test now.

 

It is going to take 45minutes to upload video, my internet connection speed is terrible.

But I'll write a quick report back now.
Bottom and right side of screen do exactly what Namaiki said they should do. Cursor turns to single line on right side of screen and single dot at bottom of screen.
On left and top of screen it does not even reach the "Edge" of screen.

 

I have three panels, one Dell original and two directly from China (Brand new).
Any chance you could check the revision number on yours to see if they are different?

 

Here is the MonInfo output from the more recent panel -

These are the 2 -
http://i.imgur.com/iH4XpKd.jpg
http://i.imgur.com/qZecmFY.jpg

 

@bloodhawk

Looks like yours is B173ZAN01.0
and my three are B173ZAN01.1

Can you run Moninfo please and upload results!

 

Ah. That would somewhat explain it.
I remember 01.1 having issues with Clevos as well, because of which when I was ordering my second panel I totally dodged it.

 

https://www.facebook.com/video.php?v=1241543712623822

 

@bloodhawk
can you please confirm that you have a Alienware 17 R4 with the "01.0" revision panel and that it works without this screen edge issue.
Thanks.

 

Not sure how i can confirm that, but here you go -

http://imgur.com/a/6A3Th

 

The panel revision number is in the moninfo report, can you possibly run moninfo on the AW 17 R4?

 

@bloodhawk
Thanks in advance, I have to crash, I think I'm getting the flu.
I'll catchup with you tomorrow.
Thanks again @bloodhawk.

 

Its the the exact same panel as in Mon Info report from a few posts back, so not sure how it will help you, since everything will be EXACTLY the same, but here you go -

 

idk what moninfo is buts its a B173ZAN01.0