Millisecond Forums

+x

 

Toni Mo - 7/4/2023

Hi,

We run a total of 3 tasks during data collection for our lab sessions - Emotional Stroop task, Colour-word Strook task and SART. On a number of occasions, we have had the Inquisit program crash during one of the task. It happens to be the same task each time and the crash does not occur every time the program is run. Here is a copy of the code received when the program crashes during the task:

Checking system capabilities...
Timer resolution: 0.0001000000000000000 milliseconds
Display: 0: \\.\DISPLAY1
Color resolution: 32 bits per pixel
Display mode: 1920 x 1080
Refresh Rate: 60 Hz
Videosync support: DXGIWaitForVBlankMode.
Building Experiment...
Extracting elements from C:/Users/fran/Desktop/MRC Study 1 Tasks/stroopwithcontrolkeyboard.iqx...
Parsing elements...
<htmlpage intro3>
<defaults>
<htmlpage intro4>
<text yellowincongruent>
<data>
<text x>
<trial redcongruent>
<list latencies>
<trial redincongruent>
<text greencontrol>
<computer>
<block finish>
<text greenincongruent>
<trial bluecongruent>
<list responses_congruent>
<list responses_incongruent>
<trial bluecontrol>
<monkey>
<text redreminder>
<htmlpage intro1>
<trial redcontrol>
<text redincongruent>
<trial blueincongruent>
<mouse>
<clearscreen>
<trial getReady>
<text bluecongruent>
<text getReady>
<text redcongruent>
<trial greenincongruent>
<expressions>
<values>
<systembeep>
<joystick>
<summarydata>
<text fixation>
<text summaryFeedback>
<text bluereminder>
<trial yellowcongruent>
<display>
<text bluecontrol>
<text finish>
<text greencongruent>
<trial yellowcontrol>
<trial yellowincongruent>
<list latencies_incongruent>
<text yellowcongruent>
<script>
<expt 1>
<trial finish>
<inquisit>
<list latencies_control>
<list latencies_congruent>
<list responses>
<block stroop>
<parameters>
<trial greencongruent>
<text greenreminder>
<text yellowreminder>
<text exit>
<text yellowcontrol>
<clearscreen monitor2>
<text target>
<text redcontrol>
<text ready>
<htmlpage intro2>
<instruct>
<list responses_control>
<trial greencontrol>
<text blueincongruent>
Results...
WARNING: OpenGL Invalid State - Sanity Check.. Function bool __cdecl inquisit::Graphics::MonitorInfo::makeCurrent(void), File Graphics.cpp, Line 401 GL Error Codes: GL_INVALID_FRAMEBUFFER_OPERATION: GL_FRAMEBUFFER: GL_FRAMEBUFFER_COMPLETE: Framebuffer Complete. GL_READ_FRAMEBUFFER_ANGLE:GL_FRAMEBUFFER_COMPLETE: Framebuffer Complete.
ERROR: OpenGL Error: IQOpenGLFramebufferObject. OpenGL Error: GL_INVALID_FRAMEBUFFER_OPERATION. blitFramebuffer File: C:\inquisit6\IQRuntime\qt\IQOpenGLFramebufferObject.cpp:1927
ERROR: OpenGL Error: IQOpenGLFramebufferObject. OpenGL Error: GL_INVALID_FRAMEBUFFER_OPERATION. blitFramebuffer File: C:\inquisit6\IQRuntime\qt\IQOpenGLFramebufferObject.cpp:1944
Data file: C:/Users/fran/Desktop/MRC Study 1 Tasks/data/stroopwithcontrolkeyboard_raw_TEST,1012_2023-07-04-09-13-24-511.iqdat
Data file: C:/Users/fran/Desktop/MRC Study 1 Tasks/data/stroopwithcontrolkeyboard_summary_TEST,1012_2023-07-04-09-13-24-511.iqdat


I have validated the scripts and did a Monkey Test run but both produced no issues with the code. This is what the screen looks like after the crash:



We do not understand why this keeps happening and we hope you are able to provide a solution to this issue, or point us in the right direction.

Many thanks,

Toni

+x

 

Dave - 7/4/2023

+x

 

Toni Mo - 7/4/2023

Hi,

We run a total of 3 tasks during data collection for our lab sessions - Emotional Stroop task, Colour-word Strook task and SART. On a number of occasions, we have had the Inquisit program crash during one of the task. It happens to be the same task each time and the crash does not occur every time the program is run. Here is a copy of the code received when the program crashes during the task:

