invalid displayframethresholdstimdisplay value Error: 11076

[Katie Young]

Has anyone else encountered this error (see image below for full message)? It happens everytime I run a task, seems to relate to display settings, but changing the refresh rate settings has no effect. I'm struggling to find any reference to this specific error online and wondering if anyone had thoughts about what it refers to?

I'm trying to run tasks on a Windows 10 computer, EPrime version 2.0.10.356 - the tasks all previously worked on a Windows 7 computer, and also functions on a version of windows 10 installed on a mac laptop through bootcamp!

Any thoughts would be much appreciated!

[David McFarlane]

Please see https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_topic_e-2Dprime_gmyo1FUBudE_&d=DwICaQ&c=nE__W8dFE-shTxStwXtp0A&r=G5rE14iEroXBmo5-NBEH68hGd8Mb0XSkrpl4X12tf70&m=qCAbrG5piOQ8d2D0Touswxgms8QiVN_FD6jIaJGJLuA&s=8xaSP2gRG76zoIM0SV6p09uT6rD0tD0r5NxFMUeTiiw&e= and
the notice at the PST Produce Service and Support page,
https://urldefense.proofpoint.com/v2/url?u=https-3A__support.pstnet.com_hc_en-2Dus&d=DwICaQ&c=nE__W8dFE-shTxStwXtp0A&r=G5rE14iEroXBmo5-NBEH68hGd8Mb0XSkrpl4X12tf70&m=qCAbrG5piOQ8d2D0Touswxgms8QiVN_FD6jIaJGJLuA&s=u2vZpBKfOwWWaoRTejX4Bff30T4RbhLdqNec-kpik3Y&e= , in case any of that applies here.

Beyond that, please submit this to PST Support.

-- David McFarlane

[David McFarlane]

Sorry, our campus has just implemented a new e-mail protection system
that mangles URLs in messages -- I thought it did that only for incoming
messages, but it seems it also does that for outgoing messages, sigh.
So here are those links again, slightly redacted to evade the URL
mangler, just manually replace "[dot]" with "." then copy & paste. Sheesh.

groups[dot]google[dot]com/d/topic/e-prime/gmyo1FUBudE/
support[dot]pstnet[dot]com/hc/en-us

-- David McFarlane

[Katie Young]

Many thanks for the response David - we looked into this, but turns out we hadn't upgraded to the affected version.

We did some further testing and discovered yesterday it was a conflict arising any time two display devices were corrected (this was an MRI setting and we have both goggles and projector display options available). The issue was resolved  by ensuring only one piece of equipment was turned on at a time & updating the display settings through Control Panel > Display > Screen Resolution > Detect, to ensure only one device was recognised at a time (in case anyone else runs into the same problem!)