MSI MPG 274URDFW E16M Local dimming and haloing issue.

Joined
Mar 7, 2026
Messages
8
I've had this monitor for 1 month now. I updated to the latest firmware as soon as I received it. Till now I was absolutely in love with this monitor. But today when I turned off my PC, the monitor started causing issues. If I am on a dark page and then go to a bright white page, the screen stays dark and takes a few seconds to increase the brightness, And sometimes the LED just stops working a few LED in the middle will be bright and the rest of the LED will be dim, The third picture shows the brightness issue. The same thing happens in gaming as well. The local dimming system is totally messed up for some reason.
And haloing. It started haloing really badly after 10–12 minutes of use. When I power off the monitor and power it on again, it works normally. Then after about 10 minutes it starts haloing again. I have added a second picture of the normal haloing. One of the things I loved about this monitor is that the haloing wasn't noticeable enough to bother me. But it suddenly started haloing really badly. My halo dimming is still at 100. I have added a second photo of normal haloing as a reference.

A couple of troubleshooting steps I did:
  1. 1. Reset monitor settings.
  2. 2. Changed local dimming settings to level 3–1 to see if it still causes issues (it does).
  3. 3. Turned down and up the halo dimming (no change whatsoever. The halo dimming is not working).
  4. 4. Reinstalled the firmware, but still nothing.
  5. 5. Deleted the Windows HDR profile and tried Auto HDR. Still the same.
  6. 6. Turned off Auto HDR and only kept HDR on. Still the same issue.

    1st picture : Bad Haloing.
    2nd picture : What normal Haloing looks like on this monitor.
    3rd picture : Brightness and Led issue.
Does anyone know a way to fix this issue? Should I downgrade, or is there a way to reset the firmware? (Resetting monitor settings from the OSD doesn't fix the issue.) I really love this monitor and would really hate to return it.
 

Attachments

  • WhatsApp Image 2026-03-07 at 7.20.43 PM.jpeg
    WhatsApp Image 2026-03-07 at 7.20.43 PM.jpeg
    46.3 KB · Views: 140
  • WhatsApp Image 2026-03-08 at 5.53.03 AM.jpeg
    WhatsApp Image 2026-03-08 at 5.53.03 AM.jpeg
    37.3 KB · Views: 130
  • WhatsApp Image 2026-03-09 at 6.29.14 PM.jpeg
    WhatsApp Image 2026-03-09 at 6.29.14 PM.jpeg
    113.2 KB · Views: 119
Last edited:
Please modify some below items to OFF in OSD menu for checking.
Night Vision / AI Vision / Adaptive-Sync / HDCR / Local Dimming
 
Please modify some below items to OFF in OSD menu for checking.
Night Vision / AI Vision / Adaptive-Sync / HDCR / Local Dimming
Hi, Night vision /AI vision are off already/HDCR/MPRT are all turned off.

I have tried turning off adaptive-sync. It does not solve the issue.

As for the Local dimming, Yes turning it off solves the issue but then It becomes a normal IPS monitor with IPS glow the LED stays at a constant brightness instead of dimming while gaming/watching content. Of course, there would be some haloing with Local dimming enabled, but till now it wasn't bad when Halo dimming was turned to 100. But the halo dimming setting completely stopped working despite keeping it at 100, it acts as if its 0.

You can check the 2 pictures I've sent. The first one is after 10-20 mins of use, when the issue appears and then 2nd picture is after I turn off/on my monitor when all the settings works normally as it should, it works for a few mins, then the issue starts again. I think it could be a firmware-related bug.


For now, I am using it without local dimming enabled to avoid issues.
 

Attachments

  • 1773021785731.png
    1773021785731.png
    1.3 MB · Views: 80
Update: Turns out my unit had a faulty adapter, which failed to properly deliver the precise voltage needed to brighten or dim the LEDs, which caused the issues mentioned above. I took my monitor to the MSI importer I bought it from, and they gave me a replacement adapter. All the issues are gone now, I am still using the monitor and hoping there wasn't any permanent damage.
 
Last edited:
Back
Top