Checking system capabilities...
Timer resolution: 0.0001000000000000000 milliseconds
Display: 0: \\.\DISPLAY1
Color resolution: 32 bits per pixel
Display mode: 1920 x 1080
Refresh Rate: 60 Hz
Videosync support: DXGIWaitForVBlankMode.
Building Experiment...
Extracting elements from C:/Users/fran/Desktop/MRC Study 1 Tasks/stroopwithcontrolkeyboard.iqx...
Parsing elements...
<htmlpage intro3>
<defaults>
<htmlpage intro4>
<text yellowincongruent>
<data>
<text x>
<trial redcongruent>
<list latencies>
<trial redincongruent>
<text greencontrol>
<computer>
<block finish>
<text greenincongruent>
<trial bluecongruent>
<list responses_congruent>
<list responses_incongruent>
<trial bluecontrol>
<monkey>
<text redreminder>
<htmlpage intro1>
<trial redcontrol>
<text redincongruent>
<trial blueincongruent>
<mouse>
<clearscreen>
<trial getReady>
<text bluecongruent>
<text getReady>
<text redcongruent>
<trial greenincongruent>
<expressions>
<values>
<systembeep>
<joystick>
<summarydata>
<text fixation>
<text summaryFeedback>
<text bluereminder>
<trial yellowcongruent>
<display>
<text bluecontrol>
<text finish>
<text greencongruent>
<trial yellowcontrol>
<trial yellowincongruent>
<list latencies_incongruent>
<text yellowcongruent>
<script>
<expt 1>
<trial finish>
<inquisit>
<list latencies_control>
<list latencies_congruent>
<list responses>
<block stroop>
<parameters>
<trial greencongruent>
<text greenreminder>
<text yellowreminder>
<text exit>
<text yellowcontrol>
<clearscreen monitor2>
<text target>
<text redcontrol>
<text ready>
<htmlpage intro2>
<instruct>
<list responses_control>
<trial greencontrol>
<text blueincongruent>
Results...
WARNING: OpenGL Invalid State - Sanity Check.. Function bool __cdecl inquisit::Graphics::MonitorInfo::makeCurrent(void), File Graphics.cpp, Line 401 GL Error Codes: GL_INVALID_FRAMEBUFFER_OPERATION: GL_FRAMEBUFFER: GL_FRAMEBUFFER_COMPLETE: Framebuffer Complete. GL_READ_FRAMEBUFFER_ANGLE:GL_FRAMEBUFFER_COMPLETE: Framebuffer Complete.
ERROR: OpenGL Error: IQOpenGLFramebufferObject. OpenGL Error: GL_INVALID_FRAMEBUFFER_OPERATION. blitFramebuffer File: C:\inquisit6\IQRuntime\qt\IQOpenGLFramebufferObject.cpp:1927
ERROR: OpenGL Error: IQOpenGLFramebufferObject. OpenGL Error: GL_INVALID_FRAMEBUFFER_OPERATION. blitFramebuffer File: C:\inquisit6\IQRuntime\qt\IQOpenGLFramebufferObject.cpp:1944
Data file: C:/Users/fran/Desktop/MRC Study 1 Tasks/data/stroopwithcontrolkeyboard_raw_TEST,1012_2023-07-04-09-13-24-511.iqdat
Data file: C:/Users/fran/Desktop/MRC Study 1 Tasks/data/stroopwithcontrolkeyboard_summary_TEST,1012_2023-07-04-09-13-24-511.iqdat


I have validated the scripts and did a Monkey Test run but both produced no issues with the code. This is what the screen looks like after the crash:



We do not understand why this keeps happening and we hope you are able to provide a solution to this issue, or point us in the right direction.

Many thanks,

Toni

The error indicates a problem with the respective system's graphics card or driver. Typically, this is caused by graphics memory fragmentation due to lack of available graphics memory and/or an outdated or malfunctioning graphics card driver.

You should:
(1) Make sure you have the latest Inquisit Lab version installed on the system, i.e. version 6.6.1 as available at https://www.millisecond.com/download .
(2) Obtain and install the latest graphics card driver available from the device's manufacturer.

+x

 

Toni Mo - 7/4/2023

+x

 

Dave - 7/4/2023

+x

 

Toni Mo - 7/4/2023

Hi,

We run a total of 3 tasks during data collection for our lab sessions - Emotional Stroop task, Colour-word Strook task and SART. On a number of occasions, we have had the Inquisit program crash during one of the task. It happens to be the same task each time and the crash does not occur every time the program is run. Here is a copy of the code received when the program crashes during the task:

