Crash Experiences Concerns

Couldn’t agree more.

You can choose what the Power button does in Power Options:

That is good to know, it is definitely getting set to “Do Nothing” since I don’t use it anyway. On my HP there is about 1/4" between the power button and the ESC key. Small enough that my fat finger can easily hit both at once!

1 Like

LOL… you know that feeling when everyone looks at you and says “Are you ready?” and your like “ughhh, I have a problem”


Me, shouting to the other band musicians:“You need to play a song without keyboards, NOW!”

Happened once in a while with my former live host, Brainspawn Forte on a Win7 laptop. Not with GP.


In my band, I shout the same thing out but just because I need to go to the bathroom😂


Yeah, if you wait for a GP crash to go to the bathroom, things can go wrong before :grimacing::stuck_out_tongue_winking_eye:


Mainstage is unstable in my experience. GigPerformer never crashed. Mainstage has a huge CPU problem and GigPerformer does not have high CPU uage. This is a major difference. I cannot use Mainstage as it crashes even with the most powerful Macbook Pros. I never faced a crash with GigPerformer.


I had to abandon all Firewire devices with Windows 10 version 1903. It broke Firewire performance and caused constant dropouts.
I’ve never had GP cause a BSOD. I have had a crash due to a plugin that did not like patch change messages. I resolved that by simply creating different rackspaces and variants instead of using a widget to send patch change messages.
Use LatencyMon to determine if the computer is optimized for audio.

1 Like

Has anyone experienced BSODs and identified the cause to be Iconnectivity’s MioXL?

Hello everybody!

I am pretty new in using Gig Performer and really love it. I am a guitarist and use it mainly with S-Gear as amp setup, and with MidiGuitar2 as guitar synth.

I had some issues to solve, maybe this helps other folks just starting with GP.

  1. I had crashes virtually every time I edited something in the “options”. I first also had a terrible big latency - I use Scarlett Solo 3r gen as interface.
    Mistake: I had set the audio input on “Windows Audio” because I had thought that ASIO is always equals ASIO4all, which I had used for the setup of my mfx.
    Solution: Set audio to ASIO and then to Facusrite…

  2. I often had crashes when starting GP. I have to say, that I play just on sessions and don’t use songs, but just rackspaces for each sound I want to use. And as mentioned above I use Sgear and MidiGuitar2 as main vsts.
    Solution: Setting MidiGuitar on “delayed loading”.

  3. I got the blue screen when I disconnected the Scarlett while running GP.
    Solution: Hands off the USB-Plug! :wink:

  4. Sometimes - I think at moments of rather high gain - my headphones plugged in the Scarlett get muted. I am not sure about the main output of the interface.
    No solution yet found. I guess I will lower the gain settings in the rackspaces. I use them pretty much up to zero db in order to use the full range of the digital “solution” (I come from the field of photography where one has to be aware of the “depth of solution” one uses when taking a picture).

For issue #4 I’d be glad to get some advice in case anybody has had the same experience or just an idea, what could be the reason for the switch-off of the headphone output at the Scarlett.

Greetings from Germany

Hans Gruber (yes, I didn’t fall off the nakatomi tower! :slight_smile: )

GP3 or GP4?

GP3. Indeed!


@Real_Hans_Gruber welcome to our forums!

You have to use ASIO drivers on Windows or the latency will simply not be adequate. The BSOD issue when plugin something in or out of your computer is only related to your drivers as GP cannot crash your computer - a driver can. Please make sure you have the latest drivers for your interface and your computer is up to date.

The issue #4 seems to be related to your interface and not to GP. Maybe someone i the forums will be able to help you with this.

1 Like


Yep, obviously a known problem with Scarlett interface:

1 Like

I was using the standard Firewire driver and the 800 port. I have since installed the Legacy driver “1394_OHCI_LegacyDriver.msi” as you suggested:

No problems so far. I will report back to group if this clears up my BSOD. Thanks for your help :slight_smile:

1 Like

Hope that helps.

If you still have issues, you could try switching to a 400 port if your card has one and if you have a correct cable. As I said earlier, there will be no performance difference and I’ve seen more complaints of problems with Windows and Firewire 800 drivers than the 400 drivers.

1 Like

Thanks for the link. Yet my issue is somewhat different! I may be able to hear my playing on headphones for a certain time but then the headphones are suddenly muted.
I haven’t checked the symmetrical audio outputs, if they are also “dead”, that’s what I am going to do next.

YAY! Switching to the Firewire Legacy driver has solved my BSODs. My computer has been running for two solid days with no crashes. I am now a happy camper! Thanks so much guys :slight_smile: