elguavas New User

Comments

  • acer have arranged to courier mine back to a service centre. it's a hassle, and i'm sure it's going to end up costing them more than replacing it, but there you go. hopefully they will fix it. this whole thing has been such a pita.
  • fwiw, the same issue occurs with this monitor in linux and freebsd, and in both of those i've tested with other monitors, including another acer monitor, just as i did under windows but the issue only occurs with this monitor. it's definitely a hardware or firmware issue with this specific monitor.
  • it used to happen on windows 7. since upgrading to windows 10 it still happens. no "drivers" are required for monitors, you are talking about a device capabilities description file that does not act as a driver, the os detects the monitors capabilities via edid in any case and it was/is properly detected in both windows 7…
  • power settings make no difference to this. i've tried everything and nothing makes any difference. it's VERY annoying. i'm going to try returning this under warranty. if i can get my money back i won't buy another acer monitor.
Avatar