Checking system capabilities...
Timer resolution: 0.0001000000000000000 milliseconds
Display: 0: \\.\DISPLAY1
Color resolution: 32 bits per pixel
Display mode: 1920 x 1080
Refresh Rate: 60 Hz
Videosync support: DXGIWaitForVBlankMode.
Building Experiment...
Extracting elements from C:/Users/fran/Desktop/MRC Study 1 Tasks/stroopwithcontrolkeyboard.iqx...
Parsing elements...
<htmlpage intro3>
<defaults>
<htmlpage intro4>
<text yellowincongruent>
<data>
<text x>
<trial redcongruent>
<list latencies>
<trial redincongruent>
<text greencontrol>
<computer>
<block finish>
<text greenincongruent>
<trial bluecongruent>
<list responses_congruent>
<list responses_incongruent>
<trial bluecontrol>
<monkey>
<text redreminder>
<htmlpage intro1>
<trial redcontrol>
<text redincongruent>
<trial blueincongruent>
<mouse>
<clearscreen>
<trial getReady>
<text bluecongruent>
<text getReady>
<text redcongruent>
<trial greenincongruent>
<expressions>
<values>
<systembeep>
<joystick>
<summarydata>
<text fixation>
<text summaryFeedback>
<text bluereminder>
<trial yellowcongruent>
<display>
<text bluecontrol>
<text finish>
<text greencongruent>
<trial yellowcontrol>
<trial yellowincongruent>
<list latencies_incongruent>
<text yellowcongruent>
<script>
<expt 1>
<trial finish>
<inquisit>
<list latencies_control>
<list latencies_congruent>
<list responses>
<block stroop>
<parameters>
<trial greencongruent>
<text greenreminder>
<text yellowreminder>
<text exit>
<text yellowcontrol>
<clearscreen monitor2>
<text target>
<text redcontrol>
<text ready>
<htmlpage intro2>
<instruct>
<list responses_control>
<trial greencontrol>
<text blueincongruent>
Results...
WARNING: OpenGL Invalid State - Sanity Check.. Function bool __cdecl inquisit::Graphics::MonitorInfo::makeCurrent(void), File Graphics.cpp, Line 401 GL Error Codes: GL_INVALID_FRAMEBUFFER_OPERATION: GL_FRAMEBUFFER: GL_FRAMEBUFFER_COMPLETE: Framebuffer Complete. GL_READ_FRAMEBUFFER_ANGLE:GL_FRAMEBUFFER_COMPLETE: Framebuffer Complete.
ERROR: OpenGL Error: IQOpenGLFramebufferObject. OpenGL Error: GL_INVALID_FRAMEBUFFER_OPERATION. blitFramebuffer File: C:\inquisit6\IQRuntime\qt\IQOpenGLFramebufferObject.cpp:1927
ERROR: OpenGL Error: IQOpenGLFramebufferObject. OpenGL Error: GL_INVALID_FRAMEBUFFER_OPERATION. blitFramebuffer File: C:\inquisit6\IQRuntime\qt\IQOpenGLFramebufferObject.cpp:1944
Data file: C:/Users/fran/Desktop/MRC Study 1 Tasks/data/stroopwithcontrolkeyboard_raw_TEST,1012_2023-07-04-09-13-24-511.iqdat
Data file: C:/Users/fran/Desktop/MRC Study 1 Tasks/data/stroopwithcontrolkeyboard_summary_TEST,1012_2023-07-04-09-13-24-511.iqdat


I have validated the scripts and did a Monkey Test run but both produced no issues with the code. This is what the screen looks like after the crash:



We do not understand why this keeps happening and we hope you are able to provide a solution to this issue, or point us in the right direction.

Many thanks,

Toni

The error indicates a problem with the respective system's graphics card or driver. Typically, this is caused by graphics memory fragmentation due to lack of available graphics memory and/or an outdated or malfunctioning graphics card driver.

You should:
(1) Make sure you have the latest Inquisit Lab version installed on the system, i.e. version 6.6.1 as available at https://www.millisecond.com/download .
(2) Obtain and install the latest graphics card driver available from the device's manufacturer.

Hi Dave,

Thanks so much for the quick response. I will do what you have advised and update the post if it has been resolved.

Best wishes,

Toni

+x

 

Dave - 7/4/2023

+x

 

Toni Mo - 7/4/2023

+x

 

