Help determining why crash occured

OS and version: PC laptop running Windows 11 Version 25H2
RAM 64.0GB
CPU 12th Gen Intel Cor i7-12700H
Glyph Atom EV SSD 4TB USB-C Portable Solid State Drive to serve samples to laptop
Gig Performer version: Version before update to 5.2.2 (not sure which version number that was)

Plugins being used at the time: Opus VST3 (not updated to the latest version that came out last week (writing this as of 05/20/26); Kontact free player running Spitfire chamber strings; SWAM tenor sax; loopMidi

Audio: MOTU AudioExpress connected via usb-c to a OWC Thunderbolt 4 dock

Issue:
Booted up for a performance (I do musicals for communty theatre) and my iLok tried activating licenses since it was just renewed. However, the iLock was renewed a week prior, checked activations and worked fine the prior week. Also, I had no issues for the past three weekends of running the show. iLok wanted to reactivate which I ok’d. Opus engine from EastWest said there was an upgrade available, however, I don’t upgrade during the run of a show so I click on “no”.

Everything seemed to be fine with one song that I tested (BTW, I’m using a sequencer named “MidiMaestro” which was built years ago by never made it to wide-acceptance. It’s very simple and has everything I need to run a musical. It is a 32bit program, but I use Gig Performer to use my 64bit sounds). Started the show and GP kept crashing. Luckily I use a piano sound from a Roland Integra-7 just incase something like this occurs. I tried reloading my GP file but it would work for 15 measures or so and crash again. I finally switched to a previous GP file that I had saved from 3 weeks prior. Worked flawlessly after that.

I back up my midi/gp files to Dropbox which I had done a few days prior, however, Dropbox crapped out and said it couldn’t upload and the page went blank. I didn’t bother trying after that. As I think back, this happened a couple of times over the past months and each time I had to get a previous version of the GP file that I had saved. It’s almost like with the failure of the upload of the gig file to dropbox, the gig file corrupted. Just a thought.

The next day, next show, I used the same older gig file I had saved and everything worked fine except GP crashed toward the end of the show when nothing was playing. Sequencer was not playing. It crashed a couple of times while idle but I was able to get it to hold until the end of the show (after reloading twice).

The show has ended at this point but I ran it couple of times at home and couldn’t duplicate the problem. Since then, I have upgraded GP to 5.2.2 and also my instance of Opus.

I do have the issue on the laptop with the having to stop and restart midi-services because of the Microsoft rollout a couple of months ago that cut-off midiports.

Thanks for your insights/opinions/suggestions in advance. I’m not going to switch to a “commercial” DAW/sequencer as none can do vamps/holds/advance etc., things that are needed for musical theatre. I wish someone could look at MidiMaestro and flesh out to a 64 bit system to bring it up-to-date (it’s based off of Cubase) as it’s an amazing piece of software.

Link to crash files: Dropbox

Please follow this instruction: How to post a crash log on Windows

On Dropbox I see many logs and the dump, but another report is needed.

This may answer part of it:

1. The “Online-Only” (Smart Sync) Trap

Dropbox has a feature called Smart Sync or Make Online-Only. To save disk space, Dropbox will sometimes remove the actual file from your hard drive and leave a “placeholder” icon.

The Problem: If Gig Performer tries to open a gig file (or load an audio sample/preset) that Dropbox has turned into an “online-only” file, Gig Performer won’t be able to find it. At best, it will freeze while waiting for Dropbox to download it; at worst, your gig won’t load right before a show.

The Fix: Right-click your Gig Performer folders inside Dropbox and select Make available offline so they are permanently locked onto your local hard drive.

from Google Gemini

2 Likes

I was in a performance so could not get that information.

It is crucial that you do your best to reproduce the crash and post the crash log.

Yeah, using sync folders where the OS removes stuff under the covers will always bite you.

Strongly discourage people from doing this.

1 Like

Are not DMP and XML files for previous crashes stored somewhere on the machine already?

Not a windows user, but maybe this will help surface the needed information?

Does this help:

There should have been an XML file as well - do you have that?

it wouldn’t let me save as xml so I copied it into textpad. Let me know if this is it or I grabbed the wrong thing

We need the crash log, not the event log → this is how your create one.