This article applies to:
Freezing or crashing occurs after entering the StartupInfo parameters or after the experiment completes.
Freezing and crashing has been observed with specific chipsets. For example, crashing has been observed on an Intel Xeon E5-2640 v4 after the StartupInfo prompts as well as at the end of the experiment run. This was resolved by implementing Workaround's 1 and 2.
Another machine (using an AMD Ryzen 9 3900X) experienced issues with crashing at the end of the experiment. This was resolved by implementing Workaround's 2 or 4.
Current affected chipsets:
- Intel Xeon E5-2640 v4
- Intel Xeon Platinum 8160
- AMD Ryzen 9 3900X
- AMD Ryzen 9 5950X
NOTE: Please inform PST if you have compatibility issues with a certain chipset so we can update this listing.
The following workarounds are possible. Note that you may need to implement one or more.
This is primarily for users experiencing freezing or crashing after the StartupInfo prompts.
Set the SetOSThreadPriority.Init.Override and SetOSThreadPriority.Override in StartupInfo Editor to 0, 1, 2, 3, or 527. This may take multiple attempts until you find a configuration that works for you.
For more information, see E-BASIC: SetOSThreadPriority permits wider range options including auto configure  and OVERVIEW: Modifying StartupInfo using StartupInfo Editor .
This is primarily for users experiencing freezing or crashing at the end of the experiment run.
Disable the Experiment Advisor Report and modules. To do so, open the Experiment Object Property Pages > Experiment Advisor tab and Uncheck all Report File and Modules.
NOTE: If this resolves the issue, you may enable and test each one individually to find the specific module to disable.
For more information, see E-STUDIO: Experiment Advisor Window .
Set E-Studio core affinity. To set E-Studio affinity, open E-Studio > open Task Manager > Details tab > find E-Studio and right-click > Set Affinity. Set a specific core(s) to see if it helps performance.
If setting a core or set of cores resolves the issue on the issue machine, the E-Studio shortcuts can be edited to open and run on a specific core(s). (Core Affinity is not saved and will revert to all on close.)
For example, you can change the Target of the E-Studio shortcut to: C:\Windows\System32\cmd.exe /c start "" /Normal /Affinity 0x1 "C:\Program Files (x86)\PST\E-Prime 3.0\Program\E-Studio.exe"
NOTE: The Affinity is a Hex value. For more information see https://bitsum.com/tools/cpu-affinity-calculator/.
This is primarily for users experiencing freezing or crashing and the workarounds above did not resolve this issue.
NOTE: This workaround should only be performed if the above steps do not work. Adjusting settings to your computer should be done at your own risk.
Disable any SMT (simultaneous multi-threading) or HT (hyper-threading) in your machine's BIOS/UEFI. Consult with your hardware manufacturer for the specific setting and location.
ERROR: Multiple monitor experiments run on Windows 10 (2004, 20H2, 21H1, 21H2) or Windows 11 freeze or receive a display is too busy error (Error 11102) 
ERROR: Experiments run on Windows 10 (1903 & 1909) freeze or receive a display is too busy error (Error 11102) 
Please sign in to leave a comment.