Dave - 7/4/2023

+x

 

Toni Mo - 7/4/2023

Hi,

We run a total of 3 tasks during data collection for our lab sessions - Emotional Stroop task, Colour-word Strook task and SART. On a number of occasions, we have had the Inquisit program crash during one of the task. It happens to be the same task each time and the crash does not occur every time the program is run. Here is a copy of the code received when the program crashes during the task:

Checking system capabilities...
Timer resolution: 0.0001000000000000000 milliseconds
Display: 0: \\.\DISPLAY1
Color resolution: 32 bits per pixel
Display mode: 1920 x 1080
Refresh Rate: 60 Hz
Videosync support: DXGIWaitForVBlankMode.
Building Experiment...
Extracting elements from C:/Users/fran/Desktop/MRC Study 1 Tasks/stroopwithcontrolkeyboard.iqx...
Parsing elements...
<htmlpage intro3>
<defaults>
<htmlpage intro4>
<text yellowincongruent>
<data>
<text x>
<trial redcongruent>
<list latencies>
<trial redincongruent>
<text greencontrol>
<computer>
<block finish>
<text greenincongruent>
<trial bluecongruent>
<list responses_congruent>
<list responses_incongruent>
<trial bluecontrol>
<monkey>
<text redreminder>
<htmlpage intro1>
<trial redcontrol>
<text redincongruent>
<trial blueincongruent>
<mouse>
<clearscreen>
<trial getReady>
<text bluecongruent>
<text getReady>
<text redcongruent>
<trial greenincongruent>
<expressions>
<values>
<systembeep>
<joystick>
<summarydata>
<text fixation>
<text summaryFeedback>
<text bluereminder>
<trial yellowcongruent>
<display>
<text bluecontrol>
<text finish>
<text greencongruent>
<trial yellowcontrol>
<trial yellowincongruent>
<list latencies_incongruent>
<text yellowcongruent>
<script>
<expt 1>
<trial finish>
<inquisit>
<list latencies_control>
<list latencies_congruent>
<list responses>
<block stroop>
<parameters>
<trial greencongruent>
<text greenreminder>
<text yellowreminder>
<text exit>
<text yellowcontrol>
<clearscreen monitor2>
<text target>
<text redcontrol>
<text ready>
<htmlpage intro2>
<instruct>
<list responses_control>
<trial greencontrol>
<text blueincongruent>
Results...
WARNING: OpenGL Invalid State - Sanity Check.. Function bool __cdecl inquisit::Graphics::MonitorInfo::makeCurrent(void), File Graphics.cpp, Line 401 GL Error Codes: GL_INVALID_FRAMEBUFFER_OPERATION: GL_FRAMEBUFFER: GL_FRAMEBUFFER_COMPLETE: Framebuffer Complete. GL_READ_FRAMEBUFFER_ANGLE:GL_FRAMEBUFFER_COMPLETE: Framebuffer Complete.
ERROR: OpenGL Error: IQOpenGLFramebufferObject. OpenGL Error: GL_INVALID_FRAMEBUFFER_OPERATION. blitFramebuffer File: C:\inquisit6\IQRuntime\qt\IQOpenGLFramebufferObject.cpp:1927
ERROR: OpenGL Error: IQOpenGLFramebufferObject. OpenGL Error: GL_INVALID_FRAMEBUFFER_OPERATION. blitFramebuffer File: C:\inquisit6\IQRuntime\qt\IQOpenGLFramebufferObject.cpp:1944
Data file: C:/Users/fran/Desktop/MRC Study 1 Tasks/data/stroopwithcontrolkeyboard_raw_TEST,1012_2023-07-04-09-13-24-511.iqdat
Data file: C:/Users/fran/Desktop/MRC Study 1 Tasks/data/stroopwithcontrolkeyboard_summary_TEST,1012_2023-07-04-09-13-24-511.iqdat


I have validated the scripts and did a Monkey Test run but both produced no issues with the code. This is what the screen looks like after the crash:



We do not understand why this keeps happening and we hope you are able to provide a solution to this issue, or point us in the right direction.

Many thanks,

Toni

The error indicates a problem with the respective system's graphics card or driver. Typically, this is caused by graphics memory fragmentation due to lack of available graphics memory and/or an outdated or malfunctioning graphics card driver.

You should:
(1) Make sure you have the latest Inquisit Lab version installed on the system, i.e. version 6.6.1 as available at https://www.millisecond.com/download .
(2) Obtain and install the latest graphics card driver available from the device's manufacturer.

