I found the WER file. The others don’t seem to be present.
Report.zip (5.2 KB)
Observed in latest hang: Audio stops, GUI frozen.
2nd Instance (empty, doing nothing) seems to be unaffected.
These are the loaded modules from your crash that are not Windows system modules, I would focus on eliminating these in this order:
|1|C:\Users\Public\Documents\Gig Performer\Extensions\GPImageViewer.dll|
|2|C:\Program Files\Scuffham Amps\S-Gear\FlxComm64.dll|
|3|C:\Program Files\Scuffham Amps\S-Gear\FlxCore64.dll|
|4|C:\ProgramData\Line 6\HelixCore\HelixCoreWin_x64.dll|
|5|C:\ProgramData\Jamstix4\bin\js4sl64.rtxc|
|6|C:\Program Files\MOTU\MAWASIO.DRV|
|7|C:\Program Files\Gig Performer 5\GigPerformer5.exe|
|8|C:\Program Files\Gig Performer 5\WinSparkle.dll|
|9|C:\Program Files\Bonjour\mdnsNSP.dll|
|10|C:\ProgramData\Microsoft\Windows Defender\Platform\4.18.24090.11-0\MpOav.dll|
Ignoring 7 and 8 GigPerformer itself, 9 and 10 are “almost” system modules.
MOTU drivers are typically stable but wouldn’t hurt to make sure you have the latest, or if it was recently updated possibly downgrading to a previous version.
This may narrow it down.
2 Likes
Duh - that’s the whole point of such tests!
If you turn off GP Script and now everything works (minus your gp script functionality) you would now KNOW that the problem has to do with something you’re doing in GP Script. And if it still hung, then you would know the problem has nothing to do with whatever you’re doing with GP Script.
That is why it is called a differential diagnosis - to eliminate possible causes of the problem
I can’t help you any more — if you can’t do the work to try and determine what change caused the problem to happen, there’s no way for anybody to just tell you what’s wrong.
Sorry
3 Likes
I was curious so did the search: an audio time-stretching and pitch-shifting library.
Presumably used within the SAFP.
2 Likes