Blur Busters Forums

BLooDS_inc wrote: ↑

02 Jul 2026, 02:07

On the Msi monitor sleep bug going out, now pulsar working after sleeps well, but borderless bug in pubg stays here, when u get 2 monitors, and u set borderless mode ingame, pulsar stops working and monitor osd shows 144 fps(my 2nd monitor hz cap) instead of 342 that stays ingame(342 rtss cap), and gsync stops working too.

Trying the 60hz and 120hz modes, on 60hz in 10 width(the minimum u can set) flicker is very minor and u can use it, on 120 hz i don t see any flickering at all.
And now the GENERAL problem of this modes - if u use pulsar with 360hz ingame, and u wanna set 60 or 120hz modes, u cant do this fast, u need to change hz of monitor, turn off gsync, its so annoying idk, every time doing this, if u can get some BUTTON in nvidia APP that 1click turn on 60hz ulmb2 or 120hz ulmb2 and reverse 1click turn 360hz PULSAR it will be so good, but now, i dont wanna every time go in to the settings and set this changes over and over

WiZZard46 wrote: ↑

18 Jul 2026, 15:47

I like this a lot. I'd make just a few changes to improve readability and make it sound a bit more natural to an audience of technically minded people. I also removed one or two repeated ideas and slightly softened the wording so it invites discussion rather than sounding like a bug report.

Hi everyone,

I'm hoping someone here might have an idea because I've been investigating this issue for almost two months, and at this point I'm honestly running out of things to test.

My monitor is an ASUS ROG Strix Pulsar XG27AQNGV, still running the factory firmware MCM101.

The monitor itself works perfectly (360 Hz, G-SYNC Pulsar, HDR, etc.), but I cannot update the firmware using NVIDIA's official G-SYNC Pulsar Firmware Updater. As soon as I click "Allow browser to connect", it immediately reports:

"No compatible devices found."

So far I've ruled out pretty much every user-side variable I can think of:

Two different Windows 11 PCs
Two different NVIDIA GPUs
Google Chrome and Microsoft Edge
The original ASUS USB 3.0 Type-B upstream cable
A second brand-new USB 3.0 Type-B cable
Multiple motherboard USB ports/controllers
Linux Mint Live USB (same behavior as Windows)

The most interesting discovery came after comparing my monitor with another XG27AQNGV owner (huge thanks to @rexbinary for taking the time to help).

Immediately after entering Firmware Update Mode:

His monitor:

Enumerates as ASUS XG27AQNGV
VID 0B05 / PID 1D67
Exposes a DFU (Device Firmware Upgrade) interface

My monitor:

Remains ROG Gaming Display Aura Device
VID 0B05 / PID 1C2C
Never exposes the DFU interface

Even under Linux Mint, the monitor still enumerates as VID 0B05 / PID 1C2C, which makes me believe this isn't related to Windows, browser permissions, drivers, or WebUSB.

From everything I've observed, it looks like my monitor never actually re-enumerates into DFU mode, even though the OSD clearly displays "Firmware Update Mode." If that's the case, it would also explain why the NVIDIA updater immediately reports "No compatible devices found."

I already have an engineering escalation open with ASUS, but it's been almost two months and I'm still waiting for their response.

One thing that has also confused me is NVIDIA's firmware update page, which mentions using a Micro-B USB cable. The XG27AQNGV, however, uses a USB 3.0 Type-B upstream connection for normal PC connectivity and also has a separate connector labeled "For service only." Since ASUS doesn't document that connector as a user firmware update port, I've intentionally avoided using it until I receive clarification from their engineering team.

So I have a couple of questions for anyone who owns this monitor:

Has anyone with an XG27AQNGV successfully updated the firmware? If so, which physical USB connection did you use—the standard USB 3.0 Type-B upstream port, or the separate "For service only" connector?
Has anyone ever seen an XG27AQNGV remain VID 0B05 / PID 1C2C in Firmware Update Mode instead of switching to VID 0B05 / PID 1D67 (DFU)?

At this point, I'm simply trying to determine whether I'm dealing with a firmware issue, a hardware issue, or perhaps an early production revision that behaves differently.

Any ideas, experiences, or suggestions would be greatly appreciated.

Thanks in advance!

kevsei wrote: ↑

19 Jul 2026, 08:47

BLooDS_inc wrote: ↑

02 Jul 2026, 02:07

On the Msi monitor sleep bug going out, now pulsar working after sleeps well, but borderless bug in pubg stays here, when u get 2 monitors, and u set borderless mode ingame, pulsar stops working and monitor osd shows 144 fps(my 2nd monitor hz cap) instead of 342 that stays ingame(342 rtss cap), and gsync stops working too.

Trying the 60hz and 120hz modes, on 60hz in 10 width(the minimum u can set) flicker is very minor and u can use it, on 120 hz i don t see any flickering at all.
And now the GENERAL problem of this modes - if u use pulsar with 360hz ingame, and u wanna set 60 or 120hz modes, u cant do this fast, u need to change hz of monitor, turn off gsync, its so annoying idk, every time doing this, if u can get some BUTTON in nvidia APP that 1click turn on 60hz ulmb2 or 120hz ulmb2 and reverse 1click turn 360hz PULSAR it will be so good, but now, i dont wanna every time go in to the settings and set this changes over and over

Hey, I had the same problem. Try switching the ports on your graphics card (switch all DP-Ports on your GPU). It seems like one port is preferred for G-Sync.

WiZZard46 wrote: ↑

Yesterday, 10:54

Hello, @liquidshadowfox!

I just found this out after busting my nuts for months trying to update. Thank you for confirming it to me. Got a Ugreen cable and the update went through like a charm.