Hi Dave,

Thanks so much for the quick response. I will do what you have advised and update the post if it has been resolved.

Best wishes,

Toni

Please do. If you happen to have a rather old Inquisit 6 Lab version installed, updating to the latest one should make a noticeable difference -- there have been a lot of optimizations over time cutting down on the amount graphics operations to lessen the likelihood of exactly these types of errors. A small number of systems, however, will still occasionally run into this problem, due to a variety of reasons (faulty driver and/or just general lack of available (graphics) memory).

+x

 

Toni Mo - 7/5/2023

+x

 

Dave - 7/4/2023

+x

 

Toni Mo - 7/4/2023

+x

 

Dave - 7/4/2023

+x

 

Toni Mo - 7/4/2023

Hi,

We run a total of 3 tasks during data collection for our lab sessions - Emotional Stroop task, Colour-word Strook task and SART. On a number of occasions, we have had the Inquisit program crash during one of the task. It happens to be the same task each time and the crash does not occur every time the program is run. Here is a copy of the code received when the program crashes during the task:

Checking system capabilities...
Timer resolution: 0.0001000000000000000 milliseconds
Display: 0: \\.\DISPLAY1
Color resolution: 32 bits per pixel
Display mode: 1920 x 1080
Refresh Rate: 60 Hz
Videosync support: DXGIWaitForVBlankMode.
Building Experiment...
Extracting elements from C:/Users/fran/Desktop/MRC Study 1 Tasks/stroopwithcontrolkeyboard.iqx...
Parsing elements...
<htmlpage intro3>
<defaults>
<htmlpage intro4>
<text yellowincongruent>
<data>
<text x>
<trial redcongruent>
<list latencies>
<trial redincongruent>
<text greencontrol>
<computer>
<block finish>
<text greenincongruent>
<trial bluecongruent>
<list responses_congruent>
<list responses_incongruent>
<trial bluecontrol>
<monkey>
<text redreminder>
<htmlpage intro1>
<trial redcontrol>
<text redincongruent>
<trial blueincongruent>
<mouse>
<clearscreen>
<trial getReady>
<text bluecongruent>
<text getReady>
<text redcongruent>
<trial greenincongruent>
<expressions>
<values>
<systembeep>
<joystick>
<summarydata>
<text fixation>
<text summaryFeedback>
<text bluereminder>
<trial yellowcongruent>
<display>
<text bluecontrol>
<text finish>
<text greencongruent>
<trial yellowcontrol>
<trial yellowincongruent>
<list latencies_incongruent>
<text yellowcongruent>
<script>
<expt 1>
<trial finish>
<inquisit>
<list latencies_control>
<list latencies_congruent>
<list responses>
<block stroop>
<parameters>
<trial greencongruent>
<text greenreminder>
<text yellowreminder>
<text exit>
<text yellowcontrol>
<clearscreen monitor2>
<text target>
<text redcontrol>
<text ready>
<htmlpage intro2>
<instruct>
<list responses_control>
<trial greencontrol>
<text blueincongruent>
Results...
WARNING: OpenGL Invalid State - Sanity Check.. Function bool __cdecl inquisit::Graphics::MonitorInfo::makeCurrent(void), File Graphics.cpp, Line 401 GL Error Codes: GL_INVALID_FRAMEBUFFER_OPERATION: GL_FRAMEBUFFER: GL_FRAMEBUFFER_COMPLETE: Framebuffer Complete. GL_READ_FRAMEBUFFER_ANGLE:GL_FRAMEBUFFER_COMPLETE: Framebuffer Complete.
ERROR: OpenGL Error: IQOpenGLFramebufferObject. OpenGL Error: GL_INVALID_FRAMEBUFFER_OPERATION. blitFramebuffer File: C:\inquisit6\IQRuntime\qt\IQOpenGLFramebufferObject.cpp:1927
ERROR: OpenGL Error: IQOpenGLFramebufferObject. OpenGL Error: GL_INVALID_FRAMEBUFFER_OPERATION. blitFramebuffer File: C:\inquisit6\IQRuntime\qt\IQOpenGLFramebufferObject.cpp:1944
Data file: C:/Users/fran/Desktop/MRC Study 1 Tasks/data/stroopwithcontrolkeyboard_raw_TEST,1012_2023-07-04-09-13-24-511.iqdat
Data file: C:/Users/fran/Desktop/MRC Study 1 Tasks/data/stroopwithcontrolkeyboard_summary_TEST,1012_2023-07-04-09-13-24-511.iqdat


