Odd frequency issue in E-Prime 2 - outputs 144Hz, should be 60Hz.

We have a script which simply displays the refresh rate on screen, which is used to confirm the monitor is capable of doing what we need it to do.

This has been working flawlessly for years, and then earlier this week it doesn't, but we can reasonably confirm, relying on backups, that the script itself has not changed.

The script is configured to run at 60Hz, and will error if it is not greater than 59, or lower than 61.  The monitor the system is connected to can do 60Hz, but will go up to 144Hz.

What we have noticed is that even though Windows is configured for 60Hz, and the script is also configured for 60Hz, it always outputs on screen that the monitor is running at 144Hz, and the script fails if you have the error checking enabled.  I've confirmed this is not cosmetic, as the monitor OSD reports it has switched to 144Hz.

The normal resolution is 1080p, but if I change the experiment to output 1920x1200, the scripts reports 120Hz, so it looks like it is just picking the maximum refresh rate for a given resolution.

I would add that I don't actually use E-Prime 2 myself, just trying to assist someone that does.  For now our workaround is to use a monitor that can only go to 1080p 60Hz, and they are up, and running again.

I have taken the script, and monitor to another desktop, and installed E-Prime 2 there, and get the same effect, even with this different machine, and completely different graphics card, and driver.

So essentially it completely ignores what is configured as the desire frequency in the script.

Does anyone have an idea why this might be?  Thanks for any advice you might give.

Howard