psychopy.org | Reference | Downloads | Github

PsychoPy (or Windows ?) bug

Hi Developers,

I think I might have accross with a bug for which I don’t know if it is down to windows or psychopy (or me).

In my system (see info below), once I connect a second monitor via vga I get the following error (the task involves sound stimuli and mic responses). Once I remove the connection the task runs just fine.


 Running: C:\Users\iargi\Desktop\Project stimuli\Repimm_task\rep_imm_lastrun.py 
pygame 1.9.4
Hello from the pygame community. https://www.pygame.org/contribute.html
Traceback (most recent call last):
  File "C:\Users\iargi\Desktop\Project stimuli\Repimm_task\rep_imm_lastrun.py", line 64, in <module>
    units='height')
  File "C:\Program Files (x86)\PsychoPy3\lib\site-packages\psychopy\visual\window.py", line 389, in __init__
    self.backend = backends.getBackend(win=self, *args, **kwargs)
  File "C:\Program Files (x86)\PsychoPy3\lib\site-packages\psychopy\visual\backends\__init__.py", line 32, in getBackend
    return Backend(win, *args, **kwargs)
  File "C:\Program Files (x86)\PsychoPy3\lib\site-packages\psychopy\visual\backends\pygletbackend.py", line 227, in __init__
    self._origGammaRamp = self.getGammaRamp()
  File "C:\Program Files (x86)\PsychoPy3\lib\site-packages\psychopy\visual\backends\pygletbackend.py", line 329, in getGammaRamp
    return getGammaRamp(self.screenID, self.xDisplay)
  File "C:\Program Files (x86)\PsychoPy3\lib\site-packages\psychopy\visual\backends\gamma.py", line 128, in getGammaRamp
    raise AssertionError('GetDeviceGammaRamp failed')
AssertionError: GetDeviceGammaRamp failed
Exception ignored in: <bound method Window.__del__ of <psychopy.visual.window.Window object at 0x000001B70C36C630>>
Traceback (most recent call last):
  File "C:\Program Files (x86)\PsychoPy3\lib\site-packages\psychopy\visual\window.py", line 501, in __del__
    self.close()
  File "C:\Program Files (x86)\PsychoPy3\lib\site-packages\psychopy\visual\window.py", line 1327, in close
    self.backend.close()  # moved here, dereferencing the window prevents
AttributeError: 'NoneType' object has no attribute 'close'

My system info

OS Name Microsoft Windows 10 Home
Version 10.0.18362 Build 18362
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name LAPTOP-SRHRC6VH
System Manufacturer LENOVO
System Model 80SM
System Type x64-based PC
System SKU LENOVO_MT_80SM_BU_idea_FM_Lenovo ideapad 310-15ISK
Processor Intel® Core™ i3-6100U CPU @ 2.30GHz, 2304 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date LENOVO 0XCN44WW, 12/04/2018
SMBIOS Version 2.8
Embedded Controller Version 1.44
BIOS Mode UEFI
BaseBoard Manufacturer LENOVO
BaseBoard Product Toronto 5A2
BaseBoard Version SDK0J40700 WIN
Platform Role Mobile
Secure Boot State On
PCR7 Configuration Elevation Required to View
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United Kingdom
Hardware Abstraction Layer Version = “10.0.18362.267”
User Name LAPTOP-SRHRC6VH\iargi
Time Zone GMT Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.91 GB
Available Physical Memory 2.97 GB
Total Virtual Memory 13.5 GB
Available Virtual Memory 6.56 GB
Page File Space 5.62 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Elevation Required to View
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware No
Hyper-V - Data Execution Protection Yes

Hi, Yiannis

I have met the same error when I updated my Windows10 manually (from 1803 or 1809 to new 1903 build).
Check your Windows10’s build number. If the number is 1903, I guess that causes problem.

If you have just updated it, you can go back to the previous build.
(I went back to the previous build.)

Also, I found an emergency solution to avoid this problem.
I think this error often occurs in multi-monitor environment.
If you use multi monitors, try turning on one monitor and turning off the other when you run your experiment program.

Good luck,
Daiki

Hi Daiki,

Thanks for your post.

Yes my version is 1903 (which was a pain to update to this version).

Indeed it is a dual (or more) monitor setup that causes the issue as per my original post.

Not a problem for me as i do not intent to use more than one monitor at a time.