I have validated the scripts and did a Monkey Test run but both produced no issues with the code. This is what the screen looks like after the crash:



We do not understand why this keeps happening and we hope you are able to provide a solution to this issue, or point us in the right direction.

Many thanks,

Toni

The error indicates a problem with the respective system's graphics card or driver. Typically, this is caused by graphics memory fragmentation due to lack of available graphics memory and/or an outdated or malfunctioning graphics card driver.

You should:
(1) Make sure you have the latest Inquisit Lab version installed on the system, i.e. version 6.6.1 as available at https://www.millisecond.com/download .
(2) Obtain and install the latest graphics card driver available from the device's manufacturer.

Hi Dave,

Thanks so much for the quick response. I will do what you have advised and update the post if it has been resolved.

Best wishes,

Toni

Please do. If you happen to have a rather old Inquisit 6 Lab version installed, updating to the latest one should make a noticeable difference -- there have been a lot of optimizations over time cutting down on the amount graphics operations to lessen the likelihood of exactly these types of errors. A small number of systems, however, will still occasionally run into this problem, due to a variety of reasons (faulty driver and/or just general lack of available (graphics) memory).

Hi Dave,

I have installed the latest version of Inquisit 6 Lab, but the problem still persists (crashed again after 7 trials).
Here are the details of the graphics card:
does this meet the Inquisit requirements?
I have also tried to update the driver and it says I have the latest driver updated.

Still wondering what the problem could be and any help is much appreciated.

Best wishes,
Toni

+x

 

Dave - 7/5/2023

+x

 

Toni Mo - 7/5/2023

+x

 

Dave - 7/4/2023

+x

 

Toni Mo - 7/4/2023

+x

 

Dave - 7/4/2023

+x

 

Toni Mo - 7/4/2023

Hi,

We run a total of 3 tasks during data collection for our lab sessions - Emotional Stroop task, Colour-word Strook task and SART. On a number of occasions, we have had the Inquisit program crash during one of the task. It happens to be the same task each time and the crash does not occur every time the program is run. Here is a copy of the code received when the program crashes during the task:

Checking system capabilities...
Timer resolution: 0.0001000000000000000 milliseconds
Display: 0: \\.\DISPLAY1
Color resolution: 32 bits per pixel
Display mode: 1920 x 1080
Refresh Rate: 60 Hz
Videosync support: DXGIWaitForVBlankMode.
Building Experiment...
Extracting elements from C:/Users/fran/Desktop/MRC Study 1 Tasks/stroopwithcontrolkeyboard.iqx...
Parsing elements...
<htmlpage intro3>
<defaults>
<htmlpage intro4>
<text yellowincongruent>
<data>
<text x>
<trial redcongruent>
<list latencies>
<trial redincongruent>
<text greencontrol>
<computer>
<block finish>
<text greenincongruent>
<trial bluecongruent>
<list responses_congruent>
<list responses_incongruent>
<trial bluecontrol>
<monkey>
<text redreminder>
<htmlpage intro1>
<trial redcontrol>
<text redincongruent>
<trial blueincongruent>
<mouse>
<clearscreen>
<trial getReady>
<text bluecongruent>
<text getReady>
<text redcongruent>
<trial greenincongruent>
<expressions>
<values>
<systembeep>
<joystick>
<summarydata>
<text fixation>
<text summaryFeedback>
<text bluereminder>
<trial yellowcongruent>
<display>
<text bluecontrol>
<text finish>
<text greencongruent>
<trial yellowcontrol>
<trial yellowincongruent>
<list latencies_incongruent>
<text yellowcongruent>
<script>
<expt 1>
<trial finish>
<inquisit>
<list latencies_control>
<list latencies_congruent>
<list responses>
<block stroop>
<parameters>
<trial greencongruent>
<text greenreminder>
<text yellowreminder>
<text exit>
<text yellowcontrol>
<clearscreen monitor2>
<text target>
<text redcontrol>
<text ready>
<htmlpage intro2>
<instruct>
<list responses_control>
<trial greencontrol>
<text blueincongruent>
Results...
WARNING: OpenGL Invalid State - Sanity Check.. Function bool __cdecl inquisit::Graphics::MonitorInfo::makeCurrent(void), File Graphics.cpp, Line 401 GL Error Codes: GL_INVALID_FRAMEBUFFER_OPERATION: GL_FRAMEBUFFER: GL_FRAMEBUFFER_COMPLETE: Framebuffer Complete. GL_READ_FRAMEBUFFER_ANGLE:GL_FRAMEBUFFER_COMPLETE: Framebuffer Complete.
ERROR: OpenGL Error: IQOpenGLFramebufferObject. OpenGL Error: GL_INVALID_FRAMEBUFFER_OPERATION. blitFramebuffer File: C:\inquisit6\IQRuntime\qt\IQOpenGLFramebufferObject.cpp:1927
ERROR: OpenGL Error: IQOpenGLFramebufferObject. OpenGL Error: GL_INVALID_FRAMEBUFFER_OPERATION. blitFramebuffer File: C:\inquisit6\IQRuntime\qt\IQOpenGLFramebufferObject.cpp:1944
Data file: C:/Users/fran/Desktop/MRC Study 1 Tasks/data/stroopwithcontrolkeyboard_raw_TEST,1012_2023-07-04-09-13-24-511.iqdat
Data file: C:/Users/fran/Desktop/MRC Study 1 Tasks/data/stroopwithcontrolkeyboard_summary_TEST,1012_2023-07-04-09-13-24-511.iqdat


I have validated the scripts and did a Monkey Test run but both produced no issues with the code. This is what the screen looks like after the crash:



We do not understand why this keeps happening and we hope you are able to provide a solution to this issue, or point us in the right direction.

Many thanks,

Toni

The error indicates a problem with the respective system's graphics card or driver. Typically, this is caused by graphics memory fragmentation due to lack of available graphics memory and/or an outdated or malfunctioning graphics card driver.

You should:
(1) Make sure you have the latest Inquisit Lab version installed on the system, i.e. version 6.6.1 as available at https://www.millisecond.com/download .
(2) Obtain and install the latest graphics card driver available from the device's manufacturer.

Hi Dave,

Thanks so much for the quick response. I will do what you have advised and update the post if it has been resolved.

Best wishes,

Toni

Please do. If you happen to have a rather old Inquisit 6 Lab version installed, updating to the latest one should make a noticeable difference -- there have been a lot of optimizations over time cutting down on the amount graphics operations to lessen the likelihood of exactly these types of errors. A small number of systems, however, will still occasionally run into this problem, due to a variety of reasons (faulty driver and/or just general lack of available (graphics) memory).

Hi Dave,

I have installed the latest version of Inquisit 6 Lab, but the problem still persists (crashed again after 7 trials).
Here are the details of the graphics card:
does this meet the Inquisit requirements?
I have also tried to update the driver and it says I have the latest driver updated.

Still wondering what the problem could be and any help is much appreciated.

Best wishes,
Toni

Theoretically it meets the requirements. That said, this integrated GPU is known to show OpenGL performance issues on some systems, at least with some driver versions (see e.g. https://www.intel.com/content/www/us/en/support/articles/000037954/graphics.html ). What source did you check with respect to the drivers? Windows Update? Intel's website? The system manufacturer's site?

+x

 

Toni Mo - 7/5/2023

+x

 

Dave - 7/5/2023

+x

 

Toni Mo - 7/5/2023

+x

 

Dave - 7/4/2023

+x

 

Toni Mo - 7/4/2023

+x

 

Dave - 7/4/2023

+x

 

Toni Mo - 7/4/2023

Hi,

We run a total of 3 tasks during data collection for our lab sessions - Emotional Stroop task, Colour-word Strook task and SART. On a number of occasions, we have had the Inquisit program crash during one of the task. It happens to be the same task each time and the crash does not occur every time the program is run. Here is a copy of the code received when the program crashes during the task:

Checking system capabilities...
Timer resolution: 0.0001000000000000000 milliseconds
Display: 0: \\.\DISPLAY1
Color resolution: 32 bits per pixel
Display mode: 1920 x 1080
Refresh Rate: 60 Hz
Videosync support: DXGIWaitForVBlankMode.
Building Experiment...
Extracting elements from C:/Users/fran/Desktop/MRC Study 1 Tasks/stroopwithcontrolkeyboard.iqx...
Parsing elements...
<htmlpage intro3>
<defaults>
<htmlpage intro4>
<text yellowincongruent>
<data>
<text x>
<trial redcongruent>
<list latencies>
<trial redincongruent>
<text greencontrol>
<computer>
<block finish>
<text greenincongruent>
<trial bluecongruent>
<list responses_congruent>
<list responses_incongruent>
<trial bluecontrol>
<monkey>
<text redreminder>
<htmlpage intro1>
<trial redcontrol>
<text redincongruent>
<trial blueincongruent>
<mouse>
<clearscreen>
<trial getReady>
<text bluecongruent>
<text getReady>
<text redcongruent>
<trial greenincongruent>
<expressions>
<values>
<systembeep>
<joystick>
<summarydata>
<text fixation>
<text summaryFeedback>
<text bluereminder>
<trial yellowcongruent>
<display>
<text bluecontrol>
<text finish>
<text greencongruent>
<trial yellowcontrol>
<trial yellowincongruent>
<list latencies_incongruent>
<text yellowcongruent>
<script>
<expt 1>
<trial finish>
<inquisit>
<list latencies_control>
<list latencies_congruent>
<list responses>
<block stroop>
<parameters>
<trial greencongruent>
<text greenreminder>
<text yellowreminder>
<text exit>
<text yellowcontrol>
<clearscreen monitor2>
<text target>
<text redcontrol>
<text ready>
<htmlpage intro2>
<instruct>
<list responses_control>
<trial greencontrol>
<text blueincongruent>
Results...
WARNING: OpenGL Invalid State - Sanity Check.. Function bool __cdecl inquisit::Graphics::MonitorInfo::makeCurrent(void), File Graphics.cpp, Line 401 GL Error Codes: GL_INVALID_FRAMEBUFFER_OPERATION: GL_FRAMEBUFFER: GL_FRAMEBUFFER_COMPLETE: Framebuffer Complete. GL_READ_FRAMEBUFFER_ANGLE:GL_FRAMEBUFFER_COMPLETE: Framebuffer Complete.
ERROR: OpenGL Error: IQOpenGLFramebufferObject. OpenGL Error: GL_INVALID_FRAMEBUFFER_OPERATION. blitFramebuffer File: C:\inquisit6\IQRuntime\qt\IQOpenGLFramebufferObject.cpp:1927
ERROR: OpenGL Error: IQOpenGLFramebufferObject. OpenGL Error: GL_INVALID_FRAMEBUFFER_OPERATION. blitFramebuffer File: C:\inquisit6\IQRuntime\qt\IQOpenGLFramebufferObject.cpp:1944
Data file: C:/Users/fran/Desktop/MRC Study 1 Tasks/data/stroopwithcontrolkeyboard_raw_TEST,1012_2023-07-04-09-13-24-511.iqdat
Data file: C:/Users/fran/Desktop/MRC Study 1 Tasks/data/stroopwithcontrolkeyboard_summary_TEST,1012_2023-07-04-09-13-24-511.iqdat


I have validated the scripts and did a Monkey Test run but both produced no issues with the code. This is what the screen looks like after the crash:



We do not understand why this keeps happening and we hope you are able to provide a solution to this issue, or point us in the right direction.

Many thanks,

Toni

The error indicates a problem with the respective system's graphics card or driver. Typically, this is caused by graphics memory fragmentation due to lack of available graphics memory and/or an outdated or malfunctioning graphics card driver.

You should:
(1) Make sure you have the latest Inquisit Lab version installed on the system, i.e. version 6.6.1 as available at https://www.millisecond.com/download .
(2) Obtain and install the latest graphics card driver available from the device's manufacturer.

Hi Dave,

Thanks so much for the quick response. I will do what you have advised and update the post if it has been resolved.

Best wishes,

Toni

Please do. If you happen to have a rather old Inquisit 6 Lab version installed, updating to the latest one should make a noticeable difference -- there have been a lot of optimizations over time cutting down on the amount graphics operations to lessen the likelihood of exactly these types of errors. A small number of systems, however, will still occasionally run into this problem, due to a variety of reasons (faulty driver and/or just general lack of available (graphics) memory).

Hi Dave,

I have installed the latest version of Inquisit 6 Lab, but the problem still persists (crashed again after 7 trials).
Here are the details of the graphics card:
does this meet the Inquisit requirements?
I have also tried to update the driver and it says I have the latest driver updated.

Still wondering what the problem could be and any help is much appreciated.

Best wishes,
Toni

Theoretically it meets the requirements. That said, this integrated GPU is known to show OpenGL performance issues on some systems, at least with some driver versions (see e.g. https://www.intel.com/content/www/us/en/support/articles/000037954/graphics.html ). What source did you check with respect to the drivers? Windows Update? Intel's website? The system manufacturer's site?

I used Windows Update to check for the driver updates and I received this message.

Would that be different from the update from Intel's website?